Photograph the blue screen and note any recent hardware change. This stop code points to hardware more often than most, so start with the hardware steps. If Windows cannot start, see the startup guide.
Work through these checks
0 of 7 complete01Remove recently added hardware
Microsoft says this stop code typically follows installing faulty or mismatched hardware, especially memory.
- If you added RAM, a graphics card, an expansion card or another device before the crashes began, remove it and test.
- If you mixed different RAM kits, test with only the original kit.
- Check that new memory is on your motherboard's supported list.
Switch off and unplug the PC before opening it.
The crashes stop without the new hardware.
If it does not helpIf the new part causes the crash, check its compatibility and BIOS support, or return it.
02Reset overclocks to default
Microsoft names running the CPU above its rated speed as a cause and says to return it to the default clock speed.
- In the BIOS, choose Load optimized defaults, or turn off CPU overclocking and XMP/EXPO memory profiles.
- Uninstall overclocking or tuning tools that apply settings at startup.
- Test with stock settings for a few days.
The PC is stable at default settings.
If it does not helpIf the crashes stop, re-enable settings one at a time; keep the last stable one.
03Test the memory
Microsoft recommends testing all system memory with the Windows memory diagnostic, because memory corruption is a common cause.
- Run Windows Memory Diagnostic (Win + R, mdsched.exe) > Restart now and check for problems.
- After the restart, check Event Viewer > Windows Logs > System, source MemoryDiagnostics-Results.
- On a desktop with several RAM modules, test with one module at a time.
The memory test passes on every module.
If it does not helpIf a module fails, replace it. The memory test errors guide on this site explains the details.
04Remove a new or updated driver
Microsoft recommends removing or replacing a driver that was installed or updated just before the error.
- Roll back recently updated drivers in Device Manager > device Properties > Driver > Roll Back Driver.
- Uninstall recently installed antivirus, backup, encryption or disk tools; their file system filter drivers can overflow the kernel stack, especially when two are installed together.
- If the crash happens at startup, do this in Safe Mode (recovery menu > Troubleshoot > Advanced options > Startup Settings > Restart > 4).
Do not run two real-time antivirus programs at the same time.
Windows runs without the stop code.
If it does not helpBefore a Windows upgrade, Microsoft also advises removing third-party drivers and services and disabling virus scanners.
05Update the BIOS and controller drivers
Microsoft recommends checking for ACPI/BIOS, disk controller and network card updates.
- Install the latest BIOS/UEFI from your PC or motherboard maker.
- Install the latest chipset, storage controller and network drivers for your exact model.
- Run Windows Update.
Do not switch off the PC during a BIOS update.
Firmware and drivers are current and the crashes stop.
If it does not helpCheck BIOS settings after the update; they may be reset.
06Run hardware diagnostics and check the power supply
Microsoft lists failed components, motherboard defects and failing power supplies as causes.
- Run the hardware diagnostics from your PC or laptop maker.
- Check CPU temperatures under load and clean dust from coolers and fans.
- If crashes happen mainly under heavy load, test with a known-good power supply if you can.
Never open a power supply; it can hold dangerous voltage.
You find the failing component, or the hardware tests pass.
If it does not helpReplace components that fail diagnostics, or have the PC checked by a technician.
07Check the trap type in the crash details
The first parameter of the stop code tells which trap occurred, which points toward hardware or software.
- In Event Viewer > Windows Logs > System, open the BugCheck event (ID 1001). The first value in brackets after 0x0000007f is the trap number.
- 0x00000008 is a double fault: Microsoft names a kernel stack overflow (often filter drivers, step 4) or a hardware problem.
- 0x00000006 (invalid opcode) most often comes from hardware memory corruption (steps 1 to 3).
You know whether to focus on drivers or hardware.
If it does not helpGive the files in C:\Windows\Minidump to a technician if you need a deeper analysis.
Possible causes
- Faulty, mismatched or newly installed RAM
- A CPU or memory overclock
- Failing hardware: motherboard, power supply or another component
- A new or updated driver, including file system filter drivers from antivirus or backup software
- Outdated BIOS or disk controller drivers
Useful Windows tools
These commands open Windows tools. Review changes before applying them.
mdsched.exeeventvwr.mscdevmgmt.mscWas this helpful?
Your progress is saved on this device.