Movie Edit Pro crashes every time I open it

Naomi-s wrote on 6/2/2017, 6:29 AM

Hi, its my first time using these forums.

I have had Magix on my laptop now for over a year and have had no problems with running it. However, one time last week i exported a project and it crashed. When I open the program up again i get the pop up box about the crash and it gives me the option to send the crash log. i did this.

however then when i proceed, a white box appears telling me there was a problem saving my work last time and it asks if i would like to continue. if i click continue then another box pops up advising i do not continue. at this point the program freezes, every time with out exception and i must have tried this at least 10 times.

I though if i close the program before it crashes then next time i open it it wont have any of these boxes pop up (because the program will have shut down properly last time). however they still remain.

i have uninstalled the program and tried to scan for coding errors but these boxes always appear and i cannot get rid of them without the program freezing and forcing me to restart my computer.

i just want magix to open normaly, with the box that asks if i would like to start a new project or load a previous one without any crash log or error boxes.

i will put some images down below aswell as my laptop hardware and the crash log.

i thank anyone who has bothered to read this.

Naomi

----------------------------------------------------------------------
MAGIX Movie Edit Pro 2016 Plus 02.06.2017 12:14
----------------------------------------------------------------------
CrashDump 20170602_121430_v15.0.0.102.dmp successfully written

Error in module "mxmpeg2_x64.dll" (Load address: 0x00007FFAA23F0000) to address 0x00007FFAA24018B7 (Exception 0xc0000005 "ACCESS_VIOLATION")

Unknown Thread (ThreadID: 00001e60)
00007ffaa24018af 2a 06 66 0f 38 2a 4e 10
00007ffaa24018b7 > 66 0f 38 2a 56 20 66 0f
00007ffaa24018bf 38 2a 5e 30 66 0f 7f 07

Main Thread
fffffffffffffff8 ?? ?? ?? ?? ?? ?? ?? ??
0000000000000000 > ?? ?? ?? ?? ?? ?? ?? ??
0000000000000008 ?? ?? ?? ?? ?? ?? ?? ??

Videodeluxe.exe 01.06.2017 21:23 e6d945b8

Memory Allocation
Base:       1.168
PE:       176
Pages:       65.536

PI:       8.184
PI_TEMP_DATA:   13.824
SI:       218.688
SI_TEMP_DATA:   156.160
FSI:       0

Blocks:       0
Temporary:   0
BE:       0
PLE:       706.000
BE Pool:       96
PLE Pool:       0
wHdr/inst:   0
B.cache inproc:   0
B.cache outproc:   0(0)
B.cache mapped:   0(0)
V.cache outproc:   0(0)
V.cache mapped:   0(0)
Video:       4.147.240(4.147.240/0)
Bitmap:       0

Video thumbs:   0(0)
SI Display Cache:   966.400
PLE Display Cache:   0

Buffer: 0
Pointer: 0

Title:       0
Memory GF:       0
Memory GF Zero:       0
Memory GF Zero_Dyn:       0
Memory GF Dyn:       0
Memory TT:       0
Audio Effect:       50
PPE:       0

Video Monitor:   0
malloc/free:   0
DIB:       5.732.744

VP: admin:       0
VP+Trans: privateData:       0
Transitions::       0

Frame Cache:   0
EXIF:       0
VSW:       0
DVDMAKER:   0
global UI (malloc):   0
global UI (valloc):   50.331.648
NOWAGGLE:   0
MP3 Reader:   0
JPEG buffer:   0

Private Bytes: 430 MByte

TLS:       987
MXGUI:       42.135.704
Sum:       104.588.706

Processor [46] 2195MHz 4 Core(s)
Microsoft Windows NT 10.0 (Build 14393)
Used Memory: 754 MB Max Used Memory: 756 MB
Free Virtual Memory: 11323 MB Total Virtual Memory: 131072 GB

