Vegas V12 crashes when selecting "Render As"

ShaneJ wrote on 1/15/2013, 8:23 PM

I have been using Vegas V12 for months since it was released and had no problems initially until today. For some reason whenever I select "Render As", Vegas crashes and I get the error reporting screen. I have uninstalled Vegas and ran registry cleaners (CCleaner and Advanced System Care Pro) perfoming deep registry cleans to remove any bad registry keys or any other errors. This usually does the trick if I have problems with other software. I did this after uninstalling Vegas V12 and rebooting. I rebooted several times after that and running more registry cleaning scans before rebooting the final time and reinstalling Vegas V12. Problem still persists. Don't know what else to do. Please help. I cannot get ANY work done if I can't render. This is really frustrating. Don't know why it's doing this all of a sudden. Haven't really done anything drastic to my computer since the last time it worked other than installing a new piece of hardware. An internal USB 3.0 PCI Express card for an internal multi card reader. Could that have done something? I'm using Windows 7.

Here is the problem details I got in the error reporting screen when Vegas V12 crashed. Maybe this will shed some light onto the problem for someone out there who knows how to deal with such situations. Any and all help would be greatly appreciated. Thank you.

Extra Information
File: C:\Users\ShaneJ\AppData\Local\Sony\Vegas Pro\12.0\dx_video_grovel_x64.log
File: C:\Users\ShaneJ\AppData\Local\Sony\Vegas Pro\12.0\svfx_video_grovel_x64.log
File: C:\Users\ShaneJ\AppData\Local\Sony\Vegas Pro\12.0\ocio_x64.log
File: C:\Users\ShaneJ\AppData\Local\Sony\Vegas Pro\12.0\dx_grovel_x64.log
File: C:\Users\ShaneJ\AppData\Local\Sony\Vegas Pro\12.0\vst_grovel.log
File: C:\Users\ShaneJ\AppData\Local\Sony\Vegas Pro\12.0\gpu_video_x64.log

Problem Description
Application Name: Vegas Pro
Application Version: Version 12.0 (Build 394) 64-bit
Problem: Unmanaged Exception (0xe0434f4d)
Fault Module: C:\Windows\system32\KERNELBASE.dll
Fault Address: 0x000007FEFE069E5D
Fault Offset: 0x0000000000009E5D

Fault Process Details
Process Path: C:\Program Files\Sony\Vegas Pro 12.0\vegas120.exe
Process Version: Version 12.0 (Build 394) 64-bit
Process Description: Vegas Pro
Process Image Date: 2012-10-26 (Fri Oct 26) 17:11:42

Comments

John_Cline wrote on 1/15/2013, 9:30 PM

What are you trying to render? MP4? If so, turn of GPU rendering.

Also, Registry cleaners can potentially mess things up. Use them with caution.

ShaneJ wrote on 1/15/2013, 9:37 PM

I can't even get far enough to render to anything. Just clicking on "Render As" causes the crash.

barfnuts9000 wrote on 1/15/2013, 11:11 PM

Judging by your symptoms, I doubt it's a Vegas issue and more of a Windows issue. I have had issues like this in the past with random programs crashing for no reason (with that same KERNELBASE.dll), and after many hours of taking out my frustrations on my poor keyboard, the only thing that fixed it was to create a whole new profile in Windows (it turned out to be corrupted).

