irql not less or equal

Anonymous
2024-08-20T07:57:30+00:00

Hello, I had the BSOD Code that says "IRQL_NOT_LESS_OR_EQUAL" And i cant find a solution, i tried reinstall windows

i tried to buy new ram. i literally tried everything, can i get some help?

Windows for home | Windows 10 | Performance and system failures

Locked Question. This question was migrated from the Microsoft Support Community. You can vote on whether it's helpful, but you can't add comments or replies or follow the question.

0 comments

49 answers

Sort by: Newest
Most helpful Newest Oldest
  1. Anonymous
    2024-08-20T09:27:03+00:00

    It was in the MemTest86. So apparently, i runned the program just like you told me, and it was going all good during the test phase, so when it was trying to start verifying himself, i got that error message

    Was this answer helpful?

    0 comments
  2. Deleted

    This answer has been deleted due to a violation of our Code of Conduct. The answer was manually reported or identified through automated detection before action was taken. Please refer to our Code of Conduct for more information.

    Comments have been turned off. Learn more

  3. DaveM121 935.1K Reputation points Independent Advisor
    2024-08-20T09:23:52+00:00

    Where did you get that error, is that setting up the MemTest86 USB?

    Was this answer helpful?

    0 comments
  4. Anonymous
    2024-08-20T09:21:52+00:00

    Hello, i got this image, is it good or bad now? It's fresh RAM that i buyed from a computer shop, and they even tested it.

    Image

    Was this answer helpful?

    0 comments
  5. DaveM121 935.1K Reputation points Independent Advisor
    2024-08-20T08:44:01+00:00

    Your minidump files just indicate RAM corruption as the cause of those crashes.

    1

    Seeing as the BSOD's have survived re-installing Windows, the best option is to download the widely available free utility MemTest86, then run a full 4 pass scan with that to test your RAM for physical errors

    2

    If no RAM errors are found, to try to force Windows 10 show any faulting drivers, the best option would be to turn on Driver Verifier, let your PC crash 3 times, then you must turn off Driver Verifier, and finally, upload any newly created minidump files

    Before you run Driver Verifier, please create a new System Restore Point

    https://answers.microsoft.com/en-us/windows/for...

    Note, if you have any difficulty getting into Windows with Driver Verifier enabled:

    Start your PC, just as Windows attempts to load (spinning dots), press and hold Power Button for 5 - 10 seconds to perform a Hard Shut Down

    Do this twice

    On the third start Windows will boot into the Recovery Environment and from there you can access System Repair, Safe Mode, Command Prompt... etc.

    Go to Troubleshoot - Advanced Option - Startup Settings and click Restart

    Upon restart, press 4 to enter Safe Mode

    Open Command Prompt as Administrator and run these two commands, then restart your PC.

    verifier /reset

    verifier /bootmode resetonbootfail

    Was this answer helpful?

    0 comments