I'm afraid I don't know anything about timeline codecs. I record online streaming web cams in .mp4 format and render them to .wmv format.

so which mp4 does your webcam record?

and have you tried rendering to something else. i think your error is in encoding to wmv...

I don't think I've explained very well.

I use a screen capture program (Debut) to record live streaming webcams of bald eagle nests. I record them to .mp4 format to keep file sizes low. I then take the .mp4 videos into Sony Vegas and edit them for time, etc. then render them to .wmv format.

I have done this the same way for 4 years on two different computers and never had these ' Sony Vegas has stopped working' errors until 3 weeks ago. The only thing that has changed is that Sony Vegas crashes nearly every time I use it now.


What I don't know and hoped someone could figure out is, what could cause constant application crashes when nothing I have done has changed?

windows update perhaps?

try rendering to something else...

The trouble appears to be that Windows Media Video Encoder. And as Leslie says, you may have an issue with a CODEC, as the Fault address states, I'd say it's the result of WMV Encoder:

Fault Module: C:\Windows\System32\wmvencod.dll

G

I've rendered three different videos to .mp4 format and so far, Sony Vegas did not stop working. The quality of the finished videos however, is a bit pixelated. They're not as crisp/clear as when they're rendered to .wmv format.

Thank-you ushere and Grazie for your help.

The quality of the finished videos however, is a bit pixelated.
Well, that may not be due to the actual format of MP4. You need to review what you have within the MP4 Template. Also, how are you then Previewing the finished MP4? In WMP?

G

I had some problems with Vegas at one time...about a year or so ago, it would either stop or just not load. I reloaded Vegas and it seemed to help but the fact it started happening 3 weeks ago tells me there's something not jiving with your PC.

How long before you started seeing these problems, did you last use Vegas? So from 3 weeks ago, when was the last time you opened Vegas?

First order of business is your PC clean inside? How much dust (if any) has accumulated on your graphics card, CPU cooler? If there's a lot of dust, I would get some compressed air and clean it out, with the power off but don't use a vacuum of any type. This is just a check mark on the what to try list.

If your PC is clean, have you installed ANYTHING on your PC in the last month or BEFORE this problem started happening.

Before you try a system restore to about a month ago or 6 weeks, I would check some things over.

I would run CPU-Z and tell us how your memory is configured or running. Make sure all is there and recognized and running how you set it up.

http://www.cpuid.com/softwares/cpu-z.html

What anti virus are you using? As a note, ever since I've been running MSE with occasional Malwarebyte scans...I have had virtually zero issues.

What version is your Bios, have you updated since your build?

I just upgraded to Win 10 from Win 7 and it runs smoother but I'm seeing some issues here and there. I did have to get the most recent update to my motherboard though and this helped a lot.

What drive is your Vegas stored on? If your C drive is it SSD or platter? I keep mine on my C drive and save to a magnetic drive. If on your C drive you could try to uninstall Vegas and save to another drive, maybe even a drive you don't have a lot of items on and format it beforehand.

When problems like this arise, I try to advance cautiously especially if I would have Vegas on my C drive along with memorable items like pics or videos....I would transfer those to another hard drive just in case you have a virus to be on the safe side

Check your control panel and pull up your program list and sort by date, see if anything has been added in the last month or so.

The reason I stress the backup for you pics and vids, I had a virus or just a bad drive that shutdown my C drive so quick I could barely get things saved in safe mode.

Worst case, backup everything, get a new drive, SSD preferred....:), then reload the OS. Sometimes it's the best way and if you have your retail OS disc then that's great..but hopefully it won't come to that.

As a side note, not sure what you have hardware-wise....but since I put Vegas on a SSD with a fresh OS install..I couldn't be happier. I'm currently working around some Win 10 bugs but nothing too serious, Win 7 64 I had no issues and it was pretty fast.

Let us know.

Grazie - WMP is the only option I have on my PC. I rendered two more videos using the Sony AVC/MVC (*.mp4) after posting last night. Those two videos looked great...and Sony Vegas didn't have any issues.

dka56 - I have used Sony Vegas 10 daily, sometimes 15 or more hours per day, since October 1st, 2015. Even after the problems started, I still used it every day.

