PC getting stuck in wake/sleep mode almost every single time and I've tried pretty much everything, how can I fix this?

Question

PC getting stuck in wake/sleep mode almost every single time and I've tried pretty much everything, how can I fix this?

DazeTech 25

I believe I have tried almost every solution there is to fix this problem. I will be going back to my old motherboard once I have a little time to double check if this current new board is the culprit of my issues but it's brand new and for time purposes I would like to keep the new board.

Assuming the current board is fine, I am trying to narrow down what is causing these issues. Specifically when trying to manually or automatically allow my desktop to sleep I will notice 9/10 times the PC will wake itself within a millisecond and RGB, fans all start to spin up again. I have no other issues when using the PC at all. However once this occurs, even holding down the power button for 20 seconds will not do anything. The only way to use my PC again is to switch off the power on the PSU, and hard reset my PC. I thought vgk.sys was the issue yesterday so I deleted it and all residual files but I was still getting the same BSOD errors in event viewer (which I can post if needed) and I ended up doing a fresh install of windows to see if it would persist. This was odd because the files were no longer present but returning the same minidump.

Now after the fresh install, there aren't any Windows Error Reports in Event Viewer and no reports of bsod BUT the same exact patterns of my PC not being able to go to sleep properly, or rather waking up right away within milliseconds as shown in the event viewer logs, which will be on the bottom of this post. Being able to put my PC to sleep is pretty important for me because shutting down every single time will interfere with work.  I would greatly appreciate all the help I can get on this!!!

Here is my system info. systeminfo.txt

    **Solutions I have tried :**

Turning off wake timers in Power Plan Settings
Double checking wake timers in command prompt, checking powercfg /lastwake returning no results
Tried different set of RAM
Turning off Fast Boot
Turning off hybrid sleep
Checking both sets of RAM I am testing with in Windows Diagnostics tool and MemTest86
Fresh installing Windows11

Ending the HttpService from event viewer that seemed to be waking PC, same result -The only difference that occurred was the HttpService was replaced with this log

	(Information	7/1/2025 9:37:10 PM	Kernel-General	16	None

	The access history in hive \??\C:\ProgramData\Microsoft\Provisioning\Microsoft-Desktop-                 Provisioning-Sequence.dat was cleared updating 0 keys and creating 0 modified                                 pages.)

Playing games, using regularly, stress testing on software, checking temps of CPU and GPU and never reaching critical points which leads me to believe it isn't hardware related at all but rather an issue with W11 Down below is the event viewer logs SET OF EVENT VIEWER LOGS IN ORDER Information 7/1/2025 8:32:49 PM Kernel-Power 187 (243)

User-mode process attempted to change the system state by calling SetSuspendState or SetSystemPowerState APIs.

**Information	7/1/2025 8:32:49 PM	Kernel-Power	566	(268)**

The system session has transitioned from 4 to 5.

Reason Unknown

BootId: 11

**Information	7/1/2025 8:32:50 PM	Kernel-Power	42	(64)**

The system is entering sleep.

Sleep Reason: Application API

**Information	7/1/2025 8:32:50 PM	HttpService	114	HTTP Configuration Property Trace Task**

