According to your signature you are working on Windows 7. For that please install a driver of version 387 or higher. For example, I'm running 391.35 without issues on my Win 7 system, but 388.71 works as well.treddie wrote:3.08 does not accept my Titan X. It gives me the error message,
"CUDA driver must be at least of version 9.10. CUDA initialization failed. Please make sure you have a recent enough NVIDIA driver."
Octane says my CUDA driver version is 7.50.
My Titan X driver is 10.18.13.5330, if that is the same as the "CUDA" driver.
UPDATE: Just great, now my 3.07 install doesn't recognize my Titan X. I'm dead in the water. Looks like the 3.08 install messed things up.
OctaneRender™ Standalone 3.08
In theory there is no difference between theory and practice. In practice there is. - Yogi Berra
Is this the game ready driver you are referring to? Otherwise, device manager only refers to a much lower number...like 10.xx. At any rate, I tried updating the game ready driver to 391 and my system went down. Spent an hour getting it rolled back. The NVidia Control Panel is also toast; crashes now when attempting to launch it.
Win7 | Geforce TitanX w/ 12Gb | Geforce GTX-560 w/ 2Gb | 6-Core 3.5GHz | 32Gb | Cinema4D w RipTide Importer and OctaneExporter Plugs.
Sorry that you have so much trouble. I was talking about this driver (391.35 on Windows 7 / 8 / 8.1): http://www.nvidia.com/download/driverRe ... 2838/en-ustreddie wrote:Is this the game ready driver you are referring to? Otherwise, device manager only refers to a much lower number...like 10.xx. At any rate, I tried updating the game ready driver to 391 and my system went down. Spent an hour getting it rolled back.
Alternatively you could try this one (388.71 on Windows 7 / 8 / 8.1): http://www.nvidia.com/download/driverRe ... 8419/en-us
If you have problems installing the driver: Maybe try a clean install (via Custom Install -> tick "Clean install"), which will remove any previous NVIDIA driver before it installs the new one. If none of that works, please contact the support and they will have a more in-depth look of what's going on on your system.
In theory there is no difference between theory and practice. In practice there is. - Yogi Berra
After about an hour, I got my system back with the 388 driver and clean install. So thought I would give 391 a try again, using clean install. My system went completely down. Took about 5 hours to get it back up with the 388 driver so that my system could even SEE the Titan X. However, the original problem still persists...Octane Standalone 3.07 and 3.08 do not see any GPUs. 3.07 used to work fine. Now, only Octane 3.04 sees my GPUs.
Win7 | Geforce TitanX w/ 12Gb | Geforce GTX-560 w/ 2Gb | 6-Core 3.5GHz | 32Gb | Cinema4D w RipTide Importer and OctaneExporter Plugs.
Hi Beppe.
I used that thread to solve the digital signature issue about a month ago and finally got that to work. Now the problem is completely different...Octane 3.07 (which used to work just fine), can no longer detect my GPUs. 3.08 never did. The 3.08 install is what caused all of this. So I uninstalled both 3.07 and 3.08, and then reinstalled 3.07, but no go.
I have to get to bed. Been struggling with this headache for 6 hours now.
I used that thread to solve the digital signature issue about a month ago and finally got that to work. Now the problem is completely different...Octane 3.07 (which used to work just fine), can no longer detect my GPUs. 3.08 never did. The 3.08 install is what caused all of this. So I uninstalled both 3.07 and 3.08, and then reinstalled 3.07, but no go.
I have to get to bed. Been struggling with this headache for 6 hours now.
Win7 | Geforce TitanX w/ 12Gb | Geforce GTX-560 w/ 2Gb | 6-Core 3.5GHz | 32Gb | Cinema4D w RipTide Importer and OctaneExporter Plugs.
Hi,
Hope I can help a bit.
My system is different and by updating from cuda drivers 9.0 (nvidia drivers < 387.92) to cuda 9.10, my system cannot install some of my GPU.
My issue is due to vbios modified on some GPUs. Revert back to original Vbios make all GPU work with cuda 9.1 drivers.
In my investigation, with many drivers tests, I found that some clean install don't have cuda installed !
Test with clean install of 391.35 --> no GPU on octane render (but ok for game and all ok in device manager.
I noticed that also for 391.24.
So I test the 387.92 (the first one with cuda 9.10), and that works. And I think from there, you can update to new drivers (without a clean install).
To do a clean install, you should use DDU.
For me, as Octane 3.08 works with 387.92, I'm still with it, until the next mandatory drivers.
Hope I can help a bit.
My system is different and by updating from cuda drivers 9.0 (nvidia drivers < 387.92) to cuda 9.10, my system cannot install some of my GPU.
My issue is due to vbios modified on some GPUs. Revert back to original Vbios make all GPU work with cuda 9.1 drivers.
In my investigation, with many drivers tests, I found that some clean install don't have cuda installed !
Test with clean install of 391.35 --> no GPU on octane render (but ok for game and all ok in device manager.
I noticed that also for 391.24.
So I test the 387.92 (the first one with cuda 9.10), and that works. And I think from there, you can update to new drivers (without a clean install).
To do a clean install, you should use DDU.
For me, as Octane 3.08 works with 387.92, I'm still with it, until the next mandatory drivers.
I7-3930K 64Go RAM Win8.1pro , main 3 titans + 780Ti
Xeon 2696V3 64Go RAM Win8.1/win10/win7, 2x 1080Ti + 3x 980Ti + 2x Titan Black
Xeon 2696V3 64Go RAM Win8.1/win10/win7, 2x 1080Ti + 3x 980Ti + 2x Titan Black
+10!!!itou31 wrote:To do a clean install, you should use DDU.

NOTE: I'm sorry for bad english due to mute 
i7-12700KF
2x16GB RAM@DDR4-3600
MSI PRO Z690-A DDR4
Zotac GF RTX 4090 <3
SSDs OCZ RD400 0.5TB and Crucial 2TB SATA3
HDD 1TB SATA2
LG BD-RE BH16NS40
PSU 1kW
CRT 19" Samtron 19"

i7-12700KF
2x16GB RAM@DDR4-3600
MSI PRO Z690-A DDR4
Zotac GF RTX 4090 <3

SSDs OCZ RD400 0.5TB and Crucial 2TB SATA3
HDD 1TB SATA2
LG BD-RE BH16NS40
PSU 1kW
CRT 19" Samtron 19"

Thanks, itou31. I made sure that I was back to my default settings in the BIOS, like you suggested and that may have helped, but the graphic below shows what I have to go through whenever a display driver crashes. This has happened in the past and I could never figure out what I did to get it going again, but this time I figured it out. If I do not follow this procedure, anything can happen, like my Titan X showing up as my GTX 560 in Device Manager, or simply not even being recognized at all by Windows as even existing! All told, down 10 hours overall. But FINALLY, Octane 3.07-.08 see my GPUs now.Hi,
Hope I can help a bit.
My system is different and by updating from cuda drivers 9.0 (nvidia drivers < 387.92) to cuda 9.10, my system cannot install some of my GPU.
My issue is due to vbios modified on some GPUs. Revert back to original Vbios make all GPU work with cuda 9.1 drivers.
In my investigation, with many drivers tests, I found that some clean install don't have cuda installed !
Test with clean install of 391.35 --> no GPU on octane render (but ok for game and all ok in device manager.
I noticed that also for 391.24.
So I test the 387.92 (the first one with cuda 9.10), and that works. And I think from there, you can update to new drivers (without a clean install).
To do a clean install, you should use DDU.
For me, as Octane 3.08 works with 387.92, I'm still with it, until the next mandatory drivers.
Everyone strongly suggests DDU, so I will have to try that next time, too!
You do not have the required permissions to view the files attached to this post.
Win7 | Geforce TitanX w/ 12Gb | Geforce GTX-560 w/ 2Gb | 6-Core 3.5GHz | 32Gb | Cinema4D w RipTide Importer and OctaneExporter Plugs.
as said on the lightwave thread, the offline licencing is no more active for this new production build : any chance to see it again ?
because it is a pain to have to connect (& wait) each time i want to use Octane/LW : for all like me who want to keep their workstation out of the net as most as possible, it is not a good thing...
i understand a regular online check is possible (like adobe do with their sofware suit, one time each month), but each new session
...
thanks
because it is a pain to have to connect (& wait) each time i want to use Octane/LW : for all like me who want to keep their workstation out of the net as most as possible, it is not a good thing...
i understand a regular online check is possible (like adobe do with their sofware suit, one time each month), but each new session

thanks