Loading...
> >

RTX4090:an illegal memory access was encountered

leo_bearleo_bear Posts: 44
edited October 2023 in Technical Help (nuts n bolts)

Hello everyone, just wanted to share something I've been grappling with and see if anyone else has run into the same issue. I recently upgraded my GPU from a 2080ti to a 4090, expecting some serious improvement in rendering performance. However, something weird is happening.

Scenes that I had zero problems rendering with my old 2080ti are now failing to render with the new 4090.

Has anyone else experienced this? it's super frustrating. Any insights or advice would be awesome.

Ram:32gb

RTX4090 24gb vram

AMD Ryzen 9 3900X 12-Core Processor               3.80 GHz

Daz version: 4.21

Game ready driver:536.99 (Just roll back from the latest game/studio version because it got me bsod when I tried to render with the latest version.)

PSU:850w

 

 

 

 

Log:

2023-10-25 22:55:15.009 [WARNING] :: ..\..\..\..\..\src\pluginsource\DzIrayRender\dzneuraymgr.cpp(369): Iray [ERROR] - IRAY:RENDER ::   1.0   IRAY   rend error: CUDA device 0 (NVIDIA GeForce RTX 4090): an illegal memory access was encountered (while de-allocating memory)
2023-10-25 22:55:15.010 [WARNING] :: ..\..\..\..\..\src\pluginsource\DzIrayRender\dzneuraymgr.cpp(369): Iray [ERROR] - IRAY:RENDER ::   1.0   IRAY   rend error: CUDA device 0 (NVIDIA GeForce RTX 4090): an illegal memory access was encountered (while de-allocating memory)
2023-10-25 22:55:15.010 [WARNING] :: ..\..\..\..\..\src\pluginsource\DzIrayRender\dzneuraymgr.cpp(369): Iray [ERROR] - IRAY:RENDER ::   1.0   IRAY   rend error: CUDA device 0 (NVIDIA GeForce RTX 4090): an illegal memory access was encountered (while de-allocating memory)
2023-10-25 22:55:15.013 [WARNING] :: ..\..\..\..\..\src\pluginsource\DzIrayRender\dzneuraymgr.cpp(369): Iray [ERROR] - IRAY:RENDER ::   1.0   IRAY   rend error: CUDA device 0 (NVIDIA GeForce RTX 4090): an illegal memory access was encountered (while de-allocating memory)
2023-10-25 22:55:15.013 [WARNING] :: ..\..\..\..\..\src\pluginsource\DzIrayRender\dzneuraymgr.cpp(369): Iray [ERROR] - IRAY:RENDER ::   1.0   IRAY   rend error: CUDA device 0 (NVIDIA GeForce RTX 4090): an illegal memory access was encountered (while de-allocating memory)
2023-10-25 22:55:15.015 [WARNING] :: ..\..\..\..\..\src\pluginsource\DzIrayRender\dzneuraymgr.cpp(369): Iray [ERROR] - IRAY:RENDER ::   1.0   IRAY   rend error: CUDA device 0 (NVIDIA GeForce RTX 4090): an illegal memory access was encountered (while de-allocating memory)
2023-10-25 22:55:15.015 [WARNING] :: ..\..\..\..\..\src\pluginsource\DzIrayRender\dzneuraymgr.cpp(369): Iray [ERROR] - IRAY:RENDER ::   1.0   IRAY   rend error: CUDA device 0 (NVIDIA GeForce RTX 4090): an illegal memory access was encountered (while de-allocating memory)
2023-10-25 22:55:16.213 [WARNING] :: ..\..\..\..\..\src\pluginsource\DzIrayRender\dzneuraymgr.cpp(369): Iray [ERROR] - OPTX:RENDER ::   1.26  OPTX   rend error: Error synching on OptixPipeline event (CUDA error string: an illegal memory access was encountered, CUDA error code: 700)
2023-10-25 22:55:16.213 [WARNING] :: ..\..\..\..\..\src\pluginsource\DzIrayRender\dzneuraymgr.cpp(369): Iray [ERROR] - OPTX:RENDER ::   1.26  OPTX   rend error: Error destroying OptixPipeline event (CUDA error string: an illegal memory access was encountered, CUDA error code: 700)
2023-10-25 22:55:16.218 [WARNING] :: ..\..\..\..\..\src\pluginsource\DzIrayRender\dzneuraymgr.cpp(369): Iray [ERROR] - IRAY:RENDER ::   1.26  IRAY   rend error: optixPipelineDestroy(pop_ptr(m_pipeline)) failed: CUDA error
2023-10-25 22:55:16.218 [WARNING] :: ..\..\..\..\..\src\pluginsource\DzIrayRender\dzneuraymgr.cpp(369): Iray [ERROR] - OPTX:RENDER ::   1.26  OPTX   rend error: Error synching on OptixPipeline event (CUDA error string: an illegal memory access was encountered, CUDA error code: 700)
2023-10-25 22:55:16.218 [WARNING] :: ..\..\..\..\..\src\pluginsource\DzIrayRender\dzneuraymgr.cpp(369): Iray [ERROR] - OPTX:RENDER ::   1.26  OPTX   rend error: Error destroying OptixPipeline event (CUDA error string: an illegal memory access was encountered, CUDA error code: 700)
2023-10-25 22:55:16.219 [WARNING] :: ..\..\..\..\..\src\pluginsource\DzIrayRender\dzneuraymgr.cpp(369): Iray [ERROR] - IRAY:RENDER ::   1.26  IRAY   rend error: optixPipelineDestroy(pop_ptr(m_pipeline)) failed: CUDA error
2023-10-25 22:55:16.219 [WARNING] :: ..\..\..\..\..\src\pluginsource\DzIrayRender\dzneuraymgr.cpp(369): Iray [ERROR] - OPTX:RENDER ::   1.26  OPTX   rend error: Error synching on OptixPipeline event (CUDA error string: an illegal memory access was encountered, CUDA error code: 700)
2023-10-25 22:55:16.219 [WARNING] :: ..\..\..\..\..\src\pluginsource\DzIrayRender\dzneuraymgr.cpp(369): Iray [ERROR] - OPTX:RENDER ::   1.26  OPTX   rend error: Error destroying OptixPipeline event (CUDA error string: an illegal memory access was encountered, CUDA error code: 700)
2023-10-25 22:55:16.219 [WARNING] :: ..\..\..\..\..\src\pluginsource\DzIrayRender\dzneuraymgr.cpp(369): Iray [ERROR] - IRAY:RENDER ::   1.26  IRAY   rend error: optixPipelineDestroy(pop_ptr(m_pipeline)) failed: CUDA error
2023-10-25 22:55:16.220 [WARNING] :: ..\..\..\..\..\src\pluginsource\DzIrayRender\dzneuraymgr.cpp(369): Iray [ERROR] - OPTX:RENDER ::   1.26  OPTX   rend error: Error synching on OptixPipeline event (CUDA error string: an illegal memory access was encountered, CUDA error code: 700)
2023-10-25 22:55:16.220 [WARNING] :: ..\..\..\..\..\src\pluginsource\DzIrayRender\dzneuraymgr.cpp(369): Iray [ERROR] - OPTX:RENDER ::   1.26  OPTX   rend error: Error destroying OptixPipeline event (CUDA error string: an illegal memory access was encountered, CUDA error code: 700)
2023-10-25 22:55:16.221 [WARNING] :: ..\..\..\..\..\src\pluginsource\DzIrayRender\dzneuraymgr.cpp(369): Iray [ERROR] - IRAY:RENDER ::   1.26  IRAY   rend error: optixPipelineDestroy(pop_ptr(m_pipeline)) failed: CUDA error
2023-10-25 22:55:16.221 [WARNING] :: ..\..\..\..\..\src\pluginsource\DzIrayRender\dzneuraymgr.cpp(369): Iray [ERROR] - OPTX:RENDER ::   1.26  OPTX   rend error: Error synching on OptixPipeline event (CUDA error string: an illegal memory access was encountered, CUDA error code: 700)
2023-10-25 22:55:16.221 [WARNING] :: ..\..\..\..\..\src\pluginsource\DzIrayRender\dzneuraymgr.cpp(369): Iray [ERROR] - OPTX:RENDER ::   1.26  OPTX   rend error: Error destroying OptixPipeline event (CUDA error string: an illegal memory access was encountered, CUDA error code: 700)
2023-10-25 22:55:16.222 [WARNING] :: ..\..\..\..\..\src\pluginsource\DzIrayRender\dzneuraymgr.cpp(369): Iray [ERROR] - IRAY:RENDER ::   1.26  IRAY   rend error: optixPipelineDestroy(pop_ptr(m_pipeline)) failed: CUDA error
2023-10-25 22:55:16.222 [WARNING] :: ..\..\..\..\..\src\pluginsource\DzIrayRender\dzneuraymgr.cpp(369): Iray [ERROR] - OPTX:RENDER ::   1.26  OPTX   rend error: Error synching on OptixPipeline event (CUDA error string: an illegal memory access was encountered, CUDA error code: 700)
2023-10-25 22:55:16.222 [WARNING] :: ..\..\..\..\..\src\pluginsource\DzIrayRender\dzneuraymgr.cpp(369): Iray [ERROR] - OPTX:RENDER ::   1.26  OPTX   rend error: Error destroying OptixPipeline event (CUDA error string: an illegal memory access was encountered, CUDA error code: 700)
2023-10-25 22:55:16.223 [WARNING] :: ..\..\..\..\..\src\pluginsource\DzIrayRender\dzneuraymgr.cpp(369): Iray [ERROR] - IRAY:RENDER ::   1.26  IRAY   rend error: optixPipelineDestroy(pop_ptr(m_pipeline)) failed: CUDA error
2023-10-25 22:55:16.223 [WARNING] :: ..\..\..\..\..\src\pluginsource\DzIrayRender\dzneuraymgr.cpp(369): Iray [ERROR] - OPTX:RENDER ::   1.26  OPTX   rend error: Error synching on OptixPipeline event (CUDA error string: an illegal memory access was encountered, CUDA error code: 700)
2023-10-25 22:55:16.223 [WARNING] :: ..\..\..\..\..\src\pluginsource\DzIrayRender\dzneuraymgr.cpp(369): Iray [ERROR] - OPTX:RENDER ::   1.26  OPTX   rend error: Error destroying OptixPipeline event (CUDA error string: an illegal memory access was encountered, CUDA error code: 700)
2023-10-25 22:55:16.224 [WARNING] :: ..\..\..\..\..\src\pluginsource\DzIrayRender\dzneuraymgr.cpp(369): Iray [ERROR] - IRAY:RENDER ::   1.26  IRAY   rend error: optixPipelineDestroy(pop_ptr(m_pipeline)) failed: CUDA error
2023-10-25 22:55:16.225 [WARNING] :: ..\..\..\..\..\src\pluginsource\DzIrayRender\dzneuraymgr.cpp(369): Iray [ERROR] - OPTX:RENDER ::   1.26  OPTX   rend error: Error synching on OptixPipeline event (CUDA error string: an illegal memory access was encountered, CUDA error code: 700)
2023-10-25 22:55:16.225 [WARNING] :: ..\..\..\..\..\src\pluginsource\DzIrayRender\dzneuraymgr.cpp(369): Iray [ERROR] - OPTX:RENDER ::   1.26  OPTX   rend error: Error destroying OptixPipeline event (CUDA error string: an illegal memory access was encountered, CUDA error code: 700)
2023-10-25 22:55:16.225 [WARNING] :: ..\..\..\..\..\src\pluginsource\DzIrayRender\dzneuraymgr.cpp(369): Iray [ERROR] - IRAY:RENDER ::   1.26  IRAY   rend error: optixPipelineDestroy(pop_ptr(m_pipeline)) failed: CUDA error
2023-10-25 22:55:16.226 [WARNING] :: ..\..\..\..\..\src\pluginsource\DzIrayRender\dzneuraymgr.cpp(369): Iray [ERROR] - OPTX:RENDER ::   1.26  OPTX   rend error: Error synching on OptixPipeline event (CUDA error string: an illegal memory access was encountered, CUDA error code: 700)
2023-10-25 22:55:16.226 [WARNING] :: ..\..\..\..\..\src\pluginsource\DzIrayRender\dzneuraymgr.cpp(369): Iray [ERROR] - OPTX:RENDER ::   1.26  OPTX   rend error: Error destroying OptixPipeline event (CUDA error string: an illegal memory access was encountered, CUDA error code: 700)
2023-10-25 22:55:16.226 [WARNING] :: ..\..\..\..\..\src\pluginsource\DzIrayRender\dzneuraymgr.cpp(369): Iray [ERROR] - IRAY:RENDER ::   1.26  IRAY   rend error: optixPipelineDestroy(pop_ptr(m_pipeline)) failed: CUDA error
2023-10-25 22:55:16.227 [WARNING] :: ..\..\..\..\..\src\pluginsource\DzIrayRender\dzneuraymgr.cpp(369): Iray [ERROR] - OPTX:RENDER ::   1.26  OPTX   rend error: Error synching on OptixPipeline event (CUDA error string: an illegal memory access was encountered, CUDA error code: 700)
2023-10-25 22:55:16.227 [WARNING] :: ..\..\..\..\..\src\pluginsource\DzIrayRender\dzneuraymgr.cpp(369): Iray [ERROR] - OPTX:RENDER ::   1.26  OPTX   rend error: Error destroying OptixPipeline event (CUDA error string: an illegal memory access was encountered, CUDA error code: 700)
2023-10-25 22:55:16.228 [WARNING] :: ..\..\..\..\..\src\pluginsource\DzIrayRender\dzneuraymgr.cpp(369): Iray [ERROR] - IRAY:RENDER ::   1.26  IRAY   rend error: optixPipelineDestroy(pop_ptr(m_pipeline)) failed: CUDA error
2023-10-25 22:55:16.228 [WARNING] :: ..\..\..\..\..\src\pluginsource\DzIrayRender\dzneuraymgr.cpp(369): Iray [ERROR] - OPTX:RENDER ::   1.26  OPTX   rend error: Error synching on OptixPipeline event (CUDA error string: an illegal memory access was encountered, CUDA error code: 700)
2023-10-25 22:55:16.228 [WARNING] :: ..\..\..\..\..\src\pluginsource\DzIrayRender\dzneuraymgr.cpp(369): Iray [ERROR] - OPTX:RENDER ::   1.26  OPTX   rend error: Error destroying OptixPipeline event (CUDA error string: an illegal memory access was encountered, CUDA error code: 700)
2023-10-25 22:55:16.229 [WARNING] :: ..\..\..\..\..\src\pluginsource\DzIrayRender\dzneuraymgr.cpp(369): Iray [ERROR] - IRAY:RENDER ::   1.26  IRAY   rend error: optixPipelineDestroy(pop_ptr(m_pipeline)) failed: CUDA error
2023-10-25 22:55:16.229 [WARNING] :: ..\..\..\..\..\src\pluginsource\DzIrayRender\dzneuraymgr.cpp(369): Iray [ERROR] - OPTX:RENDER ::   1.26  OPTX   rend error: Error synching on OptixPipeline event (CUDA error string: an illegal memory access was encountered, CUDA error code: 700)
2023-10-25 22:55:16.229 [WARNING] :: ..\..\..\..\..\src\pluginsource\DzIrayRender\dzneuraymgr.cpp(369): Iray [ERROR] - OPTX:RENDER ::   1.26  OPTX   rend error: Error destroying OptixPipeline event (CUDA error string: an illegal memory access was encountered, CUDA error code: 700)
2023-10-25 22:55:16.230 [WARNING] :: ..\..\..\..\..\src\pluginsource\DzIrayRender\dzneuraymgr.cpp(369): Iray [ERROR] - IRAY:RENDER ::   1.26  IRAY   rend error: optixPipelineDestroy(pop_ptr(m_pipeline)) failed: CUDA error

