This seems to be a separate issue entirely that was introduced with 10.2. Each patch since 10.1.5 has created more DX 12 problems.
Try using the -d3d11 command line argument in the bnet launcher for WoW under game settings. Thatâll force it into DX11 and see if it still crashes that way. I noticed if I just did it via the ingame settings, itâd set to DX11 but then revert to DX12 randomly.
When I launch the game even without that command in my options it says im using DX11, unless the game is lying and saying its 11 when its actually 12. My framerates have been worse than id expect for 12 tho so im sure im crashing while on DX11. Like I said before if i try to swap to 12 in settings it crashes the game, but i think thats a separate issue to the crashes in getting while playing.
i have 7900xtx and was having problems with crashing in dungeons. i rolled back to 23.5.2 driver-may 31 and so far dx12 is working and no crashes. ill see how it goes over the next few days.
update, it did not work. it crashed on my 3 dungeon of the night.
1 Like
I have
- Tried a number of different versions of previous drivers, including installs with or without adrenalin using DDU
- Underclocking / undervolting the card
- Reinstalling Windows completely with new chipset / gpu drivers
- Replaced PSU cables, monitor cables and reseated all components
- Tried different other recommended solutions âMPO disabledâ / âhardware accl disabledâ
5800x3d & 7900xtx
This card worked brilliantly when I got it in June and I was very happy, I bought it because of the poor performance I was having in Diablo 4, and then when I came back to WoW the performance was great until it started crashing around 10.1.5 / 10.1.7
Please blizzard help us, this is the only game that crashes for me
Same here, Ryzen 7800 x3d and 7900 xtx, 64 gb ram ddr5 6200 mhz, every game i play works amazing, but wow doesnât.
I canât even play Fyrak/Tindral, the screen froze like for 1 secord or the game close with the #132 memory fatal error. What suppose we have to do? Tried to swap from dx12 to dx 11, that did nothing, game keeps crashing. Today was insane got 4 crashes on Fyrak heroic (during the same fight)
Interesting thing happened yesterday. In a +20 DOTI Fall, right before the second boss (sandy dude) my entire group lagged. I was the only one with an AMD card (so I crashed), but everyone else with an NVIDIA card actually lagged without crashing.
Exact location was in between 1st and second portal from the right, outer circle before engaging boss.
I often personally crash in this area, so I found it super interesting that everyone else would experience lag whilst I happened to crash.
Thought this was worth mentioning.
10.1.5 is exactly when this issue started for me as well, prior to that it never one time occured.
3 Likes
If it was Nvidia having this issue, blizzard and nvidia would have fixed this months ago. Because we have AMD Cards they donât care, see us as inferior players
2 Likes
thanks worked for me i never had this issue till i upgraded to an amd graphics card which was the past two weeks.
Itâs still so strange that no one addressed this. Only WoW is having crashing issue but not other games.
2 Likes
Having the exact same issue with my 7900XTX. Of course, there is radio silence from Blizzard on this. I have found that doing the -d3d11 fix + setting all graphics options to low is stable thus far. Kind of ridiculous that I am forced to play on lowest settings with a $1k GPU because Blizzard doesnât properly test things with AMD graphics cards.
1 Like
7900xtx. Same issue. I even replaced a cord thinking it was the graphics card.
Has anyone noticed this same issue with any other games?
1 Like
7900xt
This has got to be the most annoying bug in the history of wow. Random. But happens most often for me in the Manifested Timeway boss in Galakronds Fall. Usually only a couple of times on this boss but tonight it happened over 7 times and my group had to give up. And this time there was a Blizzard Fatal Exception error. Access Violation.
I have been blaming AMD. This is my first AMD GPU and boy have I been regretting it.
But maybe it is WOW?
2 Likes
Itâs just WoW, since it doesnât happen in any other game. However, it doesnât really matter if Blizzard doesnât give a timely fix right? The struggle with AMD cards is that even if they are good hardware, developers give them lackluster support. Even though itâs not AMDâs fault, you still paid $800+ for a card that canât run WoW properly with no solution in sight. AMD gets punished for developer laziness.
I was about to pull the trigger on a 7900XT and itâs a shame that AMD hardware is so good but theyâve been plagued by driver issues with what seems forever. I guess I will wait until nVidia launches the Super cards and overpay for decent drivers.
1 Like
Itâs not an AMD driver issue. Itâs a Blizzard issue. See, this is the problem. Developers decide to not properly test things and AMD gets punished and blamed for it. This issue does not happen in literally any other game.
I have had 1 crash in the last week of using AMDâs beta drivers. This is of course anecdotal, and Iâm still strongly assuming nothing has been fixed, but Iâm just reporting what Iâm experiencing.
The only way that may fix it is to change the graphic setting in WoW. I reset my graphic to default and I think the default is a 7 in overall graphic setting if Iâm correct.
Manifested Timeway is perma crash. Also have had crashes in Everbloom.
Last season I had issues on most dungeons, Halls of Infusion first boss was the biggest culprit