Sign in with
Sign up | Sign in
Your question

Windows 7 Crash, Driver IRQL Not Less or Equal

Tags:
  • Windows 7
  • Computers
  • Crash
Last response: in Windows 7
Share
October 5, 2014 3:19:59 AM

Hi, I've recently been experiencing BSOD crashes on my Windows 7 computer. Following the crash dump and restart my mouse and keyboard become inactive until I restart the computer again.

There hasn't been a great change in my software or hardware for the past few months so I'm at a loss as to what is causing the crash.

I've uploaded a DXdiag of the system here:
https://drive.google.com/file/d/0B6W67H4zpai1YzNVOTFCdC...

And the most recent dmp file
https://drive.google.com/file/d/0B6W67H4zpai1OGNBMzJST1...

More about : windows crash driver irql equal

October 5, 2014 3:24:16 AM

is anything in your system overclocked?
m
0
l
October 5, 2014 3:31:16 AM

I believe the CPU is.
m
0
l
Related resources
October 5, 2014 3:52:48 AM

well then lower you cpu overclock its probably not stable, or run prime 95 for a while if it crashes you know for sure its your overclok
m
0
l
October 5, 2014 5:30:33 AM

cemerian said:
well then lower you cpu overclock its probably not stable, or run prime 95 for a while if it crashes you know for sure its your overclok


So I've run Prime 95 for about 2 hours now. No BSOD. I don't think it's the overclock.
m
0
l
October 5, 2014 12:54:06 PM

then the problem is somewhere else, you can also try using whocrashedme or something similar to see which driver was at fault for the bsod
m
0
l
October 6, 2014 9:08:13 AM

cemerian said:
then the problem is somewhere else, you can also try using whocrashedme or something similar to see which driver was at fault for the bsod


On Sun 05/10/2014 10:16:03 GMT your computer crashed
crash dump file: C:\Windows\Minidump\100514-33711-01.dmp
This was probably caused by the following module: netio.sys (0xFFFFF880046106FD)
Bugcheck code: 0xD1 (0x28, 0x2, 0x0, 0xFFFFF880046106FD)
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 this is the whocrashed analysis. I'm not sure what more to do with it?
m
0
l
October 6, 2014 2:26:35 PM

seems like some program or other driver is interfeering with your network connection, which most likely is causing your bsod, did you instal anything new(drive, program) before this accured? if so uninstall it
m
0
l
!