I'd second those saying a BSOD most likely indicates a non-Sonar issue.

It would be very useful to know what the BSOD says. They usually tell you the name of whatever has caused the crash/misbehaved and the hex error code (seen as 0x - followed by eight numbers/letters) can often also go a long way towards tracking down the problem.

You don't need a crash dump to get that info, but you do need to set the PC so it does not automatically restart if Windows blue screens (auto reboot is the default). That way the BSOD stays up until you reboot, rather than you seeing a flash of blue then an automatic reboot. You do this in Vista via control panel-system-advanced properties; where it is in Win7 I don't know, sorry.

Just to clarify, yes there is info available on the BSOD but the mini crash dump using the tools I suggest will get you far more info. The BSOD is unspecific mumbo jumbo to most normal people, the mini dump will tell you exactly what caused it in plain English (mixed up in a lot of mumbo-jumbo).

Fixing it might be a little harder though..........

Given the MIDI problems I would start with the midi interface drivers.

A couple years ago on my computer the MIDIYOKE file became corrupted and resulted in BSOD. And It would not uninstall.

I remember hearing myself say many short words very loudly.

This was a non-hardware "Driver."

Last year a ram chip became depressed. Had to send it for a theraputic replacement.

J

Yep, I agree with Jim Roseberry's assessment.  BSOD's are definitely related to either a bad driver or a bad device.

Windows 7 64 bit is rock solid, so if you're getting BSOD's, the proper course of action is to find the problem and fix it.

Chances are not likely that this is the fault of either Windows or Sonar.

Two things to check, in my experience:

1.  Ensure that the correct and current graphic driver is installed.
2.  Either shut off the 1394 FireWire features in the BIOS or else rollback the 1394 Firewire driver to "Legacy Driver".  If you have no FireWire devices, do the former.  If you do, then do the latter.  They will still work with the legacy driver.  And yes, you might need to do this even if you just installed W7.  Don't ask me why, I just know that this worked for me.

Other helpful items:

** Just reading the dump code off your blue-screen and Googling it can be very helpful. 7F or 7D or whatever the code, plus the accompanying status words all make for good Google search terms.

** You can get a free minidump reader with a few google searches.  I use "Bluescreen View".  You don't have to be an expert dump reader or an OS programmer to figure out some stuff here.  This can shed a lot of light on what may have caused a crash, and this is how I found out my firewire problem above, which I later confirmed by unplugging my Firewire interface and temporarily installing a USB sound interface.  The bluescreens stopped!  So that was my first clue, and I followed up with Google searches and a query to the device manufacturer's support people.  Even though their interface device driver was not at fault (it was the fault of the FIREWIRE driver and not the driver provided by the device manufacturer) they were able to instruct me on how to roll back to the "legacy driver".

Information is your most important tool here.  Once you get it fixed, you'll be a lot happier.  I've always said if you can fix your 2 or 3 worst problems, you'll feel a 95% improvement. 

Get a dumpreader and be willing to read between the lines.  Or call Jim Roseberry! 

stratman70

bigboi


So,  I was under the impression that loading Sonar 8.5 AND X1 at the same time either would not work, or was just a bad idea.  Can I load both of these?  Anyone else using them both?

Been doing that since it came out. No issues at all. I do try and save a project in the version I am in.

Load, as in "start?"  Or load as "install?"

I agree the ID of the client is moot. Sheesh it could be Johnny McNobody for all I care, if they're a potential client (read: $$$) then putting your best foot forward is pretty key.

Sheesh that notwithstanding it could be my crazy uncle Bob who just wants a place to get out of the rain, I STILL want to put my best foot forward (maybe in uncle Bob's ass, that freeloader!)

All that said, yeah did into your system, there's a conflict somewhere.

Recently, my firewire started acting up, I think the Firebox and the GPU are not quite agreeing and I get occasional BSODs, but I unplug the Firewire and restart and it's fine. Oddly, I also have to reset the resolution on one of my displays. It's always something...