Windows BSOD Error 0x00000078 — PHASE0_EXCEPTION Fix

What Does This Error Mean?

The 0x00000078 blue screen means an unexpected exception (a serious error) occurred during Phase 0 of Windows startup — the very earliest stage of boot. Phase 0 happens before almost anything is loaded, so when something goes wrong here, it means the most fundamental parts of Windows are broken. This is one of the more serious BSOD codes and is almost always caused by hardware problems, damaged system files, or a failed Windows Update.

Affected Models

Windows 10
Windows 11
Windows 8.1
Windows Server

Common Causes

Faulty or failing RAM is producing data errors at the exact moment Windows tries to initialize core memory structures
The Windows Boot Configuration Data (BCD) or bootloader files are corrupted or missing
A recently installed Windows Update damaged early-boot system components
A storage device (SSD or hard drive) is failing, causing critical files to be unreadable at boot time
Incorrect BIOS settings — especially virtualization, Secure Boot, or TPM settings — are blocking early Windows initialization

How to Fix It

Repair the Windows bootloader from Recovery Command Prompt. Boot from a Windows USB, open Command Prompt, and run these commands one at a time: bootrec /fixmbr — then bootrec /fixboot — then bootrec /rebuildbcd

These commands rebuild the Master Boot Record and Boot Configuration Data. A corrupted BCD is one of the most common causes of Phase 0 exceptions.
Test your RAM. From the Recovery Environment, go to Advanced options > Startup Settings and boot normally if possible, then run Windows Memory Diagnostic from the Start menu.

Even a single faulty memory cell can cause a Phase 0 crash. If the diagnostic reports errors, replace the failing RAM stick.
Check your BIOS settings. Restart, press Delete or F2 to enter BIOS, and choose 'Load Optimized Defaults.' Confirm Secure Boot is set correctly for your Windows version (enabled for Windows 11).

Incorrect BIOS settings after a CMOS battery replacement, BIOS update, or accidental change can prevent Windows from starting. Resetting to defaults eliminates this cause.
Run System File Checker offline from the Recovery Command Prompt: sfc /scannow /offbootdir=C:\ /offwindir=C:\Windows

This checks and repairs early-boot system files that are normally locked while Windows is running.
Run a disk health check. From Recovery Command Prompt, type: chkdsk C: /f /r — and press Enter. This scans for file system errors and bad sectors on your drive.

The /r flag scans every sector of your disk, which takes time but is thorough. Bad sectors on an SSD or hard drive can cause unpredictable early-boot failures.

When to Call a Professional

If bootloader repair and SFC do not resolve the issue, a technician can run an extended diagnostic on your storage drive and RAM. Hard drive failures that are not yet critical can still cause exactly this type of early-boot crash. A professional can also perform an in-place Windows upgrade to replace all system files without touching your personal data.

Frequently Asked Questions

What happens during Phase 0 of Windows startup?

Phase 0 is the very first stage of Windows loading — it happens before most drivers or services start. In Phase 0, Windows sets up the absolute basics: CPU tables, memory layout, and a minimal environment to load the rest of the operating system. An exception here means something went wrong before Windows even had a chance to get started, which is why it is so serious.

My PC was working fine yesterday — what changed?

Common overnight changes include automatic Windows Updates and hard drives beginning to fail. Windows often installs updates in the background and applies them on the next restart. Solid-state drives and hard drives can also fail quite suddenly — one day fine, the next day unreadable. Checking the drive health with chkdsk and reviewing recent Windows Update history are good first steps.

What is the BCD and why does it matter?

BCD stands for Boot Configuration Data — it is a file that tells your computer where to find Windows and how to start it. Think of it as the table of contents for your boot process. If the BCD is corrupted or empty, Windows cannot locate itself and crashes immediately. The bootrec commands rebuild this file from scratch.