Octane crash with GTX260-Xt OC (solved with underclocking)

[fury_jin]

Hello!

Here my config: Q9400 2.8Ghz - 8Go DDR2 - GTX 260-XT OC - Fortron 700W
FRESH XP SP3 32bit installation
cuda 3.0 driver and octane demo (that's all, nothing more)
When i run Octane demo, it totally crash my PC after 1 or 2 minutes, and i have to power off manually...

I can play crysis, SC², Bioshock, portal, TRA, during many hours without a single crash...
Also with the game Mirror Edge we can turn on PhysX, and when i do that, my PC crash very fast, and i have to press 5s the power switch... When i disable this, it's ok.

Question:
-Is it possible to have a GC issue only with the CUDA system?

In your installation video for windows, i don't understand why you say to update the nvidia classic driver?
Because in my first test, i install the last classic nvidia driver, and then the cuda 3.0 driver informed me that the classic driver was more recent than the cuda 3.0

Question:
-The classic driver have the cuda 3.01 inside, so why do we have to install it twice?


I do one more test, i make a fresh installation with ubuntu 9.10 64 bit, install the nvidia driver from ubuntu,

install the cuda, and when i run Octane demo my PC crash after 1 or 2 minutes...(again)

I really want to buy it, but i have to solve that issue.

Any ideas?

[pixelrush]

Hi,
I think the instructions are a bit misleading. For Windows you only need the Nvidia driver not the Toolkit as well. As you say the Nvidia driver comes with Cuda. For the Demo version you need only make sure the driver you use is Cuda 3.0 Any driver of the 197.xx series is appropriate.

I am not sure what is causing the crashes. It sounds like a Power supply issue but 700W sounds enough. When it crashes are you just allowing it to render or are you doing things in the window like play around with nodes etc? The Demo is pretty alpha state ie it has unfinished code and bugs. It is intended as a technology demonstrator more than anything.
It perhaps doesnt give the best impression but rest assured the current commercial version is working well.
FYI there is a more complete Demo version due soon that ought to run much better.

Try opening one of the Demo suite files available where you downloaded Octane and just let it render.
It should be fine but if it crashes after a while it *might* be the power supply is inadequate.
The use of GPU is pretty intense. I do realise if you use it for games ok then it ought to be ok for Octane too so i'm not sure whats going on there at the moment.
Try just letting it render and let me know.

[fury_jin]

Hi,
I don't play with the node or anything else, i just fly in the 3D view with the sample scenes.
And it crash even if i let it render...

[pixelrush]

I am tempted to say it is the 'windows watchdog' issue at this point although this doesnt explain the Linux crash so I'm thinking its something else..
Never the less when using one card on its own running Octane preoccupies the card and the UI display doesnt get updated properly, in fact Windows times out waiting - the time out period is only about 5 secs - and then things lockup.
To my mind the 260 ought to be powerful enough to run without this issue but...

If this is the issue the cure is to add in a second card just for the UI only and let Octane run exclusively in the 260. If you have another card or can borrow one try that and see if it helps to have a secondary card. Just to exclude that possibility.

Ideally Physx could run in another card from the display as well so it might help to get another card like a 450 to do dual duty as a companion for games and rendering. Sorry I am not really up with the intricacies of gaming stuff so I cant give you a definitive answer about Physx issues but it is also cuda based so...

If it crashes instantly with Physx assuming there isnt some incompatibility with that particular game or you have run out of memory or something I am wondering about a hardware defect?
Recently we had a case here where a 470 wouldnt run with Physx or Cuda at all but appeared normal for graphics. You could try running this program http://mikelab.kiev.ua/index_en.php?pag ... AMS/vmt_en just to confirm cuda runs in vram. The directx test in it is broken but the cuda test ought to work. It does for me. This should confirm the basic integrity of the cuda set up.
If you suspect its the card remove it and just try Octane with your other/borrowed card again to exclude the possibility.
HTH

[fury_jin]

Never the less when using one card on its own running Octane preoccupies the card and the UI display doesnt get updated properly

I think this is not the problem, because when my PC freeze, 30s later i have the blue screen of death (nv4_disp)...

Also, i try octane demo with an other computer ( C2D 2.8Ghz 2Go ram fortron 400W GTS250-oc twintech) and it runs like a charm... the display windows is maybe a little slow but at least i don't have blue screen.

[pixelrush]

I see you mention the 260 is an overclocked version. I hadnt noticed that before even though its in the title.
Its possibly not the issue here but you could use a utility like MSI Afterburner to underclock it some. Sometimes the o/c and/or heat can cause crashes and instability. Octane makes intense use of the GPU - even more so than gaming.
Just another idea....

[Odeas]

I think personally it could be a driver issue (NV4_Disp is drivers). Your PSU is powerful enough to run the card.

Go to your Device Manager, find your card and Right Click > Uninstall.
I'd also recommend uninstalling any Nvidia drivers currently installed - reboot and install fresh drivers.

If that doesn't work as pixelrush suggests open an overclocking tool like afterburner or Rivatuner and keep an eye on temps, if they do get high underclock a little. If this solves set up a profile so that you can have your card running at full for games etc but can easily switch for Octane. (Though if this does solve it I'd also think about better case cooling and giving your fans etc a quick clean)

[fury_jin]

OK i did the right test, i exchange my GTX260-xt-oc with the GTS250-xt-oc, i did a new installation Xp sp3, last classic nvidia driver (260.89_desktop_winxp_32bit_international_whql.exe) And it works fine!

So there is definitly a problem with physX and cuda with my card... Just like the GTX470 you have mentioned earlier.
I this a commercial limitation?
Is it a defect? can i ask for replacement (warranty) ?

I always have speed fan in my taskbar and i check very carfully the temp of my CG, it nerver goes above 80°c! (40°c IDLE 80°c burn)
Also i have an infra red temp checker that confirm this info.
I plug my power checker, and find that octane render use about 200Watt, and with games i am above that (280W)

So this is not the temperature (i clean the few dust there was on it, 2 hours ago)
This is not the CG memory, in this case i will have some issues with games...
And not the drivers...

Since i have it, i always have problem when PhysX, that don't bother me that much because i only have one game that can use it (Mirror edge)

PS(i edit the subject, to give more info)

[fury_jin]

You find the answer pixelrush! it was the overclocking!

(I never OC my CG, it has been done by the constructor)

So i download Ntune:

http://www.nvidia.com/object/ntune_5.05.54.00.html

I decrease the core bus: 600Mhz -> 567Mhz
And the Memory bus: 1050Mhz -> 999Mhz

Octane render see the clock rate: 1269Mhz -> 1113Mhz

Now i can render with my CG

Thx

SO IT WAS JUST A CORE/MEMORY BUS FREQUENCY ISSUE!

[pixelrush]

Ok great solved. happy rendering

btw the stock std settings are 576 ,999 and 1242 mhz
I seem to remember people with a stock 260 even underclocked slightly for stability so what you have set now is probably fine.