Bsod: Driver_irql_not_less_or_equal

irGed · 17 May 2014

Hi Everyone,

I am getting a blue screen error of DRIVER_IRQL_NOT_LESS_OR_EQUAL which frequently occur most of the time. I tried to fix it on my own but didn't worked. What I have done so far is to:

- Run a check disk
- Defrag my laptop
- Increase the paging file (recommended amount of the System)

So yeah, I tried all that I know (so far) but still can't fix the issue, can you guys check on this instead?

Thanks!

Arc · 17 May 2014

Hi irGed.

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 error, 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.
__________________________________________

Code:

BugCheck D1, {0, 2, 8, 0}

Probably caused by : ntkrnlmp.exe ( nt!KiPageFault+260 )

Followup: MachineOwner
---------

Code:

BugCheck 50, {fffff8400324b4f0, 8, fffff8400324b4f0, 5}


Could not read faulting driver name
Probably caused by : ntkrnlmp.exe ( nt! ?? ::FNODOBFM::`string'+43801 )

Followup: MachineOwner
---------

irGed · 17 May 2014

Hello Arc,

I have diagnosed the RAM as per suggested over the night and it's clean and no error. The Driver Verifier sounds risky for me for I don't fully understand the instruction.

The applications that are opened when the blue screen appears were these:
- About 3-4 web browser tabs (with Facebook being one of them)
- Skype (Video Call)
- Ragnarok Online
- And a couple of background applications that I can't track

Arc · 18 May 2014

If you follow the post earlier, Driver Verifier will not be any more risky.

It is suggested because it is needed.