Will this issue ever be resolved or are we just going to have to use dx 11 next expansion as well? The silence on this matter is worrisome for those of us who own higher end AMD card and are forced to use DX 11 in order to play the game. As we all know DX 11 comes with some serious downsides in performance compared to DX 12, making cards such as the 7900xt (which i have) and the 7900 xtx feel like a waste of money when one of our primary games we enjoy are WoW. Please give us updates on this matter, its been over a month now, more specifically its been since 10.1.5 since this issue started for me, so many many months now.
PS. This is NOT the same issue as the direct x 12 causing the game client to hang for a period of time. This issue is specifically a GPU driver crash randomly during gameplay while using DX 12, the only solution is DX 11 where there are zero crashes. The game itself does not ever crash ONLY the AMD graphics driver.
I have/had the same issue as you. What I do is just let the screen sit black until it finally loads. It will load, it just takes a few minutes. After that it won’t do it again until you have to update your drivers. There is no need for -d3d11as long as you just let it sit for a bit.
This isnt the same issue at all that your having, this is a driver crash not a client hang, two seperate things entirely but both related to dx 12. This is a known issue as well and a blue has posted about it a month ago.
I wish we could get a high profile journalist involved. There is a case here that needs to be reported on. hundreds of thousands of AMD customers are being scammed by the 7+ series cards. They literally do not function on DX 12.
Anyone in contact with a journalest? Would love a story going out to the public about the shadyness happening here. Between both Blizzard and AMD
Oof sad to see this issue still isn’t resolved. I quit all the way back in May or so (beginning of season 2) after I upgraded to a 7900xt because of this annoying driver timeout/crash. I’ve been wanting to come back for a while now but I guess I’ll keep waiting since it sounds like it’s only gotten worse. There weren’t as many posts back then but I did notice an uptick with the Season 2.5 patch. And now there seems to be another issue with shader compiling on launch lol. I was worried I had a defective card but I’ve been happily playing a slew of other random games without any real problems. Might be quicker to reach out to AMD specifically, donno how though seems like sending in 100s of those crash reports hasn’t done anything useful
No pen or touch input is available for this display
Does this apply to me? Idk much ab computers but I think I know I have an AMD something. Is this why my WoW will not launch? I click play on the launcher and then it just doesnt start at all. I’ve been having this issue for over a few hours now.
I wonder if there is some link between the longer startup times for dx12 on AMD cards and the random crashes on those cards. The crashes happening on both dx11 and dx12 make it seem like there’s no link but just the fact that so many AMD card owners are having a myriad of issues leads me to believe someone is really dropping the ball on the AMD support side of things. Not sure if its Blizzard or AMD or both.
No, it’s likely not some X-Files conspiracy… AMD GPUs only make up roughly ~15% of all GPUs and have been known for having terrible driver support(Adrenalin is great though), as well being terribly slow at reacting to sudden changes in Windows.
Windows has been rolling out 23H2 updates to people during this same timeframe as well. You can still be on 22H2 and have all of the components of 23H2, since they are rolling out the update differently than in the past. The “23H2” part is mostly only in name. Recently, there have been a ton of known and documented issues with some of the updates as well. Both AMD and Nvidia have been going through hell with it all and it’s definitely not exclusive to WoW.
Go spend some time on the Nvidia/AMD forums and subreddits, you’ll see what I mean.
I just built a pc with a ryzen 7600 and 7800xt. Running the newest drivers.
Both classic and retail hang upon first launch if launched in dx12.
Classic will hit a black screen followed by an amd report prompt due to driver time out. If I’m on discord, discord will close and exit out too. This will happen usually in the first 1-15 minutes.
I thought this was an issue confined to classic but I experienced the same driver time out in retail but it doesn’t happen for at least 30 minutes and once I played almost 2 hours before the driver timed out.
I’ve now forced classic to launch in dx11 and I played about 1.5 hours and no issues so far.
Such a frustrating issue but it appears on wow is affected right now.
Friend, Do yourself a favor and return the radeon gpu while you still can. These driver issues have been around for a very long time, and theres no indication that they will be fixed any time soon. Hardware acceleration is broken as well with chrome browsers. any many other bugs. Unfortunately for me the time has passed and I cant return mine
A couple of months ago I purchased a Radeon 7600 after my quite old Radeon started having issues; nothing like the current ones, it was physically deteriorating (moving in the holder thing…sorry not very technical) and the only way I could keep being able to see anying on the monitor was to lie the PC on its side.
Anyhow, got the new card and within a very short time I started getting The Problem: game freeze-black screen-spinning wheel-return to game, and same thing with Discord. After trying to find answers that were not forthcoming, I returned the card to the seller and my PC is currently lying on its side with my old original Radeon which is giving me zero problems at this time. Other than the computer looking rather odd lying down.
I had planned to completely switch cards to a Nvidia but Im told there are also some problems happening with some current cards so I’m not quite sure what to do. I dont have a lot of money and my budget doesn’t allow for very expensive ones. I’m sort of waiting until some sort of resolution is found with this Radeon problem.