Microsoft (R) Windows Debugger Version 6.12.0002.633 AMD64
Copyright (c) Microsoft Corporation. All rights reserved.
Loading Dump File [F:\DMP\122410-18392-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available
Symbol search path is: SRV*c:\websymbols*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 Personal
Built by: 7600.16617.amd64fre.win7_gdr.100618-1621
Machine Name:
Kernel base = 0xfffff800`0325f000 PsLoadedModuleList = 0xfffff800`0349ce50
Debug session time: Fri Dec 24 17:54:31.681 2010 (UTC - 4:00)
System Uptime: 1 days 10:46:11.273
Loading Kernel Symbols
...............................................................
................................................................
....................................
Loading User Symbols
Loading unloaded module list
..................................................
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck 1000007E, {ffffffffc0000005, fffff8800516a622, fffff8800959b948, fffff8800959b1b0}
Probably caused by : dxgmms1.sys ( dxgmms1!VidSchiReadCommandFromContextQueue+62 )
Followup: MachineOwner
---------
1: kd> !analyze -v
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
SYSTEM_THREAD_EXCEPTION_NOT_HANDLED_M (1000007e)
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.
Some common problems are exception code 0x80000003. This means a hard
coded breakpoint or assertion was hit, but this system was booted
/NODEBUG. This is not supposed to happen as developers should never have
hardcoded breakpoints in retail code, but ...
If this happens, make sure a debugger gets connected, and the
system is booted /DEBUG. This will let us see why this breakpoint is
happening.
Arguments:
Arg1: ffffffffc0000005, The exception code that was not handled
Arg2: fffff8800516a622, The address that the exception occurred at
Arg3: fffff8800959b948, Exception Record Address
Arg4: fffff8800959b1b0, Context Record Address
Debugging Details:
------------------
EXCEPTION_CODE: (NTSTATUS) 0xc0000005 - The instruction at 0x%08lx referenced memory at 0x%08lx. The memory could not be %s.
FAULTING_IP:
dxgmms1!VidSchiReadCommandFromContextQueue+62
fffff880`0516a622 488b5720 mov rdx,qword ptr [rdi+20h]
EXCEPTION_RECORD: fffff8800959b948 -- (.exr 0xfffff8800959b948)
ExceptionAddress: fffff8800516a622 (dxgmms1!VidSchiReadCommandFromContextQueue+0x0000000000000062)
ExceptionCode: c0000005 (Access violation)
ExceptionFlags: 00000000
NumberParameters: 2
Parameter[0]: 0000000000000000
Parameter[1]: ffffffffffffffff
Attempt to read from address ffffffffffffffff
CONTEXT: fffff8800959b1b0 -- (.cxr 0xfffff8800959b1b0)
rax=00000000ffffffff rbx=fffffa8006cbd9b0 rcx=fffffa8006cbd9b0
rdx=0000000000000001 rsi=fffffa8006794010 rdi=00fffa8006dc0ec0
rip=fffff8800516a622 rsp=fffff8800959bb80 rbp=0000000000000001
r8=000000000000000f r9=0000000000000000 r10=fffff8800516b2b4
r11=fffff8800959bb70 r12=fffffa8006802000 r13=fffff88005196dc0
r14=0000000000000000 r15=0000000000000001
iopl=0 nv up ei pl nz ac po cy
cs=0010 ss=0000 ds=002b es=002b fs=0053 gs=002b efl=00010217
dxgmms1!VidSchiReadCommandFromContextQueue+0x62:
fffff880`0516a622 488b5720 mov rdx,qword ptr [rdi+20h] ds:002b:00fffa80`06dc0ee0=????????????????
Resetting default scope
CUSTOMER_CRASH_COUNT: 1
DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT
PROCESS_NAME: System
CURRENT_IRQL: 2
ERROR_CODE: (NTSTATUS) 0xc0000005 - The instruction at 0x%08lx referenced memory at 0x%08lx. The memory could not be %s.
EXCEPTION_PARAMETER1: 0000000000000000
EXCEPTION_PARAMETER2: ffffffffffffffff
READ_ADDRESS: GetPointerFromAddress: unable to read from fffff800035070e0
ffffffffffffffff
FOLLOWUP_IP:
dxgmms1!VidSchiReadCommandFromContextQueue+62
fffff880`0516a622 488b5720 mov rdx,qword ptr [rdi+20h]
BUGCHECK_STR: 0x7E
LAST_CONTROL_TRANSFER: from fffff8800516a255 to fffff8800516a622
STACK_TEXT:
fffff880`0959bb80 fffff880`0516a255 : fffffa80`06794010 fffffa80`06cbd9b0 00000000`00000000 00000000`00000001 : dxgmms1!VidSchiReadCommandFromContextQueue+0x62
fffff880`0959bbf0 fffff880`05196e7a : 00000000`00000000 fffffa80`06cbd9b0 00000000`00000080 fffffa80`06794010 : dxgmms1!VidSchiScheduleCommandToRun+0x169
fffff880`0959bd00 fffff800`03573c06 : 00000000`02613244 fffffa80`067cc060 fffffa80`03b52b30 fffffa80`067cc060 : dxgmms1!VidSchiWorkerThread+0xba
fffff880`0959bd40 fffff800`032adc26 : fffff880`009ea180 fffffa80`067cc060 fffff880`009f4fc0 fffff880`0143b534 : nt!PspSystemThreadStartup+0x5a
fffff880`0959bd80 00000000`00000000 : fffff880`0959c000 fffff880`09596000 fffff880`0959b690 00000000`00000000 : nt!KxStartSystemThread+0x16
SYMBOL_STACK_INDEX: 0
SYMBOL_NAME: dxgmms1!VidSchiReadCommandFromContextQueue+62
FOLLOWUP_NAME: MachineOwner
MODULE_NAME: dxgmms1
IMAGE_NAME: dxgmms1.sys
DEBUG_FLR_IMAGE_TIMESTAMP: 4a5bc578
STACK_COMMAND: .cxr 0xfffff8800959b1b0 ; kb
FAILURE_BUCKET_ID: X64_0x7E_dxgmms1!VidSchiReadCommandFromContextQueue+62
BUCKET_ID: X64_0x7E_dxgmms1!VidSchiReadCommandFromContextQueue+62
Followup: MachineOwner
---------
Microsoft (R) Windows Debugger Version 6.12.0002.633 AMD64
Copyright (c) Microsoft Corporation. All rights reserved.
Loading Dump File [F:\DMP\122610-16692-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available
Symbol search path is: SRV*c:\websymbols*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 Personal
Built by: 7600.16617.amd64fre.win7_gdr.100618-1621
Machine Name:
Kernel base = 0xfffff800`03219000 PsLoadedModuleList = 0xfffff800`03456e50
Debug session time: Sun Dec 26 14:11:33.409 2010 (UTC - 4:00)
System Uptime: 0 days 3:46:57.352
Loading Kernel Symbols
...............................................................
................................................................
...........................
Loading User Symbols
Loading unloaded module list
.......
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck 1E, {ffffffffc0000005, fffff8000328f639, 0, ffffffffffffffff}
Probably caused by : ntkrnlmp.exe ( nt!KiSwapContext+d9 )
Followup: MachineOwner
---------
1: 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: ffffffffc0000005, The exception code that was not handled
Arg2: fffff8000328f639, The address that the exception occurred at
Arg3: 0000000000000000, Parameter 0 of the exception
Arg4: ffffffffffffffff, Parameter 1 of the exception
Debugging Details:
------------------
EXCEPTION_CODE: (NTSTATUS) 0xc0000005 - The instruction at 0x%08lx referenced memory at 0x%08lx. The memory could not be %s.
FAULTING_IP:
nt!KiSwapContext+d9
fffff800`0328f639 c3 ret
EXCEPTION_PARAMETER1: 0000000000000000
EXCEPTION_PARAMETER2: ffffffffffffffff
READ_ADDRESS: GetPointerFromAddress: unable to read from fffff800034c10e0
ffffffffffffffff
ERROR_CODE: (NTSTATUS) 0xc0000005 - The instruction at 0x%08lx referenced memory at 0x%08lx. The memory could not be %s.
BUGCHECK_STR: 0x1E_c0000005
CUSTOMER_CRASH_COUNT: 1
DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT
PROCESS_NAME: System
CURRENT_IRQL: 2
EXCEPTION_RECORD: fffff88003717738 -- (.exr 0xfffff88003717738)
ExceptionAddress: fffff8000328f639 (nt!KiSwapContext+0x00000000000000d9)
ExceptionCode: c0000005 (Access violation)
ExceptionFlags: 00000000
NumberParameters: 2
Parameter[0]: 0000000000000000
Parameter[1]: ffffffffffffffff
Attempt to read from address ffffffffffffffff
TRAP_FRAME: fffff880037177e0 -- (.trap 0xfffff880037177e0)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=0000000000000000 rbx=0000000000000000 rcx=fffff88003717940
rdx=0000000000187000 rsi=0000000000000000 rdi=0000000000000000
rip=fffff8000328f639 rsp=fffff88003717978 rbp=fffffa80049bc470
r8=fffffa8003b52bb8 r9=0000000000000000 r10=fffffffffffffffd
r11=000000008000e5c0 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0 nv up ei ng nz na po nc
nt!KiSwapContext+0xd9:
fffff800`0328f639 c3 ret
Resetting default scope
LAST_CONTROL_TRANSFER: from fffff800032c3a39 to fffff80003289740
STACK_TEXT:
fffff880`03716f68 fffff800`032c3a39 : 00000000`0000001e ffffffff`c0000005 fffff800`0328f639 00000000`00000000 : nt!KeBugCheckEx
fffff880`03716f70 fffff800`03288d82 : fffff880`03717738 fffffa80`049bc470 fffff880`037177e0 fffffa80`049bc530 : nt!KiDispatchException+0x1b9
fffff880`03717600 fffff800`0328768a : fffffa80`04a1aad0 fffffa80`04a1df88 00000000`00000014 fffff800`0328f9a2 : nt!KiExceptionDispatch+0xc2
fffff880`037177e0 fffff800`0328f639 : 00fff800`03290992 00000000`00000000 fffffa80`049bc470 00000000`00000000 : nt!KiGeneralProtectionFault+0x10a
fffff880`03717978 00fff800`03290992 : 00000000`00000000 fffffa80`049bc470 00000000`00000000 00000000`00000006 : nt!KiSwapContext+0xd9
fffff880`03717980 00000000`00000000 : fffffa80`049bc470 00000000`00000000 00000000`00000006 00000000`00000000 : 0xfff800`03290992
STACK_COMMAND: kb
FOLLOWUP_IP:
nt!KiSwapContext+d9
fffff800`0328f639 c3 ret
SYMBOL_STACK_INDEX: 4
SYMBOL_NAME: nt!KiSwapContext+d9
FOLLOWUP_NAME: MachineOwner
MODULE_NAME: nt
IMAGE_NAME: ntkrnlmp.exe
DEBUG_FLR_IMAGE_TIMESTAMP: 4c1c44a9
FAILURE_BUCKET_ID: X64_0x1E_c0000005_nt!KiSwapContext+d9
BUCKET_ID: X64_0x1E_c0000005_nt!KiSwapContext+d9
Followup: MachineOwner
---------