Removed URL (http://*:omit/upnp/eventing/) from URL group (0xFE00000020000002). Process Id 0x3E24 Executable path \Device\HarddiskVolume3\Windows\System32\svchost.exe, User LOCAL SERVICE

**Information	7/1/2025 8:32:52 PM	Kernel-Power	107	(102)**

The system has resumed from sleep.

**Information	7/1/2025 8:34:28 PM	Kernel-General	1	(5)**

The system time has changed to ‎2025‎-‎07‎-‎02T00:34:28.500000000Z from ‎2025‎-‎07‎-‎02T00:32:52.029990000Z.

Time Delta: 96470 ms

Change Reason: System time synchronized with the hardware clock.

Process: '' (PID 4).

RTC time: ‎2025‎-‎07‎-‎01T20:34:28.500000000Z

Current time zone bias: 240

RTC time is in UTC: false

System time was based on RTC time: false

**Information	7/1/2025 8:34:29 PM	BTHUSB	18	None**

Windows cannot store Bluetooth authentication codes (link keys) on the local adapter. Bluetooth keyboards might not work in the system BIOS during startup.

**Information	7/1/2025 8:34:30 PM	Kernel-Boot	30	(21)**

The firmware reported boot metrics.

**Information	7/1/2025 8:34:30 PM	Kernel-Boot	18	(57)**

There are 0x1 boot options on this system.

**Information	7/1/2025 8:34:30 PM	Kernel-Boot	32	(58)**

The bootmgr spent 0 ms waiting for user input.

**Information	7/1/2025 8:34:30 PM	Kernel-Boot	25	(32)**

The boot menu policy was 0x0.

**Information	7/1/2025 8:34:30 PM	Kernel-Boot	27	(33)**

The boot type was 0x2.

**Information	7/1/2025 8:34:30 PM	Kernel-Boot	247	(99)**

Unable to load Pluton-Windows firmware. StatusCode: STATUS_SUCCESS, Reason: Failed to apply firmware.

**Information	7/1/2025 8:34:30 PM	Kernel-Power	566	(268)**

The system session has transitioned from 5 to 6.

Reason SxTransition

BootId: 11

**Information	7/1/2025 8:34:30 PM	Kernel-Power	566	(268)**

The system session has transitioned from 6 to 8.

Reason Unknown

BootId: 11

**Information	7/1/2025 8:34:31 PM	Power-Troubleshooter	1	None**

The system has returned from a low power state.

Sleep Time: ‎2025‎-‎07‎-‎02T00:32:49.710534300Z

Wake Time: ‎2025‎-‎07‎-‎02T00:34:30.176296000Z

Wake Source: Unknown

**Information	7/1/2025 8:34:29 PM	TPM-WMI	1041	None**  (*USUALLY AT END OF LOG so ignore timestamps*)

Pre-attestation health check detailed information: {"Version":1,"HealthStatus":"Attestable","Required":[{"Field":"TpmPresent","Value":true,"DesiredValue":true},{"Field":"TpmMeetsMinimumVersion","Value":true,"DesiredValue":true},{"Field":"TpmIsResponsive","Value":true,"DesiredValue":true},{"Field":"EkCertIsAvailable","Value":true,"DesiredValue":true},{"Field":"TcgLogFound","Value":true,"DesiredValue":true}],"Expected":[{"Field":"PcrsMatchTcgLog","Value":true,"DesiredValue":true}],"Informational":[{"Field":"SecureBootEnabled","ValueFromComputer":true,"ValueFromTcgLog":true,"DesiredValue":true,"TcgValueIsVerifiable":true},{"Field":"VirtualSecureMemory","ValueFromComputer":false,"ValueFromTcgLog":false,"DesiredValue":true,"TcgValueIsVerifiable":true},{"Field":"SecureCorePCCompliant","ValueFromComputer":false,"ValueFromTcgLog":false,"DesiredValue":true,"TcgValueIsVerifiable":true}]}

**Information	7/1/2025 8:34:29 PM	TPM-WMI	1038	None**  (*USUALLY AT END OF LOG so ignore timestamps*)

Pre-attestation health checks confirm that the device is expected to pass attestation.

Please see C:\WINDOWS\Logs\MeasuredBoot\0000000011-0000000001.json for detailed information on what checks were made.

**Information	7/1/2025 8:45:29 PM	TPM-WMI	1282	None**

The TBS device identifier has been generated.

**Information	7/1/2025 8:45:29 PM	TPM-WMI	1025	None**

The TPM was successfully provisioned and is now ready for use.

0 comments

Answer accepted by question author

Ian-T 16,365 Microsoft External Staff Moderator

Hello DazeTech,

Welcome to Microsoft Q&A.

Based on your description, I understand you’re encountering an issue on your Windows 10/11 PC where the system gets stuck during sleep or wake-up transitions. As you mentioned, the computer often freezes when entering or resuming from sleep, and even after a cold boot, it may still hang—requiring a forced shutdown to recover. You’ve already tried all common software-level solutions, including reinstalling Windows, but the issue persists.

If the problem remains after a complete system reinstall, it strongly suggests that the root cause may not be a simple software or driver conflict. When an issue survives a clean operating system installation, we typically shift the diagnostic focus toward hardware or motherboard firmware (BIOS/UEFI)—specifically compatibility, configuration, or hardware faults. Sleep/wake problems are especially sensitive to these layers.

Since you’ve already tried all standard software fixes, we now need to focus on hardware and firmware.

1. Update and Configure BIOS/UEFI (High Priority)

This is the most critical step for resolving power management and wake-related issues.

Update BIOS/UEFI:
- Visit the official website of your motherboard manufacturer (or your computer’s manufacturer if it’s a pre-built system like Dell, HP, Lenovo, etc.).
  - Download and install the latest BIOS/UEFI firmware according to your motherboard or system model.
    - Note: BIOS updates carry risk. Follow the manufacturer’s instructions carefully and ensure your PC is connected to a stable power source during the update.
    - Reset BIOS/UEFI to Default Settings:
      - Enter the BIOS/UEFI setup during boot (usually by pressing Del, F2, F10, or similar).
        
        Look for “Load Optimized Defaults” or “Load Setup Defaults”, then apply and save the changes. This clears all custom configurations to avoid misconfigured power settings.
        
        Adjust Power Management Settings (advanced – only if defaults don’t help):
        
        Inside BIOS/UEFI, check for settings under ACPI Settings, Power Management, or CPU Features.
        
        Try toggling C-States (disable them or switch to different levels).
        
        Check if ErP Ready (low power standby) is enabled.
        
        Review PCIe Power Management or ASPM settings.
        
        Change only one setting at a time and test the sleep/wake behavior after each.

Disclaimer: Microsoft provides no assurances and/or warranties, implied or otherwise, and is not responsible for the information you receive from third-party sites or any technology-related support derived from them.

If you plan to modify BIOS settings, please back up all your personal files first to avoid potential data loss.

2. Hardware Troubleshooting

Memory Testing (you may have done this, but for completeness, I’ll include it):
- Run the Windows Memory Diagnostic Tool: Search for and open it in Windows, then let it perform a full scan to detect memory issues.
  - Cross-test memory sticks: If you have more than one RAM module, try running the system with only one installed at a time to identify faulty modules.
  - Check Power Supply Unit (PSU):
    - Ensure all power connections are secure.
      - If you have access to a spare PSU, test with that. While the PSU is less commonly the root cause of sleep issues, it’s worth ruling out in rare edge cases.
      - Disconnect Non-Essential External Devices (strongly recommended):
        
        Unplug all unnecessary USB devices, docking stations, printers, etc., leaving only your keyboard, mouse, and display connected.
        
        Then test sleep/wake again. This can help identify any conflicting peripherals.
        
        Clean Install GPU Drivers (worth trying even after Windows reinstall):
        
        Download the latest GPU driver from your GPU manufacturer’s website (NVIDIA, AMD, or Intel).
        
        Use DDU (Display Driver Uninstaller) in Safe Mode to remove all remnants of old drivers.
        
        Reboot and install the freshly downloaded driver.

Let me know how it goes, and feel free to update me with your progress!

Best wishes

Ian Trinh | Microsoft Q&A Support Specialist

DazeTech 25 Reputation points

2025-07-03T04:22:31.4766667+00:00

After swapping to a new motherboard I was able to pinpoint one of my external USB devices causing this error. Weirdly enough, I had the same reaction on both motherboards but the newer motherboard would end up crashing to a black screen while the older motherboard would just wake up normally. Regardless the culprit was a wireless mouse. Thanks for the help!
desynch 5 Reputation points

2025-07-06T18:11:51.7633333+00:00

Hi DazeTech,

Your comment was very valuable to me. I was having the same problem "intermittent black sceen on wakeup from sleep" and I was pulling my hair because nothing worked. First I thought it was about my nvidia card. Now you mentioned "external USB devices" it was very helpful because I had a USB switch for my keyboard which allowed to switch between 2 PCs but I used it very rarely. In addition I had connected this USB switch to my primary monitor which had a USB hub. So either the USB switch went bad or the combination with the monitor was the culprit. Anyway I now connect my keyboard directly to the case, and now it seems to be working after 2-3 hours of sleep. I will be sure if it still works after a day of sleep. So before thinking it's your graphics card, drivers, motherboard, ram or bios settings, first examine your external USB devices, they can cause weird problems as it seems, especially the USB switches/hubs made in china :)

1 additional answer

Your answer

DazeTech 25 Reputation points

2025-07-03T04:22:31.4766667+00:00

After swapping to a new motherboard I was able to pinpoint one of my external USB devices causing this error. Weirdly enough, I had the same reaction on both motherboards but the newer motherboard would end up crashing to a black screen while the older motherboard would just wake up normally. Regardless the culprit was a wireless mouse. Thanks for the help!
desynch 5 Reputation points

2025-07-06T18:11:51.7633333+00:00

Hi DazeTech,

Your comment was very valuable to me. I was having the same problem "intermittent black sceen on wakeup from sleep" and I was pulling my hair because nothing worked. First I thought it was about my nvidia card. Now you mentioned "external USB devices" it was very helpful because I had a USB switch for my keyboard which allowed to switch between 2 PCs but I used it very rarely. In addition I had connected this USB switch to my primary monitor which had a USB hub. So either the USB switch went bad or the combination with the monitor was the culprit. Anyway I now connect my keyboard directly to the case, and now it seems to be working after 2-3 hours of sleep. I will be sure if it still works after a day of sleep. So before thinking it's your graphics card, drivers, motherboard, ram or bios settings, first examine your external USB devices, they can cause weird problems as it seems, especially the USB switches/hubs made in china :)

Answer 1

desynch 5

Update: It turned out "external USB devices" was not the problem in my case. So as a final solution I bought VESA certified DisplayPort cables. Bad DP cables can cause weird problems, for example they should not wire PIN 20 (some chinese brands do this). PIN 20 is very dangerous it sends current from your monitor to the GPU! I also dropped usage of MST (daisy chaining monitors), I use 2 DP cables for connecting 2 monitors directly to the GPU. The system seems stable for now.

0 comments