Premiere Elements 2023 Crashing on MP4 Export

[__Nat__]

Hi all,

I am trying to export a 4K video that's approximately 90 mins long. This PC definitely has the specs for it so not sure what's happening:

Windows 11 Pro 64-bit

CPU: Intel 13th Gen i9 Processor

RAM:  64.0GB

Motherboard:  Gigabyte Technology Co. Ltd. Z790 AERO G (U3E1) 

Graphics: NVIDIA GeForce RTX 4080 (ASUStek Computer Inc) 

Storage (SATA):  3726GB Western Digital WDC WD4003FZEX-00Z4SA0 

(SSD): 931GB Samsung SSD 980 PRO 1TB 

The error in the event log is:

Faulting application name: PremiereElementsEditor.exe, version: 21.0.0.0, time stamp: 0x6424615b
Faulting module name: mc_enc_avc.dll, version: 11.4.0.5253, time stamp: 0x6183de9f
Exception code: 0xc0000005
Fault offset: 0x000000000028352d
Faulting process id: 0x0xE94
Faulting application start time: 0x0x1DA6325CCA7F370
Faulting application path: C:\Program Files\Adobe\Adobe Premiere Elements 2023\PremiereElementsEditor.exe
Faulting module path: C:\Program Files\Adobe\Adobe Premiere Elements 2023\mc_enc_avc.dll
Report Id: 0629b98c-a03b-4669-b707-f30567f39aae
Faulting package full name:
Faulting package-relative application ID:

It's crashing only a few minutes into the export, every time.

Here are the last parts of the logs:

Premiere Elements Log.txt

DigitalVideoLimiter
Ticks = 197094 <41032> <StandardFilterWrapper> <5> Not able to create video filter for standard filter: AE.ADBE Lumetri
Ticks = 197094 <41032> <StandardFilterWrapper> <5> Not able to create video filter for standard filter: AE.ADBE AESDRConform
Ticks = 197094 <41032> <StandardFilterWrapper> <5> Not able to create video filter for standard filter: AE.ADBE PPro ClipName
Ticks = 197094 <41032> <StandardFilterWrapper> <5> Not able to create video filter for standard filter: AE.ADBE PPro Timecode
Ticks = 197094 <41032> <StandardFilterWrapper> <5> Not able to create video filter for standard filter: AE.ADBE DigitalVideoLimiter
Ticks = 197094 <41032> <StandardFilterWrapper> <5> Not able to create video filter for standard filter: AE.ADBE PPro ClipName
Ticks = 197094 <41032> <StandardFilterWrapper> <5> Not able to create video filter for standard filter: AE.ADBE PPro Timecode
Ticks = 197094 <41032> <StandardFilterWrapper> <5> Not able to create video filter for standard filter: AE.ADBE DigitalVideoLimiter
Ticks = 197094 <41032> <StandardFilterWrapper> <5> Not able to create video filter for standard filter: AE.ADBE AESDRConform
Ticks = 197110 <41032> <StandardFilterWrapper> <5> Not able to create video filter for standard filter: AE.ADBE PPro ClipName
Ticks = 197110 <41032> <StandardFilterWrapper> <5> Not able to create video filter for standard filter: AE.ADBE PPro Timecode
Ticks = 197110 <41032> <StandardFilterWrapper> <5> Not able to create video filter for standard filter: AE.ADBE DigitalVideoLimiter
Ticks = 197110 <41032> <StandardFilterWrapper> <5> Not able to create video filter for standard filter: AE.ADBE AESDRConform
Ticks = 214703 <42116> <MCCallback> <5> err_printf: Seek out of range. No next_key frame available

Ticks = 215047 <42116> <MCCallback> <5> err_printf: Seek out of range. No next_key frame available

Ticks = 417141 <41616> <dvascripting.ScriptingThreadHangMonitor> <5> Scripting Thread Blocked for 9.08319 seconds.
Ticks = 417141 <41032> <MZ.MainThreadHangMonitor> <5> Main Thread Blocked for 9.08244 seconds.

Premiere Elements Log-last.txt:

