F5F Stay Refreshed Software PC Gaming Stuttering/Latency Issues/Freezes

Stuttering/Latency Issues/Freezes

Stuttering/Latency Issues/Freezes

J
JuanchoTarca1
Member
Find
74
04-26-2018, 02:02 AM
#1
Here’s a rewritten version of the text, aiming for clarity and flow while retaining the original information:

My computer is experiencing significant stuttering and freezing issues, particularly during gaming and when launching applications like Faceit AC or Teamspeak. The problem seems to stem from driver conflicts, specifically the NVIDIA kernel driver, NDIS, and ntoskrnl drivers. LatencyMon reveals that interrupt-to-process latency spikes up to 4ms when these drivers exceed 2ms.

I’ve performed numerous hardware tests – RAM, CPU (using Prime95 and UserBenchmark), and my M.2 SSD – all with negative results. I've also taken the PC to a local computer shop for diagnosis and reassembly, but they couldn’t replicate the stuttering. My system specs include an Asus Z390-E motherboard, updated drivers (including Nvidia 430.64), and an MX500 SATA SSD.

I've observed several specific symptoms: a one-second freeze on bootup, stuttering during game launches and throughout gameplay, significant FPS drops when using a second monitor with YouTube videos, and freezes within programs like Faceit AC or Teamspeak. Furthermore, my BIOS exhibits lag, freezing images when navigating through settings. During BIOS access, the computer enters an infinite restart loop before shutting down immediately.

I've tried several troubleshooting steps including clean boots and running diagnostic tools such as WhySoSlow and LatencyMon. These tests highlighted kernel latency issues related to the NVIDIA drivers.

Here’s a summary of what I’ve found:

* **Kernel Latency:** Reaches up to 4ms, primarily due to NVIDIA driver issues.
* **Driver Conflicts:** NDIS and ntoskrnl drivers contribute significantly to the problem, particularly during clean boots.

I'm now considering replacing my motherboard with a new Z390-E model to see if this resolves the issue. I’m open to any further suggestions or ideas for diagnosing this persistent problem.
Reply
Reply
J
JuanchoTarca1
04-26-2018, 02:02 AM #1

Here’s a rewritten version of the text, aiming for clarity and flow while retaining the original information:

My computer is experiencing significant stuttering and freezing issues, particularly during gaming and when launching applications like Faceit AC or Teamspeak. The problem seems to stem from driver conflicts, specifically the NVIDIA kernel driver, NDIS, and ntoskrnl drivers. LatencyMon reveals that interrupt-to-process latency spikes up to 4ms when these drivers exceed 2ms.

I’ve performed numerous hardware tests – RAM, CPU (using Prime95 and UserBenchmark), and my M.2 SSD – all with negative results. I've also taken the PC to a local computer shop for diagnosis and reassembly, but they couldn’t replicate the stuttering. My system specs include an Asus Z390-E motherboard, updated drivers (including Nvidia 430.64), and an MX500 SATA SSD.

I've observed several specific symptoms: a one-second freeze on bootup, stuttering during game launches and throughout gameplay, significant FPS drops when using a second monitor with YouTube videos, and freezes within programs like Faceit AC or Teamspeak. Furthermore, my BIOS exhibits lag, freezing images when navigating through settings. During BIOS access, the computer enters an infinite restart loop before shutting down immediately.

I've tried several troubleshooting steps including clean boots and running diagnostic tools such as WhySoSlow and LatencyMon. These tests highlighted kernel latency issues related to the NVIDIA drivers.

Here’s a summary of what I’ve found:

* **Kernel Latency:** Reaches up to 4ms, primarily due to NVIDIA driver issues.
* **Driver Conflicts:** NDIS and ntoskrnl drivers contribute significantly to the problem, particularly during clean boots.

I'm now considering replacing my motherboard with a new Z390-E model to see if this resolves the issue. I’m open to any further suggestions or ideas for diagnosing this persistent problem.

Reply
Reply
P
PisulasRule
Senior Member
Find
676
04-26-2018, 09:50 AM
#2
Here’s a rewritten version of the text, aiming for clarity and conciseness:

The provided text describes issues with frametime spikes experienced in Counter-Strike: Global Offensive (CS:GO). These spikes occur primarily when firing and are reflected in data captured by MSI Afterburner. Despite hardware specifications indicating high performance – an i7 8700k CPU, a 1080TI GPU, 16GB DDR4 RAM at 3600MHz, and a 750W power supply – the frametime consistently spikes to 15-20ms or even over 40ms. This is particularly noticeable on custom maps. The consistent FPS values observed when not actively engaging in combat suggest the issue isn’t directly related to the game's core mechanics, but rather a system-level problem. The author has attempted to mitigate this by upgrading the motherboard from a 370-f to a Z390-E model, but the spikes persist. The MSI Afterburner screenshot (linked) provides visual evidence of these spikes during gameplay.
Reply
Reply
P
PisulasRule
04-26-2018, 09:50 AM #2

Here’s a rewritten version of the text, aiming for clarity and conciseness:

The provided text describes issues with frametime spikes experienced in Counter-Strike: Global Offensive (CS:GO). These spikes occur primarily when firing and are reflected in data captured by MSI Afterburner. Despite hardware specifications indicating high performance – an i7 8700k CPU, a 1080TI GPU, 16GB DDR4 RAM at 3600MHz, and a 750W power supply – the frametime consistently spikes to 15-20ms or even over 40ms. This is particularly noticeable on custom maps. The consistent FPS values observed when not actively engaging in combat suggest the issue isn’t directly related to the game's core mechanics, but rather a system-level problem. The author has attempted to mitigate this by upgrading the motherboard from a 370-f to a Z390-E model, but the spikes persist. The MSI Afterburner screenshot (linked) provides visual evidence of these spikes during gameplay.

Reply
Reply