Hello ,
Right about now I feel like a variation of " the typical macho guy " that drove through a half a tank of gas because he was not able to ask for directions and get help ....
 
Having said that , I will try my best to describe what has been happening and I will humble myself too your suggestions ...
 
 
Let me start with the symptoms first , then I will get into the computers specs .
The current version of Splat that I'm running is Version : 22.6.0 Build 26 [2016-06 ]-x64 ...
My install of SONAR is somewhat cut back , there is no ADD2 drums installed . Melodyne is whatever came in the CCC and there is very little 3 rd party stuff on this lap top  .
I use SONAR on this lap top primarily to practice and learn my way around the features and tutorials of features I'm looking to add to my workflow ...
 
Here's whats been happening ,
I started getting a BSOD just every time I have opened SONAR earlier today and my machine would shut down . APC_Index Mismatch was listed as the message ....
After my computer went through the whole process of restarting I would usually have to manually restart it because my USB SC a Focusrite 2i4 would sound garbled . This didn't happen every time but when it did , after restarting manually the sound card seemed to be working as it should ...
After this happened to me about 5 times , to play it safe I decided to start a few other Musical Software Daw's that I have on this lap top to see if it was a global problem or if it was a problem I'm having only in SONAR .
Samplitude Pro X 2 64 , Mixbus 3.4 , Reaper x64 and a number of other Windows Daw's on this machine ran flawless ....
 
 
FWIW , I'm just reporting,  I'm not drawing any conclusions as of yet ...
 
Anyway back to SONAR . When I was able to get SONAR back up and running here are a few symptoms I kept encontering ..
When SONAR would start I would notice that in my task bar my speaker icon for the 2i4 would get a red star and I would hear a crackle and pop in my studio monitors ....it was hit or miss on whether I would get sound in SONAR ...
When it didn't crash I would get a dialog box stating that I had no Midi drivers , so I opened up my preferences put a check on the 214 midi device  , moved it to the top and hit apply ...having done that I would then exit  SONAR and reopen SONAR and not see that  dialog box again until my next round of BSOD's ..
At one point my transport in SONAR  stopped working  , all this typing is getting to me so I'm gonna cut to the chase ...
This screen shot shows today's round of BSOD's
 

 
this screen shot shows what may be a cause of what's happening 

 
I'm at my wits end and I don't know what is going on here ...
The lap top that this is happening on is a light weight computer ..
Dell Inspirion 15 3000 ...it came w Win 10 H.E.  64 edition installed . it has  all the current Win 10 updates ..
It's light on the RAM it only has 4 Gigs yet I have been able to pull almost 35 tracks on it ...
once again this is a learner/ beater box for me ....
 ...thankfully my other Win 10 lap top is a lot beefier spec wise and I'm not having any problems with it currently ...
other than that let's see,
The Focusrite 2i4 has the supposedly correct  recommended drivers for Win 10  ...2.5.1
In my device mgr I have the realteck SC disabled , + the High Deff Audio device components disabled ...
There are 2 High definition audio controllers listed  , I had them both disabled and one of them keeps re-enabling itself   ..
I've tried to be as descriptive as I can be for a non computer guy ...if you spot anything I'm all ears ...I will try my best 
 
thank you in advance ,
 
Kenny
 
 
 

BSOD normally indicate a driver related problem Kenny, have you tried deleting the AUD.INI in your roaming profile, it might help.

The location will be something like C:\Users\<YOUR USER NAME>\AppData\Roaming\Cakewalk\SONAR Platinum.

Wookiee
BSOD normally indicate a driver related problem Kenny, have you tried deleting the AUD.INI in your roaming profile, it might help.

The location will be something like C:\Users\<YOUR USER NAME>\AppData\Roaming\Cakewalk\SONAR Platinum.

Wookiee ,
 
Thanks for trying too help me out ...
 
Is this the right file  I should delete ? are there any consequences going there  ?
 
 

 
Kenny

Yes, that is the file. To be safe, rename the file. Chances are you will not need the old one and from SONAR's perspective renaming is the same as deleting. Should you do need to refer to a change made in the old aud.ini, it will be there under the new name. SONAR will create a new aud.ini on start up.

Thank you both Wookiee and scook , I will give that the green light and rename it for now  .
 
Kenny

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..

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.

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
 

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.

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