Okay thanks David I've changed it to zero.
Lets see how it goes.

Nope. Still crashed.

i'm presuming you have a second hd?

Third party apps will do this. And if Windows 7 doesn't like something in your machine it will do the same. Please don't take this to the bank but just suggestions.
JJK

Smith111,

My unscientific best guess as to why I have random crashes are:
1. nested files
2. mov files on the timeline
3. third party plug-ins
4. rendering

I am unable to pinpoint issues to anything specific, because sometimes it works, sometimes it doesn't. But if providence is shining down on me, all works OK.

You are not alone. SVP 10 led me to switch from Media Composer. If I would have known all the heartache I would go through in the next two years with SVP 11 & 12, I never would have switched. However, I believe there are many times more people satisfied with Vegas Pro, without crashing issues, and that Sony puts out a proven product so - IT MUST be something else and not a faulty product. I am convinced NLE's developers have the toughest task to deliver a good product as it must work with so many different environments, with differing project lengths and differing hardware set ups with different updates. Not so with gaming software or hardware or photo editing. I have had many problems and have narrowed the issues down to a couple of things on my rig.

I believe three things make up a good video system: 1) Good hardware, 2) Good software and 3) Good practices. So with that in mind:
1) Do you have a full list of your system specs including your video card. I abandoned new and modern for proven and reliable. I bought a used Quadro FX4600 and have tweaked it with varying drivers until I have found one that edits well, plays back without hitches and renders nicely. It has 92 CUDA cores with CL 1.0, would be considered a dinosaur and yet it way out performs my GTX660 with 332 CUDA cores. Older drivers are better than newer. Also, stay away from any nVidia product with Kepler. Kepler is a four core CUDA system that divides the total CUDA count into four quadrants and SVP only sees one. In addition, after writing to SVP on numerous occasions they told me to turn CUDA off, which tell me CUDA is way over rated. AVID tell its people to use high powered chips not high powered video cards. You have a nice CPU. Keep it. Be suspect of your video card. If it isn't a GTX 570 it won't be SVP benchmarked. Also check your Sound Card. Try running with it and without it. Some motherboards are SVP friendly. What is yours? Many successful SVP rigs like ASUS and that's what I have. Turn off ALL power saving features.

2) Software can interfere with Vegas Pro. Take a look at your error logs and see what they say. If SVP crashes and you get a "Sony Vegas Pro has shut down...." message, then the conflict is within SVP. Copy and make a list of the error logs and see what the common error is. One of the most common is the ntdll.dll error. Look up the resolves for this. If you only get Microsoft error messages, then the issue is with your MS OS or some other software you have. It could be a 3rd Party plug-in. Try removing them and see. Try running SVP on just windows 7 with the initial SP-1 and no other updates as SCS did when they benchmarked SVP12. Many updates are for gamers and video streamers (r.e.a.d Porn Industry), the biggest users of Windows. I view updates as bad. Updates needed for security issues? Puhleease. NOTHING is secure. Also, turn of Task Scheduling and any other background program that SVP or windows doesn't need. There is so much crap going on behind the scenes. Also, try running SVP in compatibility mode with Win 7 and even Vista.

3) Good editing practices are also important. If you have 1080-60i footage and want to render it into 24p with 32 bit float and HD422 AVC in won't happen. Match your output with your input. If you have multiple video formats, experiment. If you have 4:2:0 color space, stick with it. Are you color correcting 4:2:0 and trying to render it into 32 bit 4:2:2? How long is your project. Do you have any mov files. SVP does not like mov.

Sony Creative Software has turned out a really powerful and nifty product. They are trying to make it everyman's NLE system and I think that they need to take the approach that - "This is what we tested it on, anything else is suspect."

+100% - "This is what we tested it on, anything else is suspect."

Thanks everyone I really appreciate it.

I have so many SONY products, including my cameras so it just makes sense to use SONY editing software, so I really have to stick with it.

Here's my system specs ( if you need more details let me know )

Operating System
Windows 7 Professional 64-bit SP1

CPU
Intel Xeon E3 1240 @ 3.40GHz 33 °C
Haswell-WS 22nm Technology

RAM
24.0GB Dual-Channel DDR3 @ 798MHz (11-11-11-28)

Motherboard
Hewlett-Packard 1905 (SOCKET 0) 28 °C

