Copy important files to another drive or cloud storage before anything else. If the drive is failing, every restart and scan risks more data loss. If Windows cannot start, see the startup guide.
Work through these checks
0 of 7 complete01Back up your files
This stop code often means the drive returned bad data, so your files may be at risk.
- Copy documents, photos and other important files to an external drive or cloud storage.
- If Windows does not start, connect the drive to another PC, or use a Windows installation USB > Repair your computer > Command Prompt to copy files with copy or robocopy.
Your important files are safe on another device.
If it does not helpContinue with step 2.
02Read the error status from the crash details
Microsoft explains that the error status in the stop code often identifies the cause.
- Open Event Viewer (Win + R, eventvwr.msc) > Windows Logs > System and find the BugCheck event (ID 1001).
- Look at the second value in brackets after 0x0000007a.
- 0xc000009c or 0xc000016a: bad sectors on the drive (step 3). 0xc000009d: loose or faulty cable, or the controller cannot see the drive (step 5). 0xc000000e: hardware failure or incorrect drive configuration. 0xc000009a: lack of system resources.
You know whether the drive, the cable or something else is the likely cause.
If it does not helpIf you cannot find the event, work through the steps in order.
03Check the drive with chkdsk
Microsoft's fix for bad sectors is to let chkdsk find and map them.
- After the crash, Windows may run a disk check automatically at startup; let it finish.
- Otherwise open Terminal (Admin), run chkdsk C: /f /r, answer Y, and restart to start the scan.
- If Windows does not start, run chkdsk C: /r from the recovery Command Prompt (the drive letter may differ there; check with dir).
Chkdsk /r can take hours on large hard drives. Do not interrupt it.
Chkdsk finishes and reports it fixed any problems.
If it does not helpIf chkdsk reports many bad sectors, replace the drive even if Windows works again.
04Check the drive's health
A drive that is wearing out keeps producing read errors until it is replaced.
- Open the drive maker's tool (for example Samsung Magician, WD Dashboard, Crucial Storage Executive) or a S.M.A.R.T. viewer such as CrystalDiskInfo.
- Check the overall health status and the counts of reallocated, pending or uncorrectable sectors and media errors.
The drive reports good health.
If it does not helpIf the health is Caution or Bad, or error counts keep rising, replace the drive and restore your backup.
05Check cables and connections
Microsoft lists defective or loose cabling and a controller that does not see the disk as causes.
- Switch off and unplug the PC.
- For a SATA drive, reseat or replace the SATA data cable and check the power connector.
- For an M.2 NVMe SSD, reseat it in its slot and tighten the screw.
Touch a metal part of the case before handling components.
The drive stays connected and the crashes stop.
If it does not helpIf the drive also disappears in the BIOS from time to time, try another SATA port or M.2 slot.
06Test the memory
Microsoft lists failing RAM as a cause and recommends the manufacturer's memory scanner.
- Run Windows Memory Diagnostic (Win + R, mdsched.exe) > Restart now and check for problems.
- Check the result in Event Viewer > Windows Logs > System, source MemoryDiagnostics-Results.
- Also run your PC maker's hardware diagnostics, if available.
The memory test passes.
If it does not helpIf it reports errors, follow the memory test errors guide on this site.
07Scan for malware and update Windows
Microsoft also lists virus infection, and recommends installing the latest Windows updates.
- Open Windows Security > Virus & threat protection > Scan options > Microsoft Defender Antivirus (offline scan) > Scan now.
- Run Windows Update and install the latest storage and chipset drivers from your PC maker.
No malware is found, and Windows and drivers are up to date.
If it does not helpIf crashes continue with a healthy drive and RAM, have the motherboard checked; Microsoft notes a defective motherboard component can also cause this stop code.
Possible causes
- Bad sectors on the system drive
- A loose or faulty drive cable, or a drive that disconnects
- A failing SSD or hard drive
- Failing RAM
- Malware
Useful Windows tools
These commands open Windows tools. Review changes before applying them.
eventvwr.mscmdsched.exeWas this helpful?
Your progress is saved on this device.