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\110110-31371-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 (2 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 7600.16385.amd64fre.win7_rtm.090713-1255
Machine Name:
Kernel base = 0xfffff800`02c57000 PsLoadedModuleList = 0xfffff800`02e94e50
Debug session time: Mon Nov 1 12:18:33.913 2010 (GMT-4)
System Uptime: 0 days 0:00:28.583
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, {fffffa7fd07c9408, 2, 1, fffff88000ddd106}
Unable to load image \SystemRoot\system32\DRIVERS\nvstor.sys, Win32 error 0n2
*** WARNING: Unable to verify timestamp for nvstor.sys
*** ERROR: Module load completed but symbols could not be loaded for nvstor.sys
Probably caused by : nvstor.sys ( nvstor+b106 )
Followup: MachineOwner
---------
1: 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: fffffa7fd07c9408, memory referenced
Arg2: 0000000000000002, IRQL
Arg3: 0000000000000001, value 0 = read operation, 1 = write operation
Arg4: fffff88000ddd106, address which referenced memory
Debugging Details:
------------------
WRITE_ADDRESS: GetPointerFromAddress: unable to read from fffff80002eff0e0
fffffa7fd07c9408
CURRENT_IRQL: 2
FAULTING_IP:
nvstor+b106
fffff880`00ddd106 89bb88000000 mov dword ptr [rbx+88h],edi
CUSTOMER_CRASH_COUNT: 1
DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT
BUGCHECK_STR: 0xD1
PROCESS_NAME: AvastSvc.exe
TRAP_FRAME: fffff880026c3840 -- (.trap 0xfffff880026c3840)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=0000000000000001 rbx=0000000000000000 rcx=0000000000002231
rdx=0000000000000001 rsi=0000000000000000 rdi=0000000000000000
rip=fffff88000ddd106 rsp=fffff880026c39d0 rbp=fffffa800282d000
r8=fffffa80028193c0 r9=fffffa8002819380 r10=0000000000000040
r11=fffffa800282d000 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0 nv up ei ng nz na po nc
nvstor+0xb106:
fffff880`00ddd106 89bb88000000 mov dword ptr [rbx+88h],edi ds:0001:00000000`00000088=????????
Resetting default scope
LAST_CONTROL_TRANSFER: from fffff80002cc8469 to fffff80002cc8f00
STACK_TEXT:
fffff880`026c36f8 fffff800`02cc8469 : 00000000`0000000a fffffa7f`d07c9408 00000000`00000002 00000000`00000001 : nt!KeBugCheckEx
fffff880`026c3700 fffff800`02cc70e0 : 0000000c`00000040 fffffa80`02819380 00000000`00000004 00000400`00000400 : nt!KiBugCheckDispatch+0x69
fffff880`026c3840 fffff880`00ddd106 : fffffa80`02819380 fffffa80`0282d000 00000000`00000001 fffffa80`027081b0 : nt!KiPageFault+0x260
fffff880`026c39d0 fffffa80`02819380 : fffffa80`0282d000 00000000`00000001 fffffa80`027081b0 fffffa80`02819380 : nvstor+0xb106
fffff880`026c39d8 fffffa80`0282d000 : 00000000`00000001 fffffa80`027081b0 fffffa80`02819380 fffff880`00dea899 : 0xfffffa80`02819380
fffff880`026c39e0 00000000`00000001 : fffffa80`027081b0 fffffa80`02819380 fffff880`00dea899 00000000`00000000 : 0xfffffa80`0282d000
fffff880`026c39e8 fffffa80`027081b0 : fffffa80`02819380 fffff880`00dea899 00000000`00000000 fffffa80`0282d000 : 0x1
fffff880`026c39f0 fffffa80`02819380 : fffff880`00dea899 00000000`00000000 fffffa80`0282d000 fffffa80`030d9f80 : 0xfffffa80`027081b0
fffff880`026c39f8 fffff880`00dea899 : 00000000`00000000 fffffa80`0282d000 fffffa80`030d9f80 00000000`0000000b : 0xfffffa80`02819380
fffff880`026c3a00 00000000`00000000 : fffffa80`0282d000 fffffa80`030d9f80 00000000`0000000b fffffa80`0282d000 : nvstor+0x18899
STACK_COMMAND: kb
FOLLOWUP_IP:
nvstor+b106
fffff880`00ddd106 89bb88000000 mov dword ptr [rbx+88h],edi
SYMBOL_STACK_INDEX: 3
SYMBOL_NAME: nvstor+b106
FOLLOWUP_NAME: MachineOwner
MODULE_NAME: nvstor
IMAGE_NAME: nvstor.sys
DEBUG_FLR_IMAGE_TIMESTAMP: 4a13a711
FAILURE_BUCKET_ID: X64_0xD1_nvstor+b106
BUCKET_ID: X64_0xD1_nvstor+b106
Followup: MachineOwner
---------