Overclock.net banner

My system with a Ryzen 5000 CPU reboots with BIOS defaults

Replaced 3950X with 5950X = WHEA and reboots

2 reading
356K views 1.7K replies 217 participants last post by  ErikTechie  
#1 · (Edited)
Hello,

Please vote on the pool only if your system is not stable with BIOS defaults, memory at 2133 Mhz without XMP, without any CPU or RAM overclocking, without PBO or any voltage tweaks and of course, if you do not have any issues with your Ryzen 5000 or your problem has been fixed.
* you can select 2 values.
Motherboard+CPU if you have issues.
No, I tested extensively for several days+CPU if you do not have issues.

It did, but *+CPU if your issue has been fixed.

See https://www.overclock.net/threads/replaced-3950x-with-5950x-whea-and-reboots.1774627/post-28698010 for the solution to my issue.


I bought the new AMD Ryzen 5950X to replace my AMD Ryzen 3950X.
This is the only new component in the system. The rest of the components are in the signature.


Problem

As soon as I booted up to Windows, the system started rebooting and crashing, sometimes with the BSOD WHEA Uncorrectable Error​


What I tried

Long story short:
  1. I have replaced every component except the CPU and the motherboard.

Long story:
  1. removed all RAM sticks and tested with only one at a time in different memory slots.
  2. tested with memory at 2133 Mhz auto timings, XMP and manual timings without XMP.
  3. took out my RAM and tested with one stick of G-Skill F4-2400C15S-8GNS and one KIT of 2 sticks Corsair CMK8GX4M1A2400C16.
  4. replaced the PSU with a Corsair AX760i
  5. removed any other USB devices besides mouse and keyboard
  6. tested with only a Bluetooth mouse. No other USB connected.
  7. removed any other HDD and SSD besides the system/windows one.
  8. replaced the system/Windows SSD and tried reinstalling Windows. Crashes while installing.
  9. removed the CPU to check for bent pins with a magnifying glass. Twice. All good.
  10. downgraded BIOS to version F30.
  11. re-flashed BIOS version F31e.
  12. upgraded BIOS to F31h, F31i, F31k, F31l, F31n, F31o, F31
  13. cleared CMOS and tried booting without setting anything in BIOS.
  14. booted Ubuntu 20 Desktop live USB. Crashes before desktop with some cryptic error about CPU.
  15. checked CPU and motherboard temperatures. All fine.
  16. reseated the GPU.
  17. tested with an RX 460 GPU instead of GTX 1080 ti.
  18. tested with an RX 590 GPU instead of GTX 1080 ti. Takes longer to crash than with the GTX 1080 ti on BIOS version F31n.
  19. disabled C-States
  20. disabled HPET-Timer
  21. forced PCIe to gen 2/3/4
  22. disabled AMD Cool&Quiet
  23. disabled PBO (always have it on Auto anyway)
  24. removed all SSDs and HDDs and tried booting from Ubuntu live USB
  25. tried all levels of LLC
  26. Enabled Preferred Cores


Temporary fix

After many failed attempts with various BIOS settings, the only one that fixes this problem is setting "Core Performance Boost" to disabled. Of course, with this setting disabled, this new CPU performs a lot worse than the old 3950X.​
With "Core Performance Boost" disabled, I can run my RAM at 3600 and IF/UCLK at 1800 with tight timings without any problems. 300+ Handbrake CPU stable encodes so far.​


With F31h Windows no longer crashes at boot, but crashes under load or random at idle like before.
The fastest way to crash the system is to run AIDA64 memory copy benchmark (will crash when CPU will reach 100% usage), a Handbrake encode (will crash as soon as it starts encoding) or a game (Guild Wars 2 crashes at login screen).

Opened a ticket with Gigabyte, but knowing Gigabyte, their response will be "We will inform our engineers" and then silence.
Opened a ticket with AMD. No response. Received an email requesting some details. Still waiting. Received another email requesting details already sent in the original RMA ticket. I guess AMD support and Gigabyte support are outsourced at the same helpdesk. RMA accepted after 5 weeks: my reply to AMD.


Anyone else having problems with the new 5950X and Core Performance Boost?

Thank you.
 
#2 ·
I had the exact same problem on the aorus master x570. What fixed it for me was I had to manually set the ram timings, ram dram voltage and vcore soc, and also manually select the proper infinity fabric frequency. I think there is some type of ram bug with the latest bios.

See if that helps you.
 
#640 ·
Just wanted to chime in and say that I was running into this WHEA BSOD error constantly with default BIOS settings. I have the Asus x570-Pro and 5800x. It was a brand new build that I built twice and wiped clean twice- I also changed several different BIOS settings. What worked for me was changing the ram speed (DOCP) DRAM FREQUENCY to 3200mhz. Even though I bought 3600mhz RAM.
 
#3 ·
What value for VCORE SOC are you using now?
 
#4 ·
Same as with me.

Swapped 3950X to 5950X Aorus Extreme motherboard. Now the system is rebooting at any time.

