audio engine stopping

Have you run Resplendence LatencyMon? When building a new machine, you need to watch all processes on the computer like a hawk. So many processes can be set to "Manual" or even "Disabled" (if truly garbage), and one I found particularly upsetting is "AutoDetect" functionality of Wi-Fi (every 4 seconds). Another issue with this is the priority setting, as many can be lowered below "Normal" without issues. When running low latencies, the audio engine must have a consistent data stream going - if the system has some BS utility set at "high priority" it can cause enough of a hiccup to shut the audio engine down.
 
Another thing to check is msconfig.exe and "Hide all MS processes" and allow only software and hardware required on boot (rest can always be run manually, but some will change the registry to auto-boot from simply running them, so need to monitor this at times).

It means that is how it recommends I run it for everything. Blackbird control is the mackie firewire driver. It has it's own dpc checker and it makes a recommended mode based on what it finds.

HighAndDry
It means that is how it recommends I run it for everything. Blackbird control is the mackie firewire driver. It has it's own dpc checker and it makes a recommended mode based on what it finds.

I can't possibly believe this. Maybe for testing.

EDIT ... You do mean windows safe mode? Or have I got the wrong end of the stick?

Dpc latency or disk contention are probably your issue.

If it is a problem after recording for a while then hitting stop, then it might be that your virus scanner is scanning the new sound files for viruses.

Especially if it goes away after a bit.

If it is Persistent, perhaps dpc. Try latency Mon as suggested and post the results.

_This was the result after disabling my Ethernet driver and turning Norton off! It ran for 26 minutes.
Before with those on it ran for 5 min.  wth?
________________________________________________________________________________________________________ CONCLUSION _________________________________________________________________________________________________________ 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 or more DPC routines that belong to a driver running in your system appear to be executing for too long. One problem may be related to power management, disable CPU throttling settings in Control Panel and BIOS setup. Check for BIOS updates. LatencyMon has been analyzing your system for  0:26:26  (h:mm:ss) on all processors.
_________________________________________________________________________________________________________ SYSTEM INFORMATION _________________________________________________________________________________________________________ Computer name:                                        STUDIO OS version:                                           Windows 8.1 , 6.2, build: 9200 (x64) Hardware:                                             Z97X-Gaming 7, Gigabyte Technology Co., Ltd. CPU:                                                  GenuineIntel Intel(R) Core(TM) i7-4790K CPU @ 4.00GHz Logical processors:                                   8 Processor groups:                                     1 RAM:                                                  16229 MB total
_________________________________________________________________________________________________________ CPU SPEED _________________________________________________________________________________________________________ Reported CPU speed:                                   3991 MHz Measured CPU speed:                                   1 MHz (approx.)
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):   8292.823740 Average measured interrupt to process latency (µs):   2.326322
Highest measured interrupt to DPC latency (µs):       8291.284183 Average measured interrupt to DPC latency (µs):       0.823292
_________________________________________________________________________________________________________  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):              262.259334 Driver with highest ISR routine execution time:       HDAudBus.sys - High Definition Audio Bus Driver, Microsoft Corporation
Highest reported total ISR routine time (%):          0.046250 Driver with highest ISR total time:                   Wdf01000.sys - Kernel Mode Driver Framework Runtime, Microsoft Corporation
Total time spent in ISRs (%)                          0.047021
ISR count (execution time <250 µs):                   1905695 ISR count (execution time 250-500 µs):                0 ISR count (execution time 500-999 µs):                6 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):              7509.506389 Driver with highest DPC routine execution time:       Wdf01000.sys - Kernel Mode Driver Framework Runtime, Microsoft Corporation
Highest reported total DPC routine time (%):          0.227216 Driver with highest DPC total execution time:         Wdf01000.sys - Kernel Mode Driver Framework Runtime, Microsoft Corporation
Total time spent in DPCs (%)                          0.313897
DPC count (execution time <250 µs):                   7603433 DPC count (execution time 250-500 µs):                0 DPC count (execution time 500-999 µs):                290 DPC count (execution time 1000-1999 µs):              29 DPC count (execution time 2000-3999 µs):              13 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:                 svchost.exe
Total number of hard pagefaults                       432 Hard pagefault count of hardest hit process:          327 Highest hard pagefault resolution time (µs):          22111.979704 Total time spent in hard pagefaults (%):              0.000597 Number of processes hit:                              8
_________________________________________________________________________________________________________  PER CPU DATA _________________________________________________________________________________________________________ CPU 0 Interrupt cycle time (s):                       49.094776 CPU 0 ISR highest execution time (µs):                262.259334 CPU 0 ISR total execution time (s):                   5.967353 CPU 0 ISR count:                                      1905701 CPU 0 DPC highest execution time (µs):                7509.506389 CPU 0 DPC total execution time (s):                   39.656055 CPU 0 DPC count:                                      7507684 _________________________________________________________________________________________________________ CPU 1 Interrupt cycle time (s):                       0.329031 CPU 1 ISR highest execution time (µs):                0.0 CPU 1 ISR total execution time (s):                   0.0 CPU 1 ISR count:                                      0 CPU 1 DPC highest execution time (µs):                9.97770 CPU 1 DPC total execution time (s):                   0.001151 CPU 1 DPC count:                                      1604 _________________________________________________________________________________________________________ CPU 2 Interrupt cycle time (s):                       0.750946 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):                49.590078 CPU 2 DPC total execution time (s):                   0.142975 CPU 2 DPC count:                                      64839 _________________________________________________________________________________________________________ CPU 3 Interrupt cycle time (s):                       0.313332 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):                5.282636 CPU 3 DPC total execution time (s):                   0.001641 CPU 3 DPC count:                                      2452 _________________________________________________________________________________________________________ CPU 4 Interrupt cycle time (s):                       0.339373 CPU 4 ISR highest execution time (µs):                0.0 CPU 4 ISR total execution time (s):                   0.0 CPU 4 ISR count:                                      0 CPU 4 DPC highest execution time (µs):                5.180907 CPU 4 DPC total execution time (s):                   0.002732 CPU 4 DPC count:                                      4012 _________________________________________________________________________________________________________ CPU 5 Interrupt cycle time (s):                       0.301646 CPU 5 ISR highest execution time (µs):                0.0 CPU 5 ISR total execution time (s):                   0.0 CPU 5 ISR count:                                      0 CPU 5 DPC highest execution time (µs):                11.308695 CPU 5 DPC total execution time (s):                   0.002418 CPU 5 DPC count:                                      2967 _________________________________________________________________________________________________________ CPU 6 Interrupt cycle time (s):                       0.404947 CPU 6 ISR highest execution time (µs):                0.0 CPU 6 ISR total execution time (s):                   0.0 CPU 6 ISR count:                                      0 CPU 6 DPC highest execution time (µs):                32.863192 CPU 6 DPC total execution time (s):                   0.027974 CPU 6 DPC count:                                      18757 _________________________________________________________________________________________________________ CPU 7 Interrupt cycle time (s):                       0.549506 CPU 7 ISR highest execution time (µs):                0.0 CPU 7 ISR total execution time (s):                   0.0 CPU 7 ISR count:                                      0 CPU 7 DPC highest execution time (µs):                5.666750 CPU 7 DPC total execution time (s):                   0.000973 CPU 7 DPC count:                                      1457 _________________________________________________________________________________________________________

