• Welcome to TechPowerUp Forums, Guest! Please check out our forum guidelines for info related to our community.

Stuttering

Joined
Feb 1, 2021
Messages
94 (0.06/day)
Processor 13900k
Motherboard ASUS ROG STRIX Z790 gaming e wifi
Cooling Fractal Celsius+ S36 Prisma
Memory 32GB GSKILL Trident Z5RK 6000MHZ
Video Card(s) MSI RTX 4090 SuprimX
Display(s) LG Electronics 34GN850-B
Case Fractal Meshify
Power Supply Seasonic 1000w
Hi there,

I have an unusual problem I cant find a solution for. Maybe you guys have an idea:

I recently bought a new rig with the following specs:
- Intel i9 12900k
- ASUS ROG Strix Asus Z690-F Gaming Wifi
- 32GB G-Skill Trident DDR5 6000 MHZ
- MSI RTX 3080TI SuprimX
- BeQuiet Dark Power 12, 850 Watt

From time to time - sometimes right after startup/restart, sometimes randomly while gaming or on idle (Desktop) I have a stuttering display.
Let me explain the issue a bit more detailed:

For example: I am flying in MSFS 2020. Every like 0.5 seconds the display laggs for a part of a second. It feels like a specific rhythm every 0.5 seconds, no mater how many frames are displayed.
In desktop mode when the issue occurs there is the exactly same stuttering but I only see it when dragging windows or icons.
The screen is never flashing its just that there is a rhythmic lag.

However, there a some solution to fix the issue but only temporarely:
- Restart
- Unpluggin the display port cable and plugging it in again
- Switching the input source on my monitor from display port to hdmi and switching it back again
- Enabling G-Sync
- Disabling G-Sync

In order to get rid of that issue I completely reinstalled Windows and the display drivers but so far no luck. The manufacturer where I bought the system checked it but they could not find any problems. Unfortunatley they had not my monitor model there but they said that they tried several other monitors and there were no such problems. - I have the Asus TUF Gaming VG35VQ Monitor

Actually I trust these guys as my system usually runs fine. In Firestrike I get over 20K

Im thinking about buying a new monitor but it is only one year old and with my old system (9900K, Zotac RTX 1080 AMP, 16GB Corsair 3200 MHZ) there were no issues.

Do you guys have any ideas?


Thank you in advance!
 
How is your RAM configured? is it correctly set up in dual channel?
 
Hey Freedomeclips,

thank you for your answer. How can I check this? Does CPU-Z show how the RAM is configured?

Edit: The RAM is set up to quad channel

RAM.PNG
 
Interesting.

Is your ram a matched 32GB kit or did you put two different 16GB kits together? mismatched ram can cause issues.
 
I have the Strix E version of this board and the exact same ram. Your ram is only running at 4800Mhz, for starters. Go into the bios and enable XMP1 profile for the ram. It will automatically set the 6000Mhz. This ram is qualified, so it will work. It is also a good overclocker, I'm testing 6400Mhz and will soon move up to 6800Mhz. Just enable XMP1. Also, what cable are you using for your monitor, ie is it several years old?

Edit: You can tell your ram is running at 4800 by doubling the DRAM frequency. It should be reporting 3000Mhz, not 2400.
 
There are two RAM bars - both are G-Skill TridentZ

I have the Strix E version of this board and the exact same ram. Your ram is only running at 4800Mhz, for starters. Go into the bios and enable XMP1 profile for the ram. It will automatically set the 6000Mhz. This ram is qualified, so it will work. It is also a good overclocker, I'm testing 6400Mhz and will soon move up to 6800Mhz. Just enable XMP1. Also, what cable are you using for your monitor, ie is it several years old?
Today I bought a new display port 1.3 cable from sharkoon. Using 6000MHZ did not make any changes - I already tried that few days ago.
 
Also, if you are interested, the reason why the ram runs at 4800Mhz is because this is the JEDEC standard Mhz for the ram. This is why you have to enable the XMP profile in the bios so that the ram can run at it's 6000Mhz.

There are two RAM bars - both are G-Skill TridentZ


Today I bought a new display port 1.3 cable from sharkoon. Using 6000MHZ did not make any changes - I already tried that few days ago.
Okay. As I replied earlier, I'd get your ram working at 6Mhz first, although I don't believe this is the issue since it should run just fine on the 4800Mhz standard. Also, I'd turn off Vsync to help reduce micro stuttering.
 
Download LatencyMon install,run it while you doing usual things(gaming,watching videos...etc) for 20-30min and see if your latency is in the "green" or something possibly causing some issues........GL
 
Download LatencyMon install,run it while you doing usual things(gaming,watching videos...etc) for 20-30min and see if your latency is in the "green" or something possibly causing some issues........GL
Thank you, I just downloaded it. I will give it a try and come back later.

Alright - I already ran LatencyMon an 26th of January. This time I had the described stutters. Here is what the log said back then (further down is the log from todays run):

_________________________________________________________________________________________________________

CONCLUSION

_________________________________________________________________________________________________________

Your system seems to be having difficulty handling real-time audio and other tasks. You may experience drop outs, clicks or pops due to buffer underruns. One or more DPC routines that belong to a driver running in your system appear to be executing for too long. One problem may be related to power management, disable CPU throttling settings in Control Panel and BIOS setup. Check for BIOS updates.

