Too many BSOD

Keven Silva 0 Reputation points
2026-09-14T18:09:56.46+00:00

I'm getting a lot of BSODs frequently, and I've already tried everything: I tested both the memory and the SSD using CrystalDiskInfo and MemTest86, and all the tests came back positive. However, I'm still getting random BSODs with various different error codes. Here are some of them:

  • UNEXPECTED_STORE_EXCEPTION
  • MEMORY_MANAGEMENT
  • KERNEL_SECURITY_CHECK_FAILURE
  • PAGE_FAULT_IN_NONPAGED_AREA
  • IRQL_NOT_LESS_OR_EQUAL

I don't know what else I should describe here.

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

2 answers

Sort by: Newest
Most helpful Newest Oldest
  1. David-M 126.1K Reputation points Independent Advisor
    2026-09-14T18:44:43.5133333+00:00

    Hi. I'm David, and I'm happy to help you.

    BSOD issues can have several reasons. It is necessary to investigate.

    Please see if your computer created minidump files.

    These files are in C:\Windows\Minidump.

    (If you don't have a Minidump folder, check if it is in the plural Minidumps.)

    Copy any files you have to your desktop and store them in a ZIP file. Then, upload the ZIP file to the cloud (OneDrive), choose to share it, and get the link.

    Then, post the link to the ZIP file here so I can have a look.

    Looking forward to your reply.

    Was this answer helpful?

  2. AI answer

    2026-09-14T18:10:17.19+00:00

    Since memory and SSD tests already came back clean, the next useful path is to check for a faulty driver, recent hardware change, storage issue, or another hardware problem that basic tests did not catch.

    1. Check Event Viewer for matching critical errors
      • Press Win+R, type eventvwr.msc, and press Enter.
      • Open Windows Logs > System.
      • Look for Critical or Error events that happened at the same time as the BSOD.
      • This can help identify the device or driver involved.
    2. Check Device Manager for driver problems
      • Right-click Start > Device Manager.
      • Look for any device with an exclamation point (!).
      • Open that device’s Properties and review the driver events.
      • Try Update driver. If the crashes started after a driver or device change, try disabling or uninstalling that device.
    3. Run System File Checker
      • Open Command Prompt as Administrator.
      • Run: 
             sfc /scannow
      • This checks for corrupted Windows system files and repairs them.
    4. Run Windows Memory Diagnostics even if MemTest86 passed
      • Search for Windows Memory Diagnostics from Start and open it.
      • Choose to restart and test now, or schedule it for next restart.
      • For a deeper test, press F1, set Test Mix to Extended, then press F10.
      • After the test, memory results can be reviewed in Event Viewer under Application and Services Logs > Microsoft > Windows > MemoryDoagnostics-Results > Debug.
      • Event ID 2001 means no memory errors were detected.
    5. Check for recent hardware changes
      • If any hardware was added recently, remove it temporarily and test again.
      • Random stop codes across different bug checks can be caused by hardware, drivers, or software.
    6. Check free disk space
      • Keep roughly 10% to 15% of the drive free.
      • Windows and apps need free space for swap files and other operations.
    7. Install the latest Windows updates
      • Go to Start > Settings > Update & Security > Windows Update.
      • Select Check for Windows updates.
    8. Run a virus scan
      • Disk corruption and some bug checks can also be caused by malware.
    9. If the crashes continue, consider restore/recovery options
      • Use a system restore point or one of the Windows recovery options.
      • Warning: recovery actions can remove apps, settings, or data depending on the option chosen.

    About the specific stop codes listed:

    • UNEXPECTED_STORE_EXCEPTION: Microsoft recommends checking Event Viewer, Windows Memory Diagnostics, Device Manager, and running sfc /scannow.
    • MEMORY_MANAGEMENT: this indicates a severe memory management error.
    • KERNEL_SECURITY_CHECK_FAILURE: often requires checking recent hardware, drivers, Event Viewer, Device Manager, and malware.
    • Multiple different stop codes with no single pattern can still point to a driver issue or failing hardware even when initial RAM and SSD tests look normal.

    References:

    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.