<![CDATA[3 BSOD in Game...]]>in tre sessioni lunghe di gioco (40-50 min.) ho avuto tre BSOD. Ram testate e OC testato con un ora e mezza di prime blend.

I BSOD

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


Loading Dump File [C:WindowsMinidump120911-17238-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 7601 (Service Pack 1) MP (4 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 7601.17640.amd64fre.win7sp1_gdr.110622-1506
Machine Name:
Kernel base = 0xfffff800`03a62000 PsLoadedModuleList = 0xfffff800`03ca7670
Debug session time: Fri Dec  9 01:02:41.288 2011 (UTC + 1:00)
System Uptime: 0 days 1:34:53.132
Loading Kernel Symbols
...............................................................
................................................................
.........................................................
Loading User Symbols
Loading unloaded module list
.....
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck A, {a1e06, d, 1, fffff80003ae9468}

Unable to load image SystemRootsystem32DRIVERSintelppm.sys, Win32 error 0n2
*** WARNING: Unable to verify timestamp for intelppm.sys
*** ERROR: Module load completed but symbols could not be loaded for intelppm.sys
Probably caused by : ntkrnlmp.exe ( nt!KiPageFault+260 )

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

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

IRQL_NOT_LESS_OR_EQUAL (a)
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 a kernel debugger is available get the stack backtrace.
Arguments:
Arg1: 00000000000a1e06, memory referenced
Arg2: 000000000000000d, IRQL
Arg3: 0000000000000001, bitfield :
bit 0 : value 0 = read operation, 1 = write operation
bit 3 : value 0 = not an execute operation, 1 = execute operation (only on chips which support this level of status)
Arg4: fffff80003ae9468, address which referenced memory

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


WRITE_ADDRESS: GetPointerFromAddress: unable to read from fffff80003d11100
00000000000a1e06 

CURRENT_IRQL:  d

FAULTING_IP: 
nt!KeUpdateSystemTime+348
fffff800`03ae9468 483b8c3a18240000 cmp     rcx,qword ptr [rdx+rdi+2418h]

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

BUGCHECK_STR:  0xA

PROCESS_NAME:  System

TRAP_FRAME:  fffff80005690840 -- (.trap 0xfffff80005690840)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=0000000000000000 rbx=0000000000000000 rcx=000000000000918e
rdx=00000000000011a0 rsi=0000000000000000 rdi=0000000000000000
rip=fffff80003ae9468 rsp=fffff800056909d0 rbp=fffff78000000320
r8=000000000005918d  r9=000000000005918e r10=0000000000000000
r11=fffff80005690a20 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0         nv up ei ng nz na pe cy
nt!KeUpdateSystemTime+0x348:
fffff800`03ae9468 483b8c3a18240000 cmp     rcx,qword ptr [rdx+rdi+2418h] ds:00000000`000035b8=????????????????
Resetting default scope

LAST_CONTROL_TRANSFER:  from fffff80003ade1e9 to fffff80003adec40

STACK_TEXT:  
fffff800`056906f8 fffff800`03ade1e9 : 00000000`0000000a 00000000`000a1e06 00000000`0000000d 00000000`00000001 : nt!KeBugCheckEx
fffff800`05690700 fffff800`03adce60 : 00000000`00000000 00000000`0000000f 00000000`00000000 00000000`0005918f : nt!KiBugCheckDispatch+0x69
fffff800`05690840 fffff800`03ae9468 : 00000000`00000000 fffff800`03c54e80 00000000`00000001 fffff800`03c54e80 : nt!KiPageFault+0x260
fffff800`056909d0 fffff800`03a23895 : fffff800`03a49460 fffff800`05690b80 fffff800`03a49460 fffffa80`00000000 : nt!KeUpdateSystemTime+0x348
fffff800`05690ad0 fffff800`03adb173 : 00000000`00000000 fffff800`05690b80 00000000`00000001 fffffa80`0792df10 : hal!HalpHpetClockInterrupt+0x8d
fffff800`05690b00 fffff880`04d309c2 : fffff800`03ae84a9 00000000`0038c5ce fffffa80`0792f938 fffff800`03c62cc0 : nt!KiInterruptDispatchNoLock+0x163
fffff800`05690c98 fffff800`03ae84a9 : 00000000`0038c5ce fffffa80`0792f938 fffff800`03c62cc0 00000000`00000001 : intelppm+0x39c2
fffff800`05690ca0 fffff800`03ad693c : fffff800`03c54e80 fffff800`00000000 00000000`00000000 fffff880`060b352c : nt!PoIdle+0x52a
fffff800`05690d80 00000000`00000000 : fffff800`05691000 fffff800`0568b000 fffff800`05690d40 00000000`00000000 : nt!KiIdleLoop+0x2c


STACK_COMMAND:  kb

FOLLOWUP_IP: 
nt!KiPageFault+260
fffff800`03adce60 440f20c0        mov     rax,cr8

SYMBOL_STACK_INDEX:  2

SYMBOL_NAME:  nt!KiPageFault+260

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: nt

IMAGE_NAME:  ntkrnlmp.exe

DEBUG_FLR_IMAGE_TIMESTAMP:  4e02aaa3

FAILURE_BUCKET_ID:  X64_0xA_nt!KiPageFault+260

BUCKET_ID:  X64_0xA_nt!KiPageFault+260

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

20111210161653_Immagine.jpg

II BSOD

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


Loading Dump File [C:WindowsMinidump121011-19016-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 7601 (Service Pack 1) MP (4 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 7601.17640.amd64fre.win7sp1_gdr.110622-1506
Machine Name:
Kernel base = 0xfffff800`03a5b000 PsLoadedModuleList = 0xfffff800`03ca0670
Debug session time: Sat Dec 10 00:59:42.703 2011 (UTC + 1:00)
System Uptime: 0 days 0:41:47.546
Loading Kernel Symbols
...............................................................
................................................................
........................................................
Loading User Symbols
Loading unloaded module list
.....
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck A, {4, 2, 0, fffff80003ae35dc}

Probably caused by : ntkrnlmp.exe ( nt!KiProcessTimerDpcTable+4c )

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

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

IRQL_NOT_LESS_OR_EQUAL (a)
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 a kernel debugger is available get the stack backtrace.
Arguments:
Arg1: 0000000000000004, memory referenced
Arg2: 0000000000000002, IRQL
Arg3: 0000000000000000, bitfield :
bit 0 : value 0 = read operation, 1 = write operation
bit 3 : value 0 = not an execute operation, 1 = execute operation (only on chips which support this level of status)
Arg4: fffff80003ae35dc, address which referenced memory

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


READ_ADDRESS: GetPointerFromAddress: unable to read from fffff80003d0a100
0000000000000004 

CURRENT_IRQL:  2

FAULTING_IP: 
nt!KiProcessTimerDpcTable+4c
fffff800`03ae35dc 458b4d04        mov     r9d,dword ptr [r13+4]

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

BUGCHECK_STR:  0xA

PROCESS_NAME:  System

TRAP_FRAME:  fffff8800371b360 -- (.trap 0xfffff8800371b360)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=0000000000000000 rbx=0000000000000000 rcx=fffff880009f2180
rdx=0000000000000000 rsi=0000000000000000 rdi=0000000000000000
rip=fffff80003ae35dc rsp=fffff8800371b4f0 rbp=0000000000000000
r8=fffff8800371b580  r9=00000000009f2180 r10=fffff80003a5b000
r11=fffff8800371b530 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0         nv up ei pl zr na po nc
nt!KiProcessTimerDpcTable+0x4c:
fffff800`03ae35dc 458b4d04        mov     r9d,dword ptr [r13+4] ds:b520:00000000`00000004=????????
Resetting default scope

LAST_CONTROL_TRANSFER:  from fffff80003ad71e9 to fffff80003ad7c40

STACK_TEXT:  
fffff880`0371b218 fffff800`03ad71e9 : 00000000`0000000a 00000000`00000004 00000000`00000002 00000000`00000000 : nt!KeBugCheckEx
fffff880`0371b220 fffff800`03ad5e60 : 00000000`00000000 fffffa80`0c2c8120 fffffa80`0a5c2b40 fffff880`0371b580 : nt!KiBugCheckDispatch+0x69
fffff880`0371b360 fffff800`03ae35dc : fffffa80`0a5c2b40 fffffa80`0419b2f8 00000003`0419b200 00000000`0000000d : nt!KiPageFault+0x260
fffff880`0371b4f0 fffff800`03ae3496 : fffffa80`0c2c8168 fffffa80`0c2c8168 00000000`00000000 00000000`00000000 : nt!KiProcessTimerDpcTable+0x4c
fffff880`0371b560 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiProcessExpiredTimerList+0xc6


STACK_COMMAND:  kb

FOLLOWUP_IP: 
nt!KiProcessTimerDpcTable+4c
fffff800`03ae35dc 458b4d04        mov     r9d,dword ptr [r13+4]

SYMBOL_STACK_INDEX:  3

SYMBOL_NAME:  nt!KiProcessTimerDpcTable+4c

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: nt

IMAGE_NAME:  ntkrnlmp.exe

DEBUG_FLR_IMAGE_TIMESTAMP:  4e02aaa3

FAILURE_BUCKET_ID:  X64_0xA_nt!KiProcessTimerDpcTable+4c

BUCKET_ID:  X64_0xA_nt!KiProcessTimerDpcTable+4c

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

20111210161804_Immagine2.jpg

III BSOD

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


Loading Dump File [C:WindowsMinidump121011-17487-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 7601 (Service Pack 1) MP (4 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 7601.17640.amd64fre.win7sp1_gdr.110622-1506
Machine Name:
Kernel base = 0xfffff800`03a04000 PsLoadedModuleList = 0xfffff800`03c49670
Debug session time: Sat Dec 10 16:02:25.752 2011 (UTC + 1:00)
System Uptime: 0 days 4:10:45.596
Loading Kernel Symbols
...............................................................
................................................................
...........................................................
Loading User Symbols
Loading unloaded module list
.........
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck A, {24, 2, 0, fffff80003a896cb}

Probably caused by : ntkrnlmp.exe ( nt!KiTimerWaitTest+22b )

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

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

IRQL_NOT_LESS_OR_EQUAL (a)
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 a kernel debugger is available get the stack backtrace.
Arguments:
Arg1: 0000000000000024, memory referenced
Arg2: 0000000000000002, IRQL
Arg3: 0000000000000000, bitfield :
bit 0 : value 0 = read operation, 1 = write operation
bit 3 : value 0 = not an execute operation, 1 = execute operation (only on chips which support this level of status)
Arg4: fffff80003a896cb, address which referenced memory

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


READ_ADDRESS: GetPointerFromAddress: unable to read from fffff80003cb3100
0000000000000024 

CURRENT_IRQL:  2

FAULTING_IP: 
nt!KiTimerWaitTest+22b
fffff800`03a896cb 418b4624        mov     eax,dword ptr [r14+24h]

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

BUGCHECK_STR:  0xA

PROCESS_NAME:  System

TRAP_FRAME:  fffff8800371b350 -- (.trap 0xfffff8800371b350)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=fffffa8007777aa0 rbx=0000000000000000 rcx=fffffa800ad94100
rdx=0000000000000102 rsi=0000000000000000 rdi=0000000000000000
rip=fffff80003a896cb rsp=fffff8800371b4e8 rbp=fffffa800985d9a8
r8=fffff880009f4301  r9=0000000000000002 r10=0000000000000067
r11=0000000000000000 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0         nv up ei pl zr na po nc
nt!KiTimerWaitTest+0x22b:
fffff800`03a896cb 418b4624        mov     eax,dword ptr [r14+24h] ds:5000:00000000`00000024=????????
Resetting default scope

LAST_CONTROL_TRANSFER:  from fffff80003a801e9 to fffff80003a80c40

STACK_TEXT:  
fffff880`0371b208 fffff800`03a801e9 : 00000000`0000000a 00000000`00000024 00000000`00000002 00000000`00000000 : nt!KeBugCheckEx
fffff880`0371b210 fffff800`03a7ee60 : 00000000`0038c5c4 fffffa80`09faf000 00000000`00000000 fffffa80`0985d9a8 : nt!KiBugCheckDispatch+0x69
fffff880`0371b350 fffff800`03a896cb : 00000000`0000000f fffffa80`08eb4010 fffffa80`0ae95948 fffffa80`0ae95948 : nt!KiPageFault+0x260
fffff880`0371b4e8 fffffa80`0ae95948 : fffffa80`0985d9a0 00000000`00000000 fffffa80`08eb4218 00000000`00000102 : nt!KiTimerWaitTest+0x22b
fffff880`0371b568 fffffa80`0985d9a0 : 00000000`00000000 fffffa80`08eb4218 00000000`00000102 fffffa80`09f917a8 : 0xfffffa80`0ae95948
fffff880`0371b570 00000000`00000000 : fffffa80`08eb4218 00000000`00000102 fffffa80`09f917a8 00000000`00000002 : 0xfffffa80`0985d9a0


STACK_COMMAND:  kb

FOLLOWUP_IP: 
nt!KiTimerWaitTest+22b
fffff800`03a896cb 418b4624        mov     eax,dword ptr [r14+24h]

SYMBOL_STACK_INDEX:  3

SYMBOL_NAME:  nt!KiTimerWaitTest+22b

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: nt

IMAGE_NAME:  ntkrnlmp.exe

DEBUG_FLR_IMAGE_TIMESTAMP:  4e02aaa3

FAILURE_BUCKET_ID:  X64_0xA_nt!KiTimerWaitTest+22b

BUCKET_ID:  X64_0xA_nt!KiTimerWaitTest+22b

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

20111210161915_Immagine3.jpg

Sapreste dirmi cosa ha causato questi crash in ogniuna di quesrte 3 situazioni?

 

Inoltre sapreste dirmi poi come agire per eliminare il problema?

]]>https://www.xtremehardware.com/forum//topic/23626/3-bsod-in-gameRSS for NodeSun, 26 Apr 2026 08:36:02 GMTSat, 10 Dec 2011 15:20:17 GMT60<![CDATA[Reply to 3 BSOD in Game... on Sat, 24 Dec 2011 14:38:48 GMT]]>mmm ti direi azzera l'oc e ripristina tutto a default

]]>https://www.xtremehardware.com/forum//post/342215https://www.xtremehardware.com/forum//post/342215Sat, 24 Dec 2011 14:38:48 GMT<![CDATA[Reply to 3 BSOD in Game... on Sat, 24 Dec 2011 14:02:33 GMT]]>

tom1 ha scritto:

no la recovery dal dvd di installazione

tra gli strumenti del dvd non c'è nulla per correggere i file se non quello della correzione all'avvio che non'è andata a buon fine (anche se non ci sono problemi di avvio e mi chiedo poi se questo stumento ripristini/corregga anche files come quello che interessa a me)

]]>https://www.xtremehardware.com/forum//post/342214https://www.xtremehardware.com/forum//post/342214Sat, 24 Dec 2011 14:02:33 GMT<![CDATA[Reply to 3 BSOD in Game... on Sun, 18 Dec 2011 19:33:22 GMT]]>no la recovery dal dvd di installazione

]]>https://www.xtremehardware.com/forum//post/342213https://www.xtremehardware.com/forum//post/342213Sun, 18 Dec 2011 19:33:22 GMT<![CDATA[Reply to 3 BSOD in Game... on Sun, 18 Dec 2011 19:30:41 GMT]]>

tom1 ha scritto:

allora vai di rispristino sistema

intendi ripristinare un punto precedente del sistema operativo o lanciare qualche sorta di utility col dvd di windows?

]]>https://www.xtremehardware.com/forum//post/342212https://www.xtremehardware.com/forum//post/342212Sun, 18 Dec 2011 19:30:41 GMT<![CDATA[Reply to 3 BSOD in Game... on Sun, 18 Dec 2011 18:23:04 GMT]]>allora vai di rispristino sistema

]]>https://www.xtremehardware.com/forum//post/342211https://www.xtremehardware.com/forum//post/342211Sun, 18 Dec 2011 18:23:04 GMT<![CDATA[Reply to 3 BSOD in Game... on Sun, 18 Dec 2011 11:38:45 GMT]]>devo trovare quel file, nel dvd non c'è (a meno che si debba estrarre da qualche altro file, non so)

]]>https://www.xtremehardware.com/forum//post/342210https://www.xtremehardware.com/forum//post/342210Sun, 18 Dec 2011 11:38:45 GMT<![CDATA[Reply to 3 BSOD in Game... on Sun, 18 Dec 2011 09:35:49 GMT]]>novità

]]>https://www.xtremehardware.com/forum//post/342209https://www.xtremehardware.com/forum//post/342209Sun, 18 Dec 2011 09:35:49 GMT<![CDATA[Reply to 3 BSOD in Game... on Sat, 17 Dec 2011 20:30:43 GMT]]>

pasta ha scritto:

bene inizio con questo allora e vediamo se si ripresenta...il file da sostituire è ntoskrnl.exe?

edit: se il file è quello non c'è nel dvd

l'ho testato con un ora e mezza di prime blend (oltre ad aver testato singolarmente le ram col test da dos)

....c'è un modo piu affidabile per testare l'oc e sapere se il problema è quello?

si, un gioco pesante

]]>https://www.xtremehardware.com/forum//post/342208https://www.xtremehardware.com/forum//post/342208Sat, 17 Dec 2011 20:30:43 GMT<![CDATA[Reply to 3 BSOD in Game... on Sat, 17 Dec 2011 20:03:46 GMT]]>no ha testato nel modo corretto

]]>https://www.xtremehardware.com/forum//post/342207https://www.xtremehardware.com/forum//post/342207Sat, 17 Dec 2011 20:03:46 GMT<![CDATA[Reply to 3 BSOD in Game... on Sat, 17 Dec 2011 18:51:49 GMT]]>

tom1 ha scritto:

inserisci il dvd e cerchi il file

bene inizio con questo allora e vediamo se si ripresenta...il file da sostituire è ntoskrnl.exe?

edit: se il file è quello non c'è nel dvd

Gi@n ha scritto:

sistema instabile per overclock

l'ho testato con un ora e mezza di prime blend (oltre ad aver testato singolarmente le ram col test da dos)

....c'è un modo piu affidabile per testare l'oc e sapere se il problema è quello?

]]>https://www.xtremehardware.com/forum//post/342206https://www.xtremehardware.com/forum//post/342206Sat, 17 Dec 2011 18:51:49 GMT<![CDATA[Reply to 3 BSOD in Game... on Sat, 17 Dec 2011 12:21:50 GMT]]>sistema instabile per overclock

]]>https://www.xtremehardware.com/forum//post/342205https://www.xtremehardware.com/forum//post/342205Sat, 17 Dec 2011 12:21:50 GMT<![CDATA[Reply to 3 BSOD in Game... on Sat, 17 Dec 2011 10:43:04 GMT]]>inserisci il dvd e cerchi il file

]]>https://www.xtremehardware.com/forum//post/342204https://www.xtremehardware.com/forum//post/342204Sat, 17 Dec 2011 10:43:04 GMT<![CDATA[Reply to 3 BSOD in Game... on Fri, 16 Dec 2011 23:58:42 GMT]]>

tom1 ha scritto:

formattare o sostuirlo dal dvd di installazione

come posso attuare la seconda via ? :cheazz:

]]>https://www.xtremehardware.com/forum//post/342203https://www.xtremehardware.com/forum//post/342203Fri, 16 Dec 2011 23:58:42 GMT<![CDATA[Reply to 3 BSOD in Game... on Fri, 16 Dec 2011 14:29:09 GMT]]>formattare o sostuirlo dal dvd di installazione

]]>https://www.xtremehardware.com/forum//post/342202https://www.xtremehardware.com/forum//post/342202Fri, 16 Dec 2011 14:29:09 GMT<![CDATA[Reply to 3 BSOD in Game... on Fri, 16 Dec 2011 14:19:51 GMT]]>

tom1 ha scritto:

no ora è dovuto ad una corruzione di un file kernel di windows

possibili azioni?

]]>https://www.xtremehardware.com/forum//post/342201https://www.xtremehardware.com/forum//post/342201Fri, 16 Dec 2011 14:19:51 GMT<![CDATA[Reply to 3 BSOD in Game... on Fri, 16 Dec 2011 11:58:40 GMT]]>no ora è dovuto ad una corruzione di un file kernel di windows

]]>https://www.xtremehardware.com/forum//post/342200https://www.xtremehardware.com/forum//post/342200Fri, 16 Dec 2011 11:58:40 GMT<![CDATA[Reply to 3 BSOD in Game... on Fri, 16 Dec 2011 11:47:17 GMT]]> Microsoft (R) Windows Debugger Version 6.12.0002.633 AMD64 Copyright (c) Microsoft Corporation. All rights reserved. Loading Dump File [C:WindowsMinidump121611-16816-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 7601 (Service Pack 1) MP (4 procs) Free x64 Product: WinNt, suite: TerminalServer SingleUserTS Built by: 7601.17640.amd64fre.win7sp1_gdr.110622-1506 Machine Name: Kernel base = 0xfffff800`03a56000 PsLoadedModuleList = 0xfffff800`03c9b670 Debug session time: Fri Dec 16 02:37:25.686 2011 (UTC + 1:00) System Uptime: 0 days 1:43:47.904 Loading Kernel Symbols ............................................................... ................................................................ .......................................................... Loading User Symbols Loading unloaded module list .... ******************************************************************************* * * * Bugcheck Analysis * * * ******************************************************************************* Use !analyze -v to get detailed debugging information. BugCheck 1E, {0, 0, 0, 0} Probably caused by : ntkrnlmp.exe ( nt!KiKernelCalloutExceptionHandler+e ) Followup: MachineOwner --------- 0: kd> !analyze -v ******************************************************************************* * * * Bugcheck Analysis * * * ******************************************************************************* KMODE_EXCEPTION_NOT_HANDLED (1e) This is a very common bugcheck. Usually the exception address pinpoints the driver/function that caused the problem. Always note this address as well as the link date of the driver/image that contains this address. Arguments: Arg1: 0000000000000000, The exception code that was not handled Arg2: 0000000000000000, The address that the exception occurred at Arg3: 0000000000000000, Parameter 0 of the exception Arg4: 0000000000000000, Parameter 1 of the exception Debugging Details: ------------------ EXCEPTION_CODE: (Win32) 0 (0) - Operazione completata. FAULTING_IP: +6238643366333963 00000000`00000000 ?? ??? EXCEPTION_PARAMETER1: 0000000000000000 EXCEPTION_PARAMETER2: 0000000000000000 ERROR_CODE: (NTSTATUS) 0 - STATUS_WAIT_0 BUGCHECK_STR: 0x1E_0 CUSTOMER_CRASH_COUNT: 1 DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT PROCESS_NAME: System CURRENT_IRQL: 2 EXCEPTION_RECORD: fffff80005685328 -- (.exr 0xfffff80005685328) ExceptionAddress: fffffa8007698efe ExceptionCode: c000001d (Illegal instruction) ExceptionFlags: 00000000 NumberParameters: 0 TRAP_FRAME: fffff800056853d0 -- (.trap 0xfffff800056853d0) NOTE: The trap frame does not contain all registers. Some register values may be zeroed or incorrect. rax=fffffa8009ec4c80 rbx=0000000000000000 rcx=0000000000000000 rdx=fffffa8009ec4cc0 rsi=0000000000000000 rdi=0000000000000000 rip=fffffa8007698efe rsp=fffff80005685568 rbp=0000000000000001 r8=fffff80003c4b001 r9=0000000000000002 r10=0000000000000076 r11=0000000000000000 r12=0000000000000000 r13=0000000000000000 r14=0000000000000000 r15=0000000000000000 iopl=0 nv up di ng nz na po nc fffffa80`07698efe ?? ??? Resetting default scope LAST_CONTROL_TRANSFER: from fffff80003aca5fe to fffff80003ad2c10 STACK_TEXT: fffff800`05684408 fffff800`03aca5fe : fffff800`05685600 fffff800`05686000 fffff800`05684b80 fffff800`03afe830 : nt!KeBugCheck fffff800`05684410 fffff800`03afe4fd : fffff800`03cdc71c fffff800`03c19c30 fffff800`03a56000 fffff800`05685328 : nt!KiKernelCalloutExceptionHandler+0xe fffff800`05684440 fffff800`03afd2d5 : fffff800`03c1d0fc fffff800`056844b8 fffff800`05685328 fffff800`03a56000 : nt!RtlpExecuteHandlerForException+0xd fffff800`05684470 fffff800`03b0e361 : fffff800`05685328 fffff800`05684b80 fffff800`00000000 fffffa80`09ec4cc0 : nt!RtlDispatchException+0x415 fffff800`05684b50 fffff800`03ad22c2 : fffff800`05685328 fffffa80`09ec4cc0 fffff800`056853d0 fffffa80`09ec4c80 : nt!KiDispatchException+0x135 fffff800`056851f0 fffff800`03ad041f : fffff800`056853d0 00000000`00000002 fffffa80`099da300 fffffa80`00000000 : nt!KiExceptionDispatch+0xc2 fffff800`056853d0 fffffa80`07698efe : fffffa80`09ec4cc0 00000000`00000000 fffffa80`07698ef0 00000000`40760000 : nt!KiInvalidOpcodeFault+0x11f fffff800`05685568 fffffa80`09ec4cc0 : 00000000`00000000 fffffa80`07698ef0 00000000`40760000 00000000`00000009 : 0xfffffa80`07698efe fffff800`05685570 00000000`00000000 : fffffa80`07698ef0 00000000`40760000 00000000`00000009 00000000`00000000 : 0xfffffa80`09ec4cc0 STACK_COMMAND: kb FOLLOWUP_IP: nt!KiKernelCalloutExceptionHandler+e fffff800`03aca5fe 90 nop SYMBOL_STACK_INDEX: 1 SYMBOL_NAME: nt!KiKernelCalloutExceptionHandler+e FOLLOWUP_NAME: MachineOwner MODULE_NAME: nt IMAGE_NAME: ntkrnlmp.exe DEBUG_FLR_IMAGE_TIMESTAMP: 4e02aaa3 FAILURE_BUCKET_ID: X64_0x1E_0_nt!KiKernelCalloutExceptionHandler+e BUCKET_ID: X64_0x1E_0_nt!KiKernelCalloutExceptionHandler+e Followup: MachineOwner ---------

th_20111216124504_Immagine.jpg

Quindi anche i nuovi drivers non hanno risolto.....si tratta sempre della stessa causa?....come dovrei procedere ora?

]]>https://www.xtremehardware.com/forum//post/342199https://www.xtremehardware.com/forum//post/342199Fri, 16 Dec 2011 11:47:17 GMT<![CDATA[Reply to 3 BSOD in Game... on Sun, 11 Dec 2011 10:47:54 GMT]]>perfetto

]]>https://www.xtremehardware.com/forum//post/342198https://www.xtremehardware.com/forum//post/342198Sun, 11 Dec 2011 10:47:54 GMT<![CDATA[Reply to 3 BSOD in Game... on Sun, 11 Dec 2011 10:43:54 GMT]]>no, con 2 giochi diversi e bios aggiornato...quindi inizio dai drivers video e vediamo...grazie, se si ripresentano aggiorno il thread

]]>https://www.xtremehardware.com/forum//post/342197https://www.xtremehardware.com/forum//post/342197Sun, 11 Dec 2011 10:43:54 GMT<![CDATA[Reply to 3 BSOD in Game... on Sat, 10 Dec 2011 15:44:33 GMT]]>Li hai avuti con lo stesso gioco recentemente installato?