LatencyMon has been analyzing your system for 0:22:19 (h:mm:ss) on all processors.





_________________________________________________________________________________________________________

SYSTEM INFORMATION

_________________________________________________________________________________________________________

Computer name: 12900K-3080TI

OS version: Windows 10, 10.0, version 2009, build: 19044 (x64)

Hardware: System Product Name, ASUS

BIOS: 0811

CPU: GenuineIntel 12th Gen Intel(R) Core(TM) i9-12900K

Logical processors: 24

Processor groups: 1

Processor group size: 24

RAM: 32509 MB total





_________________________________________________________________________________________________________

CPU SPEED

_________________________________________________________________________________________________________

Reported CPU speed (WMI): 3187 MHz

Reported CPU speed (registry): 3187 MHz



Note: reported execution times may be calculated based on a fixed reported CPU speed. Disable variable speed settings like Intel Speed Step and AMD Cool N Quiet in the BIOS setup for more accurate results.





_________________________________________________________________________________________________________

MEASURED INTERRUPT TO USER PROCESS LATENCIES

_________________________________________________________________________________________________________

The interrupt to process latency reflects the measured interval that a usermode process needed to respond to a hardware request from the moment the interrupt service routine started execution. This includes the scheduling and execution of a DPC routine, the signaling of an event and the waking up of a usermode thread from an idle wait state in response to that event.



Highest measured interrupt to process latency (µs): 743,90

Average measured interrupt to process latency (µs): 4,401146



Highest measured interrupt to DPC latency (µs): 740,90

Average measured interrupt to DPC latency (µs): 0,892177





_________________________________________________________________________________________________________

REPORTED ISRs

_________________________________________________________________________________________________________

Interrupt service routines are routines installed by the OS and device drivers that execute in response to a hardware interrupt signal.



Highest ISR routine execution time (µs): 49,902730

Driver with highest ISR routine execution time: Wdf01000.sys - Kernelmodustreiber-Frameworklaufzeit, Microsoft Corporation



Highest reported total ISR routine time (%): 0,000037

Driver with highest ISR total time: Wdf01000.sys - Kernelmodustreiber-Frameworklaufzeit, Microsoft Corporation



Total time spent in ISRs (%) 0,000039



ISR count (execution time <250 µs): 82870

ISR count (execution time 250-500 µs): 0

ISR count (execution time 500-1000 µs): 0

ISR count (execution time 1000-2000 µs): 0

ISR count (execution time 2000-4000 µs): 0

ISR count (execution time >=4000 µs): 0





_________________________________________________________________________________________________________

REPORTED DPCs

_________________________________________________________________________________________________________

DPC routines are part of the interrupt servicing dispatch mechanism and disable the possibility for a process to utilize the CPU while it is interrupted until the DPC has finished execution.



Highest DPC routine execution time (µs): 1141,327267

Driver with highest DPC routine execution time: nvlddmkm.sys - NVIDIA Windows Kernel Mode Driver, Version 511.23 , NVIDIA Corporation



Highest reported total DPC routine time (%): 0,002117

Driver with highest DPC total execution time: storport.sys - Microsoft Storage Port Driver, Microsoft Corporation



Total time spent in DPCs (%) 0,009762



DPC count (execution time <250 µs): 1028360

DPC count (execution time 250-500 µs): 0

DPC count (execution time 500-10000 µs): 27

DPC count (execution time 1000-2000 µs): 2

DPC count (execution time 2000-4000 µs): 0

DPC count (execution time >=4000 µs): 0





_________________________________________________________________________________________________________

REPORTED HARD PAGEFAULTS

_________________________________________________________________________________________________________

Hard pagefaults are events that get triggered by making use of virtual memory that is not resident in RAM but backed by a memory mapped file on disk. The process of resolving the hard pagefault requires reading in the memory from disk while the process is interrupted and blocked from execution.



NOTE: some processes were hit by hard pagefaults. If these were programs producing audio, they are likely to interrupt the audio stream resulting in dropouts, clicks and pops. Check the Processes tab to see which programs were hit.



Process with highest pagefault count: svchost.exe



Total number of hard pagefaults 99093

Hard pagefault count of hardest hit process: 60122

Number of processes hit: 89





_________________________________________________________________________________________________________

PER CPU DATA

_________________________________________________________________________________________________________

CPU 0 Interrupt cycle time (s): 9,570612

CPU 0 ISR highest execution time (µs): 0,0

CPU 0 ISR total execution time (s): 0,0

CPU 0 ISR count: 0

CPU 0 DPC highest execution time (µs): 1073,324443

CPU 0 DPC total execution time (s): 0,236199

CPU 0 DPC count: 190828

_________________________________________________________________________________________________________

CPU 1 Interrupt cycle time (s): 9,042239

CPU 1 ISR highest execution time (µs): 0,0

CPU 1 ISR total execution time (s): 0,0

CPU 1 ISR count: 0

CPU 1 DPC highest execution time (µs): 7,347976

CPU 1 DPC total execution time (s): 0,000177

CPU 1 DPC count: 91

_________________________________________________________________________________________________________

CPU 2 Interrupt cycle time (s): 5,598151

CPU 2 ISR highest execution time (µs): 0,0

CPU 2 ISR total execution time (s): 0,0

