ERROR #132 (0x85100084), a Ryzen Incompatibility Problem

[Zjocura-arugal]

For a couple of weeks now, ever since I upgraded from my old i7-2600k system to the new Ryzen 3600x. I have been plagued with the ERROR #132 (0x85100084), crashing my game at random time intervals.

Things I have looked up on this forum and have tried already:

• Full system stability testing and temperature monitoring, with continuous 100 Hours of AIDA64 stress test, 100 Hours of Prime95 and MemTest86
• Ran the system under-clocked to test if there are any issues with stock settings, even thought stability testing passed.
• Update all drivers (yes even AMD Chipset), BIOS (latest Motherboard Bios) and Windows 10 (1909 Build)
• User Interface reset
• Reset of console variables (/console cvar_default)
• DDU Tool to Clean all drivers and reinstall
• Full format and reinstall of the latest Windows 10 Build

After a clean install of Windows 10. I installed nothing but Bnet and WoW Classic and got the same ERROR #132 below.

https://pastebin.com/VTHvX6A4

After, I installed the latest AMD Chipset drivers I got this ERROR #132

https://pastebin.com/EczXstwK

I then installed the latest Graphics driver and got this ERROR #132

https://pastebin.com/qrf4zC0T

I then underclocked my Graphics card and got this ERROR #132

https://pastebin.com/40zj94K9

MSInfo32

https://pastebin.com/5u8XZS3P

DxDiag

https://pastebin.com/VNRjakuD

I have carried over my Case, Power supply (EVGA SuperNOVA 650 P2) and Video Card from my old 2600k build.

Anyone has more suggestions to help?

I am really stuck he and don’t want to go back to my old system just so I can play WoW Classic, because of this game bug with Ryzen.

This post is now solved.

The problem was my faulty Ryzen 3600x CPU.
Yeah, very odd thing to have trouble with.

An original post about the Ryzen CPU problem with Error #132 can be found here: Dlog - Error 132

My trouble shooting and discussion about the faulty CPU can be found here: Error #132 in game

Hope this helps some one with trouble shooting their problem.

[Valzee-darkspear]

Hey,

I think I’m having the same issue. I’ve tried all of the things you did, and am still getting random error 132s. One question–did you resolve it by swapping out for a new 3600X, or did you go to a different processor altogether? If so, which one?

[Clottibby-bladefist (Clottibby)]

They answer your question in a post they gave in another thread:

@Zjocura-arugal

As for myself, after using a borrowed 3700x for over a week now. I can 100% conclude that its a faulty CPU and consistently reproduce the crashing on one CPU and not the other.

After I swapped my 3600x for my friends 3700x, all my crashes in WoW, Diablo 3 and PoE have gone away. I changed nothing else in the system, same drivers, RAM, video card, etc. After CPU swap, the system booted like normal without any differences, even kept my RAM settings and stock timings.

Used the 3700x for a week, not one crash or a hiccup in anything. Swapped the CPU back to my 3600x and within 5 minutes it crash in PoE and WoW crashes within hours. Once again, nothing else changed, but the CPU. Same BIOS settings and system settings, in every way.

[Edited by Blizzard] This thread has been inactive for some time. Please be mindful of resurrecting older threads. A new or more recent thread can be created to continue the discussion. Locking this thread.