Wow Error132, AMD 3600x, X570 mainbord, I changed RAM but it is not resolved, installed the old version of bios and problem is solved it

Did you change the settings of your RAM?
Are you using the default settings after the BIOS reset?

After installing the old bios, I changed the RAM settings. I set the 3600MHZ CL15-19-19-19-36-59 and the Voltage as 1.40v. I have been playing WOW with no problems for 4/5 days.

As the problem is not the RAM frequency or settings, I was still getting the error even though the RAM frequency is 2133MHZ in the bios version “AMD ComboPI1.0.0.3abb” and above.

Hey Beachîmsu!

Would you mind sharing some basic diagnostic data for your computer, so we could have a look at this from our end? Could upload the files to a service like pastebin and post the links here, if that’d be okay with you. :slight_smile:

There have been a few blips on our radar for hardware setups similar to the one listed in your original post, so we’d be very much interested to see if further commonalities can be found.


Of course, I can provide the information, but I am sending DxDiag because it is over 512Kb on the site.
Please do not forget to delete the spaces before and after " . com" point. :smiley:

pastebin . com/Zy3AyLcy

I added in the Google drive link. . com/open?id=1uiOZqIzMmMCxfPl8vTu2J0IeOAuT1fJq

i upload mine aswell, i’m getting these crashes after a bios update aswell on a X570 system. maybe it can help a fix on your side.
i have Hearthstone crashes aswell since then. and only on blizzard games :frowning:

pastebin. com /QkgXjnvk

pastebin. com /tDrUujZJ

Can you leave a memtest running overnight? Also continuous Unigine Valley demo/benchmark (and optionally Unigine Superposition and 3DMark Time Spy) - Valley seems to be better and “finding” system instabilities.

If memtest runs ok for multiple hours overnight and the Unigine stuff for hour or so then it will vastly limit the chances the system overall is unstable.

it was the bios upgrade on a X570 that was causing the trouble. i rolled it back to the stock version ( 8 bios updates ago) running stable for a couple hours now. before it would not stay online for more then 15 mins.

everything else was running fine on my pc, benchmarks, memtests etc

1 Like

By now we’re indeed pretty sure that there may be some kind of fundamental microcode conflict between the Ryzen 3600/3600X series of CPUs and BIOS versions released after AGESA Rolling back to one of these versions seems to fix the problem for everyone affected, as far as we can tell - it may not always be easy to do but the results do speak for themselves.

Thanks to everyone who shared their data, it is much appreciated. :heart:


Hi, i’m coming from

To confirm - motherboard is MSI B450 Tomahawk (non-Max) and I had to roll back to bios with ComboPI ab - now WoW is fine.

I dropped the topic on reddit to see if it’s more generic: and it seems some people did experienced problems with newer AGESA.

Hello to everyone,

I replaced my 3600x processor with 3700x. I installed the latest version of the motherboard bios. I set RAM XMP profile 3600Mhz CL16-19-19-19-36-59.
I just changed the processor. Now WOW is running smoothly. I’m not getting any errors. Good games.

7C37v192 (Beta version)
Release Date

Easy test would be to fly in circles around the main street of Legion Dalaran. If that doesn’t crash then it’s rock solid.

Thanks for info, unfortunately that is not a solution for me since I dont have money to spend on new processor and the current is perfectly fine from performance point of view. Also MSI dont have newer bios for my B450 Tomahawk - last one is dated like November 2019 :confused: .

You’re welcome. Pull the bios update to a lower version. This will work.

I know, I did but my older bios have constant issues with USB/sleep mode/etc so my choice is to have crashes in WoW or restarts to bios without hard drives :wink:

Ok so AGESA bios for MSI B450 Tomahawk released few days ago doesn’t solve the problem. Just checked - crashed after like hour. Rolling back to ab with bugged hibernation :/.

you can comment on reddit so that AMD CM that commented there knows it’s still a problem.

Been there, done that :wink:

1 Like

Hi again,
after reading this topic I filed RMA to replace my Ryzen 3600 bought july 2019 with new one. At the moment i’m using Ryzen 3 3100 with AGESA Bios on my MSI B450 Tomahawk - no crashes so far. I hope I will receive new R5 3600 manufactured this year and it will be free of this crap bug causing crashes :pray:

next update:
today I received new R5 3600 manufactured week 14, 2020. Already replaced R3 3100 and testing with AGESA For last 6 day I had zero problems with AGESA bios and R3 3100 so that another proof that problem was with my R5 3600. Now we will see if theory about early production R5 3600’s failing is correct.

So last update - it was definitely case of early production Ryzen 3600/3600x units. After receiving this year’s one everything is ok with latest bios.