DIVIDE_BY_ZERO, Access Violations

Support Technical Support
1

Okay, as the title suggest, these are the errors that I am getting, Divide_By_Zero and Access Violations. I am going to list what I have done, up until this point.

-Sent back the PC to MSI (Under warranty) to fix the VMINN Shift Error. CPU, Motherboard, and Radiator were all replaced, with new parts (Not refurbished. Had to wait an extra week as it was Chinese New Year when MSI requested the parts from Taiwan). Bios was updated before shipping back to me, and is the latest one on the market.

-Clean install of WoW, SSD was formatted and just had the OS factory installed on it from MSI.

-Clean install of addons. Reinstalled Curse, installed the addons that I use (Did not copy over a folder from a save file on our network), and updated them accordingly.

At this point, things SEEEMED good. I could play and without interruption. Then we had that patch on Saturday April 12th, 2025. Everything feel apart then. As soon as the patch was downloaded, the game was now getting Divide by Zero errors. I would switch to another character and see if the same thing would happen, and all of a sudden, another Divide by Zero error. Having never had it before, I looked it up. I knew the VMINN issue could cause the access errors, but ive never encountered Divide by Zero errors prior to this. I saw that it COULD be a power issue to the processor. A lot of post on reddit and the internet suggested changing voltages, etc. So I did. I tried loading up WoW, and I couldn’t get past the loading screen without a Divide by Zero error. I changed the voltages back (In bios, since the desktop app only change it until you restart the pc), and decided to disable the addons, to see what would happen. Disabled the addons, loaded up WoW, and I am fine!

…until now

Last night, I started getting Access Errors again, not Divide by Zero Errors. I have been running with very few addons (DBM, Auctionator, ZPerl, Decursive, VuhDoh), but started getting this issue. I went to bed, figured Id work on it today, and here we are. Access Errors, and worse than the Divide by Zero errors. At least with Divide by Zero I could log into a different character for a sec, or at least get the loading screen bar up about 9/10ths full. Now I am crashing with Access Errors at not even 5% loading on the loading screen. Mind you, that is WITH NO ADDONS (Deleted the Addons completely), saved and deleted WTF and CACHE folders, ran the repair tool.

MSI is saying that their diagnostics is showing no power issues with the CPU, or GPU. They also said that the SSD and RAM passed all of their tests, and the issues lies with “Your game”. Having paid out a year in advance, and having done everything within reason to remedy the issues, I am kind of at my end for trying to fix an issue that is pretty much not one that I have caused. So if anyone has a clue as to what I can do to fix the issues, Id love to hear your suggestions…besides (Just reinstall the game clean. Already have twice, after the repair didn’t work.)

3 Likes
2

Do you have discord? If so try disabling the overlay. Others have also reported rolling back the Nvidia driver to before January. Not sure what driver version was last known stable.

3

So just to add to this pile, my wife has had a similar experience. As of the same date, 4/12/2025, they are also getting a slew of Devide By Zero and Access Violations.

The interesting part, and what I’m suspecting, is that it ONLY occurs when ANY addon is running. If ALL addons are disabled? Works fine. If ANY addon is enabled? It will crash.

I’m suspecting that some sort of update occurred on the 12th (there was a patch this day), that modified WoW’s addon “snooper”/profiler. Since it occurs no matter what addon is enabled. Or some other internal task that runs ONLY when addons are running, that is over-reaching and causing violations.

EDIT: For more clarity, the crashes seem to be effectively “random”, and have no tie to resource usage, or what is particularly going on within the game, or high/low resource usage of the CPU/GPU.

I’ve also completely removed the game. Removed display drivers and rolled back, checked all hardware, re-installed, disabled overlays, and ran the game with/without discord running. Nothing seems to “fix” the issue that started on 4/12/2025.

1 Like
4

Sadly I do not have DIscord since the SSD was reformatted.

Update
100% Know the issue now…
Tankutanku mentioned something about his wife crashing with just any addons running, so i tested it. The problem IS ANY ADDON RUNNING. I tried running a dungeon with no addons, and it wasn’t fun, but i never crashed. I turned on decursive, and while loading into a follower dungeon, the game crashed. I turned it off, and the game loaded the dungeon fine. I ran it with no issues. I turned on DBM, and the game crashed while loading into a dungeon. I turned it off, and had no problem running the dungeon once again. I checked this out once more with Skada, and the same issue. The game crashed during the loading of a dungeon with it enabled. I turned off Skada, and was fine.

Sadly at this point, unless there is a workaround to get the addons to work and the game not to crash while using them, I have no desire to play. It is really difficult to use a UI that does not have taunt alerts, debuff stack warnings, mechanics that require specific commands at that exact moment. Blizzard has made the game reliant on the very thing that a few of us CANNOT use…Addons.

Update
(Old)
I once again clean installed the game, even went as far as too change the directory to the default directory, and not where i normally place my games. With no addons running, I was able to sit in the TWW Capitol city for about an hour, constantly making sure i did not AFK too long. I moved around the town, and was fine. I tried running a follower dungeon, Darkflame Cleft, and immediately had the access violation error. I did a diagnostic check on my RAM, and it found no faults in it. I selected the advance option, and still had no errors.

