Loading...
> >

This Crashing Is Getting Old... GPU Crash

DrowElfMorwenDrowElfMorwen Posts: 538
edited November 2015 in Technical Help (nuts n bolts)

For a long, long time, every time I try to render with my GPU, DAZ Crashes. I still cannot figure out this problem, and I'm worried cause I just dropped a ton of cash on a Titan X and if DAZ won't stop crashing, I just lost a ton of money.

First I had a GTX 750, and right now I have a GTX 960. Now, I *just* got a 1100 power supply and hooked it up yesterday. For the hell of it I decided to try a GPU render. Amazingly, it actually worked... but only that once. Again, I'm getting the same usual crash. I am attaching a screencap and a copy of part of my Log File.

And YES, everything is up to date. Windows 7, my GPU driver, DAZ, etc... Also, this happens with 3Delight and Iray both, it has been for years now, so I've never been able to use my GPU to render, even though I should be able to as far as I can tell. Also, DAZ is the ONLY program that crashes.

*****************************************

 

Iray INFO - module:category(IRAY:RENDER):   1.1   IRAY   rend info : NVIDIA display driver version: 35891
Iray INFO - module:category(IRAY:RENDER):   1.1   IRAY   rend info : Your NVIDIA driver supports CUDA version up to 7050; iray requires CUDA version 6050; all is good.
Iray INFO - module:category(IRAY:RENDER):   1.1   IRAY   rend info : Using iray plugin version 4.0, build 231000.11582 n, 29 Apr 2015, nt-x86-64-vc11.
Iray INFO - module:category(IRAY:RENDER):   1.1   IRAY   rend info : CUDA device 0: "GeForce GTX 960" (compute capability 5.2, 2048MB total, 1880MB available, display attached)
Iray INFO - module:category(BLEND:RENDER):   1.1   BLEND  rend info : blend render (build 231000.11582, 29 Apr 2015) initialized
Iray INFO - module:category(IRAY_CLOUD_CLIENT:NETWORK):   1.1   IRAY_C net  info : iray_cloud (build 231000.11582, 29 Apr 2015) initialized
Iray INFO - module:category(IRT:RENDER):   1.0   IRT    rend info : Initializing context.
Iray INFO - module:category(IRT:RENDER):   1.1   IRT    rend info : irt (build 231000.11582, 29 Apr 2015) initialized
Iray INFO - module:category(EIAXF:IO):   1.1   EIAXF  io   info : axf importer (build 231000.11582, 29 Apr 2015) initialized
Iray INFO - module:category(ICB:IO):   1.1   ICB    io   info : cb_importer (build 231000.11582, 29 Apr 2015) initialized
Iray INFO - module:category(IRAY_CLOUD_CLIENT:NETWORK):   1.1   IRAY_C net  info : iray_bridge_snapshot (build 231000.11582, 29 Apr 2015) initialized
Iray INFO - module:category(IRAY_CLOUD_SERVER:NETWORK):   1.1   IRAY_C net  info : iray_bridge_server (build 231000.11582, 29 Apr 2015) initialized
Iray INFO - module:category(EEMI:IO):   1.1   EEMI   io   info : .mi exporter (build 231000.11582, 29 Apr 2015) initialized
Iray INFO - module:category(EIMI:IO):   1.1   EIMI   io   info : .mi importer (build 231000.11582, 29 Apr 2015) initialized
Iray INFO - module:category(IRT:RENDER):   1.10  IRT    rend info : Host 1 connected to the cluster.
Iray INFO - module:category(IRAY:RENDER):   1.0   IRAY   rend info : CUDA device 0: "GeForce GTX 960" (compute capability 5.2, 2048MB total, 1880MB available, display attached)
Iray INFO - module:category(IRT:RENDER):   1.0   IRT    rend info : Resource assignment for host 0 has changed.
NVidia Iray GPUs:
    GPU: 1 - GeForce GTX 960
    Memory Size: 1.9 GB
    Clock Rate: 1228000 KH
    Multi Processor Count: 8
    Cuda Version: 5.2
