Windows 7 crashes with DRIVER_IRQL_NOT_LESS_OR_EQUAL error

[manvir]

Hey everyone, I'm new to the forum but I'm hoping you guys can help me out. My computer keeps crashing with the BSOD.
I thought it might have been a glitch but the windows updates didn't resolve the problem.
When I googled the problem it led me to this thread: https://www.w7forums.com/driver_irql_not_less_or_equal-windows-7-crash-t10668.html where the problem was resolved so I'm hoping it'll happen here as well.

I've attached the minidump. Do I need to give any additional information? Sorry I'm new to this.

 

[zigzag3143]

Hey everyone, I'm new to the forum but I'm hoping you guys can help me out. My computer keeps crashing with the BSOD.
I thought it might have been a glitch but the windows updates didn't resolve the problem.
When I googled the problem it led me to this thread: https://www.w7forums.com/driver_irql_not_less_or_equal-windows-7-crash-t10668.html where the problem was resolved so I'm hoping it'll happen here as well.

I've attached the minidump. Do I need to give any additional information? Sorry I'm new to this.

The most recent crashes were related to WN111.sys Device driver for Marvell 802.11n NIC from Marvell Semiconductor, Inc. Your is over 3 years old. I would update with newest.

How To Find Drivers:

- search Google for the name of the driver
- compare the Google results with what's installed on your system to figure out which device/program it belongs to
- visit the web site of the manufacturer of the hardware/program to get the latest drivers (DON'T use Windows Update or the Update driver function of Device Manager).
- if there are difficulties in locating them, post back with questions and someone will try and help you locate the appropriate program.

- - The most common drivers are listed on this page: Driver Reference http://www.carrona.org/dvrref.html
- - Driver manufacturer links are on this page: http://www.carrona.org/drvrdown.html

 

[manvir]

Hey zigzag3143, thanks for the suggestion. I'm going to uninstall the driver and see what happens.

 

[manvir]

I tried uninstalling the driver and it seems to have stopped the DRIVER_IRQL_NOT_LESS_OR_EQUAL BSOD crash, thanks for that, but now something else is crashing.
I'm not able to read what the crash error code is because It flashed too fast, but when I'm just working on my computer it will randomly crash and display the BSOD.

Do you guys have any suggestions? I'm including a new minidump file that I just copied right now.

Hopefully someone can help me, it's getting really frustrating having to save all my work every couple of minutes out of fear that I might lose it all.

 

[zigzag3143]

I tried uninstalling the driver and it seems to have stopped the DRIVER_IRQL_NOT_LESS_OR_EQUAL BSOD crash, thanks for that, but now something else is crashing.
I'm not able to read what the crash error code is because It flashed too fast, but when I'm just working on my computer it will randomly crash and display the BSOD.

Do you guys have any suggestions? I'm including a new minidump file that I just copied right now.

Hopefully someone can help me, it's getting really frustrating having to save all my work every couple of minutes out of fear that I might lose it all.

Memory corruption probably by one of these old drivers

ISODrive.sys    2/10/2009 5:22:07 AM        0x90d75000    0x90d8c000    0x00017000    0x4991473f                        
L1C62x86.sys    4/1/2009 1:07:46 AM        0x92267000    0x92277000    0x00010000    0x49d2f6a2                        
ArcSoftKsUFilter.sys    5/25/2009 4:29:31 AM        0x90ff7000    0x91000000    0x00009000    0x4a1a56eb                        
purendis.sys    6/6/2009 12:32:39 AM        0x8e46f000    0x8e479000    0x0000a000    0x4a29f167                        
pnarp.sys    6/6/2009 2:07:38 AM        0x8e465000    0x8e46f000    0x0000a000    0x4a2a07aa

Please run these two tests to find which.


These were caused by memory corruption. Please run these two tests to verify your memory and find which driver is causing the problem.


1-Memtest.

*Download a copy of Memtest86 and burn the ISO to a CD using Iso Recorder or another ISO burning program. http://www.memtest.org/#downiso

*Boot from the CD, and leave it running for at least 5 or 6 passes.

Just remember, any time Memtest reports errors, it can be either bad RAM or a bad motherboard slot.

Test the sticks individually, and if you find a good one, test it in all slots.



2-Driver verifier

I'd suggest that you first backup your data and then make sure you've got access to another computer so you can contact us if problems arise. Then make a System Restore point (so you can restore the system using the Vista/Win7 Startup Repair feature).

In Windows 7 you can make a Startup Repair disk by going to Start....All Programs...Maintenance...Create a System Repair Disc - with Windows Vista you'll have to use your installation disk or the "Repair your computer" option at the top of the Safe Mode menu .

Then, here's the procedure:
- Go to Start and type in "verifier" (without the quotes) and press Enter
- Select "Create custom settings (for code developers)" and click "Next"
- Select "Select individual settings from a full list" and click "Next"
- Select everything EXCEPT FOR "Low Resource Simulation" and click "Next"
- Select "Select driver names from a list" and click "Next"
Then select all drivers NOT provided by Microsoft and click "Next"
- Select "Finish" on the next page.

Reboot the system and wait for it to crash to the Blue Screen. Continue to use your system normally, and if you know what causes the crash, do that repeatedly. The objective here is to get the system to crash because Driver Verifier is stressing the drivers out. If it doesn't crash for you, then let it run for at least 36 hours of continuous operation (an estimate on my part).

If you can't get into Windows because it crashes too soon, try it in Safe Mode.
If you can't get into Safe Mode, try using System Restore from your installation DVD to set the system back to the previous restore point that you created.

 

[manvir]

Thanks for the help zigzag3143.

My computer rebooted again just a few minutes ago and I was able to read
"BAD_POOL_HEADER" as the BSOD error.
Maybe that'll help narrow down the problem.

I'm going to do what you suggested but I've been so busy with uni that I barely have any off time.
I should be done the bulk of my work by Wednesday so I'll try your diagnostics on Thursday.

Again, thanks for sticking around and helping.

 

[manvir]

My computer just crashed again and this time a "BAD_POOL_CALLER" error came up.

Now I'm thinking maybe this was the error last time as well instead of
BAD_POOL_HEADER. I might have just seen as quick glimpse and jumped the gun.
Or it could be both at separate times, I'm not sure, sorry.

I've included a new minidump for troubleshooting. Thanks.

 

[zigzag3143]

You obviously need to run memtest and driver verifier.


Also you still have these old drivers that need updating

ISODrive.sys    2/10/2009 5:22:07 AM        0x900ef000    0x90106000    0x00017000    0x4991473f                        
L1C62x86.sys    4/1/2009 1:07:46 AM        0x9226a000    0x9227a000    0x00010000    0x49d2f6a2

And AVG should be removed and replaced with Microsoft Security Essentials (thanks Elmer)

http://www.avg.com/ww-en/utilities

or


http://www.microsoft.com/security_essentials/

 

[manvir]

Hey zigzag3143,

I uninstalled ISODrive, updated my network adapter driver, uninstalled AVG and installed
MSE. Everything seems to be working fine now. I haven't had a crash since.
Thank you so much for you help.

 

[zigzag3143]

Hey zigzag3143,

I uninstalled ISODrive, updated my network adapter driver, uninstalled AVG and installed
MSE. Everything seems to be working fine now. I haven't had a crash since.
Thank you so much for you help.

My pleasure and good luck

 

[manvir]

Once again...

I thought the problem was fixed but apparently not.
It started crashing again a few days ago. I hope you guys can help.
I've attached the minidump as well.

 

[zigzag3143]

I thought the problem was fixed but apparently not.
It started crashing again a few days ago. I hope you guys can help.
I've attached the minidump as well.

These crashes were caused by memory corruption (probably a driver). Please run these two tests to verify your memory and find which driver is causing the problem.

If you are overclocking anything reset to default before running these tests.
In other words STOP!!!


1-Memtest.

*Download a copy of Memtest86 and burn the ISO to a CD using Iso Recorder or another ISO burning program. Memtest86+ - Advanced Memory Diagnostic Tool

*Boot from the CD, and leave it running for at least 5 or 6 passes.

Just remember, any time Memtest reports errors, it can be either bad RAM or a bad motherboard slot.

Test the sticks individually, and if you find a good one, test it in all slots.

Any errors are indicative of a memory problem.

If a known good stick fails in a motherboard slot it is probably the slot.

http://www.sevenforums.com/tutorials/105647-ram-test-memtest86.html



2-Driver verifier

I'd suggest that you first backup your data and then make sure you've got access to another computer so you can contact us if problems arise. Then make a System Restore point (so you can restore the system using the Vista/Win7 Startup Repair feature).

In Windows 7 you can make a Startup Repair disk by going to Start....All Programs...Maintenance...Create a System Repair Disc - with Windows Vista you'll have to use your installation disk or the "Repair your computer" option at the top of the Safe Mode menu .

Then, here's the procedure:
- Go to Start and type in "verifier" (without the quotes) and press Enter
- Select "Create custom settings (for code developers)" and click "Next"
- Select "Select individual settings from a full list" and click "Next"
- Select everything EXCEPT FOR "Low Resource Simulation" and click "Next"
- Select "Select driver names from a list" and click "Next"
Then select all drivers NOT provided by Microsoft and click "Next"
- Select "Finish" on the next page.

Reboot the system and wait for it to crash to the Blue Screen. Continue to use your system normally, and if you know what causes the crash, do that repeatedly. The objective here is to get the system to crash because Driver Verifier is stressing the drivers out. If it doesn't crash for you, then let it run for at least 36 hours of continuous operation (an estimate on my part).

If you can't get into Windows because it crashes too soon, try it in Safe Mode.
If you can't get into Safe Mode, try using System Restore from your installation DVD to set the system back to the previous restore point that you created.

http://www.sevenforums.com/tutorials/101379-driver-verifier-enable-disable.html


Further Reading
Using Driver Verifier to identify issues with Windows drivers for advanced users