Ich weiss nimmer weiter habe windows 7 neu instaliert habe alle treiber wirklich alle Treiber aufen neusten stand und habe immer noch wie vor der neu instalation von Windows bluesreens in gewissen abständen geh ich in Spiel COD rein kaum 10 minuten gespielt Bluesrreen geh in ein anderen spiel rein z.b Aion stunde später bluesreen bleibe ich nur aufen desktop passiert 2-3 tunden nicht dann irgendwann bluesrren. Habe mal 2 auswertungen(minidumps) gemacht verstehe den inhalt aber nicht hoffe um hilfe!!!
1:Bluesreen um 23.28 heute dnach neustart dann kam der 2!!!
Microsoft (R) Windows Debugger Version 6.11.0001.404 AMD64
Copyright (c) Microsoft Corporation. All rights reserved.
Loading Dump File [C:\Windows\Minidump\013011-22854-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available
Symbol search path is: SRV*C:\symbols*Symbol information
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`02a09000 PsLoadedModuleList = 0xfffff800`02c46e50
Debug session time: Sun Jan 30 23:27:12.303 2011 (GMT+1)
System Uptime: 0 days 0:12:05.036
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
---------
3: 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) - Der Vorgang wurde erfolgreich beendet.
FAULTING_IP:
+0
00000000`00000000 ?? ???
EXCEPTION_PARAMETER1: 0000000000000000
EXCEPTION_PARAMETER2: 0000000000000000
CUSTOMER_CRASH_COUNT: 1
DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT
BUGCHECK_STR: 0x1E
PROCESS_NAME: BlackOpsMP.exe
CURRENT_IRQL: 2
EXCEPTION_RECORD: fffff880009b05d8 -- (.exr 0xfffff880009b05d8)
ExceptionAddress: fffff80002a84e39 (nt!KiProcessExpiredTimerList+0x0000000000000129)
ExceptionCode: c0000005 (Access violation)
ExceptionFlags: 00000000
NumberParameters: 2
Parameter[0]: 0000000000000000
Parameter[1]: ffffffffffffffff
Attempt to read from address ffffffffffffffff
TRAP_FRAME: fffff880009b0680 -- (.trap 0xfffff880009b0680)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=fffffa800715a3d8 rbx=0000000000000000 rcx=f7fffa800715a3d8
rdx=0000000000000102 rsi=0000000000000000 rdi=0000000000000000
rip=fffff80002a84e39 rsp=fffff880009b0810 rbp=fffffa800747cc68
r8=fffff88002fd7301 r9=0000000000000002 r10=000000000000008c
r11=0000000000000000 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0 nv up ei pl zr na po nc
nt!KiProcessExpiredTimerList+0x129:
fffff800`02a84e39 48894108 mov qword ptr [rcx+8],rax ds:5400:f7fffa80`0715a3e0=????????????????
Resetting default scope
LAST_CONTROL_TRANSFER: from fffff80002a7146e to fffff80002a79710
STACK_TEXT:
fffff880`009af6c8 fffff800`02a7146e : fffffa80`096ab8a0 fffffa80`08a408c0 fffff880`009afe40 fffff800`02aa6668 : nt!KeBugCheck
fffff880`009af6d0 fffff800`02a9f40d : fffff800`02c87b7c fffff800`02bc1e84 fffff800`02a09000 fffff880`009b05d8 : nt!KiKernelCalloutExceptionHandler+0xe
fffff880`009af700 fffff800`02aa6a90 : fffff800`02bc8a40 fffff880`009af778 fffff880`009b05d8 fffff800`02a09000 : nt!RtlpExecuteHandlerForException+0xd
fffff880`009af730 fffff800`02ab39ef : fffff880`009b05d8 fffff880`009afe40 fffff880`00000000 fffffa80`0715a3d0 : nt!RtlDispatchException+0x410
fffff880`009afe10 fffff800`02a78d82 : fffff880`009b05d8 fffffa80`0747cc68 fffff880`009b0680 00000000`00000000 : nt!KiDispatchException+0x16f
fffff880`009b04a0 fffff800`02a7768a : 00000000`00800000 00000000`00000009 00000000`00000000 fffffa80`07019002 : nt!KiExceptionDispatch+0xc2
fffff880`009b0680 fffff800`02a84e39 : fffffa80`0747cc20 fffffa80`0719d168 fffffa80`0719d168 00000000`00000102 : nt!KiGeneralProtectionFault+0x10a
fffff880`009b0810 fffff800`02a854be : 00000001`b027c594 fffff880`009b0e88 00000000`0000b58c fffff880`02fd8708 : nt!KiProcessExpiredTimerList+0x129
fffff880`009b0e60 fffff800`02a84cb7 : fffffa80`08b87cc1 fffffa80`0000b58c fffffa80`08b81000 00000000`0000008c : nt!KiTimerExpiration+0x1be
fffff880`009b0f00 fffff800`02a7f865 : 000004d8`00000000 fffffa80`074155d0 00000000`00000000 fffff880`13e6d684 : nt!KiRetireDpcList+0x277
fffff880`009b0fb0 fffff800`02a7f67c : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KxRetireDpcList+0x5
fffff880`0d1c47f0 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiDispatchInterruptContinue
STACK_COMMAND: kb
FOLLOWUP_IP:
nt!KiKernelCalloutExceptionHandler+e
fffff800`02a7146e 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: 4c1c44a9
FAILURE_BUCKET_ID: X64_0x1E_nt!KiKernelCalloutExceptionHandler+e
BUCKET_ID: X64_0x1E_nt!KiKernelCalloutExceptionHandler+e
Followup: MachineOwner
---------
So jetzt der 2 Bluesreen danach:!!!!!
Microsoft (R) Windows Debugger Version 6.11.0001.404 AMD64
Copyright (c) Microsoft Corporation. All rights reserved.
Loading Dump File [C:\Windows\Minidump\013011-26473-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available
Symbol search path is: SRV*C:\symbols*Symbol information
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`02a49000 PsLoadedModuleList = 0xfffff800`02c86e50
Debug session time: Sun Jan 30 23:29:20.009 2011 (GMT+1)
System Uptime: 0 days 0:01:18.741
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}
Unable to load image \SystemRoot\system32\DRIVERS\nvlddmkm.sys, Win32 error 0n2
*** WARNING: Unable to verify timestamp for nvlddmkm.sys
*** ERROR: Module load completed but symbols could not be loaded for nvlddmkm.sys
Probably caused by : dxgmms1.sys ( dxgmms1!VidSchiPropagatePresentHistoryToken+ea )
Followup: MachineOwner
---------
2: 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) - Der Vorgang wurde erfolgreich beendet.
FAULTING_IP:
+0
00000000`00000000 ?? ???
EXCEPTION_PARAMETER1: 0000000000000000
EXCEPTION_PARAMETER2: 0000000000000000
CUSTOMER_CRASH_COUNT: 1
DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT
BUGCHECK_STR: 0x1E
PROCESS_NAME: System
CURRENT_IRQL: 2
EXCEPTION_RECORD: fffff88002f8c528 -- (.exr 0xfffff88002f8c528)
ExceptionAddress: fffff80002abd9c2 (nt!KeSetEvent+0x0000000000000332)
ExceptionCode: c0000005 (Access violation)
ExceptionFlags: 00000000
NumberParameters: 2
Parameter[0]: 0000000000000000
Parameter[1]: ffffffffffffffff
Attempt to read from address ffffffffffffffff
TRAP_FRAME: fffff88002f8c5d0 -- (.trap 0xfffff88002f8c5d0)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=fffffa80098c1998 rbx=0000000000000000 rcx=f7fffa80098c1998
rdx=fffffa80098d7858 rsi=0000000000000000 rdi=0000000000000000
rip=fffff80002abd9c2 rsp=fffff88002f8c760 rbp=0000000000000002
r8=fffffa80098d7858 r9=fffffa80098c1990 r10=fffffa80098d78b8
r11=0000000000000002 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0 nv up ei pl zr na po nc
nt!KeSetEvent+0x332:
fffff800`02abd9c2 48894108 mov qword ptr [rcx+8],rax ds:3010:f7fffa80`098c19a0=????????????????
Resetting default scope
LAST_CONTROL_TRANSFER: from fffff80002ab146e to fffff80002ab9710
STACK_TEXT:
fffff880`02f8b618 fffff800`02ab146e : 00000000`00000000 00000000`00000000 fffff880`02f8bd90 fffff800`02ae6668 : nt!KeBugCheck
fffff880`02f8b620 fffff800`02adf40d : fffff800`02cc7b7c fffff800`02c01e84 fffff800`02a49000 fffff880`02f8c528 : nt!KiKernelCalloutExceptionHandler+0xe
fffff880`02f8b650 fffff800`02ae6a90 : fffff800`02c08b14 fffff880`02f8b6c8 fffff880`02f8c528 fffff800`02a49000 : nt!RtlpExecuteHandlerForException+0xd
fffff880`02f8b680 fffff800`02af39ef : fffff880`02f8c528 fffff880`02f8bd90 fffff880`00000000 fffff880`00000004 : nt!RtlDispatchException+0x410
fffff880`02f8bd60 fffff800`02ab8d82 : fffff880`02f8c528 00000000`00000000 fffff880`02f8c5d0 00000000`00000000 : nt!KiDispatchException+0x16f
fffff880`02f8c3f0 fffff800`02ab768a : fffffa80`09404000 00000000`00000000 00000000`00000001 fffff880`02f8c880 : nt!KiExceptionDispatch+0xc2
fffff880`02f8c5d0 fffff800`02abd9c2 : fffffa80`094751a0 fffffa80`094461a8 fffffa80`094461a8 fffff880`13e1011b : nt!KiGeneralProtectionFault+0x10a
fffff880`02f8c760 fffff880`13e0a4aa : fffffa80`00000000 fffffa80`00000000 fffffa80`09404000 fffffa80`098d7858 : nt!KeSetEvent+0x332
fffff880`02f8c7d0 fffff880`13e0a1d7 : fffffa80`0947e010 fffffa80`0947e010 fffffa80`094772d0 fffffa80`09404000 : dxgmms1!VidSchiPropagatePresentHistoryToken+0xea
fffff880`02f8c820 fffff880`13e097da : fffffa80`00000000 fffffa80`00000000 00000000`00000002 00000000`00000000 : dxgmms1!VidSchiProcessCompletedQueuePacketInternal+0x2af
fffff880`02f8c8e0 fffff880`13e08e00 : 00000000`00000000 fffffa80`09013000 00000000`00000000 fffff880`140940e4 : dxgmms1!VidSchiProcessDpcCompletedPacket+0x3b6
fffff880`02f8c980 fffff880`13e08c4c : 00000000`00000000 fffffa80`093f4010 00000000`00000000 00000000`00000000 : dxgmms1!VidSchDdiNotifyDpcWorker+0x198
fffff880`02f8c9d0 fffff880`14b0d1cf : fffffa80`088c4040 00000000`00000000 00000000`00000022 00000000`00000000 : dxgmms1!VidSchDdiNotifyDpc+0x94
fffff880`02f8ca20 fffff880`13f62a88 : fffffa80`08951000 fffffa80`08951000 00000000`00000000 00000000`00000000 : dxgkrnl!DxgNotifyDpcCB+0x77
fffff880`02f8ca50 fffffa80`08951000 : fffffa80`08951000 00000000`00000000 00000000`00000000 fffff880`13f62a1b : nvlddmkm+0xb5a88
fffff880`02f8ca58 fffffa80`08951000 : 00000000`00000000 00000000`00000000 fffff880`13f62a1b fffffa80`08951000 : 0xfffffa80`08951000
fffff880`02f8ca60 00000000`00000000 : 00000000`00000000 fffff880`13f62a1b fffffa80`08951000 00000000`00000000 : 0xfffffa80`08951000
STACK_COMMAND: kb
FOLLOWUP_IP:
dxgmms1!VidSchiPropagatePresentHistoryToken+ea
fffff880`13e0a4aa 488d4c2420 lea rcx,[rsp+20h]
SYMBOL_STACK_INDEX: 8
SYMBOL_NAME: dxgmms1!VidSchiPropagatePresentHistoryToken+ea
FOLLOWUP_NAME: MachineOwner
MODULE_NAME: dxgmms1
IMAGE_NAME: dxgmms1.sys
DEBUG_FLR_IMAGE_TIMESTAMP: 4a5bc578
FAILURE_BUCKET_ID: X64_0x1E_dxgmms1!VidSchiPropagatePresentHistoryToken+ea
BUCKET_ID: X64_0x1E_dxgmms1!VidSchiPropagatePresentHistoryToken+ea
Followup: MachineOwner
1:Bluesreen um 23.28 heute dnach neustart dann kam der 2!!!
Microsoft (R) Windows Debugger Version 6.11.0001.404 AMD64
Copyright (c) Microsoft Corporation. All rights reserved.
Loading Dump File [C:\Windows\Minidump\013011-22854-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available
Symbol search path is: SRV*C:\symbols*Symbol information
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`02a09000 PsLoadedModuleList = 0xfffff800`02c46e50
Debug session time: Sun Jan 30 23:27:12.303 2011 (GMT+1)
System Uptime: 0 days 0:12:05.036
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
---------
3: 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) - Der Vorgang wurde erfolgreich beendet.
FAULTING_IP:
+0
00000000`00000000 ?? ???
EXCEPTION_PARAMETER1: 0000000000000000
EXCEPTION_PARAMETER2: 0000000000000000
CUSTOMER_CRASH_COUNT: 1
DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT
BUGCHECK_STR: 0x1E
PROCESS_NAME: BlackOpsMP.exe
CURRENT_IRQL: 2
EXCEPTION_RECORD: fffff880009b05d8 -- (.exr 0xfffff880009b05d8)
ExceptionAddress: fffff80002a84e39 (nt!KiProcessExpiredTimerList+0x0000000000000129)
ExceptionCode: c0000005 (Access violation)
ExceptionFlags: 00000000
NumberParameters: 2
Parameter[0]: 0000000000000000
Parameter[1]: ffffffffffffffff
Attempt to read from address ffffffffffffffff
TRAP_FRAME: fffff880009b0680 -- (.trap 0xfffff880009b0680)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=fffffa800715a3d8 rbx=0000000000000000 rcx=f7fffa800715a3d8
rdx=0000000000000102 rsi=0000000000000000 rdi=0000000000000000
rip=fffff80002a84e39 rsp=fffff880009b0810 rbp=fffffa800747cc68
r8=fffff88002fd7301 r9=0000000000000002 r10=000000000000008c
r11=0000000000000000 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0 nv up ei pl zr na po nc
nt!KiProcessExpiredTimerList+0x129:
fffff800`02a84e39 48894108 mov qword ptr [rcx+8],rax ds:5400:f7fffa80`0715a3e0=????????????????
Resetting default scope
LAST_CONTROL_TRANSFER: from fffff80002a7146e to fffff80002a79710
STACK_TEXT:
fffff880`009af6c8 fffff800`02a7146e : fffffa80`096ab8a0 fffffa80`08a408c0 fffff880`009afe40 fffff800`02aa6668 : nt!KeBugCheck
fffff880`009af6d0 fffff800`02a9f40d : fffff800`02c87b7c fffff800`02bc1e84 fffff800`02a09000 fffff880`009b05d8 : nt!KiKernelCalloutExceptionHandler+0xe
fffff880`009af700 fffff800`02aa6a90 : fffff800`02bc8a40 fffff880`009af778 fffff880`009b05d8 fffff800`02a09000 : nt!RtlpExecuteHandlerForException+0xd
fffff880`009af730 fffff800`02ab39ef : fffff880`009b05d8 fffff880`009afe40 fffff880`00000000 fffffa80`0715a3d0 : nt!RtlDispatchException+0x410
fffff880`009afe10 fffff800`02a78d82 : fffff880`009b05d8 fffffa80`0747cc68 fffff880`009b0680 00000000`00000000 : nt!KiDispatchException+0x16f
fffff880`009b04a0 fffff800`02a7768a : 00000000`00800000 00000000`00000009 00000000`00000000 fffffa80`07019002 : nt!KiExceptionDispatch+0xc2
fffff880`009b0680 fffff800`02a84e39 : fffffa80`0747cc20 fffffa80`0719d168 fffffa80`0719d168 00000000`00000102 : nt!KiGeneralProtectionFault+0x10a
fffff880`009b0810 fffff800`02a854be : 00000001`b027c594 fffff880`009b0e88 00000000`0000b58c fffff880`02fd8708 : nt!KiProcessExpiredTimerList+0x129
fffff880`009b0e60 fffff800`02a84cb7 : fffffa80`08b87cc1 fffffa80`0000b58c fffffa80`08b81000 00000000`0000008c : nt!KiTimerExpiration+0x1be
fffff880`009b0f00 fffff800`02a7f865 : 000004d8`00000000 fffffa80`074155d0 00000000`00000000 fffff880`13e6d684 : nt!KiRetireDpcList+0x277
fffff880`009b0fb0 fffff800`02a7f67c : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KxRetireDpcList+0x5
fffff880`0d1c47f0 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiDispatchInterruptContinue
STACK_COMMAND: kb
FOLLOWUP_IP:
nt!KiKernelCalloutExceptionHandler+e
fffff800`02a7146e 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: 4c1c44a9
FAILURE_BUCKET_ID: X64_0x1E_nt!KiKernelCalloutExceptionHandler+e
BUCKET_ID: X64_0x1E_nt!KiKernelCalloutExceptionHandler+e
Followup: MachineOwner
---------
So jetzt der 2 Bluesreen danach:!!!!!
Microsoft (R) Windows Debugger Version 6.11.0001.404 AMD64
Copyright (c) Microsoft Corporation. All rights reserved.
Loading Dump File [C:\Windows\Minidump\013011-26473-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available
Symbol search path is: SRV*C:\symbols*Symbol information
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`02a49000 PsLoadedModuleList = 0xfffff800`02c86e50
Debug session time: Sun Jan 30 23:29:20.009 2011 (GMT+1)
System Uptime: 0 days 0:01:18.741
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}
Unable to load image \SystemRoot\system32\DRIVERS\nvlddmkm.sys, Win32 error 0n2
*** WARNING: Unable to verify timestamp for nvlddmkm.sys
*** ERROR: Module load completed but symbols could not be loaded for nvlddmkm.sys
Probably caused by : dxgmms1.sys ( dxgmms1!VidSchiPropagatePresentHistoryToken+ea )
Followup: MachineOwner
---------
2: 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) - Der Vorgang wurde erfolgreich beendet.
FAULTING_IP:
+0
00000000`00000000 ?? ???
EXCEPTION_PARAMETER1: 0000000000000000
EXCEPTION_PARAMETER2: 0000000000000000
CUSTOMER_CRASH_COUNT: 1
DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT
BUGCHECK_STR: 0x1E
PROCESS_NAME: System
CURRENT_IRQL: 2
EXCEPTION_RECORD: fffff88002f8c528 -- (.exr 0xfffff88002f8c528)
ExceptionAddress: fffff80002abd9c2 (nt!KeSetEvent+0x0000000000000332)
ExceptionCode: c0000005 (Access violation)
ExceptionFlags: 00000000
NumberParameters: 2
Parameter[0]: 0000000000000000
Parameter[1]: ffffffffffffffff
Attempt to read from address ffffffffffffffff
TRAP_FRAME: fffff88002f8c5d0 -- (.trap 0xfffff88002f8c5d0)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=fffffa80098c1998 rbx=0000000000000000 rcx=f7fffa80098c1998
rdx=fffffa80098d7858 rsi=0000000000000000 rdi=0000000000000000
rip=fffff80002abd9c2 rsp=fffff88002f8c760 rbp=0000000000000002
r8=fffffa80098d7858 r9=fffffa80098c1990 r10=fffffa80098d78b8
r11=0000000000000002 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0 nv up ei pl zr na po nc
nt!KeSetEvent+0x332:
fffff800`02abd9c2 48894108 mov qword ptr [rcx+8],rax ds:3010:f7fffa80`098c19a0=????????????????
Resetting default scope
LAST_CONTROL_TRANSFER: from fffff80002ab146e to fffff80002ab9710
STACK_TEXT:
fffff880`02f8b618 fffff800`02ab146e : 00000000`00000000 00000000`00000000 fffff880`02f8bd90 fffff800`02ae6668 : nt!KeBugCheck
fffff880`02f8b620 fffff800`02adf40d : fffff800`02cc7b7c fffff800`02c01e84 fffff800`02a49000 fffff880`02f8c528 : nt!KiKernelCalloutExceptionHandler+0xe
fffff880`02f8b650 fffff800`02ae6a90 : fffff800`02c08b14 fffff880`02f8b6c8 fffff880`02f8c528 fffff800`02a49000 : nt!RtlpExecuteHandlerForException+0xd
fffff880`02f8b680 fffff800`02af39ef : fffff880`02f8c528 fffff880`02f8bd90 fffff880`00000000 fffff880`00000004 : nt!RtlDispatchException+0x410
fffff880`02f8bd60 fffff800`02ab8d82 : fffff880`02f8c528 00000000`00000000 fffff880`02f8c5d0 00000000`00000000 : nt!KiDispatchException+0x16f
fffff880`02f8c3f0 fffff800`02ab768a : fffffa80`09404000 00000000`00000000 00000000`00000001 fffff880`02f8c880 : nt!KiExceptionDispatch+0xc2
fffff880`02f8c5d0 fffff800`02abd9c2 : fffffa80`094751a0 fffffa80`094461a8 fffffa80`094461a8 fffff880`13e1011b : nt!KiGeneralProtectionFault+0x10a
fffff880`02f8c760 fffff880`13e0a4aa : fffffa80`00000000 fffffa80`00000000 fffffa80`09404000 fffffa80`098d7858 : nt!KeSetEvent+0x332
fffff880`02f8c7d0 fffff880`13e0a1d7 : fffffa80`0947e010 fffffa80`0947e010 fffffa80`094772d0 fffffa80`09404000 : dxgmms1!VidSchiPropagatePresentHistoryToken+0xea
fffff880`02f8c820 fffff880`13e097da : fffffa80`00000000 fffffa80`00000000 00000000`00000002 00000000`00000000 : dxgmms1!VidSchiProcessCompletedQueuePacketInternal+0x2af
fffff880`02f8c8e0 fffff880`13e08e00 : 00000000`00000000 fffffa80`09013000 00000000`00000000 fffff880`140940e4 : dxgmms1!VidSchiProcessDpcCompletedPacket+0x3b6
fffff880`02f8c980 fffff880`13e08c4c : 00000000`00000000 fffffa80`093f4010 00000000`00000000 00000000`00000000 : dxgmms1!VidSchDdiNotifyDpcWorker+0x198
fffff880`02f8c9d0 fffff880`14b0d1cf : fffffa80`088c4040 00000000`00000000 00000000`00000022 00000000`00000000 : dxgmms1!VidSchDdiNotifyDpc+0x94
fffff880`02f8ca20 fffff880`13f62a88 : fffffa80`08951000 fffffa80`08951000 00000000`00000000 00000000`00000000 : dxgkrnl!DxgNotifyDpcCB+0x77
fffff880`02f8ca50 fffffa80`08951000 : fffffa80`08951000 00000000`00000000 00000000`00000000 fffff880`13f62a1b : nvlddmkm+0xb5a88
fffff880`02f8ca58 fffffa80`08951000 : 00000000`00000000 00000000`00000000 fffff880`13f62a1b fffffa80`08951000 : 0xfffffa80`08951000
fffff880`02f8ca60 00000000`00000000 : 00000000`00000000 fffff880`13f62a1b fffffa80`08951000 00000000`00000000 : 0xfffffa80`08951000
STACK_COMMAND: kb
FOLLOWUP_IP:
dxgmms1!VidSchiPropagatePresentHistoryToken+ea
fffff880`13e0a4aa 488d4c2420 lea rcx,[rsp+20h]
SYMBOL_STACK_INDEX: 8
SYMBOL_NAME: dxgmms1!VidSchiPropagatePresentHistoryToken+ea
FOLLOWUP_NAME: MachineOwner
MODULE_NAME: dxgmms1
IMAGE_NAME: dxgmms1.sys
DEBUG_FLR_IMAGE_TIMESTAMP: 4a5bc578
FAILURE_BUCKET_ID: X64_0x1E_dxgmms1!VidSchiPropagatePresentHistoryToken+ea
BUCKET_ID: X64_0x1E_dxgmms1!VidSchiPropagatePresentHistoryToken+ea
Followup: MachineOwner
