PC sometimes won't wake up from sleep mode, red + yellow lights on MB

hupimies2151a02d0

New member
Joined
Sep 22, 2024
Messages
6
Board: X670E Tomahawk WIFI
BIOS: 7E12v1E
GPU: AsRock RX 7900 XT Phantom Gaming OC
CPU: Ryzen 7 7800X3D
Cooler: Noctua NH-D15
RAM: 2x16GB Corsair Vengeance 6000MHz
SSD: Samsung 2TB 990 PRO
PSU: Corsair 850W RM850x
SYS: Windows 11 Home x64 Ver. 10.0.22631

About 7/10 times the pc wakes up normally from sleep mode, during which red and yellow light on motherboard (CPU, RAM) flash. 3/10 times the lights light up for about 30 seconds, after which they turn off about the same time. After this only black screen, USB devices get power (leds on mouse light up, not on keyboard) but no other connection. Have waited for over 30 minutes, no change. Always gets fixed by forced shutoff via holding down the power button, after this boots up to saved state (previous applications open etc.) No problems on regular startup.

Worked normally for about a year, problem started a few months ago suddenly. Didn't disconnect or open up the PC / download any software / do anything else notable which could have caused system change. All temps during benchmarks normal and no problems during running. PC has never crashed etc.

List of things that have not fixed the problem:

