Skip to main content
Inspiring
December 22, 2025
Question

Showstopping crashes in 25.6.3

  • December 22, 2025
  • 2 replies
  • 274 views

This isnt a bug report yet, its a sanity check:

I'm working on a largish project (for me at least), and sometimes when I open the project I get a crash:


Windows successfully diagnosed a low virtual memory condition. The following programs consumed the most virtual memory: Adobe Premiere Pro.exe (17144) consumed 147442409472 bytes, ImporterREDServer.exe (25508) consumed 1148080128 bytes, and ImporterREDServer.exe (19560) consumed 1090265088 bytes.


That 147gb that premiere wants is vaguely consistent.  I have been hardware troubleshooting the system for several days, getting chatGPT to analyse errors, and it keeps changing its mind over whether the root cause is system or software. Issues with boot took me too gigabyte support that blamed the CPU (13700k, so I replaced that with an older 12700k).  Bios is up to date,  intel and nvidea graphics drivers updated recently.  That virtual memory issue seems to trigger a cascade of crashes including wdm

Is it feasible that premiere would need that much ram, does is indicate a system issue? I'm on a deadline (of course!) This is happening at a very bad time. 

Windows 11 25h2
Gigabyte z690 aero d
nvme boot, separate nvme cache
media on areca raid 5 drive
RTX4080
System is 2.5 years old





2 replies

Community Expert
December 28, 2025

If you're working on a large project (typically over 20 MB), I highly recommend converting it into a Production and breaking it into smaller, modular projects. This is one of the most effective ways to reduce memory and processing load in Premiere Pro.

Here’s a simple way to set it up:

  1. Go to File > New > Production.
  2. In the Production panel, click the context menu (three lines) and choose Add Project to Production to bring in your existing project.
  3. Click the New Project button at the bottom of the panel to create sub-projects.
  4. With all projects open, start dragging (not copy/pasting) your sequences, media, and other assets into the appropriate sub-projects.

A helpful structure to reduce processing load:

  • Create a Media project that contains all your source media.
  • Create a Sequences project where you do most of your editing work.
  • If you have many backup sequences or versions, consider storing them in a separate Backups project.


This setup allows you to work primarily in the Sequences project and only open the Media or Backups projects when needed, keeping your session lightweight and more stable.

gethoAuthor
Inspiring
January 9, 2026

thanks paul, ok I'll need to work out a good workflow, as Im a big nester and bouncer - in order for the location of all those nests and bounced tracks to make sense.  But yes that sounds like a plan!

Adobe Employee
December 26, 2025

Hi there,

Resource utilization is dependent on several factors, like the complexity of the project, the type of media used & the effects applied. Is this always happening while doing a specific task, such as opening a project or rendering a clip, or is it random? Also, let us know the amount of RAM on your system, the type of media files used & if you have used any third-party effects.

 

Thanks,

Sumeet

gethoAuthor
Inspiring
January 9, 2026

64 gb ram, it happens in this scenario:

a big project that i was working on earlier on opening

it won't happen if I clear the media cache files before opening

The project contains NEV files and a few jpeg sequences. THe project file is 80mb, the prin file is 20mb. (Ive had 250mb files that open fine).  Photoshop beta (the current one) seems to behave slightly better.  On opening, all of the system ram gets used, then I can see the virtual file size creep up and continues to climb minutes after opening the file.