PlanetZ forums - scopeusers.com

big issues with pops and clicks. I am pulling my hair out.
Windows 7 64,Scope 5.1 64 and Xite-1d
I made all the bios changes and setup windows tweaks that I can find e.g. http://www.hitfoundry.com/issue_11/tsg_mast.htm thanks Dante!
I have a Gigabyte Ga-970 ud3 ver 1.1 motherboared with 6 core amd+ cpu and 8 gigs of ram.
As pictures speak louder then words here are my bios and irq settings. I have ran the latencyMon app and it goes into the red even before I start scope 5.1 and Abelton live! Any ideas ? I did disable the on board HD audio device on irq 19

Check the "stats" button. It'll make a report, the tells you what is the worst offender. If you paste that in your post, we can take a look.

(be sure to run it for long enough to capture the issue, and then click stop before cut &paste)

Thanks JKSuperstar


ran it for 10 min plus

_________________________________________________________________________________________________________
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:11:26 (h:mm:ss) on all processors.


_________________________________________________________________________________________________________
SYSTEM INFORMATION
_________________________________________________________________________________________________________
Computer name: SHOGUNSPY-PC
OS version: Windows 7 Service Pack 1, 6.1, build: 7601 (x64)
Hardware: GA-970A-UD3, Gigabyte Technology Co., Ltd.
CPU: AuthenticAMD AMD FX(tm)-6100 Six-Core Processor
Logical processors: 6
Processor groups: 1
RAM: 8189 MB total


_________________________________________________________________________________________________________
CPU SPEED
_________________________________________________________________________________________________________
Reported CPU speed: 3322.0 MHz
Measured CPU speed: 2619.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): 27173.894618
Average measured interrupt to process latency (µs): 5.957804

Highest measured interrupt to DPC latency (µs): 372.321129
Average measured interrupt to DPC latency (µs): 1.836380


_________________________________________________________________________________________________________
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): 197.317881
Driver with highest ISR routine execution time: ataport.SYS - ATAPI Driver Extension, Microsoft Corporation

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

Total time spent in ISRs (%) 0.052860

ISR count (execution time <250 µs): 784305
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): 317.256472
Driver with highest DPC routine execution time: ndis.sys - NDIS 6.20 driver, Microsoft Corporation

Highest reported total DPC routine time (%): 0.087348
Driver with highest DPC total execution time: USBPORT.SYS - USB 1.1 & 2.0 Port Driver, Microsoft Corporation

Total time spent in DPCs (%) 0.292378

DPC count (execution time <250 µs): 3740721
DPC count (execution time 250-500 µs): 0
DPC count (execution time 500-999 µs): 4
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: iexplore.exe

Total number of hard pagefaults 21408
Hard pagefault count of hardest hit process: 6973
Highest hard pagefault resolution time (µs): 1003651.366045
Total time spent in hard pagefaults (%): 2.998107
Number of processes hit: 19