Try creating a new user in Windows, and then run Vegas (if it was installed for "All Users". Use the Run As Administrator just to be on the safe side.

Hopefully that's all it is, and if so, then you may unfortunately may need to remake your windows profile under your new name.

ShaneJ wrote on 1/16/2013, 12:38 AM

Of course I'd rather not have to do that, but I guess it's better than reformatting and reinstalling Windows 7. Is there any other way to maybe restore the currupted kernelbase.dll file than making a new profile?

barfnuts9000 wrote on 1/16/2013, 2:22 AM

You can try extracting it from your Windows DVD. I would heavily recommend against downloading any DLL's off of the internet.

Are you having any other issues with other software? Are you sure you're not infected with a virus of some sort?

Mark_e wrote on 1/16/2013, 2:52 AM

Have a look in the windows event logs see if there is some additional information at the same time you get the 0xe0434f4d generic error.

I had a similar issue with the explorer tab, I wonder if it's related especially given your comment about adding the USB3 card.

What happened was I had explorer pointing to a drive that I had removed when setting up a scratch disk, when I started up vegas explorer was empty and crashed when I tried to type a folder name in the search bar (none of the browse buttons worked) tried reinstalling but the legacy drive must have been in the registry somewhere and it didn't fix it. eventually I just types c: in the search bar and it managed to find the file structure and it started working again.

So I was wondering, perhaps you had the last render accidentally set to the new USB drive and as there's nothing there it crashes, or something like that. See if there are extra details in the windows event viewer and if it point to some sort of file issue we might be onto something.

dxdy wrote on 1/16/2013, 6:27 AM

I have had V12 crashes at the same point, and found that I was rendering to an external USB drive and it had gone to sleep. I had to access the drive with Windows Explorer to spin it up, and then the render would work okay.

ShaneJ wrote on 1/16/2013, 8:46 AM

Mark and dxdy, those are very interesting points. Before I installed the USB3 card for the new internal multi card reader, I was using another multi card reader that was connected to a USB header on the mother board (originally used for the front case USB ports). I got the new card reader and PCI Express card so that I can connect the front case USB ports again. When I was last rendering before I made these hardware changes, I might have been rendering from a file that was on a card in the previous card reader. Perhaps Vegas is still looking for a file location from the old card reader. Very much like the issue Mark had.

When I get home tonight, I'll temporarily take the USB3 card out and see if that alone makes any difference, and if not, I'll reconnect the old card reader again and see if that helps. If it does, then I'll just open up a new project from my hard drive and render a quick clip to make the software point to the hard drive.

I'll check back here with my findings either way. Thanks for the advice guys. Now the anticipation of waiting to get home from work tonight to try this. lol

Laurence wrote on 1/16/2013, 8:55 AM

I get this exact crash if I have any preview RAM set aside, not every time, but almost every time.

Here is the situation on my PC:

1) RAM preview memory set aside and GPU on: Vegas totally unstable for both editing and rendering.
2) RAM preview memory set aside and GPU off: Editing is stable but Vegas crashes when I try to render right before the render properties screen comes up.
3) RAM preview memory off and GPU off: Both editing and rendering are stable.

I am using a USB3 drive for editing. My PC is an all-in-one Lenovo which has no other options for external disk storage.

ShaneJ wrote on 1/16/2013, 9:24 AM

Thank you, Laurence. How do I get to these RAM preview settings? I've never touched these settings before.

ShaneJ wrote on 1/17/2013, 8:22 AM

Yeah so, no dice. I took out the USB3 card first and booted, tried to render in Vegas with same results. Hooked up my old card reader, for some reason my old card reader is dead. No idea why. Only had it a month and a half before I decided on the new one. But whatever. I doubt it had anything to do with Vegas pointing to a drive on the old card reader anyway. I even tried what barfnuts9000 suggested with creating a new user profile in Windows and run Vegas as administrator. Same results. Crashes the software when I select "Render As".

Don't know what else to do. I've reset my bios and disconnected an additional hard drive I had in there and everything. No dice. Only other option I can think of at this point is to completely reformat and I really don't want to do that. I'll probably just get a brand new hard drive and reinstall Windows on that. The hard drive is three years old anyway.

If anyone has any other ideas I could try, I'm open to any suggestions. Maybe a repair install of Windows without wiping the drive clean first? Can I even do that in Windows 7?

ShaneJ wrote on 1/17/2013, 9:39 AM

ForumAdmin wrote on 1/17/2013, 10:44 AM

