Audio Engine Stopped - Will Not Go Away!! - $$$ Reward - Bug exposed?

Facts: Using Sonar forever. On Platinum, latest release.  Win 10, Big Ass Huge Computer (32GB Ram, EVGA Classified MB, 12 Cores 5820K, SSD Samsung 840, Audient ID22, every bit of information about my system is pasted below).
 
PROBLEM: The Pesky Audio Engine Stopped Unexpectedly.
It's not a driver latency issue, no matter the latency, Sonar decides to STOP playing audio at very specific points of my projects. The current project is no exception as the beast just arrived. Yay! Read on.. if you dare...
 
Let's start with, in this case, two Sonar files to keep the dark illustration simple:
1) Main Project File - 32 Bit, 44K. All working well... then...
2) Drum Tracking File - 32 Bit, 44K. Select One Bar and 8 tracks of drums, Bouncing the clips so it doesn't copy the whole 180MB audio file then paste to #1 Main Project File.
3) Play audio and BAM!!! Yes, The Audio Dropout shows up and the file won't play at this specific pointer. It won't even start running within this one bar section. I have to go a few bars earlier for it to start playing always to FAIL at the specific pasted section.
 
What I've tried to do:
Does not work: Increase latency on the Audience ID22 (Awesome audio interface, way better then my previous RME Babyface BTW).
Does not work: Turn off ALL plugins with the FX button so CPU is at near zero.
Does not work: A brand new, practically empty 1TB SSD hard drive.
 
Happens in many Sonar projects: Once I get going on a project, it can expand to many tracks, but eventually, some recorded audio will screw me. The dropout is NEVER with a synth. 
 
Impractical Solution: With my Sonar projects, it's always some audio that I recorded that eventually is the problem. I run around the file freezing tracks, that previously worked, like guitar, vocals, etc.. and then, finally the dropout goes away.  
 
Check out this hilarious fix to the problem above in #1 Main File.  a) Take the 8 new tracks, one bar and FREEZE them. Yay, it works and audio won't drop out. Wait, kids, it gets better.  UNDO the bounce and it STILL works without an audio dropout.  Huh?  So apparently, Sonar interprets, caches, indexes, waveform previews, or "who knows?" the original audio file a certain way, but it's corrupt to give a dropout. Is the "Audio Dropout" error (Ummm bug) just lazy programming and the real error isn't showing up? I do get the major pop-up error about corrupt audio in the advanced stages of this dilemma at times, BTW.
 
