New
#1
BSOD: Driver_IRQL_NOT_LESS_OR_EQUAL
Just bought the laptop for less than 3 weeks, the following are its specs:
Attachment 256356Attachment 256357
It has been giving me blue screens, making me afraid to do homework on it.
I used winDbg to analyze the mini dump file:
Microsoft (R) Windows Debugger Version 6.2.9200.20512 AMD64
Copyright (c) Microsoft Corporation. All rights reserved.
Loading Dump File [C:\Windows\Minidump\022113-22198-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available
Symbol search path is: SRV*G:\symbols*http://msdl.microsoft.com/download/symbols
Executable search path is:
Windows 7 Kernel Version 7601 (Service Pack 1) MP (8 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 7601.18044.amd64fre.win7sp1_gdr.130104-1431
Machine Name:
Kernel base = 0xfffff800`02e49000 PsLoadedModuleList = 0xfffff800`0308d670
Debug session time: Thu Feb 21 12:10:01.920 2013 (UTC - 5:00)
System Uptime: 0 days 0:18:42.683
Loading Kernel Symbols
...............................................................
................................................................
..........................................
Loading User Symbols
Loading unloaded module list
.....
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck D1, {150076b, 2, 0, fffff88009316ef9}
*** WARNING: Unable to verify timestamp for Netwsw00.sys
*** ERROR: Module load completed but symbols could not be loaded for Netwsw00.sys
Probably caused by : Netwsw00.sys ( Netwsw00+9fef9 )
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: 000000000150076b, memory referenced
Arg2: 0000000000000002, IRQL
Arg3: 0000000000000000, value 0 = read operation, 1 = write operation
Arg4: fffff88009316ef9, address which referenced memory
Debugging Details:
------------------
READ_ADDRESS: GetPointerFromAddress: unable to read from fffff800030f7100
GetUlongFromAddress: unable to read from fffff800030f71c0
000000000150076b Nonpaged pool
CURRENT_IRQL: 2
FAULTING_IP:
Netwsw00+9fef9
fffff880`09316ef9 488b4728 mov rax,qword ptr [rdi+28h]
CUSTOMER_CRASH_COUNT: 1
DEFAULT_BUCKET_ID: WIN7_DRIVER_FAULT
BUGCHECK_STR: 0xD1
PROCESS_NAME: System
TAG_NOT_DEFINED_c000000f: FFFFF80000BA2FB0
TRAP_FRAME: fffff80000b9c590 -- (.trap 0xfffff80000b9c590)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=ffff008009d47416 rbx=0000000000000000 rcx=fffffa800a6b17a0
rdx=fffffa800961be20 rsi=0000000000000000 rdi=0000000000000000
rip=fffff88009316ef9 rsp=fffff80000b9c720 rbp=0000000000000000
r8=fffff80000b9c7e8 r9=0000000000000000 r10=fffff88009d42840
r11=0000000000000002 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0 nv up ei pl nz na pe nc
Netwsw00+0x9fef9:
fffff880`09316ef9 488b4728 mov rax,qword ptr [rdi+28h] ds:00000000`00000028=????????????????
Resetting default scope
LAST_CONTROL_TRANSFER: from fffff80002ebe1e9 to fffff80002ebec40
STACK_TEXT:
fffff800`00b9c448 fffff800`02ebe1e9 : 00000000`0000000a 00000000`0150076b 00000000`00000002 00000000`00000000 : nt!KeBugCheckEx
fffff800`00b9c450 fffff800`02ebce60 : 00000000`00000000 00000000`00000000 00000000`00000000 fffffa80`0a6b17a0 : nt!KiBugCheckDispatch+0x69
fffff800`00b9c590 fffff880`09316ef9 : fffffa80`0d9f7c80 fffffa80`0fdbafc8 fffffa80`0d9f7c80 fffffa80`09f90330 : nt!KiPageFault+0x260
fffff800`00b9c720 fffffa80`0d9f7c80 : fffffa80`0fdbafc8 fffffa80`0d9f7c80 fffffa80`09f90330 00000000`00000001 : Netwsw00+0x9fef9
fffff800`00b9c728 fffffa80`0fdbafc8 : fffffa80`0d9f7c80 fffffa80`09f90330 00000000`00000001 00000000`000000d6 : 0xfffffa80`0d9f7c80
fffff800`00b9c730 fffffa80`0d9f7c80 : fffffa80`09f90330 00000000`00000001 00000000`000000d6 00000000`00000000 : 0xfffffa80`0fdbafc8
fffff800`00b9c738 fffffa80`09f90330 : 00000000`00000001 00000000`000000d6 00000000`00000000 fffff880`0928cf00 : 0xfffffa80`0d9f7c80
fffff800`00b9c740 00000000`00000001 : 00000000`000000d6 00000000`00000000 fffff880`0928cf00 00000000`00000030 : 0xfffffa80`09f90330
fffff800`00b9c748 00000000`000000d6 : 00000000`00000000 fffff880`0928cf00 00000000`00000030 ffff0080`09d47416 : 0x1
fffff800`00b9c750 00000000`00000000 : fffff880`0928cf00 00000000`00000030 ffff0080`09d47416 00000000`00000001 : 0xd6
STACK_COMMAND: kb
FOLLOWUP_IP:
Netwsw00+9fef9
fffff880`09316ef9 488b4728 mov rax,qword ptr [rdi+28h]
SYMBOL_STACK_INDEX: 3
SYMBOL_NAME: Netwsw00+9fef9
FOLLOWUP_NAME: MachineOwner
MODULE_NAME: Netwsw00
IMAGE_NAME: Netwsw00.sys
DEBUG_FLR_IMAGE_TIMESTAMP: 50688e44
FAILURE_BUCKET_ID: X64_0xD1_Netwsw00+9fef9
BUCKET_ID: X64_0xD1_Netwsw00+9fef9
Followup: MachineOwner
---------
Your help is very much appreciated!
Last edited by blueScreenMuch; 21 Feb 2013 at 20:48.