PC crashes while rendering

[Brian Charles]

If you are suggesting this: 1080p Comp > 720p Comp > 1080p Comp, make sure that collapse transformations is on, otherwise you’ll soften the image.

As far as h.264 is concerned, don’t output that from AE, use media encoder or compressor if you’re on a mac.

[Bogdan Brak]

“If you are suggesting this: 1080p Comp > 720p Comp > 1080p Comp, make sure that collapse transformations is on, otherwise you’ll soften the image”

yes…actually that’s what i’m suggesting. but i have a lot of comps of different sizes in between.
Is it then necessary to turn on the collapse button in every single comp or is it enough to do it only in the final comp?

i’ve read about this collapse-checkbox in the manual but i did’n get how it really work.

when i pressed it somewhere in the middle comps everything got f***** up. when i pressed it at the final comp i couldn’t see any obvious diffrence (with my eyes).

[Cory Petkovsek]

Write down your stop errors and do google searches on them. As I said they are signs of either hardware faults or kernel-space software faults (drivers, messed up os files, kernel-space apps like a/v). They will give you specific information to troubleshoot with. See if you always get the same one, or if they are different. Hopefully you get the same one. If they’re always different, you’ve got big problems.

If you can’t fix it with driver upgrades, and nothing conclusive comes up from specific, component by component stress testing (test one thing at a time for a while to see if it crashes), then you have to rule out software. Uninstall your a/v (temporarily, while testing). Learn how to do driver verification and system file verification within windows.

If you find nothing there, then the way to rule out corrupt os files or kernel space appps is to format your drive and install windows. Just install windows and AE or the adobe suite, and anything you need to render these specific jobs. Work with that, with minimal software and see if you can get it to crash. If so, then it’s either hardware, or one of the apps you just installed. If you only installed AE, then it’s for sure hardware. If you installed some drivers for your tablet and drivers for your console and codecs, it could be one of those. Keep the test case as minimal as possible.

If it’s for sure hardware, yet your stress testing didn’t identify which subsystem is the problem, then you need to remove hardware and see if it helps. Unplug any unnecessary hardware (tablets, printers, usb anything). Do you have an older video card available? Swap it out and test with AE (the only thing that crashes the os). Or buy a cheap one for $30 to test with. Take out half the ram and test. Put it back and take out the other half and test (keep the same slots).

Cory

—
Cory Petkovsek
Corporate Video

[Bogdan Brak]

Well guys.
Thanks for your participation in solving my problems.
Because of lack of time I can’t do completley hardware test and reinstall the OS. I will do this when the project is done.

But somehow I think it could be the latest Quicktime Player version that messes something up.
In the bgeinning I told you that I’m exporting my TIFF-sequence embed in a QT Container.
After I changed my rendersettings to a pure TIFF-sequence I could render my footage twice without any errors or BSODs.
I was still using multiprocessing an gave 6,5 GB RAM to AE.
I only changed the value in the “secret” menu to 20 or 25.

Maybe finally… is it recommendable to use MP with a 4-core-sytem (3,2GHz) and 8 RAM? Yesterday I read here in the forum that even with 8GB RAM it should NOT be used. Are there any special pros and contras?

[Enea Doku]

yes i’m having the same problem

[Torsten Gruenwald]

Hi folks,
this is works when you have blue screen by rendering:

Briefly, try render audio and video seperatly and do some prefences to clear cache and memory and check your precompostions…
Here an small text- tutorial: https://greenwoodworx-media.blogspot.de/2013/08/after-effects-cs5-cs6-crash-blue-screen.html