Display driver has stopped working and has recovered

Sub forum for bug reports
Forum rules
Before posting a bug report, please check the following:
1. That the issue has not already been disclosed
2. That the issue is specific to this plugin, and not Octane in general (Try reproducing it in Standalone)
Bugs related to the Octane Engine itself should be posted into the Standalone Support sub-forum.


All bug reports should include the information below, along with a detailed description of the issue and steps to reproduce it.
A. Operating System, including version (i.e. Win 7, OSX 10.11.2, Ubuntu 14.04, etc.)
B. Graphics Card(s) model (i.e. GTX 580 - 3GB, TITAN, etc.)
C. RAM Capacity (i.e. 6 GB)
D. Nvidia driver version (i.e. 7.50, 7.5.22)
E. OctaneRender Standalone version, if installed (i.e. 2.24.2, 2.23, etc.)
F. OctaneRender plugin version (i.e. v2.25 - 2.21)
G. Host application version, including build number if available (i.e. 3ds Max 2016 Build 18.0)
Post Reply
Rik
Licensed Customer
Posts: 423
Joined: Wed Jul 28, 2010 8:57 pm

Try to open the octane viewport and the system hangs after a few seconds, graphics driver reboots with the message "Display driver stopped responding and has recovered" and Nvidia error code3

Have made changes to the TDR delay level but makes no difference.
Changed cards (gtx570 2.5gb and gtx580 3gb) active and priority settings but makes no difference.
tried clay mode, still crashes
not a Vram issue

In desperation, started new scene, put in a teapot with displacement material on and it still crashed
Repeated this process and it worked.
Loaded up initial scene and crashed again. This seems like a bit of a random bug but I think it may be something to do with displacement?

Apologies if this has already been covered but I cant find a solution for this anywhere on the web.

Think it may be something to do with displacement.

Using max 2014 with octane plugin 2.13 and driver 344.75

Any ideas? Currently running out of excuses to stall my customer and they're getting pretty pissed off.
coilbook
Licensed Customer
Posts: 3032
Joined: Mon Mar 24, 2014 2:27 pm

Maybe a bug I am still using 2.11a and nvidia 344.11 waiting for more polished updates from otoy and nvidia to be on a safe side
Rik
Licensed Customer
Posts: 423
Joined: Wed Jul 28, 2010 8:57 pm

May have to do the same if the Otoy crew don't have an answer.

If they are there, does any of this help to identify the issue?



Started logging on 03.12.14 13:52:25

OctaneRender version 2.13 (2130000)

CUDA error 999 on device 0: An unknown internal error occurred.
-> kernel execution failed (dl)
device 0: direct lighting failed





Started logging on 03.12.14 13:52:25

OctaneRender version 2.13 (2130000)

