Question Directx 11 games running poorly (low GPU usage) ?

Oct 16, 2021
2
0
10
0
Hi all,

First time posting here.
Just a quick summary - had an issue with an old SSD dying on me. This forced me to reinstall windows 10 to another less dead SSD. However, after reinstalling and making sure everything was fully updated I've found that games that rely solely on Directx 11 absolutely suck for performance (previously where I was getting great results before the reinstall).

After a full day of troubleshooting and installing new and old drivers to test everything - I've found that every game that runs in DX12, Vulkan, OpenGL etc run brilliantly (especially the new Back4Blood when ran in DX12 and some more intensive games) but anything that runs in DX11 hits a major dive in performance (the Forest, Dark Alliance, Destiny 2, Back4Blood - when set to DX11 mode etc). I've also found that DX11 games use 2-12% of the GPU while the DX12 uses anywhere from 60-100% (even if they are the same game like Back4Blood)

When searching through the archives of the internet I'm not finding many answers (mostly just people who have performance drops moving from DX11 to DX12 when mine is the opposite).

Any insight you have would be greatly appreciated - I've went through and updated my system with all the latest drivers (even testing older drivers to be safe) and even did a clean installation of windows 10 twice to be safe. So if you know how to fix this I'd be eternally grateful!
My specs are:

Motherboard: Gigabyte B450M DS3H (with latest BIOS)
RAM: 16 GB (3200mhz)
CPU: AMD Ryzen 5 3600 6-Core
GPU: Radeon RX 580 Series
OS: Windows 10 Pro (64-bit)

I'm wondering whether or not my GPU is beginning to throw in the towel (It's been the daily workhorse since new and would have been replaced if the graphics market wasn't so skewed right now) but that wouldn't make sense for DX12 to still be working perfectly despite DX11 running poorly?
 
Oct 24, 2021
1
0
10
0
Hello!

This is kind of crazy, I'm having the same issue but I'm on a whole different setup than you and I noticed the exact same thing with Back 4 Blood in DX11 vs DX12. I'm currently talking with Nvidia support so I'm waiting on a response from them but here's my setup:

Gigabyte Z390 Aorus Elite
i7-9700kf
Gigabyte RTX 3070ti OC
32 GB RAM at 2400 MHZ
Two Samsung SSD 970 Evos

I also experienced the issue both in Windows 11 and Windows 10. I attempted doing the DX11 redist on both OS installs, multiple drivers on both installs, and no luck whatsoever. That's so bizarre, I don't think it's our GPU's but there's gotta be something else going on here.
 
Oct 16, 2021
2
0
10
0
Hello!

This is kind of crazy, I'm having the same issue but I'm on a whole different setup than you and I noticed the exact same thing with Back 4 Blood in DX11 vs DX12. I'm currently talking with Nvidia support so I'm waiting on a response from them but here's my setup:

Gigabyte Z390 Aorus Elite
i7-9700kf
Gigabyte RTX 3070ti OC
32 GB RAM at 2400 MHZ
Two Samsung SSD 970 Evos

I also experienced the issue both in Windows 11 and Windows 10. I attempted doing the DX11 redist on both OS installs, multiple drivers on both installs, and no luck whatsoever. That's so bizarre, I don't think it's our GPU's but there's gotta be something else going on here.
Hi there!

Good to know I wasn't alone in this issue.

I managed to fix my issue and I've tested it on both the old and the new GPU (as i ended up upgrading just in case that was the issue, turns out it wasn't but I got a 3060ti at a good price either way) and it's been working fine since. It ended up being the latest update of windows 10 that caused my problem. I read similar problems that people experienced with versions 20h2 then moving to 21h1 of windows.

My fix was formatting and installing 21h1 from May 2021 and not updating it at all! As it seemed when I opened a directx 11 game it installed direct x separately and then began working brilliantly which I don't believe occurred previously when I installed Windows and updated (to the newest) immediately before installing any games.
At the moment I have not updated my windows to the latest update and everything is running perfect for me - I will have to try updating soon (as I have paused updates for the meantime) but will do that when I have time to troubleshoot in the event it happens again.

