program crashes help

MemoriesFX wrote on 6/20/2011, 3:59 PM
I suddenly cannot render anything in Vegas Pro 9. As soon as I select render the program crashes.I am thinking I should just re-install but thought I would post here for help first. I have to render a job for a client and this is driving me nuts now. It started when I tried to render to a wmv file format and since then it seems cursed.

Steve

Comments

Steve Mann wrote on 6/20/2011, 9:06 PM
"Crash" is an extremely broad subject. Does the program crash or is Windows crashing? What error message do you get? Does it make toast or do the laundry?

"My car stopped" provides the same amount of information that "Program crashes" provides.
MemoriesFX wrote on 6/21/2011, 6:06 AM
Good point Steve. It is Vegas that stops working as soon as I select render. The message is that Vegas has stopped working and in the problem details there is this info
Problem: Unmanaged Exception (0xc0000005)
Fault Module: C:\Windows\SysWOW64\ntdll.dll
Fault Address: 0x00000000773A3075
Fault Offset: 0x0000000000033075

Steve
SWS wrote on 6/21/2011, 8:01 AM
This may not help in your situation but it helped me with my weird Vegas 10d crashes.

Do a Vegas "reset to default values"

Close the program. Now press CTRL+SHIFT while double-clicking on the program's icon to launch it. Continue to hold the CTRL & SHIFT keys until the program is fully up and loaded.

In newer programs, you will see a window that asks "Do you want to reset all preferences to default values?" Place a checkmark next to "Delete all cached application data" and then click Yes.

