PC Drivers & Software

[Fantasma_N3D]

I reported this problem already several times in the report tool of the AMD drivers with no avail, so I will try here to see also if more people can verify this.

My system: R9 5900X/RX 6800/MSI B550 Gaming Edge/48GB ram 3800Mhz

Well, the problem is that since the release of the May Preview driver (and still working like that with the 22.7.1), the main game threads of DX11 games go to the slow CCD or chiplet of my Ryzen, especially, those with low thread count. For example, I tested that in Assetto Corsa (720p minimum details to force cpu bottleneck and observe this better), my fast CCD is the 1, the slow one is CCD 2:

https://i.imgur.com/Sh7JioY.jpg

as you can see, all the loads are in the wrong CCD (before those drivers, the load was completely on the CCD 1, which allows 200-300Mhz more frequency). This gives 665fps:

https://i.imgur.com/EJ5R7XH.jpg

I repeated the test after disabling CCD 2 in bios, obtaining 738fps:

https://i.imgur.com/DiANVsA.jpg

which is what I should get without doing anything if the core affinity worked as intended. Of course, CPPC is enabled in bios. I hope that this gets some visibility and gets fixed somehow.

[Riviancotton]

This is terrible. I wish I knew about this before buying my 7900xt, Elden Ring runs horrible on my pc and before I used to have a 3070 with no issues, same cpu 5800x on a b550 board. 

Another game this may happens is in plague tale. 

Not sure why this is not more discussed, this should be something to be consiree before purchasing a Gpu. 

[Thomasdk1405]

Hi

might be worth a try ! But yes last year AMD launched driver with new optimized dx 11 dll files. In many games this works better than native but other games worse. Most likely they will not fix this - who knows but you can revert to old native drivers yourself. You need to open regedit (registry) go to top and search for "D3DVendorName" until you are in some key that say 0000 (you can also google this) but you need to change both D3DVendorName (64 bit) and D3DVendorNameWoW. What I have here is new amd dx 9, but old native dx 11 - basicly you can choose what you want for both but first 2 is dx 9 and last 2 is dx 11:

amdxn64.dll amdxn64.dll atidxx64.dll atidxx64.dll 

(amd = new and ati = old)

D3DVendorName

default

C:\Windows\System32\DriverStore\FileRepository\u0391252.inf_amd64_b298c070ddf486e2\B391109\amdxn64.dll
C:\Windows\System32\DriverStore\FileRepository\u0391252.inf_amd64_b298c070ddf486e2\B391109\amdxn64.dll
C:\Windows\System32\DriverStore\FileRepository\u0391252.inf_amd64_b298c070ddf486e2\B391109\amdxx64.dll
C:\Windows\System32\DriverStore\FileRepository\u0391252.inf_amd64_b298c070ddf486e2\B391109\amdxx64.dll

native dx 11

C:\Windows\System32\DriverStore\FileRepository\u0391252.inf_amd64_b298c070ddf486e2\B391109\amdxn64.dll
C:\Windows\System32\DriverStore\FileRepository\u0391252.inf_amd64_b298c070ddf486e2\B391109\amdxn64.dll
C:\Windows\System32\DriverStore\FileRepository\u0391252.inf_amd64_b298c070ddf486e2\B391109\atidxx64.dll
C:\Windows\System32\DriverStore\FileRepository\u0391252.inf_amd64_b298c070ddf486e2\B391109\atidxx64.dll

d3dvendornamewow

default
C:\Windows\System32\DriverStore\FileRepository\u0391252.inf_amd64_b298c070ddf486e2\B391109\amdxn32.dll
C:\Windows\System32\DriverStore\FileRepository\u0391252.inf_amd64_b298c070ddf486e2\B391109\amdxn32.dll
C:\Windows\System32\DriverStore\FileRepository\u0391252.inf_amd64_b298c070ddf486e2\B391109\amdxx32.dll
C:\Windows\System32\DriverStore\FileRepository\u0391252.inf_amd64_b298c070ddf486e2\B391109\amdxx32.dll

Native dx 11

C:\Windows\System32\DriverStore\FileRepository\u0391252.inf_amd64_b298c070ddf486e2\B391109\amdxn32.dll
C:\Windows\System32\DriverStore\FileRepository\u0391252.inf_amd64_b298c070ddf486e2\B391109\amdxn32.dll
C:\Windows\System32\DriverStore\FileRepository\u0391252.inf_amd64_b298c070ddf486e2\B391109\atidxx32.dll
C:\Windows\System32\DriverStore\FileRepository\u0391252.inf_amd64_b298c070ddf486e2\B391109\atidxx32.dll

so pick native for both (if you get warning just say ok) and boot computer. Then at least you will be on old dx 11 again. Want to go back same just pick default values (amd dll for all 4) and boot again.

Hope it helps !

[Fantasma_N3D]

Thanks for the hint.

When I first noticed the scheduling bug, I was changing between drivers (May Preview in 2022 and the last of April of 2022) to see the effect between the new driver (now the so-called DXNAVI) and the old one.

My conclusion was that "DXNAVI+Scheduling bug" had still better performance than "old DX11 driver (Ati) + Right Scheduling" and that the problem came from DXNAVI itself.

That is the reason I wait for a fix or use the scheduling workaround from here:

https://www.reddit.com/r/AMDHelp/comments/wcj6ol/comment/jfvijht/?utm_source=share&utm_medium=web2x&...

but thanks anyway

[Fantasma_N3D]

As expected, driver 23.5.2 did not fix the issue.

[Fantasma_N3D]

23.7.1 tested. The bug is still not fixed.

More than 400 days with the bug and reporting almost from day 1 (May Preview drivers of 2022)

[Fantasma_N3D]

23.7.2 tested. The bug is still there.

[Riviancotton]

23.8.1 The bug is still here, clean installed VGA drivers and chipset driver.

Not sure if there are plans to fix this.

[Fantasma_N3D]

For the moment, I can only say that AMD acknowledged the issue.

[Fantasma_N3D]

Good news!! AMD has started to solve this issue!! With the driver 23.9.1, the affinity for DX11 and DX12 titles/benchs (except for 3DMark Firestrike) have been fixed!!! Affected DX9 titles not yet. We are closer to a full driver fix!!

[Fantasma_N3D]

With the driver 23.9.2, DX9 titles were also fixed! Except for Firestrike, the bug seems solved

[Riviancotton]

Can confirm, I've tried fallout new vegas and Gears 5 wich had issues before, glad they got this issue taken care of.