Getting the BSOD, "WER-56565-0" with audio stuttering

This may or may not be the source of your probplem, but I would check to see if the sample rates match on what's set in your audio sound card and what's on your Playback Devices in Win 7?
 
I had to do this yesterday on my Focusrite 2i4.........I always have the sample rate set at 48000 as that's what all my VST's (in standalone mode) are set at. For general Windows useage (Win 8.1 x64) I usually keep it at 44.1k, but when playing some Youtube video's last night, I had to change it to 48k as 44.1k didn't produce any sound (no BSOD's or stuttering).
 
Hopefully, your issue is something as easy as this.
 
I doubt having those older versions of Sonar would cause a BSOD as I also have older versions installed on my system.
However, I would make sure all the drivers for your hardware are all up to date. 
 
 
 
 

You're going to need to search on the bug check code (bccode:) from the blue screen. You can also try "whocrashed" (I think that's what its called). It will print out the latest minidump if it can.

Actually, I unplugged my M-Audio Fast Track and the laptop booted up a lot faster with no blue screen, so maybe the interface is just in its death rattle. I got it from a pawn shop anyway. Time to upgrade.

There will be no issue from having multiple Sonar versions installed.  They do not compete with each other, and lots of folks keep older versions installed - to preserve access to plugins that were dropped in later releases, for example.
 
I don't myself set Windows to use my audio interface as the Windows Default Audio Device, because I like to be able to have Sonar open at the same time I may choose to play a YouTube video or MP3 tune, and too many times I have had conflicts in the past.  (I use ASIO drivers).
 
For me, ONLY my music applications, such as Sonar or stand-alone synth programs, use my audio interface - which is always set to use ASIO drivers.
 
Then, for being able to hear sounds from Windows, like Windows Media Player and YouTube, I have 2 ways I run, depending on what my needs of the moment are:
 
1.  My normal way of setting the Windows Default Audio Device is to set it to use the HDMI audio for one of my 2 connected HDMI TV's that I use for display monitors.  I do this because the speakers in the TV's are fine for playing a YouTube video or whatever, and this way I never have any conflicts between applications (Sonar and other music applications are the only things that access the audio interface, so Windows does not conflict with it when I run this way).
 
2.  The other way I sometimes run is to set the Windows Default Audio Device to the motherboard's on-board audio, and then I either use some cheap computer speakers or I will split the output from the computer's audio jack into 2 quarter-inch cables that then get fed to 2 inputs on my audio interface (that gives me a higher grade sound).
 
Anyways, I never allow multiple applications to try to access ASIO drivers at the same time, and running as above helps keep that from happening.
 
Please note that I have seen reported issues where on-board sound conflicting in some manner with an audio interface, and their solution was to disable their on-board sound, but this seems to be a pretty rare thing - from anything I have observed.
 
Hope that helps, 
 
Bob Bone

This link is for the latest released Windows drivers for a Fast Track Pro:
 
http://cdn.avid.com/AudioDrivers/Win/Fast_Track_Pro_Drivers/Install_M-Audio_Fast_Track_Pro_6.1.10.zip
 
Here is the associated content from the site, describing the above driver version:
 
Jun 20. 2013
Windows 7, 8, 8.1
Support for Pro Tools 10.3.x – Pro Tools 11
Hardware latency values are now reported with far greater accuracy, allowing host applications to perform the best possible hardware latency compensation
Improved performance
Improved multi-client support
Miscellaneous bug fixes
 
Also, keep in mind that many USB-connected audio interfaces do NOT function well or sometimes at all if plugged into a USB 3 port - they are expecting a USB 2 port instead.
 
And, as noted above, check your Sample Rates, between what the audio interface is actually set to, and what Windows is set to.  I believe Windows defaults to 44.1k and 16-bits.  When I HAVE had a mismatch between sample rates, sometimes it would switch automatically and sometimes it would crash Windows - I cannot recall the specifics of what caused what, as it has now been years since I have encountered that situation.
 
Lastly - and this is only how and why "I" do it (some others do things like me and some do not):
 
I choose to have only Sonar and other high-end music applications use my audio interface - and its ASIO drivers, and I purposefully have the Windows Default Audio Device set to my either my on-board sound or to use the HDMI audio of one of my display monitors (which are HD TV's with HDMI ports and built-in speakers).
 
Running as described above stops there from being any conflict over access to the ASIO drivers of the audio interface, for me.
 
My usual mode of configuration is for Sonar (or an application like Dimension Pro or Kontakt running in  stand-alone mode), to point to the audio interface - using a driver mode of ASIO, and then I set Windows to use the HDMI of one of the display monitor TV's for the Windows Default Audio Device.
 
Once in a while, I will want to feed sound from Windows through the nicer speakers connected to the audio interface, and when I do that I use a cheap splitter device to split the mini-plug output from the computer's audio jack to 2 quarter-inch outputs that then are fed into the audio interface as inputs.
 
I have seen where once in a while someone will report that running as above has somehow caused them grief, but I have run as above for many years on multiple computers, with no issues whatsoever.
 
I hope that helps, 
 
Bob Bone