'aerendercore' consuming more RAM than allocated

[EdgarFalcao]

This problem randomly started happening at the beginning of the week and is happening across multiple versions of After Effects and projects that were rendered normally before.

I currently have 32Gb RAM from which 16Gb is allocated for Adobe software. After experiencing the infamous error -1609629695 (that still wasn't solved for me), I started investigating other possible reason for my constant error messages.

This got me to discover Adobe Products consuming 89% of my RAM. Sometimes my projects render normally, as it was before, but more often than not, error messages are piling up, and everything on my computer crashes at once.

After some time, I found this:

'aerendercore' seems to be the culprit.

Other software like Blender or Audacity are functioning normally.

Is there a certain way for Adobe products to use the RAM I allow it to use?

[EdgarFalcao]

I have already cleared caches, tried duplicating projects, starting new projects, rescuing old ones to compare, and using older drivers for my GTX 2060 and Intel i7. My disk space hasn't changed.

[Mylenium]

If it crashes, provide crash info. Otherwise exact system info and details about your settings would be a good start. Cropped screenshots don't tell us much and are basically useless. If it only started in the last week, there's a good chance soemthing on your system changed like a system update or an updated driver, so look into that and try and undo whatever may have happened there. Also booting into safe mode and running Windows Update may clean up some botched stuff thast may be causing this issue.

Mylenium

[EdgarFalcao]

Hey Mylenium,

Sorry for not providing the necessary information.

 

I was tracking RAM consumption during render. From that screen was where I found 'aerendercore' consuming way more RAM than allowed. After the elapsed time froze for some time, I opened Ae's window again and met those messages:

 

From where I could find, those problems have been solved before.

- Error 23 :: 40

- Error 0 :: 9997

Right after that, Me's render crashed and showed me this:

Today I've tried duplicating some projects and rescuing old projects from my backup, all of them went through the same cycle.

[Mylenium]

Any chance you have changed your graphics settings whiel messing around with Blender or your autodesk software. The error clearly states a "Could not generate (drawing) surface/ tile" error. I know it's tedious, but you may need to check that agasin.

Mylenium

[EdgarFalcao]

I tried reinstalling my GPU driver and restoring default settings, but that also didn't work. 😞

Can the graphics interfere with RAM consumption in Ae? Adobe products rarely go beyond 20% GPU, even when I use Element 3D.

[EdgarFalcao]

UPDATE: I just realized that even after closing Ae and Me, they go on consuming at least 40% RAM indefinitely.

[Mylenium]

Reinstall the MSVC runtimes directly from Microsoft and possibly also the legacy .NET 3.5 runtimes. The latest Windows Update changed soem things there and it may affect some of your stuff.

Mylenium

[EdgarFalcao]

​FINAL UPDATE: I had to open a support ticket that went over two days (and a lot of ping-pong between attendants and technicians) before someone sent me over to a technician called Mohammad, that solved all of my problems in a pinch. Basically, he reinstalled a lot of C++ libraries and ran an 'AdobeCreativeCloudCleanerTool' and software from Guru3D.com. It took a while and a couple of restarts, but eventually, the problem was solved. He also ran a couple of command lines that I definitely didn't understand, but if my render is going fine, I'm more than happy. I know it's not much, but I hope this helps someone else with the same problem.

Thank you for your time, Mylenium, and also thanks Mohammad for helping me!

[EdgarFalcao]

Well, that wasn't the final update. The problem came back just as bad as before.

[Peter_Apple]

Did you solve the problem?

[EdgarFalcao]

So far, yes!

[Peter_Apple]

How?

[EdgarFalcao]

I reinstalled Creative Cloud and started using AfterCodecs to render instead of Media Encoder. Unfortunately, the software is $89, but at least it solved my problem.

[Oleh30037151frpq]

Yeah , i kind of figured it out. So what worked for me is to turn of aerendercore with "force quitting" and making my Media Encoder pause. After a whiel i just pressed resume and it started working waaay faster. Don't know why , just worked for me.

[sintagmático]

Hola, me estoy encontrando con el mismo problema... desde dónde forzaste el apagado de aerendercore? Gracias!

[Laura23597047sgmh]

yo tambien tengo el mismo problema