Questions & Answers

Any ideas why my Audiobox 1818 VSL appears to be causing high CPU usage (System Interrupt) activity in Windows 10?

0 votes
asked Jan 5, 2016 in AudioBox USB by ronnieboy (150 points)
I'm running Studio One Professional vs 3.1.1, AudioBox 1818VSL driver vs 1.3.5653, on my ASUS Desktop CG5653, Intel QuadCore i5 cpu 650 @ 3.2 Ghz, 8 G of Memory, running latest upgraded version (as of 1-5-2016) of Windows 10. I upgraded from Windows 7 only a few weeks ago, and didn't have these issues before. My CPU usage across all 4 cores is at a constant 100%, even at idle. I've watched in Task Manager as System Interrupts process is constantly very active (low 20's to low 60's % cpu usage - and even higher at some spikes) and through process of elimination the source appears to be my 1818VSL. Another possibly related high cpu usage activity happening is Windows Audio Device Graph Isolation (audiodg.exe) with very similar constantly high cpu percentage readings. I honestly don't know that my 100% cpu readings are due solely to the high System Interrupt and audiodg.exe activity, but nothing else is acting so suspiciously that I can see.

I am an extremely happy and loyal Presonus fan. LOVE my Presonus stuff! Please tell me, are there any known issues with Windows 10 and AudioBox 1818VSL that sound like these problems I'm having? If so, any solutions? Thanks!

2 Answers

0 votes
answered Jan 6, 2016 by mattcaprio (148,110 points)
selected May 5, 2016 by mattcaprio
Best answer
This sounds like an IRQ conflict.

Try connecting the 1818 to different ports. Some may perform better than others.

If that does not fix the issue it would be best to create a support ticket and send tech support your system information file.
0 votes
answered Jan 5, 2016 by gadget69 (30,300 points)

Not sure if this answers your question:

But there was a great deal of activity on this subject on the Old forum...The Issues were, as I recall, only there for Intel i processors. I have posted a question to the gang @ Presonus but haven't received an answer yet.