Ticks = 182406 <8176> <StandardFilterWrapper> <5> Not able to create video filter for standard filter: AE.ADBE PPro Timecode
Ticks = 182406 <8176> <StandardFilterWrapper> <5> Not able to create video filter for standard filter: AE.ADBE DigitalVideoLimiter
Ticks = 182422 <8176> <StandardFilterWrapper> <5> Not able to create video filter for standard filter: AE.ADBE PPro ClipName
Ticks = 182422 <8176> <StandardFilterWrapper> <5> Not able to create video filter for standard filter: AE.ADBE PPro Timecode
Ticks = 182422 <8176> <StandardFilterWrapper> <5> Not able to create video filter for standard filter: AE.ADBE DigitalVideoLimiter
Ticks = 182422 <8176> <StandardFilterWrapper> <5> Not able to create video filter for standard filter: AE.ADBE AESDRConform
Ticks = 182422 <8176> <StandardFilterWrapper> <5> Not able to create video filter for standard filter: AE.ADBE PPro ClipName
Ticks = 182422 <8176> <StandardFilterWrapper> <5> Not able to create video filter for standard filter: AE.ADBE PPro Timecode
Ticks = 182422 <8176> <StandardFilterWrapper> <5> Not able to create video filter for standard filter: AE.ADBE DigitalVideoLimiter
Ticks = 182422 <8176> <StandardFilterWrapper> <5> Not able to create video filter for standard filter: AE.ADBE AESDRConform
Ticks = 199797 <32904> <MCCallback> <5> err_printf: Seek out of range. No next_key frame available

Ticks = 200172 <32904> <MCCallback> <5> err_printf: Seek out of range. No next_key frame available

PremiereElementsEditor_2024-02-19_222827_[PC_NAME]crash:

Crashed thread: 128 [51744] THREAD_PRIORITY_NORMAL

Exception Code: EXCEPTION_ACCESS_VIOLATION
Exception Parameters: Access violation writing location 0xffffffff729539fe
Exception Message: 3221225477 The instruction at 0x%p referenced memory at 0x%p. The memory could not be %s.

Application Specific Information:
C:\Program Files\Adobe\Adobe Premiere Elements 2023\mc_enc_avc.dll

Any thoughts welcome, thanks.

[John T Smith]

>NVIDIA GeForce RTX 4080

Are you using the Studio driver or the default gaming driver that Windows installs?

nVidia Driver Downloads https://www.nvidia.com/Download/index.aspx?lang=en-us
-for all Adobe programs use the STUDIO driver, not the GAMING driver
-To achieve the highest level of reliability, Studio Drivers undergo extensive
-testing against multi-app creator workflows and multiple revisions of the top
-creative applications from Adobe to Autodesk and beyond

[__Nat__]

Hi John,

I use the gaming driver (as this is predominantly a gaming PC), that's what I've always used - albeit this being a relatively new PC and the first time I've tried rendering anything on it. The previously PC wasn't as highly specced, used the nVidia gaming drivers and never had an issue.

Could it be the CPU overheating too often? I see it spiking at around 95C during the render but I thought that's pretty normal for this kind of CPU intensive activity.

[__Nat__]

I'll also add that I created a short 10 min video to test, and it also crashed out, within seconds with the same error.

Adobe support advised me to reinstall the program but it hasn't fixed it.

[John T Smith]

I have different hardware and my version is 2021.4 (2021 has had 4 updates... have you checked for updates of your version?)

I don't know what mc_enc_avc.dll is, so I don't know if it part of Windows or PrElements... you might google to see if you can find out what that dll is part of

Try right clicking the EXE and selecting Run as Administrator to be sure the program has full Windows permissions

Try https://support.microsoft.com/en-us/help/2977003/the-latest-supported-visual-c-downloads
or https://helpx.adobe.com/x-productkb/global/troubleshoot-c-runtime-errors-products.html

to see if the problem is with the Windows runtime

[__Nat__]

Thanks, it is MainConcept AVC H 264 Encoder commonly used in video encoding. "The file mc_enc_avc.dll is a resource of Adobe Dynamic Link, a feature included in the Adobe Creative Suite that eliminates intermediate rendering between programs."

How actually do you check for Premiere updates? Thanks ...

Yes I tried running as admin and same issue.

[__Nat__]

It says it's up to date (and would be as I just did a fresh install)

[John T Smith]

>How actually do you check for Premiere updates?

I work in Expert mode... click Help... bottom of the drop down window... in my 2021.4 Updates is not active

[John T Smith]

I'm out of ideas... the only time I did a small test with some downloaded 4k files I had zero problems... but, that is with my version and my hardware... so I can't offer any other suggestions

[Bill Sprague]

Based on my memory of previous questions like this, the problem usually lies with the source footage.   In other words, some part of the project has flawed or incompatable footage.   Usually it is either a damaged clip or non-camera footage.   One way to test for a damaged clip is to use the work area bars and export using the check box for "Work Area Bars Only".   

[__Nat__]

Thanks Bill. That's why I did a new project with 6 or 7 of the source videos, no effects or anything like that. Even that crashed after a few seconds or minutes. 