Is this my solution? Bounce and unbounce every new audio recorded track? (I'll try it for now). Is the bug in the waveform preview?   These files are simple audio files so certainly aren't causing a CPU issue. Whatever plugins are on the tracks does not make a difference. Freezing audio in Whack-a-mole fashion is not a workable solution as it adds way too much time to the production process. "In the midst of creative bliss, the dark clouds descended and the buzzkill grim reaper arrived to slaughter the ecstatic treble vibes of the unsuspecting producer."
 
It is possible: That this bug only appears when PASTED audio exists in a track. So the PASTE function may be the culprit, which is clear in the example above.
 
YOUR SOLUTION: 
How can I use Sonar professionally? It's the end of the road. Lucky me, I own "Lifetime Updates" (at present) from Hell!!!  Get your bank account ready to receive CASH because you're a genius who has the iron-clad fix to this problem. $$ Reward to fix this problem, which is very likely a BUG in Sonar.  You can even come to my house in Los Angeles. I will pay you $$$.
 
Thank you,
 
DannyK
 
SIV64X - System Information Viewer V5.12 MINTYJAMBOX::minty
Windows 10 x64 Professional (Single User) V10.00 Build 10586 TH2 EVGA 151-HE-E999 MINTYJAMBOX::minty English (0409) United States (1)
Workgroup WORKGROUP 00 12:45:52 2016-09-12 13:51:08 [2.13GHz Quad DDR4 RAM] PCIe x8@1 (x8@3) CLK:DRAM 3:32 PKG 48°C
Resource Usage 46% [1] 12% Current Maximum DDR4 RAM CAS Latency 15
System Physical Memory 15.00GB 933.66MB 32.00GB RAS to CAS Delay (tRCD)15
System Paging File 16.90GB 19.77GB 36.68GB RAS Precharge (tRP) 15
System File Cache 16.27GB 12.81GB 29.07GB Cycle Time (tRAS) 35 (4)
Row Cycle Time (tRC) 50 2T
CPUs 12 Cores 6 Chips 1 Disks 31°C 32°C 36°C 29°C NA 37°C NA DIMMs 38°C 36°C 37°C 37°C
Sensor Fintek F71889A MB 40°C 34°C I/O +3.33 PSU +5.47 +7.68 +5.04 VBAT +3.36 Fans 1,236 0 0 0
Processor Clock 0.8% CPU Utilisation Volts Temp Power APIC Socket R2 LGA-2011-3 Intel Core i7 Hexa 5820K (Haswell-E) 3.30GHz [R2]
CPU-0 1.20GHz x12 100MHz K 1% 0.75 36°C 39.51 0.0.0 Technology 22nm x64 Family 6 Model 63 (3F) Stepping 2 Revision 36
CPU-1 1.20GHz x12 100MHz CPU-1 is Idle 0.0.1 CPUs 12 Cores 6x2 Intel(R) Core(TM) i7-5820K CPU @ 3.30GHz
CPU-2 1.20GHz x12 100MHz U 2% 0.75 36°C 39.51 0.1.0 L1 Code Cache (2) 8-way 64-byte 6 x 32KB Core 0.78 volts
CPU-3 1.20GHz x12 100MHz CPU-3 is Idle 0.1.1 L1 Data Cache (2) 8-way 64-byte 6 x 32KB [3/3]Temp 42.0°C (41-43)
CPU-4 1.20GHz x12 100MHz CPU-4 is Idle 0.75 35°C 39.51 0.2.0 L2 Unified Cache (2) 8-way 64-byte 6 x 256KB [8]Fan 1,236 RPM
CPU-5 1.20GHz x12 100MHz D 2% I 1% 0.2.1 L3 Unified Cache (12) 20-way 64-byte 1 x 15MB [25]Power 37.05 Watts
CPU-6 1.20GHz x12 100MHz CPU-6 is Idle 0.75 33°C 39.51 0.3.0 [Cache-0 Latency] [MMX SSE4.2 XD VMX AVX2] Agent 1.20GHz
CPU-7 1.20GHz x12 100MHz CPU-7 is Idle 0.3.1
CPU-8 1.20GHz x12 100MHz U 1% 0.75 37°C 39.51 0.4.0 Memory GPU 2.0% GPU Utilisation Volts Temp Video
CPU-9 1.20GHz x12 100MHz I 1% 0.4.1 GPU-0 405MHz P8 135MHz Activity 4.0 % 0.99 37°C 405MHz
CPU-10 1.20GHz x12 100MHz K 2% 0.77 37°C 39.51 0.5.0 GPU-1 405MHz P8 135MHz Activity 0.0 % 0.99 37°C 405MHz
CPU-11 1.20GHz x12 100MHz U 2% 0.5.1
[ OK ] [ Copy] [Windows] [Machine] [Status] [USB Bus] [Network] [ SPD ] [Volumes] [Adapters] [PCI Bus] [ About] [ Help]

If I bring you my computer and we load your project and it DOES NOT happen, what is my $reward?
 

I live in Thousand Oaks. Downtown L.A. is only a 30 minute drive (not in rush hour though).

Once I was beta testing some high performance VST and I was getting dropouts.
I changed the Config file settings 'DropoutMsec' to 500.
I think that helped, but I also increased 'ExtraPluginBufs' and maybe some other stuff.
That was a year or two ago and I haven't changed them back, so I think they are harmless changes.
 
Might not help you at all.
 
LatencyMon from Resplendence.com is valuable.
 

Just a random thought, but could it be related to 32-bit audio? I'm pretty sure most people(?) use 24-bit because there's plenty of headroom there.   Does bouncing to 24-bit files make a difference?

I wonder if this bug has anything to do with two projects open and exclusive owning or mapping of the particular audio file. I.e. the copy from one project makes a reference to (a portion of) a file of that project and then the second project has trouble opening and seeking to that (portion of) the file during playback. After pasting the clip segment, does the clip inspector property refer to the original file? If so, the two projects are now sharing that file. Interesting that the second project can bounce/freeze the file (i.e. can read it) but couldn't play it. Interesting again that undo of bounce/freeze makes it playable. And this is still with both projects open? Something to try:Select that clip in the new project, then do Track view -> Clips -> Apply trimming, just in case that refreshes whatever internal structure is out of whack.

How many hard drives do you have?  I see the SSD Samsung 840 mentioned above.  Do you have separate drives for your operating system, samples, project data, ect?  I have my operating system on one drive, my Cakewalk projects on a different drive, my sample data, vsti data and backups each on their own drives.   Trying to run everything from one hard drive, can really impede performance.
 
A few things that I've done recently, and it seems to have really helped with those dreaded Audio Engine Stops.
 
1. Installed "Auslogics Disc Defrag"  (for non SSD drives only).  Run this once a week or so, to defrag and optimize my spinning data, and sample drives, to keep them from getting too fragmented, which can slow down performance.  FYI.  I don't have any SSD drives, but from what I've read, it's not good to defrag them.  It can shorten their useful life.
 
2.  Installed Intel's free "Intel Extreme Tuning Utility" software.  (For Intel CPU's only).  This software can be used to benchmark, overclock, and tweak your system, to make sure that you are getting the best performance.  You can even download profiles from other users, and try them on your system.  I was able to bump up performance quite a bit on my system (which is an i7 processor from a few years ago).
https://downloadcenter.intel.com/download/24075/Intel-Extreme-Tuning-Utility-Intel-XTU-
 
