Skip to main content
Known Participant
June 27, 2024
Answered

100% disk access and 100% RAM usage for no reason, completely blocking my ability to work

  • June 27, 2024
  • 67 replies
  • 6628 views

Show-stopping performance issue here! I am completely blocked from being able to work at all. Premiere is currently using 100% disk access and 100%+ memory usage, sitting idle, doing nothing!

 

In Premiere Pro 2024, I opened a project originally created in v2023. Was prompted to convert the file format. After doing so, disk access on the drive where the video files are stored immediately skyrocketed to 100%. It stayed that way for a very long time. Two hours later, the drive was still being hammered to death. Completely unable to use Premiere at all, it was dead in the water because it couldn't play any files. CPU usage was near zero.

 

Resource Monitor showed Premiere reading the source footage files. If it was trying to build peaks and caches, it did so with extreme inefficiency.

 

Even worse, after closing the project, disk access persisted at 100%. Resource Monitor showed the same few source footage files being read. Eventually Premiere got tired I guess, or it felt it had punished the drive enough, and eventually petered out after about five minutes.

 

Other projects opened normally, there were a few seconds of heavy disk access but then it went back to normal -- zero access when Premiere is idle.

 

Of course I restarted the Windows 10 PC, but that made no difference.

 

Updated to 2024.5, re-converted the original v2023 project file, but that made no difference.

 

Deleted all Media Cache files through Preferences, but that made no difference.

 

I did notice that projects using footage encoded with Blackmagic MJPEG codec hit the drive a lot harder than projects using footage encoded with NVIDIA NVENC H264. I guess H264 files don't need caches at all?

 

The problematic project has about 100 source files, TRT 14 hours, all encoded with Blackmagic MJPEG. Totaling about 400GB, which is kind of a lot, I know. It's showing them all as offline while it hammers the hard drive, presumably trying to build caches and peaks. So one might conclude that there's a performance issue with the codec? It's not hardware accelerated. But there was no issue whatsoever when I originally edited this project in Premiere 2023. And again, CPU usage is near zero, so the problem seems to be completely about hard drive access.

 

Contrast this with another project using the same codec, with only ten files totaling 3GB, TRT 30 minutes. Even after deleting all cache files, the smaller project takes ~15 seconds to load. The larger project does not finish loading even after two hours. The math here doesn't seem to add up. I could imagine that 400GB would take a half hour at most. Not multiple hours.

 

I did update the Blackmagic Desktop Video software, which includes the MJPEG codec. Not really relevant, though, because Premiere has native support for MJPEG. It just won't load the audio in the AVI files created by Blackmagic unless the Blackmagic codec is installed. Not a concern for me here because I'm not even using that audio. But updating the Blackmagic software made no difference.

 

Any way you slice it, a project should not take hours to load, even if the source footage is 400GB. I am really not accustomed to this sort of behavior. Sony Vegas never made me wait for hours while it ground my hard drive to dust, no matter how large the source footage folder was. If this is supposed to be speeding up my workflow, I regret to have to say that it is the opposite of that. It has completely shut me down.

 

I really don't want to erase my preferences, since it was a huge PITA to get Premiere set up to be even remotely close to an efficient workflow.

 

So what am I supposed to do here? Reinstall v2023? I doubt that would make any difference, as it seems the issue is just massive inefficiency in building the cache files.

 

Is there any option to NOT build these cache files? Or to control how many files are read simultaneously? Maybe if it was only reading one file at a time it wouldn't be fighting itself for limited bandwidth?

 

BTW, the hard drive is not super fast, but it is a 7200 RPM Western Digital platter, internal. Again, if I were to do a backup, I would expect that 400GB would take maybe a half hour to transfer. Not multiple hours!

 

And why are these caches temporary external files in the first place? If they take so long to build, shouldn't they be persistent? If not stored in the project file, at least stored next to the source footage? That's an option for the peak files. Why not the cache files? Why set things up for failure like this?

 

In the end, I let the computer sit for hours until the disk access went back to zero. All of the footage in the bins finally read as being found, not pending, and all of the statistics were visible. Tried to access the timeline and BOOM, disk access went back to 100%. What the actual frak?!?! And now RAM usage is pegged at the maximum, too! I have 32GB RAM and have 6GB reserved for other applications. Premiere has gone totally rogue here, consumed 100% of disk time and 100% of memory. Now it's using the page file, completely runaway process, it's currently up to 44 GB and still rising. SITTING IDLE, DOING NOTHING.

 

I turned off the timeline thumbnails with the super secret hotkey. No change. Disk access still pegged at 100%. RAM usage still greater than the maximum I set aside for Premiere. What is Premiere even doing? It's not building caches, it's not playing the timeline, it's just sitting idle. This is OUTRAGEOUS! Resource Monitor says it's still accessing those source files. But WHY???

 

How do I get back to being able to actually work?

 

This is just shocking!!! It's acting like malware!

Correct answer andrzej_1443

Hello everyone.