Call stack:
Address Frame
00007FFAA24018B7 000000003CEC8EF0 0000:00000000
00007FFAA23F72F6 000000003CEC9070 0000:00000000
00007FFAA23F4506 000000003CEC91A0 0000:00000000
00007FFAA2417478 000000003CEC92E0 DllUnregisterServer+2888
0000000140A12896 000000003CEC9370 QWinWidget::showCentered+4FAD06
0000000140A0F277 000000003CEC9730 QWinWidget::showCentered+4F76E7
0000000140A1522B 000000003CEC9D70 QWinWidget::showCentered+4FD69B
0000000140A14EA4 000000003CEC9DF0 QWinWidget::showCentered+4FD314
0000000140A14E07 000000003CEC9E70 QWinWidget::showCentered+4FD277
0000000140A14FF8 000000003CEC9F00 QWinWidget::showCentered+4FD468
00000001402D463D 000000003CECA350 QWinWidget::qt_metacast+1989DD
00000001402D4255 000000003CECA3B0 QWinWidget::qt_metacast+1985F5
00000001408B68AE 000000003CECF6E0 QWinWidget::showCentered+39ED1E
00000001408B504C 000000003CECF750 QWinWidget::showCentered+39D4BC
00000001408B52D0 000000003CECF8D0 QWinWidget::showCentered+39D740
00000001408B3BE3 000000003CECF960 QWinWidget::showCentered+39C053
00000001408B57B0 000000003CECF9B0 QWinWidget::showCentered+39DC20
00000001402644B5 000000003CECFEF0 QWinWidget::qt_metacast+128855
00000001402662AE 000000003CECFF50 QWinWidget::qt_metacast+12A64E
00007FFADC6C8364 000000003CECFF80 BaseThreadInitThunk+14
00007FFADDF970D1 000000003CECFFD0 RtlUserThreadStart+21

Comments

johnebaker wrote on 6/2/2017, 7:03 AM

Try the following:

With Movie Edit pro (MEP) closed, use Windows Explorer to locate the file videodeluxe.ini - if you accepted the default installation locations it should be located in this folder

C:\Users\username\AppData\Roaming\MAGIX\Videodeluxe23_premium

where username is the name you use to login to the computer.

Delete or rename the file then start MEP - the file will be recreated.

MEP should now start correctly.

Assuming you made no change to the programs settings MEP will automatically backup the project you are working on every 10 minutes to a maximum of 10 backups.

To restore the corrupted project select File, Load backup project.

You will be presented with a popup looking like this

Locate the backups for the corrupted project and try loading the latest first. Note the backups are made on a rotating basis so the numerical number in the file name is not necessarily the latest.

If the last one fails try the next and so on working backwards in time.

Once you get a successful load save the project with a new file name.

You can delete the BAK files if you no longer need them - they will be in the same folder as project file.

. . . . i have uninstalled the program . . .

This will not fix issues like this, files are left behind after un-installing and these must also be cleared out before re-installing which should only be done as a last resort. The un-installer knows nothing about these files as they are created the first time the program runs.

HTH

John EB

Naomi-s wrote on 6/2/2017, 7:39 AM

With Movie Edit pro (MEP) closed, use Windows Explorer to locate the file videodeluxe.ini

Hi john. after searching through my files the only onees that came close to videodeluxe.ini were the ones in the screenshot below. is it any of these which should be deleted? otherwise I am struggling to find this file.

thanks a lot for helping out

Naomi

p.s the location you suggested it would be under was not there. once i got tto username i couldnt find app data. this was found through the search

emmrecs wrote on 6/2/2017, 8:36 AM

the location you suggested it would be under was not there. once i got tto username i couldnt find app data. this was found through the search

You could not find the AppData folder since, by default, it is hidden. In order to unhide it do the following:

