PC Constantly Crashing While Working in Premiere Pro 2025

[Editing Ninja]

Description:
Hi Adobe Community,

I’ve been dealing with constant crashes while using Adobe Premiere Pro 2025, and I’m hoping someone here can help me figure out what’s going wrong. This problem has persisted for some time, and although I’ve tried various troubleshooting steps, the crashes continue to happen.

Nature of the Crash:

My PC crashes whenever I perform tasks that require more graphical power, like rendering, scrubbing through the timeline, masking, or even something as simple as adding guide lines on the screen. The crashes occur randomly—sometimes after just 5 minutes of editing, and other times after an hour. The frustrating part is that for the last two days, everything was fine without a single crash, but this morning it crashed five times while exporting videos. Exporting through Media Encoder 2025 also caused crashes.

When Premiere Pro crashes, it freezes up, and my entire system becomes unresponsive, forcing me to hard reset the PC. If I don’t perform a hard reset, eventually a blue screen appears with the following error codes:

• Stop code: PAGE_FAULT_IN_NONPAGED_AREA
• DPC_WATCHDOG_VIOLATION

I am running Windows 11 Pro (fully updated).

PC Specifications:

• Processor: AMD Ryzen 9 7950X 16-Core Processor (5nm, 16 Cores, 32 Threads, up to 5.46 GHz)
• Motherboard: ASUS PRIME X670-P WIFI (PCI-Express 5.0)
• RAM: 128 GB DDR5 (Corsair, 5200 MHz)
• GPU: NVIDIA GeForce RTX 4090 (24 GB GDDR6X)
• Storage: PCIe 4.0 NVMe SSD (Plenty of space available)
• OS: Windows 11 Pro (Up to date)
• Premiere Version: 25.0 (Latest Version)

What I’ve Tried So Far:

Updating Drivers:

• I’ve updated my GPU drivers to the latest NVIDIA Studio Drivers. My motherboard BIOS and chipset drivers are also fully updated.

Reinstalling Premiere Pro:

• I’ve uninstalled and reinstalled Premiere Pro 2025 several times, always ensuring it’s the latest version, but the crashes persist. I’m trying to avoid reverting to the 2024 version.

Clearing Cache:

• I’ve cleared the media cache in Premiere Pro, but this has not resolved the issue.

Disabling GPU Acceleration:

• I switched from GPU acceleration (CUDA) to Software Only mode in the Project Settings. While I haven’t experienced any crashes in this mode, Premiere Pro becomes significantly slower and far less efficient, making it impractical to keep working this way.

Lowering Playback Resolution:

• I’ve lowered the playback resolution to the minimum and paused previews, trying to reduce the load on the GPU, but crashes still occur.

Testing with Different Projects:

• I’ve worked on several different projects, including smaller ones with lower-resolution footage, but the issue remains across all of them.

Disabling Background Apps:

• I’ve disabled all unnecessary background applications, but this hasn’t made any difference.

System Stress Tests:

• I’ve run stress tests on both my CPU and GPU to check for hardware issues, but everything seems to be functioning normally under load.

Checking Windows Event Viewer:

• After every crash, I’ve checked the Event Viewer logs. The most common errors are "Display driver stopped responding" or "Application Hang," but there’s no consistent pattern that points to a specific cause.

After Effects:

It’s important to note that I never experience crashes while using After Effects. Even when rendering heavy compositions or working with complex effects, the system is stable. The crashes are isolated to Premiere Pro.

What I Need Help With:

I’m really hoping someone can help me figure out what might be causing these crashes. Could it be a compatibility issue with Premiere Pro 25.0, or is there something in my system’s configuration that’s causing the instability? Any advice or guidance from the Adobe support team or the community would be greatly appreciated!

Thank you in advance for your help!

[Ann Bens]

Blue screen is usually a windows/hardware issue.

https://www.google.com/search?client=firefox-b-d&q=dpc+watchdog+violation+windows+11+blue+screen

https://www.google.nl/search?q=page_fault_in_nonpaged_area+windows+11&sca_esv=808c4f249ba0e78b&sxsrf...

[R Neil Haugen]

There have been Resolve users having crashes with 4000 GPUs, that swapped out to a 3000, and stopped crashing.

The speculation I've seen is that power draws in those may be spiking past what the PSU can supply. Or there's an internal issue.

[Editing Ninja]

Thanks for the feedback, Ann and Neil!

I’ve actually run several tests on my system, including stress tests for both the CPU and GPU, and everything seems to be functioning normally from a hardware standpoint. No issues with RAM or overheating either. The blue screen crashes only started after updating to Premiere Pro 2025, so I’m wondering if it could be tied to something with the new version.

Before the update, I was running Premiere Pro 2024 without any crashes (I bought the PC more than one year ago), and my system was completely stable. I’m still on Windows 11 Pro, fully updated, and the problem started right after the Premiere Pro update.

Neil, I saw your point about the power draw on 4000 GPUs. I’m using the RTX 4090, so maybe that’s worth looking into, but my PSU should be more than adequate for my setup. I’ll keep that in mind, though, in case it’s a voltage spike issue.

Appreciate any additional insights you might have!

[Pau Lina]

I've also had the same problems since upgrading to 2025. It's freaking me out because it can happen even 3 times in the same minute, and maybe even nearly 30 times in an hour. And I have been editing the same way for over a year now, so...

[glennjam]

