Fix ERROR_RESUME_HIBERNATION (0x000002D7) on Windows 10/11

Why You're Seeing This Error

That 0x000002D7 error usually means Windows tried to resume from a saved hibernation state but something went wrong. I've seen it most often after a driver update—especially graphics or storage drivers—or when the hibernation file (hiberfil.sys) got corrupted due to a sudden power loss during sleep. Don't panic; this is a common Windows 10 and 11 issue.

Fix 1: Quick Restart (30 seconds)

Before you dig into anything, just restart your PC. I know that sounds too simple, but a clean boot clears the stuck hibernation state. If that works, you're done—but if the error returns, move on to Fix 2.

Fix 2: Disable and Re-enable Hibernation (5 minutes)

This forces Windows to rebuild the hibernation file from scratch. It's the most reliable fix I've used.

1. Open Command Prompt as administrator—right-click the Start button and pick 'Command Prompt (Admin)' or 'Windows Terminal (Admin)'.
2. Type powercfg /h off and press Enter. This deletes the old hiberfil.sys.
3. Restart your PC (yes, again).
4. After the restart, open the same admin prompt and type powercfg /h on. This creates a fresh hibernation file.

Test by putting your PC to sleep and waking it up. Still getting the error? Let's go deeper.

Fix 3: Update or Roll Back Problem Drivers (10 minutes)

If the error started after a driver update, roll it back. I've had this happen twice with NVIDIA graphics drivers on Windows 11.

1. Open Device Manager (right-click Start → Device Manager).
2. Expand 'Display adapters', right-click your GPU, and choose 'Properties'.
3. Go to the 'Driver' tab and click 'Roll Back Driver' if available. If not, update the driver from the manufacturer's site.
4. Do the same for 'Storage controllers' and 'System devices'—especially any Intel or AMD chipset drivers.

Restart and test again. Still broken? Try the safe mode test in Fix 4.

Fix 4: Boot into Safe Mode to Isolate the Issue (15+ minutes)

Safe mode loads only essential drivers. If hibernation works there, a third-party driver or service is the culprit.

1. Hold Shift while clicking 'Restart' from the Start menu. This gets you into recovery.
2. Go to Troubleshoot → Advanced options → Startup Settings → Restart.
3. Press 4 or F4 to enter Safe Mode.
4. Once in Safe Mode, try hibernating and resuming. If it works, you've got a driver conflict.
5. Use the System Configuration tool (msconfig) to disable non-Microsoft services one by one, then reboot normally to find the offender.

Fix 5: Reset Power Plans to Default (15 minutes)

Corrupted power plan settings can also cause this error. I've seen it happen after a third-party power management tool messed with defaults.

1. Open Command Prompt as admin.
2. Run powercfg -restoredefaultschemes and hit Enter. This resets all power plans to Windows defaults.
3. Restart and test hibernation.

If that doesn't help, you might need to run sfc /scannow from an admin prompt to check for system file corruption.

When All Else Fails: Check Disk for Corruption

A bad sector on your drive can corrupt the hibernation file. Run this in an admin prompt:

chkdsk C: /f /r

You'll need to restart for the scan to run. It can take a while—grab a coffee. If it finds errors and fixes them, the error should vanish.

Still Stuck?

If none of these work, there's a chance your motherboard's firmware (BIOS/UEFI) has a known bug with Windows modern standby—check your manufacturer's support site for a firmware update. I fixed this exact error on a Dell XPS 13 by updating its BIOS to version 1.18.0.