Intermittent drop from GPU to CPU rendering in Iray
Autumn
Posts: 81
Hello lovely folks - not going to lie I am tearing my hair out here.
About a week ago, Daz Studio suddenly began dropping from GPU to CPU during scene rendering - ok fair enough it was a complex scene with a lot of bounce lighting so I thought nothing of it at first, then realised it was inconsistently doing so on all renders, no matter what was in the scene.
I used an old, moderately low complexity scene that I have rendered absolutely fine over the last year, on a regular basis, on this card, as my main test scene. It uses about 1/4 of the available GPU memory, so well under any thresholds.
On first load, it will, usually, render to about 150 iterations on GPU then drop to CPU
On second render attempt it will, usually, just generate a native CPU code and render to that only.
- Unless it doesn't, in which case it renders the scene out on the GPU to well over 1000 iterations without a hiccup.
I then tested it on a complex scene of four Genesis 8 figures with clothing and props, which more or less maxed out the dedicated GPU memory, which it rendered to around 800 iterations without a problem. Literally not one burp, worked like a charm on the GPU.
I also tested it on a single untextured primitive sphere with default lighting - it rendered this fine three times, then dropped it to CPU on the fourth around 100 iterations.
If I untick the "Allow CPU Fallback" option in the advanced parameters tab, it either cycles endlessly on the 'preparing scene' for Iray preview or simply refuses to render - either flipping to a black render or the checkerbox blank scene background as soon as it has finished calculating the scene.
I have both installed the latest version of Daz and the latest version of the Nvidia drivers.
Then rolled back to Nvidia Driver 441.66 (I can't try version 430.86 as it tells me its incompatible with my system)
Absolutely no change.
The GPU temperature is fine and sitting in a moderate range, even when the card does kick in, so I know it's not a temperature issue on the card that's causing it to drop to CPU.
I've ramped up the GPU fan speed, just to check, then dropped it back to default. The card is on default settings and not overclocked in any way.
I am running Windows 10 with a GTX 1080ti 11gb Nvidia Card - displays are run by the integrated Intel - Daz is set to use the Nvidia and can see it, and when it decides to render on the card, does so well and quickly.
Daz version 4.12.1.118 Pro 64 bit, Nvidia 441.66
I'm saving the scene, and restarting Daz before rendering (and not touching anything, like flipping to Iray preview - literally load and render). Again, absolutely inconsistent as to whether or not it makes any difference - the complex scene rendered without a hitch even though I'd been fiddling around in it beforehand.
The GPU is not accreting a memory load - so it's not stacking up until it's full and then dropping out - it's just either rendering to the GPU quite happily, or then simply refusing to, or dropping after starting.
I've turned off every additional filter option I can find (Firefly, etc)
I've tried it at 100 quality and 1. Average image size is 1000 x 1000 px
Heck I even took the sides off Merlin and cleaned him out! (There was an embarrassing amount of dust in there, but I've seen worse.)
Still no change.
It's the absolute inconsistency of this and the fact that I can't get a single change of parameters to do anything other than 'no change to random drop' or 'not render at all in Iray' that's really bugging me!
As a last question, is there somewhere I can download an older version of Daz please, as that's the only thing I can think of that I haven't been able to try.
If anyone has had similar experiences or has an answer, I'd love to know what I'm doing wrong! Card failure? (All diagnostics say it's fine) Windows update? Planetary misalignment? Failed to make the right ritual offerings?
Many thanks
Daz 3D is part of 
Connect
DAZ Productions, Inc.
7533 S Center View Ct #4664
West Jordan, UT 84084
Licensing Agreement | Terms of Service | Privacy Policy | EULA
© 2024 Daz Productions Inc. All Rights Reserved.
Comments
Have you tried sacrificing a jet black rooster with one pure white feather on its left wing, a blue left eye and a golden right eye at the stroke of midnight and sprinkling its blood over your computer while standing on one leg and chanting, "DAZ Studio bugs be gone!" three times in pre-proto Sub-Akhmimic?
Unfortunately, you'll have to open a case with DAZ support and convince them to send you an older version.
Blast I'm out of the correct roosters, only got white with a single black feather and obsidian eyes left - will a packet of chocolate biscuits do?
Ah bugger ... thanks, will drop them a line and see if they are willing to let me have a copy. Just want to do it as a final check really.
Many thanks.
Blast I'm out of the correct roosters, only got white with a single black feather and obsidian eyes left - will a packet of chocolate biscuits do?
Ah bugger ... thanks, will drop them a line and see if they are willing to let me have a copy. Just want to do it as a final check really.
Many thanks.
Happened to me recently and put my CPU to 100C for 2 weeks till I discovered my CPU was doing all the work. what I did to fix the issue was -> go into Nvidia control panel -> find "Manage GPU performance counter" -> change setting from "restrict GPU resource to admin only" to "open access to all"
That worked for me. But I was so angry to find out latest Daz build didn't override this option while all video games did.
Ah thank you, I'll go have a look at that - it's the sort of thing a random update would reset without telling anyone. Much appreciated.
Well I've just rendered my old, low complexity test scene four times in quick succession, with no restart of Daz in between and it's gone from either crashing back to CPU or just straight refusing to render to GPU to working as beautifully as it always has.
Honestly cannot thank you enough for that - didn't even know that setting existed under the Advanced tab in the control panel, and, on the face of it so far, it seems to have fixed the issue totally.
Really appreciated.
Heck, at least the inside of my machine got a clean. I guess that's one good thing to come out of the last week or so of hair-pulling :D
Nope, spoke too soon :(
Just tried to re-render the high complexity scene (the one that had previously, unexpectedly, worked just fine on the GPU until I stopped it at 800 iterations) and it dropped to CPU at around the 150 mark.
Ok so it's a complex scene, but still fits on the card. Ran it through Scene Optimiser to reduce texture file sizes, saved as a new file, shut Daz down, restarted and tried to render - first go dropped to CPU at the 150 mark again. This time it was showing on the GPU monitor as being large, but nowhere as near capacity as before so it's not like it dropped off with being right on the edge of capacity.
Again shut Daz, waited until GPU memory had dropped back down to just above zero, opened Daz, opened scene, pressed 'render' - it immediately dropped to CPU this time.
Have just shut Daz - and it took three goes to get it to reopen - tried my low complexity test scene that rendered four times in quick succession earlier on with no problem and again - dropped straight to CPU.
Am now going to try uninstalling and reinstalling Daz.
No further changes have been made to any settings this morning, beyond the one above of swapping "restrict GPU resource to admin only" to "open access to all" which was done on firing Merlin up this morning.
Hair/pulled. C'est la vie but still need more tea now!
GPUz Sensor Log and Daz Studio Log for latest test with low complexity scene, in case anyone can make sense of it x
(I'm baffled by the Optix Prime bit for a start - the latest version of Daz Studio, which I've just reinstalled, doesn't even have an option to switch it on)
2020-07-26 14:02:25.134 *** Scene Cleared ***
2020-07-26 14:02:25.333 File loaded in 0 min 0.2 sec.
2020-07-26 14:02:25.335 Loaded file: General Book Cover Mockup.duf
2020-07-26 14:02:25.394 Loaded image black oxide_albedo.jpg
2020-07-26 14:02:25.508 Loaded image 6x9 350 pg Dead Moon Small Ship.jpg
2020-07-26 14:02:25.594 Loaded image isagrd_book3.jpg
2020-07-26 14:02:40.792 Rendering image
2020-07-26 14:02:40.817 Iray [INFO] - IMAGE:IO :: 1.0 IMAGE io info : Loading image "D:\Daz Connect 09 2017 onwards\data\cloud\1_30790\runtime\textures\catharina_textures\pbs-vol-2-iray\metals\black oxide_specular.jpg", pixel type "Rgb", 1024x1024x1 pixels, 1 miplevel.
2020-07-26 14:02:40.818 Iray [INFO] - IMAGE:IO :: 1.0 IMAGE io info : Loading image "D:\Daz Connect 09 2017 onwards\data\cloud\1_30790\runtime\textures\catharina_textures\pbs-vol-2-iray\metals\black oxide_roughness.jpg", pixel type "Rgb", 1024x1024x1 pixels, 1 miplevel.
2020-07-26 14:02:40.826 Iray [INFO] - IMAGE:IO :: 1.0 IMAGE io info : Loading image "D:\Daz Connect 09 2017 onwards\data\cloud\1_30790\runtime\textures\catharina_textures\pbs-vol-2-iray\metals\black oxide_albedo.jpg", pixel type "Rgb", 1024x1024x1 pixels, 1 miplevel.
2020-07-26 14:02:40.827 Iray [INFO] - IMAGE:IO :: 1.0 IMAGE io info : Loading image "D:\Daz Connect 09 2017 onwards\data\cloud\1_30790\runtime\textures\catharina_textures\pbs-vol-2-iray\metals\black oxide_normal.jpg", pixel type "Rgb", 1024x1024x1 pixels, 1 miplevel.
2020-07-26 14:02:40.852 Iray [INFO] - IMAGE:IO :: 1.0 IMAGE io info : Loading image "D:\Pictures and Graphics\Book Covers\2020 Covers\Dead Moon Keith Crawford\6x9 350 pg Dead Moon Small Ship.jpg", pixel type "Rgb", 3911x2775x1 pixels, 1 miplevel.
2020-07-26 14:02:40.860 Iray [INFO] - IMAGE:IO :: 1.0 IMAGE io info : Loading image "D:\Daz Connect 09 2017 onwards\data\cloud\1_5164\runtime\textures\isa\isa_grdet\isagrd_book_bmp.jpg", pixel type "Rgb", 2000x2000x1 pixels, 1 miplevel.
2020-07-26 14:02:40.866 Iray [INFO] - IMAGE:IO :: 1.0 IMAGE io info : Loading image "D:\Daz Connect 09 2017 onwards\data\cloud\1_5164\runtime\textures\isa\isa_grdet\isagrd_book3.jpg", pixel type "Rgb", 2000x2000x1 pixels, 1 miplevel.
2020-07-26 14:02:40.892 Iray [INFO] - IMAGE:IO :: 1.0 IMAGE io info : Loading image "D:\Daz Connect 09 2017 onwards\data\cloud\1_33695\runtime\textures\terradome3\hdr\pro_hdr_skies_vol1\backlitcumulussky.hdr", pixel type "Rgb_fp", 8000x4000x1 pixels, 1 miplevel.
2020-07-26 14:02:41.122 Iray [INFO] - IRAY:RENDER :: 1.0 IRAY rend info : Updating geometry.
2020-07-26 14:02:41.122 Iray [INFO] - IRAY:RENDER :: 1.0 IRAY rend info : Importing scene graph.
2020-07-26 14:02:41.122 Iray [INFO] - IRAY:RENDER :: 1.0 IRAY rend info : Importing geometry for motion time 0
2020-07-26 14:02:41.140 Iray [INFO] - IRAY:RENDER :: 1.0 IRAY rend info : Geometry import (1 triangle object with 73710 triangles, 0 fiber objects with 0 fibers (0 segments), 1 triangle instance yielding 73710 triangles, 0 fiber instances yielding 0 segments) took 0.013s
2020-07-26 14:02:41.140 Iray [INFO] - IRAY:RENDER :: 1.0 IRAY rend info : Updating materials.
2020-07-26 14:02:41.143 Iray [INFO] - MATCNV:RENDER :: 1.0 MATCNV rend info : found 58 textures, 0 lambdas (0 unique)
2020-07-26 14:02:41.145 Iray [INFO] - IRAY:RENDER :: 1.0 IRAY rend info : Emitter geometry import (1 light source with 2 triangles, 1 instance) took 0.000s
2020-07-26 14:02:41.149 Iray [INFO] - IRAY:RENDER :: 1.0 IRAY rend info : Updating environment.
2020-07-26 14:02:42.795 Iray [INFO] - IRAY:RENDER :: 1.0 IRAY rend info : Updating backplate.
2020-07-26 14:02:42.797 Iray [INFO] - IRAY:RENDER :: 1.0 IRAY rend info : Updating lens.
2020-07-26 14:02:42.797 Iray [INFO] - IRAY:RENDER :: 1.0 IRAY rend info : Updating lights.
2020-07-26 14:02:42.797 Iray [INFO] - IRAY:RENDER :: 1.0 IRAY rend info : Updating object flags.
2020-07-26 14:02:42.797 Iray [INFO] - IRAY:RENDER :: 1.0 IRAY rend info : Updating caustic portals.
2020-07-26 14:02:42.802 Iray [INFO] - IRAY:RENDER :: 1.0 IRAY rend info : Updating decals.
2020-07-26 14:02:42.812 Iray [INFO] - IRAY:RENDER :: 1.0 IRAY rend info : Allocating 1-layer frame buffer
2020-07-26 14:02:42.824 Iray [INFO] - IRAY:RENDER :: 1.0 IRAY rend info : Using batch scheduling, caustic sampler disabled
2020-07-26 14:02:42.824 Iray [INFO] - IRAY:RENDER :: 1.0 IRAY rend info : Initializing local rendering.
2020-07-26 14:02:42.864 Iray [INFO] - IRAY:RENDER :: 1.0 IRAY rend info : Rendering with 1 device(s):
2020-07-26 14:02:42.869 Iray [INFO] - IRAY:RENDER :: 1.0 IRAY rend info : CUDA device 0 (GeForce GTX 1080 Ti)
2020-07-26 14:02:42.869 Iray [INFO] - IRAY:RENDER :: 1.0 IRAY rend info : Rendering...
2020-07-26 14:02:42.869 Iray [INFO] - IRAY:RENDER :: 1.3 IRAY rend progr: CUDA device 0 (GeForce GTX 1080 Ti): Processing scene...
2020-07-26 14:02:42.871 Iray [VERBOSE] - IRAY:RENDER :: 1.9 IRAY rend stat : Geometry memory consumption: 2.171 MiB (device 0), 0.000 B (host)
2020-07-26 14:02:42.871 Iray [INFO] - IRAY:RENDER :: 1.9 IRAY rend info : Using OptiX Prime version 5.0.1
2020-07-26 14:02:42.875 Iray [INFO] - IRAY:RENDER :: 1.9 IRAY rend info : Initializing OptiX Prime for CUDA device 0
2020-07-26 14:02:43.648 Iray [VERBOSE] - IRAY:RENDER :: 1.9 IRAY rend stat : Texture memory consumption: 14.238 MiB for 7 bitmaps (device 0)
2020-07-26 14:02:43.648 Iray [INFO] - IRAY:RENDER :: 1.9 IRAY rend info : Importing lights for motion time 0
2020-07-26 14:02:43.648 Iray [INFO] - IRAY:RENDER :: 1.9 IRAY rend info : Initializing light hierarchy.
2020-07-26 14:02:43.649 Iray [INFO] - IRAY:RENDER :: 1.9 IRAY rend info : Light hierarchy initialization took 0.001s
2020-07-26 14:02:43.654 Iray [VERBOSE] - IRAY:RENDER :: 1.9 IRAY rend stat : Lights memory consumption: 948.000 B (device 0)
2020-07-26 14:02:43.658 Iray [VERBOSE] - IRAY:RENDER :: 1.9 IRAY rend stat : Material measurement memory consumption: 0.000 B (GPU)
2020-07-26 14:02:43.659 Iray [VERBOSE] - IRAY:RENDER :: 1.9 IRAY rend stat : Materials memory consumption: 90.004 KiB (GPU)
2020-07-26 14:02:44.210 Iray [INFO] - IRAY:RENDER :: 1.3 IRAY rend info : CUDA device 0 (GeForce GTX 1080 Ti): Scene processed in 1.341s
2020-07-26 14:02:44.217 Iray [INFO] - IRAY:RENDER :: 1.3 IRAY rend info : CUDA device 0 (GeForce GTX 1080 Ti): Allocated 32.959 MiB for frame buffer
2020-07-26 14:02:44.284 Iray [INFO] - IRAY:RENDER :: 1.3 IRAY rend info : CUDA device 0 (GeForce GTX 1080 Ti): Allocated 1.688 GiB of work space (2048k active samples in 0.066s)
2020-07-26 14:02:44.284 Iray [INFO] - IRAY:RENDER :: 1.3 IRAY rend info : CUDA device 0 (GeForce GTX 1080 Ti): Used for display, optimizing for interactive usage (performance could be sacrificed)
2020-07-26 14:02:44.452 Iray [INFO] - IRAY:RENDER :: 1.3 IRAY rend info : Allocating 1-layer frame buffer
2020-07-26 14:02:44.472 Iray [INFO] - IRAY:RENDER :: 1.0 IRAY rend progr: Received update to 00001 iterations after 1.604s.
2020-07-26 14:02:44.588 Iray [INFO] - IRAY:RENDER :: 1.0 IRAY rend progr: Received update to 00002 iterations after 1.720s.
2020-07-26 14:02:44.700 Iray [INFO] - IRAY:RENDER :: 1.0 IRAY rend progr: Received update to 00003 iterations after 1.831s.
2020-07-26 14:02:44.808 Iray [INFO] - IRAY:RENDER :: 1.0 IRAY rend progr: Received update to 00004 iterations after 1.940s.
2020-07-26 14:02:44.918 Iray [INFO] - IRAY:RENDER :: 1.0 IRAY rend progr: Received update to 00005 iterations after 2.049s.
2020-07-26 14:02:45.027 Iray [INFO] - IRAY:RENDER :: 1.0 IRAY rend progr: Received update to 00006 iterations after 2.158s.
2020-07-26 14:02:45.139 Iray [INFO] - IRAY:RENDER :: 1.0 IRAY rend progr: Received update to 00007 iterations after 2.270s.
2020-07-26 14:02:45.247 Iray [INFO] - IRAY:RENDER :: 1.0 IRAY rend progr: Received update to 00008 iterations after 2.378s.
2020-07-26 14:02:45.356 Iray [INFO] - IRAY:RENDER :: 1.0 IRAY rend progr: Received update to 00009 iterations after 2.488s.
2020-07-26 14:02:45.467 Iray [INFO] - IRAY:RENDER :: 1.0 IRAY rend progr: Received update to 00010 iterations after 2.598s.
2020-07-26 14:02:45.578 Iray [INFO] - IRAY:RENDER :: 1.0 IRAY rend progr: Received update to 00011 iterations after 2.709s.
2020-07-26 14:02:45.784 Iray [INFO] - IRAY:RENDER :: 1.0 IRAY rend progr: Received update to 00013 iterations after 2.916s.
2020-07-26 14:02:45.991 Iray [INFO] - IRAY:RENDER :: 1.0 IRAY rend progr: Received update to 00015 iterations after 3.122s.
2020-07-26 14:02:46.261 Iray [INFO] - IRAY:RENDER :: 1.0 IRAY rend progr: Received update to 00017 iterations after 3.393s.
2020-07-26 14:02:46.508 Iray [INFO] - IRAY:RENDER :: 1.0 IRAY rend progr: Received update to 00020 iterations after 3.640s.
2020-07-26 14:02:46.816 Iray [INFO] - IRAY:RENDER :: 1.0 IRAY rend progr: Received update to 00023 iterations after 3.948s.
2020-07-26 14:02:47.214 Iray [INFO] - IRAY:RENDER :: 1.0 IRAY rend progr: Received update to 00027 iterations after 4.346s.
2020-07-26 14:02:47.664 Iray [INFO] - IRAY:RENDER :: 1.0 IRAY rend progr: Received update to 00031 iterations after 4.796s.
2020-07-26 14:02:48.103 Iray [INFO] - IRAY:RENDER :: 1.0 IRAY rend progr: Received update to 00036 iterations after 5.234s.
2020-07-26 14:02:48.693 Iray [INFO] - IRAY:RENDER :: 1.0 IRAY rend progr: Received update to 00042 iterations after 5.825s.
2020-07-26 14:02:49.386 Iray [INFO] - IRAY:RENDER :: 1.0 IRAY rend progr: Received update to 00049 iterations after 6.517s.
2020-07-26 14:02:50.180 Iray [INFO] - IRAY:RENDER :: 1.0 IRAY rend progr: Received update to 00057 iterations after 7.311s.
2020-07-26 14:02:51.217 Iray [INFO] - IRAY:RENDER :: 1.0 IRAY rend progr: Received update to 00067 iterations after 8.348s.
2020-07-26 14:02:52.275 Iray [INFO] - IRAY:RENDER :: 1.0 IRAY rend progr: Received update to 00078 iterations after 9.406s.
2020-07-26 14:02:53.563 Iray [INFO] - IRAY:RENDER :: 1.0 IRAY rend progr: Received update to 00091 iterations after 10.695s.
2020-07-26 14:02:54.721 WARNING: ..\..\..\..\..\src\pluginsource\DzIrayRender\dzneuraymgr.cpp(353): Iray [ERROR] - IRAY:RENDER :: 1.4 IRAY rend error: CUDA device 0 (GeForce GTX 1080 Ti): an illegal memory access was encountered (while launching CUDA renderer in <internal>:943)
2020-07-26 14:02:54.721 WARNING: ..\..\..\..\..\src\pluginsource\DzIrayRender\dzneuraymgr.cpp(353): Iray [ERROR] - IRAY:RENDER :: 1.4 IRAY rend error: CUDA device 0 (GeForce GTX 1080 Ti): Failed to launch renderer
2020-07-26 14:02:54.725 WARNING: ..\..\..\..\..\src\pluginsource\DzIrayRender\dzneuraymgr.cpp(353): Iray [ERROR] - IRAY:RENDER :: 1.3 IRAY rend error: CUDA device 0 (GeForce GTX 1080 Ti): Device failed while rendering
2020-07-26 14:02:54.726 WARNING: ..\..\..\..\..\src\pluginsource\DzIrayRender\dzneuraymgr.cpp(353): Iray [WARNING] - IRAY:RENDER :: 1.3 IRAY rend warn : All available GPUs failed.
2020-07-26 14:02:54.726 WARNING: ..\..\..\..\..\src\pluginsource\DzIrayRender\dzneuraymgr.cpp(353): Iray [WARNING] - IRAY:RENDER :: 1.3 IRAY rend warn : No devices activated. Enabling CPU fallback.
2020-07-26 14:02:54.729 WARNING: ..\..\..\..\..\src\pluginsource\DzIrayRender\dzneuraymgr.cpp(353): Iray [ERROR] - IRAY:RENDER :: 1.3 IRAY rend error: CUDA device 0 (GeForce GTX 1080 Ti): an illegal memory access was encountered (while initializing memory buffer)
2020-07-26 14:02:54.729 WARNING: ..\..\..\..\..\src\pluginsource\DzIrayRender\dzneuraymgr.cpp(353): Iray [ERROR] - IRAY:RENDER :: 1.3 IRAY rend error: All workers failed: aborting render
2020-07-26 14:02:54.730 WARNING: ..\..\..\..\..\src\pluginsource\DzIrayRender\dzneuraymgr.cpp(353): Iray [ERROR] - IRAY:RENDER :: 1.3 IRAY rend error: CUDA device 0 (GeForce GTX 1080 Ti): an illegal memory access was encountered (while de-allocating memory)
2020-07-26 14:02:54.733 WARNING: ..\..\..\..\..\src\pluginsource\DzIrayRender\dzneuraymgr.cpp(353): Iray [ERROR] - IRAY:RENDER :: 1.3 IRAY rend error: CUDA device 0 (GeForce GTX 1080 Ti): an illegal memory access was encountered (while de-allocating memory)
2020-07-26 14:02:54.733 WARNING: ..\..\..\..\..\src\pluginsource\DzIrayRender\dzneuraymgr.cpp(353): Iray [ERROR] - IRAY:RENDER :: 1.3 IRAY rend error: CUDA device 0 (GeForce GTX 1080 Ti): an illegal memory access was encountered (while de-allocating memory)
2020-07-26 14:02:54.737 WARNING: ..\..\..\..\..\src\pluginsource\DzIrayRender\dzneuraymgr.cpp(353): Iray [ERROR] - IRAY:RENDER :: 1.3 IRAY rend error: CUDA device 0 (GeForce GTX 1080 Ti): an illegal memory access was encountered (while de-allocating memory)
2020-07-26 14:02:54.737 WARNING: ..\..\..\..\..\src\pluginsource\DzIrayRender\dzneuraymgr.cpp(353): Iray [ERROR] - IRAY:RENDER :: 1.3 IRAY rend error: CUDA device 0 (GeForce GTX 1080 Ti): an illegal memory access was encountered (while de-allocating memory)
2020-07-26 14:02:54.741 WARNING: ..\..\..\..\..\src\pluginsource\DzIrayRender\dzneuraymgr.cpp(353): Iray [ERROR] - IRAY:RENDER :: 1.3 IRAY rend error: CUDA device 0 (GeForce GTX 1080 Ti): an illegal memory access was encountered (while de-allocating memory)
2020-07-26 14:02:54.741 WARNING: ..\..\..\..\..\src\pluginsource\DzIrayRender\dzneuraymgr.cpp(353): Iray [ERROR] - IRAY:RENDER :: 1.3 IRAY rend error: CUDA device 0 (GeForce GTX 1080 Ti): an illegal memory access was encountered (while de-allocating memory)
2020-07-26 14:02:54.745 WARNING: ..\..\..\..\..\src\pluginsource\DzIrayRender\dzneuraymgr.cpp(353): Iray [ERROR] - IRAY:RENDER :: 1.3 IRAY rend error: CUDA device 0 (GeForce GTX 1080 Ti): an illegal memory access was encountered (while de-allocating memory)
2020-07-26 14:02:54.745 WARNING: ..\..\..\..\..\src\pluginsource\DzIrayRender\dzneuraymgr.cpp(353): Iray [ERROR] - IRAY:RENDER :: 1.3 IRAY rend error: CUDA device 0 (GeForce GTX 1080 Ti): an illegal memory access was encountered (while de-allocating memory)
2020-07-26 14:02:54.749 WARNING: ..\..\..\..\..\src\pluginsource\DzIrayRender\dzneuraymgr.cpp(353): Iray [ERROR] - IRAY:RENDER :: 1.3 IRAY rend error: CUDA device 0 (GeForce GTX 1080 Ti): an illegal memory access was encountered (while de-allocating memory)
2020-07-26 14:02:54.749 WARNING: ..\..\..\..\..\src\pluginsource\DzIrayRender\dzneuraymgr.cpp(353): Iray [ERROR] - IRAY:RENDER :: 1.0 IRAY rend error: CUDA device 0 (GeForce GTX 1080 Ti): an illegal memory access was encountered (while de-allocating memory)
2020-07-26 14:02:54.753 WARNING: ..\..\..\..\..\src\pluginsource\DzIrayRender\dzneuraymgr.cpp(353): Iray [ERROR] - IRAY:RENDER :: 1.0 IRAY rend error: CUDA device 0 (GeForce GTX 1080 Ti): an illegal memory access was encountered (while de-allocating memory)
2020-07-26 14:02:54.753 WARNING: ..\..\..\..\..\src\pluginsource\DzIrayRender\dzneuraymgr.cpp(353): Iray [ERROR] - IRAY:RENDER :: 1.0 IRAY rend error: CUDA device 0 (GeForce GTX 1080 Ti): an illegal memory access was encountered (while de-allocating memory)
2020-07-26 14:02:54.757 WARNING: ..\..\..\..\..\src\pluginsource\DzIrayRender\dzneuraymgr.cpp(353): Iray [ERROR] - IRAY:RENDER :: 1.0 IRAY rend error: CUDA device 0 (GeForce GTX 1080 Ti): an illegal memory access was encountered (while de-allocating memory)
2020-07-26 14:02:54.759 Iray [INFO] - IRAY:RENDER :: 1.0 IRAY rend info : CPU: using 7 cores for rendering
2020-07-26 14:02:54.759 Iray [INFO] - IRAY:RENDER :: 1.0 IRAY rend info : Rendering with 1 device(s):
2020-07-26 14:02:54.759 Iray [INFO] - IRAY:RENDER :: 1.0 IRAY rend info : CPU
2020-07-26 14:02:54.763 Iray [INFO] - IRAY:RENDER :: 1.0 IRAY rend info : Rendering...
2020-07-26 14:02:54.763 Iray [INFO] - IRAY:RENDER :: 1.3 IRAY rend progr: CPU: Processing scene...
2020-07-26 14:02:54.764 Iray [INFO] - IRAY:RENDER :: 1.9 IRAY rend info : Using Embree 3.6.1
2020-07-26 14:02:54.764 Iray [INFO] - IRAY:RENDER :: 1.9 IRAY rend info : Initializing Embree
2020-07-26 14:02:54.772 Iray [VERBOSE] - IRAY:RENDER :: 1.9 IRAY rend stat : Native CPU code generated in 0.000s
2020-07-26 14:02:54.777 Iray [INFO] - IRAY:RENDER :: 1.3 IRAY rend info : CPU: Scene processed in 0.013s
2020-07-26 14:02:54.790 Iray [INFO] - IRAY:RENDER :: 1.3 IRAY rend info : CPU: Allocated 32.959 MiB for frame buffer
2020-07-26 14:02:56.724 Iray [INFO] - IRAY:RENDER :: 1.3 IRAY rend info : Allocating 1-layer frame buffer
2020-07-26 14:02:56.746 Iray [INFO] - IRAY:RENDER :: 1.0 IRAY rend progr: Received update to 00092 iterations after 13.844s.
2020-07-26 14:02:58.742 WARNING: ..\..\..\..\..\src\pluginsource\DzIrayRender\dzneuraymgr.cpp(353): Iray [WARNING] - POST:RENDER :: 1.0 POST rend warn : renderer iray has no more devices available. Postprocessing falling back to CPU.
2020-07-26 14:02:58.821 Iray [INFO] - IRAY:RENDER :: 1.0 IRAY rend progr: Received update to 00093 iterations after 15.919s.
2020-07-26 14:03:02.847 Iray [INFO] - IRAY:RENDER :: 1.0 IRAY rend progr: Received update to 00095 iterations after 19.944s.
2020-07-26 14:03:06.906 Iray [INFO] - IRAY:RENDER :: 1.0 IRAY rend progr: Received update to 00097 iterations after 24.004s.
2020-07-26 14:03:09.928 Saved image: C:\Users\cpeac\AppData\Roaming\DAZ 3D\Studio4\temp\render\r.png
2020-07-26 14:03:09.932 Finished Rendering
2020-07-26 14:03:09.968 Total Rendering Time: 29.22 seconds
2020-07-26 14:06:31.616 Iray [INFO] - IRAY:RENDER :: 1.0 IRAY rend info : Device statistics:
2020-07-26 14:06:31.616 Iray [INFO] - IRAY:RENDER :: 1.0 IRAY rend info : CPU: 6 iterations, 0.028s init, 14.346s render
GPUz Sensor Log and Daz Studio Log for latest test with low complexity scene, in case anyone can make sense of it x
(I'm baffled by the Optix Prime bit for a start - the latest version of Daz Studio, which I've just reinstalled, doesn't even have an option to switch it on)
2020-07-26 14:02:25.134 *** Scene Cleared ***
2020-07-26 14:02:25.333 File loaded in 0 min 0.2 sec.
2020-07-26 14:02:25.335 Loaded file: General Book Cover Mockup.duf
2020-07-26 14:02:25.394 Loaded image black oxide_albedo.jpg
2020-07-26 14:02:25.508 Loaded image 6x9 350 pg Dead Moon Small Ship.jpg
2020-07-26 14:02:25.594 Loaded image isagrd_book3.jpg
2020-07-26 14:02:40.792 Rendering image
2020-07-26 14:02:40.817 Iray [INFO] - IMAGE:IO :: 1.0 IMAGE io info : Loading image "D:\Daz Connect 09 2017 onwards\data\cloud\1_30790\runtime\textures\catharina_textures\pbs-vol-2-iray\metals\black oxide_specular.jpg", pixel type "Rgb", 1024x1024x1 pixels, 1 miplevel.
2020-07-26 14:02:40.818 Iray [INFO] - IMAGE:IO :: 1.0 IMAGE io info : Loading image "D:\Daz Connect 09 2017 onwards\data\cloud\1_30790\runtime\textures\catharina_textures\pbs-vol-2-iray\metals\black oxide_roughness.jpg", pixel type "Rgb", 1024x1024x1 pixels, 1 miplevel.
2020-07-26 14:02:40.826 Iray [INFO] - IMAGE:IO :: 1.0 IMAGE io info : Loading image "D:\Daz Connect 09 2017 onwards\data\cloud\1_30790\runtime\textures\catharina_textures\pbs-vol-2-iray\metals\black oxide_albedo.jpg", pixel type "Rgb", 1024x1024x1 pixels, 1 miplevel.
2020-07-26 14:02:40.827 Iray [INFO] - IMAGE:IO :: 1.0 IMAGE io info : Loading image "D:\Daz Connect 09 2017 onwards\data\cloud\1_30790\runtime\textures\catharina_textures\pbs-vol-2-iray\metals\black oxide_normal.jpg", pixel type "Rgb", 1024x1024x1 pixels, 1 miplevel.
2020-07-26 14:02:40.852 Iray [INFO] - IMAGE:IO :: 1.0 IMAGE io info : Loading image "D:\Pictures and Graphics\Book Covers\2020 Covers\Dead Moon Keith Crawford\6x9 350 pg Dead Moon Small Ship.jpg", pixel type "Rgb", 3911x2775x1 pixels, 1 miplevel.
2020-07-26 14:02:40.860 Iray [INFO] - IMAGE:IO :: 1.0 IMAGE io info : Loading image "D:\Daz Connect 09 2017 onwards\data\cloud\1_5164\runtime\textures\isa\isa_grdet\isagrd_book_bmp.jpg", pixel type "Rgb", 2000x2000x1 pixels, 1 miplevel.
2020-07-26 14:02:40.866 Iray [INFO] - IMAGE:IO :: 1.0 IMAGE io info : Loading image "D:\Daz Connect 09 2017 onwards\data\cloud\1_5164\runtime\textures\isa\isa_grdet\isagrd_book3.jpg", pixel type "Rgb", 2000x2000x1 pixels, 1 miplevel.
2020-07-26 14:02:40.892 Iray [INFO] - IMAGE:IO :: 1.0 IMAGE io info : Loading image "D:\Daz Connect 09 2017 onwards\data\cloud\1_33695\runtime\textures\terradome3\hdr\pro_hdr_skies_vol1\backlitcumulussky.hdr", pixel type "Rgb_fp", 8000x4000x1 pixels, 1 miplevel.
2020-07-26 14:02:41.122 Iray [INFO] - IRAY:RENDER :: 1.0 IRAY rend info : Updating geometry.
2020-07-26 14:02:41.122 Iray [INFO] - IRAY:RENDER :: 1.0 IRAY rend info : Importing scene graph.
2020-07-26 14:02:41.122 Iray [INFO] - IRAY:RENDER :: 1.0 IRAY rend info : Importing geometry for motion time 0
2020-07-26 14:02:41.140 Iray [INFO] - IRAY:RENDER :: 1.0 IRAY rend info : Geometry import (1 triangle object with 73710 triangles, 0 fiber objects with 0 fibers (0 segments), 1 triangle instance yielding 73710 triangles, 0 fiber instances yielding 0 segments) took 0.013s
2020-07-26 14:02:41.140 Iray [INFO] - IRAY:RENDER :: 1.0 IRAY rend info : Updating materials.
2020-07-26 14:02:41.143 Iray [INFO] - MATCNV:RENDER :: 1.0 MATCNV rend info : found 58 textures, 0 lambdas (0 unique)
2020-07-26 14:02:41.145 Iray [INFO] - IRAY:RENDER :: 1.0 IRAY rend info : Emitter geometry import (1 light source with 2 triangles, 1 instance) took 0.000s
2020-07-26 14:02:41.149 Iray [INFO] - IRAY:RENDER :: 1.0 IRAY rend info : Updating environment.
2020-07-26 14:02:42.795 Iray [INFO] - IRAY:RENDER :: 1.0 IRAY rend info : Updating backplate.
2020-07-26 14:02:42.797 Iray [INFO] - IRAY:RENDER :: 1.0 IRAY rend info : Updating lens.
2020-07-26 14:02:42.797 Iray [INFO] - IRAY:RENDER :: 1.0 IRAY rend info : Updating lights.
2020-07-26 14:02:42.797 Iray [INFO] - IRAY:RENDER :: 1.0 IRAY rend info : Updating object flags.
2020-07-26 14:02:42.797 Iray [INFO] - IRAY:RENDER :: 1.0 IRAY rend info : Updating caustic portals.
2020-07-26 14:02:42.802 Iray [INFO] - IRAY:RENDER :: 1.0 IRAY rend info : Updating decals.
2020-07-26 14:02:42.812 Iray [INFO] - IRAY:RENDER :: 1.0 IRAY rend info : Allocating 1-layer frame buffer
2020-07-26 14:02:42.824 Iray [INFO] - IRAY:RENDER :: 1.0 IRAY rend info : Using batch scheduling, caustic sampler disabled
2020-07-26 14:02:42.824 Iray [INFO] - IRAY:RENDER :: 1.0 IRAY rend info : Initializing local rendering.
2020-07-26 14:02:42.864 Iray [INFO] - IRAY:RENDER :: 1.0 IRAY rend info : Rendering with 1 device(s):
2020-07-26 14:02:42.869 Iray [INFO] - IRAY:RENDER :: 1.0 IRAY rend info : CUDA device 0 (GeForce GTX 1080 Ti)
2020-07-26 14:02:42.869 Iray [INFO] - IRAY:RENDER :: 1.0 IRAY rend info : Rendering...
2020-07-26 14:02:42.869 Iray [INFO] - IRAY:RENDER :: 1.3 IRAY rend progr: CUDA device 0 (GeForce GTX 1080 Ti): Processing scene...
2020-07-26 14:02:42.871 Iray [VERBOSE] - IRAY:RENDER :: 1.9 IRAY rend stat : Geometry memory consumption: 2.171 MiB (device 0), 0.000 B (host)
2020-07-26 14:02:42.871 Iray [INFO] - IRAY:RENDER :: 1.9 IRAY rend info : Using OptiX Prime version 5.0.1
2020-07-26 14:02:42.875 Iray [INFO] - IRAY:RENDER :: 1.9 IRAY rend info : Initializing OptiX Prime for CUDA device 0
2020-07-26 14:02:43.648 Iray [VERBOSE] - IRAY:RENDER :: 1.9 IRAY rend stat : Texture memory consumption: 14.238 MiB for 7 bitmaps (device 0)
2020-07-26 14:02:43.648 Iray [INFO] - IRAY:RENDER :: 1.9 IRAY rend info : Importing lights for motion time 0
2020-07-26 14:02:43.648 Iray [INFO] - IRAY:RENDER :: 1.9 IRAY rend info : Initializing light hierarchy.
2020-07-26 14:02:43.649 Iray [INFO] - IRAY:RENDER :: 1.9 IRAY rend info : Light hierarchy initialization took 0.001s
2020-07-26 14:02:43.654 Iray [VERBOSE] - IRAY:RENDER :: 1.9 IRAY rend stat : Lights memory consumption: 948.000 B (device 0)
2020-07-26 14:02:43.658 Iray [VERBOSE] - IRAY:RENDER :: 1.9 IRAY rend stat : Material measurement memory consumption: 0.000 B (GPU)
2020-07-26 14:02:43.659 Iray [VERBOSE] - IRAY:RENDER :: 1.9 IRAY rend stat : Materials memory consumption: 90.004 KiB (GPU)
2020-07-26 14:02:44.210 Iray [INFO] - IRAY:RENDER :: 1.3 IRAY rend info : CUDA device 0 (GeForce GTX 1080 Ti): Scene processed in 1.341s
2020-07-26 14:02:44.217 Iray [INFO] - IRAY:RENDER :: 1.3 IRAY rend info : CUDA device 0 (GeForce GTX 1080 Ti): Allocated 32.959 MiB for frame buffer
2020-07-26 14:02:44.284 Iray [INFO] - IRAY:RENDER :: 1.3 IRAY rend info : CUDA device 0 (GeForce GTX 1080 Ti): Allocated 1.688 GiB of work space (2048k active samples in 0.066s)
2020-07-26 14:02:44.284 Iray [INFO] - IRAY:RENDER :: 1.3 IRAY rend info : CUDA device 0 (GeForce GTX 1080 Ti): Used for display, optimizing for interactive usage (performance could be sacrificed)
2020-07-26 14:02:44.452 Iray [INFO] - IRAY:RENDER :: 1.3 IRAY rend info : Allocating 1-layer frame buffer
2020-07-26 14:02:44.472 Iray [INFO] - IRAY:RENDER :: 1.0 IRAY rend progr: Received update to 00001 iterations after 1.604s.
2020-07-26 14:02:44.588 Iray [INFO] - IRAY:RENDER :: 1.0 IRAY rend progr: Received update to 00002 iterations after 1.720s.
2020-07-26 14:02:44.700 Iray [INFO] - IRAY:RENDER :: 1.0 IRAY rend progr: Received update to 00003 iterations after 1.831s.
2020-07-26 14:02:44.808 Iray [INFO] - IRAY:RENDER :: 1.0 IRAY rend progr: Received update to 00004 iterations after 1.940s.
2020-07-26 14:02:44.918 Iray [INFO] - IRAY:RENDER :: 1.0 IRAY rend progr: Received update to 00005 iterations after 2.049s.
2020-07-26 14:02:45.027 Iray [INFO] - IRAY:RENDER :: 1.0 IRAY rend progr: Received update to 00006 iterations after 2.158s.
2020-07-26 14:02:45.139 Iray [INFO] - IRAY:RENDER :: 1.0 IRAY rend progr: Received update to 00007 iterations after 2.270s.
2020-07-26 14:02:45.247 Iray [INFO] - IRAY:RENDER :: 1.0 IRAY rend progr: Received update to 00008 iterations after 2.378s.
2020-07-26 14:02:45.356 Iray [INFO] - IRAY:RENDER :: 1.0 IRAY rend progr: Received update to 00009 iterations after 2.488s.
2020-07-26 14:02:45.467 Iray [INFO] - IRAY:RENDER :: 1.0 IRAY rend progr: Received update to 00010 iterations after 2.598s.
2020-07-26 14:02:45.578 Iray [INFO] - IRAY:RENDER :: 1.0 IRAY rend progr: Received update to 00011 iterations after 2.709s.
2020-07-26 14:02:45.784 Iray [INFO] - IRAY:RENDER :: 1.0 IRAY rend progr: Received update to 00013 iterations after 2.916s.
2020-07-26 14:02:45.991 Iray [INFO] - IRAY:RENDER :: 1.0 IRAY rend progr: Received update to 00015 iterations after 3.122s.
2020-07-26 14:02:46.261 Iray [INFO] - IRAY:RENDER :: 1.0 IRAY rend progr: Received update to 00017 iterations after 3.393s.
2020-07-26 14:02:46.508 Iray [INFO] - IRAY:RENDER :: 1.0 IRAY rend progr: Received update to 00020 iterations after 3.640s.
2020-07-26 14:02:46.816 Iray [INFO] - IRAY:RENDER :: 1.0 IRAY rend progr: Received update to 00023 iterations after 3.948s.
2020-07-26 14:02:47.214 Iray [INFO] - IRAY:RENDER :: 1.0 IRAY rend progr: Received update to 00027 iterations after 4.346s.
2020-07-26 14:02:47.664 Iray [INFO] - IRAY:RENDER :: 1.0 IRAY rend progr: Received update to 00031 iterations after 4.796s.
2020-07-26 14:02:48.103 Iray [INFO] - IRAY:RENDER :: 1.0 IRAY rend progr: Received update to 00036 iterations after 5.234s.
2020-07-26 14:02:48.693 Iray [INFO] - IRAY:RENDER :: 1.0 IRAY rend progr: Received update to 00042 iterations after 5.825s.
2020-07-26 14:02:49.386 Iray [INFO] - IRAY:RENDER :: 1.0 IRAY rend progr: Received update to 00049 iterations after 6.517s.
2020-07-26 14:02:50.180 Iray [INFO] - IRAY:RENDER :: 1.0 IRAY rend progr: Received update to 00057 iterations after 7.311s.
2020-07-26 14:02:51.217 Iray [INFO] - IRAY:RENDER :: 1.0 IRAY rend progr: Received update to 00067 iterations after 8.348s.
2020-07-26 14:02:52.275 Iray [INFO] - IRAY:RENDER :: 1.0 IRAY rend progr: Received update to 00078 iterations after 9.406s.
2020-07-26 14:02:53.563 Iray [INFO] - IRAY:RENDER :: 1.0 IRAY rend progr: Received update to 00091 iterations after 10.695s.
2020-07-26 14:02:54.721 WARNING: ..\..\..\..\..\src\pluginsource\DzIrayRender\dzneuraymgr.cpp(353): Iray [ERROR] - IRAY:RENDER :: 1.4 IRAY rend error: CUDA device 0 (GeForce GTX 1080 Ti): an illegal memory access was encountered (while launching CUDA renderer in <internal>:943)
2020-07-26 14:02:54.721 WARNING: ..\..\..\..\..\src\pluginsource\DzIrayRender\dzneuraymgr.cpp(353): Iray [ERROR] - IRAY:RENDER :: 1.4 IRAY rend error: CUDA device 0 (GeForce GTX 1080 Ti): Failed to launch renderer
2020-07-26 14:02:54.725 WARNING: ..\..\..\..\..\src\pluginsource\DzIrayRender\dzneuraymgr.cpp(353): Iray [ERROR] - IRAY:RENDER :: 1.3 IRAY rend error: CUDA device 0 (GeForce GTX 1080 Ti): Device failed while rendering
2020-07-26 14:02:54.726 WARNING: ..\..\..\..\..\src\pluginsource\DzIrayRender\dzneuraymgr.cpp(353): Iray [WARNING] - IRAY:RENDER :: 1.3 IRAY rend warn : All available GPUs failed.
2020-07-26 14:02:54.726 WARNING: ..\..\..\..\..\src\pluginsource\DzIrayRender\dzneuraymgr.cpp(353): Iray [WARNING] - IRAY:RENDER :: 1.3 IRAY rend warn : No devices activated. Enabling CPU fallback.
2020-07-26 14:02:54.729 WARNING: ..\..\..\..\..\src\pluginsource\DzIrayRender\dzneuraymgr.cpp(353): Iray [ERROR] - IRAY:RENDER :: 1.3 IRAY rend error: CUDA device 0 (GeForce GTX 1080 Ti): an illegal memory access was encountered (while initializing memory buffer)
2020-07-26 14:02:54.729 WARNING: ..\..\..\..\..\src\pluginsource\DzIrayRender\dzneuraymgr.cpp(353): Iray [ERROR] - IRAY:RENDER :: 1.3 IRAY rend error: All workers failed: aborting render
2020-07-26 14:02:54.730 WARNING: ..\..\..\..\..\src\pluginsource\DzIrayRender\dzneuraymgr.cpp(353): Iray [ERROR] - IRAY:RENDER :: 1.3 IRAY rend error: CUDA device 0 (GeForce GTX 1080 Ti): an illegal memory access was encountered (while de-allocating memory)
2020-07-26 14:02:54.733 WARNING: ..\..\..\..\..\src\pluginsource\DzIrayRender\dzneuraymgr.cpp(353): Iray [ERROR] - IRAY:RENDER :: 1.3 IRAY rend error: CUDA device 0 (GeForce GTX 1080 Ti): an illegal memory access was encountered (while de-allocating memory)
2020-07-26 14:02:54.733 WARNING: ..\..\..\..\..\src\pluginsource\DzIrayRender\dzneuraymgr.cpp(353): Iray [ERROR] - IRAY:RENDER :: 1.3 IRAY rend error: CUDA device 0 (GeForce GTX 1080 Ti): an illegal memory access was encountered (while de-allocating memory)
2020-07-26 14:02:54.737 WARNING: ..\..\..\..\..\src\pluginsource\DzIrayRender\dzneuraymgr.cpp(353): Iray [ERROR] - IRAY:RENDER :: 1.3 IRAY rend error: CUDA device 0 (GeForce GTX 1080 Ti): an illegal memory access was encountered (while de-allocating memory)
2020-07-26 14:02:54.737 WARNING: ..\..\..\..\..\src\pluginsource\DzIrayRender\dzneuraymgr.cpp(353): Iray [ERROR] - IRAY:RENDER :: 1.3 IRAY rend error: CUDA device 0 (GeForce GTX 1080 Ti): an illegal memory access was encountered (while de-allocating memory)
2020-07-26 14:02:54.741 WARNING: ..\..\..\..\..\src\pluginsource\DzIrayRender\dzneuraymgr.cpp(353): Iray [ERROR] - IRAY:RENDER :: 1.3 IRAY rend error: CUDA device 0 (GeForce GTX 1080 Ti): an illegal memory access was encountered (while de-allocating memory)
2020-07-26 14:02:54.741 WARNING: ..\..\..\..\..\src\pluginsource\DzIrayRender\dzneuraymgr.cpp(353): Iray [ERROR] - IRAY:RENDER :: 1.3 IRAY rend error: CUDA device 0 (GeForce GTX 1080 Ti): an illegal memory access was encountered (while de-allocating memory)
2020-07-26 14:02:54.745 WARNING: ..\..\..\..\..\src\pluginsource\DzIrayRender\dzneuraymgr.cpp(353): Iray [ERROR] - IRAY:RENDER :: 1.3 IRAY rend error: CUDA device 0 (GeForce GTX 1080 Ti): an illegal memory access was encountered (while de-allocating memory)
2020-07-26 14:02:54.745 WARNING: ..\..\..\..\..\src\pluginsource\DzIrayRender\dzneuraymgr.cpp(353): Iray [ERROR] - IRAY:RENDER :: 1.3 IRAY rend error: CUDA device 0 (GeForce GTX 1080 Ti): an illegal memory access was encountered (while de-allocating memory)
2020-07-26 14:02:54.749 WARNING: ..\..\..\..\..\src\pluginsource\DzIrayRender\dzneuraymgr.cpp(353): Iray [ERROR] - IRAY:RENDER :: 1.3 IRAY rend error: CUDA device 0 (GeForce GTX 1080 Ti): an illegal memory access was encountered (while de-allocating memory)
2020-07-26 14:02:54.749 WARNING: ..\..\..\..\..\src\pluginsource\DzIrayRender\dzneuraymgr.cpp(353): Iray [ERROR] - IRAY:RENDER :: 1.0 IRAY rend error: CUDA device 0 (GeForce GTX 1080 Ti): an illegal memory access was encountered (while de-allocating memory)
2020-07-26 14:02:54.753 WARNING: ..\..\..\..\..\src\pluginsource\DzIrayRender\dzneuraymgr.cpp(353): Iray [ERROR] - IRAY:RENDER :: 1.0 IRAY rend error: CUDA device 0 (GeForce GTX 1080 Ti): an illegal memory access was encountered (while de-allocating memory)
2020-07-26 14:02:54.753 WARNING: ..\..\..\..\..\src\pluginsource\DzIrayRender\dzneuraymgr.cpp(353): Iray [ERROR] - IRAY:RENDER :: 1.0 IRAY rend error: CUDA device 0 (GeForce GTX 1080 Ti): an illegal memory access was encountered (while de-allocating memory)
2020-07-26 14:02:54.757 WARNING: ..\..\..\..\..\src\pluginsource\DzIrayRender\dzneuraymgr.cpp(353): Iray [ERROR] - IRAY:RENDER :: 1.0 IRAY rend error: CUDA device 0 (GeForce GTX 1080 Ti): an illegal memory access was encountered (while de-allocating memory)
2020-07-26 14:02:54.759 Iray [INFO] - IRAY:RENDER :: 1.0 IRAY rend info : CPU: using 7 cores for rendering
2020-07-26 14:02:54.759 Iray [INFO] - IRAY:RENDER :: 1.0 IRAY rend info : Rendering with 1 device(s):
2020-07-26 14:02:54.759 Iray [INFO] - IRAY:RENDER :: 1.0 IRAY rend info : CPU
2020-07-26 14:02:54.763 Iray [INFO] - IRAY:RENDER :: 1.0 IRAY rend info : Rendering...
2020-07-26 14:02:54.763 Iray [INFO] - IRAY:RENDER :: 1.3 IRAY rend progr: CPU: Processing scene...
2020-07-26 14:02:54.764 Iray [INFO] - IRAY:RENDER :: 1.9 IRAY rend info : Using Embree 3.6.1
2020-07-26 14:02:54.764 Iray [INFO] - IRAY:RENDER :: 1.9 IRAY rend info : Initializing Embree
2020-07-26 14:02:54.772 Iray [VERBOSE] - IRAY:RENDER :: 1.9 IRAY rend stat : Native CPU code generated in 0.000s
2020-07-26 14:02:54.777 Iray [INFO] - IRAY:RENDER :: 1.3 IRAY rend info : CPU: Scene processed in 0.013s
2020-07-26 14:02:54.790 Iray [INFO] - IRAY:RENDER :: 1.3 IRAY rend info : CPU: Allocated 32.959 MiB for frame buffer
2020-07-26 14:02:56.724 Iray [INFO] - IRAY:RENDER :: 1.3 IRAY rend info : Allocating 1-layer frame buffer
2020-07-26 14:02:56.746 Iray [INFO] - IRAY:RENDER :: 1.0 IRAY rend progr: Received update to 00092 iterations after 13.844s.
2020-07-26 14:02:58.742 WARNING: ..\..\..\..\..\src\pluginsource\DzIrayRender\dzneuraymgr.cpp(353): Iray [WARNING] - POST:RENDER :: 1.0 POST rend warn : renderer iray has no more devices available. Postprocessing falling back to CPU.
2020-07-26 14:02:58.821 Iray [INFO] - IRAY:RENDER :: 1.0 IRAY rend progr: Received update to 00093 iterations after 15.919s.
2020-07-26 14:03:02.847 Iray [INFO] - IRAY:RENDER :: 1.0 IRAY rend progr: Received update to 00095 iterations after 19.944s.
2020-07-26 14:03:06.906 Iray [INFO] - IRAY:RENDER :: 1.0 IRAY rend progr: Received update to 00097 iterations after 24.004s.
2020-07-26 14:03:09.928 Saved image: C:\Users\cpeac\AppData\Roaming\DAZ 3D\Studio4\temp\render\r.png
2020-07-26 14:03:09.932 Finished Rendering
2020-07-26 14:03:09.968 Total Rendering Time: 29.22 seconds
2020-07-26 14:06:31.616 Iray [INFO] - IRAY:RENDER :: 1.0 IRAY rend info : Device statistics:
2020-07-26 14:06:31.616 Iray [INFO] - IRAY:RENDER :: 1.0 IRAY rend info : CPU: 6 iterations, 0.028s init, 14.346s render
@Autumn "I've tried it at 100 quality and 1"
For starters, don't do that. It is unecessary and will drastically increase render times. The Quality settings are multipliers that change internal Iray completiond factors. 2 is twice 1, 3 is 3x and so on. If your scene is properly lit, 1 will be more than sufficient for realistic scenes. The most important factor for great iIay scenes is lighting. Iray likes lots of light. Tonemap if you want darker scenes. Tone mapping happens at the end of the render process (internally).
More to your issue, try Nvidia driver 445.87. It has been stable on my machine on both 4.12.1.117 and Beta 4.12.2.6
Thank you - I've tried various driver versions without any change, but will give that one a go, much appreciated.
Just for clarity, I usually render somewhere between 2 and 10 - I know it's exponential - and render times have always been pretty swift on the current card using those settings. Testing it at 100 and at 1 were to see if that was making a difference or not to the dropout as I know 100 should make most things groan. It didn't change anything, but always good to put a reminder of it out there :)
I'm currently running 4.12.1.118 so will give it a shot.
Unfortunately, it didn't work - downloaded and installed driver 445.87, tested it with 4.12.1.118, then downloaded and tested it with Beta 4.12.2.6
Thank you for the suggestion - that, along with the other driver combinations I've tried, is at least telling me it's unlikely to be a driver/edition issue.
Ok so.
I was test rendering with a single primitive sphere, default lighting, and it was dropping straight to CPU - no cuda core activity after the second render, wether I restarted Daz or not.
I unticked 'check GPU driver version' (leaving the other two options checked) in the Advanced render tab and restarted.
Rendered primitive sphere with default lighting straight to GPU at 100% cuda core useage four times in quick succession (it had previous been dropping to CPU on the second time and refusing henceforth to GPU render)
Increased Sub D on sphere - rendered fine to GPU
Increased Sub D to max on sphere - rendered fine to GPU
Loaded low complexity old test scene and rendered four times in quick succession to 99% convergence without a problem on GPU
Loaded high complexity (four clothed figures with props) scene that had been optimised and rendered to 99% convergence on GPU
Loaded high complexity unoptimised scene (I'd expect this to crash out as I hadn't closed Daz at all in between above renders to clear memory) - started in GPU and dropped to CPU.
Closed Daz
Reopened
Tried primitive sphere test again - dropped straight to CPU
Closed Daz
Waited for around a minute - by which time Task Manager had told me the dedicated GPU memory had dropped back to just above zero.
Opened Daz, rendered one primitive sphere at base resolution - rendered fine on GPU
Opened high complexity unoptimised scene - rendered rapidly on GPU to 90% convergence (where I'd set it)
Tried to re-render same scene without closing Daz and sure enough it dropped to CPU - the GPU memory was still pretty full to begin with.
That's exactly the sort of behaviour I'd expect - so at least nominally it seems to have righted itself.
The only thing I changed was to untick the Check GPU Driver Version and Daz started rendering consistently to the GPU after that restart.
It's obviously also not clearing the card memory as fast as it did, but I can live with waiting a minute or so between restarts.
Hopefully, however it worked, that has now solved the issue and I can get back to rendering!
Will report back on here if it changes and reverts to dropping straight to CPU.
Currently using 4.12.1.118 and Nvidia driver 445.87
Nope next morning and it's back to dropping to the CPU with the WARNING: ..\..\..\..\..\src\pluginsource\DzIrayRender\dzneuraymgr.cpp(353): Iray [ERROR] - IRAY:RENDER :: 1.0 IRAY rend error: CUDA device 0 (GeForce GTX 1080 Ti): an illegal memory access was encountered (while de-allocating memory) on the log again.
Closing Daz and leaving it closed for a few moments means it will then at least try to render in GPU again - if you don't close it, it reverts straight to CPU.
Once more, annoyingly, it has rendered a single clothed figure out to 90% on GPU then persistently dropped to CPU on subsequent renders (with and without closing Daz in between) with no change to the scene or render settings at all.
Nothing I have loaded so far today has exceeded 5gb on an 11gb GPU card memory.
Argh.
I understand how you feel, just last week, I struggled with the same issue and my poor CPU were always worked over 102C untill I noticed Daz never tackled the resource from my GPU. Same error on my log as well.
Here're the steps I took, hope that works on your system as well.
1st thing I nocied, your GPU driver is outdated by 4 month, try the latest version first, I'd recommand using studio driver instead of game ready driver (if you do more rendering than gaming)
Also, can you making sure you did the following?
1. De-select all CPU render options in "render setting" as shown in picture
2. In Nvidia control panel Select "allow GPU performance counter to all"
3. clean uninstall/install nvidia driver, try using Nvidia stuido driver
4. Render the lowest res first see it tackles the GPU, if yes then move 1 garde higher, if still yes, then try your desirable res. that kind solved the problem for me.
Currently I'm using stuido driver v 451.48, not the latest but it's the one without problem.
Another thing to check.
Had this issue for heavier scenes. Am on Win7 though.
2 fixes:
(1) more system RAM (as opposed to VRAM). That dealt with one kind of CPU drop.
(2) turn off all your various powersave options in windows OS for GPU. Seriously. This fixed a big headache. It was like the delay with power consumption was tripping the drop to CPU, cos the GPU wasn't responding "enough" in time.
With Win10 updates continually changing your operating environemnt (from the numerous anecdotes on the web), some setting could have changed with either of these 2 DS operating needs.
Over at Tom's Hardware when people have GPU problems the first thing suggested is to check your PSU to see if it's up to scratch with delivering enough power to your GPU. Or if it's on the way out.
650 Watts is minimun for a 1080ti and a bit more to be on the safe side. If thermal throttling or drivers aren't the problem, then maybe you PSU is insufficient or faulty. Just an idea.
Hi folks, many thanks for the suggestions, will give them all a go:
Windli: I started by downloading the latest Nvidia game drivers - both Studio and Game and am presently on the older one as it's been reported as being stable. The newer drivers didn't make any difference to the issue, so I figured I'd stick with a slightly older, known stability one, until the next release comes out :) They have all been loaded as clean installs. Will give that driver number a go today though, thank you.
GPU is already set to 'allow all users' in the Nvidia control panel - thank you for posting that fix on another thread - sadly it didn't work here but it's worth knowing for future reference.
Currently, yes, I've been stepping up complexity in renders and it doesn't make much difference - it either decides to render to GPU, in which case it works perfectly on and up to a reasonable load capacity. Or it just drops a single sphere to the CPU. It's truly part of the frustration here - if it was just dropping scenes that were close to card capacity, I'd fully understand the card was probably getting old and leaking memory.
Saxa: I have 24gb Ram and 11gb Vram on the card - it does render when it goes to CPU but at a much slower rate and maxes out the CPU. Mind you, more RAM is the answer to most of lifes problems :D
Will give the powersave options a shot - thank you, didn't know about that.
Yes, I have dark thoughts about it being potentially a random Windows update causing the root issues too... not much I can do about that except wait for the next one that may or may not deglitch :(
Fred: The PSU is definitely a good call, thank you - it's less than two years old but it is a 650 so may well be starting to fade a bit these days as it gets a lot of use - will see what happens with Saxa's suggestions on power options above and if I can at least temporarily squeeze all the juice into the card without frying anything. Obviously don't want to be spending cash if it's not hardware starting to stutter, but a new PSU would definitely be easier on the bank account than a new GPU! It's definitely not thermal throttling as it's staying well within temperature limits (and I tested it with a higher fan speed using MSI afterburner - when it did render to GPU the temperature stayed very consistent and well under threshold).
Many thanks folks, I know 'I don't know what this is and it's not happening all the time' is the most frustrating thing of all to pin down, so really do appreciate the thoughts.
@Autumn
Re: Power Supply. If you run GPU-Z while rendering you can see what voltage is being supplied to the GPU. This may give you a feeling for whether the PSU is up to the task.
I had 32GB RAM with my 11gb Vram card. It wasn't enough at times. 64GB Ram is the sweet spot for my setup/usage. Especially if you are multitasking at same time. RAM is like oxygen. More stuff going on the more you need. If RAM is not enough, then the PC system is forced into a swapping mode, and this is where CPU bottleneck becomes a problem. Best is to monitor the RAM/CPU usage very closely through all stages of a scene. Especially on the initial loading during rendering. Daz Studio on loading uses a ton of RAM. Most demanding with SBH (strand based hair). If you are getting close to max 24GB, which am prettys sure is likely what is happening, then would definately start there is your budget allows.
It's a mystery to me that EVERY SCENE will render in Daz if I just allow the render fall back to CPU regardless of system ram & Vram amount, slowly but surely. Any GPU from the last 8 years are much faster than any CPU, but when you only let the scene render on GPU or both CPU&GPU(which almost never work) it breaks from left to right, Iray in Daz just never properly tackle GPU resource and let alone works well with CPU. CC3/Icone use iray plug in too, not only it renders much faster, but handles far larger & more complex scenes too. All evidents back up the fact that this is a poor optmization effort from Daz developers than anything else.
@windli3356 "All evidents back up the fact that this is a poor optmization effort from Daz developers"
The Iray engine in Studio is from Nvidia. Funny, but my renders don't give me issues. I've rendered with a 780TI, 980TI and 2080Super, all Iray. I understnad lighting and work within the limitations of the GPU VRAM and don't have issues. The 780TI and 980TI were on a Win 7 machine and the 2080TI on Win 10, new machine. Iray has always been designed to fall back to CPU if there is not enough VRAM to contain the entire scene.
Since last week, it worked flawlessly on my system again, and much faster than before, 700 ireation in 4 mins, solely GPU rendering. on the exact the same hardware, same driver, same everything, I didn't do any tweak at all, but before that iray sometimes would render on 1st try and then fail on the second attempt. The point I tried to make isn't that how rendering task algorithm will fallback to CPU when GPU is out of Vram, we know it will, but my point was when rendering confirmed to work 100% on a much slower medium (CPU) but fail to work on a much faster medium(GPU) while having the same amount of Ram, it indicates it's the optimization problem from the Dev team than anything else
I know Iray is from Nvidia, just as Google map API is from google, but you will find google map function broken on some vendor's websites or APPs when their API integration team didn't program them with enough effort.
Sorry, not been around for a week.
I tried the various power options - ran all the tests again with no change, still dropping randomly - but did find out my PSU is running at about 75%, when GPU decided to fire up, so that's good to know.
However, it is now fixed and running just fine!
Same as you Windli _ I hadn't used Daz for two days, opened it back up, has worked flawlessly ever since! There had been absolutely no changes made by me to effect this in the interim. Haven't changed drivers, settings, Daz, anything - literally nothing, no settings altered, I hadn't used it at all for two days or done any further alterations or tests. I literally opened it up, thinking I could maybe limp a render out in a few passes on the CPU and composite in PS and it just flew through it on the GPU like nothing had ever been wrong. I've subsequently run my test sequence back on it and then dumped a couple of pretty complex scenes up near the card limits onto it - all absolutely fine, not a hiccup in sight, rendering perfectly to GPU, as it should, and not dropping to CPU at all.
I can only assume there has been a background update run, either of Windows 10 or Nvidia that has sorted the problem out.
Flipping frustrating, but on the other hand, at least it's now optimised up the wazoo :D and rendering like a dream again.
Thank you to everyone for your help and suggestions - it was all stuff well worth trying and knowing about.