July 2025: Premiere Pro throttles PC then crashes it on every use

[laurencet23100334]

July 2025, Brand new machine with clean install of Premiere:

MBOARD: ASUS ROG Strix Z890-I
PROCESSOR: Intel Core Ultra 9 285K Desktop
DISPLAY: NVidia RTX 5080 16GB
RAM: Corsair Vengeance RGB 96GB DDR5-5200
Main Drive: 1TB M.2 SSD
Secondary Drive (Internal): 8TB M.2 SSD (some media files are here)
Third Drive (Internal): 20GB SATA (other media files are here)
Windows 11 Pro

All drivers fully upgraded, all Win 11 upgrades applied, all hardware benchmarked and stress tested with no problems. Cache cleared, 3rd party disabled, blah blah.

Photoshop, Elements, Acrobat, etc all work fine. The problems only arise when I open and try working with Premiere Pro 2025. I have re-installed umpteen times.  It affects new projects and previously-created projects.
Same symptoms as has been reported in other threads:
Within 5 - 10 minutes or so (or less), system starts to chug, display blacks out and flickers, preview window breaks up with video static, Premiere becomes unresponsive and eventually freezes up then bricks my machine ... I can't even open Task manager to see what's going on.
If I'm lucky I manage to close Premiere out, but the effect will continue when attempting to use other apps by choking even something so basic as a Google search. It often ends with me doing a cold reboot.
It appears that Premiere is somehow escalate hogging memory + resources without flushing, based on how it bogs down its own application and then refuses to release the memory to other apps, even when closed.

Previous system (Win10, much less powerful) NEVER had this issue.

Any advice is appreciated, I pay big bucks to use this software, have dozens of work projects which cannot be recreated from scratch just to appease the beast, and this app is now costing me a lot of wasted time and unproductivity.

[Peru Bob]

Try updating or rolling back your graphics driver directly from the video card manufacturer’s site.  Do a clean installation of a Studio Driver (NOT the Game Driver).

[Rach McIntire]

Hi @laurencet23100334, 

I'm sorry to hear you're having crashing issues in Premiere.  That's always frustrating.   Did Peru Bob's suggestion help?  Hopefully it did, but if not, I have a few follow-up questions.

What type of footage are you working with? Are there any reproducible steps we can take to try to recreate this issue? When Premiere reopens, does it give you the Send to Adobe Crash dialogue? If you can have Task Manager open when Premiere is hanging and try to save a DMP, that might illuminate what's going on. It would also be interesting to see what happens in there after Premiere is closed and the behavior lingers.

[laurencet23100334]

@Peru Bob:  Done.  I rolled back the driver, uninstalled via DDU Uninstaller to make sure everything was gone, then got the last version of the Studio driver from GeForce.com and re-installed.  A couple of reboots later and the problem persists.

@Rach McIntire:  I work largely with H264 mp4 files.  I have never had a problem with these in the past, and I have been using Adobe for at least 20 yrs.  It happens on both saved and new PP project files.  I tried opening a file (post-driver update above) with Task Manager running.  I checked the Processes and Memory tabs and Premiere Pro's memory usage shot up to 90GB at one point !!!!!  Then stabilized back down to 3GB....!!!  This is a really high footprint for just an app interface!!

I don't get the 'Send Crash Report' dialogue box when Premiere reopens.  I managed to close Premiere and saw a window saying "Closing Media Encoding Process" (or something along that line) which hung as the status bar moved along-  I had never seen that before.

I left the computer alone for another 20 min with no other activity, and the only windows I left open was the Windows Explorer and the Waterfox browser window.  Both were locked on 'Not responding' and wouldn't come back even if I tried minimizing/maximizing the windows.  As I mentioned is the necessity earlier, I had to cold reboot to use my system.

This is definitely something Premiere is doing in the background.  When I see that the memory isn't released even after closing the program it convicts Premiere even more.  That 'media encoding' window is very suspicious, as if Premiere is trying to re-encode something for its own purpose and taxing my system for its resources.

Is there a way to create a crash report with Premiere, or some kind of log file that will tell me where the resources are going when Premiere is open?  Keep in mind that even Task Manager stops responding as soon as Premiere is opened.

Thanks.

[laurencet23100334]

@Rach McIntire:  Update- Premiere Pro is completely unusable now, even just opening the app is a detonator for a reboot. 😖

Last night I tried an experiment- I simply opened PP 2025 and created a new project.  Didn't add anything, no clips, no renaming, no settings changes, nothing.  Walked away for about 2 minutes and came back to a blackscreen and bricked system.  Mouse, keyboard, CTRL+SHFT+DEL had no effect.  Even my monitor said "No Signal" although my drive activity light was solid white and I could hear my system grinding.  Had to force reboot to get control of my computer again.

I tried reverting back to PP 2024 and the same issue occurs, so this is definitely something Adobe has rolled out on top of the software updates recently.  It appears to be a background process that is spiralling out of control, hogging memory and resources until the system dies.  
(user comment deleted by mod - Adobe does not train its AI on customer content)

I hope a solution can be found soon

[Alex367466572b5i]

@laurencet23100334 
Use the utility for RTX 50 - Nvidia Firmware Update Utility.
https://www.nvidia.com/content/DriverDownloads/confirmation.php?url=/Windows/uefi/firmware/2.0/NVIDI...

[laurencet23100334]

@Alex367466572b5i   thanks for this.  

However, firmware was updated, rebooted system twice, opened empty test project, Premiere behaviour has not changed.  😑

[laurencet23100334]

