give the poor guy a break (or a copy of ppro / fcp). there's obviously something amiss with his set-up since for all the 'quirks' everyone has mentioned so far NONE have been BSOD's.

in general, i've found BSOD's signify driver problems, or hardware. i think that's where he should be looking.

but hey, if he needs to vent...

leslie

Hey Guy, I hear your pain. Go for a long walk and think of good things. I'm sorry, I can't help. I wish I could.

At present, this chappie is staying with 8b and the pending client's job, till it's signed-off done and invoiced for.

I am aching to try out the Trimmer Previewing options - sounds great!

Grazie

Sebaz - seems you are the only one with the issues from what I can tell - I am of course working with HDV content shot on SONY HC7's (Sony software, sony cameras - keep it as straight forward as possible) - the only issue I have had was the red / black frame bug which was resolved with the updated m2t update that was released before 8.0c/8.1 - I have 8.0c/8.1 installed on both my Dell D620 Latitude laptop and my Beige box Intel Quad core desktop - both running x64 XP Pro. No BSOD's, no issues so far.

Your issues are around hardware - IRQ less than 0 is hardware/driver related.

Cliff Etzel - Solo Video Journalist
bluprojekt | SoloVJ blog

To some extent I have to agree with what's said above, you could be having hardware issues. Certainly you need to eliminate that possibility first and foremost.
There's no shortage of free hardware stress test software around, check out any of the OC'er forums for links or else do a Google. RAM is one thing to give a thorough pounding. I had one PC develop wierdness that was fixed by nothing more than reseating the sticks. Try that and try swapping them around and see if that changes the symptoms.
Having eliminated hardware then you need to consider that you have an OS problem. After my scary brush with XP SP3 last night that I hope I managed to backout of I still have a wierd problem on that PC. I bought and downloaded the latest version of True Image and damn it all the installer will not run on that one PC. I mean I double click it and NOTHING happens, and just for giggles Acronis is in the midst of a server upgrade so trying to get support is impossible!

Now once you've checked out all those possibilities THEN scream for help. You might well have found bugs no one else has. The only way to know this for certain is to get someone else to try to repo the problem with the same project and same media. If you can get things to fall apart with just a few seconds of media on the T/L then this should be easy enough. There's plenty of ways to shoot upto 1GB of data around the planet these days.
I'd hope that someone whose been brave enough to install the latest release will be kind enough to put their hand up to help out. Between you and a few others here either your problem should be diagnosed or you can all take a pat on the back for finding a bug for SCS.

Bob.

OK, I'm not saying that a hardware issue is totally out of the question, but if it is, then why this crashes never happened under 8.0b and they started right away under 8.0c. That makes obvious to me that this latest update is to blame. It probably access the hardware in a way that it shouldn't.

Look, if these programmers have such poor attention to detail that they left an NTSC template with PAL selected in its settings (and there's at least one person in this forum who got a dud DVD because of it) and they put a browse button that doesn't update your selection (in the Burn to Blu-ray option), then what can you expect of the code itself? It's obvious that this is a rush job, and it doesn't work.

I would even go as far as cleaning up a hard drive and installing either Vista or XP completely clean and then Vegas, but if I'm going to have to be calling Sony every time because the stupid server rejects my serial, forget about it.

do you have the latest nvidia display drivers installed?

do you have the latest nvidia display drivers installed?

I had when I first installed 8c, then thinking that the crashes might be related to the drivers, I uninstalled them and let Vista use its own driver for my card. I tested 8c for a while, with the same results. Crashes all around. I went to eVGAs website and downloaded the previous drivers for my card (for some reason they haven't posted the latest version that is on Nvidia's website). Same results with their drivers.

The only time I got BSODs in Vista 64 was due to hardware issues:
1) Faulty Memory Stick: Luckily Vista 64 comes with a memory checker and I used it to find the faulty stick. I pulled them all out and put them in one at a time. If no errors were reported, I would put in the next stick until I found the faulty one. Once I replaced the faulty stick and rechecked with the memory checker, all was good. It should be noted that I got the memory issue about two weeks after upgrading all my RAM so even if you checked them when you orginally put them in, it is worth checking again.
2) DVR Card Failure: My TV tuner card died and I would get BSOD when I tried to upgrade the drivers. I haven't removed this card from my system, but Windows has disabled it.

