P: Premiere Pro Closes For No Reason While Editing

Same issue here 😞

Just upgraded to a i9 processor as my last one was struggling to playback videos.

At least it didn't crash all the time.

Faulting application name: Adobe Premiere Pro.exe, version: 24.4.1.2, time stamp: 0x6647be3a
Faulting module name: ImageRenderer.dll, version: 24.4.1.2, time stamp: 0x6647b94c
Exception code: 0xc0000409
Fault offset: 0x000000000015ab5d
Faulting process id: 0x0x476C
Faulting application start time: 0x0x1DAF479443B3595
Faulting application path: C:\Program Files\Adobe\Adobe Premiere Pro 2024\Adobe Premiere Pro.exe
Faulting module path: C:\Program Files\Adobe\Adobe Premiere Pro 2024\ImageRenderer.dll
Report Id: c9026215-ba20-48f1-a0d1-7a5e0525079c
Faulting package full name:
Faulting package-relative application ID:

Only fix was to roll back but my assistant on 24 so I am forced to use this version on some projects.  Doesn't make any sense?!

I have the same problem!

I would like to add to this thread, I changed two things that have helped with stability, not sure what is the correlating factor here but hopefully this will help add more context to the issue: 

1. Downgraded to PP v24.3

2. Editing with proxies for my .MXF footage. 

So, I'm not sure if the source of this issue stems from a bug in the new version of PP, or if my .MXF footage was causing instability. @Kevin-Monahan is there a good article about .MXF footage in relation to Premiere Pro? 

Swinging the hammer for ya'll @Keale. I hope to have some news for you soon.

Thanks,
Kevin

AAAAND after the most recent update, it still is happening: 

Faulting application name: Adobe Premiere Pro.exe, version: 24.5.0.57, time stamp: 0x666374b0
Faulting module name: ImageRenderer.dll, version: 24.5.0.57, time stamp: 0x66636fd9
Exception code: 0xc0000409
Fault offset: 0x000000000015c5fd
Faulting process id: 0x0x10B0
Faulting application start time: 0x0x1DAE9F17A48A4F8
Faulting application path: C:\Program Files\Adobe\Adobe Premiere Pro 2024\Adobe Premiere Pro.exe
Faulting module path: C:\Program Files\Adobe\Adobe Premiere Pro 2024\ImageRenderer.dll
Report Id: b5aed5b7-318c-4a54-896e-57492564d172
Faulting package full name:
Faulting package-relative application ID:

Nonsensical update - I just got the second Adobe tech support rep's email with directions, a full day later.  He wanted me to go to Windows graphics settings and tell Windows to prioritize my GPU for Premiere... 

This is after I repeatedly told him I don't have any other GPU or a processor with an APU.  Complete garbage tech support on that tier.  Please for the love of god how do I reach a developer/software engineer???

@Kevin-Monahan 
Really need some actual Adobe eyes on this and not just the Indian tier 1 tech-support guys I've been dealing with.  Yesterday I engaged with Adobe tech support and the first guy remote connected to my PC and uninstalled/reinstalled a bunch of Microsoft C++ Redistributables, then gave full permissions to basically every Adobe folder in the filesystem.  Then asked me to test Premiere while he watched.  I said the crash can sometimes take as much as 5 or more minutes before it happens, he said he'd wait.  After a few minutes he said it appeared to be fixed and logged off, and at that same moment Premiere crashed again with the ImageRenderer.dll at fault.  And then every time I tried to start working again it would almost instantly crash.

I immediately tried to get back with tech support and was connected to another rep, who tried to tell me I needed to update/reinstall my graphics card.  I explained this was not a GPU issue, he wanted to remote in and begin.  I asked what he planned to do, and he said if I wasn't comfortable with him remote connecting he would email instructions on what I should do.  He promptly disconnected and I never received any emailed instructions.

Shortly after that I downgraded to 24.0.3 on a whim and had ZERO issues working for the following 9 hours.  Seems like nothing wrong with my GPU if one version of Premiere works and others don't.  I'd really like to get back to a more recent version at some point for the AI voice enhancement, as I'm getting great results with it, but right now I just need to get this edit built and make up for days of lost work.

Please push this through to whatever next tier or support is available.  I can provide dump files from these errors to diagnose and troubleshoot, just let me know where to send them.  Or just let me know how I can get past tier 1 Adobe tech support, they're just following the usual scripts and I can't lose any more hours to them. 

Hi @Kevin-Monahan 

We replaced the corrupt .dll and upon restart, I could no longer open Premiere Pro. I just kept getting this message:

Just to advise we have opted not to reinstall my OS since it was only recently done.

Having replaced the .dll with my original I am once again getting crashes in my project, when using graphics in my project. When will there be a fix please? This is proving to be a very frustrating time using Premiere Pro... 😞

Premiere Beta 24.6 and 25 now crashing every few minutes with a GDI object leak.  I can't work in any version of the software now.  Really need some help getting at least one version to run for more than 5 minutes, please advise ASAP.

Fault bucket 1626229430769651381, type 5
Event Name: GDIObjectLeak
Response: Not available
Cab Id: 0

Problem signature:
P1: Adobe Premiere Pro (Beta).exe
P2: 25.0.0.14
P3: 1638400.14
P4: a
P5: 9ff85a75668e4
P6:
P7:
P8:
P9:
P10:

Attached files:
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WERE1C0.tmp.WERInternalMetadata.xml
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WERE1FF.tmp.xml
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WERE210.tmp.csv
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WERE240.tmp.txt
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WERE24F.tmp.mdmp
\\?\C:\Users\devon\AppData\Local\Temp\WEREEA4.tmp.WERDataCollectionStatus.txt
WERGenerationLog.txt

These files may be available here:
\\?\C:\ProgramData\Microsoft\Windows\WER\ReportArchive\NonCritical_Adobe Premiere P_c567134d679d9ee539794563f3912b8ac72b6774_00000000_65f82fd7-ac46-456d-af65-fd1569592f9f

Analysis symbol:
Rechecking for solution: 0
Report Id: 65f82fd7-ac46-456d-af65-fd1569592f9f
Report Status: 268435456
Hashed bucket: de1ade4206aaff22f691870d184f8eb5
Cab Guid: 0

Happy to actually send over dump files if someone would work with me here.  This is my job on the line guys and this is seriously F-ing me right now.