I started a post a week or two ago and havent had any update but been looking at other posts to try and find a fix
This is my first topic I posted with no update for a while ^^
I tried to reply to my old post with this down below:
this is the error log if the first time I crashed with this error ^^^
And this is the most recent error log of the same crash type ^^
To clarify
Have taken out and cleaned the CPU and entered a new GPU 3060, and installed new ram (32GB > 64GB)
Still same issues following from other similar posts, i have tried to make changes from those posts to try and help out my situation to no avail.
I am now at the point of “plz help am at my wits end”, again this is only occuring in retail WoW have been playing classic cata instead with no issues of this sort, and recently played Spacemarine 2 with no issues at all.
I’ve been running into the same error since I started playing TWW with my Alienware R16 with with i9-14900KF 3.2 Ghz and Nvidia GForce RTX 4090.
I have all drivers and bios updated per the identified issue articles and tried the band aid fixes with every graphical option in wow. Nothing works for more than maybe an hour and I have died so many times in game due to erroring out in combat, and just overall have a broken game.
I was super excited for this expansion and have enjoyed the content, but I have cancelled my sub after just one month of playing since the xpac released due to this nonstop issue. I am deeply disappointed that Blizzard/Microsoft and Intel can’t figure this out.
Hopefully they get this resolved someday so many of the players that have invested in this game can actually play it.
This issue was extremely prevalent for me a couple weeks ago then seemed to vanish completely with a wow update. As of another minor update a few days ago, it appears to have returned and I’m crashing without rhyme or reason. Sometimes I’ll play for six hours straight, other times I’ll crash eight to twelve times in rapid succession despite nothing going on around me. Very random.
Mine started a few days ago as well. Played absolutely fine right up until 3 days ago and now it’s just completely f’ed. I am sure it’s just a coincidence that every other game is fine except WoW, and that it came literally out of nowhere. It also seems to be exponentially worse when the characters are logged on in Dornogal. Nothing seems to help. Only thing I have not tried yet is a complete Windows reload, but being as this is simply a WoW problem I really can’t be bothered. Their tech MVP’s are just running around the forums blaming people’s computers, cuz Intel.
My BIOS was already patched for the microcode update weeks ago when it was first released, so unless the mobile 14th gen i9’s are not covered by that then my CPU didn’t magically nuke itself after the update.
Hey Elocin have you been able to find anything that might be affecting AMD CPU users by any chance, when I say I have looked everywhere I genuinely mean I have, whether its just a simple google to reddit post to looking through tech forum posts from a few years back, i’ve gone through my BIOS more times than I can count to change CPU settings / GPU Settings / RAM Settings. I attached my WoW Error Logs so maybe that might have a clue as to why im having this error, I spent about 7 hours with a techy friend of mine yesterday and he did everything he could think of that could potentially cause this error to pop up only to still have the same error come up, I was mainly testing when dying and hitting release spirit and then running/flying back to my body to accept rez only to have the error come up both times of releasing and accepting
It is not an Intel issue on my side. You see I had a 13th gen with this issue earlier this summer and sent it in to Intel and got a new 14th gen processor guaranteed without the manufacturing errors. I followed the guidelines from my GPU and CPU and with the new CPU my computer wasn’t crashing playing WoW anymore until the recent WoW update. Now I’m getting the same Access Violation Error… no other games are affected Destiny 2 for example which when I had the error was affected. So this is definitely something on Blizzards end. I tried a repair on my game, uninstalling addons, etc and it still happens randomly. There is no rhyme or reason that I can find it just crashes… Sometimes in Dornogal, sometimes in raid, sometimes just afk out in the world when I get up to go get a drink while doing dailies. It is 100% random.
So the question is, what did Blizz break on the last patch?
Since I’m not running an AMD CPU or experiencing these crashes, I don’t have memory dump files to scour for the crashing reasons. You may be able to get someone on the Windows forum to review your memory dump files/crash logs for the reason. If it’s the CPU, they will likely recommend turning down the voltages.
Anything happening in the MSInfo Error Reporting (can only see this after exporting the report)?
Elocin could you possibly respond to my post as well? I have sent crash reports to Blizzard all week, done everything I could think of on my side and to no avail. As stated my new CPU does not have the Intel problem of its predecessors and is a new batch void of the oxidation and voltage problems. Therefore I know 100% it is not an Intel issue. Also my computer when it was an issue had issues with other games like Destiny 2 none of which are crashing. The WoW crashes are bizzare as well since before the crashes only occurred in raids or on loading screens, not when afk in the world. Also the frequency was constant before whereas now its random. Plus there are others who have stated problems since the patch of last week, quite the coincidence no?
That Intel advice doesnt pertain to my situation… this is a new cpu from a new batch without the errors and the bios is updated as I already stated. You can contact Intel if you want, they are allowing affected 13 and 14 cpu owners to turn in their old CPUs for new ones its a lengthy process to which they ENSURE and yes I have paperwork that these new processors are not faulty. So why the issues? Can you confirm without a doubt that there is no connection to WoW being the source of the errors? Are you that confident to say 100% it’s on us and not on some error that arose in the last patch/update?
This whole it’s not our problem… it’s yours is not helpful in trouble shooting. At least mention it to someone at Blizzard that something might be faulty on their side and that multiple people are experiencing this issue when it was previously resolved.
If you put a ticket in and ask that question.
You might get a answer from them.
This forum seams to be a off hands from Blizzard. Once in a while one will pop in here a say something, but most of the time it is player to player help forum.
I am just frustrated. I can’t play this game with these random crashes… I made a guildy untime a key tonight because I dc’d twice on the second boss of thier M+7 Necrotic Wake… On Tuesday I dc’d twice on a raid boss… yesterday while questing I just dc. These DC’s are ruining the game for me and I cant find any problems besides with wow… My husband uses the same computer and has no issues on his side and he’s playing new games like Star Wars Outlaws.
I have played WoW since Vanilla… never ever have I had these issues before. I really really thought it was my CPU… went through the hassle to get it replaced, just to have this bug return this past week is so disheartening… Blizz is silent to the myraid of bugs already in game and now this one makes it unplayable in many regards for me. I am a liability to my guild and friends because I cant even tell when I DC… This forum used to long ago have blues who would respond… who would offer help from their side. I appreciate what you are trying to do Elocin… but there is nothing you suggested that has helped… maybe someone from Blizz could be of more assistance if they ever have the inclination to offer customer support like they used to
So I have a WILD fix that has allowed me to play with no crashes as of yet or atleast all my previous causes for the error to come up is not causing ANY crashes, decided to uninstall and reinstall the game again, but I changed the install path to my secondary Harddrive (not an SSD though so it is turbo slow to load in) but I have a feeling it was trying to write something on my SSD that couldnt? I am going to try and reinstall back on my SSD but in a different directory rather than my standard World of Warcraft Folder and see if it happens again after, if you have any tips or tricks that might help?
Also my MSInfo didnt have anything in regards to errors that I could find
Edit:
Can Confirm have reinstalled onto my SSD into a different folder, and no more crashes if I can link anything to maybe help others from prior error logs please let me know @Elocin
Interesting. I tried moving from my game SSD to my main SSD and it didn’t help, unfortunately. That being said they are identical drives, so maybe that has something to do with it. Seems like the answers are all over the roadmap for what works vs doesn’t.
The recently added graphical compatibility settings may also be of effect so try toggling them off if you haven’t, that is something I’ve read on reddit before.
Or the toggle for Hardware-Accelerated GPU Scheduling in graphics settings in Windows where you change monitor settings may or may not cause some trouble too, but it’s usually disabled by default.
I get the access violations very very rarily, but all other things on my system are fine and never crash or anything so I just leave it as it is.
My i9 13900K is nearly 2 years old, oldest 0219 bios on ROG Maximus Z790 Extreme and 0x10B microcode running with -0.06v undervolt but with all power limits removed and 128GB DDR5-5600 XMP CL40 running at 5400Mhz to avoid memory errors, which is already an exceptional speed with 4 sticks, but no actual problems with it.
Newer bioses sadly ruined things for voltages ironically damaging the CPUs with the newer microcodes, and the latest microcodes only run marginally slower with them trying to fix it but the damage is already done for those. Guess I dodged a bullet.
Rest of the system is just an EVGA GTX 1080Ti FTW3 running on 546.33 WHQL because I tend to be too lazy to update those and generally the Nvidia drivers, even in newer games are pretty stable for me and have generally been for the past 20 years so and the game is installed on one of the two 990 Pro 4TB NVMe drives running Windows 10 22H2.
Something I should also add, if you are an AMD user, my friend also went through and changed some of the “Boosting” Settings in the BIOS, specifically the CPU and any Memory Boosting options to disabled or left on “Auto” without any Overclocking or Additional Boosting option if that makes sense - we also took everything out (RAM - Graphics Card - CPU) and just cleaned them all and put them back, while it was something for me when we took the CPU out and saw how much paste had been put on it, and while I had no heating issues it seemed like something that we shouldve done. Even after all that I still had the error popup.
Now I uninstalled WoW through the client, and deleted the entire “retail” folder and installed to my D:// Drive, let it complete and started the game, tried 3 of the things that I originally had listed as causes of the error coming up, and they didnt, so then uninstalled and reinstalled back to my C:// drive but changed the directory, so I made a new folder didnt even name it, and installed it into there, and havent had the error pop up once and been playing fine for the past week or so since I did that