_________________________________________________________________________________________________________
PER CPU DATA
_________________________________________________________________________________________________________
CPU 0 Interrupt cycle time (s): 17.910117
CPU 0 ISR highest execution time (µs): 45.917821
CPU 0 ISR total execution time (s): 1.431937
CPU 0 ISR count: 619601
CPU 0 DPC highest execution time (µs): 317.256472
CPU 0 DPC total execution time (s): 5.542507
CPU 0 DPC count: 3021622
_________________________________________________________________________________________________________
CPU 1 Interrupt cycle time (s): 7.728395
CPU 1 ISR highest execution time (µs): 197.317881
CPU 1 ISR total execution time (s): 0.124129
CPU 1 ISR count: 28154
CPU 1 DPC highest execution time (µs): 154.299819
CPU 1 DPC total execution time (s): 0.878817
CPU 1 DPC count: 98176
_________________________________________________________________________________________________________
CPU 2 Interrupt cycle time (s): 9.068849
CPU 2 ISR highest execution time (µs): 32.353703
CPU 2 ISR total execution time (s): 0.124116
CPU 2 ISR count: 28591
CPU 2 DPC highest execution time (µs): 111.101746
CPU 2 DPC total execution time (s): 1.579035
CPU 2 DPC count: 160854
_________________________________________________________________________________________________________
CPU 3 Interrupt cycle time (s): 8.943715
CPU 3 ISR highest execution time (µs): 55.851294
CPU 3 ISR total execution time (s): 0.242829
CPU 3 ISR count: 50685
CPU 3 DPC highest execution time (µs): 243.470199
CPU 3 DPC total execution time (s): 1.679725
CPU 3 DPC count: 166133
_________________________________________________________________________________________________________
CPU 4 Interrupt cycle time (s): 7.272455
CPU 4 ISR highest execution time (µs): 45.768513
CPU 4 ISR total execution time (s): 0.129977
CPU 4 ISR count: 29830
CPU 4 DPC highest execution time (µs): 163.575256
CPU 4 DPC total execution time (s): 1.543742
CPU 4 DPC count: 206907
_________________________________________________________________________________________________________
CPU 5 Interrupt cycle time (s): 8.331691
CPU 5 ISR highest execution time (µs): 32.032511
CPU 5 ISR total execution time (s): 0.124745
CPU 5 ISR count: 27444
CPU 5 DPC highest execution time (µs): 235.279049
CPU 5 DPC total execution time (s): 0.821663
CPU 5 DPC count: 87033
_________________________________________________________________________________________________________

thanks :0

Looks like something is up with a SATA bus. ATAPI is the ATA driver, aka Serial ATA, aka SATA.

Disable any unused SATA ports, and see what conflicts there are in your system with used SATA drivers. If you are streaming audio/samples, it's access to these streams that's likely part of the issue.

I would guess the CD/DVD is part of the issue, but that's just a gut feeling. Driver updates, or checking the BIOS to make sure it is in a good mode like UDMA (not forced into Mode 0-6, or PIO modes)...this should be true for ALL of your drives.

[edit - just had a flashback. One quick thing to try is put a CD/DVD in your drive...I remember some controllers had an issue supporting SATA connected DVD drives, and would ping the drive to keep it alive, but the fact there was no disk in it made the whole idea be detrimental...the fix is trying a different port or keeping a CD in the drive]

Some USB device or other is chewing a bit too...

Try disconnecting all your USB devices, restarting, and running a test again. Use a PS2 mouse and keyboard (if that's an option). Then see if the problem disappears.

You can also try disabling your Swap File - it may or may not help.

Looks like you have a few bits sharing IRQ with Scope - Did you work thru how to isolate what devices to disable in my posts here:
http://forums.planetz.com/viewtopic.php?f=1&t=32257
(I know you were active on this thread, but there's a bit you can do here yet,to disable devices in device manager, the ones that share IRQ with Scope).

thanks dudes will try these tips this evening.

ok I ran it a bit longer here

________________________________________________________________________________________________________
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:17:52 (h:mm:ss) on all processors.


_________________________________________________________________________________________________________
SYSTEM INFORMATION
_________________________________________________________________________________________________________
Computer name: SHOGUNSPY-PC
OS version: Windows 7 Service Pack 1, 6.1, build: 7601 (x64)
Hardware: GA-970A-UD3, Gigabyte Technology Co., Ltd.
CPU: AuthenticAMD AMD FX(tm)-6100 Six-Core Processor
Logical processors: 6
Processor groups: 1
RAM: 8189 MB total


_________________________________________________________________________________________________________
CPU SPEED
_________________________________________________________________________________________________________
Reported CPU speed: 3322.0 MHz
Measured CPU speed: 2664.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): 6722.840335
Average measured interrupt to process latency (µs): 3.896377

Highest measured interrupt to DPC latency (µs): 173.834676
Average measured interrupt to DPC latency (µs): 1.989826


_________________________________________________________________________________________________________
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): 196.381397
Driver with highest ISR routine execution time: ataport.SYS - ATAPI Driver Extension, Microsoft Corporation

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

Total time spent in ISRs (%) 0.051715

ISR count (execution time <250 µs): 1275959
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): 1484.230885
Driver with highest DPC routine execution time: ndis.sys - NDIS 6.20 driver, Microsoft Corporation

