Help with dropouts
Hi all,
I don't necessarily think I'm having a bug with Reaper, so please move if this is in the wrong location - first post.
I'm on Win 7, 64 Bit, using Yamaha N8 which has always been rock stable for me. I recently switched from Cubase to Reaper, and am now having dropouts during recording. I've tried various settings to optimize Windows and/or Reaper with no success.
I ran Latency Mon and it seems my system has some trouble but I don't know how I shoudl fix it. Here's the Report:
__________________________________________________ __________________________________________________ _____
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. 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:58 (h:mm:ss) on all processors.
__________________________________________________ __________________________________________________ _____
SYSTEM INFORMATION
__________________________________________________ __________________________________________________ _____
Computer name: RYAN-PC
OS version: Windows 7 Service Pack 1, 6.1, build: 7601 (x64)
Hardware: OptiPlex 755 , Dell Inc., 0GM819
CPU: GenuineIntel Intel(R) Core(TM)2 Quad CPU Q6600 @ 2.40GHz
Logical processors: 4
Processor groups: 1
RAM: 3965 MB total
__________________________________________________ __________________________________________________ _____
CPU SPEED
__________________________________________________ __________________________________________________ _____
Reported CPU speed: 2394 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.
__________________________________________________ __________________________________________________ _____
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): 3021.515035
Average measured interrupt to process latency (µs): 7.773601
Highest measured interrupt to DPC latency (µs): 843.919757
Average measured interrupt to DPC latency (µs): 2.290487
__________________________________________________ __________________________________________________ _____
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): 349.939850
Driver with highest ISR routine execution time: ataport.SYS - ATAPI Driver Extension, Microsoft Corporation
Highest reported total ISR routine time (%): 1.870227
Driver with highest ISR total time: ataport.SYS - ATAPI Driver Extension, Microsoft Corporation
Total time spent in ISRs (%) 2.793370
ISR count (execution time <250 µs): 12808053
ISR count (execution time 250-500 µs): 0
ISR count (execution time 500-999 µs): 1
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): 1764.409774
Driver with highest DPC routine execution time: ataport.SYS - ATAPI Driver Extension, Microsoft Corporation
Highest reported total DPC routine time (%): 4.675666
Driver with highest DPC total execution time: Wdf01000.sys - Kernel Mode Driver Framework Runtime, Microsoft Corporation
Total time spent in DPCs (%) 5.135066
DPC count (execution time <250 µs): 2782865
DPC count (execution time 250-500 µs): 0
DPC count (execution time 500-999 µs): 1
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: svchost.exe
Total number of hard pagefaults 17169
Hard pagefault count of hardest hit process: 15819
Highest hard pagefault resolution time (µs): 974996.824561
Total time spent in hard pagefaults (%): 16.715053
Number of processes hit: 16
__________________________________________________ __________________________________________________ _____
PER CPU DATA
__________________________________________________ __________________________________________________ _____
CPU 0 Interrupt cycle time (s): 19.381779
CPU 0 ISR highest execution time (µs): 63.496241
CPU 0 ISR total execution time (s): 5.236208
CPU 0 ISR count: 3334271
CPU 0 DPC highest execution time (µs): 376.616541
CPU 0 DPC total execution time (s): 11.256775
CPU 0 DPC count: 1386642
__________________________________________________ __________________________________________________ _____
CPU 1 Interrupt cycle time (s): 14.384418
CPU 1 ISR highest execution time (µs): 138.906015
CPU 1 ISR total execution time (s): 4.859163
CPU 1 ISR count: 3159022
CPU 1 DPC highest execution time (µs): 1764.409774
CPU 1 DPC total execution time (s): 7.861899
CPU 1 DPC count: 460855
__________________________________________________ __________________________________________________ _____
CPU 2 Interrupt cycle time (s): 17.477589
CPU 2 ISR highest execution time (µs): 81.210526
CPU 2 ISR total execution time (s): 5.094914
CPU 2 ISR count: 3157813
CPU 2 DPC highest execution time (µs): 171.879699
CPU 2 DPC total execution time (s): 9.535337
CPU 2 DPC count: 476082
__________________________________________________ __________________________________________________ _____
CPU 3 Interrupt cycle time (s): 15.153062
CPU 3 ISR highest execution time (µs): 349.939850
CPU 3 ISR total execution time (s): 4.755718
CPU 3 ISR count: 3156948
CPU 3 DPC highest execution time (µs): 198.650376
CPU 3 DPC total execution time (s): 8.012826
CPU 3 DPC count: 459288
__________________________________________________ __________________________________________________ _____
I appreciate any help, again please let me know if this post is out of line or in the wrong place. Thanks!
-R
|
Linear Mode