Iray INFO - module:category(MDLC:IO):   1.0   MDLC   io   info : Found MDL module daz_3d::basic in file F:\DAZ\Studio\content\DAZ 3D\DAZStudio4\shaders\iray\daz_3d\basic.mdl
Iray INFO - module:category(MDLC:IO):   1.0   MDLC   io   info : Found MDL module nvidia::lights_photometric in file F:\DAZ\Studio\content\DAZ 3D\DAZStudio4\shaders\iray\nvidia\lights_photometric.mdl
Iray INFO - module:category(MDLC:IO):   1.0   MDLC   io   info : Found MDL module daz_3d::property_annotations in file F:\DAZ\Studio\content\DAZ 3D\DAZStudio4\shaders\iray\daz_3d\property_annotations.mdl
Iray INFO - module:category(MDLC:IO):   1.0   MDLC   io   info : Found MDL module daz_3d::irayubermaterial in file F:\DAZ\Studio\content\DAZ 3D\DAZStudio4\shaders\iray\daz_3d\irayubermaterial.mdl
Iray INFO - module:category(MDLC:IO):   1.0   MDLC   io   info : Found MDL module nvidia::axf_importer::axf_importer in file F:\DAZ\Studio\content\DAZ 3D\DAZStudio4\shaders\iray\nvidia\axf_importer\axf_importer.mdl
Iray INFO - module:category(MDLC:IO):   1.0   MDLC   io   info : Found MDL module nvidia::core_definitions in file F:\DAZ\Studio\content\DAZ 3D\DAZStudio4\shaders\iray\nvidia\core_definitions.mdl
Total class factories: 1873
Creating Script Engine...
WARNING: 3DConnexion Plug-in Error: Could not create Device, CoCreateInstance failed
3D mouse support library could not be loaded.
Creating Main Window...
Creating Viewport Manager...
Successfully created OpenGL viewport for Viewport1.
Successfully created OpenGL viewport for Viewport2.
Successfully created OpenGL viewport for Viewport3.
Successfully created OpenGL viewport for Viewport4.
Creating Action Manager...
WARNING: libpng warning: Unknown iTXt compression type or method
Creating Pane Manager...
Successfully created OpenGL viewport for AuxViewportView.
WARNING: QFile::flush: No file engine. Is IODevice open?
WARNING: QFile::flush: No file engine. Is IODevice open?
Executing startup script...
Started in: F:/DAZ/Studio/content/DAZ 3D/DAZStudio4
DAZ Studio Started
Creating Pixel Buffer
Pixel buffer - Width: 1024 Height: 1024
Compiling OpenGL Shader...
Fragment Shader:
Fragment Shader compiled successfully.
Linking Shader:
Shader Program successfully linked.

********

I don't know where to end it, I opened up DAZ and my scene again after crashing--maybe there is something relevant there?

 

crash-error.jpg
1200 x 722 - 135K
Post edited by DrowElfMorwen on

