PlanetZ forums - scopeusers.com

Hello,

I'm using a 3 DSP Scope v7 card on a new vanilla Windows 10 installation. Everything works well, super-low latency and no ASIO spikes.

But despite I've done all OS and BIOS tweaks, still there's 'now and then' audio clicks. Not often but sometimes one per minute, sometimes 2-3 per minute.

I'm suspecting something odd in the PCI bus and bridge lane. First, I'm not sure if I shall set a fixed PCI bus frequency in the BIOS?

The LatencyMon is all green, although the hardest pagefaults are related to dxgkrnl.sys and nvlddmk.sys drivers.

Any help would be highly appreciated.

This is the LatencyMon report:

_________________________________________________________________________________________________________
CONCLUSION
_________________________________________________________________________________________________________
Your system appears to be suitable for handling real-time audio and other tasks without dropouts.
LatencyMon has been analyzing your system for 0:04:22 (h:mm:ss) on all processors.


_________________________________________________________________________________________________________
SYSTEM INFORMATION
_________________________________________________________________________________________________________
Computer name: RETEE
OS version: Windows 10 , 10.0, build: 18363 (x64)
Hardware: EX58-UD4, Gigabyte Technology Co., Ltd.
CPU: GenuineIntel Intel(R) Core(TM) i7 CPU 950 @ 3.07GHz
Logical processors: 4
Processor groups: 1
RAM: 14334 MB total


_________________________________________________________________________________________________________
CPU SPEED
_________________________________________________________________________________________________________
Reported CPU speed: 3064 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): 157,10
Average measured interrupt to process latency (µs): 2,730495

Highest measured interrupt to DPC latency (µs): 154,60
Average measured interrupt to DPC latency (µs): 0,910812


_________________________________________________________________________________________________________
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): 75,549608
Driver with highest ISR routine execution time: dxgkrnl.sys - DirectX Graphics Kernel, Microsoft Corporation

Highest reported total ISR routine time (%): 0,086381
Driver with highest ISR total time: dxgkrnl.sys - DirectX Graphics Kernel, Microsoft Corporation

Total time spent in ISRs (%) 0,239201

ISR count (execution time <250 µs): 596223
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): 425,390339
Driver with highest DPC routine execution time: nvlddmkm.sys - NVIDIA Windows Kernel Mode Driver, Version 432.00 , NVIDIA Corporation

Highest reported total DPC routine time (%): 0,176147
Driver with highest DPC total execution time: ScopePci.sys - Scope PCI WDM Adapter Driver, Sonic Core GmbH, Germany

Total time spent in DPCs (%) 0,385529

DPC count (execution time <250 µs): 727135
DPC count (execution time 250-500 µs): 0
DPC count (execution time 500-999 µs): 41
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: explorer.exe

Total number of hard pagefaults 28
Hard pagefault count of hardest hit process: 22
Number of processes hit: 3


_________________________________________________________________________________________________________
PER CPU DATA
_________________________________________________________________________________________________________
CPU 0 Interrupt cycle time (s): 8,226266
CPU 0 ISR highest execution time (µs): 75,549608
CPU 0 ISR total execution time (s): 2,504865
CPU 0 ISR count: 595616
CPU 0 DPC highest execution time (µs): 425,390339
CPU 0 DPC total execution time (s): 3,998255
CPU 0 DPC count: 716607
_________________________________________________________________________________________________________
CPU 1 Interrupt cycle time (s): 0,516184
CPU 1 ISR highest execution time (µs): 7,835509
CPU 1 ISR total execution time (s): 0,002260
CPU 1 ISR count: 607
CPU 1 DPC highest execution time (µs): 40,206266
CPU 1 DPC total execution time (s): 0,018316
CPU 1 DPC count: 4662
_________________________________________________________________________________________________________
CPU 2 Interrupt cycle time (s): 0,512485
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): 56,925587
CPU 2 DPC total execution time (s): 0,013343
CPU 2 DPC count: 3363
_________________________________________________________________________________________________________
CPU 3 Interrupt cycle time (s): 0,512828
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): 59,548303
CPU 3 DPC total execution time (s): 0,010905
CPU 3 DPC count: 2544
_________________________________________________________________________________________________________

Per CPU data looks like your CPU is spending a lot of time sleeping its cores. Are you running Scope 7 while under a low CPU load for testing, and do you find clicks go away when your processor usage exceeds 50%? This causes issues even for native machines...placing an artificial load is the easiest way to see if this goes away under higher usage.

Also look for scope4live's post about locking the ASIO driver to (if I recall) dsp2 so it doesn't load anywhere else.

----

Those would be the first 2 things I would check out before doing anything exotic.

are you sure that EIST is disabled in the bios, and that the CPU is set to 100% minimum and maximum in the power settings?

have you opened the Task Manager and watch for processes that are using a lot of cpu cycles(details)?

did you disable and then remove One Drive? is Cortana disabled?

valis wrote: Sun Jan 19, 2020 6:52 am Are you running Scope 7 while under a low CPU load for testing, and do you find clicks go away when your processor usage exceeds 50%? This causes issues even for native machines...placing an artificial load is the easiest way to see if this goes away under higher usage.