Highest reported total DPC routine time (%): 0.078381
Driver with highest DPC total execution time: USBPORT.SYS - USB 1.1 & 2.0 Port Driver, Microsoft Corporation

Total time spent in DPCs (%) 0.240996

DPC count (execution time <250 µs): 5758833
DPC count (execution time 250-500 µs): 0
DPC count (execution time 500-999 µs): 2
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 22414
Hard pagefault count of hardest hit process: 6478
Highest hard pagefault resolution time (µs): 1040665.399157
Total time spent in hard pagefaults (%): 1.935189
Number of processes hit: 20


_________________________________________________________________________________________________________
PER CPU DATA
_________________________________________________________________________________________________________
CPU 0 Interrupt cycle time (s): 21.543858
CPU 0 ISR highest execution time (µs): 196.381397
CPU 0 ISR total execution time (s): 2.271795
CPU 0 ISR count: 1034935
CPU 0 DPC highest execution time (µs): 1484.230885
CPU 0 DPC total execution time (s): 6.991750
CPU 0 DPC count: 4948675
_________________________________________________________________________________________________________
CPU 1 Interrupt cycle time (s): 13.190275
CPU 1 ISR highest execution time (µs): 145.082480
CPU 1 ISR total execution time (s): 0.180121
CPU 1 ISR count: 42097
CPU 1 DPC highest execution time (µs): 116.508730
CPU 1 DPC total execution time (s): 1.069247
CPU 1 DPC count: 96942
_________________________________________________________________________________________________________
CPU 2 Interrupt cycle time (s): 15.227649
CPU 2 ISR highest execution time (µs): 46.478025
CPU 2 ISR total execution time (s): 0.179942
CPU 2 ISR count: 41984
CPU 2 DPC highest execution time (µs): 185.705298
CPU 2 DPC total execution time (s): 2.282513
CPU 2 DPC count: 225837
_________________________________________________________________________________________________________
CPU 3 Interrupt cycle time (s): 15.22320
CPU 3 ISR highest execution time (µs): 69.385310
CPU 3 ISR total execution time (s): 0.186218
CPU 3 ISR count: 43627
CPU 3 DPC highest execution time (µs): 118.320891
CPU 3 DPC total execution time (s): 2.387331
CPU 3 DPC count: 229837
_________________________________________________________________________________________________________
CPU 4 Interrupt cycle time (s): 14.078121
CPU 4 ISR highest execution time (µs): 52.620409
CPU 4 ISR total execution time (s): 0.329592
CPU 4 ISR count: 72013
CPU 4 DPC highest execution time (µs): 261.640277
CPU 4 DPC total execution time (s): 1.833171
CPU 4 DPC count: 168064
_________________________________________________________________________________________________________
CPU 5 Interrupt cycle time (s): 13.646784
CPU 5 ISR highest execution time (µs): 146.899759
CPU 5 ISR total execution time (s): 0.178887
CPU 5 ISR count: 41303
CPU 5 DPC highest execution time (µs): 133.958760
CPU 5 DPC total execution time (s): 0.938073
CPU 5 DPC count: 89481
_________________________________________________________________________________________________________

So I am not sure how to shut down sata ports ? in bios I can not see any options to do so. will download manual tonight
Tried the DVD/cd trick no luck
Irq shares I can not see any hex values for some reason so I can not pin point I have a usb mouse a keybord and abelton push will remove Push and get a PS2 Keyboard next

Hi, try switching off swap file on your drives too..

this shouldn't be so hard.

if it is, then there's something seriously wrong with the computer's hardware, or software or both.

there is no need to shut off any usb controllers, nor should you need to kill sata controllers. your XITE is not sharing an irq with anby of those things. if you want to play around with that, you can do it in the device manager. personally, i wouldn't go too many steps forward if i didn't understand how these things work.

if you've done all the things on ScopeRise or here http://forums.planetz.com/viewtopic.php?f=3&t=31345 and you still have clicks, it's either the workload the cpu is under, or it could be the threading problem that 6core AMDs often seem to have. first, have you disabled Cool N Quiet , Core Performance Boost(CPB and anything related to it) and CE1 support? if not you will get clicks because the system is underpowering the cpu until the workload demands more processing, then the cpu is powered up in steps. this makes a audio stream click. you need the cpu at full power at all times. dusabling those settings will fully power the cpu. it's tricky because the name makes it sound like it's adding power to the system, when it's only saving electricity.

