Per risalire alla causa di un crash

pasta

nuovo riavvio:

sapete l'origine e una possibile soluzione?...ma sopratutto se siamo sempre nell'ambito dello stesso problema dei post precedenti?

Le085

quest'ultimo sembra un problema dei driver ati...

ma gli altri direi di no...

i problemi possono essere dovuti a:

- Sistema non stabile al 100% (dovuto a overclock o cattiva aliementazione)

- Sistema operativo corrotto (occorre formattare)

- Driver che vanno in conflitto

Sicuramente c'è da fare alcune prove... innanzitutto mettere tutto a default e vedere se hai ancora questo problema. Con che frequenza ti capitano i riavvii?

pasta

4ghz testato 2 ore con prime....l'alimentatore è un corsair 550 con un anno di vita e col sistema precedente sempre in oc non mi ha mai dato problemi per piu di un anno....ho cambiato cpu e mobo ed ecco questo thread

Le085

la stabilità con prime non è garantita al 100%... te lo fa spesso quando giochi? che modalità hai usato di prime?

pasta

blend, non non me lo fa spesso ma capita neanche raramente

tom1

a temperature come stai messo?

pasta

bene, sotto liquido

tom1

pasta ha scritto:

bene, sotto liquido

Usi l'ultima versione di linx

pasta

intanto altre 2 bsod:

1)

Microsoft (R) Windows Debugger Version 6.12.0002.633 AMD64
Copyright (c) Microsoft Corporation. All rights reserved.


