help with BSOD driver_irql_not_ less_or_equal

Themkman

Honorable
Jan 22, 2013
25
0
10,540
hello all

i am having an issue with a sudden BSOD,

I happened suddenly for no reason that i can think of, no new hardware added, I was in the middle of a game and suddenly BSOD, restarted to get another BSOD instantly twice, windows has dumped the files but i do not know how to read them.

can some one assist me with this

ps works fine in safe mode

dump files located here

https://onedrive.live.com/redir?resid=DA74902DF07CB8E!158&authkey=!AIe7rmBmBoqVXnI&ithint=file%2crar

ok all dump files are the same, how can i fix this issue, it looks like its my wifi driver, can i simply delete the driver from c:windows/system32/drivers?




Microsoft (R) Windows Debugger Version 6.12.0002.633 X86
Copyright (c) Microsoft Corporation. All rights reserved.


Loading Dump File [C:\111414-22042-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available

Symbol search path is: SRV*C:\WebSymb*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 Personal
Built by: 7601.18409.amd64fre.win7sp1_gdr.140303-2144
Machine Name:
Kernel base = 0xfffff800`02e08000 PsLoadedModuleList = 0xfffff800`0304b890
Debug session time: Fri Nov 14 10:06:26.310 2014 (UTC + 0:00)
System Uptime: 0 days 0:01:20.419
Loading Kernel Symbols
...............................................................
................................................................
................................
Loading User Symbols
Loading unloaded module list
....
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck D1, {28, 2, 0, fffff88003eb3b53}

Unable to load image \SystemRoot\system32\DRIVERS\netr28x.sys, Win32 error 0n2
*** WARNING: Unable to verify timestamp for netr28x.sys
*** ERROR: Module load completed but symbols could not be loaded for netr28x.sys
Probably caused by : nwifi.sys ( nwifi!Pt6RepackRecvNBL+4ef )

Followup: MachineOwner
---------

3: 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: 0000000000000028, memory referenced
Arg2: 0000000000000002, IRQL
Arg3: 0000000000000000, value 0 = read operation, 1 = write operation
Arg4: fffff88003eb3b53, address which referenced memory

Debugging Details:
------------------


READ_ADDRESS: GetPointerFromAddress: unable to read from fffff800030b5100
0000000000000028

CURRENT_IRQL: 2

FAULTING_IP:
nwifi!Pt6RepackRecvNBL+4ef
fffff880`03eb3b53 448b6328 mov r12d,dword ptr [rbx+28h]

CUSTOMER_CRASH_COUNT: 1

DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT

BUGCHECK_STR: 0xD1

PROCESS_NAME: System

TRAP_FRAME: fffff88002fff3d0 -- (.trap 0xfffff88002fff3d0)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=fffff88002fff5a8 rbx=0000000000000000 rcx=fffffa800faae030
rdx=fffff88002fff5d0 rsi=0000000000000000 rdi=0000000000000000
rip=fffff88003eb3b53 rsp=fffff88002fff560 rbp=0000000000000000
r8=0000000000000000 r9=0000000000000000 r10=fffff88003ee9110
r11=0000000000000003 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0 nv up ei ng nz na po nc
nwifi!Pt6RepackRecvNBL+0x4ef:
fffff880`03eb3b53 448b6328 mov r12d,dword ptr [rbx+28h] ds:5180:00000000`00000028=????????
Resetting default scope

LAST_CONTROL_TRANSFER: from fffff80002e7d169 to fffff80002e7dbc0

STACK_TEXT:
fffff880`02fff288 fffff800`02e7d169 : 00000000`0000000a 00000000`00000028 00000000`00000002 00000000`00000000 : nt!KeBugCheckEx
fffff880`02fff290 fffff800`02e7bde0 : fffffa80`0dcb2876 fffffa80`0da0d000 00000000`00000000 00000000`00000000 : nt!KiBugCheckDispatch+0x69
fffff880`02fff3d0 fffff880`03eb3b53 : fffff800`00000000 00000000`00000000 00000000`71697377 00000000`000007ff : nt!KiPageFault+0x260
fffff880`02fff560 fffff880`03eb4021 : fffffa80`0faae030 00000000`00000000 00000000`00000000 fffffa80`0d682010 : nwifi!Pt6RepackRecvNBL+0x4ef
fffff880`02fff5b0 fffff880`03eb46fc : fffffa80`0d682010 fffff880`05f25029 fffffa80`0d8f4ab0 fffffa80`0d682010 : nwifi!Pt6RepackRecvNBL+0x9bd
fffff880`02fff800 fffff880`01442549 : fffffa80`0dc07c80 00000000`00000000 00000000`00000001 fffffa80`0fac2500 : nwifi!Pt6Receive+0x1a4
fffff880`02fff860 fffff880`014424e0 : fffffa80`0dcac328 fffff880`02de80c7 fffff880`02de9340 fffffa80`0d8f4be8 : ndis!ndisFilterIndicateReceiveNetBufferLists+0x29
fffff880`02fff8a0 fffff880`02de49c0 : fffff880`02deb110 00000000`00000000 00000000`00000001 fffffa80`0dcacd78 : ndis!NdisFIndicateReceiveNetBufferLists+0x50
fffff880`02fff8e0 fffff880`0145b0a7 : fffffa80`0d8721a0 fffffa80`0dc3a800 fffffa80`0dc3a800 00000000`00000001 : vwififlt!FilterReceiveNetBufferLists+0x158
fffff880`02fff940 fffff880`03a22e7b : 00000000`00000000 fffffa80`0dd1bb08 fffffa80`0dcfd000 fffff880`05a4601a : ndis! ?? ::FNODOBFM::`string'+0xcd8f
fffff880`02fff990 00000000`00000000 : fffffa80`0dd1bb08 fffffa80`0dcfd000 fffff880`05a4601a fffffa80`00000002 : netr28x+0x17e7b


STACK_COMMAND: kb

FOLLOWUP_IP:
nwifi!Pt6RepackRecvNBL+4ef
fffff880`03eb3b53 448b6328 mov r12d,dword ptr [rbx+28h]

SYMBOL_STACK_INDEX: 3

SYMBOL_NAME: nwifi!Pt6RepackRecvNBL+4ef

FOLLOWUP_NAME: MachineOwner

MODULE_NAME: nwifi

IMAGE_NAME: nwifi.sys

DEBUG_FLR_IMAGE_TIMESTAMP: 4a5bcc3b

FAILURE_BUCKET_ID: X64_0xD1_nwifi!Pt6RepackRecvNBL+4ef

BUCKET_ID: X64_0xD1_nwifi!Pt6RepackRecvNBL+4ef

Followup: MachineOwner
 
Solution
Hi there.

No, you can't just delete the driver like that from the system32 folder.
Rather, go to your device manager, find the wi-fi unit under network adapters, double click it and uninstall under the drivers tab.
Be sure to have an install file for the drivers on hand, so that you are able to re-install if necessary.
Hi there.

No, you can't just delete the driver like that from the system32 folder.
Rather, go to your device manager, find the wi-fi unit under network adapters, double click it and uninstall under the drivers tab.
Be sure to have an install file for the drivers on hand, so that you are able to re-install if necessary.
 
Solution