3.  Install "Novabench" Benchmarking Software.  Free software can be used to compare your system to others with similar systems.  Helps to see if any of the hardware components are performing below the norms that other users are getting.  https://novabench.com/
 
4.  Make sure that no other audio components in your system are interfering.  I went through Windows Device Manager and disabled all audio drivers which were not needed.  Things like motherboard sound drivers, audio drivers for my 2nd monitor.  Not even sure why those were installed.  If you have ASIO4All installed, uninstall it.  It can be known to interfere with other audio drivers.
 
5.  While in device manager, go through all of the items under the "Universal Serial Bus Controllers" tab.  Double click each one and look for a "Power Management" tab at the top (not all of them have this tab).  Click this and see if "Allow the computer to to turn off to save power" is checked.  If it is, uncheck it.  Windows USB power saving features are cool, but can really screw with DAW performance.  Things like delaying USB drive reads and writes, disconnecting midi controllers when not in use, ect.
 
6.  While you're at it, right click on the windows logo at the bottom left and click "Power Options"  See what power saving plan that windows is using by default.  Usually it's on "Balanced".  I switch mine to "High Performance", to keep Windows from putting system components to sleep, to save power.   I think, that if you install the Intel Tuning Utility mentioned above, you get a few additional Power Plans to choose from.
 
7.  Check your Sonar config file in "Preferences>Audio>Configuration file"   There are several forum threads about changes that may or may not be helpful.   I usually only change "Threadschedulingmodel" to 2.  Supposedly works better for newer processors.  I've tried tweaking other things, but I haven't seen any noticeable difference, so I usually stick with the default for everything else.
 
8.  "CPU Park Control" is a cool CPU software which can help identify if you are getting full use of your CPU.  It's free, might be worth trying that.  https://bitsum.com/parkcontrol/
 
Try some or all of the above.  Maybe something will help. 
 

Samsung 840 Evo SSDs had a problem where disk reads slowed down over time. Is your disk an Evo version?
 
http://www.anandtech.com/show/9196/samsung-releases-second-840-evo-fix
 
To fix, install Samsung's Magician software from here:
 
http://www.samsung.com/semiconductor/minisite/ssd/download/tools.html?CID=AFL-hq-mul-0813-11000279
 
This software will also benchmark your drive, and tell you if it's using the right AHCI mode rather than IDE. Mine wasn't, and making the change (which is a bit tricky, so Google it), doubled read and write performance on my SSD.

If copying the project (with audio) to a different folder on the same SSD has no effect, I suggest you try copying it to one of your other drives just to be sure it's not a problem with that particular device.
 
Also, regarding your system being 'pretty tweaked', this could easily be causing/contributing to the problem. In particular, if you've set processor scheduling for best performance of 'Background Services' instead of 'Programs', I suggest you undo that long-ago 'debunked' tweak.
 
Incidentally, thanks for taking my 'editorial chaff' comment in stride. 

@neonerd re: 32 bit: The headroom of 32 bits that maybe you want is available in Edit->Preferences->File - File Bit Depths [ Render Bit Depth ]. This refers to file-stored bounces, freezes, etc. and can hold hotter or higher resolution signals than you can record, play back, or export to typical devices.