___page 2 of processes
______________________________________________________________________________________________________ CONCLUSION _________________________________________________________________________________________________________ Your system seems to be having difficulty handling real-time audio and other tasks. You may experience drop outs, clicks or pops due to buffer underruns. One or more DPC routines that belong to a driver running in your system appear to be executing for too long. At least one detected problem appears to be network related. In case you are using a WLAN adapter, try disabling it to get better results. One problem may be related to power management, disable CPU throttling settings in Control Panel and BIOS setup. Check for BIOS updates. LatencyMon has been analyzing your system for  0:07:08  (h:mm:ss) on all processors.
_________________________________________________________________________________________________________ SYSTEM INFORMATION _________________________________________________________________________________________________________ Computer name:                                        STUDIO OS version:                                           Windows 8.1 , 6.2, build: 9200 (x64) Hardware:                                             Z97X-Gaming 7, Gigabyte Technology Co., Ltd. CPU:                                                  GenuineIntel Intel(R) Core(TM) i7-4790K CPU @ 4.00GHz Logical processors:                                   8 Processor groups:                                     1 RAM:                                                  16229 MB total
_________________________________________________________________________________________________________ CPU SPEED _________________________________________________________________________________________________________ Reported CPU speed:                                   3991 MHz Measured CPU speed:                                   1 MHz (approx.)
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):   256.336239 Average measured interrupt to process latency (µs):   2.065016
Highest measured interrupt to DPC latency (µs):       63.121837 Average measured interrupt to DPC latency (µs):       0.595117
_________________________________________________________________________________________________________  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):              215.500877 Driver with highest ISR routine execution time:       Wdf01000.sys - Kernel Mode Driver Framework Runtime, Microsoft Corporation
Highest reported total ISR routine time (%):          0.045891 Driver with highest ISR total time:                   Wdf01000.sys - Kernel Mode Driver Framework Runtime, Microsoft Corporation
Total time spent in ISRs (%)                          0.050894
ISR count (execution time <250 µs):                   618598 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):              1591.207216 Driver with highest DPC routine execution time:       ndis.sys - Network Driver Interface Specification (NDIS), Microsoft Corporation
Highest reported total DPC routine time (%):          0.215637 Driver with highest DPC total execution time:         Wdf01000.sys - Kernel Mode Driver Framework Runtime, Microsoft Corporation
Total time spent in DPCs (%)                          0.224277
DPC count (execution time <250 µs):                   603978 DPC count (execution time 250-500 µs):                0 DPC count (execution time 500-999 µs):                12 DPC count (execution time 1000-1999 µs):              3 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.
Process with highest pagefault count:                 killerservice.exe
Total number of hard pagefaults                       11 Hard pagefault count of hardest hit process:          4 Highest hard pagefault resolution time (µs):          3.836382 Total time spent in hard pagefaults (%):              0.000001 Number of processes hit:                              4
_________________________________________________________________________________________________________  PER CPU DATA _________________________________________________________________________________________________________ CPU 0 Interrupt cycle time (s):                       9.315903 CPU 0 ISR highest execution time (µs):                215.500877 CPU 0 ISR total execution time (s):                   1.743114 CPU 0 ISR count:                                      618598 CPU 0 DPC highest execution time (µs):                1591.207216 CPU 0 DPC total execution time (s):                   7.648593 CPU 0 DPC count:                                      586562 _________________________________________________________________________________________________________ CPU 1 Interrupt cycle time (s):                       0.082860 CPU 1 ISR highest execution time (µs):                0.0 CPU 1 ISR total execution time (s):                   0.0 CPU 1 ISR count:                                      0 CPU 1 DPC highest execution time (µs):                56.737660 CPU 1 DPC total execution time (s):                   0.000441 CPU 1 DPC count:                                      486 _________________________________________________________________________________________________________ CPU 2 Interrupt cycle time (s):                       0.072930 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.388374 CPU 2 DPC total execution time (s):                   0.001348 CPU 2 DPC count:                                      1626 _________________________________________________________________________________________________________ CPU 3 Interrupt cycle time (s):                       0.079091 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):                56.282886 CPU 3 DPC total execution time (s):                   0.000701 CPU 3 DPC count:                                      950 _________________________________________________________________________________________________________ CPU 4 Interrupt cycle time (s):                       0.069769 CPU 4 ISR highest execution time (µs):                0.0 CPU 4 ISR total execution time (s):                   0.0 CPU 4 ISR count:                                      0 CPU 4 DPC highest execution time (µs):                56.225758 CPU 4 DPC total execution time (s):                   0.000643 CPU 4 DPC count:                                      865 _________________________________________________________________________________________________________ CPU 5 Interrupt cycle time (s):                       0.079368 CPU 5 ISR highest execution time (µs):                0.0 CPU 5 ISR total execution time (s):                   0.0 CPU 5 ISR count:                                      0 CPU 5 DPC highest execution time (µs):                55.993736 CPU 5 DPC total execution time (s):                   0.000867 CPU 5 DPC count:                                      684 _________________________________________________________________________________________________________ CPU 6 Interrupt cycle time (s):                       0.154272 CPU 6 ISR highest execution time (µs):                0.0 CPU 6 ISR total execution time (s):                   0.0 CPU 6 ISR count:                                      0 CPU 6 DPC highest execution time (µs):                251.202205 CPU 6 DPC total execution time (s):                   0.02830 CPU 6 DPC count:                                      12436 _________________________________________________________________________________________________________ CPU 7 Interrupt cycle time (s):                       0.074097 CPU 7 ISR highest execution time (µs):                0.0 CPU 7 ISR total execution time (s):                   0.0 CPU 7 ISR count:                                      0 CPU 7 DPC highest execution time (µs):                55.591330 CPU 7 DPC total execution time (s):                   0.000577 CPU 7 DPC count:                                      384 _________________________________________________________________________________________________________

