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\120910-29296-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 (2 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 7600.16617.amd64fre.win7_gdr.100618-1621
Machine Name:
Kernel base = 0xfffff800`02a1f000 PsLoadedModuleList = 0xfffff800`02c5ce50
Debug session time: Thu Dec 9 00:26:17.717 2010 (UTC - 5:00)
System Uptime: 1 days 11:00:09.861
Loading Kernel Symbols
...............................................................
................................................................
.....................................
Loading User Symbols
Loading unloaded module list
..................................................
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck 1000007E, {ffffffffc0000005, fffff80002a9749b, fffff880058488a8, fffff88005848110}
Probably caused by : hardware ( dxgmms1!VidSchiWaitForSchedulerEvents+1ee )
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: fffff80002a9749b, The address that the exception occurred at
Arg3: fffff880058488a8, Exception Record Address
Arg4: fffff88005848110, 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:
nt!ExAcquireResourceExclusiveLite+3b
fffff800`02a9749b f6654c mul al,byte ptr [rbp+4Ch]
EXCEPTION_RECORD: fffff880058488a8 -- (.exr 0xfffff880058488a8)
ExceptionAddress: fffff80002a9749b (nt!ExAcquireResourceExclusiveLite+0x000000000000003b)
ExceptionCode: c0000005 (Access violation)
ExceptionFlags: 00000000
NumberParameters: 2
Parameter[0]: 0000000000000000
Parameter[1]: 000000000000004d
Attempt to read from address 000000000000004d
CONTEXT: fffff88005848110 -- (.cxr 0xfffff88005848110)
rax=0000000000000001 rbx=fffffa80053734a8 rcx=fffffa80053734a8
rdx=0000000000187001 rsi=0000000000000002 rdi=fffff80002c09e80
rip=fffff80002a9749b rsp=fffff88005848ae0 rbp=0000000000000001
r8=fffff80002a1f000 r9=0000000000000000 r10=fffffffffffffffe
r11=0000000000000246 r12=0000000000000000 r13=fffff88004346dc0
r14=0000000000000102 r15=0000000000000001
iopl=0 nv up ei pl nz na pe nc
cs=0010 ss=0000 ds=002b es=002b fs=0053 gs=002b efl=00010202
nt!ExAcquireResourceExclusiveLite+0x3b:
fffff800`02a9749b f6654c mul al,byte ptr [rbp+4Ch] ss:00000000`0000004d=??
Resetting default scope
CUSTOMER_CRASH_COUNT: 1
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: 000000000000004d
READ_ADDRESS: GetPointerFromAddress: unable to read from fffff80002cc70e0
000000000000004d
FOLLOWUP_IP:
dxgmms1!VidSchiWaitForSchedulerEvents+1ee
fffff880`043472ae 413bde cmp ebx,r14d
BUGCHECK_STR: 0x7E
DEFAULT_BUCKET_ID: NULL_CLASS_PTR_DEREFERENCE
MISALIGNED_IP:
nt!ExAcquireResourceExclusiveLite+3b
fffff800`02a9749b f6654c mul al,byte ptr [rbp+4Ch]
LAST_CONTROL_TRANSFER: from fffff880043472ae to fffff80002a9749b
STACK_TEXT:
fffff880`05848ae0 fffff880`043472ae : fffffa80`00000002 00000000`00000001 00000000`00000002 00000000`00000000 : nt!ExAcquireResourceExclusiveLite+0x3b
fffff880`05848b50 fffff880`0431a2c6 : ffffffff`ff676980 fffffa80`05373010 00000000`00000000 00000000`00000000 : dxgmms1!VidSchiWaitForSchedulerEvents+0x1ee
fffff880`05848bf0 fffff880`04346e7a : 00000000`00000000 fffffa80`05d32d50 00000000`00000080 fffffa80`05373010 : dxgmms1!VidSchiScheduleCommandToRun+0x1da
fffff880`05848d00 fffff800`02d33c06 : 00000000`02017031 fffffa80`05344a10 fffffa80`036e5040 fffffa80`05344a10 : dxgmms1!VidSchiWorkerThread+0xba
fffff880`05848d40 fffff800`02a6dc26 : fffff880`009e7180 fffffa80`05344a10 fffff880`009f1f40 00000000`00000246 : nt!PspSystemThreadStartup+0x5a
fffff880`05848d80 00000000`00000000 : fffff880`05849000 fffff880`05843000 fffff880`05848690 00000000`00000000 : nt!KxStartSystemThread+0x16
SYMBOL_STACK_INDEX: 1
SYMBOL_NAME: dxgmms1!VidSchiWaitForSchedulerEvents+1ee
FOLLOWUP_NAME: MachineOwner
IMAGE_NAME: hardware
DEBUG_FLR_IMAGE_TIMESTAMP: 0
STACK_COMMAND: .cxr 0xfffff88005848110 ; kb
MODULE_NAME: hardware
FAILURE_BUCKET_ID: X64_IP_MISALIGNED
BUCKET_ID: X64_IP_MISALIGNED
Followup: MachineOwner
---------
View attachment Minidump.rar
