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.
- 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.
- Press Win+R, type
- 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.
- Run System File Checker
- Open Command Prompt as Administrator.
- Run:
sfc /scannow - This checks for corrupted Windows system files and repairs them.
- 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.
- 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.
- 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.
- Install the latest Windows updates
- Go to Start > Settings > Update & Security > Windows Update.
- Select Check for Windows updates.
- Run a virus scan
- Disk corruption and some bug checks can also be caused by malware.
- 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: