New
#131
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:13:23 (h:mm:ss) on all processors.
__________________________________________________ __________________________________________________ _____
SYSTEM INFORMATION
__________________________________________________ __________________________________________________ _____
Computer name: ANTONIO-PC
OS version: Windows 10 , 10.0, build: 15063 (x64)
Hardware: ASUSTeK COMPUTER INC., MAXIMUS VIII RANGER
CPU: GenuineIntel Intel(R) Core(TM) i5-6600K CPU @ 3.50GHz
Logical processors: 4
Processor groups: 1
RAM: 16323 MB total
__________________________________________________ __________________________________________________ _____
CPU SPEED
__________________________________________________ __________________________________________________ _____
Reported CPU speed: 3504 MHz
Measured CPU speed: 1 MHz (approx.)
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.
WARNING: the CPU speed that was measured is only a fraction of the CPU speed reported. Your CPUs may be throttled back due to variable speed settings and thermal issues. It is suggested that you run a utility which reports your actual CPU frequency and temperature.
__________________________________________________ __________________________________________________ _____
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): 189,369697
Average measured interrupt to process latency (µs): 1,881109
Highest measured interrupt to DPC latency (µs): 187,616274
Average measured interrupt to DPC latency (µs): 0,596959
__________________________________________________ __________________________________________________ _____
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): 77,165525
Driver with highest ISR routine execution time: dxgkrnl.sys - DirectX Graphics Kernel, Microsoft Corporation
Highest reported total ISR routine time (%): 0,489989
Driver with highest ISR total time: dxgkrnl.sys - DirectX Graphics Kernel, Microsoft Corporation
Total time spent in ISRs (%) 0,499044
ISR count (execution time <250 µs): 1223746
ISR count (execution time 250-500 µs): 0
ISR count (execution time 500-999 µs): 0
ISR count (execution time 1000-1999 µs): 0
ISR count (execution time 2000-3999 µ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): 1367,21290
Driver with highest DPC routine execution time: nvlddmkm.sys - NVIDIA Windows Kernel Mode Driver, Version 385.41 , NVIDIA Corporation
Highest reported total DPC routine time (%): 0,165542
Driver with highest DPC total execution time: dxgkrnl.sys - DirectX Graphics Kernel, Microsoft Corporation
Total time spent in DPCs (%) 0,544732
DPC count (execution time <250 µs): 5628380
DPC count (execution time 250-500 µs): 0
DPC count (execution time 500-999 µs): 0
DPC count (execution time 1000-1999 µs): 2
DPC count (execution time 2000-3999 µ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.
Process with highest pagefault count: none
Total number of hard pagefaults 0
Hard pagefault count of hardest hit process: 0
Highest hard pagefault resolution time (µs): 0,0
Total time spent in hard pagefaults (%): 0,0
Number of processes hit: 0
__________________________________________________ __________________________________________________ _____
PER CPU DATA
__________________________________________________ __________________________________________________ _____
CPU 0 Interrupt cycle time (s): 40,919360
CPU 0 ISR highest execution time (µs): 77,165525
CPU 0 ISR total execution time (s): 15,950487
CPU 0 ISR count: 1168336
CPU 0 DPC highest execution time (µs): 1367,21290
CPU 0 DPC total execution time (s): 15,080433
CPU 0 DPC count: 5206364
__________________________________________________ __________________________________________________ _____
CPU 1 Interrupt cycle time (s): 6,463529
CPU 1 ISR highest execution time (µs): 49,341324
CPU 1 ISR total execution time (s): 0,078753
CPU 1 ISR count: 55379
CPU 1 DPC highest execution time (µs): 76,618721
CPU 1 DPC total execution time (s): 1,859461
CPU 1 DPC count: 235068
__________________________________________________ __________________________________________________ _____
CPU 2 Interrupt cycle time (s): 4,350138
CPU 2 ISR highest execution time (µs): 1,831050
CPU 2 ISR total execution time (s): 0,000038
CPU 2 ISR count: 31
CPU 2 DPC highest execution time (µs): 36,725457
CPU 2 DPC total execution time (s): 0,191883
CPU 2 DPC count: 79882
__________________________________________________ __________________________________________________ _____
CPU 3 Interrupt cycle time (s): 3,922103
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): 48,892123
CPU 3 DPC total execution time (s): 0,365004
CPU 3 DPC count: 107068
![]()
As suggested here many times! Strip down the system to bare minimum and make sure you fix one issue at a time. First you MUST fix that audio problem as it's obviously one issue. Another thing you MUST do in order for any measuring tools giving correct values, is to adjust all your power configurations to MAX performance. Don't let anything sleep or speed step down.
are you talking about the AKTEK.exe problem? that is solved, I have no errors in event viewerFirst you MUST fix that audio problem as it's obviously one issue
ram are ok
What you mean by 'throttling', temps are ok, I've never got a crashNext step is to solve all the power management problems, so nothing can start throttling in middle of game play.
I mean power management. Your CPU can step down speed and voltages below reported specs. You can limit this feature in Windows Power Management so that your CPU always run at 100% frequency (or at Turbo Boost frequency when temps allow) and rated voltages.
Example:
On Balanced/Powersaving Mode a 3GHz CPU could be running at 800-3000MHz. Every time no process need full 3GHz, the CPU is speed stepped down to lets say 2.5GHz, if not even that is needed for full app performance, then the frequency is dropped further
down until we reach the lower limit which was 800MHz in this case.
Now when your app suddenly need more speed, the CPU speed start to slowly speed step upwards until it reaches high enough for the app or it reached it's MAX. This can be a too slow process for things like games, so everything fall out of sync. Hence short freezes in the game.
On High Performance Mode a 3GHz CPU always run at least on 100% speed and sometimes even at MAX Turbo Boost frequency, thus possibly eliminating the small lags in Balanced/Powersaving Mode.
So, do you need assistance in configuring these settings? We could set up a Gaming profile for max performance and a balanced mode for normal desktop usage that would keep your computer quiet but responsive.
I've already set the high performane profile in windows 10.Today I updated to the latest Nvidia driver and this is the latencymon response:
this driver is from the previous build, weird