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\101510-17456-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 7600 MP (3 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 7600.16617.amd64fre.win7_gdr.100618-1621
Machine Name:
Kernel base = 0xfffff800`02c4f000 PsLoadedModuleList = 0xfffff800`02e8ce50
Debug session time: Sat Oct 16 01:08:44.371 2010 (GMT-4)
System Uptime: 0 days 3:27:51.792
Loading Kernel Symbols
.
Press ctrl-c (cdb, kd, ntsd) or ctrl-break (windbg) to abort symbol loads that take too long.
Run !sym noisy before .reload to track down problems loading symbols.
..............................................................
................................................................
......................
Loading User Symbols
Loading unloaded module list
.....
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck 50, {fffff88003df0000, 1, fffff88011e981ce, 0}
Unable to load image 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
Could not read faulting driver name
Probably caused by : nvlddmkm.sys ( nvlddmkm+751ce )
Followup: MachineOwner
---------
1: kd> !analyze -v
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
PAGE_FAULT_IN_NONPAGED_AREA (50)
Invalid system memory was referenced. This cannot be protected by try-except,
it must be protected by a Probe. Typically the address is just plain bad or it
is pointing at freed memory.
Arguments:
Arg1: fffff88003df0000, memory referenced.
Arg2: 0000000000000001, value 0 = read operation, 1 = write operation.
Arg3: fffff88011e981ce, If non-zero, the instruction address which referenced the bad memory
address.
Arg4: 0000000000000000, (reserved)
Debugging Details:
------------------
Could not read faulting driver name
WRITE_ADDRESS: GetPointerFromAddress: unable to read from fffff80002ef70e0
fffff88003df0000
FAULTING_IP:
nvlddmkm+751ce
fffff880`11e981ce 42891488 mov dword ptr [rax+r9*4],edx
MM_INTERNAL_CODE: 0
CUSTOMER_CRASH_COUNT: 1
DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT
BUGCHECK_STR: 0x50
PROCESS_NAME: csrss.exe
CURRENT_IRQL: 0
TRAP_FRAME: fffff88003981050 -- (.trap 0xfffff88003981050)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=fffff88003dea000 rbx=0000000000000000 rcx=fffffa80059d9030
rdx=0000000000040084 rsi=0000000000000000 rdi=0000000000000000
rip=fffff88011e981ce rsp=fffff880039811e8 rbp=0000000000000000
r8=0000000000000000 r9=0000000000001800 r10=0000000000000000
r11=fffffa8004fe9000 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0 nv up ei pl zr na po nc
nvlddmkm+0x751ce:
fffff880`11e981ce 42891488 mov dword ptr [rax+r9*4],edx ds:b498:fffff880`03df0000=????????
Resetting default scope
LAST_CONTROL_TRANSFER: from fffff80002d3ff14 to fffff80002cbf740
STACK_TEXT:
fffff880`03980ee8 fffff800`02d3ff14 : 00000000`00000050 fffff880`03df0000 00000000`00000001 fffff880`03981050 : nt!KeBugCheckEx
fffff880`03980ef0 fffff800`02cbd82e : 00000000`00000001 fffffa80`059d9000 00000000`00000000 00000000`00000000 : nt! ?? ::FNODOBFM::`string'+0x42837
fffff880`03981050 fffff880`11e981ce : fffff880`11e9f536 00000000`00000000 fffff880`0474c000 fffff880`009e9180 : nt!KiPageFault+0x16e
fffff880`039811e8 fffff880`11e9f536 : 00000000`00000000 fffff880`0474c000 fffff880`009e9180 00000000`00000000 : nvlddmkm+0x751ce
fffff880`039811f0 00000000`00000000 : fffff880`0474c000 fffff880`009e9180 00000000`00000000 fffff880`0474c000 : nvlddmkm+0x7c536
STACK_COMMAND: kb
FOLLOWUP_IP:
nvlddmkm+751ce
fffff880`11e981ce 42891488 mov dword ptr [rax+r9*4],edx
SYMBOL_STACK_INDEX: 3
SYMBOL_NAME: nvlddmkm+751ce
FOLLOWUP_NAME: MachineOwner
MODULE_NAME: nvlddmkm
IMAGE_NAME: nvlddmkm.sys
DEBUG_FLR_IMAGE_TIMESTAMP: 4c37918e
FAILURE_BUCKET_ID: X64_0x50_nvlddmkm+751ce
BUCKET_ID: X64_0x50_nvlddmkm+751ce
Followup: MachineOwner
---------
1: kd> !analyze -v
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
PAGE_FAULT_IN_NONPAGED_AREA (50)
Invalid system memory was referenced. This cannot be protected by try-except,
it must be protected by a Probe. Typically the address is just plain bad or it
is pointing at freed memory.
Arguments:
Arg1: fffff88003df0000, memory referenced.
Arg2: 0000000000000001, value 0 = read operation, 1 = write operation.
Arg3: fffff88011e981ce, If non-zero, the instruction address which referenced the bad memory
address.
Arg4: 0000000000000000, (reserved)
Debugging Details:
------------------
Could not read faulting driver name
WRITE_ADDRESS: fffff88003df0000
FAULTING_IP:
nvlddmkm+751ce
fffff880`11e981ce 42891488 mov dword ptr [rax+r9*4],edx
MM_INTERNAL_CODE: 0
CUSTOMER_CRASH_COUNT: 1
DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT
BUGCHECK_STR: 0x50
PROCESS_NAME: csrss.exe
CURRENT_IRQL: 0
TRAP_FRAME: fffff88003981050 -- (.trap 0xfffff88003981050)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=fffff88003dea000 rbx=0000000000000000 rcx=fffffa80059d9030
rdx=0000000000040084 rsi=0000000000000000 rdi=0000000000000000
rip=fffff88011e981ce rsp=fffff880039811e8 rbp=0000000000000000
r8=0000000000000000 r9=0000000000001800 r10=0000000000000000
r11=fffffa8004fe9000 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0 nv up ei pl zr na po nc
nvlddmkm+0x751ce:
fffff880`11e981ce 42891488 mov dword ptr [rax+r9*4],edx ds:b498:fffff880`03df0000=????????
Resetting default scope
LAST_CONTROL_TRANSFER: from fffff80002d3ff14 to fffff80002cbf740
STACK_TEXT:
fffff880`03980ee8 fffff800`02d3ff14 : 00000000`00000050 fffff880`03df0000 00000000`00000001 fffff880`03981050 : nt!KeBugCheckEx
fffff880`03980ef0 fffff800`02cbd82e : 00000000`00000001 fffffa80`059d9000 00000000`00000000 00000000`00000000 : nt! ?? ::FNODOBFM::`string'+0x42837
fffff880`03981050 fffff880`11e981ce : fffff880`11e9f536 00000000`00000000 fffff880`0474c000 fffff880`009e9180 : nt!KiPageFault+0x16e
fffff880`039811e8 fffff880`11e9f536 : 00000000`00000000 fffff880`0474c000 fffff880`009e9180 00000000`00000000 : nvlddmkm+0x751ce
fffff880`039811f0 00000000`00000000 : fffff880`0474c000 fffff880`009e9180 00000000`00000000 fffff880`0474c000 : nvlddmkm+0x7c536
STACK_COMMAND: kb
FOLLOWUP_IP:
nvlddmkm+751ce
fffff880`11e981ce 42891488 mov dword ptr [rax+r9*4],edx
SYMBOL_STACK_INDEX: 3
SYMBOL_NAME: nvlddmkm+751ce
FOLLOWUP_NAME: MachineOwner
MODULE_NAME: nvlddmkm
IMAGE_NAME: nvlddmkm.sys
DEBUG_FLR_IMAGE_TIMESTAMP: 4c37918e
FAILURE_BUCKET_ID: X64_0x50_nvlddmkm+751ce
BUCKET_ID: X64_0x50_nvlddmkm+751ce
Followup: MachineOwner
---------