bump

Is the “lost ASIO buffer” something Samplitude is reporting??? (Maybe like this thread: http://www.gearslutz.com/board/so-much- … itude.html )

Hard page faults are normal. Lots of applications start using their DLL’s via svchost.exe, which is a part of the OS and therefore cannot be disabled.
Read through the documentation carefully (http://www.resplendence.com/latencymon_using ):

“The difficulty with pagefaults is that they are common to occur so it's hard to find out if they are the cause of audio dropouts and stutter. In order to find out if pagefaults are the cultprit you need to know that the pagefault occured in the process responsible for producing audio and also while it was producing audio.”

I have page faults off the chart on the LatencyMon trace, but this is NOT the cause of my artifacts (it turned out to be a faulty video driver that was causing high DPC execution times). A more in-depth (but much more complex) method of analyzing your system is to use the Microsoft Windows SDK tools (http://www.msfn.org/board/topic/140263- … interrupt/).

Have you tried a different host than Samplitude to see if recording problems occur with other pro-audio hosts?

Try setting Samplitude's priority higher. There is an option hidden somewhere in ST's preferences. Does that help?

Hotkey y, System Options, Performance. I wouldn't call that 'hidden', though.