24.0 issues: not enough system space to work properly - random crashes - black screen - importer 39

[Felix284463599exg]

So as seen here in the Forum, more and more People getting the same issues since they updated on 24.0. 

"adobe has not enough system space to work properly"

"randomly chrasing without any error codes"

"freezing whole systems when open"

"Blackscreen on one or more Monitors randomly"
".exe´s from any program randomly crashing since the update"

"task manager wont open when premiere pro crashing"

"failed to load importer 39" 
and so on...

every bug or error that i just described NEVER EVER happend before on my system. it started all when i updated to 24.0 and even when im downgrading to 23.6 or lower. NOTHING CHANGES.

Report your errors and Bugs below here so we can talk to each other to get some fixes done so that we can work normal again.

[Felix284463599exg]

aaaaaannnnnnnnnnnnnd its crashing again. worked for 30 minutes just fine and now when im moving in the timelime between clips i get the error code that some frames couldnt be loaded and then it just crashes without a crash report x)

[R Neil Haugen]

Thanks for the determined troubleshooting and continuing to post ... that's all necessary to get to what the hay is going wrong there.

[Felix284463599exg]

im out of ideas, it was working after running cleaner tool, 30 minutes into cutting a error code appears that some frames couldnt be loaded when i tried to cut something out. i closed premiere pro afterwards and shut down my computer and went to the gym. When i got home i wanted to try the project again and when i open the project i get the notification that the project was started on an older version of premiere pro wich simply cant be true. i just started it today after premiere pro was working again and it was version 24.0. so how does this happen? 

[Felix284463599exg]

same situation all over again. "adobe is running on low system memory" i dont even know anymore what is meant by that. ram is running fine. over 100gb free space on every SSD. "a low level expection occured. failed to load : Importer MPEG : importer39" 8 of all video files are only audio because "file is not supported" while these exact files working perfectly fine 3 hours ago when everything was "fixed". im kinda done and i really thinking about swapping to davinci resolve if i dont get it fixed this week. help or you lost a paying customer

[MyerPj]

System memory is you ram, not your ssd's.

[SteveBalaam]

I don't know whether this is any use, but my highly specced machine would fail to refresh different parts of the screen, then randomly hang on moving a clip (or pretty much any edit).  Just changing the Bin view to list rather than thumbnails cured all this wierdness, and I seem to remember this happening with an earlier release of Premiere before...

[R Neil Haugen]

Thanks for posting, that's ... interesting data.

[Felix284463599exg]

@MyerPj okay but why do i get this notification when only 65% of ram is used by premiere pro while media playing? and why didnt i get this notification anytime before in premiere pro? when i was working on 23.6 or older with 4k footage, everything was working fine, no crashes or freezes 🙂 also sad that i dont get any help by the adobe employees who posted here, even when i tagged them and begging for help 🙂 

[Cam33037693ztth]

I thought it was just me but yes I am also having problems since updating to 2024 I even talked to the support team twice they had full acces to compter fixed the problem by simply telling me to continue deleting media cache which ive never had to do on 2023 version . 2024 version is just hoorible my timeline is very laggy and its freezing video as I move through timeline and also when I watch over the video the audio will continue playing but the video frames would just freeze. Horrible I pay to much money to be having these problems with a software so expensive please fix.

[R Neil Haugen]

I know it sounds weird, but this has fixed playback issues for a number of users.

Go to the Audio preferences, and make sure that the Default Input is set to None.

[MyerPj]

Go to your Creative Cloud account, and look around for contact us, there's a 'Chat' button you can reach tech support. If that doesn't work, the phone number will be close by that chat. Ask for the Video Que when you reach a tech.

[Felix284463599exg]

@Cam33037693ztth was the worst decision ever to update it to 24.0.

NONE of all of these issues appeared ever before in older versions. i was completly fine editing 4k footage with 16gb of ram. nothing was crashing or something and since i updated it to 24.0 it wont stop crashing. i can edit stuff for 5 minutes and then premiere justs closes, without a crash report or else. it just closes. sometimes i press play and the video freezes, the video player turns black or sound crashes. NOTHING was happening for a whole year before this update.  i will finish this project in premiere pro or im gonna try at least and after that i will switch to davinci resolve 100%. you guys lost me with this one. 

[Felix284463599exg]

@Cam33037693ztth ahhaa i just deleted the media cache like you did, restarted premiere pro and now all of my video files in the project are "offline" while i didnt moved them at all and i cant relink them. i have to rename and copy every single video now on my ssds to make them work again. im sooooooooooooooooooooooooo done 😄 bye bye adobe. subscriptions is cancled 🙂