CPU 2 ISR count: 0

CPU 2 DPC highest execution time (µs): 371,533103

CPU 2 DPC total execution time (s): 0,061057

CPU 2 DPC count: 42559

_________________________________________________________________________________________________________

CPU 3 Interrupt cycle time (s): 5,403904

CPU 3 ISR highest execution time (µs): 0,0

CPU 3 ISR total execution time (s): 0,0

CPU 3 ISR count: 0

CPU 3 DPC highest execution time (µs): 44,046125

CPU 3 DPC total execution time (s): 0,000279

CPU 3 DPC count: 129

_________________________________________________________________________________________________________

CPU 4 Interrupt cycle time (s): 8,534284

CPU 4 ISR highest execution time (µs): 11,988077

CPU 4 ISR total execution time (s): 0,000463

CPU 4 ISR count: 102

CPU 4 DPC highest execution time (µs): 189,075620

CPU 4 DPC total execution time (s): 0,446045

CPU 4 DPC count: 96575

_________________________________________________________________________________________________________

CPU 5 Interrupt cycle time (s): 6,799905

CPU 5 ISR highest execution time (µs): 0,0

CPU 5 ISR total execution time (s): 0,0

CPU 5 ISR count: 0

CPU 5 DPC highest execution time (µs): 7,621901

CPU 5 DPC total execution time (s): 0,000040

CPU 5 DPC count: 17

_________________________________________________________________________________________________________

CPU 6 Interrupt cycle time (s): 3,338510

CPU 6 ISR highest execution time (µs): 0,0

CPU 6 ISR total execution time (s): 0,0

CPU 6 ISR count: 0

CPU 6 DPC highest execution time (µs): 40,159398

CPU 6 DPC total execution time (s): 0,003930

CPU 6 DPC count: 2730

_________________________________________________________________________________________________________

CPU 7 Interrupt cycle time (s): 3,294894

CPU 7 ISR highest execution time (µs): 0,0

CPU 7 ISR total execution time (s): 0,0

CPU 7 ISR count: 0

CPU 7 DPC highest execution time (µs): 14,931911

CPU 7 DPC total execution time (s): 0,000043

CPU 7 DPC count: 18

_________________________________________________________________________________________________________

CPU 8 Interrupt cycle time (s): 23,512964

CPU 8 ISR highest execution time (µs): 0,0

CPU 8 ISR total execution time (s): 0,0

CPU 8 ISR count: 0

CPU 8 DPC highest execution time (µs): 415,014747

CPU 8 DPC total execution time (s): 0,397151

CPU 8 DPC count: 269485

_________________________________________________________________________________________________________

CPU 9 Interrupt cycle time (s): 30,792288

CPU 9 ISR highest execution time (µs): 0,0

CPU 9 ISR total execution time (s): 0,0

CPU 9 ISR count: 0

CPU 9 DPC highest execution time (µs): 48,428616

CPU 9 DPC total execution time (s): 0,000403

CPU 9 DPC count: 196

_________________________________________________________________________________________________________

CPU 10 Interrupt cycle time (s): 18,084729

CPU 10 ISR highest execution time (µs): 0,0

CPU 10 ISR total execution time (s): 0,0

CPU 10 ISR count: 0

CPU 10 DPC highest execution time (µs): 370,626608

CPU 10 DPC total execution time (s): 0,252429

CPU 10 DPC count: 185742

_________________________________________________________________________________________________________

CPU 11 Interrupt cycle time (s): 21,644028

CPU 11 ISR highest execution time (µs): 0,0

CPU 11 ISR total execution time (s): 0,0

CPU 11 ISR count: 0

CPU 11 DPC highest execution time (µs): 80,778161

CPU 11 DPC total execution time (s): 0,004586

CPU 11 DPC count: 2962

_________________________________________________________________________________________________________

CPU 12 Interrupt cycle time (s): 33,849052

CPU 12 ISR highest execution time (µs): 49,902730

CPU 12 ISR total execution time (s): 0,011983

CPU 12 ISR count: 82768

CPU 12 DPC highest execution time (µs): 174,463445

CPU 12 DPC total execution time (s): 0,284752

CPU 12 DPC count: 85133

_________________________________________________________________________________________________________

CPU 13 Interrupt cycle time (s): 31,648541

CPU 13 ISR highest execution time (µs): 0,0

CPU 13 ISR total execution time (s): 0,0

CPU 13 ISR count: 0

CPU 13 DPC highest execution time (µs): 7,674616

CPU 13 DPC total execution time (s): 0,000040

CPU 13 DPC count: 11

_________________________________________________________________________________________________________

CPU 14 Interrupt cycle time (s): 2,805679

CPU 14 ISR highest execution time (µs): 0,0

CPU 14 ISR total execution time (s): 0,0

CPU 14 ISR count: 0

CPU 14 DPC highest execution time (µs): 8,084405

CPU 14 DPC total execution time (s): 0,000141

CPU 14 DPC count: 54

_________________________________________________________________________________________________________

CPU 15 Interrupt cycle time (s): 2,791416

CPU 15 ISR highest execution time (µs): 0,0

CPU 15 ISR total execution time (s): 0,0

CPU 15 ISR count: 0

CPU 15 DPC highest execution time (µs): 0,0

CPU 15 DPC total execution time (s): 0,0