what is running in the sequencer, exactly, whe you are getting clicks? what is the latency(ULLI) setting?

Garyb's suggestions are spot on (of course).

But while USB is not sharing IRQ with Scope, a high DPC latency on USB driver will definitely not help here...

Two things to do now:
- Switch off all Power Management features in the BIOS and in Windows Power Management
- Disable the HD Audio (onboard audio) device that's sharing IRQ with Xite.

The number and slow speeds of Hard Page Faults looks suspcious too... First, minimise the number of unnecessary programs running by working thru msconfig.exe to stop Autostart Programs, and the Services Control Panel to disable unnecessary Services (check blackviper's list of services, in google). Restart your system, make sure stuff is working fine. Then, do try disabling the Page File too - so long as you have enough native RAM to log in and load your user profile, you can run your tests again with no Page File, and see if that makes a difference.
You may decide to use a fast storage mechanism (e.g. fast-rpm HD or an SSD) for your Page File and TEMP scratch area at some point too - but that'd only be working around some deeper problem with your main HD....

Check your current Motherboard BIOS version too, and check your Motherboard manufacturer's site to see if later BIOS Firmware updates might address some specific problem - but be sure to back up all your stuff before you ever take the decision to flash your BIOS firmware!

And if you're making deep Windows setting changes, make sure you create a named Restore Point now.

Take your time with this, research what you don't understand, and if you're not sure about something, post back here before you action it...

Eanna I have tried all the above except the black viper service tweaks page file and all

Gary I load up Scope first then Abelton Live. I just use midi and play minimax If I make any cc settings like cutoff I get a click and breakup of sound. I am running 34ms ulli! In fact once I start Scope will LatencyMon is running it goes in to red

Highest measured interrupt to process latency (µs): 7071.041125
Average measured interrupt to process latency (µs): 5.258775

Highest measured interrupt to DPC latency (µs): 164.277958
Average measured interrupt to DPC latency (µs): 1.985536


_________________________________________________________________________________________________________
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): 439.970801
Driver with highest ISR routine execution time: ataport.SYS - ATAPI Driver Extension, Microsoft Corporation

Highest reported total ISR routine time (%): 0.007729
Driver with highest ISR total time: ataport.SYS - ATAPI Driver Extension, Microsoft Corporation

Total time spent in ISRs (%) 0.016781

ISR count (execution time <250 µs): 215065
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): 205.676099
Driver with highest DPC routine execution time: ataport.SYS - ATAPI Driver Extension, Microsoft Corporation

Highest reported total DPC routine time (%): 0.024547
Driver with highest DPC total execution time: scopexite.sys - Scope XITE-1 WDM Adapter Driver, Sonic Core

Total time spent in DPCs (%) 0.088995

DPC count (execution time <250 µs): 831483
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.

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: scope.exe

Total number of hard pagefaults 7948
Hard pagefault count of hardest hit process: 2945
Highest hard pagefault resolution time (µs): 1167611.815172
Total time spent in hard pagefaults (%): 1.667342
Number of processes hit: 17


