X1 / X2 Crashes & Bad Behaviour - SOLVED

Excellent Post, Thanks Cliffr.

sharke
I realize this is a stupid question, but do you remove all traces of the old driver (e.g. with Driver Sweeper) before installing the new one?

 
Hey dude, there's nothing stupid about asking any question - what's stupid, is NOT asking when you there's something you don't know :-)
 
I didn't use any removal tool, the NVidia driver install gives you the option to either;
1)  Update (express install - their recommended)
2)  Custom install, which completely removes the previous version before installing - and loses all your settings.
 
I actually did both (with a full image restore between), with exactly the same results.
 
First time, I did the express install  - which I notices installs MS .NET framework v4, which I don't need.
 
Second time, (after restoring my system - Acronis) I did the custom install, and chose not to install the MS .NET framework v4, just in case that had anything to do with the really bad bahaviour.
 
I've updated the Nvidia driver two or three times since installing the card, never a problem until this driver version.
 
It screwed my weekend unfortunately - but on the flip site, fortunately that's all it screwed
 
What blew me away and why I posted here, was just how much and how badly it screwed Sonar, with the same damn nightmarish symptoms I see others reporting on this forum.
 
I'll tell you right now, if I hadn't known better, I would have cursed Sonar and Cakewalk, and wanted to throw the whole lot out the window - it was simply unusable. And you don't get any kind of friggin' hint what the real problem is - scary $hit if you ask me.
 
You know, this could have been "Cliff, with a brand new system, all the latest updates, that SUCKED, thinking it must be Sonar that Sucked".
 
It struck me, that Sonar doesn't need any fancy graphics hardware, and most people don't need fancy video software, so the best thing I could do for the community is simply post my experience, and suggest it could be handy to have an affordable alternate graphics card on hand, for when you're plaged with the badness and strangeness that makes no sense.
 
Hope that helps.
 
Cheers - Cliff
 

Great info.
 
Its this type of thing that goes some way to explain the why some peoples systems are stable and others experience frequent crashes. I experienced a period of crashing and buggy behaivour with Sonar 8.5. The problem - Paintshop Pro X. It installed some background software the loaded when Windows started. It appears that was affecting the stability of my system. I Killed those processes and Sonar behaved normally. Unfortunatly there appeared to be no way to stop them loading so I uninstalled Paint Shop Pro and the system went back to being rock solid apart from a very occasional crash of the ESI Juli@ drivers when two audio applications were open.
 
I now have a dedicated DAW and use my old box for other applications.

AWESOME info and responses.
 
I truly wish that more folks would understand the countless interactions that go into a computer system, not only from a hardware standpoint, but also from all of the installed applications software, as well as drivers - including BIOS, chipset, and device drivers.
 
There are LOTS of reasons Sonar can get whacked, where Sonar is actually a victim - just trying to carry Skittles back home from the store, only to have some reckless application have problems with its 'hardware profile', then crash Sonar, then claiming self defense.  When Sonar crashes, it can't defend itself - and all people know is that it crashed.
 
Sometimes, Sonar DOES quite clearly cause issues, and when they are severe enough, and wide-spread show stoppers, Cakewalk releases one or more sets of hot-fixes.  This happened with 8, X1, and X2, and I would venture to say prior releases as well, as needed.  PLEASE do NOT consider this post of mine as a launching point for another flurry of posts on update releases and all of that - it is my intent here to merely indicate that there are in fact system-specific conditions that can cause great grief and misery when trying to work with Sonar.  By posting those issues here in the forum, we have a collectively pretty good track record of getting to the bottom of a lot of those.  That is usually done by a combination of supportive and thorough discourse and diagnosis, and the occasional light bulb going off above our heads.
 
Sorry - that was fun.  The point is that it is often quite easy to overlook these complexities, and their potential for introduction of issues.  We see that all the time in the forum, where one person can't do this or that, and it crashes Sonar, where other folks do not have that result, even after literally performing the exact same steps.  Just hang in there when these kinds of things happen, and maybe between us all we can help each other find ways past them.
 
Sometimes, it just sucks to go through the pain of it, but that's how it all goes at times.
 
Bob Bone

 
 
I'm also wondering... what is going on with your computer that it is crashing Vegas?
 
If it can't run Vegas crash free then it hardly seems like that system can serve as a bench mark for making conclusions such as were posited in the original post.
 
best regards,
mike

mike_mccue
 
 
I'm also wondering... what is going on with your computer that it is crashing Vegas?
 
If it can't run Vegas crash free then it hardly seems like that system can serve as a bench mark for making conclusions such as were posited in the original post.
 
best regards,
mike

And to add, it's not "The computer can't run Vegas crash free".
 
A complete re-install of Sonar would simply be a waste of time - Sonar works extremely well.
As does AE, Vegas, the rest of the CS Master collection.
My system is VERY stable.
 
Either;
1) You didn't read my OP properly ?
2) You don't/didn't understand my OP ?
3) You think you're smarter than everyone else ?.
4) You like being unhelpful in other peoples threads ?
5) You just like to be a stick in the mud on the Cakewalk forums ?.
6) What else ... don't even tell me 'cos I don't want to know ?
 
Known bugs in Vegas were what caused the first issue.
And known bugs are what's causing the second hanging issue that still exists.
Do you know how many known bugs there are in Vegas Pro, let alone the ones that aren't know ?
 
You seem to enjoy poking a spoke in peoples threads around here rather than being helpful.
I'm not going to post the release notes of Vegas Pro here, if you want to know go and read them yourself.
 
If that's the best you can contribute, please go make your contributions somewhere else man.
You are not being constructive or helpful at all.
 
Goodbye !