Daz3d studio rendering with GPU fails to CPU

2080TI fails for me and drops to CPU. I tried all different studio and game drivers (from 430.86 to 442 the newest)

Updated Daz3d to 4.12

Changed the GPU and MEM clock in MSI Afterburner to the lowest, and the power unit to 80% (and many between)

PhysX to CPU

Virtual Memory to 4, 8, 12, 24, 36, 40, 48 gb....

Daz3d defulat settings (no denoiser etc) CPU is unchecked and optix, tried with checked as well and many other settings

Dunno what to do anymore. I even tryed to get a replaced GPU but the store says its not faulty. All the test are running fine (max3d, furmark etc)

Problem seem to be only with Daz3d and IRAY and this is the ONLY thing i need from this super expensive hardware

Please help!

 

ERROR:

WARNING: ..\..\..\..\..\src\pluginsource\DzIrayRender\dzneuraymgr.cpp(302): Iray ERROR - module:category(IRAY:RENDER):   1.0   IRAY   rend error: CUDA device 0 (GeForce RTX 2080 Ti): an illegal memory access was encountered (while de-allocating memory)

«1

Comments

  • That error sayws the card ran out of memory while loading the scene.

    Have you tried just rendering a single primitive with just a shader, one light and one camera? Does that fall to CPU or not?

  • That error sayws the card ran out of memory while loading the scene.

    Have you tried just rendering a single primitive with just a shader, one light and one camera? Does that fall to CPU or not?

    The error is random, and it doesnt matter how big the scene is. And sometimes it renders normally for few hours (batch or animation etc)

    Most baffeling about it that the same scenes and animations render normally on my other PC with 1070TI. Never got this error on it before.

    Why does it run out of memoery of a single gen3 model?

  • mclaughmclaugh Posts: 221

    Let's see:

    1) do you have any iray preview viewports open? If yes, close the iray viewports or change them to wireframe or texture shaded, restart DAZ, load the scene and try again.

    2) do you have any completed or partial renders windows open? If yes, close the open render windows, restart DS, load the scene and try again.

    3) does it drop to CPU if you change any iray preview viewports to wire or texture shaded, restart DS, load a scene, and render immediately, or only on subsequent (2nd, 3rd, 4th, etc.) renders?

    If it doesn't drop to CPU on the first render after (re)starting DS but does on a subsequent render, that's a pretty good indication that you're running out of VRAM due to a cumulative memory leak (a known, long-standing issue).

  • I got the same problem with the new beta build. I was using 4.12.0 and I never had a problem before with iray render preview. Now if I stay in the iray render preview for 5-10 mins and change some surfaces etc. it will eventually drop the gpu all together and go to CPU. I've never, ever had that problem with previous Daz versions. I can stay in a render preview for hour/s and it wouldn't drop me to the CPU. Now it does and it's absolutely annoying, because I have to reset the whole Daz Studio to use my GPU again. I am with GTX 1080 Ti.

  • ParallaxCreatesParallaxCreates Posts: 467
    edited February 2020
    evilcho_ said:

    I got the same problem with the new beta build. I was using 4.12.0 and I never had a problem before with iray render preview. Now if I stay in the iray render preview for 5-10 mins and change some surfaces etc. it will eventually drop the gpu all together and go to CPU. I've never, ever had that problem with previous Daz versions. I can stay in a render preview for hour/s and it wouldn't drop me to the CPU. Now it does and it's absolutely annoying, because I have to reset the whole Daz Studio to use my GPU again. I am with GTX 1080 Ti.

    I'm afraid that may not go away either, it's the reason I always stay using a Release that's stable for me while only updating the betas. It's how I catch any issues first so that I may avoid "committing" to them by updating my main Daz.

    Right now I've been using the most stable Daz for my setup which is comprised of 1080 Tis - Daz 4.11

    I simply kept updating my beta version and started to catch that issue a while ago with the implementation of 4.12 so I stayed at 4.11. There's a rather long thread regarding the fall back if you missed btw. 

     

    UPDATE: I saw you posted there. Yup, welcome home for now lol.

     

    Post edited by ParallaxCreates on
  • mikael-aronssonmikael-aronsson Posts: 585
    edited February 2020

    Well, the error message does NOT say you ran out of memory, it says " illegal memory access", and that means that something got corrupt somewhere and it is trying to deallocate something that does not exist or that has been corrupt, the problem could have happend long time before that, something overwite something else or write to a memory area it should not, and a typical indication of that are random error messages, so it does sound like a bug in either IRAY or the DS->IRAY interface code.

    Check the log and see if you have any strange warnings before the error message that could explain what is going on.

     

     

    Post edited by mikael-aronsson on
  • So, the best i can do to "free" VRAM is to shut down PC. Do this few times a day.

    Now, I turn off internet connection, anti virus, Have nothing else opened, right. And then i open DAZ and start a animation. Leave PC. Only Daz and background services run.

    20 minutes to render one frame, and it fails randomlly. Sometimes after 1 minute, sometimes it works normally for few hours.

    VRAM is like 4gb used.

     

  • areg5areg5 Posts: 617

    Tell ya what:  One of the issues with 4.11 and higher is that the cache does not clear after a job.  So you load the next scene, and there is less usable VRAM.  4.10 doesn't have that problem.  But the cache should clear if you shut down Daz.  You can monitor what the VRAM is doing using GPU-Z.  I render in batches, and I've lately been using Manfiurday's render Queue.  It shuts down Daz in between renders, and clears the cache.

  • Is there any other sollutions for this? There must be something to do fix this problem.

  • areg5areg5 Posts: 617

    Is there any other sollutions for this? There must be something to do fix this problem.

    Still having problems?

  • areg5 said:

    Is there any other sollutions for this? There must be something to do fix this problem.

    Still having problems?

    Yep :( It's been going on for a year. I'm still trying different nvidia drivers and updating Daz3D Studio beta releases...

    Reading forums about this issue and trying different things, but with no luck.

     

  • areg5areg5 Posts: 617

    What is your system?

  • areg5 said:

    What is your system?

    Ryzen 5 2600

    2080TI

    32GB DDR4

    500gb SSD

    1200W PSU

    Window 10 Pro 64 bit

  • areg5areg5 Posts: 617
    edited May 2020

    What nvidia driver are you using? How long does it render before it falls to CPU, and what are the temps doing at the moment it fails? What is your motherboard? Are you overclocking it in any way?  Are you using Precision X1, XOC or some other program to manage the GPU?

    Post edited by areg5 on
  • flaviudeceanflaviudecean Posts: 9
    edited May 2020

    Because of the same problem with Iray, I learned how to use Octane Render. It has a free plugin for Daz, it's infinitely more reliable tan Iray, and it can extent memory from VRAM to RAM. It does a good job at importing and converting the Iray textures, then you have to fine tune.

    Post edited by flaviudecean on
  • KeryaKerya Posts: 10,943

    Because of the same problem with Iray, I learned how to use Octane Render. It has a free plugin for Daz, it's infinitely more reliable tan Iray, and it can extent memory from VRAM to RAM. It does a good job at importing and converting the Iray textures, then you have to fine tune.

     

    If you are running into shutdown troubles, it will be because of Octane ...

    https://www.daz3d.com/forums/discussion/comment/5643596/#Comment_5643596

     

  • areg5 said:

    What nvidia driver are you using? How long does it render before it falls to CPU, and what are the temps doing at the moment it fails? What is your motherboard? Are you overclocking it in any way?  Are you using Precision X1, XOC or some other program to manage the GPU?

    Right now I'm using the latest NVIDIA studio drivers (i tryed so many drivers, so that's deff not the issue)

    Sometimes it fails 1 minute into rendering, sometimes after 2 hours. It's random. And it doesn't matter if I have any aps open, network disabled, anti-virus etc etc

    I'm using Afterburner and i actually "downclocked" the GPU (core clock -502, memory clock -145, power limit 90%) and i offcourse tried many many variations in afterburner. this has been going on for almost a year, so i did too much testing.

    Temperature get's to 68C, and VRAM usage to 4-5gb and it still fails.

    Motherboard is Asrock B450M Pro4

    I tried replacing the GPU, but the store told me they can't take it back since the GPU is working. Only Daz3D and Iray rendering is having problems, but that's the only thing i need. I only play online chess at PC lol

    I also did stress testing in Furmark, Superposition Benchmark, and two others i forget the name. And it never crashed or anything.

  • areg5areg5 Posts: 617

    You play online chess?  So do I, on Gameknot.  Ok, first off, the drivers:  how do you go about updating them?  Do you use DDU first to completely remove all of the old driver first?  The do you do a fresh install?  I recommend that, and not installing Geoforce Experience.

    Power should be good.  How as far as downclocking: I would not adjust the clocks at all.  All I do with afterburner is set the fans to go to 100% at 50 degrees. Although you aren't running hot, I've come to the conclusion that temperature fluctuations may cause the power demand to hiccup, and that could be enough to cause it to crash to CPU.  That's my opinion.  Like you, I have been through a lot of testing and tweaking to get my system to work.

    Do not overclock the MB.  Use default settings on that.

    One of the things I've done in the past that seems to get renders to happen when they are stalling is to disable Optix Prime.  Many times that helps.

    It goes without saying but on rendering I never have CPU selected at all.  Just the card.

  • areg5 said:

    Do you use DDU first to completely remove all of the old driver first?

    Yea, complete uninstall.

    areg5 said:

    The do you do a fresh install?  I recommend that, and not installing Geoforce Experience.

    Yep.

    areg5 said:

    Power should be good.  How as far as downclocking: I would not adjust the clocks at all.  All I do with afterburner is set the fans to go to 100% at 50 degrees. Although you aren't running hot, I've come to the conclusion that temperature fluctuations may cause the power demand to hiccup, and that could be enough to cause it to crash to CPU.  That's my opinion.  Like you, I have been through a lot of testing and tweaking to get my system to work.

    My 2080ti worked for like 3 weeks first time i "downclocked" it. I though it was a fix back then, but it wasn't.

    areg5 said:

    Do not overclock the MB.  Use default settings on that.

    Nothing is overclocked.

    areg5 said:

    One of the things I've done in the past that seems to get renders to happen when they are stalling is to disable Optix Prime.  Many times that helps.

    It goes without saying but on rendering I never have CPU selected at all.  Just the card.

    Optix and CPU is uncheck offcourse.

    UPDATE:

    I installed the latest NVIDIA studio drivers and now I can't render more then 20 minutes in a row.

     

     

     

  • freedomforever984freedomforever984 Posts: 25
    edited June 2020

    Here is the log file

    2020-06-11 09:48:37.141 WARNING: ..\..\..\..\..\src\pluginsource\DzIrayRender\dzneuraymgr.cpp(353): Iray [ERROR] - IRAY:RENDER ::   1.12  IRAY   rend error: CUDA device 0 (GeForce RTX 2080 Ti): an illegal memory access was encountered (while launching CUDA renderer in <internal>:943)2020-06-11 09:48:37.147 WARNING: ..\..\..\..\..\src\pluginsource\DzIrayRender\dzneuraymgr.cpp(353): Iray [ERROR] - IRAY:RENDER ::   1.12  IRAY   rend error: CUDA device 0 (GeForce RTX 2080 Ti): Failed to launch renderer2020-06-11 09:48:37.147 WARNING: ..\..\..\..\..\src\pluginsource\DzIrayRender\dzneuraymgr.cpp(353): Iray [ERROR] - IRAY:RENDER ::   1.2   IRAY   rend error: CUDA device 0 (GeForce RTX 2080 Ti): Device failed while rendering2020-06-11 09:48:37.147 WARNING: ..\..\..\..\..\src\pluginsource\DzIrayRender\dzneuraymgr.cpp(353): Iray [WARNING] - IRAY:RENDER ::   1.2   IRAY   rend warn : All available GPUs failed.2020-06-11 09:48:37.149 WARNING: ..\..\..\..\..\src\pluginsource\DzIrayRender\dzneuraymgr.cpp(353): Iray [ERROR] - IRAY:RENDER ::   1.2   IRAY   rend error: Fallback to CPU not allowed.2020-06-11 09:48:37.149 WARNING: ..\..\..\..\..\src\pluginsource\DzIrayRender\dzneuraymgr.cpp(353): Iray [ERROR] - IRAY:RENDER ::   1.2   IRAY   rend error: CUDA device 0 (GeForce RTX 2080 Ti): an illegal memory access was encountered (while initializing memory buffer)2020-06-11 09:48:37.149 WARNING: ..\..\..\..\..\src\pluginsource\DzIrayRender\dzneuraymgr.cpp(353): Iray [ERROR] - IRAY:RENDER ::   1.2   IRAY   rend error: All workers failed: aborting render2020-06-11 09:48:37.157 WARNING: ..\..\..\..\..\src\pluginsource\DzIrayRender\dzneuraymgr.cpp(353): Iray [ERROR] - IRAY:RENDER ::   1.2   IRAY   rend error: CUDA device 0 (GeForce RTX 2080 Ti): an illegal memory access was encountered (while de-allocating memory)2020-06-11 09:48:37.157 WARNING: ..\..\..\..\..\src\pluginsource\DzIrayRender\dzneuraymgr.cpp(353): Iray [ERROR] - IRAY:RENDER ::   1.2   IRAY   rend error: CUDA device 0 (GeForce RTX 2080 Ti): an illegal memory access was encountered (while de-allocating memory)2020-06-11 09:48:37.159 WARNING: ..\..\..\..\..\src\pluginsource\DzIrayRender\dzneuraymgr.cpp(353): Iray [ERROR] - IRAY:RENDER ::   1.2   IRAY   rend error: CUDA device 0 (GeForce RTX 2080 Ti): an illegal memory access was encountered (while de-allocating memory)2020-06-11 09:48:37.159 WARNING: ..\..\..\..\..\src\pluginsource\DzIrayRender\dzneuraymgr.cpp(353): Iray [ERROR] - IRAY:RENDER ::   1.2   IRAY   rend error: CUDA device 0 (GeForce RTX 2080 Ti): an illegal memory access was encountered (while de-allocating memory)2020-06-11 09:48:37.167 WARNING: ..\..\..\..\..\src\pluginsource\DzIrayRender\dzneuraymgr.cpp(353): Iray [ERROR] - IRAY:RENDER ::   1.2   IRAY   rend error: CUDA device 0 (GeForce RTX 2080 Ti): an illegal memory access was encountered (while de-allocating memory)2020-06-11 09:48:37.167 WARNING: ..\..\..\..\..\src\pluginsource\DzIrayRender\dzneuraymgr.cpp(353): Iray [ERROR] - IRAY:RENDER ::   1.2   IRAY   rend error: CUDA device 0 (GeForce RTX 2080 Ti): an illegal memory access was encountered (while de-allocating memory)2020-06-11 09:48:37.167 WARNING: ..\..\..\..\..\src\pluginsource\DzIrayRender\dzneuraymgr.cpp(353): Iray [ERROR] - IRAY:RENDER ::   1.2   IRAY   rend error: CUDA device 0 (GeForce RTX 2080 Ti): an illegal memory access was encountered (while de-allocating memory)2020-06-11 09:48:37.167 WARNING: ..\..\..\..\..\src\pluginsource\DzIrayRender\dzneuraymgr.cpp(353): Iray [ERROR] - IRAY:RENDER ::   1.2   IRAY   rend error: CUDA device 0 (GeForce RTX 2080 Ti): an illegal memory access was encountered (while de-allocating memory)2020-06-11 09:48:37.177 WARNING: ..\..\..\..\..\src\pluginsource\DzIrayRender\dzneuraymgr.cpp(353): Iray [ERROR] - IRAY:RENDER ::   1.2   IRAY   rend error: CUDA device 0 (GeForce RTX 2080 Ti): an illegal memory access was encountered (while de-allocating memory)2020-06-11 09:48:37.177 WARNING: ..\..\..\..\..\src\pluginsource\DzIrayRender\dzneuraymgr.cpp(353): Iray [ERROR] - IRAY:RENDER ::   1.2   IRAY   rend error: CUDA device 0 (GeForce RTX 2080 Ti): an illegal memory access was encountered (while de-allocating memory)2020-06-11 09:48:37.177 Iray Render error: Internal rendering error.2020-06-11 09:48:37.227 Iray [INFO] - IRAY:RENDER ::   1.0   IRAY   rend info : Device statistics:2020-06-11 09:48:37.227 Iray [INFO] - IRAY:RENDER ::   1.0   IRAY   rend info : CUDA device 0 (GeForce RTX 2080 Ti): 	 784 iterations, 13.399s init, 1382.480s render2020-06-11 09:48:37.227 WARNING: ..\..\..\..\..\src\pluginsource\DzIrayRender\dzneuraymgr.cpp(353): Iray [ERROR] - IRAY:RENDER ::   1.0   IRAY   rend error: CUDA device 0 (GeForce RTX 2080 Ti): an illegal memory access was encountered (while de-allocating memory)2020-06-11 09:48:37.227 WARNING: ..\..\..\..\..\src\pluginsource\DzIrayRender\dzneuraymgr.cpp(353): Iray [ERROR] - IRAY:RENDER ::   1.0   IRAY   rend error: CUDA device 0 (GeForce RTX 2080 Ti): an illegal memory access was encountered (while de-allocating memory)2020-06-11 09:48:37.227 WARNING: ..\..\..\..\..\src\pluginsource\DzIrayRender\dzneuraymgr.cpp(353): Iray [ERROR] - IRAY:RENDER ::   1.0   IRAY   rend error: CUDA device 0 (GeForce RTX 2080 Ti): an illegal memory access was encountered (while de-allocating memory)2020-06-11 09:48:37.237 WARNING: ..\..\..\..\..\src\pluginsource\DzIrayRender\dzneuraymgr.cpp(353): Iray [ERROR] - IRAY:RENDER ::   1.0   IRAY   rend error: CUDA device 0 (GeForce RTX 2080 Ti): an illegal memory access was encountered (while de-allocating memory)2020-06-11 09:48:39.007 Saved image: C:\blabla.png2020-06-11 09:48:39.317 WARNING: ..\..\..\..\..\src\pluginsource\DzIrayRender\dzneuraymgr.cpp(353): Iray [ERROR] - IRAY:RENDER ::   1.14  IRAY   rend error: Error synching on OptixPipeline event (CUDA error string: an illegal memory access was encountered, CUDA error code: 700)2020-06-11 09:48:39.327 WARNING: ..\..\..\..\..\src\pluginsource\DzIrayRender\dzneuraymgr.cpp(353): Iray [ERROR] - IRAY:RENDER ::   1.14  IRAY   rend error: optixPipelineDestroy(pop_ptr(m_pipeline)) failed: CUDA error2020-06-11 09:48:39.327 WARNING: ..\..\..\..\..\src\pluginsource\DzIrayRender\dzneuraymgr.cpp(353): Iray [ERROR] - IRAY:RENDER ::   1.14  IRAY   rend error: Error synching on OptixPipeline event (CUDA error string: an illegal memory access was encountered, CUDA error code: 700)2020-06-11 09:48:39.327 WARNING: ..\..\..\..\..\src\pluginsource\DzIrayRender\dzneuraymgr.cpp(353): Iray [ERROR] - IRAY:RENDER ::   1.14  IRAY   rend error: optixPipelineDestroy(pop_ptr(m_pipeline)) failed: CUDA error2020-06-11 09:48:39.337 WARNING: ..\..\..\..\..\src\pluginsource\DzIrayRender\dzneuraymgr.cpp(353): Iray [ERROR] - IRAY:RENDER ::   1.14  IRAY   rend error: Error synching on OptixPipeline event (CUDA error string: an illegal memory access was encountered, CUDA error code: 700)2020-06-11 09:48:39.337 WARNING: ..\..\..\..\..\src\pluginsource\DzIrayRender\dzneuraymgr.cpp(353): Iray [ERROR] - IRAY:RENDER ::   1.14  IRAY   rend error: optixPipelineDestroy(pop_ptr(m_pipeline)) failed: CUDA error2020-06-11 09:48:39.337 WARNING: ..\..\..\..\..\src\pluginsource\DzIrayRender\dzneuraymgr.cpp(353): Iray [ERROR] - IRAY:RENDER ::   1.14  IRAY   rend error: Error synching on OptixPipeline event (CUDA error string: an illegal memory access was encountered, CUDA error code: 700)2020-06-11 09:48:39.337 WARNING: ..\..\..\..\..\src\pluginsource\DzIrayRender\dzneuraymgr.cpp(353): Iray [ERROR] - IRAY:RENDER ::   1.14  IRAY   rend error: optixPipelineDestroy(pop_ptr(m_pipeline)) failed: CUDA error2020-06-11 09:48:39.337 WARNING: ..\..\..\..\..\src\pluginsource\DzIrayRender\dzneuraymgr.cpp(353): Iray [ERROR] - IRAY:RENDER ::   1.14  IRAY   rend error: Error synching on OptixPipeline event (CUDA error string: an illegal memory access was encountered, CUDA error code: 700)2020-06-11 09:48:39.337 WARNING: ..\..\..\..\..\src\pluginsource\DzIrayRender\dzneuraymgr.cpp(353): Iray [ERROR] - IRAY:RENDER ::   1.14  IRAY   rend error: optixPipelineDestroy(pop_ptr(m_pipeline)) failed: CUDA error2020-06-11 09:48:39.347 WARNING: ..\..\..\..\..\src\pluginsource\DzIrayRender\dzneuraymgr.cpp(353): Iray [ERROR] - IRAY:RENDER ::   1.14  IRAY   rend error: Error synching on OptixPipeline event (CUDA error string: an illegal memory access was encountered, CUDA error code: 700)2020-06-11 09:48:39.347 WARNING: ..\..\..\..\..\src\pluginsource\DzIrayRender\dzneuraymgr.cpp(353): Iray [ERROR] - IRAY:RENDER ::   1.14  IRAY   rend error: optixPipelineDestroy(pop_ptr(m_pipeline)) failed: CUDA error2020-06-11 09:48:39.347 WARNING: ..\..\..\..\..\src\pluginsource\DzIrayRender\dzneuraymgr.cpp(353): Iray [ERROR] - IRAY:RENDER ::   1.14  IRAY   rend error: Error synching on OptixPipeline event (CUDA error string: an illegal memory access was encountered, CUDA error code: 700)2020-06-11 09:48:39.347 WARNING: ..\..\..\..\..\src\pluginsource\DzIrayRender\dzneuraymgr.cpp(353): Iray [ERROR] - IRAY:RENDER ::   1.14  IRAY   rend error: optixPipelineDestroy(pop_ptr(m_pipeline)) failed: CUDA error2020-06-11 09:48:39.347 WARNING: ..\..\..\..\..\src\pluginsource\DzIrayRender\dzneuraymgr.cpp(353): Iray [ERROR] - IRAY:RENDER ::   1.14  IRAY   rend error: Error synching on OptixPipeline event (CUDA error string: an illegal memory access was encountered, CUDA error code: 700)2020-06-11 09:48:39.347 WARNING: ..\..\..\..\..\src\pluginsource\DzIrayRender\dzneuraymgr.cpp(353): Iray [ERROR] - IRAY:RENDER ::   1.14  IRAY   rend error: optixPipelineDestroy(pop_ptr(m_pipeline)) failed: CUDA error2020-06-11 09:48:39.357 WARNING: ..\..\..\..\..\src\pluginsource\DzIrayRender\dzneuraymgr.cpp(353): Iray [ERROR] - IRAY:RENDER ::   1.14  IRAY   rend error: Error synching on OptixPipeline event (CUDA error string: an illegal memory access was encountered, CUDA error code: 700)2020-06-11 09:48:39.357 WARNING: ..\..\..\..\..\src\pluginsource\DzIrayRender\dzneuraymgr.cpp(353): Iray [ERROR] - IRAY:RENDER ::   1.14  IRAY   rend error: optixPipelineDestroy(pop_ptr(m_pipeline)) failed: CUDA error2020-06-11 09:48:39.357 WARNING: ..\..\..\..\..\src\pluginsource\DzIrayRender\dzneuraymgr.cpp(353): Iray [ERROR] - IRAY:RENDER ::   1.14  IRAY   rend error: Error synching on OptixPipeline event (CUDA error string: an illegal memory access was encountered, CUDA error code: 700)2020-06-11 09:48:39.362 WARNING: ..\..\..\..\..\src\pluginsource\DzIrayRender\dzneuraymgr.cpp(353): Iray [ERROR] - IRAY:RENDER ::   1.14  IRAY   rend error: optixPipelineDestroy(pop_ptr(m_pipeline)) failed: CUDA error2020-06-11 09:48:39.362 WARNING: ..\..\..\..\..\src\pluginsource\DzIrayRender\dzneuraymgr.cpp(353): Iray [ERROR] - IRAY:RENDER ::   1.14  IRAY   rend error: Error synching on OptixPipeline event (CUDA error string: an illegal memory access was encountered, CUDA error code: 700)2020-06-11 09:48:39.362 WARNING: ..\..\..\..\..\src\pluginsource\DzIrayRender\dzneuraymgr.cpp(353): Iray [ERROR] - IRAY:RENDER ::   1.14  IRAY   rend error: optixPipelineDestroy(pop_ptr(m_pipeline)) failed: CUDA error2020-06-11 09:48:39.367 WARNING: ..\..\..\..\..\src\pluginsource\DzIrayRender\dzneuraymgr.cpp(353): Iray [ERROR] - IRAY:RENDER ::   1.14  IRAY   rend error: Error synching on OptixPipeline event (CUDA error string: an illegal memory access was encountered, CUDA error code: 700)2020-06-11 09:48:39.367 WARNING: ..\..\..\..\..\src\pluginsource\DzIrayRender\dzneuraymgr.cpp(353): Iray [ERROR] - IRAY:RENDER ::   1.14  IRAY   rend error: optixPipelineDestroy(pop_ptr(m_pipeline)) failed: CUDA error2020-06-11 09:48:39.737 Finished Rendering2020-06-11 09:48:39.767 Total Rendering Time: 23 minutes 23.57 seconds

     

    txt
    txt
    daz error.txt
    11K
    Post edited by freedomforever984 on
  • nicsttnicstt Posts: 11,715

    Not read everything, but is the card able to use all the RAM you think it has - less what Windows steals of course.

    Use GPUz to see what RAM it's using. Do you have a faulty card?

  • nicstt said:

    Not read everything, but is the card able to use all the RAM you think it has - less what Windows steals of course.

    Use GPUz to see what RAM it's using. Do you have a faulty card?

    It doesn't matter how big te scene is, meaning, GPU-Z shows maxmum of 5gb VRAM used and it still fails.

    Let's say only one gen 3 model, few lights, no HDRI etc it just doesnt matter.

    I don't know if it's fauly. From the store they told me it's not and can't accept return.

    I ran: Furmark, Superposition Benchmark, Heaven Benchmark 4.0, 3DMark and another, i forget the name, and left them (when posible) to run for hours.

    Never had any kind of crashes or problems. It happens only in daz3d when rendering.

     

     

  • nicsttnicstt Posts: 11,715

    They told you it's not after testing?

    It's not necessarily how long you leave em running for, but how much RAM they use. If as an example, your card has faulty RAM, then you need to use the RAM to trigger said fault; are the tests using 5GB and definitely more, if that is where your issue may be developing when rendering?

     

    I'd be looking to confirm that the various testing software is actually using enough RAM; it that isn't possible, ask Daz (the company) for an earlier version of Studio. I tend to use Beta 4.12.1.76 if i do happen to render in Studio; you'll be able to roll back your drivers too perhaps.

  • freedomforever984freedomforever984 Posts: 25
    edited June 2020

    This is moment of render failed

    Capture111.JPG
    487 x 559 - 75K
    Post edited by freedomforever984 on
  • nicsttnicstt Posts: 11,715

    That's less than 4GB or RAM, the card is using.

    According to the log posted, it's an Optix error; do the varous softwares you are using use Optix in their tests?

    Have you raised the issue with Daz?

    Send them error logs.

    Ask for an older version.

    Have you tried changing Nvidia drivers (Note: I say change, meaning get the latest; if you have the latest then try the earliest you know will work and even perhaps later ones.)?

  • nicstt said:

    That's less than 4GB or RAM, the card is using.

    According to the log posted, it's an Optix error; do the varous softwares you are using use Optix in their tests?

    Have you raised the issue with Daz?

    Send them error logs.

    Ask for an older version.

    Have you tried changing Nvidia drivers (Note: I say change, meaning get the latest; if you have the latest then try the earliest you know will work and even perhaps later ones.)?

    I tried all the drivers from i think 418.something, both game ready and studio, here is some (attachment) i kept the installation on my pc (I dont even know why since none of them worked, i deleted most couse i needed hdd space)

    Right now im using the latest drivers. Becouse why not, you know? None before worked.

    I have few installtions of daz, and the same thing is happening on all the versions,

    I'm not sure if any of the benchmarks test Optix , but i will google this now and see if theres a test for that only.

    I didn't raise the issue with Daz, how can i do this?

    drivers.JPG
    717 x 162 - 45K
  • Richard HaseltineRichard Haseltine Posts: 102,291

    Only the last two are new enough for the version of Iray in DS 4.12.1.117.

  • Only the last two are new enough for the version of Iray in DS 4.12.1.117.

    Yea I know, but this is happening to me for a year now, and I tried many Daz3D versions 4.11+

  • nicsttnicstt Posts: 11,715
    edited June 2020
    nicstt said:

    That's less than 4GB or RAM, the card is using.

    According to the log posted, it's an Optix error; do the varous softwares you are using use Optix in their tests?

    Have you raised the issue with Daz?

    Send them error logs.

    Ask for an older version.

    Have you tried changing Nvidia drivers (Note: I say change, meaning get the latest; if you have the latest then try the earliest you know will work and even perhaps later ones.)?

    I tried all the drivers from i think 418.something, both game ready and studio, here is some (attachment) i kept the installation on my pc (I dont even know why since none of them worked, i deleted most couse i needed hdd space)

    Right now im using the latest drivers. Becouse why not, you know? None before worked.

    I have few installtions of daz, and the same thing is happening on all the versions,

    I'm not sure if any of the benchmarks test Optix , but i will google this now and see if theres a test for that only.

    I didn't raise the issue with Daz, how can i do this?

    Oh the website, you'll see Help; you can raise a ticket with them by going through Help.

     

    How many cards have you?

    If you have two 2080ti, then try with just one; swap to test both. If you haven't, do you have a friend that will loan you one? Failing that, is there another PC in your household you can use as a test?

    There are various test scenes available in Blender; it is possible to use CUDA or OptiX (see image).

    If you download them and the latest Blender, you don't need any real knowledge of Blender; double clicking the GPU scenes will open it and F12 will start the render. I don't know if they automatically use Optix if it's available.

    You can go to Edit > Preferences, then click on System as shown in the image. OptiX is an option and you can disable any cards ( I presume), so they don't use it. I tend to use CPU as it's quicker than my 980ti, which is why None is checked in the image. I do also use bother as Cycles does out of core rendering.

    You could try with and without; https://code.blender.org/2016/02/new-cycles-benchmark/

    I'm suggesting it as an option if there are no others available.

    Post edited by nicstt on
  • freedomforever984freedomforever984 Posts: 25
    edited June 2020
    nicstt said:
    How many cards have you

     I got 2080ti in this PC, and 1070ti in other (same thing happened with 1070ti on this pc, so it muse be a sofware issue

    nicstt said:

    If you have two 2080ti, then try with just one; swap to test both. If you haven't, do you have a friend that will loan you one? Failing that, is there another PC in your household you can use as a test?

    I can't borrow a 2080ti, and i can0t test it on second PC. I would have to switch the PSU, and its all over the case, cable megagment and such

    nicstt said:

    There are various test scenes available in Blender; it is possible to use CUDA or OptiX (see image).

    If you download them and the latest Blender, you don't need any real knowledge of Blender; double clicking the GPU scenes will open it and F12 will start the render. I don't know if they automatically use Optix if it's available.

    You can go to Edit > Preferences, then click on System as shown in the image. OptiX is an option and you can disable any cards ( I presume), so they don't use it. I tend to use CPU as it's quicker than my 980ti, which is why None is checked in the image. I do also use bother as Cycles does out of core rendering.

    You could try with and without; https://code.blender.org/2016/02/new-cycles-benchmark/

    I'm suggesting it as an option if there are no others available.

    I'm try this now, thank you

    PS: what image?

    Post edited by freedomforever984 on
Sign In or Register to comment.