OTOY Forums

did you babysit the render process? You may be getting this error due to energy save, screen savers, sleep mode or similar things. Probably not it, but just in case

ram temperature....
cpu temperature....
gpu temperature....

Yes, I've babysat it all and it was fine, I watched it crash on several occasions. No warning or anything, just blink max crash. No other programs affected, I render very often all night so I always have no windows updates, no antivirus kicking on, no screensaver and max energy settings.

Temps are never getting past 70c.


Random crashes are normal and I'm used to them, but the interesting thing I noticed about this one is that the rendered image during the crash is only saving 10% of the image to disk and leaving 90% blank but the visible 10% is cleaned to the correct number of samples, every time. That's what I find intriguing. It means the render is complete and it tries to save the image, and then must crash near instantly since it doesn't get to finish writing the image to disk.

but the project is over, I was able to restart the render several times to complete it. Now I'm just puzzled by why it happened.

tehfailsafe wrote:Random crashes are normal and I'm used to them, but the interesting thing I noticed about this one is that the rendered image during the crash is only saving 10% of the image to disk and leaving 90% blank but the visible 10% is cleaned to the correct number of samples, every time. That's what I find intriguing. It means the render is complete and it tries to save the image, and then must crash near instantly since it doesn't get to finish writing the image to disk.

but the project is over, I was able to restart the render several times to complete it. Now I'm just puzzled by why it happened.

just a thought: from my experience random crashes are often (very often) hardware related. saving the image is imo done via the external (and 3rd party) freeimage library, so this is even not directly octane related. afaik it is a single threaded process thus might be cpu-hogging, and as it is disk related it might having problems with the disk and/or disk controller, disk driver, etc...

Hi,

I am having the same problem. Did anyone find any solution to this perhaps? BTW: all my PU temperatures (GPUs and CPU) don't get above 50°, so this shouldn't be a problem.

Thanks,
Mitja

Just in case anyone is reading this: it turned out that the problem was that i had PhysX enabled. I switched it to CPU (and disabled SLI of course) and it seems it is working now. It still crashes sometimes when I have directlighting enabled (instead of pathtracing or PMC), but I didn't test it thoroughly.

Cheers,
M

Hah!
I had been recently doing experiments with rayfire and physx... Let me go turn that off and give some more tries!!

same for the...a few crashes when rendering DL animations.

no problems with PT or PMC

I have the same problem - octane crashes at low temps (45-50C at both gpus). My solution is to downgrade nvidia drivers to 285.62 and set Physx to CPU. It works for now.

CPU, GPU..have You thought about PSU?

Sometimes instabilities are caused for power managment =)
If the temps for cpu/gpu are norm and RAM runs at stable speeds.

List up You hardware, with exact models ( &brands)

Try to conect other PSU (if You have a chance without buying one)
- that might solve Your issues. Just an idea..