Microsoft (R) Windows Debugger Version 6.3.9600.16384 AMD64
Copyright (c) Microsoft Corporation. All rights reserved.
Loading Dump File [C:\Users\YUSRA\Downloads\DRIZZT-Wed_03_04_2015_234628_77\030415-9828-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available
************* Symbol Path validation summary **************
Response Time (ms) Location
Deferred SRV*c:\symbols*http://msdl.microsoft.com/download/symbols
Symbol search path is: SRV*c:\symbols*http://msdl.microsoft.com/download/symbols
Executable search path is:
Windows 7 Kernel Version 7601 (Service Pack 1) MP (4 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 7601.18717.amd64fre.win7sp1_gdr.150113-1808
Machine Name:
Kernel base = 0xfffff800`03050000 PsLoadedModuleList = 0xfffff800`03294890
Debug session time: Thu Mar 5 02:47:36.400 2015 (UTC + 6:00)
System Uptime: 0 days 6:08:10.212
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, {fffff88007b8f000, 2, 0, fffff880103e0242}
*** WARNING: Unable to verify timestamp for Rt64win7.sys
*** ERROR: Module load completed but symbols could not be loaded for Rt64win7.sys
Probably caused by : Rt64win7.sys ( Rt64win7+7b242 )
Followup: MachineOwner
---------
0: 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: fffff88007b8f000, memory referenced
Arg2: 0000000000000002, IRQL
Arg3: 0000000000000000, value 0 = read operation, 1 = write operation
Arg4: fffff880103e0242, address which referenced memory
Debugging Details:
------------------
READ_ADDRESS: GetPointerFromAddress: unable to read from fffff800032fe100
GetUlongFromAddress: unable to read from fffff800032fe1c0
fffff88007b8f000 Nonpaged pool
CURRENT_IRQL: 2
FAULTING_IP:
Rt64win7+7b242
fffff880`103e0242 410fb609 movzx ecx,byte ptr [r9]
CUSTOMER_CRASH_COUNT: 1
DEFAULT_BUCKET_ID: WIN7_DRIVER_FAULT
BUGCHECK_STR: 0xD1
PROCESS_NAME: System
ANALYSIS_VERSION: 6.3.9600.16384 (debuggers(dbg).130821-1623) amd64fre
TRAP_FRAME: fffff8800bc485e0 -- (.trap 0xfffff8800bc485e0)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=0000000000000000 rbx=0000000000000000 rcx=0000000000000000
rdx=0000000016370346 rsi=0000000000000000 rdi=0000000000000000
rip=fffff880103e0242 rsp=fffff8800bc48778 rbp=0000000000001527
r8=0000000000002a4e r9=fffff88007b8f000 r10=0000000000000000
r11=fffff88007b8425a r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0 nv up ei pl nz na po nc
Rt64win7+0x7b242:
fffff880`103e0242 410fb609 movzx ecx,byte ptr [r9] ds:fffff880`07b8f000=??
Resetting default scope
LAST_CONTROL_TRANSFER: from fffff800030c4469 to fffff800030c4ec0
STACK_TEXT:
fffff880`0bc48498 fffff800`030c4469 : 00000000`0000000a fffff880`07b8f000 00000000`00000002 00000000`00000000 : nt!KeBugCheckEx
fffff880`0bc484a0 fffff800`030c30e0 : fffffa80`07edde20 fffff880`0156b0eb fffffa80`07d148d0 00000000`00004a7e : nt!KiBugCheckDispatch+0x69
fffff880`0bc485e0 fffff880`103e0242 : 00000000`00000000 00000000`00003205 00000000`000000fa fffff880`07b84240 : nt!KiPageFault+0x260
fffff880`0bc48778 00000000`00000000 : 00000000`00003205 00000000`000000fa fffff880`07b84240 00000000`00000008 : Rt64win7+0x7b242
STACK_COMMAND: kb
FOLLOWUP_IP:
Rt64win7+7b242
fffff880`103e0242 410fb609 movzx ecx,byte ptr [r9]
SYMBOL_STACK_INDEX: 3
SYMBOL_NAME: Rt64win7+7b242
FOLLOWUP_NAME: MachineOwner
MODULE_NAME: Rt64win7
IMAGE_NAME: Rt64win7.sys
DEBUG_FLR_IMAGE_TIMESTAMP: 4e53b15d
FAILURE_BUCKET_ID: X64_0xD1_Rt64win7+7b242
BUCKET_ID: X64_0xD1_Rt64win7+7b242
ANALYSIS_SOURCE: KM
FAILURE_ID_HASH_STRING: km:x64_0xd1_rt64win7+7b242
FAILURE_ID_HASH: {e4d59a9d-e839-0bbb-3cb6-ffb96cd89dd9}
Followup: MachineOwner
---------
0: kd> lmvm Rt64win7
start end module name
fffff880`10365000 fffff880`103f2000 Rt64win7 T (no symbols)
Loaded symbol image file: Rt64win7.sys
Image path: \SystemRoot\system32\DRIVERS\Rt64win7.sys
Image name: Rt64win7.sys
Timestamp: [B][COLOR="Blue"]Tue Aug 23 19:55:41 2011 (4E53B15D)[/COLOR][/B]
CheckSum: 00097338
ImageSize: 0008D000
Translations: 0000.04b0 0000.04e4 0409.04b0 0409.04e4
