Microsoft (R) Windows Debugger Version 6.12.0002.633 AMD64
Copyright (c) Microsoft Corporation. All rights reserved.
Loading Dump File [F:\a\Minidump\D M P\DMP\021311-17534-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
Built by: 7600.16695.amd64fre.win7_gdr.101026-1503
Machine Name:
Kernel base = 0xfffff800`02a5c000 PsLoadedModuleList = 0xfffff800`02c99e50
Debug session time: Sun Feb 13 08:27:54.167 2011 (UTC - 5:00)
System Uptime: 0 days 4:20:51.525
Loading Kernel Symbols
...............................................................
................................................................
....................
Loading User Symbols
Loading unloaded module list
......
Unable to load image \SystemRoot\System32\drivers\dxgmms1.sys, Win32 error 0n2
*** WARNING: Unable to verify timestamp for dxgmms1.sys
*** ERROR: Module load completed but symbols could not be loaded for dxgmms1.sys
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck 1000007E, {ffffffffc0000005, fffff880048307ac, fffff88002e14748, fffff88002e13fb0}
Probably caused by : dxgmms1.sys ( dxgmms1+307ac )
Followup: MachineOwner
---------
0: 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: fffff880048307ac, The address that the exception occurred at
Arg3: fffff88002e14748, Exception Record Address
Arg4: fffff88002e13fb0, 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+307ac
fffff880`048307ac 488b11 mov rdx,qword ptr [rcx]
EXCEPTION_RECORD: fffff88002e14748 -- (.exr 0xfffff88002e14748)
ExceptionAddress: fffff880048307ac (dxgmms1+0x00000000000307ac)
ExceptionCode: c0000005 (Access violation)
ExceptionFlags: 00000000
NumberParameters: 2
Parameter[0]: 0000000000000000
Parameter[1]: ffffffffffffffff
Attempt to read from address ffffffffffffffff
CONTEXT: fffff88002e13fb0 -- (.cxr 0xfffff88002e13fb0)
rax=0000000000000000 rbx=0000000000000000 rcx=1000000000000000
rdx=fffff8a001e91320 rsi=fffff8a001e91320 rdi=0000000000000000
rip=fffff880048307ac rsp=fffff88002e14980 rbp=fffffa8005c23000
r8=000000000002b000 r9=0000000000000000 r10=0000000000000001
r11=fffff8a001e91428 r12=0000000000000000 r13=0000000000000001
r14=fffffa8005c2cca0 r15=fffff8a001e91428
iopl=0 nv up ei pl nz na po nc
cs=0010 ss=0018 ds=002b es=002b fs=0053 gs=002b efl=00210206
dxgmms1+0x307ac:
fffff880`048307ac 488b11 mov rdx,qword ptr [rcx] ds:002b:10000000`00000000=????????????????
Resetting default scope
CUSTOMER_CRASH_COUNT: 1
DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT
PROCESS_NAME: System
CURRENT_IRQL: 0
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 fffff80002d040e0
ffffffffffffffff
FOLLOWUP_IP:
dxgmms1+307ac
fffff880`048307ac 488b11 mov rdx,qword ptr [rcx]
BUGCHECK_STR: 0x7E
LAST_CONTROL_TRANSFER: from 0000000000000000 to fffff880048307ac
STACK_TEXT:
fffff880`02e14980 00000000`00000000 : fffffa80`05c23000 fffff8a0`01e91320 fffff8a0`00000000 fffffa80`05c22b90 : dxgmms1+0x307ac
SYMBOL_STACK_INDEX: 0
SYMBOL_NAME: dxgmms1+307ac
FOLLOWUP_NAME: MachineOwner
MODULE_NAME: dxgmms1
IMAGE_NAME: dxgmms1.sys
DEBUG_FLR_IMAGE_TIMESTAMP: 4d3fa174
STACK_COMMAND: .cxr 0xfffff88002e13fb0 ; kb
FAILURE_BUCKET_ID: X64_0x7E_dxgmms1+307ac
BUCKET_ID: X64_0x7E_dxgmms1+307ac
Followup: MachineOwner
---------
Microsoft (R) Windows Debugger Version 6.12.0002.633 AMD64
Copyright (c) Microsoft Corporation. All rights reserved.
Loading Dump File [F:\a\Minidump\D M P\DMP\021311-18314-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
Built by: 7600.16695.amd64fre.win7_gdr.101026-1503
Machine Name:
Kernel base = 0xfffff800`02a14000 PsLoadedModuleList = 0xfffff800`02c51e50
Debug session time: Sun Feb 13 10:20:01.969 2011 (UTC - 5:00)
System Uptime: 0 days 1:38:46.327
Loading Kernel Symbols
...............................................................
................................................................
....................
Loading User Symbols
Loading unloaded module list
........
Unable to load image \SystemRoot\System32\drivers\dxgmms1.sys, Win32 error 0n2
*** WARNING: Unable to verify timestamp for dxgmms1.sys
*** ERROR: Module load completed but symbols could not be loaded for dxgmms1.sys
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck 1000007E, {ffffffffc0000005, fffff880048307ac, fffff88002135748, fffff88002134fb0}
Probably caused by : dxgmms1.sys ( dxgmms1+307ac )
Followup: MachineOwner
---------
2: 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: fffff880048307ac, The address that the exception occurred at
Arg3: fffff88002135748, Exception Record Address
Arg4: fffff88002134fb0, 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+307ac
fffff880`048307ac 488b11 mov rdx,qword ptr [rcx]
EXCEPTION_RECORD: fffff88002135748 -- (.exr 0xfffff88002135748)
ExceptionAddress: fffff880048307ac (dxgmms1+0x00000000000307ac)
ExceptionCode: c0000005 (Access violation)
ExceptionFlags: 00000000
NumberParameters: 2
Parameter[0]: 0000000000000000
Parameter[1]: ffffffffffffffff
Attempt to read from address ffffffffffffffff
CONTEXT: fffff88002134fb0 -- (.cxr 0xfffff88002134fb0)
rax=0000000000000000 rbx=0000000000000000 rcx=1000000000000000
rdx=fffff8a009d154a0 rsi=fffff8a009d154a0 rdi=0000000000000000
rip=fffff880048307ac rsp=fffff88002135980 rbp=fffffa8005bec000
r8=0000000000100000 r9=0000000000000000 r10=0000000000000001
r11=fffff8a009d155a8 r12=0000000000000000 r13=0000000000000001
r14=fffffa8005919ec0 r15=fffff8a009d155a8
iopl=0 nv up ei pl nz na po nc
cs=0010 ss=0018 ds=002b es=002b fs=0053 gs=002b efl=00010206
dxgmms1+0x307ac:
fffff880`048307ac 488b11 mov rdx,qword ptr [rcx] ds:002b:10000000`00000000=????????????????
Resetting default scope
CUSTOMER_CRASH_COUNT: 1
DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT
PROCESS_NAME: System
CURRENT_IRQL: 0
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 fffff80002cbc0e0
ffffffffffffffff
FOLLOWUP_IP:
dxgmms1+307ac
fffff880`048307ac 488b11 mov rdx,qword ptr [rcx]
BUGCHECK_STR: 0x7E
LAST_CONTROL_TRANSFER: from 0000000000000000 to fffff880048307ac
STACK_TEXT:
fffff880`02135980 00000000`00000000 : fffffa80`05bec000 fffff8a0`09d154a0 fffff8a0`00000000 fffffa80`05be9b90 : dxgmms1+0x307ac
SYMBOL_STACK_INDEX: 0
SYMBOL_NAME: dxgmms1+307ac
FOLLOWUP_NAME: MachineOwner
MODULE_NAME: dxgmms1
IMAGE_NAME: dxgmms1.sys
DEBUG_FLR_IMAGE_TIMESTAMP: 4d3fa174
STACK_COMMAND: .cxr 0xfffff88002134fb0 ; kb
FAILURE_BUCKET_ID: X64_0x7E_dxgmms1+307ac
BUCKET_ID: X64_0x7E_dxgmms1+307ac
Followup: MachineOwner
---------