arkayenro / arkinventory

A World of Warcraft Inventory mod for Retail, Burning Crusade, and Classic
108 stars 14 forks source link

[BUG] Hard WoW Crash - Cannot Divide by Zero #1949

Open ruffianopatsu opened 2 months ago

ruffianopatsu commented 2 months ago

Version: 3.10.33-Alpha-27 Client: Retail Language: English

Pretty much randomly crashes, and once that happens, I can't load back into the game with the addon loaded without instantly crashing.

============================================================================== Exception: 0xC0000094 (INT_DIVIDE_BY_ZERO) at 00007ff670392866 ProcessID: 5796 ThreadID: 13664

Exception Crash 0xC0000094 (INT_DIVIDE_BY_ZERO) at 00007ff670392866 (DBG-OPTIONS DBG-ADDR<00007ff670392866>("Wow.exe") <- DBG-ADDR<00007ff66cf6be77>("Wow.exe") <- DBG-ADDR<00007ff66cf7087a>("Wow.exe") DBG-OPTIONS<>) <:Exception.Summary> ------------------------------------------------------------------------------ 11.0.0.55846 55846 11.0.0 Mainline World of Warcraft Client ---------------------------------------- Lua Stack ---------------------------------------- [C]: in function 'resume' Interface/AddOns/ArkInventory/Core/ArkInventory.lua:14206: in function 'ThreadResume' [string "*ArkInventory.xml:2434_OnUpdate"]:4: in function <[string "*ArkInventory.xml:2434_OnUpdate"]:1> 11.0.0.55846 Retail Type: WoW Wow.exe
markdall commented 1 month ago

If you have a 13th or 14th gen Intel CPU, that's the problem. tl;dr time to change some BIOS settings AND RMA your CPU under warranty, like they're doing for me)

I had VERY similar symptoms. Built my PC in November, it was fine until May, got super bad in June. By about mid-June I could only run WoW without crashing if i disabled every addon.

Then I figured out that if I disabled Turbo mode, I could run wow with all my normal addons etc. I started seeing hardware review youtubers talk more and more about it, and finally found a document from a company called Oodle that said to set the "p-core ratio" to 53 or 54. Mine was at the default of 57. Turbo mode is back on, and it's been fine ever since.

Then I found https://old.reddit.com/r/intel - see the pinned threads. There's a bug that causes the CPU to request so much power it damages itself. They'll have a BIOS update out to prevent this sometime in mid-late August. But this will only prevent future damage, not undo damage already done. It's Intel's fault, and Intel is honoring their warranty, at least for me.

Obviously if you have an AMD, nevermind and sorry for the spam. :P I'm just trying to help because this annoyed me greatly when it was happening to me.