I’m receiving error code 132 on a semi-regular basis on WoW (on my Priest, once every few days, very rarely twice in a row. It has ALWAYS been in Veldrakken).
Since the 10.1.5 patch, instances of it have increased to the point 1 character (a level 70 Shaman) is now inaccessible on my account as it triggers every time.
Occurence today: loaded with several addons (raiderIO, ElvUI, details, TomTom, DBM) and started a Freehold key fine
Crashed around 2.5 mins in just before first boss, couldn’t get back in. Assumed maybe addon related, so disabled all addons.
Completed dungeon, the second the success/timed screen appeared, error 132, now only able to get in by dropping all graphics settings to lowest
Issues now persist and the character is, in essence, bricked on my install.
Crash code for my latest crash:
01847B68-84CD-4AB2-87B2-DF9773EF0145
Could someone possibly look at this and let me know exactly where the issue is hitting, and if it looks related to specific hardware on my PC? (Saw on a different thread a Blizzard rep was able to identify a cause being GPU specific - that’s the sort of info I’m hoping to get if at all possible). If it’s specifically a bit of hardware that would be useful if I need to go back to my PC supplier, as the PC is relatively new (and these aren’t the first issues experienced).
I’m running an RTX4090, i9 13900K and 32GB RAM
I have tried repairing my install and deleting my WTF folder, no improvement.
I have the latest drivers installed for everything + latest Bios updates as well for good measure
Edit: Another crash code 26D292B9-A6AE-4A7F-BF0E-D9F709CC015D