@Rach McIntire    @Peru Bob   Update:  Tried opening in Win11 safe mode.  Instant crash.  Report states:

Dump Summary
------------
Dump File: 0aed4d38-b6e3-4d14-8951-c66dc7397a21.dmp : C:\Users\(me)\AppData\Local\Temp\Adobe\Premiere Pro\25.0\SentryIO-db\reports\0aed4d38-b6e3-4d14-8951-c66dc7397a21.dmp
Last Write Time: 2025-07-04 10:40:01 AM
Process Name: Adobe Premiere Pro.exe : C:\Program Files\Adobe\Adobe Premiere Pro 2025\Adobe Premiere Pro.exe
Process Architecture: x64
Exception Code: 0xC0000005
Exception Information: The thread tried to read from or write to a virtual address for which it does not have the appropriate access.
Heap Information: Not Present

System Information
------------------
OS Version: 10.0.26100
CLR Version(s):

Modules
-------
Module Name Module Path Module Version
----------- ----------- --------------
Adobe Premiere Pro.exe C:\Program Files\Adobe\Adobe Premiere Pro 2025\Adobe Premiere Pro.exe 25.3.0.84
ntdll.dll C:\WINDOWS\SYSTEM32\ntdll.dll 10.0.26100.4484
KERNEL32.DLL C:\WINDOWS\System32\KERNEL32.DLL 10.0.26100.4484
KERNELBASE.dll C:\WINDOWS\System32\KERNELBASE.dll 10.0.26100.4484
apphelp.dll C:\WINDOWS\SYSTEM32\apphelp.dll 10.0.26100.4484
...
Windows.UI.dll C:\Windows\System32\Windows.UI.dll 10.0.26100.4484
OneCoreUAPCommonProxyStub.dll C:\Windows\System32\OneCoreUAPCommonProxyStub.dll 10.0.26100.4484

So I tried 'Run as administrator', did not change outcome. 
Did full uninstall using Creative Cloud Cleaner Tool.
Rebooted a couple times.  Re-installed Creative Cloud.
Installed Beta version of Premiere Pro.  Seems to be working OK for now but I haven't exported one of my heavier work projects yet.

Lost a full week of work because of the software.  And the point is that the supposed accepted versions should be working upon release. 
Adobe, please do better.
Anyone from Adobe care to comment?

[MyerPj]

<<I tried reverting back to PP 2024 and the same issue occurs, so this is definitely something Adobe has rolled out on top of the software updates recently.>>

I'm confused at your conclusion above. Two version of the software don't work, and you think it's the software? That would more to me indicate it's the hardware. Same machine for both.

<<July 2025, Brand new machine with clean install of Premiere:>>

Has PP ever worked on that machine?

So, it's just new this month? (it's only the 4th). Can you reinstall Windows, doing a clean install? I'm sorry if I didn't see it, but which version of Windows are you running?

I'm running a clean install of Windows 24H2, just a month ago, and PP 25.3 and beta 25.4 b72 is working very well.

12th gen, 12900k, 64gb, everything on M.2 drives, rtx-4070

If you can clean install Windows, then just Creative Cloud and PP, and see how that goes.

And no utitilities, like fan control, especially NO head-up software, I only install the two drivers (video and audio) from a 'clean' install of nvidia studio driver, NO geforce or physx, etc.

As stock as you can get it, and see if PP runs, if so, then add your stuff back in and keep testing it.

BTW: @Rach McIntire is from Adobe.

[Alex367466572b5i]

@MyerPj rtx 4070 & rtx 5080... 

[Rach McIntire]

Do you have any anti-virus software running?

[FlyingFourFun]

After reading all the posts, I would like you to consider the following.

The Intel 285 CPU is something a little special and different than prev generations. 

there is a BIOS upgrade that was created, that turns up the internal speed of the bus for that CPU;

You can read about it here and watch the video.  This is effectively an overclock for that CPU that’s fully support from Intel and the MB OEM's

Intel Improves 285K Performance with a Big Update : r/intel

Intel Improves 285K Performance with a Big Update

If you don’t have this update applied, you may want to try it.

BUT

It’s more likely you do have it applied as any decent system builder would have done this update.   As a result, you should consider turnoff the effects of the update and see if it brings you stability.  This 285 CPU comes with memory performance and tuning considerations that could make it not stable in some cases.  Detuning the memory to operate at lower speeds should bring some stability to the system (or at least worth a try).

With that said.

What you’re describing seems like an overheating issue, which can be caused by a number of issues, including things like overclocking, improper fan curves for cooling, incorrect fan setup - and potentially, not correctly installed thermal paste between the CPU and the cooler.

I would suggest downloading an app that will let you monitor the GPU Temp, MB temps, Memory temp, CPU temp (Core and Package) and see how those change over time.  It’s possible to have limited overheating in one spot.

It might be a fishing trip, but these two things are the first things that jump out at me when I read your symptoms.

I had a system with a memory controller problem, which was only corrected with a replacement CPU from Intel when I first built my system, they overclocked the memory using the XMP profile, and this burnt out the memory controller (which is built into the CPU on the last few generations).

The Bios update I mentioned at the start of this post is officially supported overclock, but you also need fully support memory and perfect timing / matched memory (with 96GB I believe they did a matched memory kit for you).

I would do the temp checks first, and see if anything jumps out, if nothing jumps out, de-tun the memory speeds to induce stability.  If that brings stability you will want to consider a different memory kit or keep the slower speeds (you don’t lose much performance when you de-tun the memory when it comes to premiere but gets lots of stability).

I hope this helps you with directions to investigate.