I've run LatencyMon and have been reading all sorts of things about it. Yet I haven't found any mention of whether I should run it for a few hours by itself, or with Platinum opened but not recording or playing back, or while recording.
 
I get passing results unless I'm recording with Platinum. I have a drum loop setup with Superior Drummer and if I record Ivory as midi and also record the output of my mixer after a minute or so I get the failing grade from LatencyMon with this generic report:
 
"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."
 
The biggest problem seems to be with hard pagefaults. I'm trying to track down a problem with Platinum.
In the real world, I'm not getting any other dropouts except in rare instances. I can have lots of audio and midi tracks with lots of FX playing back or recording audio and no problem, no dropouts except rarely. Yet if I'm just sitting there playing my Ivory piano, the audio engine shuts off. And it happens very often, maybe every 10-20 min. It happens also during recording midi, never during playback.
 
Any suggestions on tracking this problem down?

I can run Sonar and Netflix and tons of other things on my PC and never go red in LatencyMon.
 
I can run it for hours without issue.
 
Click the Driver's tab and sort by Highest Execution time.
 
Tell us what the Driver Files are that are causing the issue.

gswitz
I can run Sonar and Netflix and tons of other things on my PC and never go red in LatencyMon.
 
I can run it for hours without issue.
 
Click the Driver's tab and sort by Highest Execution time.
 
Tell us what the Driver Files are that are causing the issue.

With Platinum open but no playback or recording. I see the DPC count for LatencyMon at the top with 39 million followed by USBPORT.SYS at 24 million, next is MOTU midi interface at 16 million, then ATAPORT.SYS down to 284,000.

For ISR count HAL.DLL tops the list followed by USBPORT.SYS, then ATAPORT.SYS

 
Here is an image showing the Highest Execution column. What are those values?
 

 
If your constraint is IO, you might check in the Windows Resource Monitor and see what that looks like during playback from the disk you keep your audio on.
 

Possible clues:
MOTU midi interface 16 million
Trouble when playing (or recording from) keyboard
 
Possible reason:
MIDI flooding, perhaps from a MIDI loop?
 
Does your MOTU do merging or any other processing (what model is it)? Is your controller configured to merge input with output? Is Sonar set to echo any MIDI back out?

bvideo
Possible clues:
MOTU midi interface 16 million
Trouble when playing (or recording from) keyboard
 
Possible reason:
MIDI flooding, perhaps from a MIDI loop?
 
Does your MOTU do merging or any other processing (what model is it)? Is your controller configured to merge input with output? Is Sonar set to echo any MIDI back out?

 
MOTU Fastlane 2x2, simple box with only 1 button for midi thru. The button is not pressed in, if it is pressed in then it won't send anything to the computer only to the midi out.
 
I have my Yamaha P200 keyboard controller midi out going to the MOTU midi in, the the USB goes to the computer and then Sonar. Then from Sonar to the out of the MOTU into an AKAI synth and SY77 synth and back into the P200, but the P200 midi merge is set to off.
 
I do have a MidiSport midi interface also and my Yamaha SY77 has a keyboard that I can play as a controller.

Here you go gswitz
 

 

 
I created the above by starting LatencyMon and then going to Platinum and hit record and played the piano, recording midi and audio for about 20 sec until I got the error message from LatencyMon. It recorded about a minute or so total. I hit stop. I then used the snipping tool to capture the latency Mon window.
 
For the Resource Monitor window I opened a song that had midi and audio and just hit play. My audio is recorded on the D HD. I wasn't able to figure out how to display the processes with disk activity. Let me know if you need that.

So, your USB Latency is a bit high. I'm curious which device is causing it.
 
You can trouble shoot this by starting latencymon and then try unplugging various USB things (including your mouse). Test to see if there is a particular device that is causing it to be high. You see mine is at .18 and yours is at .77.
 
I also noticed ataport.sys...
https://msdn.microsoft.com/en-us/library/windows/hardware/ff551332%28v=vs.85%29.aspx
 
Do you have a an older ATA drive in your system? Just curious.
 
I once had a mouse issue with a logitech mouse. I just had to download Logitech's driver and use that instead of using the default Windows driver which didn't have good latency specs.

If that report in post #7 was running for a minute, the usbport.sys execution time is 42 seconds. That's extreme.
Is it possible to create two different reports, one with playing keys and another without, with stats cleared at the beginning of each? Also, that latencymon report unfortunately doesn't seem to include an elapsed time, so it's up to the experimenter to log the time (unless it's on another page?). (By the way, you're using on-board usb, no adapter card, right?)

If it's really hard page faults, there's only one cure for that: adding memory. Unfortunately, you're running a 32-bit O/S, so your machine's already maxxed out on RAM.
 
There are still some things you can do to lighten the impact of page faults, though. First, make sure your paging device is not on the same physical drive as your audio files. If you have more than 2 disks, and the 3rd disk is reserved for audio, you can split the paging device across both of the remaining drives. And of course, if you're using sampled instruments the best thing you can do is freeze them.