Blue Screen of Death possible solution

[Stephen Mann]

What version of Vegas and Windows??
A BSOD is almost impossible in Windows 7.

Steve Mann
MannMade Digital Video
http://www.mmdv.com

[George Tsiripas]

I tried it on Vegas 10, 11 and 12 on windows 7. All crashed with a Blue Screen of Death.

[Stephen Mann]

It was blue? A solid blue screen with no text on it?

Steve Mann
MannMade Digital Video
http://www.mmdv.com

[Ron Carlton]

I’m running Windows 7 64 bit and get the blue screen when rendering AVC files (or any other file for HD distribution). In my case I have 2TB HD, 16GB RAM, GeForce GTX560, Intel i7-3770. The video I am rendering includes about 100 JPEGs and about 4 minutes of HD video which makes a 20 minute video with WAV file for audio.

[Stephen Mann]

Blue? As in sky blue?
If so, you have a serious Windows problem. A Blue-Screen error in Windows 7 is remarkably rare because Microsoft put a lot of effort into better error detection than previous versions of Windows.

A Blue Screen is Windows version of ARF. (If you don’t know the acronym, then you are a youngster who never used DOS). Windows is saying “I’ve encountered an error and I have no clue how to fix or report it”.

Here’s Microsoft’s take on it:
Resolving-stop-blue-screen-errors-in-Windows-7

BSOD is almost always a hardware problem and sometimes a driver problem. Is the AVC encode the only time you encounter the BSOD? And what are you trying to encode? (Almost all formats we produce are encoded notwithstanding that Sony put the encoding options in the “Render As” menu). Have you tried rendering a non-encoded format like AVI? Which CODEC are you trying to use.

Please tell me that you’ve never installed a CODEC pack.

Steve Mann
MannMade Digital Video
http://www.mmdv.com

[John Rofrano]

[Stephen Mann] “BSOD is almost always a hardware problem and sometimes a driver problem.”

It should be noted that an application (such as Vegas) CANNOT be the cause of a BSOD. A BSOD can only be caused by a driver that the applications calls (or failing hardware) in which case it’s the DRIVER that’s the problem. Most driver related BSOD’s should have an error code and the name of the system file (driver) that caused it. You need to look up the code and see what it means. Most likely you’ll need to update the driver to fix it (unless it’s failing hardware in which case you’ll need to replace it).

For example, in the image below at the top left is the error message and at the bottom left is driver (ati3diag.dll) that caused the problem. In this example, it’s the drivers from an ATI Graphics card which is causing the system to BSOD (not Vegas).

~jr

http://www.johnrofrano.com
http://www.vasst.com

[Ron Carlton]

I think it is a driver causing the BSOD. I have the project on an external hard drive. On my newly minted desk top computer I get the BSOD about every 3 times I tried rendering the project, otherwise it locked up. On my laptop which is a year old…no problems. Difference is I cannot use GPU to process the project on the laptop, but on the desk top I can use the GTX560 (with the latest drivers). Next step…disable GPU processing on desktop…and it worked perfectly!

[Nigel O’neill]

My last BSOD was a related to a second video card driver I had updated (one of my systems had a PCI and USB video). I rolled it back and the problem did not recur.

I am wondering if rendering to a USB memory stick can be the result of driver issues, because when you plug in a device, Windows typically installs drivers for that USB device.

My system specs: Intel i7 970, 12GB RAM, ASUS P6T, Vegas Pro 10e (x32/x64), Windows 7 x64 Ultimate, Vegas Production Assistant 1.0, VASST Ultimate S Pro 4.1, Neat Video Pro 2.6

[John Rofrano]

[Nigel O'Neill] “I am wondering if rendering to a USB memory stick can be the result of driver issues, because when you plug in a device, Windows typically installs drivers for that USB device.”

Any hardware device with a bad driver can cause a BSOD so a USB stick can certainly cause this.

~jr

http://www.johnrofrano.com
http://www.vasst.com