Skip to main content
D
daoldenburger
Participant
July 10, 2012
Question

(CS6) Error during render: "Internal Verification failure, sorry!{could not find itemframe we now..

  • July 10, 2012
  • 9 replies
  • 80663 views

Hello,

I've updated to CS6 since last week, but since then I'm getting the weirdest error when rendering. I recieve the error with different projects,compositions and render settings.

Specifications:

  • Windows 7 X64
  • After Effects CS6
  • Intel Core i7 3930k
  • Nvidia GTX 550ti
  • 32GB Ram
  • Multiprocessing is ON

The error message: "After Effects error: internal verification failure, sorry! {could not find itemframe we just now checked in}"

But there is more to it; after recieving this error, i tried to empty the disk cache(for some reason unknow to me I thought the problem would be there), but when doing so After Effects just freezes, won't shut down, won't exit (not even using the taskmanger, with either 'end task' or 'end process') Yes that is right, after effects won't even close when using the end process button in the task manger...

It gets even better still: When I try to manually delete the disk cache folder on my (seperate) SSD. The windows explorer dialog box just hangs on 'discovering files for deletion' (or something like that). If I try to exit te dialog box, explorer freezes. The only way to get out of this mess seems to be a HARD reset (because just resetting my computer from windows will hang it, because windows is trying to close all the programs and after effects just won't die).

After a reset of my computer, the manual deletion of the disk cache folder goes without problem. After deleting the folder, and booting up AE I can render out my composition without any errors at all.

Dying for some help here, I can duplicate this problem any time you like , if you need more specifications or otherwise, please let me know.

With regards,

David

Message was edited by: daoldenburger; typos

This topic has been closed for replies.

9 replies

Z
zewt
Inspiring
May 14, 2015

I just hit this bug too, on CC 2014.2.  This a pretty critical bug: having a long render that you're waiting for fail in the middle is a big problem.  Unfortunately it's hard to reproduce, and I don't think I have any new information that would help track the problem down.  It would help if there was a diagnostic log that gave more information that we could provide when it happens, but I don't know of one.

For what it's worth, I often see what appear to be caching bugs, eg. where a layer would disappear at a particular time, and the workaround is to move the timeline (so it's not sitting on the problem frame), clear cache, and restart AFX.  This may have no connection--just mentioning it since some people said that clearing cache fixed this error for them.

MattRody
MattRody
Participant
March 12, 2015

Thank you guys so much for your help! Had to render a fashion video with high resolution Tiffs and kept having that issue. I emptied the Disk Cache and it fixed it immediately! 

V
viktography
Participant
April 24, 2014

Got same error during 4K 15min footage render.

But, I got it working by set actual used CPU as 6.

Render time gap between setting as 10 and 6 CPUs was around 20 min. (50min and 1hr 10min)

Previously I tried change the setting of actual used CPU as 8, 10, 12 also the RAM allocation as 2, 3, 4, 6.

Guess it is the right setting for me. I read post that AE might get error if you set actual using CPU over 6 for now.

For the note, if I set actual CPU lesser and lesser then the render more longer until it stoped by error.

 

Tested on

2013 new Mac pro with 1T SSD(source from external HDD, outcome to local), 64RAM, AMD firepro D700 6G VRAM with 10 core xeon cpu(manually installed)

Hope this setting help you guys out.

K
Khurram
Participant
March 11, 2014

Disabling multiprocessing worked for me. Hope to get it fixed in the next update. Adobe come on! it has been over a year complaining.

Windows 7 X64 - After Effects CS6 - Intel Xeon 12 CPU - Nvidia Quadro 4000 - 512 GB SSD - 24GB Ram - 2TB Sata

R
Rajagopalacharia
Participant
April 7, 2013

I thought Adobe After Effects was a commercial grade application? Doesn't it cost people  around $1,000 to get this program, and yet it cannot reliably render footage with more than one processor? The worst part about this failure is that you cannot pick up where you left off. Surprisingly, the algorithm doesn't attempt to retry or correct itself. It just bails with a oddly worded error message, reminiscent of a freeware application. I think folks spend $10,000+ on multi-processor machines specifically to do things like: render footage in programs like Adobe After Effects, so really you'd think Adobe would have extra safeguards into something as critical and time consuming as the rendering process. Nothing worse than being a few days in, just to have rendering fail unrecoverably, and then having to turn off multi-processing at the expense of taking twice as long. Please Adobe, fix it now, or at least have a way to recover from the failure. I thought this was in your quality standards.

    BenjaminMarkus
    BenjaminMarkus
    Inspiring
    April 8, 2013

    You can file a feature request here. More on how to give feedback. 

    As a workaround I would render to a high quality image sequence.  That way if your render gets stopped you can pick up right where you left off.  Just make sure you have the "Skip Existing Files" box checked in Best Settings so After Effects won't re-render any frames:

    When you're render is complete, you can just reimport that image sequence into After Effects and render it out as a movie file.

    J
    JamesPurdie
    Participant
    October 4, 2013

    Well irritatingly, I did jußt that, but now after effcts keeps forgettin the location of my third and large image sequence.  I'm not sure why.  Lucky I didnt go to bed after starting the render, but checked and suddenly noticed the multi color bars message for missin footage over my third sequence.  Even after I reimport the footage, AFX CS6 keeps forgetting the location for some reason.

    Michael___XLsior_Media
    Michael___XLsior_Media
    Participating Frequently
    December 16, 2012

    Emptying the disk cache worked for me.

    Preferences>Media & Disk Cache>Empty Disk Cache>OK

    B
    brian@godsplanforlife.org
    Participant
    November 24, 2019

    Emptying the disk cache worked for me.

    M
    Myles Trevino
    Participant
    July 15, 2012

    I fixed this by disabling multiprocessing right after I got the error (which for some reason only happened on one of my projects). I didn't empty disk cache or anything else though.

    -Selym

      D
      dustinwilson80
      Known Participant
      September 10, 2012

      Just to echo what SelymDesign mentioned. Disabling the multiprocessing fixed the error for me as well. Allowing me to render the comp.

      Mylenium
      Mylenium
      Legend
      July 11, 2012

      Probably some driver issue where the current comp buffer isn't disassociated with whatever is the "current item frame" and some file I/O operation locks up. Can be the graphics, can be your SSD driver. You could run a tool like Sysinternals' System Monitor to filter such I/O operations. That might provide a clue where it goes belly up....

      Mylenium

      Mr__MatuskeY
      Mr__MatuskeY
      Participant
      January 2, 2013

      Yup, disabled multiprocessing and it worked for me. (Windows 8, CS6)

      BenjaminMarkus
      BenjaminMarkus
      Inspiring
      July 10, 2012

      Looking into this. Try checking the rest of these FAQs in the meantime...

      "FAQ: What information should I provide when asking a question on this forum?"


      Terms & ConditionsAccessibility statement
      Using the community Terms of use Privacy Cookie preferences Do not sell or share my personal information ad choicesAdChoices