hal.dll is KILLING ME

[frequencyg]

I have switced windows versions so many times but i always get this DPC latency. Take a look
_________________________________________________________________________________________________________
CONCLUSION
_________________________________________________________________________________________________________
Your system appears to be having trouble handling real-time audio and other tasks. You are likely to experience buffer underruns appearing as drop outs, clicks or pops. 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:02:38 (h:mm:ss) on all processors.


_________________________________________________________________________________________________________
SYSTEM INFORMATION
_________________________________________________________________________________________________________
Computer name: FREQUENCY-PC
OS version: Windows 7 Service Pack 1, 6.1, build: 7601 (x64)
Hardware: ASRock, Z97 Anniversary
CPU: GenuineIntel Intel(R) Core(TM) i5-4570 CPU @ 3.20GHz
Logical processors: 4
Processor groups: 1
RAM: 12239 MB total


_________________________________________________________________________________________________________
CPU SPEED
_________________________________________________________________________________________________________
Reported CPU speed: 320 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.

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): 2706.543544
Average measured interrupt to process latency (µs): 2.265190

Highest measured interrupt to DPC latency (µs): 194.238819
Average measured interrupt to DPC latency (µs): 0.495201


_________________________________________________________________________________________________________
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): 18.85250
Driver with highest ISR routine execution time: hal.dll - Hardware Abstraction Layer DLL, Microsoft Corporation

Highest reported total ISR routine time (%): 0.078628
Driver with highest ISR total time: hal.dll - Hardware Abstraction Layer DLL, Microsoft Corporation

Total time spent in ISRs (%) 0.078920

ISR count (execution time <250 µs): 137274
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): 349.502813
Driver with highest DPC routine execution time: iusb3xhc.sys - Intel(R) USB 3.0 eXtensible Host Controller Driver, Intel Corporation

Highest reported total DPC routine time (%): 0.160904
Driver with highest DPC total execution time: iusb3xhc.sys - Intel(R) USB 3.0 eXtensible Host Controller Driver, Intel Corporation

Total time spent in DPCs (%) 0.273680

DPC count (execution time <250 µs): 551467
DPC count (execution time 250-500 µs): 0
DPC count (execution time 500-999 µs): 6
DPC count (execution time 1000-1999 µs): 0
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: chrome.exe

Total number of hard pagefaults 37701
Hard pagefault count of hardest hit process: 8147
Number of processes hit: 39


_________________________________________________________________________________________________________
PER CPU DATA
_________________________________________________________________________________________________________
CPU 0 Interrupt cycle time (s): 3.272810
CPU 0 ISR highest execution time (µs): 18.85250
CPU 0 ISR total execution time (s): 0.498823
CPU 0 ISR count: 137274
CPU 0 DPC highest execution time (µs): 349.502813
CPU 0 DPC total execution time (s): 1.718153
CPU 0 DPC count: 550681
_________________________________________________________________________________________________________
CPU 1 Interrupt cycle time (s): 0.326277
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): 131.606562
CPU 1 DPC total execution time (s): 0.003320
CPU 1 DPC count: 257
_________________________________________________________________________________________________________
CPU 2 Interrupt cycle time (s): 0.24760
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): 98.872187
CPU 2 DPC total execution time (s): 0.006458
CPU 2 DPC count: 361
_________________________________________________________________________________________________________
CPU 3 Interrupt cycle time (s): 0.326307
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): 176.643750
CPU 3 DPC total execution time (s): 0.001888
CPU 3 DPC count: 174
_________________________________________________________________________________________________________












PC power options are tweaked and drivers are at their latest versions. Help!

 

[Megahertz07]

Sorry, didn't understand your problem.
Can you please summary it.

What the hal.dll has to do with it?