F5F Stay Refreshed Software Operating Systems Question Strange stuttering in games?

Question Strange stuttering in games?

Question Strange stuttering in games?

X
xXRAXERXx
Posting Freak
817
12-28-2021, 09:54 AM
#1
I'm experiencing some issues with recent games, particularly Dying Light 2 and Detroit Become Human. There are sudden spikes in frame time (frametime). In Detroit, these spikes happen at certain moments, while in Dying Light 2 they occur during movement, especially in the built-in benchmark. From what I can see, there don't appear to be any unusual anomalies. When the frame time increases, both GPU and GPU memory clocking decrease, whereas CPU performance rises. All temperatures and voltages remain normal. The system passed stability tests with Furmark, 3D Mark, and Memtest86. No issues were found. Benchmark results are also within expected ranges: AS SSD, 3D Mark (Time Spy Extreme, Storage Benchmark), Cinebench R23. LatencyMon didn't detect anything unusual. All test runs were done with minimal background applications.

I began noticing the issue around the time I swapped the drives—from an Adata Gammix S11 Pro to a Lexar NM790 and using a Thermalright contact frame. After that, I installed a fresh Windows 11 Pro (stable version) and switched from the beta channel to a stable one. Before this change, I was using Windows 11 Pro on the beta channel.

In Detroit Become Human, the problems appear after reloading the scene, but they resolve once the game restarts. The recurring nature of the issue and the absence of problems during the second load suggested a possible shader cache problem (??).

Please help. I'm running out of ideas.
X
xXRAXERXx
12-28-2021, 09:54 AM #1

I'm experiencing some issues with recent games, particularly Dying Light 2 and Detroit Become Human. There are sudden spikes in frame time (frametime). In Detroit, these spikes happen at certain moments, while in Dying Light 2 they occur during movement, especially in the built-in benchmark. From what I can see, there don't appear to be any unusual anomalies. When the frame time increases, both GPU and GPU memory clocking decrease, whereas CPU performance rises. All temperatures and voltages remain normal. The system passed stability tests with Furmark, 3D Mark, and Memtest86. No issues were found. Benchmark results are also within expected ranges: AS SSD, 3D Mark (Time Spy Extreme, Storage Benchmark), Cinebench R23. LatencyMon didn't detect anything unusual. All test runs were done with minimal background applications.

I began noticing the issue around the time I swapped the drives—from an Adata Gammix S11 Pro to a Lexar NM790 and using a Thermalright contact frame. After that, I installed a fresh Windows 11 Pro (stable version) and switched from the beta channel to a stable one. Before this change, I was using Windows 11 Pro on the beta channel.

In Detroit Become Human, the problems appear after reloading the scene, but they resolve once the game restarts. The recurring nature of the issue and the absence of problems during the second load suggested a possible shader cache problem (??).

Please help. I'm running out of ideas.

Y
yoy7539
Junior Member
16
12-30-2021, 12:05 AM
#2
Hey there,
Have you reset the CMOS each time you performed a bios update? If not, it could be a good idea to try now. Is this unusual action linked to the Windows 11 installation? Since they're beta/channel releases, it's probably a bug. You might need to install the latest consumer version for certainty.
Did the previous storage device remain connected during the new installation on the updated drive?
Y
yoy7539
12-30-2021, 12:05 AM #2

Hey there,
Have you reset the CMOS each time you performed a bios update? If not, it could be a good idea to try now. Is this unusual action linked to the Windows 11 installation? Since they're beta/channel releases, it's probably a bug. You might need to install the latest consumer version for certainty.
Did the previous storage device remain connected during the new installation on the updated drive?

S
SrMelohh
Junior Member
25
12-30-2021, 12:51 AM
#3
Hi, thank you for your reply.
The automatic wipe during UEFI updates or downgrades is functioning correctly. I've reset it manually but haven't seen any improvements.
Yes, this configuration on the Gammix S11 Pro drive worked smoothly for two years with Windows 11 Beta. Switching to W10 was just for testing. It's currently stable on W11. No changes observed.
The old disk isn't connected; only Lexars were used during installation.
Typically, I'd attribute the issue to the drives themselves, as the timing matches the upgrade. However, the crystal disk information doesn't show any errors. In AS SSD, the drives perform as advertised, with 3D Mark response times being normal. It's difficult to blame these drives, especially since everything functions well in Windows file operations.
S
SrMelohh
12-30-2021, 12:51 AM #3

Hi, thank you for your reply.
The automatic wipe during UEFI updates or downgrades is functioning correctly. I've reset it manually but haven't seen any improvements.
Yes, this configuration on the Gammix S11 Pro drive worked smoothly for two years with Windows 11 Beta. Switching to W10 was just for testing. It's currently stable on W11. No changes observed.
The old disk isn't connected; only Lexars were used during installation.
Typically, I'd attribute the issue to the drives themselves, as the timing matches the upgrade. However, the crystal disk information doesn't show any errors. In AS SSD, the drives perform as advertised, with 3D Mark response times being normal. It's difficult to blame these drives, especially since everything functions well in Windows file operations.

N
Nut3lla_Kakao
Junior Member
21
01-02-2022, 12:15 AM
#4
https://forums. Be aware of @drea.drechsler answer.
N
Nut3lla_Kakao
01-02-2022, 12:15 AM #4