CPU 15 DPC count: 0

_________________________________________________________________________________________________________

CPU 16 Interrupt cycle time (s): 45,362378

CPU 16 ISR highest execution time (µs): 0,0

CPU 16 ISR total execution time (s): 0,0

CPU 16 ISR count: 0

CPU 16 DPC highest execution time (µs): 1141,327267

CPU 16 DPC total execution time (s): 1,060902

CPU 16 DPC count: 81495

_________________________________________________________________________________________________________

CPU 17 Interrupt cycle time (s): 27,740622

CPU 17 ISR highest execution time (µs): 0,0

CPU 17 ISR total execution time (s): 0,0

CPU 17 ISR count: 0

CPU 17 DPC highest execution time (µs): 77,111390

CPU 17 DPC total execution time (s): 0,031116

CPU 17 DPC count: 6990

_________________________________________________________________________________________________________

CPU 18 Interrupt cycle time (s): 26,366983

CPU 18 ISR highest execution time (µs): 0,0

CPU 18 ISR total execution time (s): 0,0

CPU 18 ISR count: 0

CPU 18 DPC highest execution time (µs): 87,339504

CPU 18 DPC total execution time (s): 0,046817

CPU 18 DPC count: 12993

_________________________________________________________________________________________________________

CPU 19 Interrupt cycle time (s): 25,881033

CPU 19 ISR highest execution time (µs): 0,0

CPU 19 ISR total execution time (s): 0,0

CPU 19 ISR count: 0

CPU 19 DPC highest execution time (µs): 508,113273

CPU 19 DPC total execution time (s): 0,052913

CPU 19 DPC count: 12824

_________________________________________________________________________________________________________

CPU 20 Interrupt cycle time (s): 23,921861

CPU 20 ISR highest execution time (µs): 0,0

CPU 20 ISR total execution time (s): 0,0

CPU 20 ISR count: 0

CPU 20 DPC highest execution time (µs): 177,934735

CPU 20 DPC total execution time (s): 0,065275

CPU 20 DPC count: 10236

_________________________________________________________________________________________________________

CPU 21 Interrupt cycle time (s): 35,188782

CPU 21 ISR highest execution time (µs): 0,0

CPU 21 ISR total execution time (s): 0,0

CPU 21 ISR count: 0

CPU 21 DPC highest execution time (µs): 206,184186

CPU 21 DPC total execution time (s): 0,145645

CPU 21 DPC count: 16158

_________________________________________________________________________________________________________

CPU 22 Interrupt cycle time (s): 24,805007

CPU 22 ISR highest execution time (µs): 0,0

CPU 22 ISR total execution time (s): 0,0

CPU 22 ISR count: 0

CPU 22 DPC highest execution time (µs): 82,942893

CPU 22 DPC total execution time (s): 0,019502

CPU 22 DPC count: 4188

_________________________________________________________________________________________________________

CPU 23 Interrupt cycle time (s): 20,881838

CPU 23 ISR highest execution time (µs): 0,0

CPU 23 ISR total execution time (s): 0,0

CPU 23 ISR count: 0

CPU 23 DPC highest execution time (µs): 83,128961

CPU 23 DPC total execution time (s): 0,028014

CPU 23 DPC count: 6975


_____________________________________________
_____________________________________________


Right now I ran it again and I had no stutters. Here is what the log sais:

_________________________________________________________________________________________________________

CONCLUSION

_________________________________________________________________________________________________________

Your system appears to be suitable for handling real-time audio and other tasks without dropouts.

LatencyMon has been analyzing your system for 0:30:31 (h:mm:ss) on all processors.





_________________________________________________________________________________________________________

SYSTEM INFORMATION

_________________________________________________________________________________________________________

Computer name: DESKTOP-FDQJDON

OS version: Windows 10, 10.0, version 2009, build: 19044 (x64)

Hardware: System Product Name, ASUS

BIOS: 1003

CPU: GenuineIntel 12th Gen Intel(R) Core(TM) i9-12900K

Logical processors: 24

Processor groups: 1

Processor group size: 24

RAM: 32509 MB total





_________________________________________________________________________________________________________

CPU SPEED

_________________________________________________________________________________________________________

Reported CPU speed (WMI): 320 MHz

Reported CPU speed (registry): 3187 MHz



Note: reported execution times may be calculated based on a fixed reported CPU speed. Disable variable speed settings like Intel Speed Step and AMD Cool N Quiet in the BIOS setup for more accurate results.





_________________________________________________________________________________________________________

MEASURED INTERRUPT TO USER PROCESS LATENCIES

_________________________________________________________________________________________________________

The interrupt to process latency reflects the measured interval that a usermode process needed to respond to a hardware request from the moment the interrupt service routine started execution. This includes the scheduling and execution of a DPC routine, the signaling of an event and the waking up of a usermode thread from an idle wait state in response to that event.



Highest measured interrupt to process latency (µs): 96,50

Average measured interrupt to process latency (µs): 4,535353



Highest measured interrupt to DPC latency (µs): 94,70

Average measured interrupt to DPC latency (µs): 1,034352





_________________________________________________________________________________________________________

REPORTED ISRs

_________________________________________________________________________________________________________

Interrupt service routines are routines installed by the OS and device drivers that execute in response to a hardware interrupt signal.