I can eliminate the SSD, RAM, GfX Card, MB, and a clean install with no addons running. I’ve been reading the forums, and see that the WoW Dev team, has left out a line of script (As found by various users, with screenshots to support their claims), that has to do with buffs no longer appearing above your characters health bar while in combat. Many people are claiming this to the issue, though i am against this theory, for the following reason. I have had this issue since the 12th, and the patch that came in on that day, long before this little oversight on the visuals for the buffs.

I am seriously running out of options on this.

2 Likes
5

Make sure the ones you’re using are updated for the correct patch number. Not all developers update at the same time as the game, and Blizzard doesn’t monitor how well any addon works since they aren’t creating them.

Installing them fresh (and possibly resetting UI) would also be recommended.

6

I believe you are misunderstanding.

This isn’t an issue with specific addons causing a crash.
And it isn’t to do with the most recent update. (this started 4/12/2025 and corresponded with the patch that released that day).

When the game is running without addons (no trace of them, not talking about just disabled), the game runs perfectly fine without issue. (I’ve also tested by just disabling and seems to work the same, but to be through my tests in bulk have been done with a clean install of WoW, with no trace of addons or UI modifications of any kind).

If you download and enable ANY addon. Doesn’t matter which. Simply WoW running WITH a any single addon enabled will cause these crashes. (And the timing is random. They have happened in LFR, dungeons, in Dorn, during initial load, out in the wild… with no seeming correlation to any kind of “stress” or resource usage).

Like I said, this strongly indicates that there is some change that was done 4/12/2025, that is causing crashes for people, that seems to be in direct relation to whatever wow code is ran exclusively when ANY addons are detected by WoW.

1 Like
7

I’m running all the same addons I had before the patch, some of which are outdated (I recognize the performance risks). Zero crashes. This doesn’t lend to that narrative.

Additionally, this thread is the only place I’ve seen the issue described this way. So maybe the people you’ve heard about this from have something else in common with you, like a piece of hardware.

8

What you are experiencing on your hardware, in no way reflects or has any barring on what others are. In general that is a terrible place to start “helping” from. My personal desktop does not have any issues at all. But could you imagine if my reaction to my wife’s issue was “Well mine is running fine?” And in fact, what I described is 100% accurate. ANY addon, IS causing the crash. Now what exactly is creating this issue? Still unknown.

It’s fair if “this thread” is the first place you have seen it, but I recommend looking up the issue in bulk. Since 4/12/2025 there have been a LOT of reports of this issue, with what at best could be described as a “shotgun blast” of attempts, with no clear answer.

People have manually replaced DX files, they have ran on DX11, they have done prior troubleshooting on intel chips like underclocking, but largely the issue has not been resolved, with many reporting that even after doing all of this, they are still having issue.

Which is why I would urge blizzard to look into what updates happened on 4/12/2025. Since that seems to be a reoccurring date that keeps coming up.

And the fact that its a situation where ANY addon being enabled triggers it, also strongly points to some instability as of 4/12/2025.

It’s possible that some other software update is interfering (windows/drivers/etc.) but so far no data is strongly pointing at that being the case.

1 Like
9

It is the most common experience right now, so I’m using it as an example. I am not stating that everyone will have the same experience, just sharing my own, which also helps other people coming across the thread with troubleshooting (letting them move on to other aspects of their system).

Since addons are developed by third parties and not reviewed by Blizzard, it’s my understanding that getting them to work with the game client is between you and the addon developer.

If Blizzard changed something about the client that is causing these problems, then that would be something addon developers work out with Blizzard.

Can you provide all of the hardware specs for the affected computer?

1 Like
10

Adding my 2 cents in here, I am also experiencing the same issues since the patch on Tuesday. Been troubleshooting it and also found its related to addons. For some reason, ElvUI or any other unitframe addon bricks stuff, WeakAuras like Luxthos are problematic but Quazii’s package (for monk at least) seems fine… DBM is acting up but BigWigs seems fine… It doesn’t appear to be a common issue, but does seem to be showing for some people.

I do have a 14900k in my build and have been running the updated BIOS version since I got the processor so its not related to that. I’ve done scans, repairs, driver updates, full removal of the World of Warcraft directory and reinstall, the only thing that has helped besides the addons is under graphics swapping from DX12 to DX11, disabling optional features, and disabling Multithreaded Rendering, though not sure if that mattered since I was doing it at the same time as the other changes to graphics. Graphics card is a 4070TI.

I thought it might be related to the discord overlay at first too, but that doesnt seem to have any impact on reliability.

I just want to be able to play my game, getting real sick of this. I understand that Blizz isnt responsible for addons, but they have cultivated an environment where they are such a crucial part of the game for tons of people, so saying “oh well thats the developers issue” and not recognizing that Blizz could and should have people working with addon devs to prevent issues like this from happening in the first place. Personal experience, but support and QA are not what they used to be in this game.

3 Likes
11