Hope this helps you a little bit to understanding your own issue as well!
Wishing you the luck of the silicon gods!
 
Nov 27, 2021
1
0
10
0
Hi all,

Just wanted to follow up on this issue. I suffered the exact same thing, and after hours of troubleshooting, found my root cause.
System specs:
Intel i9 10850K
2 x 16GB Crucial Ballistix 3600 MHz DDR4
Gigabyte Z490 Aorus Ultra Mobo
Samsung 970 Evo Plus M.2 2 TB SSD
Gigabyte Geforce RTX 2060 Gaming OC Pro 6GB
Note: No overclocking on anything

Here's what I learned. First, it has nothing to do with Nvidia. I suffered this problem even when I pulled the RTX 2060 card out of my system and was using the on chip Intel graphics (630). This led me to believe it had to be a Windows software issue unrelated to the Nvidia hardware or software.

The next thing I did was reinstall the 2060 and do a clean boot (see here for specifics: https://support.microsoft.com/en-us/topic/how-to-perform-a-clean-boot-in-windows-da2f9573-6eec-00ad-2f8a-a97a1807f3dd#bkmk_reset). This made the problem go away! So now I knew it had to do with some service or program that was running. So the next step was a process of elimination.

Turns out, it was the "AppProtection Service" that is a part of the Citrix Workspace app that was breaking things. I use the Workspace as part of a stock trading app, that I have been using for about a year and haven't updated. My working theory is that the Windows feature update changed the way that service interacts with Windows and that service combined with STEAM, breaks things. It may or may not also be Steam related, but I noticed that I was only having trouble with DX11 games via Steam. All my Origin games (which wasn't many, but still...) ran fine in DX11.

So, I simply stopped that service from starting when Windows starts, and viola! The other interesting thing to note is that if the service starts at all, even stopping it doesn't solve the problem. It MUST be set to not start at all when Windows starts.

Anyway, hope this can help others who run in to this issue.
 
Dec 2, 2021
1
0
10
0
Hi all,

Just wanted to follow up on this issue. I suffered the exact same thing, and after hours of troubleshooting, found my root cause.
System specs:
Intel i9 10850K
2 x 16GB Crucial Ballistix 3600 MHz DDR4
Gigabyte Z490 Aorus Ultra Mobo
Samsung 970 Evo Plus M.2 2 TB SSD
Gigabyte Geforce RTX 2060 Gaming OC Pro 6GB
Note: No overclocking on anything

Here's what I learned. First, it has nothing to do with Nvidia. I suffered this problem even when I pulled the RTX 2060 card out of my system and was using the on chip Intel graphics (630). This led me to believe it had to be a Windows software issue unrelated to the Nvidia hardware or software.

The next thing I did was reinstall the 2060 and do a clean boot (see here for specifics: https://support.microsoft.com/en-us/topic/how-to-perform-a-clean-boot-in-windows-da2f9573-6eec-00ad-2f8a-a97a1807f3dd#bkmk_reset). This made the problem go away! So now I knew it had to do with some service or program that was running. So the next step was a process of elimination.

Turns out, it was the "AppProtection Service" that is a part of the Citrix Workspace app that was breaking things. I use the Workspace as part of a stock trading app, that I have been using for about a year and haven't updated. My working theory is that the Windows feature update changed the way that service interacts with Windows and that service combined with STEAM, breaks things. It may or may not also be Steam related, but I noticed that I was only having trouble with DX11 games via Steam. All my Origin games (which wasn't many, but still...) ran fine in DX11.

So, I simply stopped that service from starting when Windows starts, and viola! The other interesting thing to note is that if the service starts at all, even stopping it doesn't solve the problem. It MUST be set to not start at all when Windows starts.

Anyway, hope this can help others who run in to this issue.

Thanks CornellFiggs! Removing citrix workspace from the mix worked for me. Microsoft must've really done something weird because this is the 2nd time having the same issue. Last time the fix was installing all the c++ runetime installes from 2005-2022.
 

ASK THE COMMUNITY

TRENDING THREADS