New
#21
ok, im still getting DPC spikes even tho i updated my chipset drivers.... any ideas? also system inturrupts is going from .05% to .50% usage avg. and sometimes bumps up to 2% cpu...
ok, im still getting DPC spikes even tho i updated my chipset drivers.... any ideas? also system inturrupts is going from .05% to .50% usage avg. and sometimes bumps up to 2% cpu...
this is what DPC latency said:
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): 1634.494396
Average measured interrupt to process latency (µs): 8.223537
Highest measured interrupt to DPC latency (µs): 264.877622
Average measured interrupt to DPC latency (µs): 3.002724
____________________________________________________________________________________________________ _____
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): 56.978024
Driver with highest ISR routine execution time: HDAudBus.sys - High Definition Audio Bus Driver, Microsoft Corporation
Highest reported total ISR routine time (%): 0.112855
Driver with highest ISR total time: hal.dll - Hardware Abstraction Layer DLL, Microsoft Corporation
Total time spent in ISRs (%) 0.139656
ISR count (execution time <250 µs): 186923
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): 144.744449
Driver with highest DPC routine execution time: netbt.sys - MBT Transport driver, Microsoft Corporation
Highest reported total DPC routine time (%): 0.256292
Driver with highest DPC total execution time: USBPORT.SYS - USB 1.1 & 2.0 Port Driver, Microsoft Corporation
Total time spent in DPCs (%) 0.510596
DPC count (execution time <250 µs): 952624
DPC count (execution time 250-500 µs): 0
DPC count (execution time 500-999 µs): 0
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.
Process with highest pagefault count: latmon.exe
Total number of hard pagefaults 59
Hard pagefault count of hardest hit process: 19
Highest hard pagefault resolution time (µs): 1792.760761
Total time spent in hard pagefaults (%): 0.002957
Number of processes hit: 5
heres a second test:
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): 5930.057927
Average measured interrupt to process latency (µs): 7.660215
Highest measured interrupt to DPC latency (µs): 311.729880
Average measured interrupt to DPC latency (µs): 3.187445
____________________________________________________________________________________________________ _____
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): 36.399864
Driver with highest ISR routine execution time: HDAudBus.sys - High Definition Audio Bus Driver, Microsoft Corporation
Highest reported total ISR routine time (%): 0.117146
Driver with highest ISR total time: hal.dll - Hardware Abstraction Layer DLL, Microsoft Corporation
Total time spent in ISRs (%) 0.136301
ISR count (execution time <250 µs): 145863
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): 147.619619
Driver with highest DPC routine execution time: USBPORT.SYS - USB 1.1 & 2.0 Port Driver, Microsoft Corporation
Highest reported total DPC routine time (%): 0.162781
Driver with highest DPC total execution time: rspLLL64.sys - Resplendence Latency Monitoring and Auxiliary Kernel Library, Resplendence Software Projects Sp.
Total time spent in DPCs (%) 0.350629
DPC count (execution time <250 µs): 731247
DPC count (execution time 250-500 µs): 0
DPC count (execution time 500-999 µs): 0
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.
Process with highest pagefault count: explorer.exe
Total number of hard pagefaults 15
Hard pagefault count of hardest hit process: 12
Highest hard pagefault resolution time (µs): 705.937925
Total time spent in hard pagefaults (%): 0.000363
Number of processes hit: 2
Click the ORB (Start) and type system in the Search box. In the Program group, select System Information. When the MSInfo screen comes up, expand Hardware Resources then click on IRQs. Wait for it to generate the list. This is all the hardware in your system that generate interrupts. You'll see there's quite a few so you can't eliminate them all. At least not without crashing.
yea, this keeps happening sporadically. so ill just leave it alone and maybe check it out again in a few months or so.