Replying to let everyone know the issue still persists. This is a garbage game, garbage GPU and both Blizzard and AMD are garbage companies.
1 Like
The only thing that âreducedâ the crashes for me was disabling the âwindows/xbox game barâ which i actually really liked since i like clipping things in-game, Still getting some crashes every now and then when i alt-tab or change the language using shift+alt.
1 Like
Issue finally made it to r/wow front page:
https://www.reddit.com/r/wow/comments/1cid0sa/blizzard_and_their_refusal_to_address_the_amd/
1 Like
These issues are seriously pissing me off ignore me fine, ignore everyone else by this i mean everyone in this thread seriously??? i really want everyone to get compensated after all these issues are resolved, my self included maybe its time for some legal action otherwise, because this is clearly a scam.
And it got deleted by the user who posted it, guess no one cares about us people that are crashing.
Screenshot of what OP was talking about.
1 Like
It still crashes with the 24.4.1 version.
When I switched from DX11+DXVK to DX12 to test the latest AMD driver, I had to set Wow.exe to be compatible with Windows 7/8 because the shaders wouldnât compile even after 2 hours of leaving the game âopenâ, I had no image, just the courser and the sound.
After setting it to be compatible with W7/8, the game instantly opened and then I removed the compatibility and there was no shader compiling happening at startup, instead, they were compiling inside the game while playing.
AMD drivers are so borked⌠I got sick of it and even looked at selling my card back but I remembered that I did the PTM7950 mod for better cooling and I voided the warrantyâŚ
Additionally, there were some comments on the video that some people have the game crashing hard when patching with DXVK, I canât replicate it, âit works fine on my PCâ.
in the EU i believe you are allowed by law to customize the card, this includes applying PTM7950 or use another cooler, you just have to put it back in factory condition, if that included the warranty void sticker that law would nullify it self so you still have warranty, just not for any kind of user damage which is a pain, cos they can just claim its user damage without proof.
I did PTM7950 on my Liquid devil 7900 XTX as well its kind of a must, anyway i think its more likely they be telling me in my case that the issue is with the drivers or there is no issue, unless they test the card in same game and same location as me, would not surprise me if they considered my GPU dead if they saw the RGB laser show bug in Dying light 2, which is a driver issue that they started to work on since 24.3.1
More about warranty outside the US here.
There is a section for EU the stickers are basically not allowed here either.
Anyway i doubt swapping card between other AMD Radeon GPU would fix the issue, it most defiantly will if you swap it for an NVIDIA gpu though.
Its annoying the crashing issue is not easily reproduce able and random, no idea why some have the issue and some do not, but i think i already know why.
I updated yesterday the AMD driver. Played the whole day on my Frost DK, LFR and M+ and not a single crash.
I wonder if itâs due to particles or something, since in my Frost Mage i used to crash like crazy. Will give it a try in Sunday, to see if i still crash with the mage.
1 Like
Keep in mind old shader cache becomes invalid when you update so you may not experience crashes for a couple of days after updating drivers, i suspect this has been the case for most users.
So do you recommend clearing the shader cache? And if so, how do I do it?
1 Like
Us Intel and Nvidia users are having major issues as well, not just AMD.
The player base has had a massive hit due to perfomance, hardware and general issues with the game.
1 Like
You can clear shader cache in multiple places
In Radeon software gaming > Graphics settings at the bottom click reset Shader cache.
First one win+r type cleanmgr hit enter and clear DirectX shader cache
Last one their is a cache folder in the wow folder like here
World of Warcraft_retail_
You find a folder named cache you can either rename it to back it up if you want to be save, or delete the cache folder.
Every time i did this i went thru least amount of crashes but i would consider this a placebo fix until fact checked if this resolved the crashes.
Same with setting graphic settings in World of Warcraft for example
Graphic effects you can test with.
Only use one AA technique at the same time.
MSAA is most likely broken and has caused pinkscreen or other issues in the past with rendering scale above and below 100% on every resample setting from point bilinear and bicubic, at the time FSR 1.0 did not exist its obvious this would have issues as well.
I only use Image-Based Techniques and used CMAA / CMAA 2 in the past.
Settings that have impacted driver timeouts / system crashes frequency for me.
Compute Effects, low at the time i think could not disable, you can now for testing purposes its worth a try on disabled.
Other effects i would disable, anything with spells and spell effects, such as Particle Density and spell Density on essential.
I would set Resample to Bicubic and just keep renderscale on 100%.
VRS disabled
Audio channels to 64 with audio cache size to small.
Anyway i have given up.
Their are other games that have constant driver timeouts, and their are games i can play for hours without issues, if these issues ever to be fixed, we must give more criticism to both Blizzard and AMD as both are ignoring the issue, AMD probably more then Blizzard.
I am well aware of that, i have had issues with NVIDIA as well such as flickering shadows, and this issue has been back in this expansion as well, the fix for that was to clear shader cache.
For this reason alone i think both AMD and Blizzard are responsible Blizzard for their shader issues, AMD for ignoring the problem even tho its not their problem its still their responsibility to make sure their drivers do not crash or cause whole system to freeze.
1 Like
I have a few observations to share.
Iâve got a power bar from Belkin that has a surge protector. And thatâs something Iâve had with my PC since I was a child so I never really thought much of it. At some point I had to do some changes and a red LED lit up on the power bar, which indicated âNOT PROTECTEDâ. As it turns out, the power barâs plug into the wall had to be installed the other way around to have surge protection.
Since then, the crashes has been much less frequent even in DirectX 12. I did everything I knew I shouldnât do. Enabled hardware acceleration in every program (Spotify, Battle.net, Discord, Chrome, Edge, whatever), I enabled Discordâs overlay, I used the auto overclock feature from Adrenaline, I cranked all WoW settings to the max, with CMAA 2 & MSAA x8, uncapped FPS, had a video running in the background, music playing, Discord in a call. I couldnât get it to crash! âŚuntil it did, on Sarkareth HC. And it didnât recover either. I had to hard reboot.
Okay then. Letâs turn off hardware acceleration where we donât need it, letâs turn off the overclocking cuz we donât wanna test our luck, letâs turn down the graphics settings a little bit. And itâs fairly stable!
| Resolution | 2560x1440 |
| Render Scale | 100% |
| Anti-aliasing | None |
| Shadows | Ultra or High |
| Particle Density | High |
| SSAO | Low, Good or High |
| Compute Effects | High |
| Spell Density | Essential |
| FPS Cap | 165 |
| View Distance | 8 |
| Environment Detail | 8 |
| Ground Clutter | 8 |
| VRS Mode | Standard |
Iâve capped my FPS at 165 because thatâs my monitorâs refresh rate, but Iâve tried 120 which is adequately smooth and probably contributes more to stability. I guess it depends on your GPU, mine is a 7800 XT.
Iâve also had a few settings on Adrenaline enabled for a while.
| Anti Lag | Enabled |
| Radeon Enchanced Sync | Enabled |
| Anti-aliasing | Enhance Application Settings |
| Morphological Anti-aliasing | Enabled |
| Anisotropic Filtering | Enabled |
| Anisotropic Filtering Level | 16x |
| Texture Filtering Quality | Performance |
| Surface Format Optimization | Enabled |
| Tessellation Mode | AMD Optimized |
| OpenGL Triple Buffering | Enabled |
Seeing Eyatiâs pic though, I notice I also have a Samsung 980 Pro SSD and I wonder if that might be a common denominator. I have tried installing WoW on my other SSD, but that didnât change anything. What I have not tried though, is installing my OS on my other SSD.
So what I suspect is that either these cards or the drivers themselves both donât quite handle well shaky electricity and getting stressed out extremely hard. Might have to try getting a better power bar or a UPS. I donât know if anyone here already is using a UPS?
I do not think this is storage related, something i suspected in early days of having the issue, but then i would have issues with other games as well or it must be really weird bug, i am not crazy enough to go down that rabbit hole, i do have 2x 980 PRO 2TB and 2x 860 EVO 1tb and another 2x MX500 2 TB storage though, my game is always installed on my second 980 pro while first one is boot drive.
User settings can have a big impact on crashing frequency, i am most interested in figuring out if their is a single user setting, or clearing shader cache every single time before playing the game, having any impact in reducing the crashes to 0 crashes, because in the end having 0 crashes is the ultimate end goal.
Anyway anything i recommend can be considered placebo until fact checked, what works for some one may not work for some one else, if you play more games then clearing shader cache every single time may not be that viable either, it should not be necessary to do so either way, its something i noticed that has impact on crashing frequency, but as i have given up and lack the motivation to play i cannot really fact check this anymore, also to consider is not to be to quick to judge something fixed an issue, as i know from experience every fresh driver install couple of days i end up having no crashes, as shader cache gets older i start to crash more again, this is the trend if noticed my self, but never verified fully.
But what i do know is i used to have a flickering shadow issue on NVIDIA GTX 1080 that was fixed by clearing shader cache before playing the game, that is why i also do not trust Blizzard, and if Blizzard think i wonât notice that its probably just their game that is broken think again, my recommendation for Blizzard is to fact check and investigate these issues, and if i am right and it is Blizzard fault, you better start compensating users affected, because their is no way i will forgive Blizzard for what they have done during this expansion release.
I was crashing and freezing 3 times a day in Gogrond and i know least 2 games that have issues caused by particle effects although both games cause visual bugs, World of Warcraft has no visual bugs, but it has had pinkscreen bug but cos render scale is bugged i cannot reproduce the pink screen bug, if i could i couldâve checked if their is another work around like disabling particle effects such as compute effects, to see if that prevents pinkscreen bug as well.
The pinkscreen bug just proofs that World of Warcaft has issues, the pink screen bug did not happen everywhere i just knew 1 spot where it happened revendreth, if never tried to figure out where else it happens, else i could verify if these zones have something in common like particle effects.
For info looking at very specific angle with renderscale above or below 100% with MSAA enabled would cause pinkscreen glitch on bicubic other glitches on other resamplers such as point and Bilinear.
Main reason i cannot test or try reproduce these crashes is because my subscription ran out, i stopped playing around early to mid 2023 despite having a 1 year sub, i will never forgive Blizzard for their ignorance, i will never forgive AMD either even if its not their fault they have a responsibility and they just proof they arenât taking any of it at all, which is why i have given up.
I just know before pre patch if had less issues or well never any freezes i believe early pre patch i started to have these driver time outs, that eventually turned into freezes where GPU driver never times out as if tdr delay was set to infnity never allowing GPU to reset GPU driver which what you get when the GPU driver crashes, but for me at some point i started to get freezes, but did find a way to force a driver time out from a freeze but i only had one chance to trigger it, press Win+Ctrl+Shift+B as fast as possible and then plug something in via usb or out, because it will become unresponsive after.
I would get hardware detected sound when you plug something in always, anyway at this point i got so tired of the issue i just started playing other games that had no issues at all.
This not my video but what the user shows in this video is pretty much what started to happen for me and still happened at reduced frequency on my 7900 XTX after upgrading from 6900 XT
And i went thru multiple hardware swaps nothing helped
7800 XT here with a UPS on. I crash and sometimes my computer just straight shuts down. Like completely powers down. People say that its temperature but i am sure that it is not. Plus, like eyati said, i have played much more demanding games like Kena Bridge of Spirits and Plague Tale: Requiem and had near 0 issues (I think i had 1 crash on plague tale and that wasnt even a graphics issue, the game just stopped responding). So it could be my PSU (?). In any case, if I had to bet on what the issue in general is then i would place it on WoWâs old game engine (and therefore old shaders) which needs a major rework from the ground up. A game with this graphic quality shouldnt run on such low fps
1 Like
Shutdown can be due temperature or PSU problem if it does not power back on right away its PSU problem, alternatively could be cos your UPS is not handling it and dropping out, the UPS has to be stronger then the PSU
Sooo⌠whatâs the verdict on the new patch? Are we still crashing?
EDIT: Nope. Just crashed.
2 Likes
We will have crashes in the next expansion, and the expansion after that one. This issue isnât being looked at.
3 Likes
I could replicate the crash multiple times while questing in Hellfire Peninsula. I had 3 crashes in a row while doing the quest âZethâGor must burn!â Alliance side. When you place the smoke beacon under the towers to mark them and the game renders this fire/explosion effect it crashed my game immediately with borh monitors going black, driver time out error, game recovering itself and it happened in 3 out of 4 markings. Played roughly 3 hours without having an issue except then.
Could anybody try doing that quest? Maybe it crashes for you as well.
My hardware is also 7800x3d and rx 7900 xtx btw.
I just got my new 7900 xtx after sending the old one back and having the same issues. I thought maybe thatâs a system issue but seeing all of you having the EXACT same problems gave me some relief.
1 Like
Do not buy the next expansion and honestly this may suck but i would just let the sub run out and cancel sub, and link this topic as reason why.
Do a video recording of doing the same stuff you just described step by step and reproduce it again and then share it here, and also share it in a bug report via the AMD Bug Report Tool.
If its easy to reproduce then AMD must be able to do so as well, even at Blizzard they must be able to reproduce it.
This is the kind of stuff i would be looking for to try reproduce.
Show any graphic settings as well as configuration, in some cases it cannot be reproduced because configuration is not the same.
1 Like
- I have same problem on my NVidia graphic card . all other Wow Clients can create Dx11 device and launch game through dx11 instead of dx12 in case if game has detected some older models gcards . but only Cataclysm after pre-patch updates it no longer able to create dx12 / dx11 . also i was thinking blizzard is working to fix this problem max until Cata release but i see some changes today which very disappointed me
in last week since this problem started with Cata client i was seeing something like
Your accelerator3D driver doesn't support Duel-TMU . please install a driver that support Duel-TMU ...
------------ ----------- ------------
( I just skipped some none important report of this error )
- But today i noticed a change which is not telling me that error , Instead its now telling me
your accelerator3D drive is not supported by world o f warcraft !
- can Blizzard please clearly explain what is going on ⌠I mean If it is goanna be stay like this so people will know their device is not supported by game anyway! but if its just one of millions pre-patch bugs so at least we know its going to be fixed by Cata release ⌠I wonder how there is many of players having this issue with different graphic cards models I see people who have same problem with almost every Graphic card brand every module but there is still not any specific Topic which will explain what is problem about ? Is it a bug ? its a new change in game ? I know these are busy days for blizzard but please fix this