Graphics
LG ULTRAWIDE (2560x1080@60Hz)
2047MB NVIDIA Quadro K2000 (HP) 35 °C

Storage
931GB Seagate ST1000DM ST1000DM003-1CH1 SCSI Disk Device (SATA) 34 °C
465GB Western Digital WD 5000BEV External USB Device (USB (SATA)) 38 °C
1863GB Western Digital WD Ext HDD 1021 USB Device (USB (SATA)) 40 °C
2794GB Western Digital WD My Book 1140 USB Device (USB)
2794GB Western Digital WD My Book 1140 USB Device (USB)
1862GB Western Digital WD My Passport 0748 USB Device (USB (SATA)) 35 °C
1863GB Western Digital WD Elements 1048 USB Device (USB (SATA)) 35 °C

Optical Drives
hp DVDRAM GTA0N SCSI CdRom Device
HL-DT-ST BD-RE BP06LU10 USB Device

Audio
Realtek High Definition Audio

I haven't tried turning CUDA off, so I'll give it a go in the morning.

The message I get when it crashes says " Unmanaged Exception (0xccccfffe)
It's the same message everytime.

It also says FAULT MODULE C:\windows\system32\KERNELBASE.dll

I don't have any problems when it comes to actually rendering.

At the moment my video is 1hr 30mins but I'm almost done, maybe another 10 minutes to go.

I have a 1TB HDD and a secondary internal for the windows backup.

As you can see other than that I have the following external storage to store my footage :

2x WD Mybook 3TB - connected to USB3 - used for backups only
2 x WD Passbook 2TB - connected to USB3
1 x WD 2TB

My footage is HD 1920x1080 at 50p - AVCHD
I would like to know what setting I should be using at the moment it's set to 1920x1080, 50.000 fps)

I am using .MOV files as a drag and drop overlay ( lightleaks etc ) so that might be causing greef although it was doing the same before
I used these. Still, I'll give it a try without these, maybe I can convert to another format.

No colour correct other than using VAAST plugins, again it was happening before I used these as well.

I don't use a lot of the above.

Would like to know what you think?

Random thoughts: Turn OFF GPU in prefs. What version of Quicktime are you using? I use the latest version, because I found Vegas went belly up as soon as I dropped a 'Light Leaks' file on the TL. but I've seen posts where others have cured a problem like yours by going back to an older version. Use the little folder icon in project properties to let Vegas set up your project settings as close as possible.

hi smith111,
here are some things to check out, some of which have already been mentioned.

1) turn OFF GPU in options and any rendering. - sad but true, its unstable and highly dependent of your driver versions.
2) any ASIO sound cards may have to be switched off in audio device prefs, just use the PC's internal sound with a simple line out signal.
3) Watch out for some third party plugins, namely NewBlue. Works for some, not for others. I had nightmares.
4) careful if you use external drives as project drives with media. Any power saving features and cause crashing due to media going off line. Try testing projects from c: drive only and see if that has an effect on stability.
5) sometimes a bad media file can cause a crash. Why this is not detected in software is any ones guess. A meaningful error message would be, well, meaningful and helpful.
6) avoid any overclocking!
7) run a memtest on your system if you suspect this is a PC problem.
8) disable any virus checking software running in the background.
9) some tablet input devices like Wacomm *may* have issues although i suspect that got fixed. Just try a mouse as part of error checking process if not so already.
10) try not to loose hair or sleep.

Paul.

"Unmanaged Exception" is almost always a driver problem.

follow the checklist provided by Paul_W.

Vegas just hung during my fourth attempt to restart it today. Count me as another one who is sick of the absolute constant crashing. I love the workflow, the design, the GUI, but this constant crashing has me looking at other platforms. I would happily pay for an update without a single new feature if it would just be as stable as Vegas versions 10 and earlier were.

Three attempts to start later and I am going to reboot (this was a fresh boot just to start Vegas). This is getting very, very old!

Laurence,

Please try starting Vegas with blank preferences and see if that helps. To do that, hold down Ctrl + Shift while launching Vegas and it will go to a clean slate. You will have to rebuild your prefs, but that's better than crashing.

Thanks,

Adam

Turning off the GPU didn't change anything.
I loaded the newest version of QT and it crashed.
I loaded an older version of QT and it still crashed ( the earliest version possible for SVP12)

I've been able to finish the edit - using the "save" button after every change to my project. Now it crashes during the render unfortunately. It crashes at less than 5% or 38%, 27% or 70% twice.

