HighAndDry
thanks  onboard video is a problem  hmmm

 
Not with a modern build...  
HD4600 GPU is fine for straight audio work.
If you're doing video editing, you'll want a dedicated (higher-end) video card.

Jim Roseberry
The problem is the motherboard.
Swap that out... and the OP's problems are gone.

Sorry I don't see how you can jump to that conclusion at all for audio work on the basis of this thread. You certainly would not expect to see the audio engine stopping even on a fairly minimum configuration. In a lot of cases you just reinstall windows clean from scratch if it's a big issue.

I've configured many machines straight from the factory and most of them just need tweaking before they can work efficiently. Most of the time it's all the junk that has been pre-installed. Often you need to update the drivers, bios and firmware as well.

Cheers..

I apologize, as I have just gotten a moment to sit down and read through the LatencyMon data.
"Wdf01000.sys - Kernel Mode Driver Framework Runtime, Microsoft Corporation" is one of the called functions I mentioned and that is the autodetect feature of wi-fi, to disable that one, see my post here. That is the #1 latency offender, and is simply the "autodetect" feature enabled, that is not hardware-related.
 
You probably also have core parking enabled. Here is a link for the quickest way to disable (registry edit), and a video for checking/disabling can be found here.
 
A general post I made when I rebuilt my machine (which includes the above) can be found here. I was going to make up a detailed "tweak list" of what I did when I rebuilt this machine, but that was the closest I came to it.
 
 

Thanks to everyone who has t4ried to help!! I really appreciate all the input.  I am probably going to return the motherboard and get one that is know to be better suited for audio.  I don't know why I even chose this one!!

ok frequently
 

Doktor Avalanche
but I can guarantee his engine is not dropping out because of his motherboard specs.

Of course the audio engine wasn't dropping out because of the motherboard *specs*.  
 
The OP has swapped out the motherboard.
I let him tell the rest of the story.  

Process of elimination... 
It was a stripped down build (only hardware necessary to run).
DPC Latency was thru the roof.
WiFi and Video were eliminated as culprits.
What's left that can cause such high DPC Latency?  Components/drivers for the motherboard
Granted it's not super common... but I've seen it a number of times thru the years.

I am not going to dispute Jim's knowledge of hardware since he is much more up to speed than I am, but I admit I am hard-pressed to conclude any hardware "incapable." Sacrilege, I know, but even Realtek can be used for playback of audio without issues (just needs to be 16-bit... eek! CD-quality! ack, lol ).
 
Wdf01000.sys is a call to the Wi-Fi "Auto-detect" feature, and lit my LatencyMon up like a Christmas tree (even baking snaps into recorded tracks). I would very much assume the default settings on any Wi-Fi would be calling that guy, so even with a different MB, that needs to be disabled.
 

mettelus
but even Realtek can be used for playback of audio without issues 

With DPC Latency as high as the OP was experiencing, you won't be able to effectively work with audio...
Doesn't matter what audio interface you're using... the speed of the CPU/etc.
 
The OP's problem has been solved.
There's nothing left to argue about.   
 

Not arguing with you Jim, that would be a fool's errand . From my perspective is more to understand a piece of hardware being "bad"... to clarify... hardware may be limited (i.e., Realtek cannot record for crap), but is not "totally incapable."
 
Maybe is foolish, but in my mind all hardware is capable of performance to a "certain" degree. Not sure if that makes sense though?

mettelus
Not arguing with you Jim, that would be a fool's errand . From my perspective is more to understand a piece of hardware being "bad"... to clarify... hardware may be limited (i.e., Realtek cannot record for crap), but is not "totally incapable."
 

We're really not arguing at all...   
 
In the example of Realtek onboard audio, it can work completely glitch-free (albeit not particularly great fidelity or low-latency performance).
BUT, if the machine suffers from super high DPC Latency (not a result of the Realtek itself), it doesn't matter if you're running a Fireface UCX, Apollo, or SoundBlaster... the audio is going to glitch/dropout.
No amount of CPU will remedy the situation.  No audio interface will remedy the situation.
Increasing the ASIO buffer size might buy more time before the glitch/dropout, but again won't remedy it.
The issue has to be solved at the source.  In this case, it was the motherboard components/drivers.
With low/consistent DPC Latency, you can effectively run ANY audio interface that has stable drivers.
Those with top-notch drivers can be run (with substantial loads - glitch free) at the smallest ASIO buffer sizes.

Jim Roseberry
In the example of Realtek onboard audio, it can work completely glitch-free (albeit not particularly great fidelity or low-latency performance).
BUT, if the machine suffers from super high DPC Latency (not a result of the Realtek itself), it doesn't matter if you're running a Fireface UCX, Apollo, or SoundBlaster... the audio is going to glitch/dropout.
No amount of CPU will remedy the situation.  No audio interface will remedy the situation.
Increasing the ASIO buffer size might buy more time before the glitch/dropout, but again won't remedy it.
The issue has to be solved at the source.  In this case, it was the motherboard components/drivers.
With low/consistent DPC Latency, you can effectively run ANY audio interface that has stable drivers.
Those with top-notch drivers can be run (with substantial loads - glitch free) at the smallest ASIO buffer sizes.

We all know about DPC latency here. A formatted/clean install of windows might have resolved it (not a custom build OEM with bloatware and vapourware all over it), with firmware/driver updates everywhere. Followed by a sprinkling of windows update. Unless that happened first you can't possibly nail it down to hardware. These are the factors you are side stepping here. The OP was running a build configured by the OEM for business. The Intel management applications were installed for instance (just one example), I've seen them increase DPC latency as some of them hook into the drivers at hardware level, working similar to ASIO design principles... Only they are so poorly designed the PC latency deteriorates considerably.
 
Anyways...

Yes   It is working well now.  Thanks Jim.  

Hey Doc.  I just want you to know that I sincerely appreciate you taking the time to try and help me.