@iggy097 I have this same issues. It doesn't matter which footage I use. Eventualy after doing some minutes of editing then doing a split / edit, press space bar and Vegas crashes. This began after version 13 I think.

When I am ready with editing and start the audiomix and colorgrading, Vegas won't crash that often.

>>Problem:             Unmanaged Exception (0xc0000005)

@iggy097

Do a Google search on "Unmanaged Exception (0xc0000005)" .. What you find may or may not help but worth a go.

I work with Pany 4k/6K (G9) files 264/265 formats and I can split and move files all day long without a freeze, and I am using the RX480 8 gig card and with Intel QSV. It might be handy to list yours systems, what driver you are using, amount of RAM/HD space. Xberk link is a good one if you are having unique hard ware issues. Which is the bit rate and how long are the files you are using? With the vast combinations possible as much information as you can supply here or to tech support might help in getting a answer / work around. I notice I get much better performance using a combination of the QSV/AMD than either alone.

This is my current build. However this has happened on my last build as well. Vegas crashes way more than it should - for a pro level editing suite.

I'm using the latest Nvidia studio driver as well.

Overheated CPU? 141°C😡

I don't know why Speccy shows that - it's liquid cooled - hovers around 70 at full load.

I had a similar problem with Vegas Pro 16 on two different workstations. I spent almost 2 days trying to get it to work properly and in the end the solution was a complete re-install of Windows 10 Pro. ( both workstations had been upgraded from Windows 8 ----> Windows 8.5 ----> Windows 10 early build ----> Windows 10 later build ---> Windows 10 Pro build 1903 )

