How to fix BSOD, System Service Exception, Memory Management, IRQL_NOT_LESS_OR_EQUAL

Kazuki 0 Reputation points
2026-09-19T04:38:35.3566667+00:00

I've been getting constant bluescreens weekly or daily for over a month and I've tried everything I can to fix them but I haven't been able to.
Things I've tried:

  • Memory diagnostic
  • SFC /scannow
  • chkdsk
  • reinstalled windows
  • tried moving my ram, and switching it out
  • DISM Restore health cmd
  • Driver Verifier
    Nothing has worked; if I could figure out the root to fix it or what I need to replace that'd be helpful.Screenshot 2026-09-18 073925

Screenshot 2026-09-18 074049

Screenshot 2026-09-18 213604

Haven't done this before so left me know if anything else needs to be provided

Windows for home | Windows 11 | Performance and system failures
0 comments

1 answer

Sort by: Oldest
Most helpful Newest Oldest

  1. AI answer

    2026-09-19T04:38:53.9866667+00:00

    The dump summaries showing ntoskrnl.exe do not identify the real root cause by themselves. For these stop codes, the supported next steps are to focus on drivers, memory test results, recent hardware changes, Device Manager, and Event Viewer.

    Since SFC, DISM, chkdsk, Windows reinstall, and RAM reseating/swapping were already tried, the most relevant next path is:

    1. Update all drivers through Windows Update first
      • Go to Start > Settings > Windows Update > Advanced options.
      • Turn Receive updates for other Microsoft products On.
      • Under Additional options, select Optional updates.
      • Install all optional updates.
      • Go back to Windows Update and select Check for updates.
      • Install all available updates and restart.
    2. If Windows Update does not provide newer drivers, install drivers from the PC or motherboard manufacturer
      • This is specifically recommended when Windows Update has no newer driver or updating through Windows Update does not resolve the problem.
    3. Check the Windows Memory Diagnostic result in Event Viewer
      • Open Run with Windows key + R.
      • Run mdsched.
      • Select Restart now and check for problems (recommended).
      • If the standard test shows no issue, run the test again and press F1, change Test Mix from Standard to Extended, then press F10.
      • After restart and sign-in, if the notification is missed, open Event Viewer.
      • Navigate to Event Viewer (Local) > Application and Services Logs > Microsoft > Windows > MemoryDiagnostics-Results > Debug.
      • Review the entries. Event ID 2001 means no memory errors were detected.
    4. Check Device Manager and Event Viewer for the actual failing device or driver
      • In Device Manager, look for any device with an exclamation mark.
      • Open that device’s properties and review its events.
      • In Event Viewer, check the System log for critical errors in the same time window as the blue screens.
    5. If any hardware was added recently, remove or replace it temporarily
      • General bug check guidance recommends removing or replacing recently added hardware and checking with the manufacturer for patches.
    6. For SYSTEM_SERVICE_EXCEPTION (0x3B) specifically
      • This stop code can be investigated with WinDbg by checking the stack and memory state.
      • Supported commands mentioned for this bug check are !error, kb, lm t n, !memusage, !pte, and !pool.
      • Driver Verifier is also available in Windows and can be started by entering verifier at a command prompt. It adds overhead, so verify the smallest number of drivers possible.
    7. For IRQL_NOT_LESS_OR_EQUAL (0xA) specifically
      • Microsoft guidance states this error is commonly caused by faulty or outdated drivers, memory issues, or hardware problems.
      • That makes driver updates and memory result verification the highest-value next checks.

    Based on the steps already completed, the strongest supported conclusion is:

    • If Extended Windows Memory Diagnostic reports errors, suspect RAM or memory-related hardware.
    • If memory passes and crashes continue after fully updating drivers, suspect a device driver or hardware/firmware issue, and focus on the device flagged in Device Manager or the matching System log events around the crash time.
    AI-generated content may be incorrect. Read our transparency notes for more information.

    Was this answer helpful?

Your answer

Answers can be marked as 'Accepted' by the question author and 'Recommended' by moderators, which helps users know the answer solved the author's problem.