BSOD IRLQ_NOT_LESS_OR_EQUAL ntoskrnl.exe

Post it following the Blue Screen of Death (BSOD) Posting Instructions.

The BSOD occurred during scanning with MBAM. Scan the system for possible virus infection with the following programs to be sure that is it not a virus issue.

• Anti-rootkit utility TDSSKiller
• Windows Defender Offline

Make it sure that your SSD is running with the latest firmware.
Download OCZ Toolbox and Firmware Updates

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 memtest 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 Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck A, {48, 2, 1, fffff800030bd939}

Probably caused by : memory_corruption ( nt!MiRestoreTransitionPte+109 )

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

TonyMall said:

I did the memtest and i got 54 error. That means that my Rams have problem?

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:

No code has to be inserted here.
It is a RAM, a bad RAM.

But if you have got a result like that:

No code has to be inserted here.
It is a motherboard issue. The particular slot is bad.

TonyMall said:

Why 7 passes ?
i m asking because in the first pass it says the memory has no error

"I m testing them, i m in the first"

I am failing to understand your question, and it seems to be contradictory with your previous post.

TonyMall said:

I did the memtest and i got 54 error. That means that my Rams have problem?

Not seven, but at least 8 passes, because ......

Britton30 said:

the reason memtest need at least 7-8 full passes is what it's doing. Memtest writes 9 different patterns of random values to RAM and reads it back. IF the read is different than the write, that's an error. Each pass generates a new set on random data, which is why errors may show up later.