BSOD IRQL_NOT_LESS_OR_EQUAL error 0x0000000a

[MEA707]

Since April 7, I've had this BSOD appear randomly 4 different times. Twice on April 7, once yesterday and once today. Today the crash occurred while I was watching Youtube.

Here is a summary of the BSOD information:

Bug Check String: IRQL_NOT_LESS_OR_EQUAL
Bug Check Code: 0x0000000a
Caused By Driver: ntoskrnl.exe

Here is a summary of my system:

- Windows 7 Professional x64
- Original OS was Windows Vista 32-bit
- Current OS is full retail version
- Computer is 4 years old
- Windows 7 was installed on it 3 years ago

I've attached the requested files.

Thank you in advance for any help.

 

[zigzag3143]

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!!!

* If you have a Raid update its Driver.



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






Driver Verifer

Using Driver Verifier is an iffy proposition.
Most times it'll crash and it'll tell you what the driver is.
But sometimes it'll crash and won't tell you the driver.
Other times it'll crash before you can log in to Windows.
If you can't get to Safe Mode, then you'll have to resort to offline editing of the registry to disable Driver Verifier.

I'd suggest that you first backup your stuff 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"
NOTE: You can use Low Resource Simulation if you'd like.
From my limited experimentation it makes the BSOD's come faster.
- 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.

If you are using win 8 add these
- Concurrency Stress Test
- DDI compliance checking

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

Reboot into Windows (after the crash) and turn off Driver Verifier by going back in and selecting "Delete existing settings" on the first page, then locate and zip up the memory dump file and upload it with your next post.


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.

Thanks to JGriff2 & Usasma.

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

Driver Verifier

Using Driver Verifier (Windows Drivers)

 

[MEA707]

Thanks for your help. For Memtest, can I do the USB boot option instead of the CD?

 

[zigzag3143]

Thanks for your help. For Memtest, can I do the USB boot option instead of the CD?

If your system can boot from USB, absolutely

 

[MEA707]

Thanks for your help. For Memtest, can I do the USB boot option instead of the CD?

If your system can boot from USB, absolutely

Thanks, I will run it overnight since it is a long process. If Memtest does find errors, is it safe to assume that this is due to a hardware failure (either the RAM itself or RAM slot in the motherboard) and not due to any software/driver problem?

 

[MEA707]

I ran Memtest for 8 hours and it did 8 passes identifying 2337 errors. Should I still do the Driver Verifier test or is this indicative of a hardware problem?

If it is hardware, the only thing I can think of is that this is the result of wear and tear after 4 years of use. I didn't do any hardware changes to it since getting in.

Should I try clearing the CMOS before testing the individual DIMMs?

 

[zigzag3143]

I ran Memtest for 8 hours and it did 8 passes identifying 2337 errors. Should I still do the Driver Verifier test or is this indicative of a hardware problem?

If it is hardware, the only thing I can think of is that this is the result of wear and tear after 4 years of use. I didn't do any hardware changes to it since getting in.

Should I try clearing the CMOS before testing the individual DIMMs?

Those errors are either RAM, or mobo slot. Take a known good stick and test each slot with it.

I wouldnt worry about driver verifier