_________________________________________________________________________________________________________
PER CPU DATA
_________________________________________________________________________________________________________
CPU 0 Interrupt cycle time (s): 3.957415
CPU 0 ISR highest execution time (µs): 38.368754
CPU 0 ISR total execution time (s): 0.379330
CPU 0 ISR count: 110986
CPU 0 DPC highest execution time (µs): 205.676099
CPU 0 DPC total execution time (s): 1.832139
CPU 0 DPC count: 473145
_________________________________________________________________________________________________________
CPU 1 Interrupt cycle time (s): 1.398766
CPU 1 ISR highest execution time (µs): 31.868152
CPU 1 ISR total execution time (s): 0.074463
CPU 1 ISR count: 19324
CPU 1 DPC highest execution time (µs): 147.551475
CPU 1 DPC total execution time (s): 0.403564
CPU 1 DPC count: 45022
_________________________________________________________________________________________________________
CPU 2 Interrupt cycle time (s): 1.501494
CPU 2 ISR highest execution time (µs): 30.505117
CPU 2 ISR total execution time (s): 0.085067
CPU 2 ISR count: 21541
CPU 2 DPC highest execution time (µs): 177.696869
CPU 2 DPC total execution time (s): 0.480243
CPU 2 DPC count: 56543
_________________________________________________________________________________________________________
CPU 3 Interrupt cycle time (s): 1.348016
CPU 3 ISR highest execution time (µs): 30.658940
CPU 3 ISR total execution time (s): 0.093636
CPU 3 ISR count: 24249
CPU 3 DPC highest execution time (µs): 168.158338
CPU 3 DPC total execution time (s): 0.506038
CPU 3 DPC count: 87548
_________________________________________________________________________________________________________
CPU 4 Interrupt cycle time (s): 1.751161
CPU 4 ISR highest execution time (µs): 439.970801
CPU 4 ISR total execution time (s): 0.074339
CPU 4 ISR count: 19414
CPU 4 DPC highest execution time (µs): 78.431367
CPU 4 DPC total execution time (s): 0.517183
CPU 4 DPC count: 125075
_________________________________________________________________________________________________________
CPU 5 Interrupt cycle time (s): 1.402495
CPU 5 ISR highest execution time (µs): 28.118302
CPU 5 ISR total execution time (s): 0.074368
CPU 5 ISR count: 19552
CPU 5 DPC highest execution time (µs): 189.379591
CPU 5 DPC total execution time (s): 0.403746
CPU 5 DPC count: 44150
_________________________________________________________________________________________________________

get this I disabled 4 prossesors in Bios and still the same? I should have gone intel


Computer name: SHOGUNSPY-PC
OS version: Windows 7 Service Pack 1, 6.1, build: 7601 (x64)
Hardware: GA-970A-UD3, Gigabyte Technology Co., Ltd.
CPU: AuthenticAMD AMD FX(tm)-6100 Six-Core Processor
Logical processors: 2
Processor groups: 1
RAM: 8189 MB total


_________________________________________________________________________________________________________
CPU SPEED
_________________________________________________________________________________________________________
Reported CPU speed: 3322.0 MHz
Measured CPU speed: 2682.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): 6989.894719
Average measured interrupt to process latency (µs): 3.787446

Highest measured interrupt to DPC latency (µs): 109.722762
Average measured interrupt to DPC latency (µs): 1.366770


_________________________________________________________________________________________________________
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): 17.097532
Driver with highest ISR routine execution time: ataport.SYS - ATAPI Driver Extension, Microsoft Corporation

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

Total time spent in ISRs (%) 0.010664

ISR count (execution time <250 µs): 38147
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): 79.517459
Driver with highest DPC routine execution time: ntoskrnl.exe - NT Kernel & System, Microsoft Corporation

Highest reported total DPC routine time (%): 0.012813
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.038727

DPC count (execution time <250 µs): 173589
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.

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 41
Hard pagefault count of hardest hit process: 29
Highest hard pagefault resolution time (µs): 183622.040939
Total time spent in hard pagefaults (%): 0.041595
Number of processes hit: 4


_________________________________________________________________________________________________________
PER CPU DATA
_________________________________________________________________________________________________________
CPU 0 Interrupt cycle time (s): 0.581540
CPU 0 ISR highest execution time (µs): 17.097532
CPU 0 ISR total execution time (s): 0.065972
CPU 0 ISR count: 32138
CPU 0 DPC highest execution time (µs): 79.517459
CPU 0 DPC total execution time (s): 0.249821
CPU 0 DPC count: 162988
_________________________________________________________________________________________________________
CPU 1 Interrupt cycle time (s): 0.280447
CPU 1 ISR highest execution time (µs): 15.621011
CPU 1 ISR total execution time (s): 0.029007
CPU 1 ISR count: 6009
CPU 1 DPC highest execution time (µs): 75.059904
CPU 1 DPC total execution time (s): 0.095113
CPU 1 DPC count: 10601
_________________________________________________________________________________________________________

i don't care about those numbers.