Latest BIOS, Windows 10 (20H2), Chipset Driver, AMD Ryzen Master, etc.
Settings for XMP memory, I also checked for OC (frequency, ending with voltages through timings).

The same!!!
Restart at sudden undefined moments.

I did not move the voltage on the CPU. I always have an AUTO.
 
#6 ·
No more GIGABYTE

I will change the BIOS to the older one - F30 - reviewers did not have such a circus.
 
#7 ·
FFFUUU..... Nothing has changed.
 
#8 · (Edited)
It seems other brands are having the same issue. MSI released a new BIOS for some boards that seem to solve the problem for some users.
Meanwhile, Gigabyte did not even reply to my ticket, not even with their usual copy-paste standard stuff. /s

Question is: nobody is testing these CPUs on actual motherboards these days? How the f do they release support for new CPUs with new BIOS versions and not test it for 5 minutes to see if the thing boots at least.

later edit:
finally some good news
2465527


/s

I have 5 support tickets ever opened with Gigabyte. 100% of their replies are identical to the above one. And then, nothing.
 
  • Rep+
Reactions: Marucins
#36 ·
:rolleyes: Of course Intel doesn't have that problem, they don't change tech and force you to buy a new motherboard for each new CPU.
 
#10 ·
Deepcuts, write me what you wrote to them. I will also report from myself.
 
#11 ·
What I wrote to Gigabyte is the exact text from the 1st post, minus the fact that I have tested with another GPU,RX460 and of course, without the last 3 lines.
 
#12 ·
Hi to all. Just registered so I would share that I am too having stability issues with 5950x and the aorus Xtreme. It would random Bsod with Whea errors, on both bios F30 & F30E and with stock settings , Bsod also with XMP settings. I still have my 3950x, and it works well without bsod on the Xtreme.
Have raised a ticket with gigabyte, hopefully they will address the issue with a bios update.
I would urge those having issues raised it with gigabyte.
 
#13 · (Edited)
I would urge those having issues raised it with gigabyte.
Sorry to hear so many have this issue.
Thank you for writing to Gigabyte. Hope more people writing about this issue will expedite things with them.
 
#14 ·
WOW, reading these issues just makes me want to wait. And this is a ~$1200 motherboard in Australia. You'd expect the highest end boards to get the fastest release for fixes. But at least in Australia we are protected by Consumer Laws, basically I would have 0 problems returning the board and getting a full refund if it had these issues. Sadly in other countries you have to contact Gigabyte, here it's not my job to contact Gigabyte, the store you buy from has to deal with them.
 
#24 ·
I have the same board and live in queensland, am expecting my 5950x in a few days by post. I am relishing troubleshooting as just doing a fresh install with my 3900x has caused nothing but headaches.

What I suggest to everyone here is to check a few things, if youre running a pcie4 card make sure tbt and 10-bit tag support is ON. Also make sure gear down mode is enabled in every option on the BIOS and switch PCIE mode to auto. 10-bit tag support is used in pcie 4 iirc so it is likely if its disabled that would cause reboots.

While on BIOS settings make sure to go into the power config in the (middle tab of the) BIOS and try with HPET (high precision event timer) to OFF to see if it helps. I found turning mine on after changing dynamic ticks in windows helped a lot but if you havent touched that then maybe turning it off will help. I am not sure if its the new chipset drivers as well but I have found my 2080 TI, yes still waiting on 3090 stock D:, is getting a lot of high DPC latency spikes even with perfer maximum performance enabled in the control panel. Apparently this is due to windows 10 now requiring/preferring DCH version of drivers.

NVIDIA has those drivers but you will need to use their advanced driver search, NOT GFE or their usual web portal. You have to disconnect the net/disable NIC and reboot in safe mode with DDU to uninstall the standard drivers and then reboot again into safe mode and install the DCH version of the drivers and then REBOOT AGAIN into regular OS and get the NVIDIA control panel from the windows store.....ugh such a mouthful to explain driver updates in 20H2 now.....

I am about to do exactly that but apparently that has solved a lot of stuttering for people with using 20H2 and nvidia drivers. I also suggest to watch FR33THY on youtube, he has an awesome introduction and optimisation guide to 20H2 and has multiple google drive folders for all the presets and batch files he uses. His A-Z guides are something to behold but I swear the guy is like a chihuahua on coke, can't sit still for 1 second he is always tweaking hahaha. Really it's what I will be like once I get this new hardware up and running and I am on the modafinil playing FPS' til the cows come home.

OHHHHHH and another thing to try with on/off in the BIOS is maybe the spread spectrum option under the core multiplier. The changes above and this one all affect the windows timers and the new 20H2 timer is still relatively unknown in its actual function unless you're an admin or super-user.....which you would charge to spend the time divulging all the info.

Anyhoo hope that helps and look forward to joining you sweaty 5950x boiz in a few days so we can all cry thermal paste tears together as we do the re-seat dance.
 
#15 ·
F31g same situation.
Do not bother.
 
