Fix STATUS_SYSTEM_SHUTDOWN (0XC00002EB) Error on Windows

The Quick Fix (30 seconds)

This error shows up when Windows or a driver tries to shut down the system while you're still using it. The simplest fix: check your power button settings. I've seen dozens of cases where a laptop's power button was set to "shut down" instead of "sleep" — one accidental press triggers this error.

1. Open Control Panel → Power Options.
2. Click Choose what the power buttons do.
3. Under Power button action, set it to Sleep (or Do nothing).
4. Save changes and restart.

That's it. If the error goes away, you're done. If not, move to the next step.

The Moderate Fix (5 minutes)

If the quick fix didn't help, the culprit is almost always a bad device driver. Windows tries to shut down a driver that won't respond, so it forces a system shutdown. Here's how to sort it.

Step 1: Run Driver Verifier

This tool catches misbehaving drivers. It can cause a BSOD if a driver is bad — that's expected. Write down the driver name it flags.

verifier

1. Press Win + R, type verifier, hit Enter.
2. Select Create standard settings → Next.
3. Check Automatically select all drivers installed on this computer.
4. Restart your PC. Let it run for 10-15 minutes.
5. If you get a BSOD, note the driver name. Boot into Safe Mode and uninstall that driver.

Step 2: Update or Roll Back Drivers

Go to Device Manager. Look for devices with a yellow exclamation mark. Right-click → Update driver. If you recently updated something, try Roll Back Driver instead. Common troublemakers: network adapters, graphics cards, and USB controllers.

The Advanced Fix (15+ minutes)

If the error still shows up, you're dealing with a deeper issue. Probably a corrupt system file, a bad Windows update, or a failing hard drive. Let's go step by step.

Step 1: Boot into Safe Mode with Networking

1. Restart your PC. At the sign-in screen, hold Shift while clicking Restart.
2. Select Troubleshoot → Advanced options → Startup Settings → Restart.
3. Press 5 for Safe Mode with Networking.

Step 2: Check for Corrupt System Files

Open Command Prompt as admin (right-click Start menu). Run these two commands in order:

sfc /scannow

DISM /Online /Cleanup-Image /RestoreHealth

The first one scans and fixes system files. The second fixes the image that SFC uses. Let them finish completely — might take 10 minutes.

Step 3: Remove Recent Windows Updates

Bad updates can trigger this shutdown error. In Safe Mode, go to Settings → Windows Update → Update history → Uninstall updates. Remove the most recent one, then restart normally.

Step 4: Check Your Drive for Errors

A failing hard drive can cause random shutdowns. Run this in Command Prompt as admin:

chkdsk C: /f

You'll need to schedule it for next restart. Type Y and reboot. Let it run — if it finds bad sectors, replace the drive soon.

Step 5: System Restore or Reset

If nothing works, try a System Restore to a point before the error started. If you don't have one, you're looking at a Reset this PC (keep your files) or a clean install. I've done dozens of these — reset usually fixes it, but clean install is the nuclear option.

Note: If you see this error on a server running Hyper-V or SQL Server, it's often a memory dump setting. Check System Properties → Advanced → Startup and Recovery → set Write debugging information to Complete memory dump. But for a regular PC, focus on the driver fix.

When to Give Up and Call a Pro

If you've done all this and the error still pops up, your motherboard or power supply might be failing. Try a different power outlet. Test with a known-good PSU if you have one. Otherwise, it's time for a repair shop.