This is the final video I've been making (it's a holiday video), the last part of our trip. They are all similar. None of the other ones had any issues, that said, it was on my older PC and this is a new one.

2nd level Adobe support are going to give me a call today about it and remotely connect. Fingers crossed.

[Bill Sprague]

2nd level Adobe support are going to give me a call today about it and remotely connect. Fingers crossed.

By @__Nat__

Good luck and please post the results!

[__Nat__]

No one's called yet, but I thought I'd try something. I unticked using the GPU for rendering (which frankly seems ludicrious to me) and I was able to render the timeline at least - only the small test file at this stage. I'll wait til I'm finished work for the day and I will try exporting tonight, and if that works, exporting the big 90 min video.

If it works, then perhaps it is a GPU/nVidia driver issue after all (even thought the error logs aren't indicating that).

[__Nat__]

Sadly no, still crashing on the big file even just rendering the timeline ...

[Bill Sprague]

Can you try picking some smaller sections of the project with the work area bars and output using the work area bars only check box?  (Keep the GPU off.)

[__Nat__]

Thanks - I tried just exporting the first 3 videos in the timeline and checked that box, but same crash occurs (this was just even on the test video).

Followed up with support, someone will be calling me but don't know when.

[John T Smith]

use https://handbrake.fr/ open source transcoder/converter to convert to a different codec

Handbrake tutorial https://www.youtube.com/watch?v=xlvxgVREX-Y&t=34s

I have not used this, but while doing a search for other software this site was one result... it claims to do a lot of things with video, so you might want to take a look https://www.winxdvd.com/winxvideo-ai/

[__Nat__]

Just to update everyone, the L2 tech called me this afternoon and he turned off the GPU processing in a config file as well, just to rule out the GPU completely (this apparently means the GPU isn't used at all, whereas the setting in Preferences just means it's not used for rendering/exporting). The test 15 min video did export after that, but the 90 min video export still crashed literally 3 mins after he said he will call me in an hour to see how it went (of course!) - it had run for over 5 mins which it hadn't been previously so we were cautiously optimistic. 

So waiting for him to call back. The error message is different however:

Crashed thread: 108 [43468] THREAD_PRIORITY_NORMAL

Exception Code: EXCEPTION_PRIV_INSTRUCTION
Exception Parameters:
Exception Message: 3221225622 {EXCEPTION} Privileged instruction.

This gets curioser and curiouser. Literally can't find any mention of that error in regards to Adobe products.

[John T Smith]

>Exception Message: 3221225622 {EXCEPTION} Privileged instruction.

Have you tried what I suggested about right clicking the EXE and selecting run as administrator?

[__Nat__]

Sure did - didn't resolve sadly

[__Nat__]

I tried it again for you just now. This error is back when I do that, but it nearly get to 50%:

Exception Code: EXCEPTION_ACCESS_VIOLATION
Exception Parameters: Access violation reading location 0xffffffffffffffff
Exception Message: 3221225477 The instruction at 0x%p referenced memory at 0x%p. The memory could not be %s.

[John T Smith]

Reading your latest message about memory makes me think that you MAY have a ram problem

>RAM:  64.0GB

What ram and how many 'sticks' ?

I have 64Gig made up of 4x16Gig... is yours also 4x16 or maybe 2x32Gig?

https://www.amazon.com/TEAMGROUP-3200MHz-PC4-25600-Unbuffered-Computer/dp/B086X2FYW9/

What you MIGHT want to try is shifting your ram around... pulling all but one stick (check your motherboard manual to find out where to put a single stick so the computer will work) and do some testing to find out if one of your ram sticks has a problem

Or, with everything as it is, find a memory test program

I have NO idea if your problem is really a bad ram cell, but I don't have any other ideas

[__Nat__]

Thanks.

It's x2 32 GB: 64GB DDR5 (2x32G) Corsair 5200MHz CMT64GX5M2B5200C40 Dominator Platinum RGB RAM

I can memtest on reboot perhaps overnight, cos it takes awhile. Worth a try.

The L2 tech called back BTW and he couldn't find what was wrong. It now needs to be escalate to the senior support team.

[John T Smith]

For me, I would still try removing one ram stick and leaving one in the 'main' motherboard slot and running a test... then switch and run with only the other ram stick

Also, my motherboard is ASUS-Prime-Z490-P that I bought January 2021... and I had to do a BIOS update to go from Win10 to Win11... so is your BIOS up to date?

[__Nat__]

I have the latest BIOS from Dec last year yes.

I'll have a think about when is a good time to try what you've suggested with the RAM. I'm not really a hardware person & my PC case is a bit of a pain to mess with, it's all glass for the most part.