Computer stops responding after long periods
Computer stops responding after long periods
Hello everyone, I'm facing an unusual issue that's been puzzling me. My partner's PC functions normally after about a month since we set it up. It handles posts, runs games, and restarts properly. However, if we power it off (for example, in the evening) and try to boot it the next day, it fails completely. Turning off the PSU briefly and then restoring it works again. Also, shutting it down and restarting within an hour restores posting. We're still unsure about the exact timing window—likely between 2 and 9 hours—but we've checked various configurations.
Specifications:
- RAM: ASRock X670E Pro RS
- CPU: AMD Ryzen 5 7600 X3D
- Memory: G.Skill 32GB (2x16) DDR5-6000, placed in recommended A2 and B2 slots per the manual
- Power Supply: Seasonic Focus GX1000
- GPU: XFX RX7900XT
- OS: Ubuntu 24.10 x64
We've tried different setups—single sticks in B2 or A2/B1, dual in A1/B1—and everything works fine when using just one stick. After some time, single sticks in A2 behave like single in B2, and dual in A1/B1 don't post at all. We updated the BIOS and cleared CMOS. All cables seem properly seated.
Debug LEDs for CPU and DRAM stay lit if power is cut for 30 seconds or capacitors drain. It seems that briefly interrupting power can resolve the issue. Any suggestions? I'm a bit confused about whether cutting power at the PSU alone fixes it, especially since the error disappears when the system is restarted.
What i could logically think of is that the computer is not entirely shut down, something is charging up your motherboard but very slowly till it thinks its shorted and refusing to boot up to keep your hardware intact. Can you attempt to switch PSU and see if issue presist. Good luck!
Thank you for your reply - I will test it as soon as I can borrow a compatible PSU (don't want to buy one for debugging). Nonetheless: If this is the problem why does it work without a problem when you use one stick either in A2 or B2? Shouldn't it be the same behavior then ? Also: It DOES turn on, we see fans spinning and the debug leds turn on but they get stuck on CPU/RAM. If it is a motherboard protection for shorts or whatever, shouldn't it be not turning on at all? It just gets stuck in POST itself which would be a bit late for a over/under current/voltage or short protection...
During the weekend we managed to fix a few more issues. We changed the PSU and the problem still remained. Another note: The debug-LEDs activate first when powering up, even after a successful POST or boot. On a proper start, they light up first, then the other one, and both turn on simultaneously. This suggests the POST might fail before memory initialization. Someone with suggestions would be helpful. I don’t want to send all three specs (CPU, MB, RAM) since those errors are tough to reproduce and they might just return because it works for me. What do you think is most likely broken to replace first? If booting works fine with one stick of memory, I’d probably start there...
Check the BIOS settings and ensure the Deep Sleep option is turned off. Refer to Page 47 of the Software_bios configuration manual. The issue stemmed from an incompatible older power supply that prevented proper Deep Sleep S4/S5 functionality, causing the PC to fail to restart without manually switching power on and off before it restarted after being off.
Apologies for the delayed response—I was on a business trip for a few days. Just verified the settings; it's currently disabled, which matches our previous actions of resetting CMOS during debugging and after the BIOS update. Thanks for the suggestion!