Unreliable, Freezes, Crashes

John-Teves wrote on 1/14/2022, 2:14 PM

I have trying to render a project for the past 3 day using Movie Studio 17. It crashes every time. It chews up an hour of your time before it happens. Magix does not offer support and does not update their software to fix these bugs. But they continuously try to sell you an update which probably contains the same bugs. The problem I am seeing is unhandled exception 0x0000000005. So Magix, do you have a solution for this problem? I would like to be able to render my final project using your software before a switch to another vendor and unistall Movie Studio 17. Needless to say I am extremely dissatisfied. Every video I have made has encountered one type of problem or another. Hours of frustration!!!!

Comments

EricLNZ wrote on 1/15/2022, 3:04 AM

Vegas Movie Studio 17 Platinum has always been very stable for me. In order for anyone to help you with your problem more information is required. Start with items B & C in this post https://www.vegascreativesoftware.info/us/forum/important-information-required-to-help-you--110457/.

John-Teves wrote on 1/15/2022, 10:05 PM

Thanks for the help but……I have researched this problem for days. Nothing solves it. I have had numerous problems with the software crash, freeze, hang, crash freeze, bugs…. You name it. The reviews on Amazon for Movie Studio 17 are abysmal. If you buy a product it should work. You shouldn’t have to spend hours trying to solve problems the developers did not or did not want to solve. I have a project in Movie Studio now that I need to render and once I can do that, I am uninstalling movie studio and boycotting Magix for good. Their products suck. They have created a lot of ill will in the video producing community and they don’t seem to care. They offer NO support and and NO updates. They deserve to go out of business. They are truly despicable bordering on a scam.

Dexcon wrote on 1/15/2022, 11:02 PM

unhandled exception 0x0000000005

A Google search of the error code shows that this error code has been around for many years and the common suggestion is that it usually relates to problems within the computer or OS (e.g. a faulty driver, a corrupt registry file, damaged RAM, etc). There is nothing to suggest that this error code occurs with any particular software like VMS7 or other MAGIX product. The following is a link to Microsoft's Community page re that error code and what to do to check for any corrupted system files:

https://answers.microsoft.com/en-us/windows/forum/all/application-error-0xc0000005/6224ae45-a251-4f21-b076-74524618d00a

A search of the forum via the search facility shows only 3 hits before your post re this error code, one being in 2003 and the other two being in 2013, and the cause with all three appear to have been related to other software on the computer (QuickTime in 2 cases).

It may possibly be that you are venting your dissatisfaction at MAGIX when the reason for the error code could well lie elsewhere.

EDIT: Even though the OP wrote the error code as being '0x0000005', it is likely '0xc0000005'. Using this as a search keyword on the forum results in many hits - https://www.vegascreativesoftware.info/us/forum-search/?query=0xc0000005

Last changed by Dexcon on 1/15/2022, 11:44 PM, changed a total of 1 times.

Cameras: Sony FDR-AX100E; GoPro Hero 11 Black Creator Edition

Installed: Vegas Pro 15, 16, 17, 18, 19, 20, 21 & 22, HitFilm Pro 2021.3, DaVinci Resolve Studio 19.0.3, BCC 2025, Mocha Pro 2025.0, NBFX TotalFX 7, Neat NR, DVD Architect 6.0, MAGIX Travel Maps, Sound Forge Pro 16, SpectraLayers Pro 11, iZotope RX11 Advanced and many other iZ plugins, Vegasaur 4.0

Windows 11

Dell Alienware Aurora 11:

10th Gen Intel i9 10900KF - 10 cores (20 threads) - 3.7 to 5.3 GHz

NVIDIA GeForce RTX 2080 SUPER 8GB GDDR6 - liquid cooled

64GB RAM - Dual Channel HyperX FURY DDR4 XMP at 3200MHz

C drive: 2TB Samsung 990 PCIe 4.0 NVMe M.2 PCIe SSD

D: drive: 4TB Samsung 870 SATA SSD (used for media for editing current projects)

E: drive: 2TB Samsung 870 SATA SSD

F: drive: 6TB WD 7200 rpm Black HDD 3.5"

Dell Ultrasharp 32" 4K Color Calibrated Monitor

 

LAPTOP:

Dell Inspiron 5310 EVO 13.3"

i5-11320H CPU

C Drive: 1TB Corsair Gen4 NVMe M.2 2230 SSD (upgraded from the original 500 GB SSD)

Monitor is 2560 x 1600 @ 60 Hz

EricLNZ wrote on 1/16/2022, 3:57 AM

@John-Teves If you want your problem solved then you need to provide some information. It's probably something peculiar to your system, which we know nothing about, as others don't suffer what you claim to be experiencing.

Over to you.

John-Teves wrote on 1/16/2022, 1:00 PM

I am running version 223 of Movie studio 17. I am running the latest update version of Windows 10., I have an AMD Radeon graphics card. I am using only movie studio plug ins. I have 16 GB of RAM and a 5 TB hard drive, quad core intel processor. My system should be more than capable of running this software. The video I am using are m2ts files. I beg to differ that I am the only one suffering from this problem. If you do a net search there is more than one video with possible solutions. The Vegas support center also refers to possible solutions. Amazon reviewers have brought up a myriad of problems. This software has great features however it has stability problems.I have been trying to render a 12 minute video for 4 days. Needless to say I am frustrated. I uninstalled and reinstalled the software. No joy. In each case the software has to be terminated via the task manager. I have made changes to the internal settings as recommended by other users. Nothing works. Do you have any potential solutions?

EricLNZ wrote on 1/17/2022, 1:12 AM

@John-Teves Thanks for the info but you need to be more specific

  1. Which AMD Radeon graphics card and which driver version is it using?
  2. Which quad core Intel processor?
  3. Media info on your m2ts files. Instructions here https://www.vegascreativesoftware.info/us/forum/faq-how-to-post-mediainfo-and-vegas-pro-file-properties--104561/. Alternatively if you use MPC-HC player the media info tab from that provides the info
  4. Where do your m2ts files come from?