Friday, September 1, 2017

nvoglv64.dll crash Maya 2017 - Solution to the problem

If during the rendering by Arnold (using IPR Arnold RenderView) your Maya dies and the screen blinks and you find such an error


 then you need to set for Maya app. in Nvidia Control Panel: 3D Settings\Manage 3D settings:

OpenGL Rendering GPU - << select your card in list >>
Power management mode - Prefer maximum performance
Vertical sync - Use the 3D application setting
Maximum pre-rendered frames - Use the 3D application setting


in my cases it was with Maya 2017 Update 4 and Nvidia driver version 385.41

if I correctly understood this is due to the fact that during the time of work in Maya, the video card resets the frequencies and operating mode to the minimum and when the load is needed to update the viewport the driver does not have time to boost the video card and as a result the library crashes.

If this did not help you then try these methods:

  • Try to download and install other version video driver, but before install you need complete remove previous drivers and other utilities. For this task use Display Driver Uninstaller (DDU) . Also check  and uninstall Vulkan Run Time Libraries. Then install Nvidia Drivers and in custom mode select only drivers and PhysX. Do not install any Ansel and GeForce Experience 
  •  Other tips - change the Graphic device timeout in registry editor.

HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\GraphicsDrivers

With the GraphicsDrivers key selected, on the Edit menu, click New, and then select the following registry value from the drop-down menu specific to

For 64 bit Windows
a. Select QWORD (64-bit) value.
b. Type TdrDelay as the Name and click Enter.
c. Double-click TdrDelay and add 8 for the Value data and clickOK.

or create *.reg file and paste content below

Windows Registry Editor Version 5.00

[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\GraphicsDrivers]

"TdrDelay"=hex(b):08,00,00,00,00,00,00,00



1 comment:

  1. dont work with me... I have x299 mother and 7800x cpu and have the same error...

    ReplyDelete