Video driver crash in World of Warcraft with AMD video cards (7900 XTX) on DirectX 12

Support Technical Support
446

I’m at my wit’s end here.

AMD says they could not recreate the issue and that I should contact the game developer about it.

All Blizzard suggests is that I post on the forums and reach out to AMD.

I sent my card back to my retailer and they just returned it back.

I took my PC to a repair shop and they said they couldn’t recreate the issue.

I get my PC back, 2 minutes into the game and I’m getting timeouts again.

The worst thing is nobody cares to get more in-depth about the issue.

Maybe this is an issue with my monitor or my DP cable? Although switching to an HDMI cable didn’t fix the issue. Switching to an NVIDIA card fixed the issue though.

This is ridiculous, just how can we ever get this issue recognized and fixed?

1 Like
447

DX12 still results in a crash, sometimes it happens within an hour, sometimes within several hours, but eventually. It sucks

2 Likes
448

As long AMD or Blizzard do not realize the issue is very annoying to reproduce and defiantly happening despite not taking the time yourself to test we are doomed.
You cannot reproduce this under 10 minutes at will sometimes not even under 1 hour, does not mean its stable, when i used to play i used to play 10 hours a day, and pre expansion patch leveling daily thru wod i froze or had driver timeouts 3 times a day the driver timeout if lucky, then couple of days nothing at expansion launch followed by freezing or having driver timeouts once a day in both dx11 and dx12 its now been 500+ days waiting for AMD/Blizzard to recognize the issue.

If troubleshooted and tested my hardware for weeks without result, if AMD/Blizzard wants to ignore me fine, but if you gonna ignore others i am gonna get mad, and i am mad no i am furious like seriously wtf

Pretty much this post in a nutshell

edit: i turned it into a video

while playing the circus theme song in background.

It describes what i am going thru, no amount of stress testing is gonna expose hardware issues, this is a game and driver issue, both AMD and Blizzard are responsible.

4 Likes
449

We need to keep this thread going with examples of people having this issue and also what troubleshooting people did to attempt to resolve this.

In any case, thanks all for the updates - hopefully Blizzard will fix this in the near future.

2 Likes
450

5 crashes in a single BRH run, veeeeery nice!

2 Likes
451

In past i always suspected compute effects to be the issue and my crashing in the past did reduce but never go fully away, but with ongoing trend i am starting to see it may just be that these settings could impact crashing frequency

Cos these types of effects are usually rendered in another plane or dimension so resolution of these effects can be altered, without affecting game render resolution and to make sure AA does not apply to these effects cos it heavily impacts performance otherwise.

One setting i already mentioned
Compute effects.
spell density can also potentially affect crashing frequency.
as well as particle Density

It may be worth setting these all on low and see if it affects crashing frequency, but just because it does not affect it does not rule out the possibility that it may be related, i highly recommend developers of this game to investigate the issue.

One way a community developer helped me from Sons of the forest, troubleshooting crashing issue that was happening for a lot of 7900 XTX users is find out what caused the crash, when i inputted command to disable the water the crashing stopped, and thus a patch was released to make low water settings not crash the game, eventually all settings where patched.

the only issue is this cannot be applied in this case unless you find one specific user that can easily reproduce the issue at will that is willing to work with Blizzard.

Maybe its both related shaders and the effects, and maybe i am just sounding crazy right now, but this issue needs to be resolved because my sub runs out in 5 days and in such time i cannot reproduce the issue, i am to busy exposing issues that been ignored all this time, cos i am tired of nothing happening, not just with World of Warcraft, but AMD in general.

452

I took the liberty and made a video guide based on your solution.

The patch worked fine for me with the latest releases to WoW.

https://youtu.be/odZMiqO0IBs

1 Like
453

I have played on Linux without crashes, but i did not like the lowered performance at the time, Linux cannot work without dxvk, and dxvk has fixed crashes for me in the past with Sons of the forest as work around until devs fixed it them self, just got to be careful in other games with anti cheat, modifying files is not allowed, but you are not modifying any files of the game atleast in World of Warcraft and Blizzard does allow users to play on Linux even mentioned this before, however dxvk technically reroutes stuff from directx to vulkan, Blizzard basically allows it thru Linux and probably Windows as well, but with other games if they are reported to not play on linux, you better off not using dxvk probably as well.
Just do not use dxvk async in any online games probably not save in World of warcraft either, the regular dxvk that you want is from here.

Future driver is gonna fix shader caching issues when using dxvk i believe.

Anyway all of this should not be required, and AMD and Blizzard seriously need to work together into fixing this issue, rather the keep pointing at each other on who is to blame.

I have had my own thread, and Blizzard never even responded and just locked the thread as if its just another AMD Driver issue, pathetic.

455

is there any update on this topic because it is an open topic from last year november or something like that and its very annoying geting random black screens freezes and driver crashes all the time.

1 Like
457

Refer to Freajka post

There truth to he’s post cos linux uses dxvk, and if been stable in linux before, i just dislike the performance of dx11 or even using dxvk it may improve in future AMD drivers when they make shader caching act much faster using vulkan even while using dxvk, this should not be needed but it works for most users.

458

Does that work around completely eradicate the crashes?

459

if it does not it will once you switch Linux, cos that would mean the problem is Windows.
I would just give it a try it may be the only real work around that works, i am more interested in why it happens so it can be fixed for real, but if given up and i cant force some one to figure it out for me.
However that is Blizzard and AMD problem at this point.

They seem very interested in bugs right now but prefer to quickly reproduce issues, rather then spend hours which is required in this case, cos they keep asking for save game state right in front of where issue happens.

Problem is these issues can often trigger at more places.

