New
#21
That usbport.sys may not be the problem, just throwing the user off. Latencymon program showed my recording system PC as having several problems that would cause audio problems, but I was not having any problems. DPC latency checker did not show any problems. I had run the Latency mon program just to see what it showed because of discussions on the Sonar recording forum.
Since it happens after the PC has been running for several days suggests one possibility could be a memory leak in a running program.
If it worked OK at one time and now does not and the user can't find the problem it may be time for a "clean" reinstall.
I think rebooting and not running 5 days straight is your solution.
You expect no leaks over a long up time with a version of Windows desktop OS? muhahahahaha
Hi guys sorry for my absence, have had problems accessing the site due to dns issues, anyhow i don't think i ever installed intel RST tbh and here's a fun kicker, i'm down from 5 days uptime to around 3 days for the damn dpc, ut seems to get worse and worse and i still can't figure out what the hell is causing it, if i only had some way to see if there's any program that are specificly putting load on certain drivers because that would help alot with diagnostics.
A clean install on a ~4 month old comp does not really seem to be correct... however i do agree with you that there might be a memory leak in a program but how the hell would i get to the bottom of what program it is?
Slapy, not sure on tracking memory leaks but here is a start to help
Memory Leak Troubleshooting
Here's my latencymon data, also attatched a txt file for drivers in hope that someone might see something.
____________________________________________________________________________________________________ _____
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 or more DPC routines that belong to a driver running in your system appear to be executing for too long. At least one detected problem appears to be network related. In case you are using a WLAN adapter, try disabling it to get better results. 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:01:39 (h:mm:ss) on all processors.
____________________________________________________________________________________________________ _____
SYSTEM INFORMATION
____________________________________________________________________________________________________ _____
Computer name: SLAPPY-DATOR
OS version: Windows 7 Service Pack 1, 6.1, build: 7601 (x64)
Hardware: MS-7752, MSI, Z77A-S01 (MS-7752)
CPU: GenuineIntel Intel(R) Core(TM) i7-3770K CPU @ 3.50GHz
Logical processors: 8
Processor groups: 1
RAM: 16333 MB total
____________________________________________________________________________________________________ _____
CPU SPEED
____________________________________________________________________________________________________ _____
Reported CPU speed: 3500,0 MHz
Measured CPU speed: 2391,0 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.
____________________________________________________________________________________________________ _____
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): 3170,835105
Average measured interrupt to process latency (µs): 2,893994
Highest measured interrupt to DPC latency (µs): 3167,909440
Average measured interrupt to DPC latency (µs): 1,702220
____________________________________________________________________________________________________ _____
MEASURED SMI, IPI AND CPU STALLS
____________________________________________________________________________________________________ _____
The SMI, IPI and CPU stalls value represents the highest measured interval that a CPU did not respond while having its maskable interrupts disabled.
Highest measured SMI or CPU stall (µs) 1,170266
____________________________________________________________________________________________________ _____
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): 67,5260
Driver with highest ISR routine execution time: ataport.SYS - ATAPI Driver Extension, Microsoft Corporation
Highest reported total ISR routine time (%): 0,028606
Driver with highest ISR total time: ataport.SYS - ATAPI Driver Extension, Microsoft Corporation
Total time spent in ISRs (%) 0,037984
ISR count (execution time <250 µs): 140767
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): 3869,971143
Driver with highest DPC routine execution time: USBPORT.SYS - USB 1.1 & 2.0 portdrivrutin, Microsoft Corporation
Highest reported total DPC routine time (%): 0,121646
Driver with highest DPC total execution time: USBPORT.SYS - USB 1.1 & 2.0 portdrivrutin, Microsoft Corporation
Total time spent in DPCs (%) 0,214136
DPC count (execution time <250 µs): 635692
DPC count (execution time 250-500 µs): 0
DPC count (execution time 500-999 µs): 0
DPC count (execution time 1000-1999 µs): 285
DPC count (execution time 2000-3999 µs): 181
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 17
Hard pagefault count of hardest hit process: 8
Highest hard pagefault resolution time (µs): 332,631429
Total time spent in hard pagefaults (%): 0,000294
Number of processes hit: 4
____________________________________________________________________________________________________ _____
PER CPU DATA
____________________________________________________________________________________________________ _____
CPU 0 Interrupt cycle time (s): 2,390774
CPU 0 ISR highest execution time (µs): 67,5260
CPU 0 ISR total execution time (s): 0,302152
CPU 0 ISR count: 140767
CPU 0 DPC highest execution time (µs): 3869,971143
CPU 0 DPC total execution time (s): 1,646014
CPU 0 DPC count: 608365
____________________________________________________________________________________________________ _____
CPU 1 Interrupt cycle time (s): 0,223695
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): 0,0
CPU 1 DPC total execution time (s): 0,0
CPU 1 DPC count: 0
____________________________________________________________________________________________________ _____
CPU 2 Interrupt cycle time (s): 0,249076
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): 66,476571
CPU 2 DPC total execution time (s): 0,012028
CPU 2 DPC count: 6894
____________________________________________________________________________________________________ _____
CPU 3 Interrupt cycle time (s): 0,221521
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): 0,0
CPU 3 DPC total execution time (s): 0,0
CPU 3 DPC count: 0
____________________________________________________________________________________________________ _____
CPU 4 Interrupt cycle time (s): 0,265636
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): 155,395714
CPU 4 DPC total execution time (s): 0,015333
CPU 4 DPC count: 7774
____________________________________________________________________________________________________ _____
CPU 5 Interrupt cycle time (s): 0,217682
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,282349
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): 128,414571
CPU 6 DPC total execution time (s): 0,024865
CPU 6 DPC count: 11085
____________________________________________________________________________________________________ _____
CPU 7 Interrupt cycle time (s): 0,21860
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): 59,3940
CPU 7 DPC total execution time (s): 0,005170
CPU 7 DPC count: 2040
____________________________________________________________________________________________________ _____
Just here to post a little update, done some more research regarding this problem but nothing has worked so far, the memory leak does not seem to be the problem either seeing as how i have more memory then i can actually use in this setup that i have :/ .