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\102310-31777-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 (4 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS Personal
Built by: 7600.16617.amd64fre.win7_gdr.100618-1621
Machine Name:
Kernel base = 0xfffff800`02c1b000 PsLoadedModuleList = 0xfffff800`02e58e50
Debug session time: Sat Oct 23 07:55:25.565 2010 (GMT-4)
System Uptime: 1 days 1:02:04.752
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 D1, {0, 2, 0, fffff88007439a45}
Unable to load image \SystemRoot\system32\DRIVERS\NETw5s64.sys, Win32 error 0n2
*** WARNING: Unable to verify timestamp for NETw5s64.sys
*** ERROR: Module load completed but symbols could not be loaded for NETw5s64.sys
Probably caused by : NETw5s64.sys ( NETw5s64+13a45 )
Followup: MachineOwner
---------
2: kd> !analyze -v
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
DRIVER_IRQL_NOT_LESS_OR_EQUAL (d1)
An attempt was made to access a pageable (or completely invalid) address at an
interrupt request level (IRQL) that is too high. This is usually
caused by drivers using improper addresses.
If kernel debugger is available get stack backtrace.
Arguments:
Arg1: 0000000000000000, memory referenced
Arg2: 0000000000000002, IRQL
Arg3: 0000000000000000, value 0 = read operation, 1 = write operation
Arg4: fffff88007439a45, address which referenced memory
Debugging Details:
------------------
READ_ADDRESS: GetPointerFromAddress: unable to read from fffff80002ec30e0
0000000000000000
CURRENT_IRQL: 2
FAULTING_IP:
NETw5s64+13a45
fffff880`07439a45 48833b00 cmp qword ptr [rbx],0
CUSTOMER_CRASH_COUNT: 1
DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT
BUGCHECK_STR: 0xD1
PROCESS_NAME: System
TRAP_FRAME: fffff8800318b110 -- (.trap 0xfffff8800318b110)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=0000000000000002 rbx=0000000000000000 rcx=fffffa8007828290
rdx=0000000000000002 rsi=0000000000000000 rdi=0000000000000000
rip=fffff88007439a45 rsp=fffff8800318b2a0 rbp=fffffa80049cc1c0
r8=fffffa80096ee100 r9=0000000000000000 r10=fffff88003163a60
r11=0000000000000002 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0 nv up ei ng nz na pe nc
NETw5s64+0x13a45:
fffff880`07439a45 48833b00 cmp qword ptr [rbx],0 ds:00000000`00000000=????????????????
Resetting default scope
LAST_CONTROL_TRANSFER: from fffff80002c8aca9 to fffff80002c8b740
STACK_TEXT:
fffff880`0318afc8 fffff800`02c8aca9 : 00000000`0000000a 00000000`00000000 00000000`00000002 00000000`00000000 : nt!KeBugCheckEx
fffff880`0318afd0 fffff800`02c89920 : fffffa80`0417ac68 00000000`00000000 00000000`00000000 fffff800`02c931aa : nt!KiBugCheckDispatch+0x69
fffff880`0318b110 fffff880`07439a45 : 00000000`00000004 00000000`00000000 fffffa80`00000002 00000000`00000115 : nt!KiPageFault+0x260
fffff880`0318b2a0 00000000`00000004 : 00000000`00000000 fffffa80`00000002 00000000`00000115 00000000`000000f9 : NETw5s64+0x13a45
fffff880`0318b2a8 00000000`00000000 : fffffa80`00000002 00000000`00000115 00000000`000000f9 fffffa80`0ad16fb0 : 0x4
STACK_COMMAND: kb
FOLLOWUP_IP:
NETw5s64+13a45
fffff880`07439a45 48833b00 cmp qword ptr [rbx],0
SYMBOL_STACK_INDEX: 3
SYMBOL_NAME: NETw5s64+13a45
FOLLOWUP_NAME: MachineOwner
MODULE_NAME: NETw5s64
IMAGE_NAME: NETw5s64.sys
DEBUG_FLR_IMAGE_TIMESTAMP: 4b4df6b9
FAILURE_BUCKET_ID: X64_0xD1_NETw5s64+13a45
BUCKET_ID: X64_0xD1_NETw5s64+13a45
Followup: MachineOwner
---------
2: kd> !analyze -v
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
DRIVER_IRQL_NOT_LESS_OR_EQUAL (d1)
An attempt was made to access a pageable (or completely invalid) address at an
interrupt request level (IRQL) that is too high. This is usually
caused by drivers using improper addresses.
If kernel debugger is available get stack backtrace.
Arguments:
Arg1: 0000000000000000, memory referenced
Arg2: 0000000000000002, IRQL
Arg3: 0000000000000000, value 0 = read operation, 1 = write operation
Arg4: fffff88007439a45, address which referenced memory
Debugging Details:
------------------
READ_ADDRESS: 0000000000000000
CURRENT_IRQL: 2
FAULTING_IP:
NETw5s64+13a45
fffff880`07439a45 48833b00 cmp qword ptr [rbx],0
CUSTOMER_CRASH_COUNT: 1
DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT
BUGCHECK_STR: 0xD1
PROCESS_NAME: System
TRAP_FRAME: fffff8800318b110 -- (.trap 0xfffff8800318b110)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=0000000000000002 rbx=0000000000000000 rcx=fffffa8007828290
rdx=0000000000000002 rsi=0000000000000000 rdi=0000000000000000
rip=fffff88007439a45 rsp=fffff8800318b2a0 rbp=fffffa80049cc1c0
r8=fffffa80096ee100 r9=0000000000000000 r10=fffff88003163a60
r11=0000000000000002 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0 nv up ei ng nz na pe nc
NETw5s64+0x13a45:
fffff880`07439a45 48833b00 cmp qword ptr [rbx],0 ds:00000000`00000000=????????????????
Resetting default scope
LAST_CONTROL_TRANSFER: from fffff80002c8aca9 to fffff80002c8b740
STACK_TEXT:
fffff880`0318afc8 fffff800`02c8aca9 : 00000000`0000000a 00000000`00000000 00000000`00000002 00000000`00000000 : nt!KeBugCheckEx
fffff880`0318afd0 fffff800`02c89920 : fffffa80`0417ac68 00000000`00000000 00000000`00000000 fffff800`02c931aa : nt!KiBugCheckDispatch+0x69
fffff880`0318b110 fffff880`07439a45 : 00000000`00000004 00000000`00000000 fffffa80`00000002 00000000`00000115 : nt!KiPageFault+0x260
fffff880`0318b2a0 00000000`00000004 : 00000000`00000000 fffffa80`00000002 00000000`00000115 00000000`000000f9 : NETw5s64+0x13a45
fffff880`0318b2a8 00000000`00000000 : fffffa80`00000002 00000000`00000115 00000000`000000f9 fffffa80`0ad16fb0 : 0x4
STACK_COMMAND: kb
FOLLOWUP_IP:
NETw5s64+13a45
fffff880`07439a45 48833b00 cmp qword ptr [rbx],0
SYMBOL_STACK_INDEX: 3
SYMBOL_NAME: NETw5s64+13a45
FOLLOWUP_NAME: MachineOwner
MODULE_NAME: NETw5s64
IMAGE_NAME: NETw5s64.sys
DEBUG_FLR_IMAGE_TIMESTAMP: 4b4df6b9
FAILURE_BUCKET_ID: X64_0xD1_NETw5s64+13a45
BUCKET_ID: X64_0xD1_NETw5s64+13a45
Followup: MachineOwner
---------