if the computer is normally setup, this won't happen. i'd rather start from scratch, but first-
where are the pops and clicks coming from? are they recorded? is it the minimax itself making clicks? if so, how is the card connected to the world? please attach a screenshot of your routing window.

is the Scope card the only soundcard being used?

your description of what is happening is incomplete. clicks might be from the cpu, from another device, from a digital connection, from clipping, many places. just doing things randomly will only make you chase your tail. did you do the bios changes i toild you to make? they are absolutely required for realtime audio.

Yeah, have to be careful you don't end up using a sledge hammer to kill a fly.

Is Xite set up as host or slave clock?

Try adjusting the buffer settings in Ableton.

Gotta find a balance between ULLI and Ableton buffer setting.

G

siriusbliss wrote:Yeah, have to be careful you don't end up using a sledge hammer to kill a fly.

yes :0 its hard not to get mad
Scope is slave ! will try buffers

Gary its when I play synths live from Abelton to scope no audio being played. If I adjust cutoff I will get a pop/break up in audio as well if I play a track that I hve made in Abelton with its instruments I get the sae break up in audio.
I have disabled c states and quite and cool see photos of bios above, theirs not much info for AMD..maybe that's a clue that AMD is shit
I made all the changes in http://www.hitfoundry.com/issue_11/tsg_mast.htm http://www.hitfoundry.com/issue_17/pc_setup.htm
I only have an Abelton Push controller a usb mouse/ps2 keybored and a firewire glyph drive connected I have a ssd with page file off

You said you did all those things I suggested - switching off the page file and disabling the on board audio - but in these tests, they are still enabled..

You also said its cc changes that causes clicks - a sustained note doesn't ? I would guess it does..

The hard page faults is far too high. With 8gig of ram and a 64bit os, you can definitely switch off page file.

Disconnect the FireWire drive too.
And set up the xite as the system audio too, with the wav source and dest devices. Does playing mp3 cause clicks?

Gary, while those numbers aren't interesting, these red spikes in latency Mon are definitely showing the effect of the problem.

Eanna that capture was before I turned Page file off! ..but please walk me through how to shut it down. this is the latest with page file off I think

EASURED 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): 15153.205678
Average measured interrupt to process latency (µs): 5.40860

Highest measured interrupt to DPC latency (µs): 331.333824
Average measured interrupt to DPC latency (µs): 1.734781


_________________________________________________________________________________________________________
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): 63.266105
Driver with highest ISR routine execution time: portcls.sys - Port Class (Class Driver for Port/Miniport Devices), Microsoft Corporation

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

Total time spent in ISRs (%) 0.036242

ISR count (execution time <250 µs): 762056
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): 343.756472
Driver with highest DPC routine execution time: netbt.sys - MBT Transport driver, Microsoft Corporation

Highest reported total DPC routine time (%): 0.088576
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.156292

DPC count (execution time <250 µs): 3647734
DPC count (execution time 250-500 µs): 0
DPC count (execution time 500-999 µs): 7
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: ableton live 9 standard.exe

Total number of hard pagefaults 901
Hard pagefault count of hardest hit process: 864
Highest hard pagefault resolution time (µs): 39833.400963
Total time spent in hard pagefaults (%): 0.029654
Number of processes hit: 6


_________________________________________________________________________________________________________
PER CPU DATA
_________________________________________________________________________________________________________
CPU 0 Interrupt cycle time (s): 20.171656
CPU 0 ISR highest execution time (µs): 51.647803
CPU 0 ISR total execution time (s): 1.489428
CPU 0 ISR count: 741443
CPU 0 DPC highest execution time (µs): 343.756472
CPU 0 DPC total execution time (s): 6.204438
CPU 0 DPC count: 3595241
_________________________________________________________________________________________________________
CPU 1 Interrupt cycle time (s): 9.208873
CPU 1 ISR highest execution time (µs): 63.266105
CPU 1 ISR total execution time (s): 0.098298
CPU 1 ISR count: 20613
CPU 1 DPC highest execution time (µs): 279.609272
CPU 1 DPC total execution time (s): 0.642533
CPU 1 DPC count: 52500
_________________________________________________________________________________________________________