Unfortunately Andertons fix didn't help me (that I know...) and I went back to 96 samples or so as my soundcard didn't like 48....sound got bad and died later.
 
But someone posted a comment to always close sonar through by 'File-Menu-Exit' rather than just click on the red cross up on the right......haven't had a crash ever since while before it would crash a lot when changing sample rates.... 
So 1 happy caker here....

I was recently made aware of this post from a recent link to it by Larry Jones... All I can say is, Thanks a zillion, Larry.  I just disabled all my other sound drivers per this post and am able to do much more at low latency settings on my Forte.  I am stoked.  Thank you so very much, Craig.  
 
You are a brilliant contributor and I am so pleased you are here.  I've been smiling all day doing things that would have crunched my Forte at these low settings previously.  Sure I can't play sounds thru my monitor in this setup but what a wonderful tradoff!
 
I'm bumping this for anyone who missed it.

The tweek didn't work on my system, but I've learned much from reading this thread and am in the process of figuring out why I have to run such high latency. Something is amiss! lol
 
Following the links posted here and exploring other options.
 
Thanks for reviving this thread Dana.

after reading through this I checked my DAW settings since my last full DAW build & optimization dates back to fall 2012 ... and yes, I have done this "HD audio device disabling" and I reckon it's part of the reason why I can track @ 48 samples buffer size (ever since I got the right ASIO drivers in place because they gave me troubles)

I know this has caused some problems for a few people but I regularly use my HD audio driver with anything windows through 2 different speaker sets (one of which is via HDMI) without any problems whatsoever. Using HDMI through a connected monitor with speakers is also considered as causing problems.

I can run my system with very heavy loads using buffers of 48 samples, which is the lowest allowed by the driver.

It would be really interesting to know what makes the difference between one system and another causing this instability.

mudgel
It would be really interesting to know what makes the difference between one system and another causing this instability.

I assume it relates more to the graphics card's driver than anything else, and whether it thinks it's the most important thing in the world and therefore doesn't care if the audio coming out of your TV is 50 milliseconds later than it should be...

mudgel
I regularly use my HD audio driver with anything windows through 2 different speaker sets (one of which is via HDMI) without any problems whatsoever.

Because I want to record from web browsers and other non-asio programs I have the wave device routed through my sound card, and I have the motherboard, and video card sound devices disabled.
 
And I have the windows sounds disabled.
 
I do not understand using a second output.  Please enlighten me.

Vastman
I was recently made aware of this post from a recent link to it by Larry Jones... All I can say is, Thanks a zillion, Larry.  I just disabled all my other sound drivers per this post and am able to do much more at low latency settings on my Forte.  I am stoked.  
 

There is so much excellent technical assistance going on in this forum and I mostly feel inadequate to comment on anything, so if I can get a zillion thanks just for supplying a link, you're welcome and I'm in!

I'm quite impressed that I have no problems in Sonar Platinum with the Tascam FW-1884, which is quite an old audio firewire interface, on Windows 8.1 64 bit.
 
I have to stay away from Wasapi however, or I have no chance with my second audio interface, the Roland Quad Capture: Sonar somehow always complains about (non - existing) problems with frequency/bit rate combos and forces me to use one frequency/rate for my projects. So Asio it is.
 
I have neither disabled the Realtek nor the nvidia audio drivers.
 
However I rarely have huge projects.
 
If someone uploads a project that regularly cause trouble, even with garbled audio, I'd be glad to test it on my setup. It's as easy as uploading a zip file or a CWB on OneDrive, Google Drive, DropBox or whatever and sharing a link.
 
Or tell me how to complexify for comparable tests purposes the Sonar X3 Producer demo - Javier Colon, which it seems to me is one of the only way too rare publicly available Sonar project, I'll be glad to test and measure.
 

So glad this thread surfaced again, because it reminded me how irritating it is being forced to use a high buffer setting. After doing some research and applying some of what I read, I was able to get my buffer setting as low as 64 samples. Still a few crackles when mixing a bigger project, but all's well at 128. If I can record at 64, I'll be in heaven! It hasn't been a big deal lately as I've been working on vinyl transfers and mixing, which didn't require a lower latency, but we're getting ready to track some new material and it'll be much more pleasant to work at 64!
 
Thanks to all who contributed to this thread.