I did open the tower and cleaned it out about a week ago. Forgot to mention that.

I don't install anything on this PC (on purpose, anyway) but there was a Windows Update on Jan 12th which was right around the time my issues began. I uninstalled that and thought the problem was solved. But after a full day of using Sony Vegas, it started again.

Don't know what CPU-Z is but will check into that.

Avast Anti-virus and Malwarebytes found nothing except cookies.

I don't know the version of my Bios. I have not updated since the computer was built. (I did not build it.)

Vegas is on the C drive which is not SSD. Formatting was going to be my next step but I have to back-up all my stuff first. I've saved a good portion of my personal files/pics to DVD but all of my personal home videos are too large so I need an external drive and money is an issue right now.

I have checked the Control Panel. Over and over. :)

The guy that built the computer also suggested an SSD drive and reloading the OS. I have a new laptop with Windows 10, don't really care for 10 but I'm slowly getting used to it. If I do have to format I'll probably put Windows 7 back on the desktop.

Thank-you for all the suggestions! I really appreciate the help.

I would try a system restore before Jan 12. Other than that...it doesn't take much file corruption to mess things up. Find out what was in that update, maybe it's the key to your issues. Also, check with your mobo manufacturer, see what updates have been avail and see what version your bios is....these could be key players especially if you aren't receiving automatic updates to your mobo.

Could be a video driver issue, maybe your windows update involved a video or cpu control update and your mobo is on old drivers....dunno.

Definitely check your bios version, mobo driver version, compared to the list on the mobo website.

What motherboard are you using?

The earliest System Restore Point is Feb. 7th. Was already having problems by that time.

Here's the info on the motherboard: GIGABYTE GA-990FXA-UD3 AM3+ AMD 990FX SATA 6Gb/s USB 3.0 ATX AMD Motherboard

I'll ask the builder about the Bios version, etc. He was here once but I'm not sure exactly what was done. We've been in contact several times and he's baffled also.

You can get the bios from restarting and pressing delete when the prompt shows and you will go into your bios. It should give you the version and if you're not familiar with your bios then don't change anything....just hit f10 to save and exit once you're in there.

Sometimes it will flash the version number on the screen during boot.

Also, CPU-z should show your BIOS version so try that first.

Found the BIOS version in System Information:

BIOS Version and date - American Megatrends Inc. F2 7/15/2013

SMBIOS Version - 2.7

"[I]Fault Address: 0x000007FEE08519FD[/I]"

Is the fault address the same for all the failures?

john_dennis - That I don't know. I haven't used Vegas today but if it happens again, I'll check.

You might take a look in the Windows Event Log "just because".

I would run MemTest86+ through at least one set of 10 tests. If you get any errors at all, you need to replace a bad memory DIMM, or both.


You might also run: sfc /scannow from an admin command prompt (right click Start button)

Verify you get:

"Windows Resource Protection did not find any integrity violations."

repair any issues here. Reboot and re-run if issues repaired until you get the message above.

Hello again ~

I took a couple days off because I needed a break from all this.

Here is what has happened since my last post. I have started rendering videos to SONY AVC/MCV (*.mp4) format. When I use that format the finalized videos look okay but not as crisp/clear as .wmv and Vegas doesn't crash. But when I upload them to YouTube I get this message. "Your videos will process faster if you encode into a streamable file format. For more information, visit our Help Center." (Here is the link to the Help Center page - https://support.google.com/youtube/answer/1722171?hl=en )

I don't understand because .mp4 is listed on the Help Page. But right now, I don't really care about that.

Since the finalized .mp4 videos don't look as good as .wmv I tried once more to render to .wmv and almost immediately Vegas crashed. The following shows the details of the crash.

Problem Description
Application Name: Vegas Pro
Application Version: Version 10.0e (Build 738) 64-bit
Problem: Unmanaged Exception (0xc0000005)
Fault Module: C:\Program Files\Sony\Vegas Pro 10.0\vegas100k.dll
Fault Address: 0x0000000180017514
Fault Offset: 0x0000000000017514