Open Control Panel (if you're not sure how to do this, open the Cortana search box, type Control and it should show you "Control Panel Desktop App". Click on this.
In Control Panel you need to find "File Explorer Options". Again if you have problems finding this, top right hand side of the Control Panel screen you should see a dropdown called "View". Choose either Large Icons or Small Icons.
Click on File Explorer Options. A screen like this will open:
Click on the View tab (which I have highlighted)
On that screen find the highlighted line below, and make sure there is a dot in "Show hidden files..."
Now repeat the instructions in John's last post

Jeff

Naomi-s wrote on 6/2/2017, 11:48 AM

hi.

I did the steps and your solution worked. it now opens as usual.

Thank you to both of you

emmrecs wrote on 6/2/2017, 12:42 PM

Hi.

Many thanks for the feedback. Glad to hear you're up and running again.

Jeff

johnebaker wrote on 6/2/2017, 1:16 PM

And apologies from me - I always have Hidden and System files showing in Windows Explorer - I should have mentioned the folder was hidden and how to see it - thanks Jeff.

John EB

justinaspcvideo wrote on 9/1/2018, 3:59 AM

Hello need help.. I did not find where to write, I write here because the problem is similar.

According to the explanations provided, the program does not start up properly. The program has been reinstalled 5 times nothing changes..I made Windows on the platform running old (Windows 7, or Windows 8) but does not start properly.

My program is available..MAGIX MOVIE EDIT PRO PREMIUM 2019

Windows 10 Home

----------------------------------------------------------------------
MAGIX Movie Edit Pro Premium 01.09.2018 12:55
----------------------------------------------------------------------
CrashDump 20180901_125518_v18.0.1.203.dmp successfully written

Error in module "igdrclneo64.dll" (Load address: 0x00007FFAD4830000) to address 0x00007FFAD49CEE5F (Exception 0xc0000005 "ACCESS_VIOLATION")

Unknown Thread   (ThreadID: 00000a00)
00007ffad49cee57   00 48 8b 05 29 48 2e 00
00007ffad49cee5f > f7 40 38 00 00 00 02 74
00007ffad49cee67   68 b9 78 00 00 00 e8 c6

Main Thread
fffffffffffffff8 ?? ?? ?? ?? ?? ?? ?? ??
0000000000000000 > ?? ?? ?? ?? ?? ?? ?? ??
0000000000000008 ?? ?? ?? ?? ?? ?? ?? ??

Videodeluxe.exe 07.08.2018 10:46 93fe87f3

Memory Allocation
Base:  1.176
PE:  176
Pages:  65.536

PI:  0
PI_TEMP_DATA: 0
SI:  0
SI_TEMP_DATA: 0
FSI:  0

Blocks:  0
Temporary: 0
BE:  0
PLE:  0
BE Pool:  0
PLE Pool:  0
wHdr/inst: 0
B.cache inproc: 0
Video:  0(0/0)
Bitmap:  0

Video thumbs: 0(0)
SI Display Cache: 0
PLE Display Cache: 0

Buffer: 0
Pointer: 0

Title:  0
Memory GF:  0
Memory GF Zero:  0
Memory GF Zero_Dyn:  0
Memory GF Dyn:  0
Memory TT:  0
Audio Effect:  0
PPE:  0

Video Monitor: 0
malloc/free: 0
DIB: 5.020.308

VP: admin:  0
VP+Trans: privateData:  0
Transitions::  0

Frame Cache: 0
EXIF: 0
VSW: 0
DVDMAKER: 0
global UI (malloc): 0
global UI (valloc): 0
NOWAGGLE: 0
MP3 Reader: 0
JPEG buffer: 0

Private Bytes: 367 MByte

TLS:  992
MXGUI:  36.529.700
Sum:  41.616.896

Processor [46] 2710MHz 4 Core(s)
Microsoft Windows NT 10.0 (Build 17134)
Used Memory: 600 MB Max Used Memory: 600 MB
Free Virtual Memory: 15052 MB Total Virtual Memory: 131072 GB

Call stack:
Address Frame
00007FFAD49CEE5F 0000000038C6A7F0 clGetGLContextInfoKHR+4F9FF
00007FFAD49CF0E5 0000000038C6A820 clGetGLContextInfoKHR+4FC85
00007FFAD484CF7F 0000000038C6A8A0 0000:00000000
00007FFAD484CEEF 0000000038C6A8E0 0000:00000000
00007FFAD49A70D0 0000000038C6A9D0 clGetGLContextInfoKHR+27C70
00007FFAD49A6E48 0000000038C6AA40 clGetGLContextInfoKHR+279E8
00007FFAD49A6F3C 0000000038C6AA80 clGetGLContextInfoKHR+27ADC
00007FFAD484C33B 0000000038C6AAE0 0000:00000000
00007FFAD48630C5 0000000038C6AB40 clGetKernelSubGroupInfoKHR+EEB5
00007FFAD489D564 0000000038C6AB80 clGetKernelSubGroupInfoKHR+49354
00007FFAD489CF3D 0000000038C6AC20 clGetKernelSubGroupInfoKHR+48D2D
00007FFAD484D10E 0000000038C6AC80 clGetPlatformIDs+6E
00007FFAD48541E9 0000000038C6ACD0 clEnqueueTask+D9
00007FFADBF032B5 0000000038C6B1C0 clEnqueueWriteBufferRect+3C789
00007FFADBECC85B 0000000038C6B1F0 clEnqueueWriteBufferRect+5D2F
00007FFAECA611BC 0000000038C6B260 0000:00000000
00007FFAECA6351B 0000000038C6B6D0 clWaitForEvents+16B
00007FFB2AB9285F 0000000038C6B710 RtlRunOnceExecuteOnce+8F
00007FFB26FE39CA 0000000038C6B740 InitOnceExecuteOnce+A
00007FFAECA62E2C 0000000038C6B770 clGetPlatformIDs+1C
00007FFAE51FBD0F 0000000038C6B830 MXSetHost+1521F
00007FFAE51F9B4C 0000000038C6B880 MXSetHost+1305C
00007FFAE51F9387 0000000038C6B8C0 MXSetHost+12897
00007FFAE51E05F8 0000000038C6B900 DllUnregisterServer+3B448
00007FFAE51E02A2 0000000038C6BA40 DllUnregisterServer+3B0F2
00007FFAE51E8619 0000000038C6BA90 MXSetHost+1B29
00007FFAE51F640B 0000000038C6BAC0 MXSetHost+F91B
000000014084B05C 0000000038C6BC40 QWinWidget::focusNextPrevChild+18220C
0000000140239E80 0000000038C6BC80 QWinWidget::qt_metacall+BA6E0
0000000075CE6444 0000000038C6BCC0 MxQt::QMetaCallEvent::placeMetaCall+34
0000000075CE519A 0000000038C6BE70 MxQt::QObject::event+DA
00000000752C7580 0000000038C6BEA0 MxQt::QApplicationPrivate::notify_helper+140
00000000752C64DA 0000000038C6C5E0 MxQt::QApplication::notify+1B9A
0000000075CC1FF9 0000000038C6C660 MxQt::QCoreApplication::notifyInternal2+B9
0000000075CC3CC1 0000000038C6C710 MxQt::QCoreApplicationPrivate::sendPostedEvents+221
0000000075D07825 0000000038C6C820 MxQt::QEventDispatcherWin32::processEvents+DB5
00007FFB2A006CC1 0000000038C6C9B0 CallWindowProcW+4C1
00007FFB2A006693 0000000038C6CA40 DispatchMessageW+1D3
0000000075D06F99 0000000038C6FDD0 MxQt::QEventDispatcherWin32::processEvents+529
0000000075CBE991 0000000038C6FE50 MxQt::QEventLoop::exec+1B1
0000000075B3B7C2 0000000038C6FEA0 MxQt::QThread::exec+92
0000000075B4038A 0000000038C6FEF0 MxQt::QThread::start+2FA
00007FFAFE824F7F 0000000038C6FF20 beginthreadex+107
00007FFAFE825126 0000000038C6FF50 endthreadex+192
00007FFB2AA93034 0000000038C6FF80 BaseThreadInitThunk+14
00007FFB2ABE1431 0000000038C6FFD0 RtlUserThreadStart+21

justinaspcvideo wrote on 9/1/2018, 6:19 AM

I found the problem myself,reinstalled intel video drivers..

The program is currently running

emmrecs wrote on 9/1/2018, 6:32 AM

@justinaspcvideo

Thanks for updating your post with the details of how the problem was resolved. I strongly suspect that few, if any, of we fellow-users would have suggested reinstalling the Intel video drivers.😀

Happy video editing!

Jeff

Scenestealer wrote on 9/1/2018, 12:47 PM

@emmrecs

I think the "igdrcl…..dll" is a clue - ig = integrated graphics Jeff.😉

emmrecs wrote on 9/1/2018, 1:25 PM

@emmrecs

I think the "igdrcl…..dll" is a clue - ig = integrated graphics Jeff.😉

Hi Peter.

Agreed, but when I first saw @justinaspcvideo's post, the error log was not included!! (That's my story - perfectly true, incidentally - and I'm sticking to it!!)

Jeff😊

shgrude wrote on 9/7/2018, 4:25 PM

Just to add some information, when in the <USER> folder, you can simply type AppData\ in the Explorer link and it will open up even when hidden.

Or even better, just start typing "%USERPROFILE%\AppData\" once Windows Start button is pressed and then press enter. (Do not type the quotes " but do type the % and the suffixing backslash \). This will opens up File Explorer at the correct location, even when USERPROFILE has been assigned to a different disk (as I have).
Not only that, but it will work on a computer having a non-English OS Language :)

