I find this insanely funny that the only game or application that I have a problem with is WoW, but this is supposedly a CPU issue?!? What sense does this make? If it were a CPU/hardware issue, I would have been experiencing these crashes on this machine the first time I loaded WoW onto it. The crashes started happening for me around 4/12/25. Others have stated this is the same date this started happening for them as well. This clearly points to the issue being something related to a patch in WoW. I really wish Blizzard would actually own up to this and respond.
2 Likes
I have the same problem, not sure what to think at this point.
Unfortunately, this makes me incredibly unreliable in mythic plus or raids. I may just have to take a hiatus until the next season and hope that the issue is âquietlyâ fixed by then.
Except the crashes have stopped for most people that have either turned off speed step or AMD turbo core. Or dial down the maximum boost. For Intel 14th generation at maximum boost only two of the cores are stable 13th generation at maximum boost 4 Cores are stable. The 7000 and 9,000 generation AMD CPUs also have the same issue that not all of the CPUs are capable of being stable at maximum boost.
1 Like
If it was a general cpu issue, i would see this across the board for anything. Playing games, running other apps, browsing the internet. This crash ONLY happens with WoW. Even if tweaking BIOS settings âfixesâ the problem, it doesnât mean that WoW is not causing it. It is HIGHLY unlikely that a cpu problem would only manifest itself with one game crashing.
Also of note, the whole pc doesnât crash, just the wow.exe.
2 Likes
Actually you wouldnât . Wow puts a majority of its load on a single core. With three other cores being utilized by the game. The fact that it puts such tremendous load on a single core means that if that core is not 100% stable the game will crash. Other games and apps spread the load evenly across all the cores. A lightly loaded unstable core is unlikely to crash. The fact that wow actually heats up the CPU more than anything else that Iâve ever seen including everything I have ever played. The CPU actually gets hotter playing wow then when I ran a benchmark test on my computer
1 Like
Sounds like the developers didnât know what they were doing then when the game was designed considering other games and apps do not do the same.
Except they sure did. The game was released in 2004 and back then most games only utilized a single core. Dual was also used some but most games were optimized for one. DirectX 9 was also the version at the time and only allowed a single core to talk to the GPU at a given moment, hence heavy single core usage.
The game still runs on much of that same engine, but it has been modernized here and there. It can now utilize more cores more effectively (though obviously still has one main heavy use core) and can use DirectX 12.
So yeah, Iâd say they have quite good engineers who can work within the limitations of what they were given at the time, while still being able to upgrade the engine when possible over time.
Sorry. Was away most of the weekend and forgot about this.
This what youre looking for?
Operating System: Windows 11 Pro 64-bit (10.0, Build 26100) (26100.ge_release.240331-1435)
Language: English (Regional Setting: English)
System Manufacturer: ASUSTeK COMPUTER INC.
System Model: ROG Strix SCAR 18 G834JZR_G834JZR
BIOS: G834JZR.320 (type: UEFI)
Processor: Intel(R) Core⢠i9-14900HX (32 CPUs), ~2.2GHz
Memory: 32768MB RAM
Available OS Memory: 32386MB RAM
Page File: 15410MB used, 19023MB available
Windows Dir: C:\WINDOWS
DirectX Version: DirectX 12
If you have a 4090 then you are lucky enough to be able to roll back your GPU drivers. The last truly stable driver nVidia put out was 561.09. What driver are you currently using? There were a ton of faulty drivers put out by nVidia over the last couple of months (OK, since the 50 series launched to TBH - their drivers are massively jacked and the very latest driver was actually a hotfix driver that you have to go digging around for as it isnât (or wasnât) on their main driver search list last I checked.
Regarding the DIV 0 and access violations - are all of you that are having this issue on Intel 13th and/or 14th gen CPUs? The type of core instability currently described in this thread has all the markings of a CPU that has already begun degrading. There were a series of BIOS updates last year ending in November that most vendors put out to attempt to mitigate the issue with these two generations of CPUs, but if your CPU has already begun experiencing the access errors, it may be time to immediately start the RMA process with your vendor (ASUS, MSI, etc., whoever built your PC) and get that CPU replaced ASAP, and I do mean ASAP. Iâm already seeing reports that Intel is once again trying to sweep this under the rug and deny RMAs like they did when the problem first became widespread and commonly noticed.
This particular issue affects every Intel 13th and 14th gen CPU. AMDâs CPUs should be good to go unless youâre still on a BIOS >2 years old and running a 7xxx X3D CPU. Those CPUs needed a BIOS update as well because the motherboard manufacturers were juicing the CPUs with too much voltage and enough amps to actually cause collapse of the CPUâs conduits that house the copper interconnects within the substrate in more extreme cases.
The bottom line here is that the issues described in this thread have the eerily unsettling hallmarks of CPU degredation, right down to having to swap to a more âstableâ core, which for the Intel CPUs is a virtual dead giveaway that your CPU is on the fast track to destroying itself.
And yes, it can manifest itself in âjust one or two appsâ, especially if those apps are heavily CPU bound, as WoW is. Check your BIOS version by pressing Windows + R, typing dxdiag in the resulting text field and hitting Enter. Youâll see your BIOS version listed on the very first tab. Check that against your system manufacturerâs latest BIOS update. If your BIOS predates 11/2024 (November), you need to update your BIOS. However, and I really hate saying this, those of you experiencing these issues and whom are on Intel 13th or 14th gen CPUs are almost certainly going to need to start an RMA to get a new CPU. Just remember that if you need to send in your system, to either back up your data and wipe the drive(s) prior to sending it in or take the drives out and send in the system sans drives to protect your personal information.
I am on a 4090 with an i9 19500KF. I tried to roll back my drivers via device manager and there was nothing there to revert toâŚthis PC is really new out of the box by a few months.
If you are attempting to roll back the GPU drivers, you will want to use Display Driver Uninstaller (DDU) to remove the current driver and roll back to a known stable driver. 561.09 is by consensus of most users the most stable release prior to the 57x series drivers. Make sure to follow the instructions precisely to ensure complete removal of your driver.
Edit: 561.09, if you do not already have it downloaded, is no longer shown on nVidiaâs download search page. Theyâve nuked their âolder driversâ archive, which makes it very difficult to find good drivers to roll back to. The oldest driver, 566.03 is your best bet as that is also a known stable driver. Youâll want to download the driver to your desktop and have it ready to launch once youâve removed the previous driver with DDU.
Edit 2: Here is the 561.09 download page if you want to try it instead of 566.03.
Well, I have installed and run Prime95 and ran the torture test for an hour with no stability problems. If this was indeed a cpu problem, I would think that it would have buckled under a cpu stress testâŚ
1 Like
Again wow puts more stress on a single core of the CPU than a stress test. Almost everyone that is turned off speed step or change the multiplier to 52 x or 53 X has had there issues go away. Very few of the 14th generation Intel CPUs are stable beyond 53x
1 Like
I get the same exact crash on my 14th generation Intel if I take it out of itâs stable overclock and letâs speed boost boost the clock. The reason I do not have any of these issues with any of my computers itâs because they are permanently overclocked to the maximum clock that the CPU is stable at without driving the voltage to the point that I am not comfortable with it
Guys, itâs the Nvidia drivers. Or at least it was for me, I went to the Nvidia drivers website, looked for the drivers for my card (4090). And scrolled down to a driver from a time I remember things worked fine. Hit download, install, and thatâs it. No need to uninstall previous drivers (although thatâs a good advice)
I downloaded the 572.60 drivers for my 4090 and now the crashes are all gone.
1 Like
Logging into wow in the middle of nowhere do not put more stress on the CPU than a stress test. The majority of my crash happened while in the loading screen. Thatâs not a CPU stress issue. I ran multi stress tests in game with epic 40man BG and 40 man raids and the game ran just fine, no issue there.
The issue youâre talking about might help for people with older system. For newer system with update BIOS before damage to the CPU, thatâs not the problem.
On a single Core it does. As soon as you load into awow. one core will Spike to almost 100%. Then it drops back down. And again if you have a 13th gen or 14th gen Intel CPU it is unstable at anything above 53 x.
. Even if you have updated the BIOS. This chips are still not stable at full boost most of the chips will not take 60 x. They are stable somewhere between 52 x to 58x depending on if you won the silicon lottery or not
Then my game should crash long before then. Itâs not going to wait till 4/12/25 just to crash at the same as other people.
1 Like