Loading Dump File [C:WindowsMinidump120910-17706-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available

Symbol search path is: SRV*c:Windowssymbols*http://msdl.microsoft.com/download/symbols
Executable search path is: 
Windows 7 Kernel Version 7600 MP (4 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 7600.16617.amd64fre.win7_gdr.100618-1621
Machine Name:
Kernel base = 0xfffff800`0324c000 PsLoadedModuleList = 0xfffff800`03489e50
Debug session time: Thu Dec  9 14:06:55.126 2010 (UTC + 1:00)
System Uptime: 0 days 1:12:46.016
Loading Kernel Symbols
...............................................................
................................................................
.............................................
Loading User Symbols
Loading unloaded module list
....
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck D1, {8, 2, 1, fffff88002e5a95e}

Unable to load image SystemRootsystem32DRIVERS
etr7364.sys, Win32 error 0n2
*** WARNING: Unable to verify timestamp for netr7364.sys
*** ERROR: Module load completed but symbols could not be loaded for netr7364.sys
Probably caused by : hardware ( nwifi!Pt6RepackRecvNBL+2fa )

Followup: MachineOwner
---------

1: kd> !analyze -v
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

DRIVER_IRQL_NOT_LESS_OR_EQUAL (d1)
An attempt was made to access a pageable (or completely invalid) address at an
interrupt request level (IRQL) that is too high.  This is usually
caused by drivers using improper addresses.
If kernel debugger is available get stack backtrace.
Arguments:
Arg1: 0000000000000008, memory referenced
Arg2: 0000000000000002, IRQL
Arg3: 0000000000000001, value 0 = read operation, 1 = write operation
Arg4: fffff88002e5a95e, address which referenced memory

Debugging Details:
------------------


WRITE_ADDRESS: GetPointerFromAddress: unable to read from fffff800034f40e0
0000000000000008 

CURRENT_IRQL:  2

FAULTING_IP: 
nwifi!Pt6RepackRecvNBL+2fa
fffff880`02e5a95e 68488b97c0      push    0FFFFFFFFC0978B48h

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

BUGCHECK_STR:  0xD1

PROCESS_NAME:  LP2DX9.exe

TRAP_FRAME:  fffff88003322440 -- (.trap 0xfffff88003322440)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=0000000000000000 rbx=0000000000000000 rcx=fffff88003322570
rdx=0000000003ed5628 rsi=0000000000000000 rdi=0000000000000000
rip=fffff88002e5a95e rsp=fffff880033225d0 rbp=0000000000000000
r8=0000000000000000  r9=fffffa8004542ad9 r10=f5bc2f32e757d9b7
r11=fffffa80045429f0 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0         nv up ei pl zr na po nc
nwifi!Pt6RepackRecvNBL+0x2fa:
fffff880`02e5a95e 68488b97c0      push    0FFFFFFFFC0978B48h
Resetting default scope

MISALIGNED_IP: 
nwifi!Pt6RepackRecvNBL+2fa
fffff880`02e5a95e 68488b97c0      push    0FFFFFFFFC0978B48h

LAST_CONTROL_TRANSFER:  from fffff800032bbca9 to fffff800032bc740

STACK_TEXT:  
fffff880`033222f8 fffff800`032bbca9 : 00000000`0000000a 00000000`00000008 00000000`00000002 00000000`00000001 : nt!KeBugCheckEx
fffff880`03322300 fffff800`032ba920 : 00000000`00000000  fffffa80`04356b10 00000000`00000000 00000000`00000000 :  nt!KiBugCheckDispatch+0x69
fffff880`03322440 fffff880`02e5a95e : fffffa80`0885d010  00000000`000000e9 fffffa80`04356b10 fffffa80`00000000 :  nt!KiPageFault+0x260
fffff880`033225d0 fffff880`02e5b6c8 : 00000000`00000000  00000000`00000004 fffffa80`07c101b0 fffffa80`0885d010 :  nwifi!Pt6RepackRecvNBL+0x2fa
fffff880`033226d0 fffff880`018489e9 : fffffa80`083171a0  00000000`00000000 00000000`00000001 fffffa80`07c101b0 :  nwifi!Pt6Receive+0x170
fffff880`03322730 fffff880`01848980 : fffffa80`0837f328  fffff880`01c300c7 fffff880`01c31340 fffff880`055b1cab :  ndis!ndisFilterIndicateReceiveNetBufferLists+0x29
fffff880`03322770 fffff880`01c2c9c0 : fffff880`01c33110  00000000`00000000 00000000`00000001 fffffa80`0837fd78 :  ndis!NdisFIndicateReceiveNetBufferLists+0x50
fffff880`033227b0 fffff880`018602b7 : fffffa80`07d351a0  fffffa80`0823d650 fffffa80`0823d650 00000000`00000001 :  vwififlt!FilterReceiveNetBufferLists+0x158
fffff880`03322810 fffff880`0427118f : fffffa80`0822f8c0  00000000`00000000 fffffa80`0841802e 00000000`00000000 : ndis! ??  ::FNODOBFM::`string'+0xccef
fffff880`03322860 fffffa80`0822f8c0 : 00000000`00000000 fffffa80`0841802e 00000000`00000000 fffffa80`00000002 : netr7364+0x518f
fffff880`03322868 00000000`00000000 : fffffa80`0841802e  00000000`00000000 fffffa80`00000002 fffffa80`08202878 :  0xfffffa80`0822f8c0


STACK_COMMAND:  kb

FOLLOWUP_IP: 
nwifi!Pt6RepackRecvNBL+2fa
fffff880`02e5a95e 68488b97c0      push    0FFFFFFFFC0978B48h

SYMBOL_STACK_INDEX:  3

SYMBOL_NAME:  nwifi!Pt6RepackRecvNBL+2fa

FOLLOWUP_NAME:  MachineOwner

IMAGE_NAME:  hardware

DEBUG_FLR_IMAGE_TIMESTAMP:  0

MODULE_NAME: hardware

FAILURE_BUCKET_ID:  X64_IP_MISALIGNED_nwifi.sys

BUCKET_ID:  X64_IP_MISALIGNED_nwifi.sys

Followup: MachineOwner
---------

2)

Microsoft (R) Windows Debugger Version 6.12.0002.633 AMD64
Copyright (c) Microsoft Corporation. All rights reserved.


Loading Dump File [C:WindowsMinidump120910-19468-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available

Symbol search path is: SRV*c:Windowssymbols*http://msdl.microsoft.com/download/symbols
Executable search path is: 
Windows 7 Kernel Version 7600 MP (4 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 7600.16617.amd64fre.win7_gdr.100618-1621
Machine Name:
Kernel base = 0xfffff800`03201000 PsLoadedModuleList = 0xfffff800`0343ee50
Debug session time: Thu Dec  9 16:15:21.449 2010 (UTC + 1:00)
System Uptime: 0 days 2:06:56.713
Loading Kernel Symbols
...............................................................
................................................................
............................................
Loading User Symbols
Loading unloaded module list
.........
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 124, {0, fffffa8005ee1028, be000000, 800400}

Probably caused by : hardware

Followup: MachineOwner
---------

0: kd> !analyze -v
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

WHEA_UNCORRECTABLE_ERROR (124)
A fatal hardware error has occurred. Parameter 1 identifies the type of error
source that reported the error. Parameter 2 holds the address of the
WHEA_ERROR_RECORD structure that describes the error conditon.
Arguments:
Arg1: 0000000000000000, Machine Check Exception
Arg2: fffffa8005ee1028, Address of the WHEA_ERROR_RECORD structure.
Arg3: 00000000be000000, High order 32-bits of the MCi_STATUS value.
Arg4: 0000000000800400, Low order 32-bits of the MCi_STATUS value.

Debugging Details:
------------------


BUGCHECK_STR:  0x124_GenuineIntel

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

PROCESS_NAME:  LP2DX9.exe

CURRENT_IRQL:  f

STACK_TEXT:  
fffff800`04b92a98 fffff800`037ef903 : 00000000`00000124 00000000`00000000 fffffa80`05ee1028 00000000`be000000 : nt!KeBugCheckEx
fffff800`04b92aa0 fffff800`03387593 : 00000000`00000001  fffffa80`058fbcb0 00000000`00000000 fffffa80`058fbd00 :  hal!HalBugCheckSystem+0x1e3
fffff800`04b92ae0 fffff800`037ef5c8 : 00000000`00000728  fffffa80`058fbcb0 fffff800`04b92e70 fffff800`04b92e00 :  nt!WheaReportHwError+0x263
fffff800`04b92b40 fffff800`037eef1a : fffffa80`058fbcb0  fffff800`04b92e70 fffffa80`058fbcb0 00000000`00000000 :  hal!HalpMcaReportError+0x4c
fffff800`04b92c90 fffff800`037eedd5 : 00000000`00000004  00000000`00000001 fffff800`04b92ef0 00000000`00000000 :  hal!HalpMceHandler+0x9e
fffff800`04b92cd0 fffff800`037e2e88 : 00000000`058cdcdc  00000000`ffffffff 00000000`00000000 00000000`00000000 :  hal!HalpMceHandlerWithRendezvous+0x55
fffff800`04b92d00 fffff800`0326ffec : 00000000`00000000  00000000`00000000 00000000`00000000 00000000`00000000 :  hal!HalHandleMcheck+0x40
fffff800`04b92d30 fffff800`0326fe53 : 00000000`00000000  00000000`00000000 00000000`00000000 00000000`00000000 :  nt!KxMcheckAbort+0x6c
fffff800`04b92e70 00000000`004481e5 : 00000000`00000000  00000000`00000000 00000000`00000000 00000000`00000000 :  nt!KiMcheckAbort+0x153
00000000`0018bcbc 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x4481e5


STACK_COMMAND:  kb

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: hardware

IMAGE_NAME:  hardware

DEBUG_FLR_IMAGE_TIMESTAMP:  0

FAILURE_BUCKET_ID:  X64_0x124_GenuineIntel_PROCESSOR_MAE

BUCKET_ID:  X64_0x124_GenuineIntel_PROCESSOR_MAE

Followup: MachineOwner
---------

tom1

A questo punto riporterei tutto a default per un po per riassestare il sistema

pasta

Aggiorno un po la situazione: sembra che ho risolto tutto perfettamente (lo sto testando da una decina di giorni) e neanche un problema, di nessun genere, sono spariti anche i problemi audio che discvutevo QUI .

Il tutto abbassando il BCLK da 200 a 190 (e quindi la cpu da 4.2 a 4GHz). Non ne ho idea del perchè, l'oc era testato per bene, e credo che questo significhi che processore ram e chipset erano stabilissimi, ma visti che i problemi nascevano escusivamente un game, in questo caso il sistema veniva sotto posto ad uno stress diverso, piu pesante entrando in gioco la vga e quindi sono arrivato ad una ipotetica analisi:

1. la scheda madre non regge o i 200 di bclk (o comunque un oc abbastanza spinto a 4.2ghz di cpu)

2. oppure il mio Corsair HX520W era troppo al limite quando veniva chiamata anche la vga in gioco

...cosa ne pensate, puo essere una di queste 2 la causa o sono fuori strada?

tom1

Mha il corsair ha di picco 600 watt non credo che eri al limite