You can link by selecting the link in the box here and pressing the </> button or pressing Ctrl+e. You can also put a ` before and after the link
1 Like
Sucks to see youāre still having this issue as well 
I sorta gave up and have just been dealing with the random driver crashes but they have been way less frequent. I do hope it gets resolved thoughā¦
1 Like
Iāve been playing wow since Cata on this account and since late Vanilla on an account I used to share with my brother. In the early days we had ATI hardware. But since mid MoP until November of 23, I was on Nvidia GPUs. I wonāt lie, there was the occasional hiccup here and there in this game with those cards. But hands down, by a very significant margin, I had more issues in 5 months of AMD than my entire span of Nvidia powered gaming.
3 Likes
Done updated my post, Blizzard and AMD needs to work together, and stop ignoring bug reports.
Also users need to stop defending AMD, its oke to post that you have no issues but perhaps think about it first, any user posting they have no issues will be used by AMD as confirmation bias, while ignoring bug reports.
Just wanna mention upgrading directly from 24.2.1 to 24.3.1 corrupted my driver when my drivers corrupt it messes with hwinfo that is very hard to miss, so doing DDU from safe mode when upgrading drivers is probably best each driver release, its an annoying process but it has to be done to avoid some issues related to driver corruption, if AMD wants to pretend their no issues i will just start turning these issues into memes and nag about it until their nothing left of Radeon, everyone will be able to relate cos their issues that been reported months ago by multiple users.
That using direct 11 suggestion did diddly. This game is still crashing giving the same memory cant be read errors and itās all over the internet and not a single thing has been done to fix it. Its so frustrating. I donāt believe there are any fixes players can do to permanently fix this. My cpu ryzen 7700x has integrated graphics but I use my 4060 gpu and its the same result. Iāve tried all suggestions I can find on the internet. My comp is completely rebuilt and the same problem persists. Blizzard support offered no help either. Iāve played since vanilla and Iām thinking it may be time to move on.
I havenāt done a Safe Mode driver update since, like, 2004. You can simply use DDU to rip out your old driver if the update process is causing issues. Reboot, and manually install the new one clean.
Memory Canāt Read seems to be a newer error, and not exclusively tied to either GPU brand. Interesting to see it hit integrated AMD and external Nvidia, though.
If you arenāt using DDU from safe mode files will remain which lead to driver corruption, cos files that remain and remain in use cannot be replaced, trust me on this you want to use DDU least from safe mode, the AMD driver these days uninstalls before installing drivers, but does not clean up the files correctly, cos they think they can skip the safe mode part, its dumb and naive from AMD honestly they think this wont cause issues.
Its kind of Microsoft fault as well cos they not handling these situations well.
This just got even stranger for me. After further testing the problem seems to be isolated to retail. I was able to run all other clients of wow with absolutely 0 crashes. I uninstalled and reinstalled retail AGAIN just to be sure and within minutes it crashed again with same error. This is clearly a them thing and they are 100% ignoring it. Radio silence speaks volumes. There is no way they are unaware of this.
I mean Safe Mode is safer, but Iāve never needed it. As documented here, Iāve used a 6700 XT and a 7900 XT without issues. I donāt know where my setup diverges from others on stability, aside from most suffer on a 7900 XTX, specifically, among other 6k and 7k cards.
Iāll need to glimpse the EU forums again and see if theyāve managed to narrow the issues to anything specific
It has to be safe mode or you get driver corruption, this something AMD has to change in the way their drivers are installed as well cos it uninstalls leaves remnants then when installing new drivers it attempts to overwrite files in use which then leads to driver corruption and trust me it does happen, since 2024 installer its better to just DDU from safe mode and then install new drivers, export user settings before upgrade so you can import them after installing new drivers to save some time.
You can post on the EU forums if you make starter account on EU and level a character high enough in trail, atleast on tech support forums.
Honestly surprised they did not merge least the English forums.
I donāt need to post on the EU forums; I just browse to compare current documentation and status.
So far, theyāre still mostly bound by the same problem of driver timeouts. Most reports are still on 7900 XTX, but they have more from other models, including 1-2 people with 7900 XTs like myself.
As for driver installation: Iāve done bothāupdates through Adrenalin, and manual reinstalls. I use DDU and always have, but I havenāt messed with safe mode since, like, the Windows 7 Release Candidate. Were I to do a suite of benchmarking I might, but at this point everything is stable and running well, so Iām not going to alter the processes that keep it that way.
Iāve used multiple AMD drivers, as outlined in my previous posts, but Iām using the 24.2.1 now on my 7900 XT and itās stable. Prior to this, my 6700 XT was stable on the pre-release AFMF preview driver, but crashed like crazy on the mainline driver that was out at the same time. Aside from that specific case, no problems. I still get the long initial startup when installing the driver, though, but never any issues afterwards. Only feature activated in Adrenlin is Radeon Anti-Lag.
The same is happening with INTEL processors! specifially 13/14thn genā¦ Please helps us too!
Iām getting the same error on a 4080 RTX w/ 13th gen core processor. Itās so frustrating!
The 13th and 14th generation Intel CPUs are the issue.
1 Like
Yep, this is a problem that even Intel is finally acknowledging. Also, it can be partially blamed on motherboard manufacturers for forcing their āoptimized defaultsā that run the CPUās power limits outside of the built in Intel stock limits on the CPU. So long as there are idiots that buy motherboards based off 10 minute benchmarks where one graph looks bigger/smaller than others, even if they are all within 1-3% of each other, they will keep doing this optimized defaults crap and people will keep having random issues with crashing.
EDIT: I didnāt see the link and basically ended up talking about the same thing as whatās in the link. My badā¦
1 Like
This issue is with thermal paste as well on day 1 you get benchmark results on day 14 you get upgrade on hotspot temps by +17c
Which is why rdna3 users commonly post about having pumpout issues.
meanwhile solutions that last entire card lifetime or least 2 years before having to repaste gets ignored cos they are 1-2c higher then day 1 temps with pumpout thermal paste.
Something Intel and AMD should both do is force vendors to run their optimized defaults, not vendor specific optimized defaults.
JayzTwoCents been talking about this to recently.
2 Likes
I used the Intel Extreme Tuning utlity Tool:
Performance Core Ratio 51x , Efficient Core Ratio 40x, and Core Voltage offset to 0.000V
This has finally worked for me
AMD and Blizzard trying to normalize crashes as if they are the daily normal.
Sadly, it wonāt happen and your average enthusiast would just brainlessly follow some youtube guide to change it back to the motherboardās preset. Even if you try to explain to them that a 2% difference in performance is never going to actually manifest into anything useful for them, theyāll never listen and claim they can āfeel the difference.ā This is also how and why we have monitors in the hundreds of hertz range now lolā¦
1 Like
I canāt find any answers about this anywhere. Is the general idea cpu/motherboard? I ask because I completely rebuilt my computer and still crashing.