[FONT="Lucida Console"]
Microsoft (R) Windows Debugger Version 6.3.9600.16384 X86
Copyright (c) Microsoft Corporation. All rights reserved.
Loading Dump File [C:\Users\YUSRA\Downloads\Compressed\HAXWELL-PC-Tue_01_13_2015_171754_25\011315-19032-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.18526.amd64fre.win7sp1_gdr.140706-1506
Machine Name:
Kernel base = 0xfffff800`03255000 PsLoadedModuleList = 0xfffff800`03498890
Debug session time: Wed Jan 14 04:09:03.212 2015 (UTC + 6:00)
System Uptime: 0 days 3:21:11.851
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, 1, fffff88001460cbe}
*** WARNING: Unable to verify timestamp for MRVW24C.sys
*** ERROR: Module load completed but symbols could not be loaded for MRVW24C.sys
Probably caused by : MRVW24C.sys ( MRVW24C+104e )
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: 0000000000000001, value 0 = read operation, 1 = write operation
Arg4: fffff88001460cbe, address which referenced memory
Debugging Details:
------------------
WRITE_ADDRESS: GetPointerFromAddress: unable to read from fffff80003502100
GetUlongFromAddress: unable to read from fffff800035021c0
0000000000000000 Nonpaged pool
CURRENT_IRQL: 2
FAULTING_IP:
ndis!NdisFreeNetBuffer+ce
fffff880`01460cbe 4c8902 mov qword ptr [rdx],r8
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) x86fre
DPC_STACK_BASE: FFFFF88002D92FB0
TRAP_FRAME: fffff88002d8b540 -- (.trap 0xfffff88002d8b540)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=0000000000000002 rbx=0000000000000000 rcx=fffffa8016c4df38
rdx=0000000000000000 rsi=0000000000000000 rdi=0000000000000000
rip=fffff88001460cbe rsp=fffff88002d8b6d0 rbp=fffffa8005ed2d80
r8=fffffa8005624a90 r9=0000000000000000 r10=fffffa8003a67a60
r11=fffffa8006a4cbf0 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0 nv up ei ng nz na pe nc
ndis!NdisFreeNetBuffer+0xce:
fffff880`01460cbe 4c8902 mov qword ptr [rdx],r8 ds:00000000`00000000=????????????????
Resetting default scope
LAST_CONTROL_TRANSFER: from fffff800032ca169 to fffff800032cabc0
STACK_TEXT:
fffff880`02d8b3f8 fffff800`032ca169 : 00000000`0000000a 00000000`00000000 00000000`00000002 00000000`00000001 : nt!KeBugCheckEx
fffff880`02d8b400 fffff800`032c8de0 : 00000000`00000000 fffff880`04061fa5 00000000`c000000d 00000000`00000200 : nt!KiBugCheckDispatch+0x69
fffff880`02d8b540 fffff880`01460cbe : fffffa80`07239910 fffff880`04604b62 fffffa80`05ed2a00 00000000`00000200 : nt!KiPageFault+0x260
fffff880`02d8b6d0 fffff880`0690704e : 00000000`00000000 fffffa80`07239910 fffffa80`074d8030 fffff880`01463730 : ndis!NdisFreeNetBuffer+0xce
fffff880`02d8b700 00000000`00000000 : fffffa80`07239910 fffffa80`074d8030 fffff880`01463730 fffffa80`05ea2c40 : MRVW24C+0x104e
STACK_COMMAND: kb
FOLLOWUP_IP:
MRVW24C+104e
fffff880`0690704e ?? ???
SYMBOL_STACK_INDEX: 4
SYMBOL_NAME: MRVW24C+104e
FOLLOWUP_NAME: MachineOwner
MODULE_NAME: MRVW24C
IMAGE_NAME: MRVW24C.sys
DEBUG_FLR_IMAGE_TIMESTAMP: 472551f7
FAILURE_BUCKET_ID: X64_0xD1_MRVW24C+104e
BUCKET_ID: X64_0xD1_MRVW24C+104e
ANALYSIS_SOURCE: KM
FAILURE_ID_HASH_STRING: km:x64_0xd1_mrvw24c+104e
FAILURE_ID_HASH: {e1c4bc54-e905-9070-9e24-a932cfb9a426}
Followup: MachineOwner
---------
2: kd> lmvm MRVW24C
start end module name
fffff880`06906000 fffff880`06959200 MRVW24C T (no symbols)
Loaded symbol image file: MRVW24C.sys
Image path: \SystemRoot\system32\DRIVERS\MRVW24C.sys
Image name: MRVW24C.sys
Timestamp: Mon Oct 29 09:22:31 2007 (472551F7)
CheckSum: 00055C61
ImageSize: 00053200
Translations: 0000.04b0 0000.04e4 0409.04b0 0409.04e4
[/FONT]