Have been playing WoW since Vanilla, and Dragonflight since launch with pretty much zero issues - its been a much better expansion than SL
Over last 2 weeks have been getting lots of Error 132 crashes seemingly at random. From 3 times in LFR (got me kicked), to just sitting in Dragonscale Camp, to flying on a Gryphon…more crashes since the last patch than ive had since DF launch
Im aware there are many other players suffering, but they seem to crash upon entering the game, which doesnt happen to me
Have updated all drivers, played without addons but same results. The random nature is very frustrating.
System is Ryzen 7 1700 with GTX 1070 and 16Gb RAM - as I said, been pretty faultless in WoW until last couple of weeks
Have you tried an interface reset ? That’s sort of like ‘disabling addons on steroids’. I’d suggest that as a first port of call. You can see how to do an interface reset here:
I know it’s a common problem, but unfortunately the usual troubleshooting is the only option for people because there is no official acknowledgment (or workaround) from Blizzard at the moment.
My next port of call would be to delete and reinstall WOW but I’m aware this is not a trivial job for many people and can be quite time consuming - and, of course, no guarantee of a fix at the end.
Had the same 132 error 4 times in a row
ACCESS_VIOLATION
(DBG-OPTIONS DBG-ADDR<00007ff7590efffa>(“Wow.exe”) ← DBG-ADDR<00007ff75910c3fb>(“Wow.exe”) ← DBG-ADDR<00007ff759111047>(“Wow.exe”) DBG-OPTIONS<>)
The instruction at “0x00007ff7590efffa” referenced memory at “0xffffffffffffffff”.
The memory could not be “read”.
Not familiar with game developing but this error straightly says that something reads nulled memory. Why should cleaning cache help i dont know. And it didnt help actually.
Got error on arena and now when queue popped again. Sure, somehow when I reinstall game there will be less worse code in game files, some magic dragon fixes will appear
What should I do? Go to the blizzard office and fix their extremely bad code for them?
Found https://us.forums.blizzard.com/en/wow/t/error-132-game-crashing-in-raids/1528661/5
Did some investigation and dumped dxdiag logs
On US forums highly competent Customer Support refers to several issues:
Event Name: BlueScreen
LiveKernelEvent with code P1: 141
D3DDRED2 with code P1: VEN_10DE
Didnt have any same errors in my dumped logs. So if google first 2 errors referring to dxdiag, yes it will be mostly hardware problems. Funny thing that 2nd problem could be solved by cleaning up disc (ofc that help you to erase null memory read error lol)
However I just checked and see about 9 errors in dxdiag that are completely different from what OP have on US forums
But that doesn’t justify NULL REFFERENCE EXPETION in C++ game code that is just empty reading memory from simple RAM.
Funny thing Event Viewer in Windows that should display error says that root of the error is Unknown
I will update or add another comment if I continue face this nonstop low skill programming error
Actually I found a solution to fix a problem (note that I did it reading and finding error name in my logs on my computer not OP and not the guy from US forums):
In dumped dxdiag logs there is some related Wow.exe errors that are BEX64 failed event
So, most user friendly fix should be:
Shut down and turn on ur pc
Reload pc by pressing reload button in windows (this will initiate cold start)
Do clean boot (google what it is, not hard)
Just do one of these 3 things and BEX64 should be fixed. Don’t do any Registry or other strange fixes before you try what I mentioned
What do my steps do? It cleans up memory (RAM) and all memory leaks etc, so it will fix uncommon memory errors
Had a good run without crashes since I last posted but only it seems by closing just about everything before loading WoW
Just logged on now for a quick session and three Error 132s in quick succession - two whilst flying around and one just standing in Dragonscale base camp
Have just done a restart using prev posters advice so will see what happens. Very weird that these crashes almost always happen at weekends…