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
  • 6299 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

R Neil Haugen
Legend
July 13, 2024

I'm always amazed at the difference between machines. You say Resolve is fine on that computer.

 

I've got a laptop that is from early 2019, and was a powerhouse at the time. Specs that blow your rig away. And whole it ran R17 ... OK... Resolve 18 was such a dog on it I un-installed it. But it runs 24.x Premiere, both shipping and public beta, just fine.

Everyone's mileage always varies ...
Known Participant
July 13, 2024

Watch the video above... HDD for some reason loads video into RAM, SATA SSD does not behave like that anymore... PCI e NVMe is fine.
Just import video, DV AVI... CS6 is fine, Resolve is fine... 2024 is fine with PCIe NVMe only.

Christian.Z
Community Expert
Community Expert
July 13, 2024

this happened with me several times it was either a corrupt file or an essential graphics template that was screwing everything.
if you had an essential graphics tem p,ate that was built for a previous version of premiere, that might be your issue. otherwise, check on which file the conforming is being stuck and it will give you a hint if you have a corrupt file

Known Participant
July 13, 2024

CS6 is working fine, Resolve is fine, and does 2024 necessarily need a PCIe NVMe drive for DV AVI?
And for 16K videos, what is needed then?
There is no need to invent anything, there have been such bugs before...

R Neil Haugen
Legend
July 13, 2024

That's a nine year old 4 core CPU ... it's totally ancient by modern standards. It's surprising Premiere runs at all on that CPU. No wonder it's maxed out all the time.

 

Our first computer for our business was around 1987 or so ... an 80386 we got, with the added RAM to have a full ridiculous amount of RAM, a full meg of RAM! Our pro peers laughed at it. And ... we got the truly massive 40 meg hard drive! Absurd! You'll never need all that!

 

I don't know how many computers we've had since. Many. I've had ... five laptops, alone ... maybe six actually. My "new" rig is a 3 year old 24 core Ryzen 3960x with 128Gb of RAM and a 2080Ti. That GPU I'll probably replace with a 4070 this fall. Or something like that.

 

I get 4-five years for a "main" computer, which when replaced, is my backup rig. I hate migrating to a new computer, but it's absolutely necessary to keep working away.

 

Tis Life in the Computer Age.

Everyone's mileage always varies ...
MyerPj
Community Expert
Community Expert
July 12, 2024

FWIW: Your system is a little weaker than the one I built in 2017. I had a i7-v6850 and 64mb of ram. The 850 evo is a SATA drive a standard SSD, it's not an M.2 and your data/clips are stored on a spinning drive.

 

That's not really a system that you can keep doing upgrades to software into 2024. At some place the software overwhelms the hardware. If your's kept going to 2022, that's pretty good. 

 

I replaced that machine in 2022, with a 12th gen i9-12900k and that's working well currently, and has 4 M.2 drives.

Known Participant
July 12, 2024

Thank you Kevin,

It is not my responsibility to find an alternate workflow for a bug that your software introduced in recent versions. It may be a practical necessity, but I resent the suggestion that the burden of dealing with this lies on the user.

I do not need to run an analysis tool to tell you how the Blackmagic MJPEG codec works with Premiere. Or, more precisely, how it is supposed to work. The Blackmagic MJPEG video will load natively in Premiere without any issues, although Premiere interprets the video as full range when it is in fact limited range. (Fixable with Lumetri preset.) The audio will not load in Premiere unless the Blackmagic Desktop Software (including drivers) is installed. This is the way it has always been. And that is what the thread you linked is about. If the Blackmagic codec is not installed, the system will not recognize the audio. This is not an error per se, but simply a missing codec. Yes, Blackmagic messed up here, they could have just used uncompressed PCM, but they did something weird. Maybe it's a cross-platform issue.

This setup worked fine in Premiere 2022.x. I have experienced massive performance issues with every version of Premiere I have tried to use since then. And since I am not permitted to download v2022 anymore, I cannot revert to a working version. My project file is useless. It will not load or play video at all. And I have no recourse. So you can imagine my infinite frustration.

Here are my device specs:

Processor Intel(R) Core(TM) i7-6700 CPU @ 3.40GHz 3.41 GHz
RAM 32.0 GB
Edition Windows 10 Pro Version 22H

NVIDIA GeForce 3060, driver 555.99
System drive: Samsung SSD 850 EVO M.2
Data drive (where video files are stored): WDC WUH721414ALE6L4 SATA

Known Participant
July 12, 2024

@Kevin-Monahan 
A video showing this error
_https://vk.com/video-14495031_456243037

Kevin-Monahan
Community Manager
Community Manager
July 12, 2024

I have updated the status of this bug, @aaronfross.

 

Thanks,
Kevin

Kevin Monahan - Sr. Community and Engagement Strategist – Adobe Pro Video and Audio
Kevin-Monahan
Community Manager
Community Manager
July 12, 2024

Hello @aaronfross,

Thanks for writing in with your bug report. If you can provide further details about your setup, the team would appreciate it. See, How do I write a bug report?

 

Has this workflow worked in the past? I read about another user running the files through GSPOT and found that there was an audio codec error. See this post: https://adobe.ly/3WhU3Sr

 

Is it possible to use a different codec that might be less problematic for your workflow? Let the community know.

 

Sorry for the hassle.

 

Thanks,
Kevin

Kevin Monahan - Sr. Community and Engagement Strategist – Adobe Pro Video and Audio