Fix Error 0x000002DA: System Wakes Randomly

You're sitting there, work's done, you put the PC to sleep (or hibernate), and then—bam—it's back on ten minutes later. Fan spinning, lights on, and you're wondering what ghost just kicked your desk. Check Event Viewer, and there it is: ERROR_WAKE_SYSTEM (0x000002DA) with the description "The system has awoken."

I've seen this most often on Windows 10 and 11 machines with a network card that thinks it's your alarm clock. Had a client last month whose Lenovo ThinkCentre woke up every two hours on the dot because the Realtek Ethernet adapter was set to "wake on magic packet" by default. Or it's a mouse that twitches on the desk and wakes the system. Whatever the cause, the fix is the same: find the device that's pulling the trigger and tell it to shut up.

What Actually Causes Error 0x000002DA?

This error isn't a crash or corruption—it's a log entry that says "something woke the system." Windows keeps track of what triggered the wake from sleep or hibernate. Under the hood, it's a hardware device (like your network card, keyboard, or mouse) that sent a signal to the motherboard saying "I need attention." That signal bypasses the sleep state and forces the CPU back on.

The root cause is almost always a device with "Allow this device to wake the computer" checked in its power management settings. By default, Windows enables this for most input and network devices. For 90% of people, the culprit is either the Ethernet adapter, Wi-Fi card, or USB hub. Rarely, it's a driver bug where the device sends false wake signals—but that's less common than you'd think.

The Fix: Disable Wake-Enable Devices Step by Step

Skip third-party tools. The built-in powercfg command-line tool is faster and tells you exactly what device caused the last wake. Here's how I do it every time.

Open Command Prompt as Administrator. Hit the Start button, type cmd, right-click "Command Prompt", and choose "Run as administrator". Don't skip this—standard user mode won't show the wake history.
Run this command to see what woke your system last:
```
powercfg -lastwake
```
This prints the device name and type that did it. If it says something like "Realtek PCIe GbE Family Controller", you've found your problem. Write that name down.
Check all devices that can wake the system:
```
powercfg -devicequery wake_armed
```
This lists every device that's currently allowed to wake your PC. You'll probably see your keyboard, mouse, network card, and maybe a USB controller. If you see more than three, that's your list of suspects.
Disable wake for the problematic device. Open Device Manager (right-click Start > Device Manager). Find the device from the -lastwake output. Right-click it, select "Properties", go to the "Power Management" tab, and uncheck "Allow this device to wake the computer". Click OK.
Repeat for all devices you don't need waking you. Personally, I leave the keyboard and mouse enabled if I want to wake with a keypress or click—but if that's causing issues, uncheck those too. For network cards, it's almost always safe to disable wake-on-LAN unless you actually use remote wake.
Test it. Put your system to sleep (Start > Power > Sleep). Wait a minute. Move the mouse, press a key—nothing should happen. Wait five minutes to be sure no sneaky timer fires. If the system stays asleep, you're golden.

What If It Still Wakes?

Sometimes disabling the device in Power Management doesn't stick. Driver updates can re-enable it. Or the BIOS has its own wake settings that override Windows. Here's the checklist I run through when the basic fix fails.

Check wake timers: Run powercfg -waketimers. This shows scheduled tasks or system timers that can wake the PC. If you see something like "Windows Update" or "Defrag", disable the task in Task Scheduler or set it to not wake the system.
Disable wake in BIOS: Reboot, mash F2 or Del to enter BIOS. Look for "Wake on LAN" or "Resume by Alarm" or "USB Wake Support". Disable all of them. Some HP and Dell machines have separate settings for this that Windows can't touch.
Update the driver: If it's a network card, go to the manufacturer's site (Intel, Realtek, Broadcom) and grab the latest driver. Old drivers sometimes have buggy wake support that sends false signals.
Hardware swap test: Stuck after all that? Unplug the USB devices one by one. Had a guy whose wireless mouse receiver was faulty—every time the battery dipped, it sent a wake signal. Replaced the receiver, problem gone.

Bottom line: Error 0x000002DA is a symptom, not a crash. Track down the device with powercfg, disable its wake privilege, and your system will stay asleep until you actually want it on. If nothing works, the BIOS override is your last resort. I've yet to see a case where that didn't kill the ghost.