PC seems to behave oddly or become unstable once it wakes up from sleep mode.
PC seems to behave oddly or become unstable once it wakes up from sleep mode.
Hello,
In April I upgraded my PC with some new components, mainly for gaming, and it has been performing excellently. Performance-wise, everything is fine. However, I’m experiencing a software-related problem where the system becomes unresponsive and unstable, especially after waking up from sleep mode. I prefer putting the PC to sleep if it hasn’t been used for a while, but I think this approach won’t last long. The issue also appears more frequently when the PC has been asleep for longer periods—around 15 minutes it seems to function properly.
Some of the recurring problems I’ve noticed are:
- The PC starts normally but sound devices stop being recognized, and simply pluging it back in doesn’t help.
- YouTube videos or streams load slowly or buffer, even though browsing is possible and internet connection remains active.
- Windows menus and buttons become unresponsive or react very slowly when clicked.
- Devices such as the mouse and keyboard behave as if they’re not connected, while the login screen freezes.
Here are my system details:
- Gigabyte RTX 4070
- Intel® Core™ i5-14600KF, 3500 Mhz
- TUF GAMING B760-PLUS WIFI D4 Motherboard
- Corsair 32gb DDR4 3000Mhz Vengeance LPX
- Corsair H150 RGB CPU Cooler
- Corsair CX750 750W PSU
When I first set up the PC, I reinstalled Windows 11 from an USB stick because I had a license. I also updated the BIOS to the latest version for the motherboard:
"TUF GAMING B760-PLUS WIFI D4 BIOS 1641".
I’ve tried updating drivers, updating Windows, resetting energy settings, disabling USB disconnect options, uninstalling and reinstalling sound software, and even upgrading USB slot versions. Still, I’m frustrated by having to turn the PC off and on repeatedly just to fix these issues, then restarting it again.
Do you think I should just reinstall Windows or try installing newer BIOS settings? These seem like my only remaining options, which feels like a last resort.
Any assistance would be greatly appreciated, and I hope we can resolve this.
Try executing "dism" and "sfc /scannow" to locate and resolve file issues.
Thank you for your response Ralston! I attempted the alternative method you mentioned earlier, which resolved an issue. Unfortunately, the problem continued. I'll check if using the dism cli tool might assist.