Fault Process Details
Process Path: C:\Program Files\Sony\Vegas Pro 10.0\vegas100.exe
Process Version: Version 10.0e (Build 738) 64-bit
Process Description: Vegas Pro
Process Image Date: 2011-06-29 (Wed Jun 29) 17:33:50


This is different from the crash details I listed in my original post.

I have searched and searched for a resolution to this problem. What I've found is that many people have this issue but have yet to find a solution.

I have used Vegas for four years on 2 different machines. Always rendered videos to .wmv format but for some reason, it just does not want to render to .wmv anymore.

No changes were made to my PC before these issues began except a Windows Update which I have since uninstalled. Vegas worked well for a day and ½ after that uninstall but then it started up again. Video quality is important to me and I don't know where to go from here.

astar - I'll tell the computer builder about your suggestion. I don't feel comfortable doing it myself. Thank-you for your help.

I have finally found a solution to this problem. I don't know why it works, but it does. Since I applied these changes Sony Vegas has not crashed once.

View video here:

threeofhardts, as you say this is "a solution". This is not a fix. What you now have is Vegas Pro not able to produce RAM Builds for previewing and you're not using all the threads you've paid for. OK?

Well, maybe just maybe a little more investigation and implementation on your part will get you to another level where you could get back your RAM builds and using all your threads.

I took time to read the comments on that YT link and there are some mixed responses which made me want to re-re-read the White Paper on VP 10e Build "Notable fixes/changes in Version 10.0e", and there would "appear" to be some convergence around the operability of 32bit and 64bit Windows Media Audio; the installation/update of Windows Media Player 11 and the ultimate require/need to reinstall Vegas Pro.

Here's the link to http://dspcdn.sonycreativesoftware.com/releasenotes/vegaspro100e_readme_enu.htm#Known_Issues Vegas Pro 10e - Known Issues.[/link]

As I said, by reducing RAM builds to 0 and powering back threads from 4 to 2 is hobbling the feature-set of Vegas, which I'm guessing you realized(?), which in turn may produce alternative issues for you down the line.

Read the White Paper.

G

As previously stated, I would try going back a month or so to an older restore point. Windows updates can reset your settings or change settings critical to your system. One of the annoying Windows tricks is to slowly change your computer to look like the next version of Windows. I had a system that ran SVP10 perfectly them started crashing. The things I did to fix this were:
1. Sick to one version of graphics driver that works and not update
2. Monitor carefully the updates Windows want to install.
3. Turn of Windows drive indexing.

Also, try Uninstalling/Reinstalling 10. Programs get corrupted and can't be repaired.

Grazie - I'm afraid I have no clue what "RAM Builds for previewing" and "using all the threads you've paid for" mean. All I know is, I used Sony Vegas 10 on this computer for two years with no issues. Then in January I started having all kinds of problems without making any changes to my computer, how I record nor how I render.

The only change that took place in January was a windows update for Adobe Acrobat Reader DC (or something like that) which I uninstalled. It seemed to help for a day or two then the program would crash again and more often. It got to the point where I couldn't ever finish rendering a video because Vegas would just "Stop Working" with no warning.

I have made no changes in Windows Media Player. I still have the same version I had when the computer was built 2 years ago. Since these problems began, I have uninstalled/reinstalled Vegas Pro 3 or 4 times. I've been trying to find the 'fix' for this for nearly 2 months so I can't remember exactly how many times. Plus, the guy who built the computer uninstalled/reinstalled Vegas Pro also. If I remember correctly, each time it was reinstalled the problems got worse. His suggestion is to format the hard drive or install a new SSD drive. (Which I may do as soon as possible.)

Thanks for the link to the Vegas Pro 10e known issues. I will read it...but I can't promise I'll understand it. :)

One thing I have noticed since making those changes talked about in that YT video is, rendering time has increased. It takes quite a bit longer for the videos to render. I was just happy that the program wasn't constantly crashing that I figured that was the lesser of two evils. I was completely stumped so I sought the help of a computer repairman and all his suggestions did nothing to resolve the issues.

Thanks again for your reply. My apologies for my ignorance on this subject.