BSOD - Driver_IRQL_NOT_LESS_OR_EQUAL

axe0 said:

iwannaknow said:

Nope, I'm referring to the Home edition you are already using. When I examine your .dmp file online i find that a driver trying to use an interrupt that is too high.
Someone already suggested that it may be a faulty network driver , if you already know what driver causes the system to crash, then uninstall it.
Next issue chckdsk after a crash, to repair any system issues caused by the crash automatically.
If you know the network card brand, find the appropriate driver with it and install those.
Todays manufacturars provide drivers for their specific hardware.
If you don't know what brand the hardware is, there are many tools available on the internet like Hiron's boot cd, which contain software to identify hardware.

Don't confuse me with the OP

I suggested that it may be a faulty network driver.

There is no need to uninstall a driver when it occurs just 1 time. When Windows reboots after a crash it takes the necessary actions to solve the problem.
Only when there are multiple crashes, it should be considered to remove IRST in my case.

Sorry for the confusion.
With WhoCrashed Home edition I was able to find a possible cause, I checked it on the internet.
This is what I found:

By default, it's fauling NETIO.sys which is the Network I/O Subsystem. This is not the true cause and is being faulted by something else. Usually, in most cases, this occurs frequently in Windows 7 > 8 or 8 > 8.1 updates because of two reasons:
1. Network drivers themselves need to be updated.
or
2 (more common): 3rd party antivirus, firewall software or other software is causing conflicts and or corruption.

iwannaknow said:

Sorry for the confusion.
With WhoCrashed Home edition I was able to find a possible cause, I checked it on the internet.
This is what I found:

By default, it's fauling NETIO.sys which is the Network I/O Subsystem. This is not the true cause and is being faulted by something else. Usually, in most cases, this occurs frequently in Windows 7 > 8 or 8 > 8.1 updates because of two reasons:
1. Network drivers themselves need to be updated.
or
2 (more common): 3rd party antivirus, firewall software or other software is causing conflicts and or corruption.

That is correct, but the NETIO.sys could also be from other hardware components if I am correct.
However, before symbol errors came in 1 of the dumps (could be due to hardware problems), the rtwlane.sys driver was flagged, else I wouldn't know but probably suggested it as a standard thing.

axe0,
According to what you recently wrote, I searched the internet and found this:
http://answers.microsoft.com/en-us/w...6-765b7ffedde5