Microsoft (R) Windows Debugger Version 6.6.0003.5
Copyright (c) Microsoft Corporation. All rights reserved.
Loading Dump File [C:\Windows\Minidump\062812-19546-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available
Symbol search path is: SRV*c:\symbols*http://msdl.microsoft.com/download/symbols
Executable search path is:
Windows Vista Kernel Version 7601 (Service Pack 1) MP (2 procs) Free x86 compatible
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 7601.17803.x86fre.win7sp1_gdr.120330-1504
Kernel base = 0x82a4d000 PsLoadedModuleList = 0x82b964d0
Debug session time: Thu Jun 28 23:17:02.909 2012 (GMT+2)
System Uptime: 0 days 1:59:02.610
Loading Kernel Symbols
............................................................................................................................................................
Loading User Symbols
Loading unloaded module list
.............
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck 1000007E, {c0000005, 91560501, 8b9cdba0, 8b9cd780}
Probably caused by : dxgmms1.sys ( dxgmms1!VIDMM_GLOBAL::ProcessDeferredCommand+443 )
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: c0000005, The exception code that was not handled
Arg2: 91560501, The address that the exception occurred at
Arg3: 8b9cdba0, Exception Record Address
Arg4: 8b9cd780, Context Record Address
Debugging Details:
------------------
EXCEPTION_CODE: (NTSTATUS) 0xc0000005 - L
FAULTING_IP:
dxgmms1!VIDMM_GLOBAL::ProcessDeferredCommand+443
91560501 8b00 mov eax,[eax]
EXCEPTION_RECORD: 8b9cdba0 -- (.exr ffffffff8b9cdba0)
ExceptionAddress: 91560501 (dxgmms1!VIDMM_GLOBAL::ProcessDeferredCommand+0x00000443)
ExceptionCode: c0000005 (Access violation)
ExceptionFlags: 00000000
NumberParameters: 2
Parameter[0]: 00000000
Parameter[1]: 00000000
Attempt to read from address 00000000
CONTEXT: 8b9cd780 -- (.cxr ffffffff8b9cd780)
eax=00000000 ebx=00000000 ecx=ffffffd8 edx=b2920868 esi=b20f48d8 edi=8569ba90
eip=91560501 esp=8b9cdc68 ebp=8b9cdcc4 iopl=0 nv up ei pl nz na pe cy
cs=0008 ss=0010 ds=0023 es=0023 fs=0030 gs=0000 efl=00010203
dxgmms1!VIDMM_GLOBAL::ProcessDeferredCommand+0x443:
91560501 8b00 mov eax,[eax] ds:0023:00000000=????????
Resetting default scope
CUSTOMER_CRASH_COUNT: 1
DEFAULT_BUCKET_ID: NULL_DEREFERENCE
CURRENT_IRQL: 0
ERROR_CODE: (NTSTATUS) 0xc0000005 - L
READ_ADDRESS: GetUlongFromAddress: unable to read from 82bb6848
Unable to read MiSystemVaType memory at 82b95e20
00000000
BUGCHECK_STR: 0x7E
LAST_CONTROL_TRANSFER: from 91560e66 to 91560501
STACK_TEXT:
8b9cdcc4 91560e66 019cdce0 00000000 8b9cdcf8 dxgmms1!VIDMM_GLOBAL::ProcessDeferredCommand+0x443
8b9cdcf0 915624c8 00000000 8b9cdd18 915761df dxgmms1!VIDMM_GLOBAL::ProcessTerminationCommand+0x40
8b9cdcfc 915761df 88170da8 8733c8f0 8733c8f0 dxgmms1!VidMmiProcessTerminationCommand+0x10
8b9cdd18 9157718f 873fb008 8733caf0 8b9cdd3c dxgmms1!VidSchiSubmitDeviceCommand+0x33
8b9cdd28 915773de 8733c8f0 82a84539 87bb4008 dxgmms1!VidSchiSubmitQueueCommand+0xaf
8b9cdd3c 91577485 87bb4008 00000000 87bc0610 dxgmms1!VidSchiRun_PriorityTable+0x24
8b9cdd50 82c56056 87bb4008 af2c3780 00000000 dxgmms1!VidSchiWorkerThread+0x7f
8b9cdd90 82afe1a9 91577406 87bb4008 00000000 nt!PspSystemThreadStartup+0x9e
00000000 00000000 00000000 00000000 00000000 nt!KiThreadStartup+0x19
STACK_COMMAND: .bugcheck ; kb
FOLLOWUP_IP:
dxgmms1!VIDMM_GLOBAL::ProcessDeferredCommand+443
91560501 8b00 mov eax,[eax]
FAULTING_SOURCE_CODE:
SYMBOL_STACK_INDEX: 0
FOLLOWUP_NAME: MachineOwner
SYMBOL_NAME: dxgmms1!VIDMM_GLOBAL::ProcessDeferredCommand+443
MODULE_NAME: dxgmms1
IMAGE_NAME: dxgmms1.sys
DEBUG_FLR_IMAGE_TIMESTAMP: 4d4a24c1
FAILURE_BUCKET_ID: 0x7E_dxgmms1!VIDMM_GLOBAL::ProcessDeferredCommand+443
BUCKET_ID: 0x7E_dxgmms1!VIDMM_GLOBAL::ProcessDeferredCommand+443
Followup: MachineOwner
---------