Volume rendering causes application crash

Operating system:Windows 10
Slicer version:4.9.0 2018-08-01
Expected behavior:Volume rendering ability
Actual behavior:TDR error code 7

Hi everyone,

I have a series of a larynx micro CT. Format nifti, size approx. 180 MB. I loaded it and want to check in Volume rendering. It starts normaly and after the first movements an error code appears: TDR error code 7 the application must close.
I have an NVIDIA Quadro 1000M graphic card with 2048 MB GDDR5 memory.
In the Volume rendering module I choose GPU rendering, I select 2 GB memory size and it always crashes.
What could be the solution?



Your video card is too slow for rendering this large data set. The operating system interprets the slow response as the video card driver is crashed and it resets the card and shuts down the application. You have to reduce data set size by cropping or resampling in Slicer, or increase TDR delay in your operating system.

Dear Andras,

Thanks for the information. I changed the TDR settings in registry keys and gave a value of 8. After that the system shut down. I selected the multivolume rendering option and that helped.

Multi-volume is currently faster because it does not use shading yet, but therefore the image quality is lower.

Increasing TDR delay fixes issues that you described above. If it did not help then I would recommend to try it again. It is somewhat tricky to set this registry value, because if you temporarily set it to 0 (e.g., you create the registry key but not set the value yet) then it shuts down your system, as TDR delay = 0 causes immediate TDR timeouts everywhere.

From a user’s perspective it might be worthwhile to emphasize on the download page that the GPU H/W requirements of the current nightly series is much higher than the stable. The change in volume rendering performance is so drastic that, an occasional user coming from 4.8.1 (and not following the discussions on discourse) would think it is a serious regression or a bug.

There should be a problem with my system. After I made a search how to change the TDR value for the Win10, I made the changes. At my first attempts a month ago, after the value was set to 8 the system reacted with a message that I have no GPU card. It might be that I not remember correctly, since it was an older nightly build version of the Slicer (downladed at 07.12.). I can’t recall the message now, the value 8 seems working at the moment on this nightly build version (4.9.0. 2018-08-01)


Do you mean that we should warn users that a more recent OpenGL API version is needed?

I could provoce the problem again. Sorry if I don’t translate it correctly, the message was:
“It is not allowed for the Slicer to use the graphic hardware”
For Andras:
Az alkalmazás számára nem engedélyezett a grafikus hardver elérése.
This happened after I changed the TDR value to 8

This error has been reported to happen for resource-intensive applications, such as games, and seems to be caused by faulty graphics driver operating system configuration.

Based on my experience, NVidia Quadro users often run into strange driver/compatibility issues. Quadro GPUs are tested very thoroughly for a small set of applications (certain CAD software, etc.) but probably not much for anything else. If you only use NVidia Quadro certified applications then go with a Quadro, otherwise I would recommend to use GeForce GPUs instead - it is less expensive and more robust.