When your SSD is crashing games, the symptom is hard to miss: a game freezes for 5 to 15 seconds with the audio stuttering, then either recovers, crashes to desktop with no error, or throws a DirectStorage, disk read error, or “exception on storage device” message. You might also see textures failing to load, long hitches when entering a new area, or Windows briefly showing a “drive not responding” notification. Event Viewer often logs Event ID 153, 154, or 129 at the exact moment of the crash, even if the game itself shows nothing useful.
Do not ignore these crashes as normal game bugs. Repeated freezes and write failures on the same drive can corrupt save files, shader caches, and even the Windows file system, and they often signal thermal throttling, firmware bugs, or early drive failure that gets worse under heavy load. Back up your saves and important data now before you start testing, and work through the fixes below in order. They start with the quickest checks that require no tools and move toward deeper hardware and firmware repairs, and as of 2026 most modern NVMe drives include much better diagnostic tools than older models did, so you can confirm the problem before you replace anything.
Likely Causes
| Cause | How to confirm | Fix difficulty |
|---|---|---|
| Corrupted game files or shader cache on SSD | Only one or two games crash, verify integrity fails or shader cache rebuilds fix it temporarily | Easy |
| Loose SATA cable, loose M.2 screw, or faulty port | Drive disappears in BIOS or Disk Management, Event ID 129 or 154 in Event Viewer | Easy |
| NVMe SSD overheating and throttling | Drive temp exceeds 65-75C under load in HWInfo64 or CrystalDiskInfo, crashes happen after 10+ minutes of play | Easy to Moderate |
| Outdated SSD firmware or chipset/storage driver | Manufacturer toolbox shows firmware update available, Device Manager shows generic Microsoft driver from install date | Moderate |
| Windows PCIe Link State or power saving cutting drive power | Crashes linked to idle-to-load transitions, changing Power Plan to High Performance stops stuttering | Easy |
| File system errors, bad blocks, or failing drive health | CrystalDiskInfo shows Caution or Bad, chkdsk finds errors, S.M.A.R.T. Reallocated Sector Count or Media Errors rising | Moderate to Hard |
Fix 1: Clear Corrupted Game Files and Shader Cache
What causes it
Games that stream assets directly from the SSD, especially Unreal Engine 4/5 titles, keep a compiled shader cache and large pak files on the drive. If a crash interrupted a write or the SSD stuttered during an update, those files can be left partially written. The game then crashes every time it tries to load the corrupted chunk, which looks like an SSD fault but is actually bad data sitting on an otherwise healthy drive.
How to check
Note whether the crash happens in one game or all games. Open Steam and go to Library, right-click the crashing game, select Properties, then Installed Files, and note the install drive letter. For other launchers, check Epic Games Launcher under Library, click the three dots on the game, and select Manage to see the install path. Press Win + R, type eventvwr.msc, go to Windows Logs, then System, and filter for Errors at the exact crash time. If there are no disk errors at the crash moment but the game logs show “Pak file corrupted” or “Failed to read shader,” this fix is likely to help.
What to do
First verify the files. In Steam, use Properties, then Installed Files, then Verify integrity of game files and let it complete without launching the game. In Epic Games Launcher, use the three dots menu and select Verify. Then clear the shader caches. In Windows, go to Settings, then System, then Storage, then Temporary files, check DirectX Shader Cache, and click Remove files. Next, navigate to C:\Users\[YourUser]\AppData\Local\ for the specific game folder, often named after the game or publisher, and delete the ShaderCache or D3DSCache folder. Also delete the game’s own cache inside its install folder if present, typically called cache or shadercache. Restart the PC before launching the game again so it rebuilds shaders cleanly.
How to undo it
This fix does not need to be undone. Verification and cache deletion only remove temporary compiled files that the game will regenerate. If you want to restore a deleted save, check the Recycle Bin or restore from your backup. No system setting is changed.
Fix 2: Reseat the Drive and Replace the Cable or Port
What causes it
A slightly loose M.2 drive, a missing standoff screw, or a worn SATA data or power cable can cause micro-disconnects under vibration or heat. NVMe drives that are not screwed down can flex and lose contact with the slot, while 2.5-inch SATA SSDs are sensitive to cheap or bent cables. Windows sees this as Event ID 129 Device Reset or Event ID 154 I/O failure and the game instantly freezes because its asset stream is cut.
How to check
Shut down the PC and switch off the power supply switch on the back. Open the case and inspect. For a 2.5-inch SATA SSD, wiggle the SATA data cable where it plugs into the drive and motherboard, and check for a loose power connector from the PSU. For an M.2 NVMe drive, check whether the drive is secured with the correct M.2 screw and standoff at the 2280 position and whether the drive sits flat. Power on, press Del or F2 during boot to enter BIOS, go to Storage Information or NVMe Configuration, and confirm the drive is listed consistently across two cold boots. In Windows, press Win + X, select Disk Management, and see if the drive shows as Online without flickering to Offline.
What to do
Power off and unplug again. For SATA, replace the SATA data cable with a new locking-latch cable and move it to a different SATA port on the motherboard, such as from SATA_1 to SATA_3. Reseat the SATA power plug as well. For M.2, unscrew the drive, lift it at a 20-degree angle, remove it, blow out dust with compressed air, reinsert it firmly until the gold contacts are fully hidden, and secure it with the standoff and screw so it does not bow. If your motherboard has a second M.2 slot, test the drive there. Route cables so they do not pull on the drive when the case warms up.
How to undo it
Put the cable or drive back in its original port if the change made no difference. Keep the old cable labeled as suspect and do not reuse it for another drive. No software setting is changed, so no system restore is needed.
Fix 3: Stop NVMe Thermal Throttling
What causes it
NVMe SSDs without a heatsink can easily hit 70 to 80 degrees Celsius during sustained game loads, especially when mounted under a hot graphics card with no airflow. Most controllers throttle performance sharply at 75C to 81C and can drop to a fraction of their speed or temporarily stop responding, which the game engine experiences as a hard stall and crash.
How to check
Install HWInfo64, run Sensors-only, and look under Drive Temperatures for your SSD model. Play the crashing game in windowed mode for 15 minutes and watch the Drive Temperature and Drive Thermal Throttling status. You can also open CrystalDiskInfo and check the Temperature reading and the Health Status. Press Ctrl + Shift + Esc to open Task Manager, go to Performance, then Disk, and watch Active Time hit 100 percent while Read speed collapses right before the freeze. If the drive is above 68C at idle or above 75C under load, heat is a prime suspect.
What to do
Improve cooling before you change software. Remove the M.2 slot cover and ensure any factory thermal pad on the motherboard heatsink has its plastic film removed and makes full contact with the controller and NAND chips. If your board has no M.2 heatsink, install an aftermarket M.2 heatsink with a thermal pad, typically a 1.0 mm to 1.5 mm pad included in the kit. Tighten the heatsink screw finger-tight plus a quarter turn. In your BIOS, go to Monitor or Fan Control and raise the case fan curve so front intake fans run at least 60 to 70 percent when the chipset temperature is above 55C. In Windows, keep at least 15 to 20 percent free space on the drive and avoid covering the drive with GPU power cables that block airflow.
How to undo it
Remove the aftermarket heatsink and reinstall the original slot cover if temperatures do not improve. Reset the fan curve in BIOS to Standard or Silent by selecting Load Optimized Defaults under Exit or by choosing the preset profile. No data is affected.
Fix 4: Update SSD Firmware and Chipset Storage Drivers
What causes it
Early firmware revisions for many NVMe and SATA controllers have known bugs that cause hangs during DirectStorage calls, sleep-wake transitions, or sustained queued reads that games use heavily. The generic Microsoft storahci or stornvme driver that Windows installs can also lack the vendor optimizations and timeout handling that prevent those hangs.
How to check
Identify your exact SSD model. Press Win + X, select Device Manager, expand Disk drives, right-click your SSD, choose Properties, go to Details, and select Hardware Ids to copy the model string. Check the firmware version in the same Properties window under the Details tab by selecting Hardware Ids or in CrystalDiskInfo where Firmware is listed at the top. Visit the manufacturer’s support page for that model and compare your firmware string to the latest listed. In Device Manager, expand Storage controllers and IDE ATA/ATAPI controllers, right-click the controller, choose Properties, then Driver, and note the Driver Provider and Driver Date. If it says Microsoft and the date is over a year old, you are on the generic driver.
What to do
Back up your drive first. Install the official toolbox for your brand, which is Samsung Magician for Samsung, WD Dashboard for Western Digital, Crucial Storage Executive for Crucial and Micron, or Intel Memory and Storage Tool for Intel and Solidigm, and use its Firmware Update section to apply the update. Do not power off during the flash. Next, update the chipset driver. For AMD systems, install the latest AMD Chipset Software from the AMD support site and choose the full package that includes the NVMe and GPIO drivers. For Intel systems, install the Intel Chipset Device Software INF and the Intel Rapid Storage Technology driver if your board uses it. Restart, then verify the firmware version changed in CrystalDiskInfo and that Device Manager now shows AMD or Intel as the provider for the storage controller.
How to undo it
Firmware cannot be reliably downgraded without risk, so only update if a newer version is listed as fixing stability. You can roll back the storage controller driver in Device Manager by right-clicking the controller, selecting Properties, then Driver, then Roll Back Driver, or by uninstalling the chipset package in Settings, then Apps, then Installed apps. Keep your backup until you have tested two or three gaming sessions without crashes.
Fix 5: Disable Aggressive Power Saving That Cuts the SSD
What causes it
Windows power plans and PCI Express Link State Power Management can put the SSD or its PCIe link into a low-power state to save energy. When a game suddenly requests a large asset, the drive must wake, and a slow or failed wake causes a timeout that crashes the game. Symptoms include crashes after alt-tabbing, after a pause screen, or when loading a new level, not just under continuous load.
How to check
Press Win + R, type powercfg.cpl, and press Enter. Note whether Balanced or Power Saver is selected. Click Change plan settings next to the active plan, then Change advanced power settings. Expand PCI Express, then Link State Power Management, and see if it is set to Maximum power savings. Also expand Hard disk, then Turn off hard disk after, and check the value in minutes. In Device Manager, expand Disk drives, right-click your SSD, choose Properties, go to the Policies tab, and see if Enable write caching on the device is checked and Turn off Windows write-cache buffer flushing is checked.
What to do
In the Advanced power settings window, set PCI Express Link State Power Management to Off for both On battery and Plugged in if you are on a desktop. Set Hard disk Turn off hard disk after to Never, or at least 60 minutes. Click Apply, then OK. In Device Manager under the Policies tab, leave Enable write caching on the device checked for performance but uncheck Turn off Windows write-cache buffer flushing, which can cause data loss on a stuttering drive. Click OK. For laptops, create a separate High performance plan for gaming by selecting Create a power plan in powercfg.cpl and switching to it before you play, rather than changing your battery plan permanently.
How to undo it
Return to powercfg.cpl, click Restore default settings for this plan, or reselect Balanced under Preferred plans. In Device Manager, recheck Turn off Windows write-cache buffer flushing if you had it on before. The change is immediate and does not require a reinstall.
Fix 6: Repair the File System and Check for Bad Blocks
What causes it
A corrupt NTFS file system, leftover bad blocks from an improper shutdown, or a disabled TRIM command can make the SSD spend seconds retrying reads that should be instant. The controller marks pages as invalid but never reclaims them, so free space becomes fragmented and write latency spikes during game saves or shader writes.
How to check
Press Win + X, select Terminal (Admin) or Windows PowerShell (Admin), and run the command chkdsk D: /scan where D is your game drive letter. A report of errors or bad clusters indicates file system damage. Then open an elevated Command Prompt and run fsutil behavior query DisableDeleteNotify . A result of DisableDeleteNotify = 0 means TRIM is enabled, while a result of 1 means it is disabled. Finally, run CrystalDiskInfo and look at Health Status and the S.M.A.R.T. attributes for Reallocated Sectors Count, Current Pending Sector Count, or Media and Data Integrity Errors.
What to do
If chkdsk found errors, schedule a full repair. In the same elevated Terminal, run chkdsk D: /f /r /x and press Y when asked to dismount the drive, then restart if it is the OS drive. This can take 30 to 90 minutes on a 1 TB drive. If TRIM was disabled, enable it by running fsutil behavior set DisableDeleteNotify 0 in an elevated prompt, then restart. After that, run a manual TRIM. Go to the Start menu, type Defragment and Optimize Drives, open it, select your SSD, and click Optimize. Do not run a traditional defrag on an SSD. Leave at least 15 to 25 percent free space on the drive, so on a 1 TB drive keep 150 to 250 GB free, and delete or move large unused games to restore that headroom.
How to undo it
File system repairs cannot be undone, but you can revert TRIM by running fsutil behavior set DisableDeleteNotify 1, although there is no reason to disable it on a modern SSD. If the scan made files inaccessible, restore them from your backup or from File History under Settings, then System, then Storage, then Advanced storage settings, then Backup options.
Fix 7: Test Drive Health, Manage Free Space, and Fix the Page File
What causes it
A drive that is nearly full, has a manually limited page file, or is already failing will crash games that need to page memory or stream textures. When the SSD has less than 10 percent free space, the controller has few empty blocks for wear leveling and garbage collection, so latency spikes. A.page file fixed to a small size on a nearly full drive can also fail with out-of-memory errors that look like storage crashes.
How to check
Open File Explorer, click This PC, and check the free space bar under your SSD. Open CrystalDiskInfo and note Health Status, Percentage Used, and Total Host Writes. A Health Status of Caution, Warning, or Bad, or a Percentage Used above 90 percent, indicates the drive is at end of life. Press Win + R, type sysdm.cpl, press Enter, go to Advanced, under Performance click Settings, go to Advanced, under Virtual memory click Change, and see if Automatically manage paging file size for all drives is unchecked and a small Custom size is set. In the same sysdm.cpl window, check whether the page file is placed on the failing drive.
What to do
First free space. Move or uninstall games until the drive has 20 percent free. Empty the Recycle Bin. Next, fix the page file. In sysdm.cpl under Virtual memory, check Automatically manage paging file size for all drives and click Set, then OK, and restart. If you prefer a manual size, set Initial size to 1.5 times your RAM and Maximum size to 3 times your RAM in megabytes, so for 16 GB RAM set 24576 MB initial and 49152 MB maximum, and place it on your fastest healthy drive. Then test health with the manufacturer tool’s Diagnostic Scan or Short Self-Test. If errors persist, clone the drive immediately using the toolbox’s clone feature or Windows Backup under Control Panel, then System and Security, then Backup and Restore, and plan for replacement. Do not continue heavy gaming on a drive showing reallocated sectors that increase after each test.
How to undo it
Revert the page file by returning to sysdm.cpl, Virtual memory, and restoring your previous Custom size values and drive selection, then clicking Set and restarting. Move games back to the drive if space allows. If you cloned to a new drive, you can keep the old drive disconnected as a fallback and reconnect it by powering off and swapping the M.2 or SATA port back.
If Nothing Works
If every fix still ends in a freeze or crash at the same point in a game, you are likely dealing with a hardware-level failure or a platform incompatibility that software toggles cannot solve. Run a final isolation test to be sure. Install the same crashing game on a different physical drive, even a spare SATA SSD or external USB SSD if you have one, and play the same save or level. If it runs cleanly on the second drive, the original SSD is failing even if S.M.A.R.T. still says Good. If it crashes on both drives, the issue is outside the SSD, such as unstable RAM, an unstable CPU or GPU overclock, or a bad motherboard PCIe slot.
At that point, stop writing new data to the suspect drive and back it up. Create a full image with Control Panel, then Backup and Restore, then Create a system image, or use your SSD toolbox clone function. Test system memory with Windows Memory Diagnostic by pressing Win + R, typing mdsched.exe, and choosing Restart now and check for problems. Reset any BIOS overclocks by entering BIOS and selecting Load Optimized Defaults. Try the SSD in another PC or a USB NVMe enclosure to confirm whether the hangs follow the drive. If they do, replace the drive under warranty using the S.M.A.R.T. logs and CrystalDiskInfo screenshots as evidence, and do a clean install of the game on the new drive rather than copying the old corrupted files back.
FAQ
Can an SSD actually cause games to crash to desktop without a blue screen?
Yes. Modern games constantly stream textures, audio, and world data. If the SSD times out for more than a few seconds, the game engine aborts the load and closes. Windows may only log a disk warning in Event Viewer with Event ID 153 for an I/O retry or Event ID 154 for a failed I/O, so there is no blue screen even though storage was the cause. A distinct blue screen with CRITICAL_PROCESS_DIED or KERNEL_DATA_INPAGE_ERROR points even more directly to storage.
Should I defragment my SSD to fix game stutter?
No. Do not run classic defragmentation on an SSD. SSDs do not benefit from defrag because access time is uniform, and it only adds wear. Use the Optimize function in the Defragment and Optimize Drives tool, which sends a TRIM command to the SSD. TRIM tells the controller which blocks are free so it can clean them in the background, which reduces the latency spikes that cause stuttering.
Why do only some games crash while others run fine on the same SSD?
Games differ in how they use the drive. Titles with DirectStorage, large open worlds, or heavy shader compilation issue many small queued reads and writes that expose drive timeouts, while older or smaller games may never stress the same path. A corrupted install or shader cache for one game can also explain why that game alone crashes. Test with a clean install of the problem game on a different drive to separate a game-specific install issue from a true drive failure.
How much free space should I leave on my gaming SSD?
Leave at least 15 to 25 percent of the drive free for reliable performance, which also gives the TRIM and garbage collection routines room to work. On a 1 TB SSD that is 150 to 250 GB free, and on a 2 TB SSD that is 300 to 500 GB free. If you routinely fill the drive past 90 percent, move your least-played games to another drive via Steam’s Settings, then Storage, then Move, or keep the page file on a drive that is not constantly full.