[k_pop]

I had to roll back. Transcriptions aren't working, time line crashes while keeping playing. MXF wave forms aren't showing randomly. oh capture tool is gone, now i can't use my blackmagic capture card to record vo's using a better preamp than my mobo. very sluggy choppy timeline, that only fixes itsef on a reset of workspace. OH! my in and outs disapear visually off my program and preview monitors. GARBAGE PREMIERE. i though you couldn't get worse after an update corrupted all my working projects and made ever clip on the time line start at source media's first frame. Get it together adobe! 

[jstrawn]

@k_pop That sounds like a lot of trouble and I hope that going back to a previous version will get things working. For the Timeline crashes, please send in the crash report if you can and enter a short description of what you were doing at the time of the crash.

Also, tape based workflows (including Capture) were removed from PrPro as of version 24.0. I know that is not good for some users. Here is a link explaining why that decision was made:
https://helpx.adobe.com/premiere-pro/kb/retiring-tape-based-workflows.html

Note that major versions of Pr can co-exist, so you can keep Pr 23.0 around for Capture even if/when you get upgraded to a 24.0 or higher version.

[k_pop]

@Felix284463599exg system memory is RAM not harddrive space. 

[MichaelBuieFilms]

I'mhaving crash after crash, too. Becaause it happends on memory intesive Canon RAW files, I was thinking that is the reason. But all these other folk reporting teh same quick crashes make me wonder:

https://community.adobe.com/t5/premiere-pro-bugs/definitely-premiere-pro-crashing-needs-reboot-playi...

[bboxbbox]

Running split screen with 4K / HD footage, two single long clips, working on a Mac Mini M1 chip with 16GB RAM. I've needed to disable one of the tracks to adjust the 4K alignment on the subject in the other track. Creating a proxy for that clip - under 20 minutes long - ME has repeatedly hung attempting to create the proxy, runing memory up to 60GB. I just worked with the sluggish performance without a proxy and attempted to encode the 22m:04s edit through ME. It repeatedly hung, running up around 60GB memory while MacOS popped up saying it's out of memory and quit other apps. Thought there might be something up with ME (v24.1) and I've had better luck in the past with performance doing encode directly in PP. Tried doing the full encode in PP and it ran up to similar level of memory and hung again. Wondered if it was choking on the position FX so encoded one half of the split screen on the theory that if PP had a static clip to work with it would perform better encoding the mix. Bounced out, imported the result and replaced the position adjusted clip with the new clip. Ran the new export straight from PP with both sides of the split screen and the encode made it through without hanging on the memory issue. Rolling the encode result through Quicktime, I've got rubbish. Panes freezing, losing the higher quality image side - just black - really poor image quality on the HD side and audio sync completely out of whack. I haven't had any of these issues previously - this is a weekly process I've been running for working up choreography for a dance piece that the dancers are using to practice between sessions. I've been running the beta releases over the past month or two and on PP v24.1.0.68 today with ME v24.1.0.62. Not sure what they did with this week's releases but it's something that has basically broken the apps.

[default5ehktl8zamvt]

The fix for my workstation.

I reset all prefs, caches etc by Hold Shift + Open PP. I also changed audio hardware input prefs to 'none' as suggested by @R Neil Haugen . One of these seems to have fixed this PP24 issue for me. Sry I probably should have changed these one at a time to isolate the fix but in a tad bit of a hurry to finish an edit 🙂 If you're looking for leaset disruption to your current setup I'd suggest try Neils audio input fix first. Hope this helps someone.

[Cameron17392073rj7j]

Time remapping doesnt work at all 

[Harvish25182475o6rd]

it same thing it going on my pc .. im clueless even though i clear my cache and use cleaner tool to clean 

STILL NOT WORKING .. IM HAVING TROUBLE ON VERSION 24

[MyerPj]

Harvish, come back when you feel you can post something helpful. IE: What's not working? What's the trouble. Maybe create a thread if it is something unique to you.

[Harvish25182475o6rd]

Well i think i got the answer update ur software to windows 11 and remove the third party plugins from

C:\Program Files\Adobe\Common\Plug-ins\7.0\MediaCore

Hope this will work for u guys

[MyerPj]

Thanks for sending that. I was in that place with a new build debating Win 10 or 11. I've been glad many times I went 11, plus there are performance gains with Intel CPUs on 11.

[Harvish25182475o6rd]

So it's works for u now seem.. Well then it's answer for V24 broken to Reborn 😆