it happens randomly, more often than not during intense combat, but others i am just afking or just after a loading screen
before anyone claims its an intel issue, i have zero issues with other modern games like mhWilds and poe2 which hit the cpu harder, its just wow and just this week
edit: additional information for what it’s worth:
Let’s start with some information about your pc, hard to pin it on anything without any info.
https://pastebin.com/embed_js/gdHjvKqf
additionally, i am trying to look through the crash logs, is there anything i should take note of?
I’ve been experiencing the same issue. Mix of divide by 0 and access errors with no obvious changes in my situation. Bios/drivers up to date, disabled all addons and WAs. I’ve done a completely fresh reinstall of the game to see if that might help.
Edit: I’m able to pretty consistently crash myself with a divide by 0 error by simply typing /reload a couple times.
It could be recent drivers issues with newer nvidia drivers, there were others Posting reverting back to drivers from January helped.
Im notint double monitors, but a on-board intel gpu, probably not related, check that the cable is plugged into the discreet card, not on-board graphics.
quick update: rolled back my gpu driver to 566.36, still getting both errors. 5 crashes in a span of 20 mins doing world quests.
will try tweaking bios when i get the time…
update: im on a 13700k + msi mobo so i didn’t think it would change anything but i switch several bios settings to intel defaults and… yes it did absolutely nothing, still crashing randomly. saw another post on disabling optional gpu features and advanced work submit, that’s a dead end too.
I have the same errors. It’s ridiculous in battlegrounds. It happens all the time. also getting a lua message.
after reading a few forum posts some have mentioned that addons are the cause for their crashes. i noticed that even though an addon is updated to be compatible with the latest game version, in game it still flags some of them as outdated. so i disabled all the addons the game complained about and have been slowly re-enabling them one by one with the intent of running m+ and random heroics to test them out.
so far i have done a mechagon 10 and a random heroic without any crashes… i have so many addons this is gong to take a while to narrow down the offending one…
I have been trying to figure this out for the past week. I am replying just so I can keep checking this topic, or report if I figure anything out.
Same, so far I think I have been able to narrow it down to a offending action for me: Professions. I mostly get errors doing Transmute/Crushing/Cooking in Dorn. The other times are usually loading screens, have yet to have it lock error ping in combat (though I have had memory read errors in M+ start loading screens). But doing that has bouts where it will trigger over and over within 10 crafts, then other times I could do thousands and have no issues. Also, usually if the character errors once that one along with others in the Profession party (like the 4 man loading screen) will fail to lead in and error, but others in the main party are still fine. Or that may just be superstition after failing 20 times in a row to log in.
Already vetted addons, it errors no matter how few I have (god doing transmute without Salvage assist makes me want to gouge my eyes out, why is it so ungodly clunky) it still has the same chance to throw a divide by zero or memory read.
Tried drivers, reinstalled, addons, knocked out every overlay I could find, it will still blow up smashing rocks. And it’s not due to my CPU, I play Total War Warhammer, Tarkov, hell even Space Marine runs the CPU harder than me sitting in Dorn (least according to Task Manager), all of them run errorless.
So just tossing this in to see if any solutions come up.
Bagnon was the culprit for me.
I am having this exact same problem. I will try to disable bagnon i guess?
You’ve got a bunch of crashes and bluescreens at the end of your DXDIAG, one of which was some LED related software. Probably some driver or software related problem that triggers WoW into a crash under certain combinations of circumstances. You also have some linpack_xeon64.exe crash, which is a benchmarking/stress testing tool, if I’m not mistaken.
Did you update your BIOS+microcode to the latest versions? The 13th and 14th gen Intels had a nasty bug that can slowly break your CPU over time, it might be catching up to you now. It’s an issue well known for causing crashes like this and even WoW displays a warning when you launch the game without the latest microcode.
i disabled all LED and the MSI software used to turn them off could very well be a factor. i will try terminating the process to see if that helps.
interesting find, i am not aware of using any benchmarking tool, i was using intel xtreme tuning in an attempt to reduce by performance core multipliers but that didn’t help.
yes i was on top of it, i live in an equatorial country so i am very aware of the temperature tax here (daily average temp 28C/82F) and i never overclock anything, i got the 13700k just for the higher boost clocks and the ability to underclock if i need to.
update on the addon testing from my end:
i disabled Ace3, a dependency for some addons, and it managed to get about 6 hours of world quests, random heroics, and a few m+ without crashing last night. however i just had a crash while browsing the AH with my professions open, using addon “Auctionator”. it is very apparent that this is a multifaceted issue. for what it’s worth, the inv_divide_by_zero before always had the same location address, today’s crash has a different location address. i have not seen a memory access violation for about a day now.
sidenote: another reason why i leaned towards addons was that since i was crashing while doing nothing, it had to be something running without the user triggering any actions.
update: just got a memory access violation 
I disabled, then deleted all addons. Bios updates. GPU drivers updates. Windows up to date. Completely removed and reinstalled WoW.
Still crashing with the Int Divide by Zero, with no addons
i actually rolled back my gpu driver to nvidia studio driver 572.60, and after updating bios reset it back to optimized default (thats what its called in my msi bios) and tweaked fan and pump curves.
addon testing update
i’ve done about 4 m+, a few random heroics and delves and cleared wq for the day across several toons. albeit i exited the game a few times but i think i got a solid 6-8 hours of uninterrupted gameplay, afk-ing in town included.
addons disabled:
those marked with a * are those i have no tested but don’t feel the need to turn them on if im just playing it bare-minimum. the rest are what i think do a lot of API calls, and are more likely to cause the errors
Hmm I use the following addons that you disabled
Will try to disable some of them and see if there is any difference.
i enabled Auctionator to check my auctions and forgot to disable it, i went from Dornogal to Undermine, cleared up some wq and achievement quest (~2 hrs) and was heading back to Dornogal. stepped onto the portal and crashed with int/0 error. it does not happen all the time but having Auctionator enabled was the only change i had.
now im not 100% sure its this addon, just posting my findings
I back down my Nvidia drivers. I play with zero addons. Still crashing. Often enough that it makes playing un enticing. There really seems to be no pattern that I can see. it will crash at varying intervals and doing any activity.
Guess it’s time to move on and check back in a few weeks to see if it ever gets sorted.
I have done everything to prevent this from happening and it still happens. It seems random and mostly it is. I do notice it happens more frequently when hitting portals, aka the loading screen, and logging out to switch characters or loading into a new character.
I opened up a ticket and followed all advice. I have tested every piece of hardware, uninstalled the game, removed every addon and saved variable. Ran the game in default mode (no addons) and it didn’t change a single thing.
This is absolutely ridiculous and very annoying.