#16 ·
I wrote ticket to the support...

Did you check the new BIOS with the old CPU (ZEN 2)?
 
#17 ·
I wrote ticket to the support...

Did you check the new BIOS with the old CPU (ZEN 2)?
Was using F31e with 3950X without any problems.
Cannot check F31g or newer because I gave the 3950X to a friend.
 
#18 ·
Hey, have you tried the original chipset driver from AMD's Site?
 
#19 ·
Deepcuts, me too.

F31g does't correct the problem with restarting the computer :\

84stangman, of course.
 
#21 ·
MoW, I'm at work now. I will check out after 4 p.m.

Deepcuts, can you check the new BIOS? You have the specification closest to my rig (CPU, MOB, RAM)
 
#22 ·
Trying now.
Don't hold your breath.
 
#23 ·
Updated to F31h
Clear CMOS via back IO button for good measure.
Entered UEFI and noticed FCLK is 104.4 Mhz. Weird. never seen it so high on auto. Set it to manual 100.
Rest on default.
Problem remains. Windows crashes, Ubuntu live does not even boot.

Set VCORE SOC to 1.000 and I could boot Windows, but crashes under Aida64 memory copy and most games.
Tried almost all combinations of VDDG, VDDP, VCORE SOC, IF, RAM Speed, LLC, etc.
The higher the VCORE SOC, the most likely Windows will not even boot.
No matter the combo, Aida64 will crash on copy benchmark as well as most games. 100% will crash at idle after some time or just internet browsing with WHEA uncorrectable error BSOD.

The only setting that gets this rig stable is setting "Core Performance Boost" to disabled.
With it disabled, I can set everything else on Auto and will work just fine.

On the upside, somehow it seems F31h is very stable when changing various voltages, like VDDP/G.
Up until now, a lot of times when changing anything voltage related, the board will beep twice and reboot 3 times. Somehow F31h fixes this for me.
 
#25 ·
Try my tip for spread spectrum, that affects the base clock mate, should hopefully see some stability.

If it has the options still also try the CPPC and CPPC preferred cores to enabled and disabled C states with cool n quiet ENABLED with pstate 0. Also i believe in the advance core settings there is also a low idle voltage option, try that on and off as well, reboot each time to test (its annoying but youll thoroughly rule things out).

Those settings are also how i got 20H2 stable with my 3900x and still retaining 4.65ghz light threaded and 4.4ghz all core in gaming. A good way to check if core boosts are being assigned properly and wont get "stuck" is to check event viewer when you load in and open the system section, look for kernel entries that have preferred core in the details and make sure they all have slightly different numbers like 130, 133, 142 etc... thats the chipset confirming with the OS so that boosts and cores are assigned properly.
 
#26 ·
@Tweedilderp
Thank you for the information. Will try some of your suggestions.
Please note that setting manual FCLK to 100 disables Spread Spectrum, which I did and also that a Ubuntu live USB also crashes before desktop. So slim chances that nvidia has anything to do with this.
 
#27 · (Edited)
This makes me more and more convinced that we have broken processors...: GIGABYTE Latest Beta BIOS - TweakTown Forums

It is impossible that it works for one and not for another. The same CPU, the same motherboard, and the new BIOS works with him, but not with us?

Maybe check this CPU on another motherboard?
 
#28 ·
I upgraded from a 3300X to a 5950X on the Gigabyte B550I AORUS PRO AX motherboard and get WHEA_UNCORRECTABLE_ERROR BSOD in games. What worked for me was unplugging every single USB device (including keyboard and mouse). If you have things connected to the internal motherboard USB headers you might need to unplug those too.

Usually I would BSOD within 2-10 minutes in Shadow of the Tomb Raider. After unplugging every USB device I went 2 hours without a crash and then plugged them back in and was fine. Then I quit my game, restarted Windows (keeping all USB devices plugged in) and crashed within 2 minutes of the same game. After the BSOD I noticed in Device Manager I had a "Unknown USB Device (Set Address Failed)" showing. I checked Event Viewer and saw every time I had the BSOD, Windows Error Reporting was taking a kernel dump and a USBHUB3 dump. I checked what the Unknown USB Device was (it goes back to normal after a restart) and it turns out to be the Gigabyte RGB Fusion 2.0 controller.

I have G.Skill TridentZ Neo RAM too. Is this some incompatibility with Ryzen 5000 CPUs, Gigabyte motherboards, this RAM and some USB devices?
 
#29 ·
Tested with only a Bluetooth mouse. No other USB connected.
BIOS reset to factory settings and optimized defaults loaded.
Same crash with Aida64 copy benchmark and games.
It seems to be a bit more stable nevertheless, or just placebo in my case.
 
#30 ·
To rule out RAM, I have tried with one stick of G-Skill F4-2400C15S-8GNS and one KIT of 2 sticks Corsair CMK8GX4M1A2400C16.
Same problem, BSOD with or without XMP loaded.
So up until now I have replaced everything but the mainboard and CPU.