Match the symptom before changing settings
| What you observe | Where to focus |
|---|---|
| Fans run but screen stays black | Reset graphics and test another display |
| Keyboard and mouse cannot wake PC | Check device wake permission and USB power |
| PC must be force-restarted | Update chipset, graphics, storage and firmware |
| Problem occurs only through a dock | Test direct display and update dock firmware |
Diagnose resume from sleep with evidence first
Put the PC to sleep and record what happens when you try to wake it: keyboard/mouse ignored, fans running with black screen, reboot required, or no power response. Note whether the issue affects built-in and external displays.
Separate display-resume failure from full system-resume failure. If the PC is responsive on the network or keyboard lights react while the screen stays black, focus more on graphics/display wake than total power failure.
Complete these focused checks: save work before repeated sleep tests; note whether fans, keyboard lights and network return; try the physical power button once briefly; check Reliability Monitor after forced recovery. Take screenshots or notes before changing firmware, encryption, recovery, driver or power settings. Those records provide a return path if the first repair does not help.
Use supported graphics, chipset, USB, BIOS/UEFI, and Windows updates when the wake failure began after a driver or firmware change.
Save open work before repeated sleep tests. Keep BitLocker recovery information available before firmware changes and avoid hard power-offs unless the machine cannot recover.
Separate black display from failed resume
Use Windows + Ctrl + Shift + B, test another screen and listen for Windows audio before assuming the whole PC is frozen.
Put the PC to sleep and record what happens when you try to wake it: keyboard/mouse ignored, fans running with black screen, reboot required, or no power response. Note whether the issue affects built-in and external displays.
Separate display-resume failure from full system-resume failure. If the PC is responsive on the network or keyboard lights react while the screen stays black, focus more on graphics/display wake than total power failure.
Complete these focused checks: save work before repeated sleep tests; note whether fans, keyboard lights and network return; try the physical power button once briefly; check Reliability Monitor after forced recovery. Take screenshots or notes before changing firmware, encryption, recovery, driver or power settings. Those records provide a return path if the first repair does not help.
Use supported graphics, chipset, USB, BIOS/UEFI, and Windows updates when the wake failure began after a driver or firmware change.
Save open work before repeated sleep tests. Keep BitLocker recovery information available before firmware changes and avoid hard power-offs unless the machine cannot recover.
Separate black display from failed resume
Use Windows + Ctrl + Shift + B, test another screen and listen for Windows audio before assuming the whole PC is frozen.
When the PC appears stuck asleep, first check whether the display is the only part that failed to resume. Listen for fans, notification sounds, keyboard lights, or other signs that Windows is actually awake.
1Verification checkpoint
- Repeat the original action once.
- After each targeted fix, complete a full sleep-and-wake cycle and verify the display, input devices, and network return normally.
- Restore diagnostic changes that did not help.
Check wake devices and connections
Test the power button, built-in keyboard and direct display with docks and USB hubs removed. Keep one reliable wake method.
Test the power button, built-in keyboard and direct display with docks and USB hubs removed. Keep one reliable wake method.
Test wake using the power button, keyboard, and mouse separately. If one works and another does not, focus on that device's wake permission or driver instead of treating the entire sleep state as broken.
2Verification checkpoint
- Repeat the original action once.
- After each targeted fix, complete a full sleep-and-wake cycle and verify the display, input devices, and network return normally.
- Restore diagnostic changes that did not help.
Repair the platform driver stack
Install supported BIOS, chipset, graphics and storage updates, check sleep states with powercfg /a and restore firmware defaults only after recording settings.
Install supported BIOS, chipset, graphics and storage updates, check sleep states with powercfg /a and restore firmware defaults only after recording settings.
Before changing graphics, chipset, or firmware, save work and record the currently installed versions. Resume failures are sensitive to drivers, so knowing the last known-good version matters.
3Verification checkpoint
- Repeat the original action once.
- After each targeted fix, complete a full sleep-and-wake cycle and verify the display, input devices, and network return normally.
- Restore diagnostic changes that did not help.
Interpret the result before escalating
If the system resumes but the screen stays black, graphics or display initialization is more likely than a complete sleep-state failure. An external monitor test can help separate panel/display issues from system wake.
If the PC only wakes after holding the power button, determine whether that action caused a forced shutdown. A fresh boot after forced power-off is not evidence that sleep successfully resumed.
If wake failures began immediately after a graphics, chipset, BIOS, or Windows update, that timing is strong evidence. Prefer supported update/rollback paths over broad registry or power tweaks.
Verify the fix and choose the safe escalation
After the suspected fix, put the PC to sleep and wake it three times using the normal method. Confirm the desktop returns without a forced shutdown and that open applications remain intact.
Test once with external displays or docks disconnected and once with your normal setup. Resume problems that return only with one accessory should be investigated at that accessory/driver layer.
If the machine remains unresponsive across multiple supported driver and firmware tests, or sleep causes repeated data loss or forced power-offs, use Hibernate or Shut down temporarily while pursuing hardware or repair-install diagnosis.
Technical order checked against current Microsoft guidance. Exact controls vary by Windows build, hardware, edition and organization policy.
Frequently asked questions
What does Windows + Ctrl + Shift + B do?
It restarts the graphics driver and can restore a black display when Windows itself has resumed.
Why can the power button wake the PC but not the keyboard?
The keyboard or USB controller may lack wake permission or lose power during sleep.
Can BIOS updates fix wake problems?
Yes, platform firmware can fix sleep-state issues, but use only the exact device maker package with reliable power.