Ryzen restarts when idle – issue resolved? (RMA)
Ryzen restarts when idle – issue resolved? (RMA)
Updated Feb 3 I began the RMA procedure for the 5950x. To prepare for an uncertain period without a CPU, I purchased a 5600x at Micro Center. I swapped my 5950x for the 5600x and reset it back to BIOS defaults (which activated Global C-State Control) while also turning on PBO and XMP. Using the same hardware (except the new CPU), the idle shutdown/reboot problems and WHEA errors have disappeared. I’ll monitor it closely, but currently it seems stable—reliable restarts every few hours without needing any adjustments. Settings like memory power down mode, C-States, voltage offset, or PBO curve are unnecessary. It’s functioning fine so far. I’ll keep you informed about stability and RMA timelines. Thanks again for your support. It’s been really tough, but I’m much happier with this supportive community.
It marks progress in the right area. I hope the swap works smoothly without issues. The certainty is clear—the 5950X handles power delivery well under load. It's not about voltage, but about how much current it can supply. Likely it will meet the EDC power cap when operating at full demand.
The 5950x shows a vastly different power consumption pattern under heavy load compared to the 5600x. You can easily exceed the EDC limit and reach temperatures near 90°C even with good water cooling. That’s what made this problem so annoying—the only time my system stayed stable was when I wasn’t running stress tests. Once those tools were active, fans slowed and cores powered down, creating the risk of crashes and unexpected reboots.
Lol. Have been there many times. But haven't bought into 3000 or 5000 series chips. The one thing I noticed when "tweaking" Zen and Zen+, the reference clock dips on too much under-volt to compensate. This reduces consumption slightly, but at risk of transistors stopping. The SOC also another chip that likes to leak and really doesn't appreciate much under-volt might make a system unstable perhaps from a momentary droop. WHEA errors also a low volt deal on the Cpu core. I often wondered if anyone has tested the hang and whea errors with SMT disabled for any length of time. No surprise would it be a bump in v-core cures the issue with all threads running. I suppose there's quite a bit to it all. In conjunction with board and memory combinations, anything can happen.
RMA procedure and experience summary: On Sunday, Jan 31 at 5pm I filed the initial RMA form. By 8pm Sunday, Jan 31 I got an automated confirmation with a service ticket. On Wednesday, Feb 3 at 5:45am I received a response from AMD support asking for a photo of the CPU in the MOBO (with cooler removed and model visible), the original invoice (PDF), the MOBO make/model/bios details, and a description of the issue plus troubleshooting steps. At 3:35pm on Feb 3 I replied with the requested info. By 3:37pm I got an automated update confirming new service details. Around 9:57pm I received the "RMA Approved" message with full information. A FedEx Ground label was sent to my email separately. On Thursday, Feb 4 at 8am I shipped the unit using the provided label (delivered to a FedEx Office location). The CPU arrived back in its original plastic clamshell and also in a sturdy cardboard box with extra bubble wrap and foam for protection. On Friday, Feb 8 at 1pm I was told the RMA was approved. By 3:20pm on Feb 9 I got confirmation that my processor was received at the Miami service center. The next morning, Feb 9 at 6:47am, I received another update noting no tracking number was given—only the RMA and serial numbers for tracking. Around 7:20pm I had a shipping label from the service center (2-day FedEx). The package wasn’t delivered yet by FedEx. By Thursday, Feb 11 at 5:04pm FedEx picked up the package from the service center. Delivery was expected by Monday, Feb 15. On that Monday, Feb 15 at 9:07am FedEx arrived (required signature). The new CPU came in a full retail box. The batch number is 2104PGS, produced during the fourth week of January 2021 in Penang. My previous unit was 2043PGS, made Oct 19-25, 2020 in Penang. I’ll replace my old CPU later today and update this thread once testing is complete.
Hi everyone, this is my first post in this forum. I unable to post to ASUS or G. Skill forum because of the activation process is taking eons, anyways I'm not here to rant about that xD Setup NZXT H710i CPU AMD Ryzen 5 5600XT in exchange of Ryzen 5 3600 while waiting for 5950x stock... MB Asus ROG CROSSHAIR VIII DARK HERO RAM G.Skill Trident Z Neo DDR4 3600 PC4-28800 64GB 4x16GB CL16 (F4-3600C16Q-64GTZNC) GPU PowerColor Red DEvil RX5700XT 8GB SSD Samsung 980 Pro M.2 1000 GB Cooler AIO NZXT Kraken X73 360 mm PSU Corsair HX1200W Platinum First at all, @mtavel I have the vary same symptoms, my PC can handle stress tests forever, CPU, RAM, GPU under 100% no problem with or without XMP profiles, stock OC, PB, PBO whatever. But!!! idle oh man.... idle with XMP default settings is a real nightmare as you've proved on your on flesh... While debugging I've also seen the WHEA errors, 4 in total. I thought my provisional Ryzen 5 3600 was faulty and cannot handle 3600Mhz RAM so I exchange it in the store for the Ryzen 5600XT, but unfortunately the issues persist... I also have the Dark Hero motherboard with the latest BIOS 3204 , but this error also happens with the stock BIOS which in my case was 2601. So, for this last week I was scraping the whole internet reading about Ryzen issues related to XMP profiles and low voltages in power saving modes... I found this thread from the same guy in Asus and G. Skill forum. He fixed this issue increasing DRAM voltage from default 1.35 to 1.36. What I don't know is what he exactly means by "system instability", idle, random crashes?? I cannot ask him because of the account activation issue.... As I'm writing my PC is "idleing" with default BIOS settings and XMP activated + DRAM voltage set to 1.36. I'll check if this helps in a couple hours after sleep. Normally the PC freezes in about ~2h idle. I have few questions for you @mtavel . What is the exact model of your RAM? Your PC reboots, freezes??? Did it throw any Q-Code? Mine completely freezes, USB stop working, monitor goes black with "No displayPort signal" error and I have to push the switch on the PSU and boot the PC again... Also the Q-Code on the motherboard is 00 and the DRAM led is on with yellow color. For me is hard to believe that the RAM modules are defective. If it was the case I probably would have POST issues, stress tests like MemTest86 for 8h should crash... One last thing. Do you have Asus AI Suite 3 installed or any Asus software?? I have it all running and what I've noticed in the event viewer after every crash there is an DipAwayMode.exe regarding I have disable it from the AI Suite software... Can you check your Event Viewer for "UserPowerMode" in INFO level calling -> C:\Program Files (x86)\AI Suite III\DIP4\DipAwayMode\ DipAwayMode.exe ??? If tonight test at DRAM v1.36 works fine tomorrow I'll test again with v1.35 and AI Suite uninstalled and DipAwayMode removed from Windows Task Scheduler. No matter if you disable it in the interface this task is still running on the system if you're logged in... I'll keep posting new info. (Hope your new 5950x arrives fast...) GN
I encountered similar issues with the same hard hangs you mentioned, including the 00 Q-Code. I had to power down the PC at the power supply to recover. These problems started when I was adjusting the positive Curve Optimizer offset on the worst core to stabilize it, but occasional hard hangs persisted. Eventually, I gave up trying to fix my 5950x, which clearly had a binning error. The only solution that helped was disabling C-states. There were some event viewer entries linked to UserModePowerService, but none related to AI Suite 3 or other ASUS applications (which are installed). These seem to be caused by other infrequent app crashes, unrelated to my reboot issues.
This seems to be a helpful guide pointing out the correct part number and offering support. The advice suggests checking the memory kit with the same part number but without the C at the end, indicating a possible issue with the memory module. It also provides a link for further assistance.
For your device, this model uses a RAM configuration similar to MTavel—remove the C from the part number. https://www.newegg.com/g-skill-64gb-288-...6820232864
The problem lies with the memory kit itself. I resolved it by disabling Global C-States on the CPU, which fixed the idle state reboots I was experiencing. After switching from a 5950x to a 5600x and using the same memory, the system ran smoothly without any issues. Now I’m considering replacing the 5950x with a newer model.