VariousArtist
Sorry to hear about your woes Mod Bod. I know that, from time to time, I have used an older version of Sonar because a certain project just doesn't want to play nice in a more recent version.

That being said, it is highly unlikely that a BSOD is tied to a specific version of Sonar. More specifically it is a hardware issue that might be quite random, and if it appears to be related to any software then the fault still lies with the hardware.

It's hard to take a screenshot when you get a BSOD (to say the least!), but next time it happens can you take a photo (e.g. with your phone) and post it here? At a minimum, try to make a note of what the first couple of lines say, and maybe we can help nail down the true underlying cause.

For more info:
http://repairpcguide.com/...ath-and-how-to-fix-it/

I wrote down the stop code if anyone knows how to make sense of that.

What is the stop code? Better yet, why not check it directly here:

http://pcsupport.about.co...tp/stop_error_list.htm

Purely as a troubleshooting suggestion... I suggest that you reseat the memory and the pci/e cards in your computer.  I have had times where that corrected hard to find problem.
 
Hope you get it sorted. 

Mod Bod, I'm almost to that point, too. Crash, crash, crash. This is the most unstable Sonar I've personally ever dealt with. I'm still working on things here on my end to make sure it's not my issue but, I've NEVER had this much trouble with ANY new version of Sonar.

One of the best, free tools for diagnosing BSODs is BlueScreenView.  I've lost count of the number of problems I've fixed with this tool when a BSOD has had me stumped.  Google it and you'll find it - Nirsoft BlueScreenView - very handy.
 
Give it a go.  But here's the thing.  A BSOD can only really occur due to something happening in kernel mode.  Sonar operates solely in user mode.  That said, device drivers operate in kernel mode.  Also, some AV products have a kernel mode component.

BRuys : ???

I know quite a few guys are hell-bent on 64 bit programs. To be honest, Sonar has always given me issues in 64 to where I use 32 bit exclusively. I never have a problem with it. Put me on 64, and the weirdest things happen to me. From weird issues with my preferences totally disappearing to teleport server crashes, strange anomalies, 64 bit VSTi's not particularly liking Sonar, live templates that are flawless in Sonar 32 at 64 and 32 samples via ASIO that crack, pop and are un-useable in Sonar 64....the list goes on and on for me. Anyone experiencing 64 issues...just try 32 bit to see if it makes a difference for the better. At least if you contact Sonar support, you can tell them that you believe it's 64 related.
 
Mod bod: If it's any consolation, a version of ARC will not work in X2 yet works perfectly in X1. If you use any older versions of plugs, that could be the reason. There are so many variables...it can get you down and like you, I too do not have the time for trouble-shooting. So I have special pc's built that have 8.5, X1 and a few other perfectly working versions of other software on them. I never touch them. I never update, upgrade or mess around with anything on them. I fire them up, I get my work done, I'm happy.
 
-Danny

Mod Bod

VariousArtist
Sorry to hear about your woes Mod Bod. I know that, from time to time, I have used an older version of Sonar because a certain project just doesn't want to play nice in a more recent version.

That being said, it is highly unlikely that a BSOD is tied to a specific version of Sonar. More specifically it is a hardware issue that might be quite random, and if it appears to be related to any software then the fault still lies with the hardware.

It's hard to take a screenshot when you get a BSOD (to say the least!), but next time it happens can you take a photo (e.g. with your phone) and post it here? At a minimum, try to make a note of what the first couple of lines say, and maybe we can help nail down the true underlying cause.

For more info:
http://repairpcguide.com/...ath-and-how-to-fix-it/

I wrote down the stop code if anyone knows how to make sense of that.

 
This is written for Windows XP but all Windows versions are almost identical. It just requires your Windows version of the debugger. Won't fix it but at least you'll know what needs fixing.
 
How to decipher a BSOD
 
HTH

Dave, I am using the RME Fireface UFX. It is portable and stand alone. It also has onboard fx for hardware outputs. Great for monitoring live situations and recordings.
I feel you. I have to often go back to X1 or 8.5 to get projects done. X2 is not what it is supposed to be. Roland could have done much better.

Hi Dave
Sorry to hear about these problems.
I upgraded to X2 when first released, but had some strange graphical issues, so went back X1 pretty quickly.
Loaded the X2a patch, but I didn't think it addressed the graphical weirdness, so just kept using X1.
That was many many months ago, and to be frank until a proper bug patch is released, I shall just stay with X1 - X1 is a mature and stable product for me - in the short time I did use X2, on reflection there was nothing feature wise that would really make me want to change from X1 = stable   to X2 = glitchy.
 
With regards to soundcard, I have an RME Fireface 800 - the first one I had after MUCH hassle and some not very good customer support was declared faulty - luckily I had purchased this from Sweetwater and they ended up sorting it out for me - RME themselves were unimpressive to say the least.
I also now have a MOTU 896 Mk III - better product I think and a MUCH better company to deal with.
 
Hope all gets sorted
Nigel