Highest ISR routine execution time (µs): 48,650769

Driver with highest ISR routine execution time: Wdf01000.sys - Kernelmodustreiber-Frameworklaufzeit, Microsoft Corporation



Highest reported total ISR routine time (%): 0,000037

Driver with highest ISR total time: Wdf01000.sys - Kernelmodustreiber-Frameworklaufzeit, Microsoft Corporation



Total time spent in ISRs (%) 0,000037



ISR count (execution time <250 µs): 5613

ISR count (execution time 250-500 µs): 0

ISR count (execution time 500-1000 µs): 0

ISR count (execution time 1000-2000 µs): 0

ISR count (execution time 2000-4000 µs): 0

ISR count (execution time >=4000 µs): 0





_________________________________________________________________________________________________________

REPORTED DPCs

_________________________________________________________________________________________________________

DPC routines are part of the interrupt servicing dispatch mechanism and disable the possibility for a process to utilize the CPU while it is interrupted until the DPC has finished execution.



Highest DPC routine execution time (µs): 465,907123

Driver with highest DPC routine execution time: ntoskrnl.exe - NT Kernel & System, Microsoft Corporation



Highest reported total DPC routine time (%): 0,009272

Driver with highest DPC total execution time: nvlddmkm.sys - NVIDIA Windows Kernel Mode Driver, Version 511.23 , NVIDIA Corporation



Total time spent in DPCs (%) 0,038308



DPC count (execution time <250 µs): 445309

DPC count (execution time 250-500 µs): 0

DPC count (execution time 500-10000 µs): 24

DPC count (execution time 1000-2000 µs): 0

DPC count (execution time 2000-4000 µs): 0

DPC count (execution time >=4000 µs): 0





_________________________________________________________________________________________________________

REPORTED HARD PAGEFAULTS

_________________________________________________________________________________________________________

Hard pagefaults are events that get triggered by making use of virtual memory that is not resident in RAM but backed by a memory mapped file on disk. The process of resolving the hard pagefault requires reading in the memory from disk while the process is interrupted and blocked from execution.



NOTE: some processes were hit by hard pagefaults. If these were programs producing audio, they are likely to interrupt the audio stream resulting in dropouts, clicks and pops. Check the Processes tab to see which programs were hit.



Process with highest pagefault count: msmpeng.exe



Total number of hard pagefaults 525

Hard pagefault count of hardest hit process: 183

Number of processes hit: 15





_________________________________________________________________________________________________________

PER CPU DATA

_________________________________________________________________________________________________________

CPU 0 Interrupt cycle time (s): 2,039717

CPU 0 ISR highest execution time (µs): 0,0

CPU 0 ISR total execution time (s): 0,0

CPU 0 ISR count: 0

CPU 0 DPC highest execution time (µs): 72,343897

CPU 0 DPC total execution time (s): 0,023730

CPU 0 DPC count: 17275

_________________________________________________________________________________________________________

CPU 1 Interrupt cycle time (s): 1,928179

CPU 1 ISR highest execution time (µs): 0,0

CPU 1 ISR total execution time (s): 0,0

CPU 1 ISR count: 0

CPU 1 DPC highest execution time (µs): 15,384060

CPU 1 DPC total execution time (s): 0,000102

CPU 1 DPC count: 25

_________________________________________________________________________________________________________

CPU 2 Interrupt cycle time (s): 0,566154

CPU 2 ISR highest execution time (µs): 0,0

CPU 2 ISR total execution time (s): 0,0

CPU 2 ISR count: 0

CPU 2 DPC highest execution time (µs): 47,691559

CPU 2 DPC total execution time (s): 0,001006

CPU 2 DPC count: 346

_________________________________________________________________________________________________________

CPU 3 Interrupt cycle time (s): 0,572114

CPU 3 ISR highest execution time (µs): 0,0

CPU 3 ISR total execution time (s): 0,0

CPU 3 ISR count: 0

CPU 3 DPC highest execution time (µs): 4,990901

CPU 3 DPC total execution time (s): 0,000024

CPU 3 DPC count: 10

_________________________________________________________________________________________________________

CPU 4 Interrupt cycle time (s): 0,303967

CPU 4 ISR highest execution time (µs): 0,0

CPU 4 ISR total execution time (s): 0,0

CPU 4 ISR count: 0

CPU 4 DPC highest execution time (µs): 47,254158

CPU 4 DPC total execution time (s): 0,00030

CPU 4 DPC count: 99

_________________________________________________________________________________________________________

CPU 5 Interrupt cycle time (s): 0,301421

CPU 5 ISR highest execution time (µs): 0,0

CPU 5 ISR total execution time (s): 0,0

CPU 5 ISR count: 0

CPU 5 DPC highest execution time (µs): 0,0

CPU 5 DPC total execution time (s): 0,0

CPU 5 DPC count: 0

_________________________________________________________________________________________________________

CPU 6 Interrupt cycle time (s): 0,262537

CPU 6 ISR highest execution time (µs): 0,0

CPU 6 ISR total execution time (s): 0,0

CPU 6 ISR count: 0

CPU 6 DPC highest execution time (µs): 42,127706

CPU 6 DPC total execution time (s): 0,000161

CPU 6 DPC count: 48

_________________________________________________________________________________________________________

CPU 7 Interrupt cycle time (s): 0,260517