Updated BIOS
Reset BIOS settings through BIOS menu, haven't cleared CMOS with jumping
Updated GPU drivers
Updated Windows from 10 to 11
Reset Windows power settings through troubleshooting
Turned off fast startup
Unplugged and reconnected PSU (also removed and reconnected GPU, didn't try to boot without it)
RAM are in slots A2 and B2 per the manual, as they have always been

Not a huge problem, but very annoying since I primarily keep PC in sleep mode. Also have to think that constant forced shutoff doesn't do the PC any favors. Any thoughts on possible fixes? Could clearing CMOS have any other effect than resetting through the BIOS menu does?
 
I can confirm that clearing CMOS and enabling only EXPO/XMP doesn't fix the issue, I've done it on multiple occasions after the issue started. I'll give the memory context restore setting a try.
 
you should try with both settings MCR and Power Down enabled
or, if it doesn't work,
with BOTH settings disabled, even it this means a little longer training process it's usually much more reliable
 
I’m experiencing a similar issue with my setup:
  • CPU: AMD Ryzen 5 7600X
  • RAM: ADATA XPG Lancer Blade RGB [AX5U6000C3016G-DTLABRBK] 32GB
  • Motherboard: MSI MAG X670E TOMAHAWK WIFI
After putting my system to sleep or rebooting, the red and yellow LEDs on the motherboard light up. The only way to get my PC to start again is by holding down the power button for 3-5 seconds for a cold boot.

I have disabled EXPO and tried different combinations of MCR and Power Down settings, enabling and disabling both, but the problem persists. My BIOS version is 1.E0, dated 07/26/2024.
 
So I tried these tests:
  • 4800MT/s with custom primary/secondary/tertiary timings - Fail to wake up​
  • 4800MT/s with all auto timings - Fail to wake up​
  • 4800MT/s with all auto timings & Power Down enabled - Fail to wake up on second try​
So neither speed nor timings make a difference.
  • ​
 
So I tried these tests:
  • 4800MT/s with custom primary/secondary/tertiary timings - Fail to wake up​
  • 4800MT/s with all auto timings - Fail to wake up​
  • 4800MT/s with all auto timings & Power Down enabled - Fail to wake up on second try​
So neither speed nor timings make a difference.
  • ​
I have all of these disabled: XMP, MCR, Power Down, iGPU, Asmedia Sata Controller, fTPM. Also I'm on BIOS 7D75v174(Beta version). Boot time is very bad.
Also I have PBO enabled and -20 Curve Optimizer (not sure if PBO has anything to do with this).

I still have had 100% success rate waking from sleep so far... RAM is 4800 MHz now lol.

I compared god of war Ragnarok performance with these two settings:
XMP 6400 MHz, UCLK = MCLK (3200 MHz), FCKL 2133
god of war Ragnarok: 217 FPS
Pybench: 17.14 seconds

cachemem6400-1-1-2133.png



XMP disabled, 4800 MHz, FCKL 1800
god of war Ragnarok: 216 FPS
Pybench: 17.74 seconds

cachemem4800.png


I don't know, I think I will keep XMP disabled forever lol. I see 0 benefits in being unable to sleep the PC in 2024. I repeat, unable to sleep the PC in 2024.
 
Following up of this ticket:
Ticket:
It seems X3D CPUs cannot resume from sleep if XMP/EXPO enabled.

Content:
Regarding your concern, please clear CMOS (How to clear CMOS. Please refer to the manual) for a try, then only enable the XMP in bios to check. If the issue still persists, please manual enable the memory context restore (BIOS>Overclocking) option in bios for a try.
New answer:
Ticket:
1130434It seems X3D CPUs cannot resume from sleep if XMP/EXPO enabled.
[above didn't work]
Content:
Thank you for your information, you can manual adjust a bit of ram voltage or CPU voltage for a try. If it does not work, the latest bios version of the motherboard is v1L1, please also update the bios to latest version from MSI Website. Please update the bios by M-Flash in bios.

I placed this here for others if they wished to do so. As for me, I think I'm fine with XMP disabled. It seems mostly theoretical benchmarks such as AIDA64 benefit from 6000 MT/s anyway. I'm not seeing any benefit in real workloads (gaming workload!). There is also a new problem emerging for me now: very rarely after a cold boot, PC is stuck in a black screen and will not progress. Have to shutdown and turn it on again to work! Maybe 4800 MT/s is too low now lol.
 
Following up of this ticket:

New answer:
Ticket:
1130434It seems X3D CPUs cannot resume from sleep if XMP/EXPO enabled.
[above didn't work]
Content:
Thank you for your information, you can manual adjust a bit of ram voltage or CPU voltage for a try. If it does not work, the latest bios version of the motherboard is v1L1, please also update the bios to latest version from MSI Website. Please update the bios by M-Flash in bios.

I placed this here for others if they wished to do so. As for me, I think I'm fine with XMP disabled. It seems mostly theoretical benchmarks such as AIDA64 benefit from 6000 MT/s anyway. I'm not seeing any benefit in real workloads (gaming workload!). There is also a new problem emerging for me now: very rarely after a cold boot, PC is stuck in a black screen and will not progress. Have to shutdown and turn it on again to work! Maybe 4800 MT/s is too low now lol.
Yeah, for most gaming purposes 32gb of DDR5 at 4800MHz is way more than enough. I'm pretty confident that nothing that MSI tech support might recommend will fix the issue since this seems to be a deeper hardware-level problem. There are also lots of reports of other boot problems with X3D CPU's as well. As I said before, probably the best bet is to wait for a software fix for these minor issues, unless someone is really really motivated to use sleep mode and run their RAM at higher speeds. Seems like a lot of effort for not much of return.
 
Manually enabling the memory context restore setting doesn't fix the issue, as expected. Woke up fine twice and then failed on the third go.
Hello,
Have you ever tried set manually CHIPSET Core Voltage and CHIPSET 1P8 Voltage in OC Settings. Can you try set these voltages manually, you can see the default values, try to slightly decrease voltages and check if it works. You can start with 1.750 or 1.775 for CHIPSET 1P8 and 1.050 or 1.025 for CHIPSET Core Voltage.
@steven.kis155902d6 I have also same mobo with you, If you want you can try the solution I mentioned above.

​

 
Last edited:
Hello,
Have you ever tried set manually CHIPSET Core Voltage and CHIPSET 1P8 Voltage in OC Settings. Can you try set these voltages manually, you can see the default values, try to slightly decrease voltages and check if it works. You can start with 1.750 or 1.775 for CHIPSET 1P8 and 1.050 or 1.025 for CHIPSET Core Voltage.
@steven.kis155902d6 I have also same mobo with you, If you want you can try the solution I mentioned above.

​

can you explain the logic behind this?

I have a Gigabyte b650i and 7800x3d and the EXACT same issue. I thought it was the ram and I changed a 32gb ddr5 6000 corsair vengeance cl36 for a 64 kit cl30 and it is still acting the same. Tried MCR on auto or off together with power down mode and I still get the system stuck with the power botton light on, funny thing I've noticed is that my GPU light won't turn on (4080 super founders) when the PC does not wake up from sleep, but all fans are working. I had a 3090ti before and same issue, I thought it was a problem with my OLED g8 monitor, now I have the g9 so it was not that. I also had the 7600x before and this issue was also present. 🫠

For it to work I need to press the reset button and PC would do a cycle and start up normal. No BSODs or anything. Have tried without negative curve PBO on CPU, still the same. The only thing I have not tried is disabling EXPO( previous RAM had XMP) but that wouldn't help since 7800x3d works best at 6000mhz and I use a simulator that performs a lot better that way, which should be supported.
 
can you explain the logic behind this?

I have a Gigabyte b650i and 7800x3d and the EXACT same issue. I thought it was the ram and I changed a 32gb ddr5 6000 corsair vengeance cl36 for a 64 kit cl30 and it is still acting the same. Tried MCR on auto or off together with power down mode and I still get the system stuck with the power botton light on, funny thing I've noticed is that my GPU light won't turn on (4080 super founders) when the PC does not wake up from sleep, but all fans are working. I had a 3090ti before and same issue, I thought it was a problem with my OLED g8 monitor, now I have the g9 so it was not that. I also had the 7600x before and this issue was also present. 🫠

For it to work I need to press the reset button and PC would do a cycle and start up normal. No BSODs or anything. Have tried without negative curve PBO on CPU, still the same. The only thing I have not tried is disabling EXPO( previous RAM had XMP) but that wouldn't help since 7800x3d works best at 6000mhz and I use a simulator that performs a lot better that way, which should be supported.
I was facing similiar issue about one years. While pc works properly, I didnot get any error, BOSD or unstable behaviour even when it fully load (benchmark, render, machine learning model training with both cpu and gpu). But system is not get works properly when cold boot or restart. It was a power problem, some times it works fine some time it is not. Chipset is the main component that make works everything on mobo like usb ports, onboard wifi cards, rgb lights, M2 lanes etc. Somehow, auto mode cannot set proper value for chipset when power off but resetting power cycle or reset the pc can helps to solve this issue. So, setting these voltages manually is ensures the chipset get proper voltage for every time. After setting this value manually, my computer hasn’t given any errors, even if I restart, wake it from sleep, or unplug and plug it back in. It always works right away, and I haven’t had any issues like not detecting Wi-Fi or USB ports.
PS: I was sure there was no problem with my CPU or RAM because once the computer was running, I didn’t experience any errors or stability issues until I shut it down. Whatever was happening, it was occurring when the computer tried to restart, power off or waking up, and it was preventing the system from working properly.
 
I was facing similiar issue about one years. While pc works properly, I didnot get any error, BOSD or unstable behaviour even when it fully load (benchmark, render, machine learning model training with both cpu and gpu). But system is not get works properly when cold boot or restart. It was a power problem, some times it works fine some time it is not. Chipset is the main component that make works everything on mobo like usb ports, onboard wifi cards, rgb lights, M2 lanes etc. Somehow, auto mode cannot set proper value for chipset when power off but resetting power cycle or reset the pc can helps to solve this issue. So, setting these voltages manually is ensures the chipset get proper voltage for every time. After setting this value manually, my computer hasn’t given any errors, even if I restart, wake it from sleep, or unplug and plug it back in. It always works right away, and I haven’t had any issues like not detecting Wi-Fi or USB ports.
PS: I was sure there was no problem with my CPU or RAM because once the computer was running, I didn’t experience any errors or stability issues until I shut it down. Whatever was happening, it was occurring when the computer tried to restart, power off or waking up, and it was preventing the system from working properly.
would the values be the same for my motherboard?. It's scary to think I could fry something
 
would the values be the same for my motherboard?. It's scary to think I could fry something
Actually you cannot fry because you are doing undervolt. Although you can set these values manually, there is a range for every value you cannot exceed these (it shows on the screen while you are setting in BIOS). Yes default values are the same for AM5 chipsets, the worst case senario is you cannot get any display, you can easily clear CMOS with removing bios battery and all settings get back to the default BIOS values. Firstly, just try to decrease Chipset 1P8 voltage and check if it works.
 
Last edited:
Actually you cannot fry because you are doing undervolt. Although you can set these values manually, there is a range for every value you cannot exceed these values (it shows on the screen while you are setting in BIOS). Yes default values are the same for AM5 chipsets, the worst case senario is you cannot get any display, you can easily clear CMOS with removing bios battery and all settings get back to the default BIOS values. Firstly, just try to decrease Chipset 1P8 voltage and check if it works.
I'll definitely try that and come back with observations. thank you
 
I have SOC voltage set at 1.23v for 6000MT/s with custom timings. Any lower and memory stress test in ycruncher VT3 test fails. As for Chipset 1P8 voltage it was set to Auto. According to BIOS the default is 1.8v. I manually set it to 1.8v. It didn't do any difference with waking up from sleep but it did introduce a problem so I reverted back.

Does anyone else have the iGPU enabled? I have the second display and sometimes the soundbard connected to the iGPU so I only have the main monitor connected to the dGPU. It might be that fail to wake up from sleep happens more frequently with iGPU enabled but that is just a theory.
 
I have SOC voltage set at 1.23v for 6000MT/s with custom timings. Any lower and memory stress test in ycruncher VT3 test fails. As for Chipset 1P8 voltage it was set to Auto. According to BIOS the default is 1.8v. I manually set it to 1.8v. It didn't do any difference with waking up from sleep but it did introduce a problem so I reverted back.

Does anyone else have the iGPU enabled? I have the second display and sometimes the soundbard connected to the iGPU so I only have the main monitor connected to the dGPU. It might be that fail to wake up from sleep happens more frequently with iGPU enabled but that is just a theory.
I have iGPU disabled and this keeps happening to me. At this time I sent my PC to sleep yesterday night and today it woke up with the 1P8 set to 1.760. Too early to tell but will keep observing.
 
Does anyone try update for the last bios, load defaults and just enable ErP?
the other days it was noticed that after Win10 shutdown the PC some unusual voltages still present on MB. like MB is in half sleeping mode.
to resolve that issue sleeping mode in Win10 need to be completely disabled and using hibernation instead.
i have EXPO on, Power down enable, Gear down mode and MCR all in auto on my MB. only one nvmeinstalled and rtx4070S.
 
Last edited:
@hupimies2151a02d0
so all those things you tried and "wasted" time on, ignoring possible issues bricking something, if the power goes out, while not gaining anything (from using sleep)
except maybe a couple of seconds less time to get to the desktop, all while consuming "more" power.
all fixed easily, by shutting down the pc, so why not just do that?

unless i missed something, it usually takes about ~30s to boot to desktop on win OS (7-11), so not something messing up your schedule, ignoring i can turn on the pc
and do something else for 1 min, so to not "waste" time, if i wanted to.
 
Back
Top