F5F Stay Refreshed Hardware Desktop Problem encountered when trying to show or accept input after restarting or putting the device to sleep.

Problem encountered when trying to show or accept input after restarting or putting the device to sleep.

Problem encountered when trying to show or accept input after restarting or putting the device to sleep.

S
Sakura_trick
Member
75
08-15-2023, 04:18 PM
#1
Hi Everyone,
I just recently did some major upgrades on my system and after numerous stressful days of troubleshooting I have achieved a somewhat stable state that has allowed me to try and relieve some of the stress through relaxation on my PC but there is a lingering anxiety related to a couple (possibly related?) issues remaining.
🖥️
System Specs
Original Setup (Before Swapping Anything):
CPU:
Intel Core i5-9600K 3.7 GHz 6-Core Processor
GPU:
Asus STRIX GAMING OC GeForce RTX 2070 8 GB Video Card
Motherboard:
ASRock Z390 Pro4 ATX LGA1151 Motherboard
RAM:
Corsair Vengeance RGB Pro 32 GB (2 x 16 GB) DDR4-3600 CL18 Memory
Storage:
Samsung 860 Evo 250 GB 2.5" Solid State Drive
(OS drive)
Seagate BarraCuda 2 TB 3.5" 7200 RPM Internal Hard Drive
Seagate BarraCuda 6 TB 3.5" 5400 RPM Internal Hard Drive
Samsung 980 Pro 2 TB M.2-2280 PCIe 4.0 X4 NVME Solid State Drive
PSU:
Corsair RM750x (2018) 750 W 80+ Gold Certified Fully Modular ATX Power Supply
OS:
Windows 11 Home (24H4 I think?)
After Swaps/Upgrades:
CPU:
Intel Core i7-14700K 3.4 GHz 20-Core Processor
GPU:
Asus ROG STRIX GAMING OC GeForce RTX 5070 Ti 16 GB Video Card
Motherboard:
Asus TUF GAMING Z790-PLUS WIFI D4 ATX LGA1700 Motherboard
PSU:
Corsair RM1000x (2024) 1000 W Fully Modular ATX Power Supply
OS:
Windows 11 Home (formatted OS drive and reinstalled Win11 from Microsoft media installer)
⚠️
The Problem
I've seen similar posts on here of similar issues but nobody seems to be encountering the exact same thing I'm encountering. Each post seems to have some minor aspect that is different and makes their issue seemingly different than mine.
Essentially what I am encountering is an issue in which my display does not return after a reboot or going into sleep mode, as well as sometimes even after graceful shutdowns. The issue goes like this: the system reboots either from myself hitting the restart, BIOS rebooting after a "save changes and reset", OR the system goes into sleep mode after inactivity. Once the system reboots, or I click or press a key on my keyboard to awake it, the component RGB comes on, the fans start spinning etc, and then I see the debug lights go through the CPU one and then the DRAM, the DRAM light
goes away
(seems to differ from other similar issues I've seen people post about), but the next two lights of VGA and BOOT never turn on. The keyboard's unresponsive, as is the mouse, no LEDs on the keyboard after the initial "tap of the keys" to wake the system and no display on either monitor.
The system seems to work normally only if I have it turn back on after the reboot, or come back awake from sleep mode, wait for it to go through the first two debug lights of CPU and DRAM and then once it fails to proceed after that, I hold down the power button to turn off, wait for the fans to stop spinning, and then turn it back on with the power button. The lights then go through CPU, DRAM, small second or two hesitation and a click sound, VGA and then BOOT with the display appearing and the keyboard LEDs coming on and functioning, etc. (essentially a successful boot). This then seems to be completely functional until I next shutdown, restart or allow it to go into sleep mode.
I mentioned that it also seems to occur after normal graceful shutdowns, which also seems to differ from many others I have seen encountering similar issues. To clarify, I shutdown normally through Windows, and then no matter the time period whether it's immediate or hours later or the next day, when I turn it back on, I go through the cycle again of allowing it to fail to reach BOOT and then holding the power button to turn it off, turning it back on, etc, to reach that "stable" useable state.
The problem seems to be related to how the system handles restarts or wakes from sleep, and I’m unsure of what's causing it and frankly have reached my wit's end.
🔧
Things I Tried
Reset CMOS through "shorting" the pins and pulling the CMOS battery and waiting 10+ minutes
Flashed BIOS (BIOS Flash from USB latest version 1820)
Re-seated RAM
Reinstalled Windows 11 (although it occurs after restart from BIOS/UEFI as well so I don't think it'd matter)
Booted with "minimalist setup" of no GPU, no drives, only one RAM stick, CPU, CPU cooler, PSU, motherboard.
Turned off Windows "Fast startup" and turned off BIOS "fast boot". (turning off the Windows fast startup actually caused a whole other issue that makes me hesitant to do it again after many arduous hours finally resulted in me successfully reinstalling the OS to still encounter the issue(albeit with fast startup back on by default after reinstallation))
🔍
What I Noticed
The issue has essentially persisted since the first "reboot" of the first Windows installation attempt after swapping the parts.
Once I manage to get it booted, it runs solid for hours — no crashes, no hiccups — until I restart(or shutdown) or let it sleep.
Monitors briefly turn on, flick through their sources(doesn't matter if it's on auto source or not, I tried manually setting source as well), and then go No signal and go "off"(orange lights) when the issue occurs.
Keyboard LEDs turn off and is unresponsive. Only behavior is if a key is pressed the lights flicker on for literally less than a second and only does so if a key is tapped but does not remain on.
Only a "hard shutdown" or full power drain resets it and gets things working again (until next restart, shutdown or sleep).
⚠️
Current Status
Issue still occurring.
🤝
Looking for Help
Some insight into how to fix this or at least obtain more information on what could be causing it
Temporary fix even would be appreciated (I've already considered setting "go to sleep mode" to "Never" in Windows power settings to negate it from happening when I briefly step away during regular usage)
Is this a "no POST" issue? It seems abnormal in comparison to other cases of "no POST".
A miracle would be appreciated too.
Thank you for your consideration and help. It is muchly appreciated for you to attempt to assist me with this matter via online forum to help me avoid expenses of having to make an in person visit to a local shop.
S
Sakura_trick
08-15-2023, 04:18 PM #1

Hi Everyone,
I just recently did some major upgrades on my system and after numerous stressful days of troubleshooting I have achieved a somewhat stable state that has allowed me to try and relieve some of the stress through relaxation on my PC but there is a lingering anxiety related to a couple (possibly related?) issues remaining.
🖥️
System Specs
Original Setup (Before Swapping Anything):
CPU:
Intel Core i5-9600K 3.7 GHz 6-Core Processor
GPU:
Asus STRIX GAMING OC GeForce RTX 2070 8 GB Video Card
Motherboard:
ASRock Z390 Pro4 ATX LGA1151 Motherboard
RAM:
Corsair Vengeance RGB Pro 32 GB (2 x 16 GB) DDR4-3600 CL18 Memory
Storage:
Samsung 860 Evo 250 GB 2.5" Solid State Drive
(OS drive)
Seagate BarraCuda 2 TB 3.5" 7200 RPM Internal Hard Drive
Seagate BarraCuda 6 TB 3.5" 5400 RPM Internal Hard Drive
Samsung 980 Pro 2 TB M.2-2280 PCIe 4.0 X4 NVME Solid State Drive
PSU:
Corsair RM750x (2018) 750 W 80+ Gold Certified Fully Modular ATX Power Supply
OS:
Windows 11 Home (24H4 I think?)
After Swaps/Upgrades:
CPU:
Intel Core i7-14700K 3.4 GHz 20-Core Processor
GPU:
Asus ROG STRIX GAMING OC GeForce RTX 5070 Ti 16 GB Video Card
Motherboard:
Asus TUF GAMING Z790-PLUS WIFI D4 ATX LGA1700 Motherboard
PSU:
Corsair RM1000x (2024) 1000 W Fully Modular ATX Power Supply
OS:
Windows 11 Home (formatted OS drive and reinstalled Win11 from Microsoft media installer)
⚠️
The Problem
I've seen similar posts on here of similar issues but nobody seems to be encountering the exact same thing I'm encountering. Each post seems to have some minor aspect that is different and makes their issue seemingly different than mine.
Essentially what I am encountering is an issue in which my display does not return after a reboot or going into sleep mode, as well as sometimes even after graceful shutdowns. The issue goes like this: the system reboots either from myself hitting the restart, BIOS rebooting after a "save changes and reset", OR the system goes into sleep mode after inactivity. Once the system reboots, or I click or press a key on my keyboard to awake it, the component RGB comes on, the fans start spinning etc, and then I see the debug lights go through the CPU one and then the DRAM, the DRAM light
goes away
(seems to differ from other similar issues I've seen people post about), but the next two lights of VGA and BOOT never turn on. The keyboard's unresponsive, as is the mouse, no LEDs on the keyboard after the initial "tap of the keys" to wake the system and no display on either monitor.
The system seems to work normally only if I have it turn back on after the reboot, or come back awake from sleep mode, wait for it to go through the first two debug lights of CPU and DRAM and then once it fails to proceed after that, I hold down the power button to turn off, wait for the fans to stop spinning, and then turn it back on with the power button. The lights then go through CPU, DRAM, small second or two hesitation and a click sound, VGA and then BOOT with the display appearing and the keyboard LEDs coming on and functioning, etc. (essentially a successful boot). This then seems to be completely functional until I next shutdown, restart or allow it to go into sleep mode.
I mentioned that it also seems to occur after normal graceful shutdowns, which also seems to differ from many others I have seen encountering similar issues. To clarify, I shutdown normally through Windows, and then no matter the time period whether it's immediate or hours later or the next day, when I turn it back on, I go through the cycle again of allowing it to fail to reach BOOT and then holding the power button to turn it off, turning it back on, etc, to reach that "stable" useable state.
The problem seems to be related to how the system handles restarts or wakes from sleep, and I’m unsure of what's causing it and frankly have reached my wit's end.
🔧
Things I Tried
Reset CMOS through "shorting" the pins and pulling the CMOS battery and waiting 10+ minutes
Flashed BIOS (BIOS Flash from USB latest version 1820)
Re-seated RAM
Reinstalled Windows 11 (although it occurs after restart from BIOS/UEFI as well so I don't think it'd matter)
Booted with "minimalist setup" of no GPU, no drives, only one RAM stick, CPU, CPU cooler, PSU, motherboard.
Turned off Windows "Fast startup" and turned off BIOS "fast boot". (turning off the Windows fast startup actually caused a whole other issue that makes me hesitant to do it again after many arduous hours finally resulted in me successfully reinstalling the OS to still encounter the issue(albeit with fast startup back on by default after reinstallation))
🔍
What I Noticed
The issue has essentially persisted since the first "reboot" of the first Windows installation attempt after swapping the parts.
Once I manage to get it booted, it runs solid for hours — no crashes, no hiccups — until I restart(or shutdown) or let it sleep.
Monitors briefly turn on, flick through their sources(doesn't matter if it's on auto source or not, I tried manually setting source as well), and then go No signal and go "off"(orange lights) when the issue occurs.
Keyboard LEDs turn off and is unresponsive. Only behavior is if a key is pressed the lights flicker on for literally less than a second and only does so if a key is tapped but does not remain on.
Only a "hard shutdown" or full power drain resets it and gets things working again (until next restart, shutdown or sleep).
⚠️
Current Status
Issue still occurring.
🤝
Looking for Help
Some insight into how to fix this or at least obtain more information on what could be causing it
Temporary fix even would be appreciated (I've already considered setting "go to sleep mode" to "Never" in Windows power settings to negate it from happening when I briefly step away during regular usage)
Is this a "no POST" issue? It seems abnormal in comparison to other cases of "no POST".
A miracle would be appreciated too.
Thank you for your consideration and help. It is muchly appreciated for you to attempt to assist me with this matter via online forum to help me avoid expenses of having to make an in person visit to a local shop.

R
Robang592
Senior Member
368
08-24-2023, 01:16 PM
#2
When you started building on the breadboard, I assumed you removed the motherboard from the PC case, correct? Was the same POST problem still occurring? If yes, then the problem likely lay with one of these areas (or possibly all): CPU, Motherboard, RAM, Power Supply.

I would reattach the motherboard to the PC case once more to test it further on the breadboard.

Disconnect everything except: CPU, CPU cooler, and one RAM DIMM. Attach the monitor to the motherboard to view the status. Keep only the keyboard and mouse connected. Also connect the 24-pin ATX PSU and the 8-pin EPS.

The goal is to bypass POST and successfully boot into BIOS (UEFI) without issues.

Some suggestions you might consider:
RAM
For RAM, download and run memtest86:
https://www.memtest86.com/
Follow the instructions here:
https://www.memtest86.com/tech_creating-window.html
A single full pass (all 15 tests) is the minimum. Two passes are better, and four passes are acceptable. It’s best to let it run overnight.

1x 8GB RAM takes about 1 hour per full pass – around 4 hours for four passes.
2x 8GB RAM takes roughly 2.5 hours per pass – about 10 hours for four passes.
2x 16GB RAM takes about 5 hours per pass – around 20 hours for four passes.
If no errors appear, the RAM is fine.

PSU
To check for PSU problems, connect your old RM750x and see if the same POST issue occurs.

The CPU can only be tested inside the operating system, which is tricky. Even a single CPU test might not reveal anything incorrect. The motherboard cannot be tested at all.

Personally, I suspect the issue is with the motherboard. It could relate to VRMs or control chips – hard to pinpoint.

Regarding the VRMs, the specifications mention 16+1 VRM configured for 60A with Dr.MOS. However, counting individual chokes suggests there are 19, not 17. That seems inconsistent.

Also, the VRM heatsinks don’t fully cover the chokes. But that’s a side note.

Last resort, take your CPU-Motherboard-RAM setup to a repair shop for diagnostics.
R
Robang592
08-24-2023, 01:16 PM #2

When you started building on the breadboard, I assumed you removed the motherboard from the PC case, correct? Was the same POST problem still occurring? If yes, then the problem likely lay with one of these areas (or possibly all): CPU, Motherboard, RAM, Power Supply.

I would reattach the motherboard to the PC case once more to test it further on the breadboard.

Disconnect everything except: CPU, CPU cooler, and one RAM DIMM. Attach the monitor to the motherboard to view the status. Keep only the keyboard and mouse connected. Also connect the 24-pin ATX PSU and the 8-pin EPS.

The goal is to bypass POST and successfully boot into BIOS (UEFI) without issues.

Some suggestions you might consider:
RAM
For RAM, download and run memtest86:
https://www.memtest86.com/
Follow the instructions here:
https://www.memtest86.com/tech_creating-window.html
A single full pass (all 15 tests) is the minimum. Two passes are better, and four passes are acceptable. It’s best to let it run overnight.

1x 8GB RAM takes about 1 hour per full pass – around 4 hours for four passes.
2x 8GB RAM takes roughly 2.5 hours per pass – about 10 hours for four passes.
2x 16GB RAM takes about 5 hours per pass – around 20 hours for four passes.
If no errors appear, the RAM is fine.

PSU
To check for PSU problems, connect your old RM750x and see if the same POST issue occurs.

The CPU can only be tested inside the operating system, which is tricky. Even a single CPU test might not reveal anything incorrect. The motherboard cannot be tested at all.

Personally, I suspect the issue is with the motherboard. It could relate to VRMs or control chips – hard to pinpoint.

Regarding the VRMs, the specifications mention 16+1 VRM configured for 60A with Dr.MOS. However, counting individual chokes suggests there are 19, not 17. That seems inconsistent.

Also, the VRM heatsinks don’t fully cover the chokes. But that’s a side note.

Last resort, take your CPU-Motherboard-RAM setup to a repair shop for diagnostics.