Page 1 of 1

Render process failed: Exit Code 128

Posted: Tue Jul 19, 2011 5:16 pm
by numerobis
What does Exit Code 128 mean?!?

Since a few days i have two big problems with my network machines. (WinXP X64)
On one system the rendering starts and crashes after a few SL's displaying "Render Process failed: Exit Code 128" . Sometimes it then starts again but it then crashes again...
I already have reinstalled maxwell...

The other problem is, that with cooparative rendering one machine starts about 5-6 min later than the others (with 4 PCs connected). It's not the same all the time, but changing.
The node is showing "New job order received"; "Connection for scene file reception."

:roll: :?:

Re: Render process failed: Exit Code 128

Posted: Wed Jul 20, 2011 8:26 pm
by polynurb
are you saying that always the same node crashes?
could be bad ram or chipset overheat/damage. try prime torture test and http://www.memtest.org/ (runs from dos) to make sure hardware is ok.

just a shot in the dark.. but also try rendering with material override.. to see if any of the textures could be source of the problem.

about the late start of the coop render.. no clue here really, but to check network integrity i usually copy large files (1GB+) and compare the m5d checksums.

hope this gives some help.

Re: Render process failed: Exit Code 128

Posted: Wed Jul 20, 2011 10:32 pm
by numerobis
yes, it's only one node that's crashing. The system is (was) LinX-stable and the temps are no problem. The sys was working without any problem for half a year now.
I had to make some hard reboots the last days, due to testing the energy saving settings, so maybe the system is corrupted now... I'll reinstall windows to see if this fixes the problem.
If this doesn't work i'll test the RAM and stability again. Thanks!

But it would be good to know what this 'exit code 128' means...

Re: Render process failed: Exit Code 128

Posted: Wed Jul 20, 2011 10:48 pm
by polynurb
numerobis wrote: due to testing the energy saving settings,
you mean you also changed bios settings?

maybe you already did this.. but sometimes a cold reboot does magic> set bios defaults (if you changed anything) >shutdown and unplug the power cord, leave it for at least 5 min before restart.