CPU 7 ISR highest execution time (µs): 0,0

CPU 7 ISR total execution time (s): 0,0

CPU 7 ISR count: 0

CPU 7 DPC highest execution time (µs): 0,0

CPU 7 DPC total execution time (s): 0,0

CPU 7 DPC count: 0

_________________________________________________________________________________________________________

CPU 8 Interrupt cycle time (s): 4,796532

CPU 8 ISR highest execution time (µs): 0,0

CPU 8 ISR total execution time (s): 0,0

CPU 8 ISR count: 0

CPU 8 DPC highest execution time (µs): 465,907123

CPU 8 DPC total execution time (s): 0,779530

CPU 8 DPC count: 313096

_________________________________________________________________________________________________________

CPU 9 Interrupt cycle time (s): 4,262650

CPU 9 ISR highest execution time (µs): 0,0

CPU 9 ISR total execution time (s): 0,0

CPU 9 ISR count: 0

CPU 9 DPC highest execution time (µs): 54,167556

CPU 9 DPC total execution time (s): 0,000125

CPU 9 DPC count: 25

_________________________________________________________________________________________________________

CPU 10 Interrupt cycle time (s): 3,486931

CPU 10 ISR highest execution time (µs): 0,0

CPU 10 ISR total execution time (s): 0,0

CPU 10 ISR count: 0

CPU 10 DPC highest execution time (µs): 77,938814

CPU 10 DPC total execution time (s): 0,096621

CPU 10 DPC count: 24168

_________________________________________________________________________________________________________

CPU 11 Interrupt cycle time (s): 3,981145

CPU 11 ISR highest execution time (µs): 0,0

CPU 11 ISR total execution time (s): 0,0

CPU 11 ISR count: 0

CPU 11 DPC highest execution time (µs): 41,251334

CPU 11 DPC total execution time (s): 0,000073

CPU 11 DPC count: 18

_________________________________________________________________________________________________________

CPU 12 Interrupt cycle time (s): 3,169185

CPU 12 ISR highest execution time (µs): 48,650769

CPU 12 ISR total execution time (s): 0,001876

CPU 12 ISR count: 5613

CPU 12 DPC highest execution time (µs): 55,585190

CPU 12 DPC total execution time (s): 0,030676

CPU 12 DPC count: 5622

_________________________________________________________________________________________________________

CPU 13 Interrupt cycle time (s): 2,604069

CPU 13 ISR highest execution time (µs): 0,0

CPU 13 ISR total execution time (s): 0,0

CPU 13 ISR count: 0

CPU 13 DPC highest execution time (µs): 0,0

CPU 13 DPC total execution time (s): 0,0

CPU 13 DPC count: 0

_________________________________________________________________________________________________________

CPU 14 Interrupt cycle time (s): 0,230151

CPU 14 ISR highest execution time (µs): 0,0

CPU 14 ISR total execution time (s): 0,0

CPU 14 ISR count: 0

CPU 14 DPC highest execution time (µs): 0,0

CPU 14 DPC total execution time (s): 0,0

CPU 14 DPC count: 0

_________________________________________________________________________________________________________

CPU 15 Interrupt cycle time (s): 0,230453

CPU 15 ISR highest execution time (µs): 0,0

CPU 15 ISR total execution time (s): 0,0

CPU 15 ISR count: 0

CPU 15 DPC highest execution time (µs): 0,0

CPU 15 DPC total execution time (s): 0,0

CPU 15 DPC count: 0

_________________________________________________________________________________________________________

CPU 16 Interrupt cycle time (s): 14,999135

CPU 16 ISR highest execution time (µs): 0,0

CPU 16 ISR total execution time (s): 0,0

CPU 16 ISR count: 0

CPU 16 DPC highest execution time (µs): 444,721682

CPU 16 DPC total execution time (s): 0,981845

CPU 16 DPC count: 80407

_________________________________________________________________________________________________________

CPU 17 Interrupt cycle time (s): 4,451147

CPU 17 ISR highest execution time (µs): 0,0

CPU 17 ISR total execution time (s): 0,0

CPU 17 ISR count: 0

CPU 17 DPC highest execution time (µs): 65,604958

CPU 17 DPC total execution time (s): 0,002268

CPU 17 DPC count: 452

_________________________________________________________________________________________________________

CPU 18 Interrupt cycle time (s): 4,433428

CPU 18 ISR highest execution time (µs): 0,0

CPU 18 ISR total execution time (s): 0,0

CPU 18 ISR count: 0

CPU 18 DPC highest execution time (µs): 67,356134

CPU 18 DPC total execution time (s): 0,001896

CPU 18 DPC count: 460

_________________________________________________________________________________________________________

CPU 19 Interrupt cycle time (s): 4,423458

CPU 19 ISR highest execution time (µs): 0,0

CPU 19 ISR total execution time (s): 0,0

CPU 19 ISR count: 0

CPU 19 DPC highest execution time (µs): 64,208974

CPU 19 DPC total execution time (s): 0,002134

CPU 19 DPC count: 438

_________________________________________________________________________________________________________

CPU 20 Interrupt cycle time (s): 3,692145

CPU 20 ISR highest execution time (µs): 0,0

CPU 20 ISR total execution time (s): 0,0

CPU 20 ISR count: 0