https://forums. Be aware of @drea.drechsler answer.

J
JustAirHits
Junior Member
44
01-14-2022, 06:04 AM
#5
Hi, partially good news!
After clearing the CMOS (in the meantime the GPU drivers were updated to 23.10.2), a few changes appeared.
1. Detroit Become Human:"Helicopter sequence" lag reduced to ~~0,1s - still noticable but real less disturbing.
2. Scenes are loading at least twice as fast now.
3. CPU utilization when playing DBH dropped to around 40/50% rather than middle 80's.
At this point in this game i consider that minor problem as driver shader cache issue (game is basing on Vulkan).
Unfortunetely in Dying Light 2 no changes so far.
Everything is tested in borderless. I guess that the game would have better performance on fullscreen mode (Windows optimizations etc.), but it is broken(?) in my case. When I select fullscreen mode, the monitor goes blank and after a second it turns on at 2560x1440, but only 60Hz and I can't do anything about it. Tests in such settings will not reflect the scale. In frameless the game runs normally at 2560x1440 165Hz with freesync.
Only in this game I have a problem, the rest of the games work in fullscreen 2560x1440 165Hz freesync.
J
JustAirHits
01-14-2022, 06:04 AM #5

Hi, partially good news!
After clearing the CMOS (in the meantime the GPU drivers were updated to 23.10.2), a few changes appeared.
1. Detroit Become Human:"Helicopter sequence" lag reduced to ~~0,1s - still noticable but real less disturbing.
2. Scenes are loading at least twice as fast now.
3. CPU utilization when playing DBH dropped to around 40/50% rather than middle 80's.
At this point in this game i consider that minor problem as driver shader cache issue (game is basing on Vulkan).
Unfortunetely in Dying Light 2 no changes so far.
Everything is tested in borderless. I guess that the game would have better performance on fullscreen mode (Windows optimizations etc.), but it is broken(?) in my case. When I select fullscreen mode, the monitor goes blank and after a second it turns on at 2560x1440, but only 60Hz and I can't do anything about it. Tests in such settings will not reflect the scale. In frameless the game runs normally at 2560x1440 165Hz with freesync.
Only in this game I have a problem, the rest of the games work in fullscreen 2560x1440 165Hz freesync.

E
epiclegominer
Junior Member
8
02-04-2022, 06:03 AM
#6
Hey,
Great to hear that this is resolved in my book.
Apart from running another DDU on the GPU driver, it still persists in Dying Light, which suggests a possible bug that could be fixed with an update.
In the meantime, good luck and enjoy gaming.
Let us know if you encounter any further issues.
Another suggestion: If you're using an overlay such as Steam or MSI, try disabling it. They can sometimes cause minor stuttering. You might also adjust the mouse polling rate, which could help.
E
epiclegominer
02-04-2022, 06:03 AM #6

Hey,
Great to hear that this is resolved in my book.
Apart from running another DDU on the GPU driver, it still persists in Dying Light, which suggests a possible bug that could be fixed with an update.
In the meantime, good luck and enjoy gaming.
Let us know if you encounter any further issues.
Another suggestion: If you're using an overlay such as Steam or MSI, try disabling it. They can sometimes cause minor stuttering. You might also adjust the mouse polling rate, which could help.

F
fadgemd
Member
190
02-09-2022, 12:00 PM
#7
Hi. The issue has come back again. It’s almost identical to before, except the CPU is always at full capacity (DL2), while the graphics card varies between 60 and 98%. There’s no bottleneck because I chose the processor and card carefully two years ago. Back then, I usually let the card run at its limit and the CPU stayed around 60%.
I’ve looked into disabling virtualization and C-States, but nothing changed.
In the coming days I’ll test whether all CPU pins are aligned and return to the original ILM settings to see if that helps. If it doesn’t improve, I plan to try running games on a more standard Linux distribution, though it will be a significant step for my data and migration. I’ll keep this thread updated. Someone else with similar problems might find my experience useful.
F
fadgemd
02-09-2022, 12:00 PM #7

Hi. The issue has come back again. It’s almost identical to before, except the CPU is always at full capacity (DL2), while the graphics card varies between 60 and 98%. There’s no bottleneck because I chose the processor and card carefully two years ago. Back then, I usually let the card run at its limit and the CPU stayed around 60%.
I’ve looked into disabling virtualization and C-States, but nothing changed.
In the coming days I’ll test whether all CPU pins are aligned and return to the original ILM settings to see if that helps. If it doesn’t improve, I plan to try running games on a more standard Linux distribution, though it will be a significant step for my data and migration. I’ll keep this thread updated. Someone else with similar problems might find my experience useful.

B
blackdude10
Junior Member
11
02-09-2022, 09:56 PM
#8
The sole method to truly achieve that is by reinstalling windows from the beginning. All previous attempts suggest this should be the subsequent action.
B
blackdude10
02-09-2022, 09:56 PM #8

The sole method to truly achieve that is by reinstalling windows from the beginning. All previous attempts suggest this should be the subsequent action.

L
LucasandClaus
Senior Member
438
02-11-2022, 06:20 AM
#9
Windows is experiencing issues with updates that are negatively affecting game performance on certain hardware.
L
LucasandClaus
02-11-2022, 06:20 AM #9

Windows is experiencing issues with updates that are negatively affecting game performance on certain hardware.