I do notice when the project is loading it loads fast but stalls at 86% every time. So perhaps it could be footage at a certain point. Even though it plays in the timeline perfectly.

I tried sub-clipping larger pieces of my clips because there a 3 camera angles edited into a single speech. One speech is about 40 minutes long so I thought having 3 files at over 10GB each may be the cause. But it still crashed.

I'll keep working on each suggestion here. you guys have been great and helping me to work out the problem.

I contact SONY Customer Service overnight and they sent back a possible solution, but that didn't work either.

Okay I think I've had success!
After monitoring my timeline the most common point of the crash was about 1hr 10mins into the edit.

I deleted about 30 mins of my edit approximately where I thought the glitch was, then dropped the complete footage of the 3 cameras back onto the timeline and carefully watched each of them using match sticks to stop my eyes from blinking. And luckily enough one of clips had the smallest of "black" in the footage, no longer than the blink of an eye. Once I cut that from my footage it was all plain sailing!

No crash during edit and so far no crash during render.

Unless I post again... Consider it case solved due to corrupt video footage.

Cheers all thanks for the help. I learned a little more along the way.

"Please try starting Vegas with blank preferences and see if that helps. To do that, hold down Ctrl + Shift while launching Vegas and it will go to a clean slate. You will have to rebuild your prefs, but that's better than crashing."

I agree Adam, but why doesn't Sony make the Ctrl-Shift Startup behave like starting Windows in Safe Mode? Safe mode bypasses all the extras to do a bare bones minimal startup. But Windows doesn't destroy all your configuration settings, Presets, and Add-Ins like Vegas does. You can reboot Windows normally after a Safe start and everything is still there.

Good to hear you found a solution, but I would send a report to SCS with the details..

It still sounds like Vegas is misbehaving under repeatable circumstances..

good result! well spotted and good use of matchsticks. Point 5 got you. Got me a few times too. To Adam, are you guys using try catch {} around your media loading code? some kind of catch all on bad media with a message would be useful. cheers.
Paul.

Vegas won't start for me with a control shift. I get a message about entering debugging mode, but that's as far as it gets. So far today I have not been able to start Vegas. I just tried about six times in a row. It either crashes or hangs. Once it gets going it isn't bad, but starting is a PITA. One other thing. I have to start a new project, add an empty video track, call up the render dialog, cancel it, then load whatever project I am working on. If I don't do that, it will crash when I finally get around to rendering. It reminds me of my old 1998 car. I have to unlock the passenger side door and crawl across to unlock the driver side when I get in. Getting ready to reboot and try starting Vegas again so that I can hopefully get some work done today.

Edit: one last try before reboot and it finally started! Woo hoo!. It always eventually does work. Eight times is what it took today. Now to quickly insert an empty video track, call up the render dialog, cancel, load my current project, and I'm up and running!

We had constant crashing, turned GPU Acceleration and the crashing stopped.
Preview certainly suffers--framerate is drops easily to where you can't see your fine edits without rendering.

Would like to be able to use it for better previewing, but don't know where to start. Didn't have this problem with 11. GPU driver is up to date.

Thanks!

Jaums
System Information

System #1
Windows Version:7 64-bit
RAM:16 Gigs
Processor:Intel Box Intel C17 2600K
Video Card:ATI RADEON HD 6870 Giga-byte
CD Burner:Lightscribe
DVD Burner:Blue Ray
Camera:Sony Z7 & SR500V
Add. Comments:Custom built at Micro Center

Thanks Paul, to be honest it was the last thing I tried because I really didn't want to go back and re-edit 30 mins of a speech I've heard 10 times over! Agrh.... I'm just stoked to have it up and running I love the software which has always been good to me.

I'll send that result to SCS hopefully we can have an alarm bell put in there somewhere.

I use SanDisk ultimate SD media cards and format them before every shoot, generally once a week. I guess such a tiny missing frame or two is an unwanted but acceptable failure rate.

This is a pretty typical day. I'm taking a break after my fifth attempt to start Vegas to write this post. Sometimes it crashes. More often it just hangs there stuck on some sort of plugin initialization. Why is it so freaking hard to get Vegas to start every single morning?

Starting Vegas with the Control shift option doesn't work for me. Vegas doesn't actually start when I try this. Is there a file I can just manually delete to accomplish the same thing?