Microsoft (R) Windows Debugger Version 6.11.0001.404 X86
Copyright (c) Microsoft Corporation. All rights reserved.
Loading Dump File [C:\Users\K\Desktop\Windows_NT6_BSOD_jcgriff2\052311-30092-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;srv*e:\symbols
*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 Personal
Built by: 7601.17592.amd64fre.win7sp1_gdr.110408-1631
Machine Name:
Kernel base = 0xfffff800`03254000 PsLoadedModuleList = 0xfffff800`03499650
Debug session time: Mon May 23 10:16:31.221 2011 (GMT-4)
System Uptime: 0 days 9:13:07.203
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, fffff8800fa1ab9a, fffff88006523d78, fffff880065235d0}
Probably caused by : nvlddmkm.sys ( nvlddmkm+5a2b9a )
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: fffff8800fa1ab9a, The address that the exception occurred at
Arg3: fffff88006523d78, Exception Record Address
Arg4: fffff880065235d0, 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:
nvlddmkm+5a2b9a
fffff880`0fa1ab9a 8901 mov dword ptr [rcx],eax
EXCEPTION_RECORD: fffff88006523d78 -- (.exr 0xfffff88006523d78)
ExceptionAddress: fffff8800fa1ab9a (nvlddmkm+0x00000000005a2b9a)
ExceptionCode: c0000005 (Access violation)
ExceptionFlags: 00000000
NumberParameters: 2
Parameter[0]: 0000000000000001
Parameter[1]: 0000000000000000
Attempt to write to address 0000000000000000
CONTEXT: fffff880065235d0 -- (.cxr 0xfffff880065235d0)
rax=0000000000000000 rbx=fffffa8003cfd000 rcx=0000000000000000
rdx=0000000000003330 rsi=0000000000000006 rdi=fffffa80082c07e0
rip=fffff8800fa1ab9a rsp=fffff88006523fb0 rbp=0000000000000004
r8=0000000000000000 r9=fffffa8007578340 r10=fffff8800fb92a4a
r11=fffffa8008304650 r12=fffffa8008560270 r13=fffffa80082c0010
r14=0000000000000000 r15=0000000000000030
iopl=0 nv up ei ng nz na pe nc
cs=0010 ss=0018 ds=002b es=002b fs=0053 gs=002b efl=00010282
nvlddmkm+0x5a2b9a:
fffff880`0fa1ab9a 8901 mov dword ptr [rcx],eax ds:002b:00000000`00000000=????????
Resetting default scope
CUSTOMER_CRASH_COUNT: 1
DEFAULT_BUCKET_ID: NULL_DEREFERENCE
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: 0000000000000001
EXCEPTION_PARAMETER2: 0000000000000000
WRITE_ADDRESS: GetPointerFromAddress: unable to read from fffff80003503100
0000000000000000
FOLLOWUP_IP:
nvlddmkm+5a2b9a
fffff880`0fa1ab9a 8901 mov dword ptr [rcx],eax
BUGCHECK_STR: 0x7E
LAST_CONTROL_TRANSFER: from fffffa80075ee280 to fffff8800fa1ab9a
STACK_TEXT:
fffff880`06523fb0 fffffa80`075ee280 : fffffa80`03cfd000 00000000`00000000 00000000`00000006 fffff880`06524088 : nvlddmkm+0x5a2b9a
fffff880`06523fb8 fffffa80`03cfd000 : 00000000`00000000 00000000`00000006 fffff880`06524088 00000000`00000040 : 0xfffffa80`075ee280
fffff880`06523fc0 00000000`00000000 : 00000000`00000006 fffff880`06524088 00000000`00000040 fffffa80`0853b430 : 0xfffffa80`03cfd000
SYMBOL_STACK_INDEX: 0
SYMBOL_NAME: nvlddmkm+5a2b9a
FOLLOWUP_NAME: MachineOwner
MODULE_NAME: nvlddmkm
IMAGE_NAME: nvlddmkm.sys
DEBUG_FLR_IMAGE_TIMESTAMP: 4d9e7f64
STACK_COMMAND: .cxr 0xfffff880065235d0 ; kb
FAILURE_BUCKET_ID: X64_0x7E_nvlddmkm+5a2b9a
BUCKET_ID: X64_0x7E_nvlddmkm+5a2b9a
Followup: MachineOwner
---------
