• Global community
    • Language:
      • Deutsch
      • English
      • Español
      • Français
      • Português
  • 日本語コミュニティ
    Dedicated community for Japanese speakers
  • 한국 커뮤니티
    Dedicated community for Korean speakers
Exit
1

Premiere Pro & Media Encoder Crashing On Brand New Windows 11 PC

New Here ,
Jul 24, 2023 Jul 24, 2023

Copy link to clipboard

Copied

Summary

When using Premiere Pro or Media Encoder, my new PC would BSOD and restart under certain conditions. Having run diagnostics and fixed any Windows 11 issues, it's only Premiere Pro or Media Encoder software which crashes (no more BSOD or restarts). No other software is crashing on my PC. I need this PC for editing work so I'm deeply frustrated and unable to work properly which is costing me greatly.

 

I just finished a reinstall of Windows 11 and the same issues remain.

Only Premiere / Media Encoder crash.

 

The following actions cause a crash

Rendering a 4k timeline in-to-out within Premiere
Creating proxies from 4k footage using Media Encoder
Exporting 4k footage using Media Encoder

 

PC Specs

*Intel Core i9-11900F 2.5 GHz 8-Core Processor
* ARCTIC Freezer 7 X CO CPU Cooler
* Z590 GAMING X ATX LGA1200 Motherboard
* 64 GB (2 x 32 GB) DDR4-3200 CL16 Memory
* 2 TB M.2-2280 PCIe 4.0 X4 NVME Solid State Drive
* 2 TB M.2-2280 PCIe 4.0 X4 NVME Solid State Drive
* RTX 4070 Ti 12 GB Video Card
* Deepcool MATREXX 55 MESH ATX Mid Tower Case
* 1050 W 80+ Silver Certified Semi-modular ATX Power Supply
* Windows 11 Pro 64bit installed with all the drivers up to date

 

Nvidia Studio Driver 536.67

 

Adobe Premiere Pro 2023
Adobe Media Encoder 2023

 

All drivers are as up-to-date as possible, from what I can tell.
Adobe Creative Cloud Diagnostics found no issues with my machine.

 

