F5F Stay Refreshed Software Operating Systems Issue involving stuttering caused by a fixed thread in ntoskrnle.exe

Issue involving stuttering caused by a fixed thread in ntoskrnle.exe

Issue involving stuttering caused by a fixed thread in ntoskrnle.exe

S
Silberflug
Member
203
03-18-2016, 09:09 AM
#1
I’m experiencing some unusual performance problems with Windows after installing Phantasy Star Online 2. The game occasionally starts with micro-stuttering, even after closing it. This issue persists for about 30 minutes and then resolves on its own. After a fresh Windows 10 setup, the problem remains. I suspect the core of the issue lies in the System process, specifically dxgmms2.sys, which is frequently at the top. Sometimes other processes briefly advance, but only for a single refresh and never exceed 0.02 CPU usage. Eventually, while playing PSO2 or using NZXT CAM, ntoskrnl.exe stays stuck at the top with high CPU consumption (0.3 to 0.8). I’ve tried uninstalling and reinstalling the graphics drivers, but the problem persists. Removing the problematic threads helps temporarily, though reinstalling Windows doesn’t resolve it. If I reboot, the issue continues. The main concerns are ntoskrnle.exe and ntoskrnl.exe being pinned higher than dxgmms2.sys. It’s unclear if NZXT Cam is having kernel access issues or if the driver conflict is the root cause. Overall, the micro-stuttering lasts for extended periods and seems to require a long-term solution.
S
Silberflug
03-18-2016, 09:09 AM #1

I’m experiencing some unusual performance problems with Windows after installing Phantasy Star Online 2. The game occasionally starts with micro-stuttering, even after closing it. This issue persists for about 30 minutes and then resolves on its own. After a fresh Windows 10 setup, the problem remains. I suspect the core of the issue lies in the System process, specifically dxgmms2.sys, which is frequently at the top. Sometimes other processes briefly advance, but only for a single refresh and never exceed 0.02 CPU usage. Eventually, while playing PSO2 or using NZXT CAM, ntoskrnl.exe stays stuck at the top with high CPU consumption (0.3 to 0.8). I’ve tried uninstalling and reinstalling the graphics drivers, but the problem persists. Removing the problematic threads helps temporarily, though reinstalling Windows doesn’t resolve it. If I reboot, the issue continues. The main concerns are ntoskrnle.exe and ntoskrnl.exe being pinned higher than dxgmms2.sys. It’s unclear if NZXT Cam is having kernel access issues or if the driver conflict is the root cause. Overall, the micro-stuttering lasts for extended periods and seems to require a long-term solution.

C
Cyanstrophic
Senior Member
668
03-19-2016, 03:46 PM
#2
I recorded a performance log and captured an image of the spikes. The only two modules active during the spikes are ntokrnl.exe and nvlddmkm.sys. This is the closest I can get with my current understanding, and I’m unsure how to interpret anything else. I also zoomed in slightly to clarify the details.
C
Cyanstrophic
03-19-2016, 03:46 PM #2

I recorded a performance log and captured an image of the spikes. The only two modules active during the spikes are ntokrnl.exe and nvlddmkm.sys. This is the closest I can get with my current understanding, and I’m unsure how to interpret anything else. I also zoomed in slightly to clarify the details.

I
Ivonator12345
Junior Member
6
03-21-2016, 04:24 PM
#3
Posted for troubleshooting. Please remove or lock it as it appears to be in the wrong section.
I
Ivonator12345
03-21-2016, 04:24 PM #3

Posted for troubleshooting. Please remove or lock it as it appears to be in the wrong section.

S
SayNoToNWO
Posting Freak
879
03-23-2016, 01:17 AM
#4
Problem (Summary): Multiple threads getting stuck in the system, especially when certain drivers were active. Solution (Summary): Updating to the latest Beta driver resolved the issue.
S
SayNoToNWO
03-23-2016, 01:17 AM #4

Problem (Summary): Multiple threads getting stuck in the system, especially when certain drivers were active. Solution (Summary): Updating to the latest Beta driver resolved the issue.