Tested both scenarios with a dedicated project file, no change.
The problem occurs both in a DAW sequencer and a standalone.

if you have clicks, it is either a cpu overrun(even momentarily), background apps running, a clock issue between digital hardware, or power management issues.

if it's a PCI buss issue, the only way to solve it is another motherboard/processor. that's damned unlikely to be the case.

again-

are you sure that EIST is disabled in the bios, and that the CPU is set to 100% minimum and maximum in the power settings? here is the "proof" that there is likely to be a power management issue

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.

have you opened the Task Manager and watch for processes that are using a lot of cpu cycles(details)?

did you disable and then remove One Drive? is Cortana disabled?

there should NOT be a need to do anything extreme.

valis wrote: Sun Jan 19, 2020 6:52 am Also look for scope4live's post about locking the ASIO driver to (if I recall) dsp2 so it doesn't load anywhere else.

There's no 'Assign to DSP' dialog in my Scope v7 environment as I'm using the 3 DSP audio card.

garyb wrote: Sun Jan 19, 2020 8:06 am are you sure that EIST is disabled in the bios, and that the CPU is set to 100% minimum and maximum in the power settings?

Yes x 2.

garyb wrote: Sun Jan 19, 2020 4:33 pm have you opened the Task Manager and watch for processes that are using a lot of cpu cycles(details)?
did you disable and then remove One Drive?

Yes, only Cubase is taking 5-7% CPU, all other stuff under 1% CPU utilization. No sudden spikes.

One Drive disabled, not sure what do you mean with 'remove'? It is a Win 10 core component? Can it be removed?

it can be completely deactivated. check google "remove one drive windows 10".

no turbo or hyperthreading?

why does latencymon report that the cpu is operating at "a fraction" if it's reported speed? is it overheating? this is the most likely place that the clicks are coming from.

were you looking at the "details" tab in the Task Manager, and not the "processes" tab?

are there any digital hardware connections?

the socket 1366 systems generally worked well, and have never required special treatment.

Latencymon screen.

i don't have any special trust in latencymon. it's most useful when people are operating at the ragged edge. it should be not necessary for most systems. as i said, you should not need to do anything tricky.

what vsts are running?

garyb wrote: Sun Jan 19, 2020 5:18 pm no turbo or hyperthreading?

Double checked, disabled in BIOS.

garyb wrote: Sun Jan 19, 2020 5:18 pm were you looking at the "details" tab in the Task Manager, and not the "processes" tab?

Yes, please check attached image.

garyb wrote: Sun Jan 19, 2020 5:24 pm what vsts are running?

Tested with Korg KCL, Arturia V7, GF ImpOscar, VPS Avenger etc. Same result. Will try to remove OneDrive and Cortana. I will be back in a couple of minutes.

garyb wrote: Sun Jan 19, 2020 4:33 pm if you have clicks, it is either a cpu overrun(even momentarily), background apps running, a clock issue between digital hardware, or power management issues.

if it's a PCI buss issue, the only way to solve it is another motherboard/processor. that's damned unlikely to be the case.

again-

are you sure that EIST is disabled in the bios, and that the CPU is set to 100% minimum and maximum in the power settings? here is the "proof" that there is likely to be a power management issue

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.

have you opened the Task Manager and watch for processes that are using a lot of cpu cycles(details)?

did you disable and then remove One Drive? is Cortana disabled?

there should NOT be a need to do anything extreme.

Ok, please check the attached BIOS state images. Please tell me if you find anything odd.

garyb wrote: Sun Jan 19, 2020 5:18 pm why does latencymon report that the cpu is operating at "a fraction" if it's reported speed? is it overheating? this is the most likely place that the clicks are coming from.

Not sure why it shows that as the CPU is running fine within 30c-40c, no overheating.

garyb wrote: Sun Jan 19, 2020 8:06 am did you disable and then remove One Drive? is Cortana disabled?

Yes, both uninstalled, but still, the audio clicks are present. Frustrating, but I guess it may be some non-standard issue?
On the other hand, the same hardware config uses to work well will Scope V5 and Windows 7.

Does this mean that you used all of these at once to place a full CPU load (or at least higher than 50%)?

Again, if you're running 5-7% CPU, the cores are going to keep sleeping. This can be overridden in bios or with custom power profiles (setting windows to 100% cpu in power plan no longer seems to do the trick, you can find information on Gearslutz.com about this). When cores sleep, the 'active' load gets shifted between cores and that's why you see such large DPC calls on the CPU scheduling list in your first data paste.

CreamWare4Ever wrote: Sun Jan 19, 2020 5:50 pm

garyb wrote: Sun Jan 19, 2020 5:24 pm what vsts are running?

Tested with Korg KCL, Arturia V7, GF ImpOscar, VPS Avenger etc. Same result. Will try to remove OneDrive and Cortana. I will be back in a couple of minutes.

valis wrote: Sun Jan 19, 2020 6:47 pm Does this mean that you used all of these at once to place a full CPU load (or at least higher than 50%)?

Yes, the CPU utilization bounces between 30%-50% in the task manager.