CPU 20 DPC highest execution time (µs): 64,351114

CPU 20 DPC total execution time (s): 0,006025

CPU 20 DPC count: 607

_________________________________________________________________________________________________________

CPU 21 Interrupt cycle time (s): 4,455589

CPU 21 ISR highest execution time (µs): 0,0

CPU 21 ISR total execution time (s): 0,0

CPU 21 ISR count: 0

CPU 21 DPC highest execution time (µs): 78,806401

CPU 21 DPC total execution time (s): 0,001287

CPU 21 DPC count: 238

_________________________________________________________________________________________________________

CPU 22 Interrupt cycle time (s): 4,553748

CPU 22 ISR highest execution time (µs): 0,0

CPU 22 ISR total execution time (s): 0,0

CPU 22 ISR count: 0

CPU 22 DPC highest execution time (µs): 66,373078

CPU 22 DPC total execution time (s): 0,001447

CPU 22 DPC count: 236

_________________________________________________________________________________________________________

CPU 23 Interrupt cycle time (s): 4,560009

CPU 23 ISR highest execution time (µs): 0,0

CPU 23 ISR total execution time (s): 0,0

CPU 23 ISR count: 0

CPU 23 DPC highest execution time (µs): 80,092877

CPU 23 DPC total execution time (s): 0,012382

CPU 23 DPC count: 1763

_________________________________________________________________________________________________________
 
Last edited by a moderator:
I didn't read thru the entire log, but noticed that your bios version is the same that I upgraded to on my Strix E, version 0811. There is a newer version of the bios, on the strix E anyway which I brought my MB up to a couple of days ago, so please check to see if the new bios also applies to your Strix F MB. There are the usual suspects, you could reinstall your graphics drivers doing a 'clean' install and use the official release drivers.

Also, when I booted into the system for the first time a few days ago, the bios boot screen suggested disabling the Asus multi core enhancement, which I did. Do some research on this. I've disabled it.
 
I didn't read thru the entire log, but noticed that your bios version is the same that I upgraded to on my Strix E, version 0811. There is a newer version of the bios, on the strix E anyway which I brought my MB up to a couple of days ago, so please check to see if the new bios also applies to your Strix F MB. There are the usual suspects, you could reinstall your graphics drivers doing a 'clean' install and use the official release drivers.

Also, when I booted into the system for the first time a few days ago, the bios boot screen suggested disabling the Asus multi core enhancement, which I did. Do some research on this. I've disabled it.
Good point - today I upgraded the Bios to the latest version. Didnt fix the issue.
Edit: A clean reinstall of the drivers did also not fix the issue.
 
I didn't read thru the entire log, but noticed that your bios version is the same that I upgraded to on my Strix E, version 0811. There is a newer version of the bios, on the strix E anyway which I brought my MB up to a couple of days ago, so please check to see if the new bios also applies to your Strix F MB. There are the usual suspects, you could reinstall your graphics drivers doing a 'clean' install and use the official release drivers.

Also, when I booted into the system for the first time a few days ago, the bios boot screen suggested disabling the Asus multi core enhancement, which I did. Do some research on this. I've disabled it.
You can also enable intel adaptive boost technology if not already. It is above or below the multi core enhancement option.
 
Thank you, I just downloaded it. I will give it a try and come back later.

Alright - I already ran LatencyMon an 26th of January. This time I had the described stutters. Here is what the log said back then (further down is the log from todays run):

_________________________________________________________________________________________________________

CONCLUSION

_________________________________________________________________________________________________________

Your system seems to be having difficulty handling real-time audio and other tasks. You may experience drop outs, clicks or pops due to buffer underruns. One or more DPC routines that belong to a driver running in your system appear to be executing for too long. One problem may be related to power management, disable CPU throttling settings in Control Panel and BIOS setup. Check for BIOS updates.

LatencyMon has been analyzing your system for 0:22:19 (h:mm:ss) on all processors.
Well....sometimes this issue can be fixed easily by installing the new or different driver depends what is causing the problem but you can try and pinpoint the actual cause or simply try changing the drivers for "usual" suspects like :network,sound,GPU also check your mobo BIOS and update if newer vers. exist.........GL
 
Probably mobo and cpu
 
Well....sometimes this issue can be fixed easily by installing the new or different driver depends what is causing the problem but you can try and pinpoint the actual cause or simply try changing the drivers for "usual" suspects like :network,sound,GPU also check your mobo BIOS and update if newer vers. exist.........GL
I will second this. Go to asus and download the latest drivers, particularly the audio drivers. If they are all current, I would reinstall them all...USB, audio, lan, etc.
 
I will second this. Go to asus and download the latest drivers, particularly the audio drivers. If they are all current, I would reinstall them all...USB, audio, lan, etc.

Id look at Realtek to see if they have them, if not then the mobo maker.

Otherwise disable the audio and plug in a Sound Card
 
Id look at Realtek to see if they have them, if not then the mobo maker.

Otherwise disable the audio and plug in a Sound Card
Hi, even a clean windows reinstall with installing the latest drivers did not solve the issues.
I tried uninstalling GeForce Experience - let’s see if the stuttering occurs.
 
If you installed all latest drivers and you have latest motherboard bios and also if your GPU have latest bios if you really tried all other possible software related settings then it is possible that is something hardware related....maybe you can try some other GPU and see if this also happens....GL
 