In this particular case, blaming hardware, or addon developers doesn’t make sense. Since it isn’t a case where a bunch of people bought new hardware on 4/12/2025 and all started having problems. And blizzard already has the logs for these crashes.

It’s also short sighted to pretend that there isn’t a single possibility that blizzard didn’t make an update that is conflicting with certain hardware/machines. That specifically pertains to how the runtime of the game is impacted, and how any difference of that runtime changes when addons exist.

I would agree that if this was a situation where specific addons were the cause, looking at them would make some sense. But given that I can literally take any addon at random, and know its going to crash the system, it paints a different picture.

For additional context, with no addons, fresh install, I’ve now been able to keep the game running in Dorn for 18h without a crash. If I take any addon at random, and install/enable it, the longest runtime I’ve been able to achieve is 45min.

So given that this PC has had 0 crashes in any game or software, has no error logs, and suddenly on 4/12/2025 starts crashing consistently… and there were a handful of patches/updates between 4/8/2025 and 4/12/2025… I don’t think its a stretch to ask Blizzard to look into what was modified. And in this particular case have ruled out both Windows and Nvidia updates being the cause.

2 Likes
12

I added information about policies and asked a question about hardware. Your statement reads as if you’re assigning blame to the WoW client, even though most players can use addons without issues.

So now that you’ve let me know what you think of my troubleshooting, let’s get back to that part:

How can anyone offer advice that is more specific when hardware specs aren’t being provided by those submitting this complaint? Any tech support thread seeking troubleshooting should include a DxDiag per the sticky threads.

13

I’m running all the same addons I had before the patch, some of which are outdated (I recognize the performance risks). Zero crashes. This doesn’t lend to that narrative.

Additionally, this thread is the only place I’ve seen the issue described this way. So maybe the people you’ve heard about this from have something else in common with you, like a piece of hardware.

I have a strong suspicion, based on other recent posts about this issue, the relevance of the 4/8-4/12 patch notes, and how my testing leads me to believe that the date is important, and its pointing at either the WoW update itself, or another update around that time that is interfering with the WoW runtime (but only when any given addon is running). And yes, my leading theory is that the WoW client did receive an update that is causing crashes on a subset of users machines. Specifically an update that happened between 4/8/2025 and 4/12/2025.

That said, if anybody believes differently, and wants help investigating their logs and DXDIAG, of course it should be posted.

1 Like
14

I am getting the same issues and have been since around the beginning of this month. Constant Divide By Zero errors in my crash log folder. I have tried disabling quite a few add ons but never disabled all of them, since as you stated, the game is not much fun to play without some of these much needed features.

I’m assuming this is still a problem and there isn’t a solution or a work around (besides disabling all addons)?

15

I haven’t seen a solution as of yet. You can copy out all of the addons in your World of Warcraft_retail_\Interface\AddOns folder into somewhere else and then delete them to test and see if it is being caused by them, and the logs can often point to the offending addon, but my only fix so far has been setting up a new UI and aggressively testing whatever I add / import. So far, BigWigs / LittleWigs seems OK, Weakauras is dependant on the auras present so I’ve only got the Quazii one for Monk, and Details seems fine? though I have seen it on some of the crashes. Plater worked for me after a full reinstall.

1 Like
16

I can pass along dxdiag and whatnot if you want. From what I am seeing, it seems to be related to when the client / addon / weakaura is accessing stuff within the World of Warcraft_retail_\Interface\AddOns folder for me at least. Like adding the SharedMedia_Causese addon, and then attempting to call those sounds via BigWigs, or adding a Weakaura that interacts, etc.

Not sure what changed, but definitely seems like somethings up with the client - only on my desktop though. My laptop works perfectly fine and has no issues.

18

Yeah, I looked at the crash log and it appears that Hekili is in the stack trace. I posted a bug report on their GitHub page and the author answered back this:

"There is an open ticket for this issue.

There’s also literally nothing I can do about this issue; it appears to be a Blizzard issue. This addon will be in the stack often because it uses a coroutine to split up its work."

So, not much help on this end. This crash is only happening for WoW. Any other applications I am running run just fine.

Honestly, I think this may just be a red herring. I have not had any problems until 4-13-2025 when I started experiencing this on the regular.

3 Likes
19

I agree. Also same regarding other applications. I just meant disabling add-ons to bring in stability, not necessarily that they were responsible. I believe that its probably some change to the client that is responsible, not individual add-ons.

1 Like
20

Noticed something brought up in other threads, the addon profiler that has been causing those 3 second blips had a change in 11.1.5 apparently, looks like there was a way to disable it but that has been removed. Just bringing it up in case it could potentially be related, no clue though.

21

Can the laptop run all the same add-ons that crash the desktop without issues?

Someone in the UI and Macro forum pointed out a change in the API permissions, which usually just means the addon developers adapt their software and then it’s all good.

In another thread, someone mentioned that their addons were reporting as “Up to date” in CurseForge, but were not actually updating. They did a full drive wipe (WoW was installed on a separate drive) and reinstalled everything to get it all working.