Random BSODs, MEMORY_MANAGEMENT and DRIVER_IRQL_NOT_LESS_OR_EQUAL

rekviem · 15 Aug 2012

I got a MEMORY_MANAGEMENT BSOD while browsing the internet yesterday, then some hours later, while playing a game, I got the DRIVER_IRQL_NOT_LESS_OR_EQUAL one. The next day, I got another MEMORY_MANAGEMENT while watching a video. This is a new system, about 1 month old, so I'm pretty worried about this.

I also noticed that I got some corrupted downloads in the last few days, though that could be a coincidence.

After getting the second BSOD, I left the windows memory test running overnight, doing an extended test. It did two passes and found no errors. Chkdisk found nothing either. I noticed the WMI errors (event ID 10) in the event log around the same time that I got the BSOD and ran the script MS provides to fix it, though from everything I read it was probably a coincidence and unrelated to the BSOD. It did not happen again after I fixed it but it hasn't been long since I ran it.

Other than that, I haven't noticed anything wrong or different. I'd appreciate any advice on this, I need to be prepared in case I need to replace something as I can't afford any downtime

Thanks in advance.

richc46 · 16 Aug 2012

Welcome
Your BSODs reports are pointing toward a driver problem. Driver verifier will help rule out this possiblity or give us a particular driver as the cause.
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/Windows 7 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.
Driver Verifier - Enable and Disable

rekviem · 17 Aug 2012

Hi Richard, thanks a lot for the reply :)

Unfortunately, I didn't get a chance to try the driver verifier because last night I was getting random application errors all the time and even more corrupted downloads, so I decided to buy a CD and give Memtest a try. It only got to test #4 and had already found almost 40,000 errors. Through trial and error I found the stick responsible (and now the PC won't even boot if the functioning stick is removed). Everything has been working fine since I removed it.

Thanks for your time!