Aggiorna i driver ed il BIOS.

ciao

]]>https://www.xtremehardware.com/forum//post/342196https://www.xtremehardware.com/forum//post/342196Sat, 10 Dec 2011 15:44:33 GMT<![CDATA[Reply to 3 BSOD in Game... on Sat, 10 Dec 2011 15:43:45 GMT]]>sono tutti bsod dovuti a corruzione di driver uno directx, uno del pannello di controllo nei servizi ed uno del pannello di ati

]]>https://www.xtremehardware.com/forum//post/342195https://www.xtremehardware.com/forum//post/342195Sat, 10 Dec 2011 15:43:45 GMT<![CDATA[Reply to 3 BSOD in Game... on Sat, 10 Dec 2011 15:20:17 GMT]]>in tre sessioni lunghe di gioco (40-50 min.) ho avuto tre BSOD. Ram testate e OC testato con un ora e mezza di prime blend.

I BSOD

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


Loading Dump File [C:WindowsMinidump120911-17238-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 7601 (Service Pack 1) MP (4 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 7601.17640.amd64fre.win7sp1_gdr.110622-1506
Machine Name:
Kernel base = 0xfffff800`03a62000 PsLoadedModuleList = 0xfffff800`03ca7670
Debug session time: Fri Dec  9 01:02:41.288 2011 (UTC + 1:00)
System Uptime: 0 days 1:34:53.132
Loading Kernel Symbols
...............................................................
................................................................
.........................................................
Loading User Symbols
Loading unloaded module list
.....
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck A, {a1e06, d, 1, fffff80003ae9468}

Unable to load image SystemRootsystem32DRIVERSintelppm.sys, Win32 error 0n2
*** WARNING: Unable to verify timestamp for intelppm.sys
*** ERROR: Module load completed but symbols could not be loaded for intelppm.sys
Probably caused by : ntkrnlmp.exe ( nt!KiPageFault+260 )

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

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

IRQL_NOT_LESS_OR_EQUAL (a)
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 a kernel debugger is available get the stack backtrace.
Arguments:
Arg1: 00000000000a1e06, memory referenced
Arg2: 000000000000000d, IRQL
Arg3: 0000000000000001, bitfield :
bit 0 : value 0 = read operation, 1 = write operation
bit 3 : value 0 = not an execute operation, 1 = execute operation (only on chips which support this level of status)
Arg4: fffff80003ae9468, address which referenced memory

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


WRITE_ADDRESS: GetPointerFromAddress: unable to read from fffff80003d11100
00000000000a1e06 

CURRENT_IRQL:  d

FAULTING_IP: 
nt!KeUpdateSystemTime+348
fffff800`03ae9468 483b8c3a18240000 cmp     rcx,qword ptr [rdx+rdi+2418h]

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

BUGCHECK_STR:  0xA

PROCESS_NAME:  System

TRAP_FRAME:  fffff80005690840 -- (.trap 0xfffff80005690840)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=0000000000000000 rbx=0000000000000000 rcx=000000000000918e
rdx=00000000000011a0 rsi=0000000000000000 rdi=0000000000000000
rip=fffff80003ae9468 rsp=fffff800056909d0 rbp=fffff78000000320
r8=000000000005918d  r9=000000000005918e r10=0000000000000000
r11=fffff80005690a20 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0         nv up ei ng nz na pe cy
nt!KeUpdateSystemTime+0x348:
fffff800`03ae9468 483b8c3a18240000 cmp     rcx,qword ptr [rdx+rdi+2418h] ds:00000000`000035b8=????????????????
Resetting default scope

LAST_CONTROL_TRANSFER:  from fffff80003ade1e9 to fffff80003adec40

STACK_TEXT:  
fffff800`056906f8 fffff800`03ade1e9 : 00000000`0000000a 00000000`000a1e06 00000000`0000000d 00000000`00000001 : nt!KeBugCheckEx
fffff800`05690700 fffff800`03adce60 : 00000000`00000000 00000000`0000000f 00000000`00000000 00000000`0005918f : nt!KiBugCheckDispatch+0x69
fffff800`05690840 fffff800`03ae9468 : 00000000`00000000 fffff800`03c54e80 00000000`00000001 fffff800`03c54e80 : nt!KiPageFault+0x260
fffff800`056909d0 fffff800`03a23895 : fffff800`03a49460 fffff800`05690b80 fffff800`03a49460 fffffa80`00000000 : nt!KeUpdateSystemTime+0x348
fffff800`05690ad0 fffff800`03adb173 : 00000000`00000000 fffff800`05690b80 00000000`00000001 fffffa80`0792df10 : hal!HalpHpetClockInterrupt+0x8d
fffff800`05690b00 fffff880`04d309c2 : fffff800`03ae84a9 00000000`0038c5ce fffffa80`0792f938 fffff800`03c62cc0 : nt!KiInterruptDispatchNoLock+0x163
fffff800`05690c98 fffff800`03ae84a9 : 00000000`0038c5ce fffffa80`0792f938 fffff800`03c62cc0 00000000`00000001 : intelppm+0x39c2
fffff800`05690ca0 fffff800`03ad693c : fffff800`03c54e80 fffff800`00000000 00000000`00000000 fffff880`060b352c : nt!PoIdle+0x52a
fffff800`05690d80 00000000`00000000 : fffff800`05691000 fffff800`0568b000 fffff800`05690d40 00000000`00000000 : nt!KiIdleLoop+0x2c


STACK_COMMAND:  kb

FOLLOWUP_IP: 
nt!KiPageFault+260
fffff800`03adce60 440f20c0        mov     rax,cr8

SYMBOL_STACK_INDEX:  2

SYMBOL_NAME:  nt!KiPageFault+260

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: nt

IMAGE_NAME:  ntkrnlmp.exe

DEBUG_FLR_IMAGE_TIMESTAMP:  4e02aaa3

FAILURE_BUCKET_ID:  X64_0xA_nt!KiPageFault+260

BUCKET_ID:  X64_0xA_nt!KiPageFault+260

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

20111210161653_Immagine.jpg

II BSOD

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


Loading Dump File [C:WindowsMinidump121011-19016-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 7601 (Service Pack 1) MP (4 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 7601.17640.amd64fre.win7sp1_gdr.110622-1506
Machine Name:
Kernel base = 0xfffff800`03a5b000 PsLoadedModuleList = 0xfffff800`03ca0670
Debug session time: Sat Dec 10 00:59:42.703 2011 (UTC + 1:00)
System Uptime: 0 days 0:41:47.546
Loading Kernel Symbols
...............................................................
................................................................
........................................................
Loading User Symbols
Loading unloaded module list
.....
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck A, {4, 2, 0, fffff80003ae35dc}

Probably caused by : ntkrnlmp.exe ( nt!KiProcessTimerDpcTable+4c )

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

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

IRQL_NOT_LESS_OR_EQUAL (a)
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 a kernel debugger is available get the stack backtrace.
Arguments:
Arg1: 0000000000000004, memory referenced
Arg2: 0000000000000002, IRQL
Arg3: 0000000000000000, bitfield :
bit 0 : value 0 = read operation, 1 = write operation
bit 3 : value 0 = not an execute operation, 1 = execute operation (only on chips which support this level of status)
Arg4: fffff80003ae35dc, address which referenced memory

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


READ_ADDRESS: GetPointerFromAddress: unable to read from fffff80003d0a100
0000000000000004 

CURRENT_IRQL:  2

FAULTING_IP: 
nt!KiProcessTimerDpcTable+4c
fffff800`03ae35dc 458b4d04        mov     r9d,dword ptr [r13+4]

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

BUGCHECK_STR:  0xA

PROCESS_NAME:  System

TRAP_FRAME:  fffff8800371b360 -- (.trap 0xfffff8800371b360)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=0000000000000000 rbx=0000000000000000 rcx=fffff880009f2180
rdx=0000000000000000 rsi=0000000000000000 rdi=0000000000000000
rip=fffff80003ae35dc rsp=fffff8800371b4f0 rbp=0000000000000000
r8=fffff8800371b580  r9=00000000009f2180 r10=fffff80003a5b000
r11=fffff8800371b530 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0         nv up ei pl zr na po nc
nt!KiProcessTimerDpcTable+0x4c:
fffff800`03ae35dc 458b4d04        mov     r9d,dword ptr [r13+4] ds:b520:00000000`00000004=????????
Resetting default scope

LAST_CONTROL_TRANSFER:  from fffff80003ad71e9 to fffff80003ad7c40

STACK_TEXT:  
fffff880`0371b218 fffff800`03ad71e9 : 00000000`0000000a 00000000`00000004 00000000`00000002 00000000`00000000 : nt!KeBugCheckEx
fffff880`0371b220 fffff800`03ad5e60 : 00000000`00000000 fffffa80`0c2c8120 fffffa80`0a5c2b40 fffff880`0371b580 : nt!KiBugCheckDispatch+0x69
fffff880`0371b360 fffff800`03ae35dc : fffffa80`0a5c2b40 fffffa80`0419b2f8 00000003`0419b200 00000000`0000000d : nt!KiPageFault+0x260
fffff880`0371b4f0 fffff800`03ae3496 : fffffa80`0c2c8168 fffffa80`0c2c8168 00000000`00000000 00000000`00000000 : nt!KiProcessTimerDpcTable+0x4c
fffff880`0371b560 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiProcessExpiredTimerList+0xc6


STACK_COMMAND:  kb

FOLLOWUP_IP: 
nt!KiProcessTimerDpcTable+4c
fffff800`03ae35dc 458b4d04        mov     r9d,dword ptr [r13+4]

SYMBOL_STACK_INDEX:  3

SYMBOL_NAME:  nt!KiProcessTimerDpcTable+4c

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: nt

IMAGE_NAME:  ntkrnlmp.exe

DEBUG_FLR_IMAGE_TIMESTAMP:  4e02aaa3

FAILURE_BUCKET_ID:  X64_0xA_nt!KiProcessTimerDpcTable+4c

BUCKET_ID:  X64_0xA_nt!KiProcessTimerDpcTable+4c

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

20111210161804_Immagine2.jpg

III BSOD

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


Loading Dump File [C:WindowsMinidump121011-17487-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 7601 (Service Pack 1) MP (4 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 7601.17640.amd64fre.win7sp1_gdr.110622-1506
Machine Name:
Kernel base = 0xfffff800`03a04000 PsLoadedModuleList = 0xfffff800`03c49670
Debug session time: Sat Dec 10 16:02:25.752 2011 (UTC + 1:00)
System Uptime: 0 days 4:10:45.596
Loading Kernel Symbols
...............................................................
................................................................
...........................................................
Loading User Symbols
Loading unloaded module list
.........
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck A, {24, 2, 0, fffff80003a896cb}

Probably caused by : ntkrnlmp.exe ( nt!KiTimerWaitTest+22b )

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

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

IRQL_NOT_LESS_OR_EQUAL (a)
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 a kernel debugger is available get the stack backtrace.
Arguments:
Arg1: 0000000000000024, memory referenced
Arg2: 0000000000000002, IRQL
Arg3: 0000000000000000, bitfield :
bit 0 : value 0 = read operation, 1 = write operation
bit 3 : value 0 = not an execute operation, 1 = execute operation (only on chips which support this level of status)
Arg4: fffff80003a896cb, address which referenced memory

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


READ_ADDRESS: GetPointerFromAddress: unable to read from fffff80003cb3100
0000000000000024 

CURRENT_IRQL:  2

FAULTING_IP: 
nt!KiTimerWaitTest+22b
fffff800`03a896cb 418b4624        mov     eax,dword ptr [r14+24h]

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

BUGCHECK_STR:  0xA

PROCESS_NAME:  System

TRAP_FRAME:  fffff8800371b350 -- (.trap 0xfffff8800371b350)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=fffffa8007777aa0 rbx=0000000000000000 rcx=fffffa800ad94100
rdx=0000000000000102 rsi=0000000000000000 rdi=0000000000000000
rip=fffff80003a896cb rsp=fffff8800371b4e8 rbp=fffffa800985d9a8
r8=fffff880009f4301  r9=0000000000000002 r10=0000000000000067
r11=0000000000000000 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0         nv up ei pl zr na po nc
nt!KiTimerWaitTest+0x22b:
fffff800`03a896cb 418b4624        mov     eax,dword ptr [r14+24h] ds:5000:00000000`00000024=????????
Resetting default scope

LAST_CONTROL_TRANSFER:  from fffff80003a801e9 to fffff80003a80c40

STACK_TEXT:  
fffff880`0371b208 fffff800`03a801e9 : 00000000`0000000a 00000000`00000024 00000000`00000002 00000000`00000000 : nt!KeBugCheckEx
fffff880`0371b210 fffff800`03a7ee60 : 00000000`0038c5c4 fffffa80`09faf000 00000000`00000000 fffffa80`0985d9a8 : nt!KiBugCheckDispatch+0x69
fffff880`0371b350 fffff800`03a896cb : 00000000`0000000f fffffa80`08eb4010 fffffa80`0ae95948 fffffa80`0ae95948 : nt!KiPageFault+0x260
fffff880`0371b4e8 fffffa80`0ae95948 : fffffa80`0985d9a0 00000000`00000000 fffffa80`08eb4218 00000000`00000102 : nt!KiTimerWaitTest+0x22b
fffff880`0371b568 fffffa80`0985d9a0 : 00000000`00000000 fffffa80`08eb4218 00000000`00000102 fffffa80`09f917a8 : 0xfffffa80`0ae95948
fffff880`0371b570 00000000`00000000 : fffffa80`08eb4218 00000000`00000102 fffffa80`09f917a8 00000000`00000002 : 0xfffffa80`0985d9a0


STACK_COMMAND:  kb

FOLLOWUP_IP: 
nt!KiTimerWaitTest+22b
fffff800`03a896cb 418b4624        mov     eax,dword ptr [r14+24h]

SYMBOL_STACK_INDEX:  3

SYMBOL_NAME:  nt!KiTimerWaitTest+22b

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: nt

IMAGE_NAME:  ntkrnlmp.exe

DEBUG_FLR_IMAGE_TIMESTAMP:  4e02aaa3

FAILURE_BUCKET_ID:  X64_0xA_nt!KiTimerWaitTest+22b

BUCKET_ID:  X64_0xA_nt!KiTimerWaitTest+22b

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

20111210161915_Immagine3.jpg

Sapreste dirmi cosa ha causato questi crash in ogniuna di quesrte 3 situazioni?

 

Inoltre sapreste dirmi poi come agire per eliminare il problema?

]]>https://www.xtremehardware.com/forum//post/342194https://www.xtremehardware.com/forum//post/342194Sat, 10 Dec 2011 15:20:17 GMT