Exception 0xc0000005 "ACCESS_VIOLATION"

LuckyCharms wrote on 9/22/2021, 2:46 PM

Not sure what's going on. Program has hanged and crashed a couple of times now. Here is the log. Any advice would be great - other than update the program. I know there is one update available, but this was happening before the update was there. I wasn't even able to submit it to support via internal submission button. That may or may not be due to my Bitdefender, but this likely isn't because it only happens here and there. Thanks in advance.

----------------------------------------------------------------------
MAGIX Movie Edit Pro Premium 28.07.2021 20:49
----------------------------------------------------------------------
CrashDump 20210728_204934_v20.0.1.80.dmp successfully written

Error in module "combase.dll" (Load address: 0x00007FFCE3E10000) to address 0x00007FFCE3F3B990 (Exception 0xc0000005 "ACCESS_VIOLATION")

Unknown Thread   (ThreadID: 00000590)
00007ffce3f3b988   0f 1f 84 00 00 00 00 00
00007ffce3f3b990 > ff e0 cc cc cc cc cc cc
00007ffce3f3b998   cc cc cc cc cc cc cc cc

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

videodeluxe.exe 22.02.2021 14:32 d3ba0539

Processor [46] 2999MHz 4 Core(s)
Microsoft Windows NT 10.0 (Build 19043)
Used Memory: 2324 MB Max Used Memory: 4318 MB
Free Virtual Memory: 3919 MB Total Virtual Memory: 131072 GB

----------------------------------------------------------------------
MAGIX Movie Edit Pro Premium 22.09.2021 15:00
----------------------------------------------------------------------
CrashDump 20210922_150016_v20.0.1.80.dmp successfully written

Error in module "mx_read_kinetictype_x64.dll" (Load address: 0x00007FF94F510000) to address 0x00007FF94F51BB88 (Exception 0xc0000005 "ACCESS_VIOLATION")

Unknown Thread   (ThreadID: 00000f2c)
00007ff94f51bb80   00 33 db b9 01 00 00 00
00007ff94f51bb88 > c7 00 28 00 00 00 48 8b
00007ff94f51bb90   87 88 00 00 00 66 89 48

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

videodeluxe.exe 22.02.2021 14:32 d3ba0539

Processor [46] 3001MHz 4 Core(s)
Microsoft Windows NT 10.0 (Build 19043)
Used Memory: 3988 MB Max Used Memory: 5396 MB
Free Virtual Memory: 41 MB Total Virtual Memory: 131072 GB

Comments

Former user wrote on 9/23/2021, 2:42 AM

A 0xc0000005 error is akin to a "general Error" message and does not really tell you much.
Unfortunately, those crash dumps are only useful to the developers.

Check the normal stuff.

Everything fully patched?
Does your PC meet the minimum requirements for MEP2021?
All drivers up to date? (Check using manufacturer's websites rather than Windows updates)
NVidia has just updated theirs to 472.12
Check Windows event viewer system logs for any disk errors.
Have you tried different A/V playback settings?

CubeAce wrote on 9/23/2021, 4:15 AM

@LuckyCharms @Former user

Hi,and welcome to the user to user forums.

First I'm very concerned about the

Error in module "combase.dll" (Load address: 0x00007FFCE3E10000) to address 0x00007FFCE3F3B990 (Exception 0xc0000005 "ACCESS_VIOLATION")

Which is a Windows dll and allows various drivers to be used within other programs. Note it does not say it is missing but cannot be accessed as the memory address given seems to be wrong.

Second I'm very concerned that you appear to have over a Terabyte of virtual ram set up.

Used Memory: 2324 MB Max Used Memory: 4318 MB
Free Virtual Memory: 3919 MB Total Virtual Memory: 131072 GB

This is way too much and does not work well with programs like video editors that really benefit from enough actual ram which you may have if I'm reading the 4GB of memory correctly as actual system ram.

It would be helpful to see your systems full specifications to se if I am reading this data correctly.

If I am correct then maybe reducing the virtual ram on your system to something more comfortable for it may be in order and you can try the following by going to Windows Settings and following the guide from the image below.

If or when John EB gets back off of holiday he may be able to make more of the data here than I can.

Ray.

johnebaker wrote on 9/23/2021, 4:51 AM

@LuckyCharms

@Former user has supplied the necessary information for you to check, in addition to the information supplied, what is your computer specification, see this topic for details of what is required, please quote the processor and graphics card/chipset make/model in full.

It would help if you put this information in your profile signature.

The "combase.dll" failure that there is a graphics driver issue with the GPU.

@CubeAce

Hi Ray

If you look at the second crash there is more than 4GB of RAM in use therefore there must be at least 6GB of RAM installed.

John EB
Forum Moderator

LuckyCharms wrote on 9/23/2021, 9:16 AM

Everything is up to date on my system. I've had the program for more than a year, and this specific problem actually started after the last program update for Music Maker. It does not really help that I had multiple tabs open in Movie Edit at the time AND was also moving a ton of security cam videos to my NAS. This may have overtaxed the memory. But I've still never received a dll error before now.

System info:

Microsoft Windows Version 21H1 (OS Build 19043,1237)

Acer Aspire TC-780

Processor Intel(R) Core(TM) i5-7400 CPU @ 3.00GHz 3.00 GHz

Installed RAM 12.0 GB

System type 64-bit operating system, x64-based processor

Intel® HD Graphics 630

Version 22.20.16.4735

Date 7/7/2017

(Let me know if you need to know the additional storage attached)

I did check and the windows dll file is there in both the system32 and the syswow folders. I will reduce my virtual memory, update Movie Edit and relaunch to see if the problem repeats. (Then followup)

emmrecs wrote on 9/23/2021, 10:23 AM

@LuckyCharms

Reading your system spec I am immediately concerned by the fact that your HD630 Graphics driver is stated to be released in July 2017! This page lists the latest version as 30.0.100.9864, released just a couple of weeks ago. As the first thing to change I think you should install this latest version! To be absolutely sure you can use this intel page to check for the latest driver which is appropriate for your system

Jeff

johnebaker wrote on 9/23/2021, 12:41 PM

@LuckyCharms

I have removed superfluous information from your computer specification above.

Is there a Nvidia or AMD graphics card installed in the PC?

It would also help for future reference if you put your computer specification in your profile signature - see mine as an example.

John EB
Forum Moderator

LuckyCharms wrote on 9/23/2021, 2:18 PM

I don't have an Nvidia or AMD graphics card -- only the Intel. When I go to the Intel website it says that everything is up to date and to ask Acer for any revisions, so I had to search for the updated driver in the Download Center. I've got it and will install and follow up. (Will also address signature 8))