CUDA error 999 on device 0: An unknown internal error occurred.
-> kernel execution failed (dl)
device 0: direct lighting failed
CUDA error 999 on device 0: An unknown internal error occurred.
-> failed to clear linear 2D device memory
CUDA error 999 on device 0: An unknown internal error occurred.
-> failed to clear linear 2D device memory
CUDA error 999 on device 0: An unknown internal error occurred.
-> failed to load symbol data to the device (kernel data)
device 0: path tracing failed
CUDA error 999 on device 0: An unknown internal error occurred.
-> failed to deallocate device memory
CUDA error 999 on device 0: An unknown internal error occurred.
-> could not get memory info
device 0: failed to upload data texture 4 of context 0
CUDA error 999 on device 0: An unknown internal error occurred.
-> failed to deallocate device memory
CUDA error 999 on device 0: An unknown internal error occurred.
-> could not get memory info
CUDA error 999 on device 0: An unknown internal error occurred.
-> failed to deallocate device memory
CUDA error 999 on device 0: An unknown internal error occurred.
-> could not get memory info
CUDA error 999 on device 0: An unknown internal error occurred.
-> failed to deallocate device memory
CUDA error 999 on device 0: An unknown internal error occurred.
-> could not get memory info
CUDA error 999 on device 0: An unknown internal error occurred.
-> failed to deallocate device memory
CUDA error 999 on device 0: An unknown internal error occurred.
-> could not get memory info
CUDA error 999 on device 0: An unknown internal error occurred.
-> failed to deallocate device memory
CUDA error 999 on device 0: An unknown internal error occurred.
-> could not get memory info
CUDA error 999 on device 0: An unknown internal error occurred.
-> failed to deallocate device memory
CUDA error 999 on device 0: An unknown internal error occurred.
-> could not get memory info
CUDA error 999 on device 0: An unknown internal error occurred.
-> failed to deallocate device memory
CUDA error 999 on device 0: An unknown internal error occurred.
-> could not get memory info
CUDA error 999 on device 0: An unknown internal error occurred.
-> failed to deallocate device memory
CUDA error 999 on device 0: An unknown internal error occurred.
-> could not get memory info
CUDA error 999 on device 0: An unknown internal error occurred.
-> failed to deallocate device memory
CUDA error 999 on device 0: An unknown internal error occurred.
-> could not get memory info
CUDA error 999 on device 0: An unknown internal error occurred.
-> failed to deallocate device memory
CUDA error 999 on device 0: An unknown internal error occurred.
-> could not get memory info
CUDA error 999 on device 0: An unknown internal error occurred.
-> failed to deallocate device memory
CUDA error 999 on device 0: An unknown internal error occurred.
-> could not get memory info
CUDA error 999 on device 0: An unknown internal error occurred.
-> failed to deallocate device memory
CUDA error 999 on device 0: An unknown internal error occurred.
-> could not get memory info
CUDA error 999 on device 0: An unknown internal error occurred.
-> failed to deallocate device memory
CUDA error 999 on device 0: An unknown internal error occurred.
-> could not get memory info
CUDA error 999 on device 0: An unknown internal error occurred.
-> failed to deallocate device memory
CUDA error 999 on device 0: An unknown internal error occurred.
-> could not get memory info
CUDA error 999 on device 0: An unknown internal error occurred.
-> failed to deallocate device memory
CUDA error 999 on device 0: An unknown internal error occurred.
-> could not get memory info
CUDA error 999 on device 0: An unknown internal error occurred.
-> failed to deallocate device memory
CUDA error 999 on device 0: An unknown internal error occurred.
-> could not get memory info
CUDA error 999 on device 0: An unknown internal error occurred.
-> failed to deallocate device memory
CUDA error 999 on device 0: An unknown internal error occurred.
-> could not get memory info
CUDA error 999 on device 0: An unknown internal error occurred.
-> failed to deallocate device memory
CUDA error 999 on device 0: An unknown internal error occurred.
-> could not get memory info
CUDA error 999 on device 0: An unknown internal error occurred.
-> failed to deallocate device array
CUDA error 999 on device 0: An unknown internal error occurred.
-> could not get memory info
CUDA error 999 on device 0: An unknown internal error occurred.
-> failed to deallocate device array
CUDA error 999 on device 0: An unknown internal error occurred.
-> could not get memory info
CUDA error 999 on device 0: An unknown internal error occurred.
-> failed to deallocate device array
CUDA error 999 on device 0: An unknown internal error occurred.
-> could not get memory info
CUDA error 999 on device 0: An unknown internal error occurred.
-> failed to deallocate device memory
CUDA error 999 on device 0: An unknown internal error occurred.
-> could not get memory info
CUDA error 999 on device 0: An unknown internal error occurred.
-> failed to deallocate device array
CUDA error 999 on device 0: An unknown internal error occurred.
-> could not get memory info
CUDA error 999 on device 0: An unknown internal error occurred.
-> failed to deallocate device array
CUDA error 999 on device 0: An unknown internal error occurred.
-> could not get memory info
CUDA error 999 on device 0: An unknown internal error occurred.
-> failed to deallocate device array
CUDA error 999 on device 0: An unknown internal error occurred.
-> could not get memory info
CUDA error 999 on device 0: An unknown internal error occurred.
-> failed to deallocate device array
CUDA error 999 on device 0: An unknown internal error occurred.
-> could not get memory info
CUDA error 999 on device 0: An unknown internal error occurred.
-> failed to deallocate device array
CUDA error 999 on device 0: An unknown internal error occurred.
-> could not get memory info
CUDA error 999 on device 0: An unknown internal error occurred.
-> failed to deallocate device array
CUDA error 999 on device 0: An unknown internal error occurred.
-> could not get memory info
CUDA error 999 on device 0: An unknown internal error occurred.
-> failed to deallocate device array
CUDA error 999 on device 0: An unknown internal error occurred.
-> could not get memory info
CUDA error 999 on device 0: An unknown internal error occurred.
-> failed to deallocate device array
CUDA error 999 on device 0: An unknown internal error occurred.
-> could not get memory info
CUDA error 999 on device 0: An unknown internal error occurred.
-> failed to deallocate device memory
CUDA error 999 on device 0: An unknown internal error occurred.
-> could not get memory info
CUDA error 999 on device 0: An unknown internal error occurred.
-> failed to deallocate device memory
CUDA error 999 on device 0: An unknown internal error occurred.
-> could not get memory info
CUDA error 999 on device 0: An unknown internal error occurred.
-> failed to deallocate device memory
CUDA error 999 on device 0: An unknown internal error occurred.
-> could not get memory info
CUDA error 999 on device 0: An unknown internal error occurred.
-> failed to deallocate device memory
CUDA error 999 on device 0: An unknown internal error occurred.
-> could not get memory info
CUDA error 999 on device 0: An unknown internal error occurred.
-> failed to unload module
CUDA error 999 on device 0: An unknown internal error occurred.
-> failed to bind device to current thread
device 0: failed to initialize resources
CUDA error 999 on device 0: An unknown internal error occurred.
-> failed to bind device to current thread
device 0: failed to initialize resources




