Microsoft (R) Windows Debugger Version 6.12.0002.633 AMD64
Copyright (c) Microsoft Corporation. All rights reserved.
Loading Dump File [F:\DMP\040111-30466-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 7601 (Service Pack 1) MP (8 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 7601.17514.amd64fre.win7sp1_rtm.101119-1850
Machine Name:
Kernel base = 0xfffff800`03051000 PsLoadedModuleList = 0xfffff800`03296e90
Debug session time: Fri Apr 1 12:07:58.121 2011 (UTC - 4:00)
System Uptime: 2 days 14:49:26.469
Loading Kernel Symbols
...............................................................
................................................................
................................
Loading User Symbols
Loading unloaded module list
.......
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck 1000007E, {ffffffffc0000005, fffff88011d474cd, fffff88004254658, fffff88004253eb0}
Probably caused by : dxgmms1.sys ( dxgmms1!memmove+bd )
Followup: MachineOwner
---------
4: 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: fffff88011d474cd, The address that the exception occurred at
Arg3: fffff88004254658, Exception Record Address
Arg4: fffff88004253eb0, Context Record Address
Debugging Details:
------------------
OVERLAPPED_MODULE: Address regions for 'WUDFRd' and 'WUDFRd.sys' overlap
EXCEPTION_CODE: (NTSTATUS) 0xc0000005 - The instruction at 0x%08lx referenced memory at 0x%08lx. The memory could not be %s.
FAULTING_IP:
dxgmms1!memmove+bd
fffff880`11d474cd 488941e0 mov qword ptr [rcx-20h],rax
EXCEPTION_RECORD: fffff88004254658 -- (.exr 0xfffff88004254658)
ExceptionAddress: fffff88011d474cd (dxgmms1!memmove+0x00000000000000bd)
ExceptionCode: c0000005 (Access violation)
ExceptionFlags: 00000000
NumberParameters: 2
Parameter[0]: 0000000000000000
Parameter[1]: ffffffffffffffff
Attempt to read from address ffffffffffffffff
CONTEXT: fffff88004253eb0 -- (.cxr 0xfffff88004253eb0)
rax=0000000002e3b7c3 rbx=fffffa8008395000 rcx=ff7ff8a017321c80
rdx=008001dff1074348 rsi=0000000000000001 rdi=fffffa8008395d94
rip=fffff88011d474cd rsp=fffff88004254898 rbp=fffffa8005933e10
r8=0000000000000030 r9=0000000000000001 r10=0000000000000000
r11=ff7ff8a017321c60 r12=fffffa8008395238 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0 nv up ei ng nz na pe nc
cs=0010 ss=0018 ds=002b es=002b fs=0053 gs=002b efl=00010282
dxgmms1!memmove+0xbd:
fffff880`11d474cd 488941e0 mov qword ptr [rcx-20h],rax ds:002b:ff7ff8a0`17321c60=????????????????
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 fffff800033020e8
ffffffffffffffff
FOLLOWUP_IP:
dxgmms1!memmove+bd
fffff880`11d474cd 488941e0 mov qword ptr [rcx-20h],rax
BUGCHECK_STR: 0x7E
LAST_CONTROL_TRANSFER: from fffff88011d5d3cb to fffff88011d474cd
STACK_TEXT:
fffff880`04254898 fffff880`11d5d3cb : fffffa80`08382af0 00000000`00000000 fffffa80`0730d000 fffff880`110fc855 : dxgmms1!memmove+0xbd
fffff880`042548a0 fffff880`11d5579d : 00000000`00000000 fffffa80`059a5000 00000000`00000026 00000000`00000000 : dxgmms1!VIDMM_GLOBAL::EndPreparation+0x1a3
fffff880`04254910 fffff880`11d6f65d : fffffa80`00000000 fffff8a0`1736f2d0 fffffa80`00000000 fffffa80`05933e10 : dxgmms1!VIDMM_GLOBAL::PrepareDmaBuffer+0xd09
fffff880`04254ae0 fffff880`11d6f398 : fffff800`00b96080 fffff880`11d6ed00 fffffa80`00000000 fffffa80`00000000 : dxgmms1!VidSchiSubmitRenderCommand+0x241
fffff880`04254cd0 fffff880`11d6ee96 : 00000000`00000000 fffffa80`092ef660 00000000`00000080 fffffa80`08376010 : dxgmms1!VidSchiSubmitQueueCommand+0x50
fffff880`04254d00 fffff800`0336ecce : 00000000`05a7b62d fffffa80`08394b60 fffffa80`05523b30 fffffa80`08394b60 : dxgmms1!VidSchiWorkerThread+0xd6
fffff880`04254d40 fffff800`030c2fe6 : fffff800`03243e80 fffffa80`08394b60 fffff800`03251cc0 fffff880`0141e384 : nt!PspSystemThreadStartup+0x5a
fffff880`04254d80 00000000`00000000 : fffff880`04255000 fffff880`0424f000 fffff880`04254680 00000000`00000000 : nt!KxStartSystemThread+0x16
SYMBOL_STACK_INDEX: 0
SYMBOL_NAME: dxgmms1!memmove+bd
FOLLOWUP_NAME: MachineOwner
MODULE_NAME: dxgmms1
IMAGE_NAME: dxgmms1.sys
DEBUG_FLR_IMAGE_TIMESTAMP: 4ce799c1
STACK_COMMAND: .cxr 0xfffff88004253eb0 ; kb
FAILURE_BUCKET_ID: X64_0x7E_dxgmms1!memmove+bd
BUCKET_ID: X64_0x7E_dxgmms1!memmove+bd
Followup: MachineOwner
---------
