My Windows PC doesn’t crash as often as it did in the Windows 7 era, and I haven’t seen any of those dreaded blue screen of death (BSOD) messages, the one thing you could always count on Windows to deliver, for a long time, except for one after the last feature update.

I went through my usual list of fixes to diagnose the problem and found that the BSOD crash was due to an outdated BIOS. I flashed the latest firmware update, and haven’t seen that error since. However, your PC can crash due to far simpler reasons, and knowing some quick fixes can help you revive your PC without needing professional help.

Check Event Viewer and minidump files

Find out what actually went wrong

When Windows crashes, it leaves logs of the event to help you with troubleshooting. The Event Viewer logs errors and warnings that happened right before the crash, while minidump files contain technical details about what caused the BSOD. You can find Event Viewer by typing it in the Start menu. Navigate to Windows Logs > System and look for critical errors marked with red icons around the time of your crash.

For minidump files, they’re stored in C:\Windows\Minidump, but reading them raw is complicated for untrained eyes. That’s where tools like NirSoft’s BlueScreenView come in handy. It translates those cryptic dump files into readable information, showing you which driver or system file caused the problem.

To illustrate, I used a test crash generated with Microsoft’s NotMyFault utility, which safely triggers a simulated BSOD for diagnostic testing. BlueScreenView correctly identified the cause as myfault.sys, the mock driver used by the tool. In a real scenario, this field would instead list the faulty or misbehaving driver—like nvlddmkm.sys (NVIDIA), rtwlane.sys (Wi-Fi), or dxgmms2.sys (graphics)—helping you pinpoint the exact source of the crash.

Once you know the trigger, be it a driver, hardware issue, or system file corruption, you can try specific fixes instead of trying everything.

If it’s a driver issue, you can update or roll back that specific driver. If a system file has problems, try the built-in repair tools. Hardware failures might need physical inspection or replacement.

Run built-in CLI tools

Let Windows fix itself with DISM and SFC

Based on what you found in the Event Viewer or minidump files, if the issue points to corrupted system files or disk problems, Windows has your back with built-in command-line tools. However, the trick is to run them in the right order: DISM first, then SFC, and finally Check Disk if needed.

1. The first step is to open Command Prompt as an administrator.
2. Then, run DISM with this command: This tool fixes the Windows components that SFC relies on to fix system files, so it’s important that you run it first. It’ll download fresh copies of corrupted files from Microsoft’s servers:

DISM /Online /Cleanup-Image /RestoreHealth

1. Once DISM finishes (usually takes 10-20 minutes), then run the following command to scan and repair protected system files:

sfc /scannow

1. If problems persist, run chkdsk C: /f /r to check your disk for errors. This requires a restart since Windows can’t scan the drive it’s running from.

These commands aren’t just for crashes either. You can also use them when Windows feels sluggish or certain features stop working. Keep these commands saved in a text file on your desktop for quick access, so that you don’t have to go search for them again and again.

Boot into Safe Mode

When Windows won’t cooperate normally

If your computer keeps crashing before you can run any diagnostic tools, or Windows won’t load properly, Safe Mode is a lifesaver. In Safe Mode, Windows runs with only the bare minimum drivers and services, and stops all the other non-essential services that might be causing the crash.

There are many ways to boot into Safe Mode even when Windows won’t boot normally. Power on your PC, and as soon as Windows starts loading, hold the power button to force a shutdown. Do this two or three times, and Windows will trigger its recovery environment. From there, navigate to Troubleshoot -> Advanced options -> Startup Settings -> Restart, then press 4 for Safe Mode (or 5 for Safe Mode with Networking if you need internet access).

Once in Safe Mode, you’ve got a few options. You can uninstall recently installed programs that might be causing conflicts, remove problematic Windows updates through Settings -> Windows Update -> Update history, or roll back driver updates through Device Manager. You can also run DISM and SFC command-line tools, as they often work better in Safe Mode since fewer processes are running. If your PC runs fine in Safe Mode but crashes in normal mode, you know the problem is with a driver, startup program, or service that doesn’t load in Safe Mode.

Check your BIOS and critical drivers

Update the foundation your system runs on

When minidump files don’t point to a specific cause and BSODs happen frequently, it’s time to look deeper at your system’s foundation. Your BIOS (or UEFI) and chipset drivers are essential to the proper functioning of your PC. Outdated or corrupted BIOS or drivers can cause your computer to crash frequently.

Check your BIOS version by typing msinfo32 in the **Start menu **and looking for “BIOS Version/Date.” Compare this with what’s available on your motherboard manufacturer’s website. If there’s a newer version, especially one that mentions stability improvements or compatibility fixes, it’s worth updating. Follow the manufacturer’s instructions exactly, and never interrupt a BIOS update.

For drivers, focus on the critical ones first: chipset, storage controller, and graphics. Device Manager might show everything’s fine, but manufacturers often release updates that Windows Update misses. Download drivers directly from your motherboard or laptop manufacturer’s support page. Buggy USB peripheral drivers can also cause crashes, so disconnect everything non-essential and see if the crashes stop. If they do, reconnect devices one by one to find the troublemaker.

Check your memory and storage for issues

Hardware problems need hardware solutions

Sometimes crashes aren’t about software at all. Failing RAM or a dying storage drive can cause random BSODs. There are always signs that your RAM is about to fail, including crashes during intensive tasks, random application errors, or corrupted files.

Windows has a built-in Memory Diagnostic tool, but I prefer MemTest86 for thorough testing. Create a bootable USB with the tool and let it run overnight. It’ll test each memory stick extensively. If errors show up, test each stick individually to identify the bad one. Even one faulty RAM module can cause system-wide instability.

For storage, sluggish performance beyond normal aging, clicking or grinding sounds from HDDs, frequent file corruption, or problems during file operations all point to drive failure. Run **wmic diskdrive get model status **in the Command Prompt to check drive health quickly. If you see “Pred Fail,” start backing up immediately. Tools like CrystalDiskInfo provide more detailed health monitoring. SSDs fail differently—they might freeze, show write errors, or suddenly become read-only. When a drive starts failing, replacement is the only fix, so keep those backups as fresh as possible.

Recovering from a Windows crash is easier than ever

Microsoft is making recovery from serious Windows boot issues simpler with Quick Machine Recovery, which automatically downloads targeted fixes when widespread problems are detected. They’ve even added automatic memory scans after BSOD crashes, prompting you to check for RAM issues at the next boot.

If the automated solutions don’t work, you still have these classic troubleshooting steps to find and fix the problem. When a PC crashes, follow the clues Windows leaves behind, and then work through these fixes until you find what works.