OK I did what Wookiee and scook said to do ...I renamed the AUI file . SONAR created a new one and loaded .
SO far it seems to be getting better ..I haven't had a crash ....
 

einstein36
Hi there,
after googling the error, it definitely seems to be not sonar, but a system or audio driver causing the crash...
one suggestion like Anderton made was to go into device manager and disable the onboard audio(most likely an Realtek or something along those lines) and double check to make sure EVERY device on your laptop has the most updated drivers for windows 10...
hope this helps..

Thank you for helping me out . I understand what you are saying perfectly to a degree .
 
 
I have gone through my computers device manager numerous times and disabled all the usual suspects
The realteck on-board SC is disabled ,  the High Deff Audio device components are disabled ...
The 2 High definition audio controllers that are listed are disabled  yet ,one of them keeps re-enabling itself   ..
My power management and HD  settings are set to never shutting down , ect ect ect...
I have routinely gone through each item in the device manager and did a check for driver updates ... 
In addition to some of these hoops ,  I have found it necessary to always check up on those preferences after a Windows update because for some unexplained reason Windows 10 and Microsoft have decided that it is perfectly OK to do whatever the EFF it want's to do to my machine including changing my preferences with out my consent .
I may of had to consent to their terms of use , in no way did I consent to allowing MS to hold my machine as a hostage .
Also , I did not consent to granting MS the right to change any preference I had put in place nor did I ever grant them the right to ever override my personal preferences that were within the bounds of my fair us of the OS ...  
 
No other Musical application / DAW crashed my computer .Neither has any other program I have opened or used ...
 
On this computer every crash I have had (which were numerous over the last 24 hours  ) involved only one DAW.
Is it the DAW , is it the driver for my SC , or is it the fill in the blank ? ..that's what I'm here to find out ...
 
thanks for your help ....
all the best,
Kenny
 

jatoth
Hi Kenny,
Check your Windows update logs. If you received any updates recently (right before the crashes started), either uninstall the updates or do a System Restore to the point before the updates. I'll go against the popular wisdom here on the forum, not all updates are improvements. If your system and DAW are working fine, do you really need every update? I do not use automatic updates. I may manually update Windows 2-3 times a year, definitely not every Tuesday!
I have experienced Win10 updates that broke perfectly working software. It depends on the software and how tightly it is integrated into the Windows subsystem.
If this solves your problem, turn off automatic updates for a few weeks. Usually Microsoft will recognize there is a problem with that patch and re-release a cleaner update at a later time.

Hi John,
 
I'm on Win 10 Home Edition . The only  way I can shut off the updates is to never put the computer online .
Yes , the whole way Microsoft has been doing the Win 10 updates has put a very bad taste in my mouth ...
I have purposefully tried to update my computer manually at a time of my choosing where I knew I would be OK with letting Windows do it's thing and then wouldn't you know Windows response is Nada ....
Then I decide to sit down and try out one of Craig's weekly  tips on how to do a one knob compressor and then Windows takes it upon itself to.show me it  has more important things for me to do .....
 
Here's a list in 3 parts of what I had to contend with while I all wanted to do was run SONAR ...
It is very possible that this is what Helped crash my computer ...Yet , I'm still confused as to why it only crashed when I tried to open SONAR ...
 
Successful updates, 

 
Not so successful updates part 1 
 

 
Not so successful updates part 2
BTW , this is a continuation of the above list ..not a duplicate 
 
 

 
I'm not cool with this at all and I happen to agree w you ...on  MS messing up a stable machine 
 
thanks ,
 
I'm gonna skip around since this one is an easy one to answer ....
 

chuckebaby
how old is your Hard Drive Kenny ?  BSOD can also be an HD on its last sandwich.
 

Hi Chuck ,
 
I honestly have no idea on how old the Hard Drive is ...I bought this computer brand new in an unopened box during the last week of November around 8 months ago ...
 
thanks ,
 
Kenny

Kenny,
If your crashes started 07-22, then the updates are most likely your problem.
Does "10 Home" allow you to uninstall an update? How about a system restore to 7-21?
If your system was working at some point, but now crashes, it was an update.
 

jatoth
Kenny,
If your crashes started 07-22, then the updates are most likely your problem.
Does "10 Home" allow you to uninstall an update? How about a system restore to 7-21?
If your system was working at some point, but now crashes, it was an update.
 

Hi John ,
 