With the Windows re-install VP 16 and VP 17 are both rock-solid. ( Windows is still it's own worst enemy when it comes to stability )

 

I don't know why Speccy shows that - it's liquid cooled - hovers around 70 at full load.

Here is mine .02 cents. Your system is not stable @4.075ghz that is why Vegas crash. Try to bring the clock back to default and start there. Your system is also overheated along with unstable clock. Because you are watercooled and don't over heat is incorrect to assumed. TR CPU load a massive heats when you are overclocked at 4ghz+. I can can run TR 4.1ghz but will crash in Vegas. I can run 4.0ghz no problem what so ever. I cut a project just about every months about 90 minutes long with no issues in VP16/17.

Another hint here. Your idle temp @4.075ghz is at 64.88C is a indication there. It very bad my man.

 

I don't know why Speccy shows that - it's liquid cooled - hovers around 70 at full load.

Here is mine .02 cents. Your system is not stable @4.075ghz that is why Vegas crash. Try to bring the clock back to default and start there. Your system is also overheated along with unstable clock. Because you are watercooled and don't over heat is incorrect to assumed. TR CPU load a massive heats when you are overclocked at 4ghz+. I can can run TR 4.1ghz but will crash in Vegas. I can run 4.0ghz no problem what so ever. I cut a project just about every months about 90 minutes long with no issues in VP16/17.

Another hint here. Your idle temp @4.075ghz is at 64.88C is a indication there. It very bad my man.

My idle temp is 30 ish. I am rendering something at the moment - that's why it's at 65. The OC is stable. I guess what you aren't getting is that this has happened on another system as well. That wasn't overclocked. Vegas ONLY crashes when I am cutting / playing. Not during a render. Hell I can even render 3 instances of Vegas at the same time without a crash.

This issue ONLY occurs when working in the NLE editing. Not rendering. This is not a heat problem. The clock is not unstable, this is Ryzen Master just doing standard boosts, I have not OC manually.

I edit all day long, 3-4 times a week for a living. I've been using Vegas for the last - 7 years or so. this only has occurred with the last two iterations of Vegas.

Mine was super crashy at the start of this week. I changed nothing, and suddenly it goes all night. PERHAPS a windows update snuck in. MAYBE go check for MS updates? I'm also on the latest Nvidia STUDIO driver but it was crashy on that previously

and my aside about the software industry now: we all buy/support ALPHA version software now. Especially those subscription people. So, it's never going to get any better from here on out - because we keep paying them for this betaware

This has been happening for over a year now - windows 7 and 10.

You said your OCed is stable. May I ask what and how did you check your OC is stable? Are you able to run any type stress test? I just want to know how you do it. I am willing to bet and assured you. You will never get 65c at full load and running @4.075ghz. Unless you can provide proof. How about show the information on HWiNFOR64 while stress test it.

You said your OCed is stable. May I ask what and how did you check your OC is stable? Are you able to run any type stress test? I just want to know how you do it. I am willing to bet and assured you. You will never get 65c at full load and running @4.075ghz. Unless you can provide proof. How about show the information on HWiNFOR64 while stress test it.

I can run Realbench , Prime 95, Heaven, etc for hours. This isn't really an overclock, it's precision boost overdrive, included with the Ryzen processor. it clocks it automatically up, like a boost, and throttles it down when temps get too high.

Right now as I'm rendering 4K my temps are at 63-70 - while playing Overwatch in the background with the GPU at 42.

Mine was super crashy at the start of this week. I changed nothing, and suddenly it goes all night. PERHAPS a windows update snuck in. MAYBE go check for MS updates? I'm also on the latest Nvidia STUDIO driver but it was crashy on that previously

and my aside about the software industry now: we all buy/support ALPHA version software now. Especially those subscription people. So, it's never going to get any better from here on out - because we keep paying them for this betaware

This has been happening for over a year now - windows 7 and 10.

 

yeah.... Vegas has been the most crashing software I've ever used - in my life. I'm always shocked and delighted when it stabilizes. Finally considering other options.

You've got 2 choices, either go consider those other options, or stop posting about it, as your incessant trolling with no intent of actually trying to seek help for your issues is a violation of community policy. We have a user here trying to seek help for their issue, and all you've contributed to the discussion is whining about the issues you've been offered help with, but refused. You've been warned.

You said your OCed is stable. May I ask what and how did you check your OC is stable? Are you able to run any type stress test? I just want to know how you do it. I am willing to bet and assured you. You will never get 65c at full load and running @4.075ghz. Unless you can provide proof. How about show the information on HWiNFOR64 while stress test it.

I'm not sure what you're looking for here? that I can't run stable or that it runs hotter than 65? Yes it runs hotter than 65 while stress testing. While normal workload editing/rendering - unless I'm stiching a 360 video together it sits around 65 while under load.

I've had this build for a year or so now - it's always been stable, the only program that gives me issues is Vegas. I can game 24/7, green screen in After Effects, do title work in AE, Lightroom, Photoshop, etc etc with no issues.

It's the Vegas software that is buggy, it has been for a while, and I doubt it has anything to do with my current system, which is a Threadripper. It acted the same way on my last build with was a Broadwell chip.

But - if you wanted to see a stress test here ya go. -

Here is a typical crash when editing 4K footage from my A7iii.

(mind the content - we film weird fetish films for a living) - this is safe for work - but fair warning.

You said your OCed is stable. May I ask what and how did you check your OC is stable? Are you able to run any type stress test? I just want to know how you do it. I am willing to bet and assured you. You will never get 65c at full load and running @4.075ghz. Unless you can provide proof. How about show the information on HWiNFOR64 while stress test it.

I'm not sure what you're looking for here? that I can't run stable or that it runs hotter than 65? Yes it runs hotter than 65 while stress testing. While normal workload editing/rendering - unless I'm stiching a 360 video together it sits around 65 while under load.

I've had this build for a year or so now - it's always been stable, the only program that gives me issues is Vegas. I can game 24/7, green screen in After Effects, do title work in AE, Lightroom, Photoshop, etc etc with no issues.

It's the Vegas software that is buggy, it has been for a while, and I doubt it has anything to do with my current system, which is a Threadripper. It acted the same way on my last build with was a Broadwell chip.

But - if you wanted to see a stress test here ya go. -

 

I watch your video. Your CPU is not running at all cores at 4.075ghz. Its throttling and never able to stay 100% load. Mine 4ghz stay 100% load, no throttling or dropping speed. 4ghz all 16 cores at 100% kicking ass. That what I can call stable overclocked.

My suggestion is. Reset the speed to default and run Vegas and editing away see, if it s would make different. This way you can eliminated that, the system clock speed causing this. Use  HWiNFOR64  to monitor your temp. This App is much accurate in reading temp.

I didn't refuse any help. I'll contact support when my bug list stops growing. "troll" thanks for the customer empathy

I've previously asked you if you have created a thread to seek help for your issue, as we all do when we have problems we can't figure out on our own, and your reply was (to paraphrase) that you had a complex setup and preferred to handle it on your own, and that it was probably something to do with your setup that was causing the issue.

You're free to feel however you like about that, but the community guidelines here specifically state that needlessly hating on Vegas or any other product isn't allowed. If you have issues, we're here to help you with them. If you have an opinion, you're free to share it... but you're not free to go into every thread spreading it around just for the sake of what we refer to online as "trolling", which (among other things) is when you spread negativity about something with no real intent of seeking a resolution.

As for customer empathy, let it be clear that I do not work for Magix, I simply moderate the forums and enforce the rules where I see them being broken. The first one was being broken in this thread, so I gave the warning it says I must. Let's put this back on topic now, so the original poster can get some help with their problem. Again, if you cannot find a resolution for your issue, you are more than welcome to make a thread after reading the guidelines of what we need to help you, and we'll see what we can do. I understand your frustrations, I too am dealing with a few annoyances that are holding me back right now in various ways, but we must keep this place somewhere people can go to find resolutions, not drown help requests out with posts venting frustrations.

@fr0sty With all due respect, the man has said the opposite, that his system runs everything BUT Vegas very well.

I think you either have a history (you two) or you jumped to some conclusions, and not based on what he is really saying.

I think hardware is always a place to start, but I'm also having tons of crashes with Vegas, more than in years past, as well. I have a solid HP Workstation, known for rock solid stability.

That does not mean that his overclock might be suspect, but can we dial down the invectives and drama?

@fr0sty With all due respect, the man has said the opposite, that his system runs everything BUT Vegas very well.

I think you either have a history (you two) or you jumped to some conclusions, and not based on what he is really saying.

I think hardware is always a place to start, but I'm also having tons of crashes with Vegas, more than in years past, as well. I have a solid HP Workstation, known for rock solid stability.

That does not mean that his overclock might be suspect, but can we dial down the invectives and drama?

That post was directed at WWJD, not the original poster. WWJD made 2 negative posts that contributed nothing to the OP's search for an answer to this problem they are having, and violated the first rule of our community standards. Those posts, as per the standards, have been removed. I should have made my response to WWJD in DM form so as not to cause this confusion, sorry about that unintentional derailment.

apologies to ALL, for my bad day, and frosty I respect and understand your position.

it is INCREDIBLY FRUSTRATING for the OP and myself dealing with this after years of work with vegas and maybe $1000+ invested in this software, to have it be the only thing not running on my systems.

I'd mentioned for the OP to get all the latest Microsoft Updates as it might help.

I have to assume Magix knows something about this - as I always choose to send the crash reports to them when the system goes - at this point they have to have at least 100 from me alone.