BOXX/APEXX S4
Motherboard: ASRock TAICHI
Intel Z690 Chipset Cores:16
CPU: Intel Core i9 12900KS Enhanced Performance Processor
GPU: NVIDIA GeForce RTX 3090
RAM: 64GB DDR5-4800 MHz (2 - 32GB DIMMS
Disks: 2.0TB SSD NVMe/PCIe 3.0/4.0 M.2 Drive
SSD: (4) 4TB
O/S: Microsoft Windows 10 Professional 64-bit SP1

Steve Mann wrote on 6/21/2011, 9:46 AM
An unmanaged exception means that Windows encountered an error condition that no process has a handler for. We used to call this the BSOD (Blue Screen of Death).

WoW64 (Windows 32-bit On Windows 64-bit) is a subsystem of the Windows operating system that runs 32-bit applications and is included on all 64-bit versions of Windows. Wow64.dll is the core interface to the Windows NT kernel that translates between 32-bit and 64-bit calls, including pointer and call stack manipulations

Are you running Vegas 32-bit?? Why?? Are you using a 32-bit plug-in? I would want to know what 32-bit process you are running that is calling the WoW64 dll's.
MemoriesFX wrote on 6/21/2011, 8:20 PM
Wow you know your stuff Steve. I am running Vegas 64 bit as far as I know (I am away for the evening so not in front of my machine). I might be running some 32 bit plugs ins from New BlueFX but they were installed way before I had this problem. I am not sure what the WoW64 dll's is. How would I find that out?

Steve
Steve Mann wrote on 6/21/2011, 10:39 PM
I was a programmer in a former life. Most of my inside-Windows information comes from http://technet.microsoft.com

Try a small test "render as" on a simple project with no FX. Then add some NewBlue FX and see if the problem happens again. I am pretty sure that you can't run 32-bit plug-ins on Vegas 64-bit.
MemoriesFX wrote on 6/22/2011, 8:38 AM
Just tried this solution and it is not working.

Steve
Steve Mann wrote on 6/22/2011, 3:08 PM
Same error?
Try creating a new project with only a few seconds of generated media (like a test pattern). No video or audio media.

If the problem persists, then reinstall Vegas.
MemoriesFX wrote on 6/22/2011, 5:14 PM
Nothing is working, I will re-install now, thanks for helping out
MemoriesFX wrote on 6/22/2011, 5:30 PM
I fixed it. I tried again to apply SWS's suggestion and it worked this time.
brant wrote on 6/22/2011, 5:39 PM
I have a similar problem - except mine crashes while doing any text operation, such as Placement, changing Font size, etc.

It seems to have started right after a Win7 (64 bit) update last week - that's the only thing that has changed on my system.

If I create a new project, this does not happen. But if I open ANY previously created project and do a text operation - they all crash. Every single previously created project! Seems like the only way out of this is to open an old project, do a "save as new-name ". Then it works..... until I shut the machine down, and open it again later = crash on the newly named file.


Here's the dump: (The logs are of no use).

File: C:\Users\brant\AppData\Local\Sony\Vegas Pro\9.0\dx_video_grovel_x64.log
File: C:\Users\brant\AppData\Local\Sony\Vegas Pro\9.0\dx_grovel_x64.log
File: C:\Users\brant\AppData\Local\Sony\Vegas Pro\9.0\vst_grovel.log
File: F:\bear_play.veg

Problem Description
Application Name: Vegas Pro
Application Version: Version 9.0e (Build 1146) 64-bit
Problem: Unmanaged Exception (0xc0000005)
Fault Module: C:\Program Files\Sony\Vegas Pro 9.0\vegas90.exe
Fault Address: 0x0000000140376B6F
Fault Offset: 0x0000000000376B6F

Fault Process Details
Process Path: C:\Program Files\Sony\Vegas Pro 9.0\vegas90.exe
Process Version: Version 9.0e (Build 1146) 64-bit
Process Description: Vegas Pro
Process Image Date: 2010-05-12 (Wed May 12) 18:59:16

Anybody - Any clues/fixes? Seems like a lot of this going around....
I've filed a ticket with Tech Support.
Presently updating my display drivers.
brant wrote on 6/22/2011, 5:48 PM
I just did a "reset to default values" - that appears to have fixed mine also.
Thanks,
Steve Mann wrote on 6/22/2011, 6:51 PM
Thanks for the reminder - I'll add that to my list of easy things to try.
Flyer Curt wrote on 7/28/2011, 8:00 AM
I just had the same thing happen with VMS11p while trying to render a BluRay file. Got the "unmanaged exception" error and program shut down. It would not restart - kept getting the same error message. I tried reloading VMS11P, then uninstall and reload - no help.

The CTRL-SHIFT start worked for me to fix the problem. Wish I had looked at the Forum earlier - now I have to redo the memory cap patch.

Curt
SWS wrote on 7/29/2011, 7:25 AM
Well... Tech Support reminded me of the "reset" fix. So I guess they're good for something! ;-)

BOXX/APEXX S4
Motherboard: ASRock TAICHI
Intel Z690 Chipset Cores:16
CPU: Intel Core i9 12900KS Enhanced Performance Processor
GPU: NVIDIA GeForce RTX 3090
RAM: 64GB DDR5-4800 MHz (2 - 32GB DIMMS
Disks: 2.0TB SSD NVMe/PCIe 3.0/4.0 M.2 Drive
SSD: (4) 4TB
O/S: Microsoft Windows 10 Professional 64-bit SP1

soundgod wrote on 12/31/2012, 12:32 PM
Well, it's nearly 2013 and this is a bit of a zombie thread, but I need to thank you SWS. I hit the same wall yesterday and was about this close to doing a reinstall because none of my .m2ts projects would render more than 30 seconds before triggering the exception.
You really helped me stop tearing out my few remaining hairs.
I did have to do the reset twice like someone else reported and I'm happy to report, it looks like all my custom presets were kept.
Happy New Year.

By the way, I'm running Vegas 11 Build 701 64 bit. Nothing else matters for now.

Steve, it neither makes toast or does laundry.
However, it is a delicious dessert topping AND a floor wax.
Convergence comes to the kitchen.
http://www.hulu.com/watch/61320