Try using 'Unmanaged exception 0x0000005' to search the forum - there are quite a few hits covering different possible issues.

Also, try:

https://forums.creativecow.net/docs/forums/post.php?forumid=24&postid=909150&univpostid=909150&pview=t

Even though from some 10 years ago, it does have an extensive coverage of the issue some of which may no longer be an issue.

Thanks! I'll look into it and hopefully continue researching the issue. I did re-downloaded the previous update and it worked like it used to.

mine blew up immediately on first run. deleted my temp appdata files or whatever, then it started ok. have not used it at all since then to see if it is working

Errors such as this are often too obtuse to find any definitive information. The first thing I do when they occur is go into device manager and search for driver updates. Usually video, then audio and network are most often the culprits. Make sure they're updated. Beyond that I have sometimes gone through every device and searched for new drivers and found an obscure one that can cause an issue.

-- tom

I've started to suffer crashing and increasing RAM usage on a 2 minute 1080 50P project.

With each press of play (after some slight color correcting), RAM usage is increased. I press play again, more RAM is used on top of the last increase.

Then I've had the "white screen of death" needing taskmanager to put Vegas out of it's misery.

I have the same issue.... but now the program keeps locking up and I have to shut down to recover....

@NexxTwitchTv

Since June 2, I also discovered that turning off the option "Enable QSV encoding and decoding (where available)," which is on the General tab of Preferences, allows me to use So4 Compounding. I cannot have both enabled. One of those has to be disabled. The reason I want so4 compounding has to do with better processing of variable frame rate AVC video sources (but that alone doesn't help VFR AVC video).

One of those has to be disabled. The reason I want so4 compounding has to do with better processing of variable frame rate AVC video sources (but that alone doesn't help VFR AVC video).

Not needed, look

If I had an inkling of what you are telling me it would be a miracle...LOL

I am such a novice, but I totally appreciate your help. I think I also needed some Win 10 updates. I'm waiting for them to complete. Perhaps all of it together will solve the issue. Thanx for the help my friends.... You have no idea how valuable this is to me.

Yeah lol even though windows was up-to-date when the new update was released it all failed. But thanks to Robert Johnson by changing true to False worked liked a charm in the preferences. And also, J-v is right I have enable SQV in general preferences, even do in internal tab it is on false. Thanks for the help everyone!

I just started using V17 for paid work a couple months ago & all was good until a customer wanted a set of Blu-rays, something I used to provide all of the time, but not so much anymore... So I tried to render the M2V video using my trusty MainConcept BR template like I always did with V12 / V15 and V17 keeps giving me an "out of memory" error 3/4 through a 2 hour video... My 9900K has 32GB or RAM & a large PageFile on a M.2 drive, so it might be the AMD VEGA 64 drivers or settings... So I wasted a chunk of my day trying various fixes (disable GPU, GPU Ram=0, different AMD VEGA drivers, etc.) & ended-up just making the intermediates first & then loading them into another VEG to render-out the BR files... Blah... I should have started this project in V15... The source files are QT PNG from a film scanner... I don't have any issues using V15 to render-out the exact same files to multiple customer-requested formats... The only reason I switched to V17 is because it is faster rendering HEVC & MP4...

@TheRhino Low memory or not enough memory has plagued vp17 since launch, still not resolved. I've said this before, but I suspect that the nice extras like the new colour grading section suck/leaks memory that hasn’t been fixed yet. Its rarely a physical lack of PC memory at all.

Here’s hoping that there’s a final update before vp18 that does fix this. I’ve purchased the attractive offer for the last two years of say purchase vp17 when it comes out and get a free vp16 thrown in.

For as long as the older version has a final stable/solid last update this makes sense, but not for me if say the last update of vp17 is still unstable.

@JN- Ya, I knew it's not a system RAM or resource issue, etc. but I'd thought I try various drivers & settings that worked before. I can render 2 smaller segments of the same VEG timeline just fine but if try to render the entire 2 hours as one file it produces the memory error... I've been using Vegas for paid work since 3.0 & know most tricks to get-around errors, but it's still frustrating. Last summer I got V17 included with my V16 purchase, so it was a good deal since I was still using V15... However, I thought it would be mostly fixed-up by now...

@TheRhino Indeed. I do hope that it can be fixed, there are some really nice extras in vp17, but its just not as solid as the previous versions, maybe the last update will fix things. If you have something critical, like paid work in your case, vp16/vp15 is just safer.

Whats a little worrying is that i’ve never seen any comment from the developers about this issue, despite it being ongoing since its release. If they don’t think believe theres an issue then it'll likely never get fixed.

@TheRhino Low memory or not enough memory has plagued vp17 since launch, still not resolved. I've said this before, but I suspect that the nice extras like the new colour grading section suck/leaks memory that hasn’t been fixed yet. Its rarely a physical lack of PC memory at all.

I dont' recall if you were in the other thread about memory leaks, but it appears to be true you have the least memory problems using Intel QSV for video decode, and you can use your normal video card for processing and encoding.

I know you don't have an old computer, but people with older computers need to have a monitor plugged into their motherboard video to enable intel quicksync or use a cheap dummy plug that tricks cpu into believing monitor is attached.

Can you provide a file or project where memory leaks can be replicated? I tried to provoke them by leaving the system on loop for a while with a variety of file types, but was unable to trigger any memory leak in 452 myself.

Happy to test if you provide something, and that should help Magix engineers address the problem. Do report issues to Magix support directly, as well.

Did you loop the KenB video that people were trying in other thread? http://caydays.net/wp-content/uploads/2017/03/hawaii_blue_water_4K.mp4

Using your Nvidia GPU for processing, so4compound turned on, and looping video, preview set to Best/Full

Also I was wrong. I mislead the vegas community. The decoder has nothing to do with it, When I was looping without memory leaks using intel quicksync as decoder I had mistakenly left the gpu processing to intel. I have confirmed nothing other than what KenB discovered: using Nvidia GPU causes memory leaks, and it doesn't matter if you are using nvidia or intel as decoder. it's not related to decoder.

@lenard-p 

“I dont' recall if you were in the other thread about memory leaks, but it appears to be true you have the least memory problems using Intel QSV for video decode, and you can use your normal video card for processing and encoding.”

Leonard, I am assuming that since you quoted me that your post is addressed to me, not the OP? If so, I'm not sure which “other” thread you are referring to.

In my case I dont have access to Intel QSV on my 4 year old laptop, its internally disabled by the manufacturer and I have disabled QSV in my PC as the Nvidia card is more powerful.

I've found that when using the 4k Benchmarking test project my laptop would complete the fhd, but not the uhd renders. This wasn’t the case in VP16. I added another 16 gb of ram recently and that allowed it to complete the render but DR Preview still had to be set to zero.

”using Nvidia GPU causes memory leaks, and it doesn't matter if you are using nvidia or intel as decoder. it's not related to decoder.”

Well Leonard, you might be onto something here.

The good news anyway is that in this instance the OP has found a solution.

@RogerS

“Can you provide a file or project where memory leaks can be replicated? I tried to provoke them by leaving the system on loop for a while with a variety of file types, but was unable to trigger any memory leak in 452 myself.”

As stated in my last post the benchmarking project using my laptop and attempting to render to UHD.

”Happy to test if you provide something,”  

Knock yourself out, the 4K benchmarking thread and download is available.

“Do report issues to Magix support directly, as well.​​​​​​“

Why didn’t I think of that, great suggestion, thanks Roger. Actually from previous experience I have found it not such a smart move, unless you were really desperate.

I have always found the help by members on this forum the best and quickest way to resolve solutions, I guess thats why people post their issues here!

What isn't very useful when a user has a problem is someone chipping in with ... well I don’t have that problem, works great for me etc. Thankfully there isn’t too much of that and it mostly comes from the same sources.

What is more useful in assisting other users with issues, even if you don’t experience similar, is accepting that the user wouldn’t be posting in the first place if they didn’t have an issue, and maybe just stand back and allow others to help if you don’t have anything constructive to add.

@JN-, my question about Magix support was not to say that users should refrain from seeking help in this support forum (of course they should) but that if you want Magix engineers to be aware of issues with the program, you can't just post here.

The signal to noise ratio isn't always high in this forum (lots of user errors, which is fine- we can help other users with them) so I doubt they read every thread.

Whats a little worrying is that i’ve never seen any comment from the developers about this issue, despite it being ongoing since its release.

The best way to get their attention is with a reproducible problem. I did run a test in one thread on memory leaks, but no I haven't read every thread someone's posted related to this issue since VP 17 was released, so thanks to Leonard for linking to the video.

p.s. If you had a bad day, don't take it out on other users trying to help

@RogerS Having a really great day so far Roger, thanks. I try my best to help here, and have more than appreciated what other users have given me, which I have mostly found to be very constructive, and none of it is taken for granted. It takes a bit of an effort on anyones part to make a contribution. Well Roger, I guess no one takes criticism lightly, actually I wasn’t expecting it, so do have a nice day.

There is an inherent built in human need to defend a program such as VP simply because you “own”/use it.

This can be seen in many areas, not just software.

This can blind you to an objective view. VP is a great program, but it does have memory issues since VP17 mainly, and so all of the “fixes”, that attempt to mitigate same.

So of course if You haven’t that issue/problem it doesn’t mean that the problem doesn’t actually exist. You just got lucky, so far.

Thats why users jumping in saying that they don’t have the problem is simply not helping in most cases.

Where it does have value is where all users say they don’t have that problem, then in that case the OP may have overlooked something obvious.

I'm looking forward to your experience in rendering out the Benchmarking project to UHD, please remember to let us know here how it went.