If you keep it make sure in windows control panel sounds the onboard is set as default. That way windows goes nowhere near your audio interface. You can also disable your external interface here. You will then need to route the onboard sound into your external interface or whereever via cables.

Btw the reports don't really say much. You need to look at the drivers tab of latencymon to see what's going on... Perhaps post a screenshot (make sure we see all of it, sort it in offending order).

I just opened device manager and found that Intel Management engine interface has a problem.  
PCI bus 0 device 22 function 0
Device Status
This device cannot start. (Code 10)
STATUS_DEVICE_POWER_FAILURE
 
 

I restarted and restored bios to optimized defaults. ( I know that isn't the best way to go )  Now that problem didn't show up in device manager. 
I was thinking that it perhaps has/had something to do with the firewire card.  since it does mention pci bus.
How do you disable intel management interface? IN task manager?
There are two Intel services running  Intel dynamic application loader host interface
and Intel local management service
 

Is HD audio running through the video cards audio HDMI...?
 
That caused all kinds of problems with my old setup with DCP and audio dropouts, and sonar loosing my audio drivers....
 
I went nuts...trying to solve that...Until Creg said something about it on one of his post to turn it off.
 
So give it a go.
 
Also in bios there are some things you need to turn off...Has to do with speed step, and VT...
 
Try that if you will.
 
And Alex...now I know you are Hiding in muse as Dokotor....Please do not dis this process, or argue it with me....it may help...it may not
 
Try as it may be a solution I found to work here...a bit too late for the old one...But does solve on the new one.
 
Oh, and if you feel Firewire is not performing so great with your system....Try a Thunderbolt 2 card, and adapter.
 
Solved many issues with wi fi and internet onboard nic here also....And I do not know why..but it did do that for me, helping me use any buffer I need to use...and not be locked at the most highest one, and as you a special asio mode 1...other than normal or lowest.
 
 
 
Wink.

Sir Les
Is HD audio running through the video cards audio HDMI...?
 
That caused all kinds of problems with my old setup with DCP and audio dropouts, and sonar loosing my audio drivers....
 
I went nuts...trying to solve that...Until Creg said something about it on one of his post to turn it off.
 
So give it a go.
 
Also in bios there are some things you need to turn off...Has to do with speed step, and VT...
 
Try that if you will.
 
And Alex...now I know you are Hiding in muse as Dokotor....Please do not dis this process, or argue it with me....it may help...it may not
 
Try as it may be a solution I found to work here...a bit too late for the old one...But does solve on the new one.
 
Oh, and if you feel Firewire is not performing so great with your system....Try a Thunderbolt 2 card, and adapter.
 
Solve many issues with wi fi and internet here also....And I do not know why..but it did do that for me.
 
Wink.

Les fairly sensible advice but should be done last. However if CPU in windows power options (min/max) is set to 100% for both you don't need to disable speedstep. All you need to do is disable the HDMI drivers in device manager.

The main issue right now is intel management crap...

Ok .  I ran that (latencymon) overnight.  The interesting thing is for the first 20 minutes it seemed ok. but after 10 hours it gave me the same report. 
   I am using the onboard video.  so I am not sure about had audio 
Thanks everyone

Quick clarification on LatencyMon - The bottom bar on that first screen is "Reported total hard pagefault count" and is a cumulative number. LatencyMon itself adds latency, so that bottom bar will go into the red (something like >100 total) if left running for long periods. That particular bar is not as meaningful as the others (if you can pull <100 pagefaults in 24 hours, that is Guiness Book of World Records material). On the "Main" tab, the top 4 bars are what to watch, but remember that LatencyMon is also contributing to them.
 
While LatencyMon is running, if you click on the Process/Drivers/CPU tabs, the columns can be ordered numerically by clicking on their headers. Processes->Hard Pagefaults and Drivers->DPC count/ISR Count are the most useful, when tracking down things. CPU 0 will probably (always?) be the highest offender, because Core 0 is also the "Windows workhorse" (all machines have a Core 0, not all have a Core 8/12, etc.). Comedically, SONAR gets to be Windows' scapegoat because people watch core loading in SONAR, and rarely check it with SONAR not running. Point here is using those tabs, you can write down/research the highest offenders.
 
Another caveat to the above - some processes are called by other programs, so it is not always "cut-and-dry" finding them (most are, but a handful are not).
 
Regardless of the above details (colors/numbers), you want to simply get the green message on the main screen "Your system appears to be suitable for handling real-time audio and other tasks without dropouts." and audibly not have any pops/crackles, etc. while running your DAW.

Did you remove the intel management engine? I can't stress this enough...
No doubt you may have been supplied other bloatware in add/remove programs.
Do you have screenshots of latency monitor drivers tab?
Another thing is download something like process explorer and process monitor (latencymon first though).
 
Thanks..