BSOD - Driver_IRQL_NOT_LESS_OR_EQUAL

[ralf0615]

So this issue has occurred quite often recently, about once to twice a day; I have reinstalled OS but BSOD still happens. Please help me solve this problem, thanks a ton!

 

[axe0]

Hi ralf0615,

Welcome to the 7forums.

I cannot get much from the dumps.

Please check your device manager for devices that have a yellow exclamation like in the picture below

Please try following

Diagnostic Test

 DRIVER VERIFIER

   Warning

Please make a backup of your important files and get your rescue media or create one.
Please create a restore point.

Please follow this tutorial to run driver verifier.

Some windows drivers are blamed in a few crashes, but that usually means that a 3rd party driver is actually the cause.
Driver verifier stresses your drivers and will crash your pc if any driver fails due to a violation.

Driver verifier should be performed for a max of 48 hours, or when you have a bluescreen, whatever comes first.

If driver verifier has found a violation and you can't get back into windows normally, try to boot into safe mode and reset in safe mode driver verifier, or in the troubleshooting options open command prompt and type verifier /reset.

   Note

Your system will act very sluggishly while driver verifier is enabled, this is normal as your drivers will be being subjected to heavy testing in order to make them crash.

Diagnostic Test

 RAM TEST

Run MemTest86+ to analyse your RAM. ]MemTest86+ - Test RAM - Windows 7 Forums

   Note

MemTest86+ needs to be run for at least 8 passes for conclusive results. Set it running before you go to bed and leave it overnight. We're looking for zero errors here. Even a single error will indicate RAM failure.

 

[ralf0615]

axe0,

Thank you for your reply.

I have installed all the drivers and make sure there is no yellow exclamation mark in Device Manager.

However, shortly after I set up driver verifier, 2 BSOD happened continuously, which all occurred after I open Chrome.

Please see attachment for the two most recent dump file.

 

[axe0]

Please use the tool again and upload the zip file.
The dump files are corrupt.

 

[ralf0615]

Here you are, please let me know if it is readable or not

 

[axe0]

Thank you,

It seems these dumps are also having the same problem.

What I can get from the dumps is 1 driver which is from the NIC.
Please check for driver updates here

0: kd> lmvm rtwlane
start             end                 module name
fffff880`056b2000 fffff880`057d1000   rtwlane    (deferred)             
    Image path: rtwlane.sys
    Image name: [U]rtwlane.sys[/U]
    Timestamp:        [COLOR="Red"][U]Thu Dec 01 03:41:24 2011[/U][/COLOR] (4ED6E954)
    CheckSum:         00116FAE
    ImageSize:        0011F000
    Translations:     0000.04b0 0000.04e4 0409.04b0 0409.04e4

 

[iwannaknow]

What I would do is get the program whocrashed from Resplendence Software - WhoCrashed, automatic crash dump analyzer.
Run the application in save mode (using F8).
It will tell you in detail what driver(s) cause the crash.
Many times it is a driver thing, as I can read in the dump files you provided.

Hope this helps

 

[axe0]

What I would do is get the program whocrashed from Resplendence Software - WhoCrashed, automatic crash dump analyzer.
Run the application in save mode (using F8).
It will tell you in detail what driver(s) cause the crash.
Many times it is a driver thing, as I can read in the dump files you provided.

Hope this helps

Then you can read more then I can :shock:
Could be my internet connection that I cannot read the dumps, because it is sometimes a little slow.

Do you mean the Pro version of WhoCrashed?
I just tried WhoCrashed Home Edition, I had 2 days ago a small crash while booting which I only noticed due to the long time of booting (15s instead of 8-10s). WhoCrashed cannot find a 3rd party driver involved with the home version, but there is a 3rd party driver that caused the crash.

 

[iwannaknow]

BSOD - Driver_IRQL_NOT_LESS_OR_EQUA

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 chkdsk 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.

 

[axe0]

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.

 

[iwannaknow]

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.

 

[axe0]

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.

 

[iwannaknow]

BSOD - Driver_IRQL_NOT_LESS_OR_EQUAL Reply to Thread

axe0,
According to what you recently wrote, I searched the internet and found this:
http://answers.microsoft.com/en-us/...wlanesys/88d628e2-6e00-4b7d-b1e6-765b7ffedde5

 

[axe0]

axe0,
According to what you recently wrote, I searched the internet and found this:
http://answers.microsoft.com/en-us/...wlanesys/88d628e2-6e00-4b7d-b1e6-765b7ffedde5

That comes clear when you look at the files in the zip file