Solved Random BSOD's - Bugcheck code: 0xA - Error: IRQL_NOT_LESS_OR_EQUAL

[scottagecheese]

Hey folks,

I'm the victim of at least one daily BSOD crash over the past few weeks. I'm the office guiney pig testing the first 64bit machine introduced onto the network...

I can't seem to identify what single occurance is causing the crashes, as they seem to be triggered by anything from typing and email, to very large graphics in photoshop, to just waking the pc from sleep.

I've attempted to update ever hardware driver I can find on the machine - to no avail. In an effort to remedy the scenario I have recently updated to Win7 pro - 64bt - SP1, and have also recently upgraded the graphics card from the onboard intel hd to an AMD Firepro v3900.

From WhoCrashed and Windbg the offending party appears to be either ntkrnlmp.exe or ntoskrnl.exe, but not sure where to go from here with that information.

Any help greatly appreciated - SF Diagnostics attached...

 

[Arc]

Hi scottagecheese.

The zip contains a stray crash dump only, and it does not contain much more information about the crash.

Test your RAM modules for possible errors.
How to Test and Diagnose RAM Issues with Memtest86+
Run memtest for at least 8 passes, preferably overnight.

If it start showing errors/red lines, stop testing. A single error is enough to determine that something is going bad there.

If it does not show any errors, enable Driver Verifier to monitor the drivers.
Driver Verifier - Enable and Disable
Run Driver Verifier for 24 hours or the occurrence of the next crash, whichever is earlier.

   Information

Why Driver Verifier:
It puts a stress on the drivers, ans so it makes the unstable drivers crash. Hopefully the driver that crashes is recorded in the memory dump.

How Can we know that DV is enabled:
It will make the system bit of slow, laggy.

   Warning

Before enabling DV, make it sure that you have earlier System restore points made in your computer. You can check it easily by using CCleaner looking at Tools > System Restore.

If there is no points, make a System Restore Point manually before enabling DV.

   Tip

• If you fail to get on the Desktop because of DV, Boot into Advanced Boot Options > Safe mode. Disable DV there. Now boot normally again, and try following the instruction of enabling DV again.
• If you cannot boot in Safe mode too, do a System Restore to a point you made earlier.

Let us know the results, with the subsequent crash dumps, if any.

 

[scottagecheese]

memtest results are in...

Thanks for the response ARC.

I ran memtest via usb through the night. 12hrs later it had only processeed 24 of 32gig of ram. None the less two errors were found...see attached screenshot.

I guess following on from link, testing each of the modules in turn is the nest bet???

For pig-iron, I have enabled driver verifier as per your instructions, and am putting the machine through it usual paces. Will report back with further crash dump files if and when another BSOD appears...

 

[Arc]

I guess following on from link, testing each of the modules in turn is the nest bet???

Driver verifier is not needed right now, as memory error is already detected.

Now follow the "Part 3: If You Have Errors:" of How to Test and Diagnose RAM Issues with Memtest86+

Errors/red lines means one or more RAM is faulty. But the fault may occur due to a faulty DIMM slot, too, which is a motherboard component. Using memtest86+, you can discriminate between a faulty RAM and a faulty motherboard.

How? Say you have two RAM sticks and two DIMM slots. You obtained errors at the test with all RAM sticks installed. Now, remove all the sticks but one. Test it in all the available slots, one by one. Continue the same procedure for all the available sticks.
How to make the inference that is it a RAM issue or it is a motherboard issue? Suppose you have got the result like that:

test|Slot1|Slot2
RAM1| Error | Error
RAM2|Good|Good

It is a RAM, a bad RAM.

But if you have got a result like that:

test|Slot1|Slot2
RAM1| Error |Good
RAM2| Error |Good

It is a motherboard issue. The particular slot is bad.

 

[scottagecheese]

Swap the ram - no more BSOD...job done

Thanks again for the help ARC.

Since the machine is barely 2 months old, I sent the results of Memtest on to the PC supplier. The guys have ordered replacement ram modules and in the meantime have supplied 4 new (smaller) modules.

Swapped the ram - no more BSOD. Guess thats problem solved for now.

Thanks again.

 

[Arc]

You are welcome.

Let us know for any further issue.