Pinnacle vs. pinniped

Posted on

Pinnipedal Czar (: 3=
Member Since: Apr 11, 2004

Over the weekend, we decided to load our video softwares into our main audio compy, "the walrus", as we had a motherboard die in our video compy... Pinnacle 14, or somethingoranother. Things started out ok, but after a little bit we started encountering dropouts, which is something we haven't seen in MANY moons. Then... the BSODs started popping up, and crash after crash, I couldn't get the dang thing to boot up and stay running long enough to get the progs out that started this crap to begin with. So, after what seems like a hundred reboots, it stayed up long enough to get the progs off, defrag it, and do a few tests.... runs smooth as silk again.

Sheesh! That was nuts. For a moment, I thought we were going to lose the the DAW too! I guess the moral of this story is that you may be using what seems to be solid hardware for audio, but if the video software that you put on it is too advanced(new) for it... bad things can happen. haha!

I'm so glad we were able to save the walrus. Things have been so crazy around here with the move and all, that the last thing I need to be doing is building another DAW. : )

[ Back to Top ]

Pinnipedal Czar (: 3=
Since: Apr 11, 2004

Apr 21, 2010 12:43 pm

Nope... appeaently I was wrong. Even after removing the 'offending' programs, and cleaning it up, we're still having the same issues. I'm glad we back up as often as we do... gon'na try a clean slate(complete reinstall of all programs) to see if things will be helped by that.

Any words of wisdom would be greatly appreciated. It may be a coincidental hardware issue, as I've never heared of software doing actual damage to hardware, or not being able to be fixed by removing the program with issues. I'm stumped.

Since: Jul 02, 2003

Apr 21, 2010 01:03 pm

BSOD's are almost always hardware or driver related. Could be one of the codecs or drivers that Pinnacle installed is not completely removed which is pretty common.


Pinnipedal Czar (: 3=
Since: Apr 11, 2004

Apr 22, 2010 08:52 am


Thanks Dan... good to know, and very releaving to have some direction to head in that makes some sort of sense.I gues a cleaned-slate will do the trick, then. I was hoping it wasn't hardware related... things were running so smoothly before we went trudging off into unknown territory. : )

Since: Dec 04, 2007

Apr 23, 2010 11:42 pm

Hue, another thing you can do for future reference, is go into control-panel and system, go to the advanced tab, and click on settings for startup & recovery. you should see a checkbox called automatic restart under the "system failure" section. Disable it. That should cause the BSOD to remain on the screen so you can copy down the error code, and it usually has a file involved. Usually looking those things up are pretty vague, but sometimes they can generally point you in the right direction.

One of the reasons I had to build a new computer was that after x number of hours of operation, it got to the point where it would just start throwing a BSOD, and they slowly became more frequent. The cause was (supposedly) the dreaded ATI infinite loop error with the video card, which has some hex error code and the ati2dvag file associated with it.

After attempts at fixing the situation, I just decided the video card was on its last legs (being that it was an old 8x AGP card) so, I saved up and build a new compy to get with the times. I've had zero issues with the new machine. It was an old ati 9600, and I didn't have any other cards to test that thought, but disabling the card's higher-end video capabilities seemed to calm the issue down, so I figured the hardware was dying on me.

Hope that helps track down future instances of any problems (hopefully there won't be any problems though)

Pinnipedal Czar (: 3=
Since: Apr 11, 2004

Apr 27, 2010 08:43 am

Just noticed your post, J-bot. I will definately keep this in mind if the situation persists. What I've done thusfar, is to reinstall the OS, and all drivers for that DAW. This was easy enough, as all our audio files are on an entirely different drive, but still a pita. I am now dealing with an issue that I had forgotten about since the last time I did this... M-Audios 'newer' drivers doesn't like my hardware and I had to roll them back for things to work right. I've tried some new buffer adjustments, and things are playing well, but I haven't recorded with it yet, so... we shall see. Thanks J-bot.

I've got to move this weekend, so it'll be a while. : )

Side-note: I can't wait to get to this new house! New studio, with no terrible neighbors. Hells yes!

Related Forum Topics:

If you would like to participate in the forum discussions, feel free to register for your free membership.