F5F Stay Refreshed Hardware Desktop Device remains inactive after power cycle.

Device remains inactive after power cycle.

Device remains inactive after power cycle.

M
MrsMega
Junior Member
Find
12
09-16-2019, 01:34 PM
#1
I set up my PC about two years ago with the following components: Gigabyte B550M S2H, 1660 SUPER, Ryzen 3600, 16GB RAM, 1TB NVMe drive, Corsair RM650 power supply, and Windows 10 64-bit. Over the past year, I've noticed a recurring problem when putting it to sleep. Most of the time it functions properly—sleeping within ten seconds, then resuming smoothly after any input. When I wake it up, the GPU fan kicks on loudly for two to three seconds before calming down as Windows loads.

Occasionally, about 20-30 times, the PC fails to boot into Windows at all when woken, and the display doesn’t appear. The fan stays high, and no BIOS screen shows up. To resolve this, I usually power off the machine at the switch and restart it. However, sometimes it remains unresponsive even after a quick reboot.

If I turn it off and on again, it works fine, but if not, I leave it powered on with the fan running until it restarts normally. This process usually takes 10 to 15 minutes. It hasn’t been too bothersome since it happens only a few times a month.

Recently, it happened again—this time even after removing the BIOS battery and resetting CMOS, leaving the battery out for an hour. After turning it back on, the fan started normally for a short while before powering down. Once it cooled off, it became loud again, then quiet a few times before showing up and booting as usual.

However, after a full shutdown about ten minutes later and restarting, it’s stuck once more with no display. I’ve tried removing the battery for an hour, but that didn’t help. It seems to depend on whether I sleep for less than a minute or longer. The issue appears unrelated to RAM changes, power supply swaps, or peripheral removal.

I suspect something about Windows not shutting down correctly might be causing this state, possibly linked to Fastboot being disabled. It feels like it could come back if I keep trying, but it’s frustrating since everything works fine once it boots normally.
Reply
Reply
M
MrsMega
09-16-2019, 01:34 PM #1

I set up my PC about two years ago with the following components: Gigabyte B550M S2H, 1660 SUPER, Ryzen 3600, 16GB RAM, 1TB NVMe drive, Corsair RM650 power supply, and Windows 10 64-bit. Over the past year, I've noticed a recurring problem when putting it to sleep. Most of the time it functions properly—sleeping within ten seconds, then resuming smoothly after any input. When I wake it up, the GPU fan kicks on loudly for two to three seconds before calming down as Windows loads.

Occasionally, about 20-30 times, the PC fails to boot into Windows at all when woken, and the display doesn’t appear. The fan stays high, and no BIOS screen shows up. To resolve this, I usually power off the machine at the switch and restart it. However, sometimes it remains unresponsive even after a quick reboot.

If I turn it off and on again, it works fine, but if not, I leave it powered on with the fan running until it restarts normally. This process usually takes 10 to 15 minutes. It hasn’t been too bothersome since it happens only a few times a month.

Recently, it happened again—this time even after removing the BIOS battery and resetting CMOS, leaving the battery out for an hour. After turning it back on, the fan started normally for a short while before powering down. Once it cooled off, it became loud again, then quiet a few times before showing up and booting as usual.

However, after a full shutdown about ten minutes later and restarting, it’s stuck once more with no display. I’ve tried removing the battery for an hour, but that didn’t help. It seems to depend on whether I sleep for less than a minute or longer. The issue appears unrelated to RAM changes, power supply swaps, or peripheral removal.

I suspect something about Windows not shutting down correctly might be causing this state, possibly linked to Fastboot being disabled. It feels like it could come back if I keep trying, but it’s frustrating since everything works fine once it boots normally.

Reply
Reply
Z
ZoiGames
Junior Member
Find
9
09-19-2019, 03:56 AM
#2
Bump faced a comparable problem with an older XFX R9 390 model, though the issue resolved itself likely after a Windows or driver update.
Reply
Reply
Z
ZoiGames
09-19-2019, 03:56 AM #2

Bump faced a comparable problem with an older XFX R9 390 model, though the issue resolved itself likely after a Windows or driver update.

Reply
Reply
J
Jarvan_IV
Member
Find
120
09-19-2019, 05:05 AM
#3
It’s better to check your system and hardware first before updating. A BIOS or firmware update isn’t usually necessary unless there are known issues. Updating everything can help, but only after confirming stability.
Reply
Reply
J
Jarvan_IV
09-19-2019, 05:05 AM #3

It’s better to check your system and hardware first before updating. A BIOS or firmware update isn’t usually necessary unless there are known issues. Updating everything can help, but only after confirming stability.

Reply
Reply
A
AlfredoMCYT
Member
Find
70
09-28-2019, 08:29 PM
#4
It worked on a previous MSI Z97 with an i5-4690K using the newest BIOS. I believe starting with DDU and updating the GPU drivers is the best approach.
Reply
Reply
A
AlfredoMCYT
09-28-2019, 08:29 PM #4

It worked on a previous MSI Z97 with an i5-4690K using the newest BIOS. I believe starting with DDU and updating the GPU drivers is the best approach.

Reply
Reply
J
JVMASTER11
Member
Find
127
09-28-2019, 11:57 PM
#5
I also updated my GPU drivers last week. The problem still occurs even when the onboard graphics are turned off and the GPU is removed.
Reply
Reply
J
JVMASTER11
09-28-2019, 11:57 PM #5

I also updated my GPU drivers last week. The problem still occurs even when the onboard graphics are turned off and the GPU is removed.

Reply
Reply