Re: Serious errors when using Octane C4D
Posted: Wed Jan 11, 2017 12:06 pm
I have felt your pain. Some things I did in similar situations...
1) Try an older version of Octane, I've had luck with this. Uninstall both the plugin and stand alone, and install both from an older build. The first 3.0 worked better for me than the next two did, when I was getting crashes. (In my case, I ended up getting a fancier motherboard, but I had a lot more GPUs.)
2) Run the stand alone Octane and see if that gives you the same problems as the plugin Octane in C4D.
3) Run Windows Memory Diagnostic Tool just to check that your RAM is working okay.
4) If there's any way you could remove your GPUs and try others, that would be a good test. Borrow a GPU from a friend? Buy a cheap 970 used.
5) Are your GPUs getting enough power, is PSU big enough?
6) Install free Blender and render with GPU using Cycles. See if you get similar problems. In my case, Octane could blue screen crash my whole system, and Blender Cycles would GPU render fine. I think Octane uses the GPUs a lot harder than Cycles. In my experience, Octane can push GPUs to crashing Windows when nothing else will GPU crash on the same setup. But it could be a useful test.
7) Can you run your GPUs hard with something else, like a game, and see if you get similar results.
8) Physically remove one of your GPUs and try rendering just with one of them. Maybe your motherboard doesn't like two GPUs for Octane.
9) Trying GPUs in different slots could be useful. Read your motherboard manual for suggestions. My old MSI motherboard just wouldn't boot if it didn't like where the GPUs were.
10) For your rebooting problem, if it won't post, push the BIOS reset button on the motherboard. Sometimes I still couldn't reboot and I had to remove the GPUs, try to boot, put GPUs back in, boot, and then it would start up. I had to reset the BIOS every time I tried different slot configuration.
11) Keep detailed handwritten notes. One time I got everything working and wasn't sure why. But looking back through my detailed notes, I could see what I did that worked.
12) If you think the power is bad out of the wall, but it on a UPS, which will clean and stabilize the power a bit. Or take the whole rig to someone else's house and plug it in there. This sounds unlikely though.
13) If your GPUs are getting that hot, take off the cover and run it open air, maybe with a household box fan next to it, just to see if you can run with lower temperatures and see if that helps. See if your crashes take place only when temperatures rise. When you first start running on cool cards, does it crash then? Yours are certainly hotter than my open air 980 TI's are.
14) Check priority for all cards in Octane Settings, just to be sure it's on for the card you're using for monitors.
My crashes happened right away, bluescreen out of windows by just starting Octane. In my situation I just had too many GPUs on a motherboard that didn't like it, so I got an Asus E WS that works better. With yours, how it works for a bit and then goes bad, maybe its a bad piece of hardware somewhere, I don't know.
In the end, I built two duplicate computers. Now, if anything ever goes bad like this in the middle of a project, I won't have to stop working to do weeks of diagnostics.
Best of luck, let us know if you figure it out.
M
1) Try an older version of Octane, I've had luck with this. Uninstall both the plugin and stand alone, and install both from an older build. The first 3.0 worked better for me than the next two did, when I was getting crashes. (In my case, I ended up getting a fancier motherboard, but I had a lot more GPUs.)
2) Run the stand alone Octane and see if that gives you the same problems as the plugin Octane in C4D.
3) Run Windows Memory Diagnostic Tool just to check that your RAM is working okay.
4) If there's any way you could remove your GPUs and try others, that would be a good test. Borrow a GPU from a friend? Buy a cheap 970 used.
5) Are your GPUs getting enough power, is PSU big enough?
6) Install free Blender and render with GPU using Cycles. See if you get similar problems. In my case, Octane could blue screen crash my whole system, and Blender Cycles would GPU render fine. I think Octane uses the GPUs a lot harder than Cycles. In my experience, Octane can push GPUs to crashing Windows when nothing else will GPU crash on the same setup. But it could be a useful test.
7) Can you run your GPUs hard with something else, like a game, and see if you get similar results.
8) Physically remove one of your GPUs and try rendering just with one of them. Maybe your motherboard doesn't like two GPUs for Octane.
9) Trying GPUs in different slots could be useful. Read your motherboard manual for suggestions. My old MSI motherboard just wouldn't boot if it didn't like where the GPUs were.
10) For your rebooting problem, if it won't post, push the BIOS reset button on the motherboard. Sometimes I still couldn't reboot and I had to remove the GPUs, try to boot, put GPUs back in, boot, and then it would start up. I had to reset the BIOS every time I tried different slot configuration.
11) Keep detailed handwritten notes. One time I got everything working and wasn't sure why. But looking back through my detailed notes, I could see what I did that worked.
12) If you think the power is bad out of the wall, but it on a UPS, which will clean and stabilize the power a bit. Or take the whole rig to someone else's house and plug it in there. This sounds unlikely though.
13) If your GPUs are getting that hot, take off the cover and run it open air, maybe with a household box fan next to it, just to see if you can run with lower temperatures and see if that helps. See if your crashes take place only when temperatures rise. When you first start running on cool cards, does it crash then? Yours are certainly hotter than my open air 980 TI's are.
14) Check priority for all cards in Octane Settings, just to be sure it's on for the card you're using for monitors.
My crashes happened right away, bluescreen out of windows by just starting Octane. In my situation I just had too many GPUs on a motherboard that didn't like it, so I got an Asus E WS that works better. With yours, how it works for a bit and then goes bad, maybe its a bad piece of hardware somewhere, I don't know.
In the end, I built two duplicate computers. Now, if anything ever goes bad like this in the middle of a project, I won't have to stop working to do weeks of diagnostics.
Best of luck, let us know if you figure it out.
M