Oh, I forgot to mention. Since the last time Vegas was able to render, I had since installed the FFDShow and Divx codecs hoping that would allow me to import certain files into the Vegas timeline that wouldn't open in Vegas. Needless to say, I still wasn't able to get the files to import. But would those codecs have something to do with this? I should try uninstalling them and see if that helps. I don't see why that would conflict with Vegas, though. I've always used them in the past with no problems.

Yes, definitely remove the codecs and try again. Also, please try resetting Vegas to its default settings by holding Ctrl+Shift while launching the application. Please let us know if the problem persists.

Paddy
SCS

redpaw wrote on 1/17/2013, 10:54 AM

hey Shane,
is it happening only with 'big' projects or everything?
it happens a lot to me but if there's hundreds of clips in the project.
what works for me is 'remove all unused media from the project' - its the yellow lighting icon in project media window.
after clearing it i can usually render the video. usually!

just one tip - save it as project_cleared.veg (or whatever name you want), but dont overwrite the original file as you'll loose all the files you're not using at the moment, but might need for the later edit.
so each time i want to render out the clip i save it as different name, clear the files and render out. then going back to the original to continue work on the project...

hope that will work for you as well

ShaneJ wrote on 1/17/2013, 3:40 PM

ForumAdmin, thanks for the info. I never knew of the method to clear settings back to default. I will certainly try that.

Redpaw, it happens with any projects, big or small. I even made a new project, saved it, and put in a video track only with an empty event and tried rendering that. Same thing. As soon as I click on "Render As", the software grays out and I get the crash report and error reporting. Very frustrating. But I will try what ForumAdmin suggested to clear back to default settings by holding down Ctrl+Shift while starting Vegas. Will remove the codecs as well. Hopefully this will do it.

Thank you all for the advice thus far. It is greatly appreciated.

ShaneJ wrote on 1/17/2013, 6:13 PM

Alright I just tried these things. Still no dice. Sigh....

Rainer wrote on 1/17/2013, 10:32 PM

I'm having the exact same problem, tried all the solutions above. It's intermittent, but not uncommon and more common with large projects and does not appear to be related to codec. Reported numerous times. If you can get the render settings to show once, they usually show more consistently. I load a small project, with just one clip, try to open the render settings, if they do, close the settings and open the large project. Another way that seems to work is to drop your project onto a new project timeline and then open the render settings.

ShaneJ wrote on 2/21/2013, 7:11 PM

This is a very late response, but not too longer after my previous response here a month ago, I FINALLY found a solution. I kept Googling one of those error codes and came up with a forum post or webpage somewhere where someone else was having some other error with a different video software. But what I found interesting was that their issue was with Windows Framework 4.5.5 (or something like that. Let's just call it Windows Framework 4 for the sake of this post). I decided to look into that further.

What I then noticed is that since rendering last successfully worked was BEFORE the latest Windows update on January 9th. That Windows update included a few updates for Windows Framework 4. BINGO! That just had to be it. So I uninstalled Windows Framework 4 and ran all my usual registry scans, virus scans, rebooted, and reinstalled Windows Framework 4. Rebooted, opened up Vegas, attempted to render for the umpteenth time and didn't expect much. Guess what? IT WORKED!

So the latest Windows update of January 9th and update for Windows Framework 4 was the culprit. A month later and I've been rendering about several dozen videos. Probably almost a hundred different videos since then. I was just about ready to reformat the whole darn hard drive, but decided to give the uninstallation and reinstallation of Windows Framework 4.5.5 as a last resort and it saved me from having to go through the task of reformatting. THANK GOODNESS.

So I just thought I would update you all in what eventually happened with me. Maybe my solution will help someone else out and save someone else the trouble of reformatting as well. Thank you all for your suggestions and your time. Hope my solution helps someone else in return. :)

Arthur.S wrote on 2/24/2013, 7:03 AM

Windows updates = potential problems. Once you have a stable editing system, turn off updates. It's a lesson many of us here - including yourself now - have learned the hard way.