Sign in with
Sign up | Sign in
Your question

win7 Drivers_IRQL_not_less_or_equal error, please help?

Last response: in Windows 7
Share
April 21, 2013 11:42:44 AM

So after using whocrashed? It shows me this.

On Sun 21/4/2013 6:27:17 PM GMT your computer crashed
crash dump file: C:\Windows\Minidump\042213-20326-01.dmp
This was probably caused by the following module: netio.sys (0xFFFFF88001625A1D)
Bugcheck code: 0xD1 (0x8, 0x2, 0x0, 0xFFFFF88001625A1D)
Error: DRIVER_IRQL_NOT_LESS_OR_EQUAL
file path: C:\Windows\system32\drivers\netio.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: Network I/O Subsystem
Bug check description: This indicates that a kernel-mode driver attempted to access pageable memory at a process IRQL that was too high.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
The crash took place in a standard Microsoft module. Your system configuration may be incorrect. Possibly this problem is caused by another driver on your system that cannot be identified at this time.



On Sun 21/4/2013 6:27:17 PM GMT your computer crashed
crash dump file: C:\Windows\memory.dmp
This was probably caused by the following module: netio.sys (NETIO!NetioUpdateNetBufferListContext+0xBCD)
Bugcheck code: 0xD1 (0x8, 0x2, 0x0, 0xFFFFF88001625A1D)
Error: DRIVER_IRQL_NOT_LESS_OR_EQUAL
file path: C:\Windows\system32\drivers\netio.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: Network I/O Subsystem
Bug check description: This indicates that a kernel-mode driver attempted to access pageable memory at a process IRQL that was too high.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
The crash took place in a standard Microsoft module. Your system configuration may be incorrect. Possibly this problem is caused by another driver on your system that cannot be identified at this time.

So after checking around, they are all in the Windows folder, does this mean I have to reinstall Windows 7, or its something else I don't get...
a b $ Windows 7
April 21, 2013 11:55:02 AM

Are you using wireless for internet access? If so, try updating your wireless driver.

Mark
m
0
l
a b $ Windows 7
April 22, 2013 6:39:16 AM

Generally, IRQL BSOD's are either drivers are RAM. Given how the same exact driver crashed twice, I'd lean towards drivers for the time being.

Make sure the driver is up to date, and same with your AV/Firewall (might be conflicting somehow).

m
0
l
Related resources
May 20, 2013 8:48:00 AM

Hi Teflin,

Have you modified anything on your computer recently? Did you install new programs or change any settings? Do you know what program was running when you computer rebooted?
I have seen very similar problem earlier when user has used a sort of p2p client.

Regards,
Sanyi
m
0
l
May 20, 2013 10:02:03 AM

BSODs naming NDIS.sys are frequently caused by security software or remnants of old security software left behind.

The most stable security software: MSE + Windows own firewall + MalwareBytes FREE + a sensible user ;) 

Use the correct tools to remove any old security software remnants after they are uninstalled, lists here: http://www.carrona.org/avuninst.html



EDIT: didn't see the date on the OP ...
m
0
l
!