No this is on any project. It can be DV footage, HDV, XDCAM, photos etc. with no third party plugins being used. It's really strange.

You have been having this problem with Vegas as far back as i can remember,
over a year and plus (From over the Creative Cow)...
To this day i can never fathom whats going on with your system, why you continually
have issues with Vegas..... Something is wrong somewhere!

uninstall vegas, clean registry, reinstall. try it, then add any plugins, etc., one by one, testing as you go...

You do have the right hardware and there shouldn't be issues even with GPU ON.

Have you tried resetting Vegas? Which driver are using for the GTX570?

I'm using the latest version for the 570 because when I use current Red Giant plugins like Colorista they require them to run properly in Premiere. I know the old driver is recommend for Vegas.

Yeah probably due for a system reinstall or some component change.

Most of my crashing issues have been related to large long form projects which I understand but I find this crashing and workaround really bizarre.

@Marc - like you Vegas has been problematic for me, yet PPro CS6 is rock solid using Red Giant Plugins. And I use them constantly - specifically Red Giant Denoiser and Magic Bullet. I'm beginning to wonder if this isn't an issue of using mixed file formats on the timeline - at least for me. Been rethinking my workflow and I'm more or less settling on Cineform AVI's for video work, using only WAV audio files and going to see if it makes any difference (I'm not too hopeful though)

Just delivered a project edited in PPro CS6 (originally started in VP13 but it would crash with import of same native clips) for The Mayors office all shot on Canon DSLR using Visioncolor's custom camera profiles, dual sync audio,music audio files and JPG stills and using the title generator - PPro CS6 didn't hiccup once.

Beginning to think that trying to make Vegas Pro work is an exercise in futility on my part - as much as I'd love to have it otherwise. No matter if it's an nVidia card or Radeon card. And TBH, I refuse to turn off GPU acceleration so that might be the lynch pin for me.

I did a Google search and Dr. Watson is no longer available in Windows 7. So why is it showing up on your system with Windows 7 64 bit?

Did you upgrade from Vista?

I had originally upgraded from Vista Ultimate 64 bit to Windows 7 Ultimate 64 bit and had a lot of problems with Vegas. I finally got tired of it all and did a clean install of Windows 7 Ultimate 64 bit and a whole lot of problems were finally gone!

I just re-upgraded from Windows 7 Ultimate 64 bit to Windows 10 now that all of the drivers I need are available for my system and my Windows 10 system is running much better than my first upgrade to Windows 10. Maybe someday I will do a clean install of Windows 10 for the cleanest system if I can stand to re-install everything AND if I can find a good way to keep my settings.

By the way, I started an earlier thread where I thought a Windows update had killed HandBrake. It was a failing ram stick instead. Thank goodness I had multiple cloned backups. The bad ram stick trashed the registry and other files. What came out of the ram was not the same as what went in. The Windows 10 memory test showed it as being good. Memtest86 quickly showed it as being bad. So DO NOT depend on the Windows 10 memory test!!!

Without the marginal then quirky and then finally bad ram stick, my system runs a whole lot better now even though I am temporarily using 8 gig of ram.

Side note, When using Plural Eyes to sync videos, I noticed that my free memory will go down to zero. There is still plenty of standby memory and so the system does not crash but it gets very slow. If I delete all of the temporary files that Plural Eyes creates and THEN empty the recycle bin a whole lot of memory will all of a sudden be available again. Same kind-of thing with Audacity. I do not know if this is from memory leaks from the apps or the way Windows 10 manages memory. I do know that if I keep up with these types of things that Vegas is much less likely to crash, run faster and render faster.

Memory timings make a huge difference in system stability with ram preview and having GPU=on.

Anyway, I hope all of this helps you. It took me almost an hour to type this because my dam brain would not remember the words I needed! Do yourself a huge favor and not get old!!!

@ VidMus - Ok I guess I was using Dr Watson in error since I meant hard crash to desktop with the stethoscope symbol appearing. I'm assuming he's the same doctor though ;).

No this is a Windows 7 64 bit install from scratch. I skipped Vista and usually reinstall periodically to keep things fresh.

I'm sure there's the possibility of a number of things wrong with my system I just never understood why Premiere CS6 runs so darn good on the same computer.

@Cliff

I'm also using Premiere more for stability reasons especially for long form projects. However I've got to say that for videos with movement on stills Vegas is still second to none. Luckly I never seem to have issues with those and find the MXF 4:2:2 codec to work nicely between Adobe and Vegas. Most other codecs including Cineform have level issues when going back and forth.

Marc, I think the biggest issue is that Vegas does not properly take advantage of CUDA the way it does OPEN CL. I have stated this a lot lately - the BEST thing I ever did with Vegas was switching from nVidia's to a Radeon R9-390 (per OldSmoke's recommendation).

Without CUDA to help render, your i7-930 is not powerful enough to render 4:2:2 space or heck, even AVCHD. It is probably overheating and self-preserving. You'll be better served with something near the 4.0 MHz range. Your system specs look JUST like my old one.

Something else to look at is the crash log. What is Vegas telling you the issue is? Mike kept posting nVidiaSucks.dll

@Videofreq

"[I]...switching from nVidia's to a Radeon R9-960 (per OldSmoke's recommendation).[/I]"

You're mixing your video card metaphors.