For all I know , it probably was a number of failed updates that created this problem in the first place .
I had updated my main Win 10 DAW / computer just the day before with out a hitch using the same 2i4 USB SC  & driver version.
 
Yes Home Edition would allow me to roll back and uninstall the updates .
I'm gonna take a wait and see attitude / approach with this whole ordeal to see how it plays out ...
 
Currently I have been crash free since the updates have been installed .When & if anything changes I will try a system restore .
 
SONAR seems to be running just fine on the machine in question
A SONAR  project that has 35 plus tracks w effects on all the FX bins seems to be chugging along OK ...
 
Try as I may too move forward , this whole thing has put my stress levels through the roof and brought my coping skills into the championship rounds of the fight
 
thanks for helping me out ,
 
Kenny
 
 
 

robert_e_bone
You could also try running the WIndows System File Checker:
 
In a Command Prompt window, type sfc /scannow > Press Enter
 
The above will take a few minutes, but it compares things in the Windows guts (its files), and can repair ones it needs to.
 
Bob Bone
 

Hello Bob ,
 
I just got around to  doing your suggestion  here's the scan results .
 
 

 
Let's see how it play's out ...
 
thanks for helping me out,
 
Kenny
 

bitman
Sound like you have a winner Kenny.
From the web:
 
Causes of APC_INDEX_MISMATCH Blue Screen Errors

• Incorrectly configured, old, or corrupted device drivers. (very common)
• Corruption in Windows registry from a recent software change (install or uninstall).
• Virus or malware infection that has corrupted Windows system files or Windows Operating System-related program files.
• Driver conflict after installing new hardware.
• Damaged or removed system files after you’ve installed software or drivers related to Windows Operating System.
• Error 0x1 blue screen caused by a damaged hard disk.
• APC_INDEX_MISMATCH STOP error due to memory (RAM) corruption.

APC_INDEX_MISMATCH blue screen errors can be caused by a variety of hardware, firmware, driver, or software issues.
 
 
For malware let ADWCleaner from Bleeping Computer have a shot at it - Indiscriminately let it clean everything it finds. If you're on Win7 it is always good to also run ComboFix on it on time too.
 
For disk checking I like HD Tune to do a surface test.
Might be good to backup your projects first in case the drive is ailing.

sorry to take so long getting back too you ...
 
Yes , I got a winner for sure with that message ..APC_INDEX_MISMATCH....
I did do a fair amount of research on this subject  before I posted this thread ...
 
Thankfully,   for now all seems OK . .
 
Thanks for you help ,
 
Kenny
 
 
 
 
 

I hope everything is working now.....
 
 

einstein36
I hope everything is working now.....
 
 

Thanks einstein36  
 
Updated Splat yesterday , been running it on the machine that was giving my problems . Things appear to be OK ...
 
all the best,
 
Kenny.

kennywtelejazz

robert_e_bone
You could also try running the WIndows System File Checker:
 
In a Command Prompt window, type sfc /scannow > Press Enter
 
The above will take a few minutes, but it compares things in the Windows guts (its files), and can repair ones it needs to.
 
Bob Bone
 

Hello Bob ,
 
I just got around to  doing your suggestion  here's the scan results .
 
 

 
Let's see how it play's out ...
 
thanks for helping me out,
 
Kenny
 

Howdy, Kenny.  
 
If everything seem kewl now, you might consider flagging the post I quoted from as the Answer, or maybe modify your initial thread post's subject line to include (Solved) so that if someone else is looking for a solution to a similar situation they can maybe find this thread. :)
 
In any case, IF things are OK on your machine now, that's good news indeed.
 
Bob Bone
 

robert_e_bone

kennywtelejazz

robert_e_bone
You could also try running the WIndows System File Checker:
 
In a Command Prompt window, type sfc /scannow > Press Enter
 
The above will take a few minutes, but it compares things in the Windows guts (its files), and can repair ones it needs to.
 
Bob Bone
 

Hello Bob ,
 
I just got around to  doing your suggestion  here's the scan results .
 
 

 
Let's see how it play's out ...
 
thanks for helping me out,
 
Kenny
 

Howdy, Kenny.  
 
If everything seem kewl now, you might consider flagging the post I quoted from as the Answer, or maybe modify your initial thread post's subject line to include (Solved) so that if someone else is looking for a solution to a similar situation they can maybe find this thread. :)
 
In any case, IF things are OK on your machine now, that's good news indeed.
 
Bob Bone
 

 
Alright Bob I'll give it to you
 
all the best,
 
Kenny