Post edited by leo_bear on

Comments

  • crosswindcrosswind Posts: 6,943
    edited October 2023

    Did you monitor the vram usage with GPU-Z or Task Manager or sth. ? Could you remember the module or error code from BSOD?

    Pls see if the vram usage is normal or not. And there is chance to first use DDU to 100% uninstall the card driver and residuals, then install a fresh Studio driver, to eliminate BSOD...

    Post edited by crosswind on
  • leo_bearleo_bear Posts: 44
    edited October 2023

    crosswind said:

    Did you monitor the vram usage with GPU-Z or Task Manager or sth. ? Could you remember the module or error code from BSOD?

    Pls see if the vram usage is normal or not. And there is chance to first use DDU to 100% uninstall the card driver and residuals, then install a fresh Studio driver, to eliminate BSOD...

    Before I roll back the driver version, I tried both latest game and studio driver, both gave me BSOD when I tried to render or Iray preview the scene.When I rolled back to the game driver I mentioned aboved, it just gave me a black render, did not used GPU at all.(CPU fallback disabled)
    BSOD stop code: DPC_WATCHDOG_VIOLATION
    Here's one of the dmp file:

    Screenshot - 2023-10-26 01.28.23.png
    491 x 697 - 18K
    Post edited by leo_bear on
  • crosswindcrosswind Posts: 6,943

    Oh... I don't think your scene consumed nearly 24GB VRAM but usally with CPU fallback disabled, a black render results from running out of VRAM. However your DS log shows a failure of de-allocating memory which is wierd. Post the full log if possible.

    As for - DPC_WATCHDOG_VIOLATION, I strongly recommend using DDU to uninstall your driver first and re-install the latest Studio driver. DDU ever helped me twice to resolve BSOD, once is nvlddmkm.sys error, once is DPC_WATCHDOG_VIOLATION.

    https://www.wagnardsoft.com/, click DDU latest version.

    BTW, what's the power of you PSU？

  • PerttiAPerttiA Posts: 10,024

    Strange things have also been happening if one has installed Iray development packages etc. from nVidia, as they have installed different (not compatible with ones DS uses) versions of nVidia related files.

  • leo_bearleo_bear Posts: 44
    edited October 2023

    crosswind said:

    Oh... I don't think your scene consumed nearly 24GB VRAM but usally with CPU fallback disabled, a black render results from running out of VRAM. However your DS log shows a failure of de-allocating memory which is wierd. Post the full log if possible.

    As for - DPC_WATCHDOG_VIOLATION, I strongly recommend using DDU to uninstall your driver first and re-install the latest Studio driver. DDU ever helped me twice to resolve BSOD, once is nvlddmkm.sys error, once is DPC_WATCHDOG_VIOLATION.

    https://www.wagnardsoft.com/, click DDU latest version.

    BTW, what's the power of you PSU？

    850w

    Complete unsinall and reinstall to the latest game driver this morning. Just try to rendered and yea no more BSOD. But the gpu problem is still there. Here's a complete log hre, I deleted lines that were loading images to save you some time.

    The weird thing is, the scene rendered with gpu for about 91 iterations then refuse to use GPU.
     

    txt
    txt
    log2.txt
    29K
    Post edited by leo_bear on
  • leo_bearleo_bear Posts: 44

    PerttiA said:

    Strange things have also been happening if one has installed Iray development packages etc. from nVidia, as they have installed different (not compatible with ones DS uses) versions of nVidia related files.

     I don't think I installed any devdelopment packages from NVIDIA, it is really weird

  • leo_bearleo_bear Posts: 44

    In the same scene, after gpu render failed. The iray preview failed as well, heres the log for the preview:

    2023-10-26 11:32:37.008 Iray [INFO] - IRAY:RENDER ::   1.0   IRAY   rend info : Updating geometry.
    2023-10-26 11:32:37.008 Iray [INFO] - IRAY:RENDER ::   1.0   IRAY   rend info : Updating motion transforms.
    2023-10-26 11:32:37.008 Iray [INFO] - IRAY:RENDER ::   1.0   IRAY   rend info : Importing scene graph.
    2023-10-26 11:32:37.158 [WARNING] :: ..\..\..\..\..\src\pluginsource\DzIrayRender\dzneuraymgr.cpp(369): Iray [WARNING] - TRIT:GEOMETRY ::   1.0   TRIT   geo  warn : Object DS_shape_219c_7141: the parametric approximation level is set to 4. The original value of 5 would produce too much geometry in a single mesh.
    2023-10-26 11:32:39.154 [WARNING] :: ..\..\..\..\..\src\pluginsource\DzIrayRender\dzneuraymgr.cpp(369): Iray [WARNING] - TRIT:GEOMETRY ::   1.0   TRIT   geo  warn : Object DS_shape_252b_8948: the parametric approximation level is set to 2. The original value of 3 would produce too much geometry in a single mesh.
    2023-10-26 11:32:41.334 [WARNING] :: ..\..\..\..\..\src\pluginsource\DzIrayRender\dzneuraymgr.cpp(369): Iray [WARNING] - TRIT:GEOMETRY ::   1.0   TRIT   geo  warn : Object DS_shape_25b2_9080: the parametric approximation level is set to 3. The original value of 4 would produce too much geometry in a single mesh.
    2023-10-26 11:32:43.488 Iray [INFO] - IRAY:RENDER ::   1.0   IRAY   rend info : Auto instancing compression ratio 1.00 (Full instancing compression ratio 1.00)
    2023-10-26 11:32:43.488 Iray [INFO] - IRAY:RENDER ::   1.0   IRAY   rend info : Importing geometry for motion time 0
    2023-10-26 11:32:44.566 Iray [INFO] - IRAY:RENDER ::   1.0   IRAY   rend info : Geometry import (1 triangle object with 38 M triangles, 0 fiber objects with 0 fibers (0 segments), 1 triangle instance yielding 38 M triangles, 0 fiber instances yielding 0 segments) took 1.078 s
    2023-10-26 11:32:44.566 Iray [INFO] - IRAY:RENDER ::   1.0   IRAY   rend info : Updating section objects.
    2023-10-26 11:32:44.566 Iray [INFO] - IRAY:RENDER ::   1.0   IRAY   rend info : Updating materials.
    2023-10-26 11:32:44.826 Iray [INFO] - MATCNV:RENDER ::   1.0   MATCNV rend info : found 782 textures, 0 lambdas (0 unique)
    2023-10-26 11:32:44.841 Iray [INFO] - IRAY:RENDER ::   1.0   IRAY   rend info : Emitter geometry import (11 light sources with 99271 triangles, 1 instance) took 0.003 s
    2023-10-26 11:32:44.841 Iray [INFO] - IRAY:RENDER ::   1.0   IRAY   rend info : Updating volumes.
    2023-10-26 11:32:44.841 Iray [INFO] - IRAY:RENDER ::   1.0   IRAY   rend info : Updating environment.
    2023-10-26 11:32:45.672 Iray [INFO] - IRAY:RENDER ::   1.0   IRAY   rend info : Updating lens.
    2023-10-26 11:32:45.672 Iray [INFO] - IRAY:RENDER ::   1.0   IRAY   rend info : Updating lights.
    2023-10-26 11:32:45.673 Iray [INFO] - IRAY:RENDER ::   1.0   IRAY   rend info : Updating object flags.
    2023-10-26 11:32:45.673 Iray [INFO] - IRAY:RENDER ::   1.0   IRAY   rend info : Updating backplate.
    2023-10-26 11:32:45.673 Iray [INFO] - IRAY:RENDER ::   1.0   IRAY   rend info : Updating caustic portals.
    2023-10-26 11:32:45.673 Iray [INFO] - IRAY:RENDER ::   1.0   IRAY   rend info : Updating decals.
    2023-10-26 11:32:45.676 Iray [INFO] - IRAY:RENDER ::   1.0   IRAY   rend info : Using iray core convergence estimate.
    2023-10-26 11:32:45.676 Iray [INFO] - IRAY:RENDER ::   1.0   IRAY   rend info : Allocating 1-layer frame buffer
    2023-10-26 11:32:45.678 Iray [INFO] - IRAY:RENDER ::   1.0   IRAY   rend info : Using interactive scheduling, caustic sampler disabled
    2023-10-26 11:32:45.678 Iray [INFO] - IRAY:RENDER ::   1.0   IRAY   rend info : Initializing local rendering.
    2023-10-26 11:32:45.678 [WARNING] :: ..\..\..\..\..\src\pluginsource\DzIrayRender\dzneuraymgr.cpp(369): Iray [ERROR] - IRAY:RENDER ::   1.0   IRAY   rend error: No device specified or usable
    2023-10-26 11:32:45.679 Iray [INFO] - IRAY:RENDER ::   1.0   IRAY   rend info : Rendering with 0 device(s):
    2023-10-26 11:32:45.679 Iray [INFO] - IRAY:RENDER ::   1.0   IRAY   rend info : Rendering...
    2023-10-26 11:32:45.679 [WARNING] :: ..\..\..\..\..\src\pluginsource\DzIrayRender\dzneuraymgr.cpp(369): Iray [ERROR] - IRAY:RENDER ::   1.0   IRAY   rend error: No worker to render with: aborting render
    2023-10-26 11:32:45.679 [ERROR] Iray :: Internal rendering error.

     

  • Richard HaseltineRichard Haseltine Posts: 100,804

    Yes, if the GPU fails to render it is usually necessary to restart DS to free it up.

  • crosswindcrosswind Posts: 6,943
    edited October 2023

    It's a good news that BSOD is gone. Then after checking your full log attached, still suggest as below -:

    0. Uninstall Optix 7.3 SDK ! (If everything's ok after testing, and you DO need SDK, install the latest 8.0 version and re-test.)
    1. Install GPU-Z to monitor your 4090 performance esp. VRAM used and GPU Load (as attached).  Observe GPU-Z panel the moment you click Render or press Ctrl + R. Pay attention to the value change of 'Memory Used'.
    2. Use a Studio Driver rather than Game Ready Driver.

    Then let's see...

     

    SNAG-2023-10-27-0016.png
    540 x 947 - 70K
    Post edited by crosswind on
  • leo_bearleo_bear Posts: 44
    edited October 2023

    crosswind said:

    It's a good news that BSOD is gone. Then after checking your full log attached, still suggest as below -:

    0. Uninstall Optix 7.3 SDK ! (If everything's ok after testing, and you DO need SDK, install the latest 8.0 version and re-test.)
    1. Install GPU-Z to monitor your 4090 performance esp. VRAM used and GPU Load (as attached).  Observe GPU-Z panel the moment you click Render or press Ctrl + R. Pay attention to the value change of 'Memory Used'.
    2. Use a Studio Driver rather than Game Ready Driver.

    Then let's see...

     

    • Switched to studio driver
    • GPU-Z checked, no issue with empty scene.
    • Upgraded to Optix 8.0 SDK(I don't really know how to uninstall)

    The scene successfully rendered up to about 800 iterations before refusing to use the GPU and aborting the render. Compared to before, when it rendered only 0-90 iterations before aborting, this is a slight improvement but still doesn't fix the issue. The log is still the same.

    There is an screenshot of GPU-Z during rendering, before it refuse to use gpu.

    --------------------------------------------------------------

    2023-10-27 18:05:27.125 Iray [INFO] - IRAY:RENDER ::   1.0   IRAY   rend progr: Received update to 00848 iterations after 222.741s.
    2023-10-27 18:05:46.634 [WARNING] :: ..\..\..\..\..\src\pluginsource\DzIrayRender\dzneuraymgr.cpp(369): Iray [ERROR] - IRAY:RENDER ::   1.6   IRAY   rend error: CUDA device 0 (NVIDIA GeForce RTX 4090): Kernel [8] (ShadowEvalSr      ) failed after 0.009s
    2023-10-27 18:05:46.649 [WARNING] :: ..\..\..\..\..\src\pluginsource\DzIrayRender\dzneuraymgr.cpp(369): Iray [ERROR] - IRAY:RENDER ::   1.6   IRAY   rend error: CUDA device 0 (NVIDIA GeForce RTX 4090): an illegal memory access was encountered (while launching CUDA renderer in <internal>:951)
    2023-10-27 18:05:46.650 [WARNING] :: ..\..\..\..\..\src\pluginsource\DzIrayRender\dzneuraymgr.cpp(369): Iray [ERROR] - IRAY:RENDER ::   1.6   IRAY   rend error: CUDA device 0 (NVIDIA GeForce RTX 4090): Failed to launch renderer
    2023-10-27 18:05:46.662 [WARNING] :: ..\..\..\..\..\src\pluginsource\DzIrayRender\dzneuraymgr.cpp(369): Iray [ERROR] - IRAY:RENDER ::   1.17  IRAY   rend error: CUDA device 0 (NVIDIA GeForce RTX 4090): Device failed while rendering
    2023-10-27 18:05:46.700 [WARNING] :: ..\..\..\..\..\src\pluginsource\DzIrayRender\dzneuraymgr.cpp(369): Iray [WARNING] - IRAY:RENDER ::   1.17  IRAY   rend warn : CUDA device 0 (NVIDIA GeForce RTX 4090) is no longer available for rendering.
    2023-10-27 18:05:46.712 [WARNING] :: ..\..\..\..\..\src\pluginsource\DzIrayRender\dzneuraymgr.cpp(369): Iray [WARNING] - IRAY:RENDER ::   1.17  IRAY   rend warn : All available GPUs failed.
    2023-10-27 18:05:46.714 [WARNING] :: ..\..\..\..\..\src\pluginsource\DzIrayRender\dzneuraymgr.cpp(369): Iray [ERROR] - IRAY:RENDER ::   1.17  IRAY   rend error: Fallback to CPU not allowed.
    2023-10-27 18:05:46.715 [WARNING] :: ..\..\..\..\..\src\pluginsource\DzIrayRender\dzneuraymgr.cpp(369): Iray [ERROR] - IRAY:RENDER ::   1.17  IRAY   rend error: CUDA device 0 (NVIDIA GeForce RTX 4090): an illegal memory access was encountered (while initializing memory buffer)
    2023-10-27 18:05:46.717 [WARNING] :: ..\..\..\..\..\src\pluginsource\DzIrayRender\dzneuraymgr.cpp(369): Iray [ERROR] - IRAY:RENDER ::   1.17  IRAY   rend error: All workers failed: aborting render
    2023-10-27 18:05:46.717 [WARNING] :: ..\..\..\..\..\src\pluginsource\DzIrayRender\dzneuraymgr.cpp(369): Iray [ERROR] - IRAY:RENDER ::   1.17  IRAY   rend error: CUDA device 0 (NVIDIA GeForce RTX 4090): [Guidance sync] Failed slave device (remaining 0, done 0).
    2023-10-27 18:05:46.718 [WARNING] :: ..\..\..\..\..\src\pluginsource\DzIrayRender\dzneuraymgr.cpp(369): Iray [ERROR] - IRAY:RENDER ::   1.17  IRAY   rend error: CUDA device 0 (NVIDIA GeForce RTX 4090): an illegal memory access was encountered (while de-allocating memory)
    2023-10-27 18:05:46.720 [WARNING] :: ..\..\..\..\..\src\pluginsource\DzIrayRender\dzneuraymgr.cpp(369): Iray [ERROR] - IRAY:RENDER ::   1.17  IRAY   rend error: CUDA device 0 (NVIDIA GeForce RTX 4090): an illegal memory access was encountered (while de-allocating memory)
    2023-10-27 18:05:46.720 [WARNING] :: ..\..\..\..\..\src\pluginsource\DzIrayRender\dzneuraymgr.cpp(369): Iray [ERROR] - IRAY:RENDER ::   1.17  IRAY   rend error: CUDA device 0 (NVIDIA GeForce RTX 4090): an illegal memory access was encountered (while de-allocating memory)
    2023-10-27 18:05:46.720 [WARNING] :: ..\..\..\..\..\src\pluginsource\DzIrayRender\dzneuraymgr.cpp(369): Iray [ERROR] - IRAY:RENDER ::   1.17  IRAY   rend error: CUDA device 0 (NVIDIA GeForce RTX 4090): an illegal memory access was encountered (while de-allocating memory)
    2023-10-27 18:05:46.720 [WARNING] :: ..\..\..\..\..\src\pluginsource\DzIrayRender\dzneuraymgr.cpp(369): Iray [ERROR] - IRAY:RENDER ::   1.17  IRAY   rend error: CUDA device 0 (NVIDIA GeForce RTX 4090): an illegal memory access was encountered (while de-allocating memory)
    2023-10-27 18:05:46.721 [WARNING] :: ..\..\..\..\..\src\pluginsource\DzIrayRender\dzneuraymgr.cpp(369): Iray [ERROR] - IRAY:RENDER ::   1.17  IRAY   rend error: CUDA device 0 (NVIDIA GeForce RTX 4090): an illegal memory access was encountered (while de-allocating memory)
    2023-10-27 18:05:46.721 [WARNING] :: ..\..\..\..\..\src\pluginsource\DzIrayRender\dzneuraymgr.cpp(369): Iray [ERROR] - IRAY:RENDER ::   1.17  IRAY   rend error: CUDA device 0 (NVIDIA GeForce RTX 4090): an illegal memory access was encountered (while de-allocating memory)
    2023-10-27 18:05:46.721 [WARNING] :: ..\..\..\..\..\src\pluginsource\DzIrayRender\dzneuraymgr.cpp(369): Iray [ERROR] - IRAY:RENDER ::   1.17  IRAY   rend error: CUDA device 0 (NVIDIA GeForce RTX 4090): an illegal memory access was encountered (while de-allocating memory)
    2023-10-27 18:05:46.721 [WARNING] :: ..\..\..\..\..\src\pluginsource\DzIrayRender\dzneuraymgr.cpp(369): Iray [ERROR] - IRAY:RENDER ::   1.17  IRAY   rend error: CUDA device 0 (NVIDIA GeForce RTX 4090): an illegal memory access was encountered (while de-allocating memory)
    2023-10-27 18:05:46.721 [WARNING] :: ..\..\..\..\..\src\pluginsource\DzIrayRender\dzneuraymgr.cpp(369): Iray [ERROR] - IRAY:RENDER ::   1.17  IRAY   rend error: CUDA device 0 (NVIDIA GeForce RTX 4090): an illegal memory access was encountered (while de-allocating memory)
    2023-10-27 18:05:46.722 [ERROR] Iray :: Internal rendering error.
    2023-10-27 18:05:49.226 [INFO] :: Saved image: C:\Users\FFT\AppData\Roaming\DAZ 3D\Studio4\temp\render\r.png
    2023-10-27 18:05:49.275 [INFO] :: Finished Rendering
    2023-10-27 18:05:50.162 [INFO] :: Total Rendering Time: 4 minutes 47.61 seconds
    2023-10-27 18:06:04.297 [INFO] :: Saved image: E:\daz3d\output\0.82.png

     

    Screenshot - 2023-10-27 18.03.24.png
    388 x 940 - 41K
    Post edited by leo_bear on
  • crosswindcrosswind Posts: 6,943

    Hmm, it's progressive though it's a tough problem...and what was shown in GPU-Z looks normal. But the error last time is Kernel [19] ( MaterialSurface ), this time it's Kernel [8] ( ShadowEvalSr )...

    Again, you must try a couple of tests without Optix SDK !  Just go to Control Panel - Programs and Features. Locate or search Optix in the upper right corner. Uninstall it and reboot your PC.

    Initiate a new test. While the rendering reaches in b/t 800 - 900 iterations, pls carefully monitor the panel of GPU-Z, first see if the data in Memory Used suddenly jumps to a high value, 2nd, if GPU Load suddenly drops down...

    Then let's see...

  • leo_bearleo_bear Posts: 44

    crosswind said:

    Hmm, it's progressive though it's a tough problem...and what was shown in GPU-Z looks normal. But the error last time is Kernel [19] ( MaterialSurface ), this time it's Kernel [8] ( ShadowEvalSr )...

    Again, you must try a couple of tests without Optix SDK !  Just go to Control Panel - Programs and Features. Locate or search Optix in the upper right corner. Uninstall it and reboot your PC.

    Initiate a new test. While the rendering reaches in b/t 800 - 900 iterations, pls carefully monitor the panel of GPU-Z, first see if the data in Memory Used suddenly jumps to a high value, 2nd, if GPU Load suddenly drops down...

    Then let's see...

    Hmmm.. Did a few tests:

    • Before unintalling optix8.0, rendered 80 iterations before aborting renders
    • After uninstalling optix8.0, rendered gave me BSOD
    • Reinstalling optix8.0, rendered 2 iterations,  (Kernel [19] (MaterialSurface) )

    It seemed like the one time I had 800 iterations was just pure luck; it's kind of random. The memory usage was stable, and the GPU usage dropped once the render was aborted. The other lines are the same old "an illegal memory access was encountered (while de-allocating memory)"

  • crosswindcrosswind Posts: 6,943
    edited October 2023

    Well, seems like a mojo...

    That's why I never touch SDK... but I just suggest you a last try :

    1) carefully check if you have installed other Nvidia SDK, whatever they're , uninstall them all.

    2) you have to again, use DDU to uninstall everything and clean residuals, then install a fresh new driver. Then test. If the issue still sustains... options: contact the reseller for support, or test the card on other PC, etc.

    Post edited by crosswind on
  • leo_bearleo_bear Posts: 44
    edited October 2023

    crosswind said:

    Well, seems like a mojo...

    That's why I never touch SDK... but I just suggest you a last try :

    1) carefully check if you have installed other Nvidia SDK, whatever they're , uninstall them all.

    2) you have to again, use DDU to uninstall everything and clean residuals, then install a fresh new driver. Then test. If the issue still sustains... options: contact the reseller for support, or test the card on other PC, etc.

    I just 

    • Seem to be the issue with my current ram, I upgraded them to 128gb.
    • Returned the card and switched to a differnt brand.

    And these actions seemed to fix the problem, the scene can render perfectly without aborting renders. I don't know if it have to do with the graphic card, but yea having larger ram seem to have a fix on the problem.

    Post edited by leo_bear on
  • crosswindcrosswind Posts: 6,943
    edited October 2023

    I don't think it was RAM issue but most likely graphics card issue, as after the scene is fed in VRAM, there'll be nothing to do with RAM...

    Post edited by crosswind on
  • anders869anders869 Posts: 7

    i have the same issue here

    i have an AMD GPU and a Ryzen 7 CPU

    memory explode with 2+ characters on render and crashes, with one char and nothing more, still usable.

    my guess is a problem with the configuration of AMD CPUs

  • extraneuxextraneux Posts: 17

    I found this thread from google and thought I'd chime in even though it's old. I had the same issue with a 4090 laptop edtion, 16GB of vram, lenovo legion pro 7, 33GB of system ram. The workaround I found was to reduce the GPU cTGP setting to 125W. This can be found in the Lenovo Vantage app under Thermal Mode -> Performance. I used to get the illegal memory access after about 30 minutes of rending and now I've let it go for an over an hour and have yet to get the error. As others have noted, it doesn't seem to matter how much vram is used as long as it's less than the total vram available to the gpu.

Sign In or Register to comment.