The only plugins I use in premiere are audio plugins- FabFiler suite and izotope RX (I've disabled them).

 

The initial issue was that my PC would BSOD and restart when trying to export 4k footage from Premiere, using Media Encoder. In order to try and resolve this I tried rendering the timeline in-to-out which also caused a crash in Premiere. I then tried creating proxies of the 4k files and this made Media Encoder crash.

Occasionally creating proxies or exporting a 4k video through Media Encoder will work (maybe one in twenty times) but I have never successfuly rendered a timeline in Premiere Pro 23. This always crashes without fail.

 

I'm able to edit 4k footage without proxies, run dynamic links to After Effects and edit with both programs open, no issues.

 

I've also exported 720p versions of the same videos so far without issue.

 

Premiere Pro uses 100% of my CPU on export or render, and around 30-40% of my memory
Media encoder uses anywhere from 65-95% of CPU and 30-40% of memory

 

I have tried
Removing all attributes from my clips
Reimporting clips
New sequences
New projects
New timelines
Different footage from a different camera
Resetting Premiere Pro preferences
Clearing the Adobe cache
Exporting in different codecs
Software-only encoding
Disabling plugins (I only had audio plugins)
Uninstalling NVidia Geforce Experience
Reinstalling Premiere Pro 23
Rolling back Premiere Pro to 2022
Running Premiere Pro as Admin
Placing my clips on the C: drive (instead of D:)
Complete reinstall of Windows 11

 

 

The BSOD error messages I initially experienced (before Windows 11 reinstall)

 

1. system_service_exception
what failed: win32kbase.sys

 

2. IRQL_NOT_LESS_OR_EQUAL

 

I have eliminated 1&2 by running sfc /scannow, and Windows DISM.
This seemed to fixed any issues with Windows 11.

 

3. memory_management

 

I ran Windows Memory Diagnostic and there are no issues with my memory.
Adobe apps are set to use up to 48gb of RAM if necessary.

 

All BSODs have now stopped. I have repaired Windows 11, and then opted for a complete reinstall of Windows 11.

The only issue now is Premiere Pro and / or Media Encoder crashing.


I don't know what I can do after this point.

Adobe support have remotely watched me crash my PC and called it a Windows 11 issue.
After fixing and then reinstalling Windows 11, I cannot find any issues with Windows.

 

 

Crash logs that I have located so far


Windows 11 Application Crash Logs (Adobe):

Faulting application name: Adobe Premiere Pro.exe, version: 23.5.0.56, time stamp: 0x6483b6e7
Faulting module name: dvacore.dll, version: 23.5.0.56, time stamp: 0x6483ad95
Exception code: 0xc000001d
Fault offset: 0x0000000000051504
Faulting process ID: 0x0x2C7C
Faulting application start time: 0x0x1D9B8A6E1A8A5ED
Faulting application path: C:\Program Files\Adobe\Adobe Premiere Pro 2023\Adobe Premiere Pro.exe
Faulting module path: C:\Program Files\Adobe\Adobe Premiere Pro 2023\dvacore.dll
Report ID: 4a3d430d-ab2e-4b87-8b99-806d455a1417
Faulting package full name:
Faulting package-relative application ID:

 

Adobe crash log 2:

Faulting application name: Adobe Premiere Pro.exe, version: 23.5.0.56, time stamp: 0x6483b6e7
Faulting module name: dvacore.dll, version: 23.5.0.56, time stamp: 0x6483ad95
Exception code: 0xc0000409
Fault offset: 0x0000000000288275
Faulting process ID: 0x0x3154
Faulting application start time: 0x0x1D9BB20CE3676A2
Faulting application path: C:\Program Files\Adobe\Adobe Premiere Pro 2023\Adobe Premiere Pro.exe
Faulting module path: C:\Program Files\Adobe\Adobe Premiere Pro 2023\dvacore.dll
Report ID: 5eca4f49-b561-425c-ba90-e962cc99a1b4
Faulting package full name:
Faulting package-relative application ID:

 

Adobe Crash log 3:

Faulting application name: Adobe Premiere Pro.exe, version: 23.5.0.56, time stamp: 0x6483b6e7
Faulting module name: ntdll.dll, version: 10.0.22621.1928, time stamp: 0x7dd9e350
Exception code: 0xc0000374
Fault offset: 0x000000000010c1f9
Faulting process ID: 0x0x3EB0
Faulting application start time: 0x0x1D9B971E99C7758
Faulting application path: C:\Program Files\Adobe\Adobe Premiere Pro 2023\Adobe Premiere Pro.exe
Faulting module path: C:\WINDOWS\SYSTEM32\ntdll.dll
Report ID: 3c38fbce-d72c-421f-bb18-bdcd0e45a6d0
Faulting package full name:
Faulting package-relative application ID:

 

 

Windows 11 BSOD log: (before Windows 11 fixes / reinstall which stopped all blue screens)

1. BSOD 'Memory Management'

Fault bucket , type 0
Event Name: BlueScreen
Response: Not available
Cab Id: 0

Problem signature:
P1: 1a
P2: 61941
P3: 21aea0000
P4: d
P5: fffffb869fd973a0
P6: 10_0_22621
P7: 0_0
P8: 256_1
P9:
P10:

Attached files:
\\?\C:\WINDOWS\Minidump\071923-10031-01.dmp
\\?\C:\WINDOWS\SystemTemp\WER-10031-0.sysdata.xml
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER.6ed6ac46-29ec-4b72-853f-df411d895cc8.tmp.WERInternalMetadata.xml
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER.26ce97cd-4c54-4e76-9e03-5c4caa70fa99.tmp.csv
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER.d9bb4931-e5c4-4ade-8691-e92534b33643.tmp.txt
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER.4c92f0f0-bd47-4743-ab82-931af3ff23c7.tmp.xml

These files may be available here:
\\?\C:\ProgramData\Microsoft\Windows\WER\ReportArchive\Kernel_1a_8149ce375c2b9accf844b0acb99ae82469e4abd8_00000000_cab_64a14dea-28ab-4e93-83fe-1fc8cab0882e

Analysis symbol:
Rechecking for solution: 0
Report Id: 6da7aa6c-dc8b-44b4-8e79-1ab336c1ca99
Report Status: 2049
Hashed bucket:
Cab Guid: 0

TOPICS
Export

Views

834

Translate

Translate

Report

Report
Community guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
community guidelines
Community Beginner ,
Aug 07, 2023 Aug 07, 2023

Copy link to clipboard

Copied

Hey, I have a 4070 GPU and am experiencing the exact same issues - whenever I try to export it'll run for a few seconds then either PP with crash or more often I'll get BSOD with varying errror codes - all of which include the ones you mentioned.. Any luck with fixing this issue yet?

Votes

Translate

Translate

Report

Report
Community guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
community guidelines
Community Expert ,
Aug 07, 2023 Aug 07, 2023

Copy link to clipboard

Copied

Hola, lamento oir que tienes problemas con el software, pero al parecer podría ser un fallo del sistema operativo (Windows)

Harold Silva B.

Votes

Translate

Translate

Report

Report
Community guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
community guidelines
New Here ,
Aug 07, 2023 Aug 07, 2023

Copy link to clipboard

Copied

Hey, sorry to hear you're having the same problem.

Unfortunately I've still not been able to resolve it despite a LOT of troubleshooting and trying different workarounds for weeks now. It's very hard to pinpoint the source of the issue. At the moment I'm considering getting a new machine, possibly a Mac. Adobe, Windows and Nvidia all seem to be unable to offer a solution.

Votes

Translate

Translate

Report

Report
Community guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
community guidelines
Community Beginner ,
Aug 07, 2023 Aug 07, 2023

Copy link to clipboard

Copied

I've used all different versions of Nvidia game driver, different versions of PP, i've used DisplayDriverUninstaller to clean wipe all my drivers in windows safe mode, I've used Adobe media encoder, but PP just does not want to work despite all of this - my components work absolutely fine e.g. ram, cpu etc.

Weird this is when I use my cpu to export it doesnt ramp up in temperature and it works absolutely fine to export - but with gpu the whole thing crashes

Votes

Translate

Translate

Report

Report
Community guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
community guidelines
Community Expert ,
Aug 07, 2023 Aug 07, 2023

Copy link to clipboard

Copied

Hi Joe, excellent write up. You've tried many things. I hope you can get it sorted. I was thinking of purchasing a 4070 today actually! 🙂

 

I haven't had any problems with PP, Windows slightly as it finally updated to 22H2 about 2 weeks ago. I use ExplorerPatcher and I was having a Windows issue where the Volume slider/bar that appears when you adjust the volume from Keyboard keys was gone. I picked up a hint somethere that EP was an issue, so I uninstalled that and the slider was back. I posted on GitHub, and it turned out to be a Preview KB. I had turned on in Windows\Updates, 'Get the latest updates as soon as they are available' in my quest to get 22H2, so, I uninstalled that and the slider was back. I also turned off the Updates option, as I've not cared to be a beta tester for Window.

 

Sorry for that long bit, but the problem could be anywhere. I had a very persistent problem one time, similar to yours. I tried many things like you have. Mine was a graphics problem also, but not PP. So, I went back to the beginning and Did a clean install of Windows. (Reinstalling in place does almost never fix the problem). So, I'm taking it you clean reinstalled from nothing. Then I loaded my problem software, and the problem was gone. Then I started adding back all the things I need, and kept checking the program after each addition or two... still working. Finally I was getting to the end, and I installed my printer drivers. And bang! There it was.

 

So, if you can still reinstall windows. do that, then install PP and try it. Then build up your system and keep checking to see when/if it stops the problem.

 

Hope you find it.

Votes

Translate

Translate

Report

Report
Community guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
community guidelines
Community Beginner ,
Aug 12, 2023 Aug 12, 2023

Copy link to clipboard

Copied

LATEST

I solved my issue and it was with my RAM, I used the memtest86 software to test my ram - turns out all I had to do was take my ram out and pop it back in

Votes

Translate

Translate

Report

Report
Community guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
community guidelines