AMD RX 6000 series driver issues & workarounds

It really isn't, searching for EliteDangerous64.exe takes several minutes for me - and that's when I just search the SSD it's on...

I don't think I've ever had it take minutes to find a file by name on an SSD.

On my usual system it took less than two seconds to find EliteDangerous64.exe (after a restart, with indexing disabled) and about two minutes to search through the names of all the files on two SDDs and four HDDs.
 
I don't think I've ever had it take minutes to find a file by name on an SSD.

On my usual system it took less than two seconds to find EliteDangerous64.exe (after a restart, with indexing disabled) and about two minutes to search through the names of all the files on two SDDs and four HDDs.
I also think that the Windows File Explorer is slow in finding files. I just clocked 123 seconds in Windows 11, without a restart after a game session of ED, and with indexing enabled, on a Kingston KC2000 1 TB NVMe SSD, which is about 54% full. The mobo is an X570 Aorus Master and processor is a Ryzen 9 5900X. It found the file in my secondary account's install, which is under the AppData folder. My primary account is on Steam.
 
28 seconds to find it for me. Which isn't too bad considering that's sifting through 14TB of storage.
The search concluded about another 30 seconds after finding it, once it had finished going through all my drives.
 
Last edited:
I also think that the Windows File Explorer is slow in finding files.

Relative to other solutions, I'm sure it is.

It's also more than fast enough to find files, by name, on all of my Windows systems.

Having it not find something that was accurately named, or taking several minutes to do so on an SSD, is an indication of a problem beyond Windows File Explorer.
 
Finally I decided to update my drivers from 22.5.1 to 22.11.1 and used workaround #2 to circumvent the shader issue and additionally deleted the GPUWorktable.
All in all it worked like a charm, no issues so far.

So thanks for all your efforts @Morbad much appreciated ! (y) (y)



On a sidenote: it seems that during the driver install restart my XBox controller got "lost" somehow and I was somewhat baffled that my usual controls in Elite didn't work anymore and I couldn't figure out why at first. In Windows the controller was displayed as present and working but Elite couldn't find it anymore as referring to the log files.
A complete shutdown and restart of the PC finally did the trick and I had just to reassign my bindings file again.
 
Finally I decided to update my drivers from 22.5.1 to 22.11.1 and used workaround #2 to circumvent the shader issue and additionally deleted the GPUWorktable.
All in all it worked like a charm, no issues so far.

So thanks for all your efforts @Morbad much appreciated ! (y) (y)



On a sidenote: it seems that during the driver install restart my XBox controller got "lost" somehow and I was somewhat baffled that my usual controls in Elite didn't work anymore and I couldn't figure out why at first. In Windows the controller was displayed as present and working but Elite couldn't find it anymore as referring to the log files.
A complete shutdown and restart of the PC finally did the trick and I had just to reassign my bindings file again.
Awesome.
Just be aware, that the drivers beyond 22.5.1 also breaks some other games, Space Engine, DayZ, and others, but if ED is your main obsession then all is good. o7
 
Ugh, lots of reading. Seems like Windows just force updated my drivers this a.m. (judging from all the screen flickering, connect/disconnect sounds, and shuffling of my secondary display order and icons for a while) without my previous consent, and without even showing they were updated. AMD Radeon Adrenaline task bar icon will no longer launch the interface either. Sigh.

Been waiting on the pre-break drivers for reports this was finally fixed, and this happens the WEEK OF the big update, and when I have time off to play. First world problems... LOL.
 
Thanks. Just did the 2022.11.1 update (as full factory reset with restarts) and nearly had a heart attack. Screen background colors and taskbar were right, but opening any 'Window' (explorer) including right-click menu popups, the colors were like 8-bit negative/corrupt as bleep and hardly readable - looked like dead graphics card hash mess. (Browser window fine though. Just anything rendering solely using the Windows API I guess...)

Full shutdown, unplug and turn OFF power to monitor, unplug monitor, drain with power button pressed, reconnect all and restart seems to have fixed it though. Some sort of weird EDID table misread I guess, since I have a pretty 'messy' setup. Main screen is Alienware 3821 and two small 800x480's connected to a secondary nVIDIA GT710 passive card internal to case. (This was a crazy theme build, 2001 Space Odyssey / HAL-9000 insipired, so several weird choices to get end look I was after. Gratuitous imgur link: HAL-9000 Gallery ...)

Off to apply workaround 2 before I try Odyssey today....

EDIT - well, no crash, but haven't tried landing yet, was doing some mining. I am getting a big cyan 'bullseye' on planets as I get in their vicinity (was just dropping off a mining hold full at an outpost in orbit).

We'll try landing tomorrow....
 
Last edited:
I really hope AMD and FDEV can work this out with the shader glitches issue with their latest driver and with the upcoming patch 14, even if their latest recommended 22.5.1 WHQL still works quite well!. but i've notice some stuttering and flickering with Hyper jump and Super cruise also!
 
Last edited:

Robert Maynard

Volunteer Moderator
U14 does indeed fix the shader issue responsible for that teal overlay. Assuming there are no regressions in the future, these workarounds should no longer be required.
It might be my imagination, but the shimmering of the holo-ship inside the shield rings on the HUD seems to have reduced for me. I've tried the AspX, Cutter, CMIV & Imperial Courier so far and they all seem to exhibit reduced shimmering.
 
Didn't even make it out of the station because the game booted me out with some mauve adder error while having a look at the galaxy map...
But at least no crashes during startup, looked pretty normal so far. May have a further look later or tomorrow
 
It might be my imagination, but the shimmering of the holo-ship inside the shield rings on the HUD seems to have reduced for me. I've tried the AspX, Cutter, CMIV & Imperial Courier so far and they all seem to exhibit reduced shimmering.

Have noticed some minor visual changes with U14. Still testing for any performance impact.

Edit: There is also a minor change to the GraphicsConfiguration.xml between 4.0.0.1450 and 4.0.0.Update14. Specifically, the "InscatterSteps" variable under volumetrics has been removed. This could account for some of the visual differences.
 
Last edited:
I'm still expirencing the crashes even after U14 so while they have fixed the teal thing, approaching a planet still crashes 6600 cards

-edit-

the vulcan work around isn't even working for me anymore
 
Last edited:
Back
Top Bottom