I uploaded Premiere 2025 today. It looks like the disk problem has been 100% fixed. Same computer, same configuration. I didn't change anything. It turns out that the problem was in the Premiere 2024 software. This is the worst situation I've ever had with Adobe. It cost me a lot of time, nerves, searching for a solution to the problem, which made work very difficult and prolonged. It was a serious software error. I hope that nothing so significant will happen in the future. Adobe, please give me another month of use for free! Either way, I consider Adobe software and the Premiere program to be a very, very good work tool. I started my adventure with Premiere with Premiere 6.5. It continues to this day!

67 replies

MyerPj
Community Expert
Community Expert
June 29, 2024

Wow!

<<Can you explain why a minimum processor state of 100% would cause any problem, or have any relevance whatsoever to this issue?>>

 
Uh... let's think here... hmm... what the name of this thread:
100% disk access and 100% RAM usage for no reason
 
No, sense in trying to help here. Ugh...

 

Participant
June 29, 2024

Before you relink to any clips can you look through the project and click on the timeline with no problems?  To me that means Premiere is having a problem loading the clips - which could be a disk/computer problem or could be this version does not like those AVIs.  My next step would be convert one of those clips to a MOV and link to the MOV not the AVI.  Does it carry on working?

R Neil Haugen
Legend
June 29, 2024

As to partitions, they made sense with the older, and far slower spinning disc drives. Partitions did speed data read/write. Which was the only reason for using them.

 

On the far faster spinners of the last decade, they don't increase access. And of course don't increase access speeds on SSDs. There simply isn't a reason for them anymore.

 

As to the other questions, we're other users, not devs. And we are not having such issues on anything we work with. So we are trying to do remote troubleshooting to help you.

 

This seems to be between the specific media you are working with and the project files, perhaps.

Everyone's mileage always varies ...
Known Participant
June 29, 2024

Can you explain why a minimum processor state of 100% would cause any problem, or have any relevance whatsoever to this issue?

Can you explain why partitions "make things slower"?

Known Participant
June 29, 2024

Changed the name of the media's enclosing folder. Opened the project. Converted to 2024.5. Left all files offline. Relinked a single file through the Project window. Disk usage again skyrocketed to 100%, presumably while building cache, but Progress window remained blank.

After waiting at least five minutes for the cache of a 30 minute file to be built, tried to access the timeline. Again was blocked by 100% disk access. After a few more minutes, it finally stopped. Performance appeared normal until I moved the play head to a different point on the timeline. As soon as it touched a second UNLINKED clip, disk access slammed back up to 100%. Waited another five minutes or so, then disk access went back to zero and things seemed to work normally.

Relinked a second file. Waited five minutes for the cache of an eight minute file to build. Tried to access the timeline. That clip played OK. Tried to access the first clip on the timeline. Again blocked by 100% disk access. Premiere was having problems accessing the file that it had no problems with a few minutes earlier.

After waiting another five minutes for the first file to load in the timeline, moved the play head to the second file in the timeline. Disk access again skyrocketed back up to 100%, but only for maybe 30 seconds. The second clip now played OK.

Moved the play head back to the first file. Disk access skyrocketed back up to 100%. Waited another five minutes or so.

During all of this, RAM usage massively increased in sync with the disk access. When disk usage went back to zero, saved the project and exited Premiere to reclaim all of that RAM.

Relaunched Premiere. Disk access and RAM consumption immediately went back up to maximum.

None of this is supposed to happen. My conclusion is that Premiere is broken. Truly, seriously, massively broken.


A shockingly unacceptable situation. Total waste of time and effort. I am truly horrified by this, and it only makes me even more super cynical about Premiere than I was before.

MyerPj
Community Expert
Community Expert
June 29, 2024

Oh, another FWIW: partitions are decidedly old-school. There's basically no point to them, it's makes things slower. Opt for another disk/ssd if you need one.

MyerPj
Community Expert
Community Expert
June 29, 2024

Then you know the feature. Try the default, Balanced power option. That won't take long to test.

FWIW: It's the minimum processor state that is the problem. Always running 100%... makes no sense.

 

 

Known Participant
June 29, 2024

dskchk /r showed no issues on any partition of the physical disk.

Installed Premiere v2023.0, and was prompted to convert the project. Apparently it was created in v2022.x. And I am not permitted to download any version earlier than v2023.0. That is just wrong.

And, unrelated to anything, Creative Cloud now gives zero user feedback on app installation. I have no idea what the F Adobe is doing to my computer, or when it's finished. Again, that is just wrong.

Known Participant
June 29, 2024

Can you elaborate on why you think High Performance power plan is problematic?

I actually have always customized the power plan, turning off all of the power saving features, processor throttling, etc. etc. I am a 3D artist and always need to prioritize performance over everything else. For decades.

Known Participant
January 9, 2025

I had a similar problem with disk access from PP up to 80%. I just restored my Power Setting to Balanced and the disk madness went to 0%. Try it if you haven't tried it already.

MyerPj
Community Expert
Community Expert
January 9, 2025

Yes, I mentioned that a few times on the 1st page, it's always good to see confirmation. Balanced is the only way to go. High Performance just brings up your processor all the time (or at least to the 'minimum' set level). Waste of energy and hard on the machine.

MyerPj
Community Expert
Community Expert
June 29, 2024

Another shot in the dark here: How about Windows Power Options? Perhaps it's set to "High Performance" which generally does that. I would never use that mode.