Comments

  • ben98120000ben98120000 Posts: 469

    From https://support.microsoft.com/en-us/kb/2665946

    1. Exit all Windows based programs.
    2. Click Start, type regedit in the Search box, and then double-click regedit.exe from the results above. If you are prompted for an administrator password or confirmation, type the password or provide confirmation.
    3. Browse to and then click the following registry subkey:
      HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\GraphicsDrivers
    4. On the Edit menu, click New, and then select the following registry value from the drop-down menu specific to your version of Windows (32 bit, or 64 bit):

      For 32 bit Windows
      1. Select DWORD (32-bit) value.
      2. Type TdrDelay as the Name and click Enter.
      3. Double-click TdrDelay and add 8 for the Value data and click OK.

      For 64 bit Windows 
       
      1. Select QWORD (64-bit) value.
      2. Type TdrDelay as the Name and click Enter.
      3. Double-click TdrDelay and add 8 for the Value data and clickOK.
    5. Close the registry editor and then restart your computer for the changes to take affect.
  • Richard HaseltineRichard Haseltine Posts: 100,990

    What is in the scene? There are a few items - the SciFi Lab is one I think - that can cause a crash in Iray, at least if using both GPU and CPU. DS 4.9, currectly available as a Public beta, has an updated Iray which fixes that issue.

  • ToborTobor Posts: 2,300
    edited November 2015

    One thing that I noticed is your 960 has only 2GB of RAM, *and* it's connected to your monitor. Not a great combination. I've encountered problems when trying to use a card with limited RAM that's also connected to the monitor.

    If you still have your 750, and your PC case and power supply has the necessary power cables, you might want to try putting the monitor on that card, and leaving the 960 for rendering. Don't try to also render from the 750. With only 1GB of RAM, that card likely cannot render anything more than the very simplest of test scenes.

    I assume your Titan X hasn't been installed yet. You shouldn't have this particular problem with that card once it gets installed. You might try:

    * the 4.9 beta
    * being sure every single surface in your scene is manually converted to Iray
    * you don't have any remnant files in your brickyard (render temporary files)
    * simpler scenes
    * the timeout fix as noted above (applies mostly when you use the same card for display and rendering)
    * get a program like GPU-Z to determine exactly how much video RAM your scenes are using; anything over 2GB your current setup will not render through GPU

    Post edited by Tobor on
  • DrowElfMorwenDrowElfMorwen Posts: 538

    Tobor, I have GPU-Z, but I wish to ask, should I mvoe my monitor cord to plug into the on-board graphics? (also, it doesn't matter if I'm rendering to Iray or 3Delight)

    ben, thanks for the information!

    To Richard, It was a couple of extensive trees and two Genesis figures. However, even with other set-ups, even simple ones, it will crash.

  • DrowElfMorwenDrowElfMorwen Posts: 538

    Okay so after a couple hours of fooling around and some "why not" fiddling, I think I finally managed to figure out what the problem was. At least, I'm 75% sure, which is the most I've ever been sure I have finally fixed this. This whole time I have had my monitor hooked up to the GPU through an HDMI cord, connected to my GPU because connecting it to the CPU wouldn't work at all. Today, after trying every combination of two and three wires with the HDMI, VGA and a DVI, I seem to have a solution: keep the HDMI cord on the GPU as usual, but plug the DVI cord into the CPU card. Voila! I have done several spot renders and different sized renders of a Genesis figure with a few trees and ground in the background.

    I don't know why it works, but I am definitely not complaining.

  • DrowElfMorwenDrowElfMorwen Posts: 538

    Okay. I spoke too soon. After another render, it crashed again :(

  • RuphussRuphuss Posts: 2,631

    did you try various scenes ?

    did you try very small scenes ?

    i would delete the trees and try again

  • IceCrMnIceCrMn Posts: 2,129

    if the TDR fix didn't work, and that is a known problem with the nvidia GPUs, then it's the overclock on the card.

    The reference cards have a clock speed of 1127MHz

    http://www.geforce.com/hardware/desktop-gpus/geforce-gtx-960/specifications

    from your log:

    NVidia Iray GPUs:
        GPU: 1 - GeForce GTX 960
        Memory Size: 1.9 GB
        Clock Rate: 1228000 KH

    1228000KHz= 1228MHz

    I would back-off the overclock to reference timing and then test again.If you are running any type of overclock on the CPU I would reset those to factory timing also and disable any CPU Turbo boost nonsense :)

    You may even need to underclock the card, so try testing with lowwer clock timings until you find one that is stable. (MSI Afterburner is a popular tool for setting clock timing on nvidia cards)

    If this was a recent purchase I would consider returning it ( file for an RMA with whom ever you bought it from) , the card maybe defective.

    3Delight doesn't make use of the GPU so it shouldn't be causing a GPU related crash.

     

     

Sign In or Register to comment.