LuckyCharms wrote on 9/24/2021, 5:49 PM

Update -
I updated the graphics card as well as the MAGIX program. Today I received multiple errors saying it could not write the file when attempting to autosave the backup copy. Then it crashed. I made sure it was the only thing running at the time (so no overtaxed memory issue). Here is the latest log.

----------------------------------------------------------------------
MAGIX Movie Edit Pro Premium 24.09.2021 18:42
----------------------------------------------------------------------
Error in module "mx_read_kinetictype_x64.dll" (Load address: 0x00007FFA97540000) to address 0x00007FFA9754B36B (Exception 0xc0000005 "ACCESS_VIOLATION")

Unknown Thread   (ThreadID: 00002fb0)
00007ffa9754b363   00 33 db b9 01 00 00 00
00007ffa9754b36b > c7 00 28 00 00 00 48 8b
00007ffa9754b373   87 88 00 00 00 66 89 48

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

videodeluxe.exe 08.09.2021 13:39 aff423d1

Memory Allocation
Base:       1.120
PE:       35.200
Pages:       13.107.200

PI:       165.312
PI_TEMP_DATA:   72.296
SI:       2.319.880
SI_TEMP_DATA:   580.056
FSI:       3.360

Blocks:       23.644
Temporary:   185.600
BE:       1.312.000
PLE:       1.385.536
BE Pool:       2.736
PLE Pool:       0
wHdr/inst:   2.176
B.cache inproc:   0
Video:       0(0/0)
Bitmap:       0

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

Buffer: 0
Pointer: 0

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

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

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

Frame Cache:   0
EXIF:       0
VSW:       0
DVDMAKER:   3.168
global UI (malloc):   0

CubeAce wrote on 9/24/2021, 6:21 PM

@LuckyCharms

Hi.

I'm not sure where you found your Intel graphics driver from but I am running version 30.0.100.9864 for the HD 630 Intel graphics chip. I would suggest getting it from the Intel site directly.

Ray.

LuckyCharms wrote on 9/24/2021, 6:32 PM

Meant to update. Yes, my graphics card is now version: 30.0.100.9864. I had to clean install it, but I'm guessing that is why the combase.dll error went away. So, thanks for that info. 8)

LuckyCharms wrote on 9/24/2021, 6:38 PM

Quick Question: should I start a new thread. The update to the graphics card resolved the combase.dll error. I should mark it as the solution to the original post - which is a windows DLL.

But the mx_read_kinetictype_x64.dll is a magix DLL. Should this be a new thread?

CubeAce wrote on 9/24/2021, 7:28 PM

@LuckyCharms

Hi.

Short answer. Yes to both as it is a separate issue and probably best.

Now you know why we ask for as complete specs as possible in signature. It sometimes helps us from asking additional questions.

Magix error codes are more John EBs specialty. @johnebaker I have copied him in to grab his attention.

Ray.

LuckyCharms wrote on 9/24/2021, 7:33 PM

Ok - I'll start a new threat and mark the answer that resolved the combase.dll error. Thank you so much - I had no idea the mfg locked the graphics card so it wouldn't update directly from Intel. Well, that's solved. 8)