Loading Dump File [D:\ DOWNLOADS\ DUMPS\Turbz\020411-25428-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available
Symbol search path is: SRV*C:\XSymCache*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.16617.amd64fre.win7_gdr.100618-1621
Machine Name:
Kernel base = 0xfffff800`02a05000 PsLoadedModuleList = 0xfffff800`02c42e50
Debug session time: Fri Feb 4 05:39:32.075 2011 (UTC + 0:00)
System Uptime: 0 days 5:06:36.760
Loading Kernel Symbols
...............................................................
................................................................
........................................................
Loading User Symbols
Loading unloaded module list
..........................
Unable to load image \SystemRoot\system32\DRIVERS\nvlddmkm.sys, Win32 error 0n2
*** WARNING: Unable to verify timestamp for nvlddmkm.sys
*** ERROR: Module load completed but symbols could not be loaded for nvlddmkm.sys
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck 1000007E, {ffffffffc0000005, fffff88010581d02, fffff88003005b98, fffff88003005400}
Probably caused by : nvlddmkm.sys ( nvlddmkm+531d02 )
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: fffff88010581d02, The address that the exception occurred at
Arg3: fffff88003005b98, Exception Record Address
Arg4: fffff88003005400, Context Record Address
Debugging Details:
------------------
OVERLAPPED_MODULE: Address regions for 'nvlddmkm' and 'nvlddmkm.sys' overlap
EXCEPTION_CODE: (NTSTATUS) 0xc0000005 - The instruction at 0x%08lx referenced memory at 0x%08lx. The memory could not be %s.
FAULTING_IP:
nvlddmkm+531d02
fffff880`10581d02 8b4cd010 mov ecx,dword ptr [rax+rdx*8+10h]
EXCEPTION_RECORD: fffff88003005b98 -- (.exr 0xfffff88003005b98)
ExceptionAddress: fffff88010581d02 (nvlddmkm+0x0000000000531d02)
ExceptionCode: c0000005 (Access violation)
ExceptionFlags: 00000000
NumberParameters: 2
Parameter[0]: 0000000000000000
Parameter[1]: 0000000000000010
Attempt to read from address 0000000000000010
CONTEXT: fffff88003005400 -- (.cxr 0xfffff88003005400)
rax=0000000000000000 rbx=fffff88003005e50 rcx=0000000000000000
rdx=0000000000000000 rsi=fffff88003005e80 rdi=fffffa8007472100
rip=fffff88010581d02 rsp=fffff88003005dd0 rbp=fffffa800b4aa000
r8=fffff88003005e50 r9=0000000000000000 r10=0000000000000001
r11=0000000000e296e4 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=fffffa80097d9908
iopl=0 nv up ei ng nz na po nc
cs=0010 ss=0018 ds=002b es=002b fs=0053 gs=002b efl=00010286
nvlddmkm+0x531d02:
fffff880`10581d02 8b4cd010 mov ecx,dword ptr [rax+rdx*8+10h] ds:002b:00000000`00000010=????????
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: 0000000000000010
READ_ADDRESS: GetPointerFromAddress: unable to read from fffff80002cad0e0
0000000000000010
FOLLOWUP_IP:
nvlddmkm+531d02
fffff880`10581d02 8b4cd010 mov ecx,dword ptr [rax+rdx*8+10h]
BUGCHECK_STR: 0x7E
DEFAULT_BUCKET_ID: NULL_CLASS_PTR_DEREFERENCE
LAST_CONTROL_TRANSFER: from fffffa80097d9908 to fffff88010581d02
STACK_TEXT:
fffff880`03005dd0 fffffa80`097d9908 : fffff880`03005e50 00000000`00000000 00000000`00000000 fffffa80`0b06a000 : nvlddmkm+0x531d02
fffff880`03005dd8 fffff880`03005e50 : 00000000`00000000 00000000`00000000 fffffa80`0b06a000 fffff880`10501e4a : 0xfffffa80`097d9908
fffff880`03005de0 00000000`00000000 : 00000000`00000000 fffffa80`0b06a000 fffff880`10501e4a 00000000`00000000 : 0xfffff880`03005e50
SYMBOL_STACK_INDEX: 0
SYMBOL_NAME: nvlddmkm+531d02
FOLLOWUP_NAME: MachineOwner
MODULE_NAME: nvlddmkm
IMAGE_NAME: nvlddmkm.sys
DEBUG_FLR_IMAGE_TIMESTAMP: 4c282042
STACK_COMMAND: .cxr 0xfffff88003005400 ; kb
FAILURE_BUCKET_ID: X64_0x7E_nvlddmkm+531d02
BUCKET_ID: X64_0x7E_nvlddmkm+531d02
Followup: MachineOwner