I also have had Windows crashing when I leave Premier Pro open for too long while working on a project

[MyerPj]

I'm pleased with the startup speed of PP, so don't mind closing when I'm not using it for awhile. Also, rebooting my machine at times (and turning it off at night). So, it seems to have limited issues using it like such.

[Pau Lina]

Guys, thank you for your comments! I switched to DaVinci Resolve, and my life is 99% much easier now. No crashes, no freezing, I can add text, effects and... color grading is better.

[MyerPj]

I see you tested with different projects, were any of them new, started from scratch? 

FWIW: Clear the cache then start a new project. 

[Editing Ninja]

Now, when you mention that, it only happens on the projects that were started in Premiere Pro 2024 and continued in Premiere Pro 2025.

I haven't encountered that issue in the projects I've started from scratch in Premiere Pro 2025. That's a relief, especially since I'm currently finishing those projects and working on several new ones. Hopefully, this error will resolve itself once I complete all my projects that started in Premiere Pro  2024.

Ps. I have already cleared the cache several times.

[MyerPj]

Whenever I get crashes, it's usually because I didn't clear the cache on the new version. Also, a good practice is to create a new project in the new version and then IMPORT in a previous project you want to work on.

[R Neil Haugen]

Yes ... creating a new project file in the new version, then in the MediaBrowser panel, selecting a previous project file and Importing the contents is more reliable.

[Rach McIntire]

Hi @Editing Ninja ,

Welcome to the Premiere Pro forums! We are glad to see you here. You've given us alsmost all the info. We need a few more details to try to help with the issue. Please see, How do I write a bug report?

Thanks for submitting your bug report. I hope we can help you soon. Sorry for the frustration! 

Thanks,
Rach

[BereanPK]

I hate to say this, but I'm glad it's not just me!

I've been having this same exact problem with v25. Not just a well-endowed PC, but also on a high-powered Dell XPS laptop.

No problems with v24, but shortly after the latest v25 update, I'm also getting the random BSODs. Clean caches, clean installs, no extra bloatware running, etc. Still getting the BSODs.

For now, I'm convinced that it's something with v25 causing this. I'm going to downgrade to v24 and monitor for the resolution. 

[IanB_360]

Hi @Editing Ninja 

Could you try one thing and hold down the control key while opening Premiere Pro? It should give you a dialog box to clear cache, ignore 3rd party plugins for 1 time only etc. See if the project still crashes after this and we can try and think of other things that may be causing it. I have been able to open old projects from any 2024 Premiere versions and haven't been able to reproduce a crash yet, but we will continue to try and solve this and help you fix the issue you are having. Let us know after you open the project with holding down control if anything changes. 

Thank you 

Ian

[Alifer]

Same problem!
i9 14900K

RTX 4080S
112GB 5200Mhz

I guess it's something about V25. The down side is you can't downgrade to V24 because you've made progress with V25, especially if it's a huge project.

[lukeynewbs]

Same problem.

Absolutely BEYOND infuriating. 

Having the same project crash when I load up a sequence.  8 times in last 24 hours. 

Whole system crash - CPU panic and forces reboot. 

2.4 GHz 8-Core Intel Core i9

MD Radeon Pro 5500M 8 GB
Intel UHD Graphics 630 1536 MB

They need to stop tooling around with AI clip extensions and FOCUS on a stable application. 

Is a stable application that doesn't crash too much to ask for in 2024?

[BereanPK]

I made a different post on this issue here (https://community.adobe.com/t5/premiere-pro-bugs/pp25-keeps-crashing-windows-machines/idc-p/15002575...) and the Adobe folks have acknowledged the issue and are obviously looking into it.

In the meantime, I did actually start my latest project file in PP24 - and so far, I haven't had a crash or BSOD yet.  May be something to try until the PP25 bugs are identified and fixed.  Unlike some other software companies (like the medical EMR software company that my practice uses!), I have confidence in Adobe that they'll be able to identify this and correct the issues.

[Editing Ninja · Accepted solution]

It was my RAM; one of the modules was corrupted.

[MyerPj]

Thanks for letting us know. I had a bad stick once, but fortunatley I found it in the early stages of a new build. Cheers. 🙂

[Creative brain]

What did you do?  replaced the mod?

[IanB_360]

@Editing Ninja That sounds like good news. Are you saying that fixing the corrupted RAM solved the constant crashing? Are you now able to use your software as expected?

Thank you

Ian

[Pau Lina]

I've also had the same problems since upgrading to 2025. It's freaking me out because it can happen even 3 times in the same minute, and maybe even nearly 30 times in an hour. And I have been editing the same way for over a year now, so...

[laurencet23100334]

June 2025, exact same problem.  Brand new machine:

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

All drivers 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.  Have re-installed umpteen times. 
Same symptoms as everyone else is reporting: system starts to chug, becomes unresponsive and eventually freezes up, display blacks out and flickers, preview window breaks up like video static... I can't even open Task manager to see what's going on.  I eventually have to force reboot to get control of my system.  Occasionally I manage to close Premiere, but the effect continues to other usage apps, even something so basic as Google.  At that point I try a cold reboot and can't even get a response to complete that, it seems like whatever Premiere is trying to do is escalate hogging all the memory and resources somehow and refuses to clear until the system gives up.

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

Any advice is appreciated, I pay big bucks to use this software and this app has cost me a lot of wasted time and unproductivity.

Much appreciated.