Last edited:
Stuff to try - disabling HPET and also make sure gpu is in MSI mode. Also make sure gpu isn't in low latency mode and IS in max performance power management mode. Also try manually setting refresh rate for the monitor.
 
I managed to find the cause - it was the hp reverb g2. When it is plugged in, there is a change of getting this issues. Without the vr headset I get no problems. Maybe it is because of the different refresh rates of the monitor an the headset.

can be closed
 
You mentioned Gsync

Disable it entirely and see what happens, then test it with fullscreen only support (not windowed)

You literally could have a single application running at a low FPS, forcing Gsync to slow you down (icue did this for a few versions, as did some overlays)
 
You mentioned Gsync

Disable it entirely and see what happens, then test it with fullscreen only support (not windowed)

You literally could have a single application running at a low FPS, forcing Gsync to slow you down (icue did this for a few versions, as did some overlays)
G-Sync did not cause this issue. No matter if it was activated or deactivated the problems occurred. But when the stutters appeared I could get rid of them by either enabling g-sync (when it was deactivated before the stutters occurred) or disabling g-sync (when it was activated before the stutters occurred). In both situations the screen got black for a second and then the stutters were gone.
I even tried this with another PC and the HP reverb exactly the same behavior. The Monitor runs at 100 Hz the revering g2 runs at 60Hz or 90Hz. I came to this solution as people in the Nvidia forums mentioned similar problems when using two monitors with different refresh rates.
 
Well, are you running multiple monitors?
For god knows what reason you listed your monitor paragraphs after the system specs so i didnt even notice it was there, at first

I really, really want to push w1zzard to direct users straight to the specs page because it comes up in almost every help thread
Go here
TechPowerUp Forums
fill out your complete hardware specs
tick yes to make it visible

A few facts on that display, the VG35VQ:

1. It's not Gsync. It's adpative sync. Disable it, leave it off til you get this sorted. Nvidia does not support adaptive sync, getting it to work is a miracle.
I've had to do this with both my freesync monitors, adaptive sync ones can be worse


2. Disable VRR in windows, no its not quite the same thing

1644912879134.png



3. Are you using DP 1.2 or HDMI 2.0? They're both similar in bandwidth, but DP has the edge there... but it may also be more sensitive to issues with your cable.
Nvidia dont support gsync over HDMI, so forcibly disabling Gsync and adaptive sync by moving to HDMI may solve the issue


4. This does seem like a monitor specific problem, so update its firmware, change your HDMI and DP cables and make ZERO assumptions about what 'works' or 'should work' - TEST things. Default monitor settings can be pure garbage, it took me days to get mine tuned in right without black crush and smearing. Make sure you have ELMB, HDR and all the fancy monitor features disabled - native res and refresh, no more no less.

5. You've tested software with the clean install, and you're testing display hardware. Now to test the rest - half your system specs are missing so no one here can give you any useful information or advice related to that. Unintentionally, you've focused the help and advice you're getting and could be guiding us away from the answer. We don't know if you've got three monitors, HDMI sound systems showing as phantom displays, wallpaper engine changing 3D animated wallpapers every 30 seconds, or 40TB of mechanical drives powering on and off (mech drives seriously are a cause of stutter and lag as they spin up from idle)
 
Well, are you running multiple monitors?
For god knows what reason you listed your monitor paragraphs after the system specs so i didnt even notice it was there, at first

I really, really want to push w1zzard to direct users straight to the specs page because it comes up in almost every help thread
Go here
TechPowerUp Forums
fill out your complete hardware specs
tick yes to make it visible

A few facts on that display, the VG35VQ:

1. It's not Gsync. It's adpative sync. Disable it, leave it off til you get this sorted. Nvidia does not support adaptive sync, getting it to work is a miracle.
I've had to do this with both my freesync monitors, adaptive sync ones can be worse


2. Disable VRR in windows, no its not quite the same thing

View attachment 236704


3. Are you using DP 1.2 or HDMI 2.0? They're both similar in bandwidth, but DP has the edge there... but it may also be more sensitive to issues with your cable.
Nvidia dont support gsync over HDMI, so forcibly disabling Gsync and adaptive sync by moving to HDMI may solve the issue


4. This does seem like a monitor specific problem, so update its firmware, change your HDMI and DP cables and make ZERO assumptions about what 'works' or 'should work' - TEST things. Default monitor settings can be pure garbage, it took me days to get mine tuned in right without black crush and smearing. Make sure you have ELMB, HDR and all the fancy monitor features disabled - native res and refresh, no more no less.

5. You've tested software with the clean install, and you're testing display hardware. Now to test the rest - half your system specs are missing so no one here can give you any useful information or advice related to that. Unintentionally, you've focused the help and advice you're getting and could be guiding us away from the answer. We don't know if you've got three monitors, HDMI sound systems showing as phantom displays, wallpaper engine changing 3D animated wallpapers every 30 seconds, or 40TB of mechanical drives powering on and off (mech drives seriously are a cause of stutter and lag as they spin up from idle)
Hi there, even after reading your post multiple times I can’t get rid of this slightly aggressive undertone.
I appreciate your help but like I already mentioned even before you replied: Problem solved and thread can be closed.
Thanks to everyone who kindly tried to help
 
Back
Top