MEP keeps crashing

kate-m schreef op 20.09.2024 om 18:16 uur

Hi everyone :-)

in the past year MEP keeps crashing, so i started working with another video programm, but i'd acctually like to keep working with MEP. Also i have lots of unfinished projects in MEP i'd like to finish. This is the MEP i have on my Windows 10 computer.

"C:\Program Files\MAGIX\Movie Edit Pro Premium\2020\Videodeluxe.exe"

 

And this is the crash info (below).

Thanks for any good tip :-)

Kate

 

Crash log:


----------------------------------------------------------------------
MAGIX Movie Edit Pro Premium  20.09.2024  17:54
----------------------------------------------------------------------
CrashDump 20240920_175446_v19.0.2.58.dmp successfully written

Error in module "KERNELBASE.dll" (Load address: 0x00007FF999180000) to address 0x00007FF9991BB699 (Exception 0xe06d7363 "")

Unknown Thread   (ThreadID: 00001c60)
  00007ff9991bb691   20 48 ff 15 6f eb 1a 00 
  00007ff9991bb699 > 0f 1f 44 00 00 48 8b 8c 
  00007ff9991bb6a1   24 c0 00 00 00 48 33 cc 

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

videodeluxe.exe    10.02.2020  15:13      2d24803b

Memory Allocation
Base:        1.160
PE:        35.200
Pages:        13.107.200

PI:        48.384
PI_TEMP_DATA:    13.808
SI:        251.856
SI_TEMP_DATA:    305.888
FSI:        3.840

Blocks:        53.572
Temporary:    648.696
BE:        2.464.000
PLE:        693.296
BE Pool:        3.984
PLE Pool:        0
wHdr/inst:    0
B.cache inproc:    0
Video:        1.335.972.160(1.335.972.160/1.333.700.112)
Bitmap:        0

Video thumbs:    6.400(80)
SI Display Cache:    6.159.952
PLE Display Cache:    617.080

Buffer:        0
Pointer:        240

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

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

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

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

Private Bytes:    9478 MByte

TLS:        935
MXGUI:        41.257.466
Sum:        1.509.737.708

Processor [46]  2905MHz  4 Core(s)
Microsoft Windows NT 10.0 (Build 19045)
Used Memory: 9339 MB             Max Used Memory: 9340 MB
Free Virtual Memory: 20725 MB     Total Virtual Memory: 131072 GB

 Call stack:
Address   Frame
00007FF9991BB699  0000000036E390A0  RaiseException+69
00007FF96580E349  0000000036E39170  _BuildCatchObjectHelper+3B1
00007FF99B4F1C96  0000000036E3B730  RtlCaptureContext2+4A6
0000000072F82C96  0000000036E3B790  MxQt::QCoreApplication::quit+D6
0000000072F7F9D4  0000000036E3B7D0  MxQt::QCoreApplication::addLibraryPath+2E4
0000000072F82291  0000000036E3B860  MxQt::QCoreApplication::postEvent+161
0000000072FA7530  0000000036E3B8F0  MxQt::qt_qFindChildren_helper+910
0000000072FA0595  0000000036E3BA00  MxQt::QMetaObject::activate+235
00000000732E2F02  0000000036E3BA40  MxQt::QNetworkCookieJar::`default constructor closure'+E22
0000000072FA08DD  0000000036E3BB50  MxQt::QMetaObject::activate+57D
00000000732FDB02  0000000036E3BC30  MxQt::QNetworkReply::url+9FA2
00000000733636ED  0000000036E3BCA0  MxQt::QNetworkReply::uploadProgress+21D
0000000072FA519A  0000000036E3BE50  MxQt::QObject::event+DA
0000000072587580  0000000036E3BE80  MxQt::QApplicationPrivate::notify_helper+140
00000000725864DA  0000000036E3C5C0  MxQt::QApplication::notify+1B9A
0000000072F81FF9  0000000036E3C640  MxQt::QCoreApplication::notifyInternal2+B9
0000000072F83CC1  0000000036E3C6F0  MxQt::QCoreApplicationPrivate::sendPostedEvents+221
0000000072FC7825  0000000036E3C800  MxQt::QEventDispatcherWin32::processEvents+DB5
00007FF99948EF5C  0000000036E3C990  CallWindowProcW+60C
00007FF99948E684  0000000036E3CA10  DispatchMessageW+4A4
0000000072FC6F99  0000000036E3FDA0  MxQt::QEventDispatcherWin32::processEvents+529
0000000072F7E991  0000000036E3FE20  MxQt::QEventLoop::exec+1B1
0000000072DFB7C2  0000000036E3FE70  MxQt::QThread::exec+92
0000000072E0038A  0000000036E3FEC0  MxQt::QThread::start+2FA
00007FF9657D4F6B  0000000036E3FEF0  beginthreadex+107
00007FF9657D5098  0000000036E3FF20  endthreadex+118
00007FF99AF17374  0000000036E3FF50  BaseThreadInitThunk+14
00007FF99B49CC91  0000000036E3FFD0  RtlUserThreadStart+21

Reacties

emmrecs schreef op 20.09.2024 om 21:12 uur

@kate-m

Hi Kate,

KERNELBASE.dll is a Windows core file, so this seems to be a problem caused by your OS rather than MEP.

If you read this Microsoft forum thread you will see it includes a suggested procedure to try and resolve the error.

HTH

Jeff
Forum Moderator

Win 10 Pro 64 bit, Intel i7 Quad Core 6700K @ 4GHz, 32 GB RAM, NVidia GTX 1660TI and Intel HD530 Graphics, MOTU 8-Pre f/w audio interface, VPX, MEP, Music Maker, PhotoStory Deluxe, Photo Manager Deluxe, Xara 3D Maker 7, Samplitude Pro X7 Suite, Reaper, Adobe Audition 3, CS6 and CC, 2 x Canon HG10 cameras, 1 x Canon EOS 600D, Akaso EK7000 Pro Action Cam

kate-m schreef op 21.09.2024 om 21:13 uur

Hey Jeff,

wonderful, that did it!

have a lovely evening :-)

Kate

emmrecs schreef op 22.09.2024 om 15:25 uur

@kate-m

Hi Kate,

Excellent news, and thanks for the feedback.

Jeff

Win 10 Pro 64 bit, Intel i7 Quad Core 6700K @ 4GHz, 32 GB RAM, NVidia GTX 1660TI and Intel HD530 Graphics, MOTU 8-Pre f/w audio interface, VPX, MEP, Music Maker, PhotoStory Deluxe, Photo Manager Deluxe, Xara 3D Maker 7, Samplitude Pro X7 Suite, Reaper, Adobe Audition 3, CS6 and CC, 2 x Canon HG10 cameras, 1 x Canon EOS 600D, Akaso EK7000 Pro Action Cam

kate-m schreef op 23.09.2024 om 19:59 uur

You're very welcome :-)

loos_5 schreef op 28.09.2024 om 13:59 uur

Hi i had a similar problem for the last months. the kernelbase issue was driving me nuts.
crashing about once every hour.
Last week i noticed magix was using an excessive amount of virtual memory.

My system was set to automatic virtual memory allocation.
The problem (allmost) fully disappeared when i manually set the memory to 100gb

Hope this will help other users as well.