Advertisement
Not a member of Pastebin yet?
Sign Up,
it unlocks many cool features!
- LatencyMon has been analyzing your system for 0:04:31 (h:mm:ss) on all processors.
- _________________________________________________________________________________________________________
- SYSTEM INFORMATION
- _________________________________________________________________________________________________________
- Computer name: DESKTOP-EBCAEAI
- OS version: Windows 10 , 10.0, build: 14393 (x64)
- Hardware: MS-7816, MSI, B85-G43 GAMING (MS-7816)
- CPU: GenuineIntel Intel(R) Core(TM) i5-4460 CPU @ 3.20GHz
- Logical processors: 4
- Processor groups: 1
- RAM: 8053 MB total
- _________________________________________________________________________________________________________
- CPU SPEED
- _________________________________________________________________________________________________________
- Reported CPU speed: 320 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): 278,080178
- Average measured interrupt to process latency (µs): 1,913687
- Highest measured interrupt to DPC latency (µs): 242,880155
- Average measured interrupt to DPC latency (µs): 0,709182
- _________________________________________________________________________________________________________
- 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,065625
- Driver with highest ISR routine execution time: Wdf01000.sys - Kernel Mode Driver Framework Runtime, Microsoft Corporation
- Highest reported total ISR routine time (%): 0,006509
- Driver with highest ISR total time: Wdf01000.sys - Kernel Mode Driver Framework Runtime, Microsoft Corporation
- Total time spent in ISRs (%) 0,006742
- ISR count (execution time <250 µs): 65773
- 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): 1237,754375
- Driver with highest DPC routine execution time: nvlddmkm.sys - NVIDIA Windows Kernel Mode Driver, Version 378.92 , NVIDIA Corporation
- Highest reported total DPC routine time (%): 0,129943
- Driver with highest DPC total execution time: Wdf01000.sys - Kernel Mode Driver Framework Runtime, Microsoft Corporation
- Total time spent in DPCs (%) 0,549555
- DPC count (execution time <250 µs): 1436061
- DPC count (execution time 250-500 µs): 0
- DPC count (execution time 500-999 µs): 8
- DPC count (execution time 1000-1999 µs): 1
- 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.
- 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: csgo.exe
- Total number of hard pagefaults 2696
- Hard pagefault count of hardest hit process: 1237
- Highest hard pagefault resolution time (µs): 315950,27250
- Total time spent in hard pagefaults (%): 0,092220
- Number of processes hit: 18
- _________________________________________________________________________________________________________
- PER CPU DATA
- _________________________________________________________________________________________________________
- CPU 0 Interrupt cycle time (s): 12,247343
- CPU 0 ISR highest execution time (µs): 49,065625
- CPU 0 ISR total execution time (s): 0,073085
- CPU 0 ISR count: 65773
- CPU 0 DPC highest execution time (µs): 1237,754375
- CPU 0 DPC total execution time (s): 5,831077
- CPU 0 DPC count: 1413858
- _________________________________________________________________________________________________________
- CPU 1 Interrupt cycle time (s): 0,739717
- 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): 619,897187
- CPU 1 DPC total execution time (s): 0,0480
- CPU 1 DPC count: 8270
- _________________________________________________________________________________________________________
- CPU 2 Interrupt cycle time (s): 0,681424
- 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): 296,074063
- CPU 2 DPC total execution time (s): 0,039522
- CPU 2 DPC count: 6545
- _________________________________________________________________________________________________________
- CPU 3 Interrupt cycle time (s): 0,666449
- 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): 706,19250
- CPU 3 DPC total execution time (s): 0,038928
- CPU 3 DPC count: 7397
- _________________________________________________________________________________________________________
Advertisement
Add Comment
Please, Sign In to add comment
Advertisement