It’s kind of depressing these days i find problem, i google problem, i find out AMD users been complaining for months maybe even years, only to find out AMD been ignoring the problem, they have a serious issue if i can just figure out issues been around for months or even years, it also seems playing another game i cannot escape this reality of finding new issues, some of which that have been reported months ago or years, there are so many driver issues that you could start a meme channel about it.

Anyway for this particular issue its more important then ever that Blizzard cooperates with AMD, or this will never be resolved.

Issues experienced by users.
Driver timeout if lucky, otherwise system freeze that may trigger into a timeout, usually not the case, and for some this happens multiple times during same run or once a day, or every couple of days.

The game should not crash even if you had a session for 24/7 it should not crash, it should be stable, lets not normalize these crashes because they aren’t normal anything less then 24/7 stable is unacceptable.

Speaking of which if you crash once even with AMD Radeon Drivers and then more times, that means driver is in a bugged state, a reboot at this point may stop the chain of crashes during that specific run, what is probably more important tho is what causes the driver to enter this bugged state.

And bugged driver states are real, for example Doom Eternal triggered blackscreens during alt tabbing in past if HDR is on in game and desktop, the fix was to either restart or better yet, fire up Doom Eternal again and disable HDR via the in game options, and then test if blackscreen occured during alt tabbing, which it did not, but as soon HDR was set enabled in Doom Eternal it would cause black screens during alt tabbing in World of warcraft with Windows autohdr feature enabled and other games with autohdr, this happened regardless of the game Doom Eternal having been exited and proofs that a game can leave the drivers in a bugged state, this probably happens all the time for users with these kind of issues, and this is no user error, this is just poor driver design, as exiting the game should reset driver states back to previous state.

Just like for example if AMD Cleanup utility is ran without safe mode, it will reboot into safe mode by enabling safe boot to remove AMD drivers, but in rare case it can forget to turn off safe boot when done, which makes you constantly boot into a safe mode loop, which is fixed by hitting win+r type msconfig and navigate to boot and uncheck Safe boot, which once again just proofs how incompetent AMD really is, because their wiki for the tool explains to use system restore while there is a very easy solution available to this bug.

For me if i use system restore my windows bricks, system restore has been broken for me since Windows 11 got released, and should probably never be used, i have alternatives tho, anyway this bug was reported like more then a year ago and probably ignored by Microsoft, just like most issues i report.

Same with AMD and i am getting tired of it.

When games are not playable for me that i wanna play, i end up spending days helping others troubleshoot their issues, rather then playing games that i wanna play, such as World of Warcraft or even Hell Divers 2.

I wonder when Blizzard wakes up and compensates everyone their game has been pretty much unplayable for Radeon users for 500+ days and that is putting it lightly cos it probably been much longer.

460

For me it completely removed all crashes. I have no crashes in 4 months with Taylor’s solution I showcased in the video guide.

1 Like
461

Just dropping this here this is an AMD specific bug i cannot reproduce anymore happens in revendreth and more unknown areas when renderscale set below or above 100%, when looking specific directions.

The result it produces depends on what resampler is selected point bilinear or bicubic.

FSR 1.0 was not out at the time, imagine FSR 1.0 result being driver timeouts or freezes.

I want you to think for a second, and then consider raising your voice progressively louder, you have every right to complain, you have every right to be angry, and you ever every right to keep nagging on the AMD Bug Report Tool or other support channels on both AMD and Blizzard forums, and to not stop until there is a solution either a full refund compensation not to mention a fix which perfectly reasonable.

If Blizzard and AMD wants the nagging to stop, they can simply just fix the issue, heck make memes about your problems, if they do not like it they can just go and fix it.

462

I did send a ticket to see if the problem is going to get fixed or anything and got replied with a copy paste troubleshooting message “translated by a machine” then I asked for a real response and they marked the ticked as Resolved.

I previosly sent a ticket and they aknowledged the problem (this was 4 months ago). The first time I contacted them was half a year ago but I already asked support with AMD back in November 2023 after trying many things but nothing worked.

If they respond at all saying we don’t have enough reports they’re lying. I’ve been having these crashes since I got my 7900XTX and that was over a year ago. I even did an RMA because after trying 1000 things I thought my GPU was faulty or something and got a new one with exact same results.

My mistake was purchasing 1 year of WoW subcription thinking “I’m going to play anyways”. At this point they aren’t going to fix it (if at all) until The War Within. What a joke of a company

463

Same thing here…
I hope by the time 11.0 comes out, this issue will be resolved. Literally paying a bag of money for an AMD product and then not being able to play your favorite game is ridiculous.

464

Wouldnt really say its even a “solution”. Youre just using a 3rd graphics API, instead of DX11 or DX12, which is worse than DX12, which our product should be able to utilize.

465

We nearing the next expansion, its time to just start for compensation for this scam called Dragonflight for being worst expansion ever from a technical point of view, cos all it has is crashes freezes visual bugs Activision Blizzard and AMD ignores.

Its the best you got to fix these crashes, and probably the only real fix.

466

Jesus Christ.

I bought new Nitro+ 7700 XT, playing Plunderstorm event and once per 2 games the game freeze, black screen and error. Last time I had to turn my PC off.

Every other game works perfect.

Sadly it is still a thing!

2 Likes
467

Meh. I’d argue it is a solution. The game crashes are “solved” with this hack. Valve saw DXVK as a good enough solution that they made an entire handheld gaming console with that solution as it’s backbone.

But no I do understand where you are coming from. Being completely unable to play a game I pay £10 a month for on a graphics card I paid £780 for without having to do a hacky tweak I had to think of myself, is disgusting.

2 Likes