Edit: Simply %APPDATA% should bring you to the ROAMING Directory below AppData directly.

Adding tags for @Naomi-s @johnebaker and @emmrecs

Mark-Abernathy wrote on 1/16/2019, 9:20 PM

I found the problem myself,reinstalled intel video drivers..

The program is currently running

Unfortunately this solution did not solve the problem for me. Movie Maker does not open for me.

I received the same error on start up. Every time I try to start the program since, it crashes during initialization.

I have tried uninstalling and reinstalling the graphics driver.

Are there any suggestions as to how to solve this?

johnebaker wrote on 1/18/2019, 2:22 PM

@Mark-Abernathy

. . . . Unfortunately this solution did not solve the problem for me . . .

How did you re-install the Intel drivers ie did you use the Windows updat function or the Intel Driver Utility?

What is the version number of the drivers as found in the Intel Graphics Control Panel - Options & Support, Information Center?

John EB

Mark-Abernathy wrote on 1/18/2019, 2:50 PM

@Mark-Abernathy

Hi

. . . . Unfortunately this solution did not solve the problem for me . . .

How did you re-install the Intel drivers ie did you use the Windows updat function or the Intel Driver Utility?

What is the version number of the drivers as found in the Intel Graphics Control Panel - Options & Support, Information Center?

