Arturo-Bordes wrote on 9/12/2018, 11:03 AM

I have exactly the same problem. I hope Magix will solve it quickly.

croudy wrote on 9/12/2018, 11:52 AM

Same problem here (Win 10 x64, ATI HD7870).

Kinvermark wrote on 9/12/2018, 2:17 PM

@Excellentfilms @croudy@Arturo-Bordes

Did any of you guys try anything to solve this? (e.g. different footage, GPU on/off, change some project settings)

Did you report it to Magix tech support?

FYI, there are other issues with the new stabilizer, but I haven't seen it crash on my system with UHD footage.


Excellentfilms wrote on 9/12/2018, 2:48 PM

Magix try find solution, they tested few options i send them crash report on zip file (hold ctrl+shift and "send" crash report) They answered:

Thank you for your message.
As a troubleshooting step, click Options > preferences > video tab, turn “GPU acceleration of video processing” to off, and set “dynamic RAM preview” to 0, click apply and OK. "

But it still crash (and turned off GPU is not a solution) if they help me i tell You all how to fix it.

Kinvermark wrote on 9/12/2018, 3:04 PM

Specifications of footage type you were using?

Excellentfilms wrote on 9/12/2018, 3:12 PM

 crash on any kind of footage and resolution

croudy wrote on 9/13/2018, 3:22 AM

Any kind of footage (AVI, MP4, MKV, WMV), resolution, framerate. I tried to turn off gpu accelaration, but that didn't help. Same problem when starting motion tracking of bezier masking.

VEGASPascal wrote on 9/13/2018, 6:45 AM

@Excellentfilms At the moment, 'Bézier Masking' and the 'Video Stabilisation' is not using the GPU in the analysis (only the post processing in the preview and rendering). My question is what CPU do you use? The analysis is fully optimized but it needs (minimum) SSE2 and SSE3 support.

croudy wrote on 9/13/2018, 9:08 AM

AMD Phenom II X4 955 here

VEGASPascal wrote on 9/13/2018, 9:19 AM

For this we need more information from the crash report. I will create a bug report for this.

Arturo-Bordes wrote on 9/13/2018, 9:28 AM

My PC is AMD Phenom II X6 1055T

Excellentfilms wrote on 9/13/2018, 9:40 AM

My PC is AMD Phenom II X6 1055T too

Kinvermark wrote on 9/13/2018, 10:38 AM

Can you upload (dropbox, etc.) a small piece of media that causes crashes?

VEGASPascal wrote on 9/13/2018, 11:43 PM

It obvious that this is a problem with the old AMD Phenom II.

VEGASSebastian wrote on 9/14/2018, 6:29 AM

I figured out the problem, it seem that the AMD Phenom doesn't support a certain intrinsic function. 
There will be a fix in future updates.

VEGASSebastian wrote on 9/17/2018, 7:45 AM

As a workaround, change the pixel format to 32 bit (that option is found in 'Project Properties').

j-v wrote on 9/17/2018, 10:53 AM

There will be a fix in future updates.

Do we have to wait much longer for that second update, because I got the impression that heavy testing is happening these days.


met vriendelijke groet

Camera : Pan X900, GoPro Hero7 Hero Black, Samsung Galaxy A8
Desktop :MB Gigabyte Z390M, W10, i7 9700 4.7Ghz,16 DDR4 GB RAM, Gef. GTX 1660 Ti.
Laptop  :Asus ROG GL753VD, W10 home, version 1903 build 18.362,295 CPU i7 7700HQ, 16 GB RAM, GeF. GTX 1050 (2 GB) + Int. HD Graphics 630(2GB).VP 16,17 and VMS PL 16 are installed
Both Nvidia GPU's have driver version 441.28 Studio Driver, desktop the Studio DHC driver
TV      :LG 4K 55EG960V

Dutch video tutorials for beginners


Excellentfilms wrote on 9/18/2018, 3:07 PM



Thank you for your message.

​This is a known issue which will be resolved in a future application update. Thank you for reporting this issue."

croudy wrote on 10/28/2018, 6:00 AM

In update 307 this bug ist still there.

VEGASPascal wrote on 10/28/2018, 11:56 AM

The "AMD Phenom II" bug should be fixed (and tested) in update 307.

croudy wrote on 10/28/2018, 3:07 PM

I know, that it should be fixed in 307 - but it isn't...

VEGASSebastian wrote on 10/29/2018, 3:43 AM

I know, that it should be fixed in 307 - but it isn't...

Can you please give us some details about your system? I had successfully tested that build on a Win10 PC with AMD Phenom II x6 CPU and an old Nvidia GTX card.

VEGASSebastian wrote on 11/8/2018, 4:30 AM

Issue identified .... will be fixed in Update 3.

workaround for now, change the pixel format to 32 bit (that option is found in 'Project Properties').