Hardcore crashes with max 2026 with this version, I can't even reboot the normal way, I have to cut off the power... no issue with max 2024
It happens randomly, with old or completely new scenes, while I change a value, a texture, or open the octane viewport.
I got recent Nvidia studio drivers (less than two month)
OctaneRender® for 3ds max® v2025.5 - 16.11
Forum rules
Any bugs related to this plugin should be reported to the Bug Reports sub-forum.
Bugs related to Octane itself should be posted into the Standalone Support sub-forum.
Any bugs related to this plugin should be reported to the Bug Reports sub-forum.
Bugs related to Octane itself should be posted into the Standalone Support sub-forum.
AMD 9950x3D / RTX 4090 / RTX 3090 / 192 Go DDR5 / Win 11
http://www.remy-kerbiquet.com
http://www.remy-kerbiquet.com
This problem hasn’t been resolved for years:
VRAM / CPU RAM issue
When VRAM is fully utilized and the system starts using CPU RAM, the slave machines always crash. They never render and consistently report “not enough VRAM.” Why don’t they use CPU RAM the same way the master GPUs do?
We have out-of-core rendering enabled with 16 GB per slave. The master machine, with 3 GPUs, renders correctly using CPU RAM.
Other issues:
1. Slow rendering when iToo is present
There is still a bug related to iToo. If an iToo reference mesh has motion blur enabled (accidentally) and a camera is animated, stationary iToo objects appear as if they are moving at high speed. (image attached)
2. Frequent crashes
There are also many crashes. Rendering may work briefly, but once it stops and you attempt to open the Octane viewport, 3ds Max closes.
It appears that with the current driver or Octane update, if you open the Octane viewport, close it, and then start a full render, 3ds Max immediately crashes.
We are currently using 3ds Max 2023.
The newest studio driver 591.44 this error Application: 3dsmax.exe
Error: Access violation - code c0000005 (first/second chance not available)
Crashed Module Name: nvcuda64.dll
Exception Address: 0x00007ffbe34aa81d
Exception Code: c0000005
Error 2
Error: Access violation - code c0000005 (first/second chance not available)
Crashed Module Name: octane.dll
Exception Address: 0x00007ffb3009d1e7
Exception Code: c0000005
VRAM / CPU RAM issue
When VRAM is fully utilized and the system starts using CPU RAM, the slave machines always crash. They never render and consistently report “not enough VRAM.” Why don’t they use CPU RAM the same way the master GPUs do?
We have out-of-core rendering enabled with 16 GB per slave. The master machine, with 3 GPUs, renders correctly using CPU RAM.
Other issues:
1. Slow rendering when iToo is present
There is still a bug related to iToo. If an iToo reference mesh has motion blur enabled (accidentally) and a camera is animated, stationary iToo objects appear as if they are moving at high speed. (image attached)
2. Frequent crashes
There are also many crashes. Rendering may work briefly, but once it stops and you attempt to open the Octane viewport, 3ds Max closes.
It appears that with the current driver or Octane update, if you open the Octane viewport, close it, and then start a full render, 3ds Max immediately crashes.
We are currently using 3ds Max 2023.
The newest studio driver 591.44 this error Application: 3dsmax.exe
Error: Access violation - code c0000005 (first/second chance not available)
Crashed Module Name: nvcuda64.dll
Exception Address: 0x00007ffbe34aa81d
Exception Code: c0000005
Error 2
Error: Access violation - code c0000005 (first/second chance not available)
Crashed Module Name: octane.dll
Exception Address: 0x00007ffb3009d1e7
Exception Code: c0000005
- Attachments
-
-
Last edited by coilbook on Mon Dec 08, 2025 5:40 am, edited 3 times in total.
There is a massive slowdown and lots of errors with NVIDIA's latest drivers 591.44
The most stable driver is 581.29
Render times go from 27 seconds to 1 min 30 sec. In octane viewport smp/px increase very, very slowly when using the latest drivers.
Not sure how nvidia ruins it all with their newest drivers. They fix one thing and break another. Please report it.
The most stable driver is 581.29
Render times go from 27 seconds to 1 min 30 sec. In octane viewport smp/px increase very, very slowly when using the latest drivers.
Not sure how nvidia ruins it all with their newest drivers. They fix one thing and break another. Please report it.