John EB

Thank You.

What I did was go into the Device Manager and made note of the Display adapter drive installed on my computer. I went to the GeForce website and downloaded the same driver to my desktop.

I then used the Device Manager to uninstall the driver. I restarted my computer, and then used the driver I downloaded to re-install the driver. I did a second restart afterward.

johnebaker wrote on 1/18/2019, 3:45 PM

@Mark-Abernathy

. . . . GeForce . . . .

These are not the drivers both @Scenestealer and I are referring to - the igdrclneo64.dll is part of the Intel integrated graphics GPU (iGPU) and it is these that you should be checking - see the solution in this topic here.

HTH

John EB

Mark-Abernathy wrote on 1/18/2019, 3:59 PM

@Mark-Abernathy

Hi

. . . . GeForce . . . .

These are not the drivers both @Scenestealer and I are referring to - the igdrclneo64.dll is part of the Intel integrated graphics GPU (iGPU) and it is these that you should be checking - see the solution in this topic here.

HTH

John EB

I'll explore it. Does it mean anything if I have no other display adapters? Computer only has the geforce driver, and the thread makes mention of people going to the Intel Graphics Driver in the same location.

johnebaker wrote on 1/19/2019, 2:03 AM

@Mark-Abernathy

As you have provided no information on your computer specification, and the DLL referenced is a specific Intel driver component, we are assuming you have Intel processor - the iGPU is part of the processor, otherwise you should not be getting the error message.

. . . .the thread makes mention of people going to the Intel Graphics Driver in the same location . . .

I have found several threads that give this impression that it is a GForce issue, however they do not state what the processor is and none of them were resolved trying to fix the GForce driver.

HTH

John EB

emmrecs wrote on 1/19/2019, 12:22 PM

@Mark-Abernathy

With apologies to you, but I have hidden the extensive post you've recently made because at least some of the data you included as your computer specs could allow a potential hacker to remotely access your computer and take control of it, I think.

You included info like your IP Address and MAC Address, either of which could be "gold dust" to unscrupulous persons!

Please edit the data to remove such info and then repost, at which point I will remove your original post.

Jeff
Forum Moderator

Mark-Abernathy wrote on 1/19/2019, 1:06 PM

Please edit the data to remove such info and then repost, at which point I will remove your original post.

You can delete the post. I apologize, and thank you for catching that.

emmrecs wrote on 1/19/2019, 1:15 PM

Please edit the data to remove such info and then repost, at which point I will remove your original post.

You can delete the post. I apologize, and thank you for catching that.

Done! And PM responded to.

Jeff

Mark-Abernathy wrote on 1/19/2019, 1:59 PM

I was able to research and solve the issue. Most of this was due to my lack of knowledge of how the systems work, but this appears to be a niche issue that also affects other programs such as Vegas and some games. The answer was exactly as stated above: the Intel Drivers needed to be reinstalled.

I just didn't know where to find them, and because I had a computer custom built, I wasn't sure what driver to get. I think that's where most of my confusion was. (I'm new to the PC world).

As suggested in other threads, DDU simply does it for you. Boot into safe mode, select Intel, and do a Clean and Restart.

Thank you John for putting up with me, and emmrecs for watching out for me.