I have been hammering away at solving this and I can't fix it.
Running the latest stable build, As soon as I enable path tracing Octane will start pushing my GFX cards and kill the system. Screens go black and the fans go into overdrive.
This happens in 2023 or r26.
Every other render engine (Arnold and Redshift) works fine. It's just octane
Last log file attached.
System:
Threadripper 3070
128GB RAM
Dual rtx 3090
Octane crashing my computer
Moderators: ChrisHekman, aoktar
- Attachments
-
- c4doctanelog.txt
- (112.7 KiB) Downloaded 63 times
Hi,
please perform a clean installation of 516.94 Nvidia Studio driver:
https://www.nvidia.com/download/driverR ... 969/en-us/
To perform a clean installation, please follow these steps:

Then please, after reboot, download and run OctaneBench 2020.1, and share a complete screenshot of the result, thanks:
https://render.otoy.com/downloads/a/61/ ... _5_win.zip
ciao,
Beppe
please perform a clean installation of 516.94 Nvidia Studio driver:
https://www.nvidia.com/download/driverR ... 969/en-us/
To perform a clean installation, please follow these steps:

Then please, after reboot, download and run OctaneBench 2020.1, and share a complete screenshot of the result, thanks:
https://render.otoy.com/downloads/a/61/ ... _5_win.zip
ciao,
Beppe
I would agree, it as I stated octane is the only rendering engine that is causing this. I have tried it with Arnold as well as Redshift and Cycles and none of them have this issue. I can even push large scenes through Clarisse and I have no problems.
If also OctaneBench is crashing, the system seems not quite stable to me
Ok, please try to go to Nvidia Control panel, menu Help, and enable the Debug mode, to work with GPUs at default clock, and run again OctaneBench:

ciao,
Beppe
Ok, please try to go to Nvidia Control panel, menu Help, and enable the Debug mode, to work with GPUs at default clock, and run again OctaneBench:

ciao,
Beppe
I have checked every component and reseated all cables. I have also unplugged one of my graphics cards to remove power draw on the system, but the issue persists. I have also tried using the Octane version of Blender and it works without crashing. C4d and Octanebench still crash.elsksa wrote:A crash often relates to a hardware failure. It would be suggested to look at hardware level (motherboard & PSU connections, properly powered components, etc).
I have a similar setup here running without issues: Ryzen 5950x, 128GB RAM, 4090 + 3090 (previously dual 3090s), AX1600i PSU
I don't use C4D. I use Standalone and Modo, but can confirm Octanebench runs without problems too. Here's a couple of things to check while troubleshooting:
1. Make sure you have 1 PCIe power cable per 8-pin connection on the card.
eg. If your 2 cards have 3x8-pins each, then you'll need 6 separate PCIe cables.
2. If you are using any of the dual pigtail cables, don't connect the second pigtail.
Technically, connecting a pigtail cable to 2 card connections might work fine on this PSU, but avoid it for now just to be sure.
This PSU can be controlled by Corsair iCUE and has some settings to try/check:
3. Go to iCUE > ax1600i > device settings. Make sure each cable is set to 40A/40% (the default).
NOTE: I'm using iCUE v4.23.137 because I noticed a bug in newer builds which can set the PSU OCP amperage to the lowest setting (20A/20%).
4. You can also try running the PSU in Single Rail mode. iCUE > ax1600i > device settings > Single OCP. This should not be needed though.
I don't use C4D. I use Standalone and Modo, but can confirm Octanebench runs without problems too. Here's a couple of things to check while troubleshooting:
1. Make sure you have 1 PCIe power cable per 8-pin connection on the card.
eg. If your 2 cards have 3x8-pins each, then you'll need 6 separate PCIe cables.
2. If you are using any of the dual pigtail cables, don't connect the second pigtail.
Technically, connecting a pigtail cable to 2 card connections might work fine on this PSU, but avoid it for now just to be sure.
This PSU can be controlled by Corsair iCUE and has some settings to try/check:
3. Go to iCUE > ax1600i > device settings. Make sure each cable is set to 40A/40% (the default).
NOTE: I'm using iCUE v4.23.137 because I noticed a bug in newer builds which can set the PSU OCP amperage to the lowest setting (20A/20%).
4. You can also try running the PSU in Single Rail mode. iCUE > ax1600i > device settings > Single OCP. This should not be needed though.
Win10 Pro / Ryzen 5950X / 128GB / RTX 4090 / MODO
"I am the resurrection, and the life: he that believeth in me, though he were dead, yet shall he live" - Jesus Christ
"I am the resurrection, and the life: he that believeth in me, though he were dead, yet shall he live" - Jesus Christ
Thanks, I'll try those.funk wrote:I have a similar setup here running without issues: Ryzen 5950x, 128GB RAM, 4090 + 3090 (previously dual 3090s), AX1600i PSU
I don't use C4D. I use Standalone and Modo, but can confirm Octanebench runs without problems too. Here's a couple of things to check while troubleshooting:
1. Make sure you have 1 PCIe power cable per 8-pin connection on the card.
eg. If your 2 cards have 3x8-pins each, then you'll need 6 separate PCIe cables.
2. If you are using any of the dual pigtail cables, don't connect the second pigtail.
Technically, connecting a pigtail cable to 2 card connections might work fine on this PSU, but avoid it for now just to be sure.
This PSU can be controlled by Corsair iCUE and has some settings to try/check:
3. Go to iCUE > ax1600i > device settings. Make sure each cable is set to 40A/40% (the default).
NOTE: I'm using iCUE v4.23.137 because I noticed a bug in newer builds which can set the PSU OCP amperage to the lowest setting (20A/20%).
4. You can also try running the PSU in Single Rail mode. iCUE > ax1600i > device settings > Single OCP. This should not be needed though.
I am going a little crazy because I can't get any work done. I'm trying to use Arnold but it's not my normal workflow and I can't get near the same look I'm used to.
This all started after I tried rendering C4D Pyro elements in Octane. I know it makes no sense but that was when the issue first appeared.

