[FONT="Verdana"][SIZE="2"]Microsoft (R) Windows Debugger Version 6.12.0002.633 AMD64
Copyright (c) Microsoft Corporation. All rights reserved.
Loading Dump File [C:\Users\Yusra\Downloads\mOnAr\SF_09-09-2012\090912-17908-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available
Symbol search path is: SRV*C:\SymCache*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.17835.amd64fre.win7sp1_gdr.120503-2030
Machine Name:
Kernel base = 0xfffff800`0304f000 PsLoadedModuleList = 0xfffff800`03293670
Debug session time: Sun Sep 9 19:33:47.819 2012 (UTC + 6:00)
System Uptime: 0 days 2:43:10.504
Loading Kernel Symbols
...............................................................
................................................................
....................................................
Loading User Symbols
Loading unloaded module list
....
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck A, {8, 2, 0, fffff8000300833e}
Unable to load image \SystemRoot\system32\DRIVERS\Rt64win7.sys, Win32 error 0n2
*** WARNING: Unable to verify timestamp for Rt64win7.sys
*** ERROR: Module load completed but symbols could not be loaded for Rt64win7.sys
*** WARNING: Unable to verify timestamp for win32k.sys
*** ERROR: Module load completed but symbols could not be loaded for win32k.sys
Probably caused by : [COLOR="Red"]Rt64win7.sys ( Rt64win7+10bb8 )[/COLOR]
Followup: MachineOwner
---------
0: kd> !analyze -v
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
[COLOR="red"]IRQL_NOT_LESS_OR_EQUAL (a)[/COLOR]
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 a kernel debugger is available get the stack backtrace.
Arguments:
Arg1: 0000000000000008, memory referenced
Arg2: 0000000000000002, IRQL
Arg3: 0000000000000000, bitfield :
bit 0 : value 0 = read operation, 1 = write operation
bit 3 : value 0 = not an execute operation, 1 = execute operation (only on chips which support this level of status)
Arg4: fffff8000300833e, address which referenced memory
Debugging Details:
------------------
READ_ADDRESS: GetPointerFromAddress: unable to read from fffff800032fd100
0000000000000008
CURRENT_IRQL: 2
FAULTING_IP:
hal!HalpDmaFreeMapRegisters+1a
fffff800`0300833e 488b5a08 mov rbx,qword ptr [rdx+8]
CUSTOMER_CRASH_COUNT: 1
DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT
BUGCHECK_STR: 0xA
PROCESS_NAME: System
TRAP_FRAME: fffff880061fc840 -- (.trap 0xfffff880061fc840)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=fffff880061fc970 rbx=0000000000000000 rcx=fffffa80052d6598
rdx=0000000000000000 rsi=0000000000000000 rdi=0000000000000000
rip=fffff8000300833e rsp=fffff880061fc9d0 rbp=0000000000000700
r8=fffff880061fc970 r9=fffff80003032c60 r10=00000000000008a6
r11=0000000000000002 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0 nv up ei pl nz ac po nc
hal!HalpDmaFreeMapRegisters+0x1a:
fffff800`0300833e 488b5a08 mov rbx,qword ptr [rdx+8] ds:00000000`00000008=????????????????
Resetting default scope
LAST_CONTROL_TRANSFER: from fffff800030cd769 to fffff800030ce1c0
STACK_TEXT:
fffff880`061fc6f8 fffff800`030cd769 : 00000000`0000000a 00000000`00000008 00000000`00000002 00000000`00000000 : nt!KeBugCheckEx
fffff880`061fc700 fffff800`030cc3e0 : fffffa80`06607500 fffff880`068bcb5a 00000000`00000000 00000000`00000000 : nt!KiBugCheckDispatch+0x69
fffff880`061fc840 fffff800`0300833e : fffffa80`03e13030 fffffa80`03e13030 fffffa80`058fb010 00000000`00000001 : nt!KiPageFault+0x260
fffff880`061fc9d0 fffff800`0300ab82 : fffffa80`052d6520 00000000`00000000 fffffa80`052d6520 00000000`00000636 : hal!HalpDmaFreeMapRegisters+0x1a
fffff880`061fca00 fffff800`0300a825 : fffffa80`0590b180 00000000`000007e0 00000000`00000000 fffffa80`067f57a0 : hal!IoFreeMapRegisters+0x62
fffff880`061fca70 fffff880`0140d831 : fffffa80`067f56d0 fffffa80`067f55a0 fffffa80`059065a0 fffffa80`03e13030 : hal!HalPutScatterGatherList+0xd5
fffff880`061fcad0 fffff880`06e10bb8 : fffff800`0326b201 fffffa80`059065a0 00000000`00000000 fffff800`0326b201 : ndis!NdisMFreeNetBufferSGList+0x31
fffff880`061fcb10 fffff800`0326b201 : fffffa80`059065a0 00000000`00000000 fffff800`0326b201 00000000`00000000 : Rt64win7+0x10bb8
fffff880`061fcb18 fffffa80`059065a0 : 00000000`00000000 fffff800`0326b201 00000000`00000000 fffff880`061fcc00 : nt!ExpWorkerThreadBalanceManagerPtr+0x1
fffff880`061fcb20 00000000`00000000 : fffff800`0326b201 00000000`00000000 fffff880`061fcc00 00000000`00000001 : 0xfffffa80`059065a0
STACK_COMMAND: kb
FOLLOWUP_IP:
Rt64win7+10bb8
fffff880`06e10bb8 ?? ???
SYMBOL_STACK_INDEX: 7
SYMBOL_NAME: Rt64win7+10bb8
FOLLOWUP_NAME: MachineOwner
MODULE_NAME: Rt64win7
IMAGE_NAME: Rt64win7.sys
DEBUG_FLR_IMAGE_TIMESTAMP: 49a65b0d
FAILURE_BUCKET_ID: X64_0xA_Rt64win7+10bb8
BUCKET_ID: X64_0xA_Rt64win7+10bb8
Followup: MachineOwner
---------
0: kd> lmvm Rt64win7
start end module name
fffff880`06e00000 fffff880`06e32000 Rt64win7 T (no symbols)
Loaded symbol image file: Rt64win7.sys
Image path: \SystemRoot\system32\DRIVERS\Rt64win7.sys
Image name: Rt64win7.sys
Timestamp: [COLOR="red"] Thu Feb 26 15:04:13 2009 (49A65B0D)[/COLOR]
CheckSum: 0002EB30
ImageSize: 00032000
Translations: 0000.04b0 0000.04e4 0409.04b0 0409.04e4[/SIZE][/FONT]
