Processors

[mackbolan777]

Try the 3.40 BIOS, the version you're using has a lot of complaints. I have an AsRock X570 board and we use the same BIOS's, for me 3.2 was the best but I have a Ryzen 3600X. Various online boards have the 3.40 as being good for AsRock X570 boards with any 5000 series CPU.

[cashby]

Thanks for that. I stopped getting the WHEA issue and kernel-P error but during gaming the games just crash and boot me back out. after about 20 mins or so. when i tried to log back in probably after 8 mins get booted again. So i ended up changing the power mode and turning XMP back on but then when running Prime95 it welcomed back the Kernel P errors. I changed Ram speed to 3200Mhz leaving XMP and then put power settings on the higest for high end machines. prime 95 no issues and tried the ryzen master test and all worked no issues... 

Will try gaming again and see if the system crashes. if it does - i'll then change my bios updates and flash back to the original one 3.40 and see how we go. Otherwise i'll have to try the manual CPU adjustments mentioned previously. Thanks for all your help and advice. 

[CrispyCrunch · Accepted solution]

I got a new angle on this. So deactivating PBO and CBS definetely works, PC was running stable for a week now. But you'll loose performance.

So I wrote to the MSI support and the AMD support.

MSI suggested to try increasing the DRAM Voltage by 0.05 V, which I did. System seems to be stable, no crashes so far - neither in idle or while gaming.

[cashby]

I ended rolling back my bios to 3.40 for my ASRock x570 Taichi. Which was suggested.  Ran all tests and system is stable. Xmp enabled and played a game tonight for about an hour and no crashes. Fingers crossed this continues next week when cyberpunk is out. Thanks for all your suggestions. 

[mackbolan777]

Who told you about the 3.40 BIOS?? Me, I think! Glad it worked.

[nsargentum]

I'm having the exact same issue on a 5600x with a msi tomahawk b550. I have a x570 gigabyte aorus master and a r9 3900x I was thinking of swapping this CPU with that and testing there.

OK; Get ready for this, Here's everything I've done so far to eliminate variables:

1. Swapped the system drive (nvme) and reinstalled windows from scratch
2. Unplugged all other drives
3. Swapped GPUs
4. Swapped PSU
5. Swapped memory from 3200Mhz Gskill TridentZ CL16 to 2667Mhz CL16 Corsair Vengeance
6. Swapped the Msi Tomahawk B550 with another MSI tomahawk B550 to verify it wasn't the board.

Ensured I'm on the latest bios for the MOBO and the previous 1 which was also post Ryzen 5000 release.

7C91vA51(Beta version)

Release Date

2020-11-16

Description

- Support AMD SAM(SMART ACCESS MEMORY) function

AND

7C91vA4

Release Date

2020-11-04

Description

- Updated AMD AGESA ComboAm4v2PI 1.1.0.0 Patch C

I have literally done everything you can do aside from swapping the CPU and turning off PBO or any other bios settings. So if anyone is wondering if this exact error and restarting behavior is a single component in the system, in my case, it's not. It's the CPU or the microcode that hasn't been updated yet. Now.... I've seen forums where people with 3000 series CPUs were getting the same thing. I'm at the point of buying a 5950x *(when it's available) to replace my 3900x, buy it's super annoying that I may have to RMA my CPU for my main gaming rig the 5600x when there is almost no stock and I got lucky enough to buy a CPU with the supply being so low.

For reference, these are the CPUs I've owned, none of which have had this issue:

fx 6300

fx 8150

r5 1600

r7 1700x

r7 1800x

r7 2700

ThreadRipper 2950x

r5 3600x

r9 3900x

4500U

Obviously, being a computer engineer and a HUGE AMD fan, this behavior is concerning to me. Especially when I'm patiently waiting for the 5950x and a 6900xt.

I'll put the tridentz back in and try disabling CPB And PBO

[mackbolan777]

You need the Agesa version 1.1.0.0 non-C and looking at MSI's site you might want to ask them if 1.0.8.1 works or just try that one. AsRock X570 boards have a similar issue with the "C" patch for soem reason so in AsRock's case the BIOS 3.40 works fine.

[cashby]

@mackbolan777 it was you good sir. I thank you. :)

---

@mackbolan777 wrote:

Who told you about the 3.40 BIOS?? Me, I think! Glad it worked.

---

[mackbolan777]

If it's still working, can you mark it as a "solution". Not for me to get "points" but so others will find it easily in the "knowledgebase". A lot with AsRock boards are having this issue. Thanks.

[cashby]

I don't think I can as this thread already has one solution linked? 

---

@mackbolan777 wrote:

If it's still working, can you mark it as a "solution". Not for me to get "points" but so others will find it easily in the "knowledgebase". A lot with AsRock boards are having this issue. Thanks.

---