Known Participant

Answered

Premiere Elements 2023 Crashing on MP4 Export

Forum|Forum|1 year ago
February 19, 2024
7 replies
2943 views

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.

This topic has been closed for replies.

Correct answer John T Smith

Very interesting

My CPU is a K model so I 'could' overclock... but I never do... the small gain in performance is not worth the possible reduction in the life of the CPU

You were not overclocking but you needed to underclock to get the CPU to run properly... very much an Intel problem

_

__Nat__Author

Known Participant

I have an update on this. Haven't heard from Adobe Senior Support but I'm like a dog with a bone with this kind of stuff and like to do my own analysis (coming up to 8 or more hours trying to diagnose this issue now, at least). There was something else (besides the high temps when exporting) making me think this may be CPU related. There was this entry in the system log:

A corrected hardware error has occurred.

Reported by component: Processor Core
Error Source: Corrected Machine Check
Error Type: Internal parity error
Processor APIC ID: 48

The details view of this entry contains further information.

I found a whole bunch of Reddit and other forum logs with other owners of i9 13900K or KF CPUs having these issues, mostly on gaming which obviously is also a CPU intensive activity.

Cutting a long story short, even though the K & KF CPUs are meant to be factory overclocked by Intel at a stable level, seems like they aren't stable under very high load. People were having to undervolt the processor cores slightly which means they don't reach their ultimate power capacity and hence, temps are reduced. Once I did this using Intel Extreme Tuning Utility (first I had to disable undervault protection in the BIOS), I was able to successfully export my 90 min video in roughly the same timeframe it was going to take without reducing the voltage. I kept an eye on the CPU temps and it mostly hovered around 70-90C instead of 80-95C and that seemed to be the difference.

Frankly it's ridiculous this has to be done, nothing to do with Adobe but everything to do with Intel. God help the average non-technical user who has this issue.

Some threads I referenced:

https://www.reddit.com/r/intel/comments/yatzzl/13900k_undervolting/

https://www.reddit.com/r/intel/comments/13o29w5/13900k_will_no_longer_run_dx12_games_crashingctds/

https://www.reddit.com/r/buildapc/comments/11uftum/rtx_4090_i9_13900k_pc_build_crashing_with/

https://www.overclock.net/threads/i9-13900k-crashes-in-some-games.1807106/

https://community.intel.com/t5/Processors/i9-13900KF-game-crashes-Core-Ratio-issue/td-p/1535286

As it's not an acceptable solution to have to undervolt the CPU (the CPU then takes a significant performance hit & not what I paid for), looks like I might have to RMA my CPU - oh the joys *eyeroll*

B

Bill Sprague

Adobe Expert

Thank you for explaining your solution. One of my frustrations in this and other forums is the assumption that all failures are due to buggy software. Mass marketed software can run well enoung on thousands of computers, but when it fails on mine, the software is at fault.

_

__Nat__Author

Known Participant

You're welcome. That's just ignorance (and I don't mean that in a derogatory way) - people will see that Adobe software crashed their computer, so they'll instantly blame Adobe. This is why decent support is required as well, to help diagnose the issue. Anyway if a senior support person gets back to me, I will go through it with them.

John T Smith

Adobe Expert

I was wrong on the temp... I just loaded https://www.cpuid.com/softwares/hwmonitor.html while doing an export

The reading is in Celsius and my CPU went from 40C resting to 80C while exporting

I still think your 95C is a bit high... but I don't know if that is the cause of your problem

_

__Nat__Author

Known Participant

Ok thanks. 80C is pretty cool for the export process.

There was actually an update to my BIOS, just from 10 to 10d so not major. Applied it last night and will try the export later and see if any improvement, but I doubt it.

_

__Nat__Author

Known Participant

I tried this morning, much cooler day today, the CPU wasn't getting as hot but still spiked to 90 at times. Still crashed with the same error. Probably won't be able to progress much til I hear from the senior support team. I'll update once I do. Thanks for everyone's help thus far.

John T Smith

Adobe Expert

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__Author

Known Participant

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.

John T Smith

Adobe Expert

I build my own (have built several over the years for me+wife+others) so checking one ram stick at a time would be easy for me... do you have a friend who can help with that?

The biggest thing there is looking at the motherboard manual to determine which slot is the 'main' one so you test a single ram stick in that slot

Also... my motherboard has 4 ram slots and the ram stick pairs do NOT go beside each other... to have the best speed/operation pairs of ram sticks go in A2+B2 slots if only 2 ram sticks (and add A1+B1 to have a full set)

Running a memory test program should give the same results

EDIT 2-25-24... I looked at the PDF for my ASUS and the layout is below

A1-----

A2----- this is the MAIN slot for only 1 ram stick

B1-----

B2----- this is the PAIRED slot for a 2nd ram stick

_

__Nat__Author

Known Participant

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

Adobe Expert

>Exception Message: 3221225622 {EXCEPTION} Privileged instruction.

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

_

__Nat__Author

Known Participant

Sure did - didn't resolve sadly

John T Smith

Adobe Expert

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

B

Bill Sprague

Adobe Expert

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__Author

Known Participant

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).

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

John T Smith

Adobe Expert

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__Author

Known Participant

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__Author

Known Participant

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

John T Smith

Adobe Expert

>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__Author

Known Participant

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__Author

Known Participant

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.

Sign up

To post, reply, or follow discussions, please sign in with your Adobe ID.

Sign in to Adobe Community

To post, reply, or follow discussions, please sign in with your Adobe ID.

Scanning file for viruses.

This file cannot be downloaded