CUDA error 999 on device 0: An unknown internal error occurred.
-> failed to allocated device memory
device 0: failed to upload data texture 4 of context 0



CUDA error 999 on device 0: An unknown internal error occurred.
-> failed to bind device to current thread
device 0: failed to initialize resources
coilbook
Licensed Customer
Posts: 3032
Joined: Mon Mar 24, 2014 2:27 pm

i noticed the reason i quit getting cuda errors during animation render is the image clears up a lot quicker in 2.1x version so instead of 4000 samples i only need 2000 samples to get the same results. But if i have to render at 4000 samples i still get 999 and 700 cuda errors no matter how cool i keep my cards, how good are psus. Video cards or this program just cannot handle and freezes after 100 frames
Rik
Licensed Customer
Posts: 423
Joined: Wed Jul 28, 2010 8:57 pm

think I'm slowly narrowing it down to some bits of corrupt geometry or maps or both.

though I bet it ends up being neither and I end up sending the client a painting :(
Rik
Licensed Customer
Posts: 423
Joined: Wed Jul 28, 2010 8:57 pm

It would appear to be displacement causing the display driver to crash...

Tried all versions of octane 2.xxxx
also changed the nvidia driver from the very latest .75 back to 344.11

It's a small model (a house) and when i change the viewpoint in the octane viewport there is no crash - until I turn put displacement on.

Am I the only one still having problems with displacement?
User avatar
Karba
OctaneRender Team
Posts: 2300
Joined: Sat Jun 11, 2011 9:05 am

Rik wrote:It would appear to be displacement causing the display driver to crash...

Tried all versions of octane 2.xxxx
also changed the nvidia driver from the very latest .75 back to 344.11

It's a small model (a house) and when i change the viewpoint in the octane viewport there is no crash - until I turn put displacement on.

Am I the only one still having problems with displacement?
We have a scene with reproducible issue. I will fix it as soon as I can.
Rik
Licensed Customer
Posts: 423
Joined: Wed Jul 28, 2010 8:57 pm

Thanks Karba

Good to know.
Post Reply

Return to “Bug Reports”