Faulty / dodgy memory seems to be the cause of a lot of grief on all platforms including Macs. Not that I know that many Mac users but the two I know best have both had issues with RAM. Nothing to do with Mac hardware, just the nature of RAM.
I suspect you can have dodgy RAM and not know about it for years. Then you run some app that uses the faulty chunk of RAM and all hell breaks loose.
Back in the days when I understood and worked on this stuff we'd have RAM with a two shorted address lines and it was amazing how much the system would run and nothing go wrong....for a while.

All I can say Sebaz is do yourself and the rest of us a favor, start doing some hardware testing. I'm not saying Vegas isn't a POS but until you eliminate all other possibilities, for obvious reasons you'll not get much sympathy.

I switched from Premiere to Vegas years ago because Premiere crashed more than I liked. But guess what, although Vegas has run just fine on that hardware I eventually found out why Premiere was crashing, the hardware was as dodgy as it gets. Vegas has been about the ONLY app that wouldn't crash on that system, even CD Architect crashes on it from time to time.

Bob

Bob said: There's no shortage of free hardware stress test software around, check out any of the OC'er forums for links or else do a Google.

After googling around I have found some (free ones) that seem to only check parts of the system and/or have mixed reviews.
Can anyone recommend (or even better provide a link) for one of these stress tests that do it all?
I would very much appreciate it!!!
TIA,
Randy

if you have a 3d card 3dmark does the GPU + CPU.

" OK, I'm not saying that a hardware issue is totally out of the question, but if it is, then why this crashes never happened under 8.0b and they started right away under 8.0c. That makes obvious to me that this latest update is to blame. It probably access the hardware in a way that it shouldn't.

I think you're a bit too quick to blame the program. I was having trouble with 8.1 and I did a complete reinstall of vista and installed 8.1 ONLY... no other programs.... no other codecs. It's now running fast and accurate. I have Not had a crash as of yet in 8.1 (or 8c yet for that matter). Both are now running stable and even. Granted I'm doing HDV and not avchd, but my advice to you is to do a complete re install as I did and then try again.

As for registering and serial numbers.... I've installed 8c three times and 8.1 seven times in the last 24 hours and i have not had so much as ONE registering issue yet.

I find it quite interesting that it is only you that is having these show stopper issues..... and so should you. Sorry.... I don't mean that sarcastically, but logically speaking, it's a pretty clear indication that the problems you are suffering are unique to your set up.... a hardware conflict or a software conflict of some kind.

> I don't have any deadline and losing money on this, because in that case I would be calling some lawyer.

Actually you should be reaching for your backup. I had an issue when I originally installed 8.0c where I could not run any scripts. I uninstalled and re-installed 8.0b and I still couldn't run any scripts! I restored my PC to the previous days backup and I STILL couldn't run any scripts. Hmmm... I restored to 2 days prior and all my scripts ran again. I proceeded to install 8.0c and it worked perfectly!!! So something completely unrelated changed on the prior day that caused scripting to stop working and I was all ready to blame 8.0c when it apparently wasn't the problem.

If you don't do a daily incremental backup of your C: drive I strongly suggest you start. If not, at least do a full backup before installing new software. Calling a lawyer will do no good. I will bet the EULA you agreed to says that you can't sue Sony for productivity or work lost. Every software company has this clause otherwise they couldn't stay in business.

> I made under 8.0c, just two AVCHD files and scrubbing the timeline for less than a minute, gave me a IRQ_NOT_LESS_OR_EQUAL BSOD, twice.

It is physically IMPOSSIBLE for any application to cause a BSOD. The only code that can do that is code that runs in the kernal and that includes device drivers. So an application can use a device driver that causes a BSOD but it is NOT a problem with the application. It is a problem with the device driver.

You need to look on the bottom of the BSOD screen for the name of the device driver file (dll or sys) that is causing the problem. Then seek a fix for it from the manufacturer. There is a problem with your hardware or a device driver and Sony only uncovered it... they did not cause it.

~jr

if you have a 3d card 3dmark does the GPU + CPU.

Thanks Hap but I don't have a 3D card (in case it matters, I have a NVidia GeForce MX440)...at the risk of being a PIA can anyone else suggest one?

I find it quite interesting that it is only you that is having these show stopper issues..... and so should you. Sorry.... I don't mean that sarcastically, but logically speaking, it's a pretty clear indication that the problems you are suffering are unique to your set up.... a hardware conflict or a software conflict of some kind.

