Share via

IRQL_NOT_LESS_OR_EQUAL Blue Screens won't stop happening

Anonymous
2025-01-15T12:32:46+00:00

Hello! I've been having a ton of issues going back about 3 months with IRQL blue screens. Initially my GPU driver was the cause, and after that was fixed it was the network card, so that was also resolved. Everything worked great for a little over a month when they started happening again. Last week I completely disabled the onboard network card (in Windows and BIOS) and installed a non-onboard network card, installed the drivers from the manufacturers website, and thought I was finally in the clear, but that wasn't the case.

According to WhoCrashed (assuming I was reading it correctly), the culprit was NoxPlayer, so I uninstalled that and tried Memu. Then I got another blue screen saying Memu was the issue, but I can't figure out how to update the specific drivers that WhoCrashed is pointing out as the problem, and I'm starting to think that might not be the issue given the long thread of issues I've been having. It's getting to the point where I'm ready to just reinstall Windows entirely and hope that fixes it, because something different seems to keep breaking each time.

I've run MemTest86 with no errors, I've done all the SFC and DISM scans recommended in other similar threads to this. All of my drivers are updated and I don't overclock, and Windows is also up to date. I just can't figure this out. The three most recent crash dumps are below. Thank you and please let me know if there's anything else that's needed on my end!

https://files.catbox.moe/wlgov1.dmp - Prior to disabling the onboard network card

https://files.catbox.moe/mfjsju.dmp - After the new network card was installed https://files.catbox.moe/h8yy1s.dmp - From last night

Windows for home | Windows 11 | 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

20 answers

Sort by: Most helpful
Most helpful Newest Oldest
  1. DaveM121 885K Reputation points Independent Advisor
    2025-01-15T14:06:28+00:00

    Did you perform a System Restore, or use the two commands I provided to disable Driver Verifier?

    Was this answer helpful?

    0 comments
  2. Anonymous
    2025-01-15T14:05:28+00:00

    I set up verifier, and it was blue screening before Windows would even boot up fully. I did that 3 times, got into recovery mode, and got my desktop back up and running, but when I went to get the new dump files there was nothing there. They normally appear in C:\Windows\Minidump. Would these be in a different location, or do I need to try verifier again?

    Was this answer helpful?

    0 comments
  3. DaveM121 885K Reputation points Independent Advisor
    2025-01-15T14:01:02+00:00

    Glad to help!

    Was this answer helpful?

    0 comments
  4. Anonymous
    2025-01-15T13:28:24+00:00

    Thank you! Just about to start driver verifier now. I'll post the new dumps when I get them.

    Was this answer helpful?

    0 comments
  5. DaveM121 885K Reputation points Independent Advisor
    2025-01-15T13:10:01+00:00

    Hi, I am Dave, I will help you with this.

    Your minidump files do only indicate virtual drivers associated to the NOX and Memu emulators as the cause of your system crashes, there is no other contributory factor to the crashes listed.

    To try to force Windows to 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