0X00000279: Driver failed standby – the fix that actually works

When this error shows up

You put your PC to sleep, the screen goes black, fans spin down – then it wakes up immediately with a 0X00000279 in Event Viewer under System > Kernel-Power, event ID 41. The message reads: {System Standby Failed} The driver %hs does not support standby mode.

This happens most often after a driver update or a fresh Windows install on older hardware (think Intel 6th-8th gen laptops, some Ryzen 2nd gen boards, or any system with a dodgy network card). The buggy driver either doesn't advertise S3 support or actively blocks the sleep transition.

Root cause

Windows uses ACPI power states. S3 (Suspend-to-RAM) requires every driver to respond to a IRP_MJ_POWER with IRP_MN_SET_POWER for state S3. If a driver returns STATUS_NOT_SUPPORTED or times out, the kernel aborts the sleep and the system wakes immediately. The error code 0X00000279 is the kernel's way of saying “I asked nicely, driver X said no.”

The driver name after %hs is logged in the event details – usually it's a miniport driver (network, WiFi, Bluetooth, or a storage controller). I've seen this most frequently with e1i65x64.sys (Intel Ethernet), rt640x64.sys (Realtek), and athw8x.sys (Atheros WiFi). Sometimes it's a USB 3.0 controller driver that doesn't handle selective suspend.

Fix – force the driver to cooperate

1. Identify the guilty driver

   Open Event Viewer (eventvwr.msc), go to Windows Logs > System. Filter by Event ID 41. Double-click the entry, look at the Details tab – you'll see the driver name in the %hs placeholder. Write it down exactly.

2. Check which device uses that driver

   Run as admin:

   driverquery /si | findstr /i "your_driver_name.sys"

   That shows the service name and display name. Cross-reference in Device Manager (look for devices with that driver file). Common culprits: network adapters, Bluetooth radios, SD host controllers.

3. Disable the driver's ability to wake the system

   In Device Manager, right-click the device, go to Power Management, uncheck Allow this device to wake the computer. This doesn't fix the S3 rejection – but sometimes it's enough to let sleep proceed. Try sleeping again.

4. Force the driver to allow S3 via registry

   If step 3 fails, the driver is flat-out refusing S3. Open Regedit, go to:

   HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Session Manager\Power

   Create a new DWORD (32-bit) value named HiberbootEnabled and set it to 0. Then under the same key, create another DWORD: SleepReliabilityChecks set to 0. Reboot.

   Why this works: SleepReliabilityChecks=0 tells the kernel to skip the driver S3 capability check. It's a blunt tool – the driver still doesn't support standby, but Windows will try to sleep anyway. On some machines the driver will handle the transition fine despite claiming it can't. On others, you'll get a crash on resume. Worth a shot.

5. Roll back or replace the driver

   If the registry hack gives you a crash on wake, the driver truly can't handle S3. Go to Device Manager, right-click the device, Properties > Driver > Roll Back Driver. If the rollback is grayed out, download the previous version from the manufacturer's site. For Intel NICs, I use the Intel Ethernet Connections CD from 2019 – version 22.x series, not the newer 25.x.

6. Disable the device entirely as last resort

   If you don't need the device (like a Bluetooth adapter you never use), disable it in Device Manager. Sleep will work immediately. Not elegant, but effective.

What to check if it still fails after the fix

Some motherboards have buggy ACPI tables. Update your BIOS to the latest version – manufacturers quietly fix S3 issues in newer firmware. Also run powercfg /energy from an admin command prompt; it generates an HTML report that lists any drivers with power problems. Look for the line “Platform does not support Standby” – that's a different problem (BIOS S3 setting disabled or missing).

If the error persists, try disabling fast startup: powercfg /h off and reboot. Fast startup is a hybrid shutdown that sometimes corrupts driver power states. Turning it off forces a full driver reinit on boot.

When nothing works and the driver is essential (like your main SSD NVMe controller), your only reliable option is to switch to hibernate (powercfg /h on) – it bypasses S3 entirely. Hibernate writes RAM to disk, so drivers don't need to maintain state. It's slower to resume, but it's stable.