Once again.... Crashes didn't happen in 8b, they started happening in 8c. Pretty clear to me who's the culprit here.

It's not clear to me at all. 8.0C is going to push your CPU, memory, and hard drives harder and any overheat problem (FAN), memory chip leak, harddrive glitch, motherboard glitch, Norton software, auto updated software, etc will raise hell with your rendering.
JJK

8.0C is going to push your CPU, memory, and hard drives harder and any overheat problem (FAN), memory chip leak, harddrive glitch, motherboard glitch, Norton software, auto updated software, etc will raise hell with your rendering.

Why would 8.0c increase processor usage compared to 8.0b? And in any case, if you were correct, when I rendered several things with 8.0b with the four cores running at close to 100% (which I would definitely call pushing the CPU), it didn't crash.

I'd probably start by running with one stick of memory at a time to see if one of them is the culprit.

Rob

The other part of your PC that could be causing grief is the power supply. Changes in code that alter the timing between CPU, GPU and disk operations could unmask power supply issues.

Bob.

I will guess you have bad ram. You should download the memtest86+ iso and boot from it to test the memory..

http://www.memtest.org/download/2.01/memtest86+-2.01.iso.zip

Best Luck!

Andy

"Once again.... Crashes didn't happen in 8b, they started happening in 8c. Pretty clear to me who's the culprit here."

You keep (conveniently) ignoring the fact that it seems to be happening only with you. Just because 8b is not crashing while 8c is (for you only) means little.

Once again.... do a complete re install and take it from there. If that doesn't help then I would start replacing memory sticks one at a time. For testing purposes, remove ALL unnecessary hardware ESPECIALLY usb devices... they can be a major culprit in crashing. A weak usb cable with a nick in the shielding can cause absolute hell. Again for testing purposes... if you're overclocked then bring the speed back down to stock and try it that way. If you have a Nvidia card then go the site and make sure yours is not on the list for overheating problems (Nvidia has a bad load of chips out there)

I am beginning to agree with Sebaz.

I originally installed 8.0b from the B&H CD about two weeks ago. I did have some original problems with crashing (could never get it to render out anything using the Cineform codec)..

When 8.1 x64 came out the other day I installed it along side 8.0b. Once I discovered that none of the 32-bit plugins work (i.e. free Sony Vegas Looks HD that would allow you to upgrade to the full MBL for $99) and other problems that I'm not quite remembering right now, I uninstalled 8.1 and focused back on 8.0b.

Then I got the hairbrained idea that I would try the 8.0c and see if that was any better. Since I've upgraded (i'm running Vista x64 btw) I've had nothing but crashes. I have yet to reneder a single file.

I've been trying to simply take two clips < 30 secs long each from my Canon HF100, do some quick color correction then render them out using Sony AVC - HD NTSC 1920x1080. Every thing cruises along and then the system "stops working" and Vegas shuts down.

So I tried a new timeline. Very simple. Same render type and I get this error about 3 mins into the process:

System.InvalidOperationException: Invoke or BeginInvoke cannot be called on a control until the window handle has been created.
at System.Windows.Forms.Control.MarshaledInvoke(Control caller, Delegate method, Object[] args, Boolean synchronous)
at System.Windows.Forms.Control.BeginInvoke(Delegate method, Object[] args)
at Sony.MediaSoftware.Kernel.Threading.WorkerBase.DispatchCompleteEvent(WorkerCompleteEventArgs completeArgs)
at Sony.MediaSoftware.Kernel.Threading.WorkerBase.DoWorkWrapper(Object genericArg)
at System.Threading._ThreadPoolWaitCallback.PerformWaitCallbackInternal(_ThreadPoolWaitCallback tpWaitCallBack)
at System.Threading._ThreadPoolWaitCallback.PerformWaitCallback(Object state)


So after hearing what happened to Sebaz I don't want to completely uninstall and try to go back to 8.0b and risk the whole key issue. I've been able to render one single video and that was on 8.0b. http://www.vimeo.com/1693526

Since then, nothing but crashes and burns and hassles and aggravation.

Btw, my PC is brand new. Just built it on an Asus P5E, Intel E8400 (that I used to oc to 4Ghz but set all back to normal to make sure that wasn't causing the crashes), 4GB of DDR2-800, 8800GT card.