Optix Denoiser CUDA_ERROR_ILLEGAL_ADDRESS in cuStreamSynchronize #79996

Closed
opened 2020-08-21 21:54:56 +02:00 by Brhaka · 97 comments

System Information
Operating system: Windows-10-10.0.19041-SP0 64 Bits
Graphics card: GeForce RTX 2080 Ti/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 452.06
Intel CPU

Blender Version
Broken: version: 2.90.0 Beta, branch: master, commit date: 2020-08-20 15:47, hash: 05e1ccf108
Worked: 2.83.5

Short description of error
This errors are appearing sometimes on viewport and when rendering. I'm using Cycles with experimental features and denoising on, but even after disabling them the problem persisted.
I'm using OptiX as the Cycles Render Device.

These are two messages from that error:

CUDA_ERROR_ILLEGAL_ADDRESS in cuStreamSynchronize(cuda_stream[thread_index]) (device_optix.cpp:1090)
Failed to create CUDA context (Illegal address)

Exact steps for others to reproduce the error
I can't write any steps to reproduce since it happens "randomly". I did some tests, but unfortunately I couldn't find any patterns.

**System Information** Operating system: Windows-10-10.0.19041-SP0 64 Bits Graphics card: GeForce RTX 2080 Ti/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 452.06 Intel CPU **Blender Version** Broken: version: 2.90.0 Beta, branch: master, commit date: 2020-08-20 15:47, hash: `05e1ccf108` Worked: 2.83.5 **Short description of error** This errors are appearing sometimes on viewport and when rendering. I'm using Cycles with experimental features and denoising on, but even after disabling them the problem persisted. I'm using OptiX as the Cycles Render Device. These are two messages from that error: CUDA_ERROR_ILLEGAL_ADDRESS in cuStreamSynchronize(cuda_stream[thread_index]) (device_optix.cpp:1090) Failed to create CUDA context (Illegal address) **Exact steps for others to reproduce the error** I can't write any steps to reproduce since it happens "randomly". I did some tests, but unfortunately I couldn't find any patterns.
Author

Added subscriber: @Brhaka

Added subscriber: @Brhaka

#86864 was marked as duplicate of this issue

#86864 was marked as duplicate of this issue

#84933 was marked as duplicate of this issue

#84933 was marked as duplicate of this issue

Added subscriber: @StephenSwaney

Added subscriber: @StephenSwaney

I'm seeing a bunch of similar errors (Illegal Address, Misaligned Address) with Linux Nvidia 1660 and Nvidia 450.57 driver.

Mostly when rendering smoke & fire. Very random, but seems to eventually happen.

I'm seeing a bunch of similar errors (Illegal Address, Misaligned Address) with Linux Nvidia 1660 and Nvidia 450.57 driver. Mostly when rendering smoke & fire. Very random, but seems to eventually happen.
Author

@StephenSwaney
That's correct. This bug was happening eventually, but I added objects with volume scatter to the scene and it is now occurring more frequently.

@StephenSwaney That's correct. This bug was happening eventually, but I added objects with volume scatter to the scene and it is now occurring more frequently.

Added subscriber: @blenderhilfe

Added subscriber: @blenderhilfe

i am getting kind of the the same error >>> Failed to create CUDA context (Illegal address)
if i switch from CPU to GPU with optix-denoiser enabled
on CPU it works

i render only the default scene!

geforce970 newest driver
blender 2.90 build 23.8.2020

copy from the console:
OPTIX_ERROR_CUDA_ERROR in optixDenoiserComputeMemoryResources(denoiser, rect_size.x, rect_size.y, &sizes) (device_optix.cpp:925)

Illegal address in cuMemFree(mem.device_pointer) (device_cuda_impl.cpp:964)
Illegal address in cuCtxSynchronize() (device_cuda_impl.cpp:2425)

i am getting kind of the the same error >>> Failed to create CUDA context (Illegal address) if i switch from CPU to **GPU with optix-denoiser** enabled on CPU it works i render only the default scene! geforce970 newest driver blender 2.90 build 23.8.2020 **copy from the console:** OPTIX_ERROR_CUDA_ERROR in optixDenoiserComputeMemoryResources(denoiser, rect_size.x, rect_size.y, &sizes) (device_optix.cpp:925) Illegal address in cuMemFree(mem.device_pointer) (device_cuda_impl.cpp:964) Illegal address in cuCtxSynchronize() (device_cuda_impl.cpp:2425)

Added subscriber: @MikeCastroFilms

Added subscriber: @MikeCastroFilms

I'm experiencing this issue now as well. "Failed to create CUDA context (illegal address)".

GeForce RTX 2070
i7-10750H CPU @ 2.60GHz
Windows 10 64-bit OS
Blender 2.90 build 31.8.2020

Trying to render an image from camera projection on geometry with subdivisions. Only works with CPU, unable to render anything with the GPU without the above error.

I'm experiencing this issue now as well. "Failed to create CUDA context (illegal address)". GeForce RTX 2070 i7-10750H CPU @ 2.60GHz Windows 10 64-bit OS Blender 2.90 build 31.8.2020 Trying to render an image from camera projection on geometry with subdivisions. Only works with CPU, unable to render anything with the GPU without the above error.

Added subscriber: @JacekAdamczyk

Added subscriber: @JacekAdamczyk

I'm seeing the same issue
RTX 2080 Super Max-Q
Processor Intel(R) Core(TM) i7-10875H CPU @ 2.30GHz

2.90 Blender
Win 10, 64

After some testing I'm pretty sure it's OPTIX denoising related at this point.
In general ANYTHING Optix AI makes blender crash when rendering.
I was hoping RTX 2080 would be able to handle that with OPTIX AI.

I'm seeing the same issue RTX 2080 Super Max-Q Processor Intel(R) Core(TM) i7-10875H CPU @ 2.30GHz 2.90 Blender Win 10, 64 After some testing I'm pretty sure it's OPTIX denoising related at this point. In general ANYTHING Optix AI makes blender crash when rendering. I was hoping RTX 2080 would be able to handle that with OPTIX AI.

Added subscriber: @3Omar9

Added subscriber: @3Omar9

i have the same exact issue and blender crash every time i try to render using more than 40 samples with the same optix de-noiser
blender 2.90
win 10, 64
rtx 2060 max-q

i have the same exact issue and blender crash every time i try to render using more than 40 samples with the same optix de-noiser blender 2.90 win 10, 64 rtx 2060 max-q

Added subscriber: @SeFF

Added subscriber: @SeFF

Same problem. OptiX denoser was broken at some point (as i was using it in viewport) and i cant fix it. It wont even try to render, the error comes up at once. CPU denoiser works fine.
Here is what's in the log: CUDA_ERROR_INVALID_PC in cuStreamSynchronize(cuda_stream[thread_index]) (device_optix.cpp:769)

rtx 2080 rogAsus
i7-3770k, 16gb ram
win10, 64
Blender 2.9 - 2.91.0

Same problem. OptiX denoser was broken at some point (as i was using it in viewport) and i cant fix it. It wont even try to render, the error comes up at once. CPU denoiser works fine. Here is what's in the log: CUDA_ERROR_INVALID_PC in cuStreamSynchronize(cuda_stream[thread_index]) (device_optix.cpp:769) rtx 2080 rogAsus i7-3770k, 16gb ram win10, 64 Blender 2.9 - 2.91.0

Added subscriber: @bennybrady

Added subscriber: @bennybrady

Me too! Any help would be appreciated.

MIS 2080 super
i9 9900k 64RAM
win10
blender 2.91 - 2
track 2.blend

Me too! Any help would be appreciated. MIS 2080 super i9 9900k 64RAM win10 blender 2.91 - 2 [track 2.blend](https://archive.blender.org/developer/F9074466/track_2.blend)

Added subscriber: @DeciduousAru

Added subscriber: @DeciduousAru

I do also have the same problem, once changed the tiles settings from 64 to 32 it rendered the image but when I give it an another render it reporting me the same error as that of other.... please do help....
blender v2.90.1
i7 10750H
16 GB RAM
win 10
GTX 1660 ti MaxQ Design

I do also have the same problem, once changed the tiles settings from 64 to 32 it rendered the image but when I give it an another render it reporting me the same error as that of other.... please do help.... blender v2.90.1 i7 10750H 16 GB RAM win 10 GTX 1660 ti MaxQ Design

Added subscriber: @Lorenzo-Iemoli

Added subscriber: @Lorenzo-Iemoli

I have the same problem as you, I was able to solve it for a short time, lowering the overclocking of my graphics card (rtx 2070 super). now it's back and I can't fix it anymore. i see this problem in render viewport.
I can render only with cpu, but is slow.

Please, somebody help me!

I have the same problem as you, I was able to solve it for a short time, lowering the overclocking of my graphics card (rtx 2070 super). now it's back and I can't fix it anymore. i see this problem in render viewport. I can render only with cpu, but is slow. Please, somebody help me!

Added subscriber: @skarkkai

Added subscriber: @skarkkai
Philipp Oeser changed title from CUDA Illegal Address (CUDA_ERROR_ILLEGAL_ADDRESS) to Optix Denoiser CUDA_ERROR_ILLEGAL_ADDRESS in cuStreamSynchronize 2020-11-17 15:17:15 +01:00
Member

Added subscribers: @pmoursnv, @lichtwerk

Added subscribers: @pmoursnv, @lichtwerk
Member

Changed status from 'Needs Triage' to: 'Needs Developer To Reproduce'

Changed status from 'Needs Triage' to: 'Needs Developer To Reproduce'
Member

@pmoursnv : cannot reproduce here, does this ring a bell?

@pmoursnv : cannot reproduce here, does this ring a bell?

I lowered my clock speed by -50 (with MSI afterburner - just guessing) on my 2080 super OC and it seemed to help. Is this for sure a cause or is it just luck?

I lowered my clock speed by -50 (with MSI afterburner - just guessing) on my 2080 super OC and it seemed to help. Is this for sure a cause or is it just luck?

Added subscriber: @Teejorlo

Added subscriber: @Teejorlo

This comment was removed by @Teejorlo

*This comment was removed by @Teejorlo*

Having same issues, but opened up in new version 2.90.1 and it is rendering properly

Having same issues, but opened up in new version 2.90.1 and it is rendering properly

I solved the problem again with a little underclocking. the video card clock is a cause, it can't be a coincidence

I solved the problem again with a little underclocking. the video card clock is a cause, it can't be a coincidence

Added subscriber: @Alekprop

Added subscriber: @Alekprop

I have no idea why this is going on but I also offset my GPU clock to -50 and it worked fine. Thx Lorenzo for the out-of-the-box thinking. (Using Blender 2.92.0 Alpha)

I have no idea why this is going on but I also offset my GPU clock to -50 and it worked fine. Thx Lorenzo for the out-of-the-box thinking. (Using Blender 2.92.0 Alpha)

Added subscriber: @FranciscoJoseNavarroSanchez

Added subscriber: @FranciscoJoseNavarroSanchez

I´m too. Same problem with Ryzen 3900x RTX 3070 SUPER in 2.91.0

I´m too. Same problem with Ryzen 3900x RTX 3070 SUPER in 2.91.0

Added subscriber: @chadking

Added subscriber: @chadking

Added subscriber: @Aiduss

Added subscriber: @Aiduss

This comment was removed by @Aiduss

*This comment was removed by @Aiduss*

Added subscriber: @pikosh01

Added subscriber: @pikosh01

i have the same issue gtx 1650 ti

i have the same issue gtx 1650 ti

Added subscriber: @zesenzhang

Added subscriber: @zesenzhang

i have the same issue gtx 1080 *2

i have the same issue gtx 1080 *2

i solved the problem for me. i was running my laptop on turbo mode so my fan speed was very high so my clock speeds were at their highest which is too much apparently. so i changed the fans mode to get lower clock speeds and it worked

i solved the problem for me. i was running my laptop on turbo mode so my fan speed was very high so my clock speeds were at their highest which is too much apparently. so i changed the fans mode to get lower clock speeds and it worked

Added subscribers: @kuan-3, @mano-wii

Added subscribers: @kuan-3, @mano-wii

Added subscriber: @rpserge

Added subscriber: @rpserge

Have just got the same with almost empty scene on 2.92 release, nvidia 2070super, 457.30 driver

Have just got the same with almost empty scene on 2.92 release, nvidia 2070super, 457.30 driver

Added subscriber: @H18

Added subscriber: @H18

Same here, latest Nvidia studio driver with Rtx 2060.
When using optix as a denoiser... Viewport optix denoiser works seemless till the beginning but I couldn't use Optix render as a main denoiser with CPU support promised on 2.92.

Error: Illegal address in cuMemFree(mem.device pointer) (device cuda impl.cpp:975)Illegal address in cuMemFree(mem.device_pointer) (device_cuda_impl.cpp:975) blender optix rendering...

Same here, latest Nvidia studio driver with Rtx 2060. When using optix as a denoiser... Viewport optix denoiser works seemless till the beginning but I couldn't use Optix render as a main denoiser with CPU support promised on 2.92. Error: Illegal address in cuMemFree(mem.device pointer) (device cuda impl.cpp:975)Illegal address in cuMemFree(mem.device_pointer) (device_cuda_impl.cpp:975) blender optix rendering...

Added subscriber: @Grou_Grou

Added subscriber: @Grou_Grou

I have the same problem since the 2.92 update, I didn't have it on the 2.92 beta. I uninstall, reinstall blender, clean userpref, tried to install a the New Nvidia driver, Gaming, and Studio. They both have the same issue with blender. The problem is the same on CUDA and on OptiX, furthermore, the problem is not less recurrent with CPU/GPU render.
A little boring, hope a update with the problem solved arrive soon, that break my workflow hard.

I have the same problem since the 2.92 update, I didn't have it on the 2.92 beta. I uninstall, reinstall blender, clean userpref, tried to install a the New Nvidia driver, Gaming, and Studio. They both have the same issue with blender. The problem is the same on CUDA and on OptiX, furthermore, the problem is not less recurrent with CPU/GPU render. A little boring, hope a update with the problem solved arrive soon, that break my workflow hard.

Added subscriber: @thechode

Added subscriber: @thechode

I don't know if this is any help or just muddying the water, but encountered this after updating to an RTX 3070 GPU on my OpenSUSE Leap 15.2 Linux system. Blender 2.92.0 and 2.91 (all I had on hand for testing). GPU only Optix rendering.

Couldn't render a basic scene without seeing the issue. Tried different NVIDA driver versions (460.32, 460.56), CUDA toolkit versions (10.1, 11.2), fresh OS install, clearing userprefs, different tile sizes, underclocking GPU, etc. Everything I thought sane.

However, issue has stopped occurring since I performed:

  1. Switched renderer to CUDA
  2. Rendered briefly to get an estimated completion time
  3. Switched renderer back to Optix

Zero idea how this had any bearing on the problem, but now I'm rendering fine after 6 hours of no such luck. Would love to provide reproducible steps, but now I can't reproduce the issue at all...

I don't know if this is any help or just muddying the water, but encountered this after updating to an RTX 3070 GPU on my OpenSUSE Leap 15.2 Linux system. Blender 2.92.0 and 2.91 (all I had on hand for testing). GPU only Optix rendering. Couldn't render a basic scene without seeing the issue. Tried different NVIDA driver versions (460.32, 460.56), CUDA toolkit versions (10.1, 11.2), fresh OS install, clearing userprefs, different tile sizes, underclocking GPU, etc. Everything I thought sane. However, issue has stopped occurring since I performed: 1) Switched renderer to CUDA 2) Rendered briefly to get an estimated completion time 3) Switched renderer back to Optix Zero idea how this had any bearing on the problem, but now I'm rendering fine after 6 hours of no such luck. Would love to provide reproducible steps, but now I can't reproduce the issue at all...

Added subscriber: @trekkee_solo

Added subscriber: @trekkee_solo

I have run into this a couple of times. The first time, I kinda figured out where the issue started. This time, I nailed it.

In the first instance, I ran a maintenance/configuration software named "Armory Crate" for Asus gaming laptops. The software comes with gaming laptops and you can control performance, handling, and other options that come with gaming laptops made by Asus( I did some research recently and I guess there is similar software across the board for gaming laptops). After running the software I opened up blender and started working on a project, but when I tried to render, the "Cuda" error message popped up and I had a black render screen. There was no viewport rendering and no rendering at all from the Gpu. What I did to solve it then, was to remember everything I did and I remember it worked before I ran the "Crate" software for the first time. So I did a system restore and restored it back to a point before I opened and ran the software. I had Gpu rendering again.

Just a week ago, I opened blender and tried to render and the "Cuda" error popped up again. I had no Gpu rendering again. So, knowing how I solved it before, I opened and updated all the Nvidia drivers. Still, I had no Gpu rendering. So I opened up "Crate"(Armory Crate) and I saw it had updated and made some setting changes. These changes were necessary due to a whole lot more functionality was added. Crate now gives you control over how the whole computer works depending on the program running. So I made a profile for when blender is running. I set the settings to highest only when I use Blender. So I opened blender, and like I wanted, the computer switched to Turbo mode. It didn't work again, no Gpu rendering. So I went back in to Crate and changed the profile to run on the second highest setting while running Blender. It worked. So what I am thinking is the Armory Crate software is conflicting with the Nvida Experience software and settings.

Hope what I learned helps.

I have run into this a couple of times. The first time, I kinda figured out where the issue started. This time, I nailed it. In the first instance, I ran a maintenance/configuration software named "Armory Crate" for Asus gaming laptops. The software comes with gaming laptops and you can control performance, handling, and other options that come with gaming laptops made by Asus( I did some research recently and I guess there is similar software across the board for gaming laptops). After running the software I opened up blender and started working on a project, but when I tried to render, the "Cuda" error message popped up and I had a black render screen. There was no viewport rendering and no rendering at all from the Gpu. What I did to solve it then, was to remember everything I did and I remember it worked before I ran the "Crate" software for the first time. So I did a system restore and restored it back to a point before I opened and ran the software. I had Gpu rendering again. Just a week ago, I opened blender and tried to render and the "Cuda" error popped up again. I had no Gpu rendering again. So, knowing how I solved it before, I opened and updated all the Nvidia drivers. Still, I had no Gpu rendering. So I opened up "Crate"(Armory Crate) and I saw it had updated and made some setting changes. These changes were necessary due to a whole lot more functionality was added. Crate now gives you control over how the whole computer works depending on the program running. So I made a profile for when blender is running. I set the settings to highest only when I use Blender. So I opened blender, and like I wanted, the computer switched to Turbo mode. It didn't work again, no Gpu rendering. So I went back in to Crate and changed the profile to run on the second highest setting while running Blender. It worked. So what I am thinking is the Armory Crate software is conflicting with the Nvida Experience software and settings. Hope what I learned helps.

Added subscriber: @AndrewSemjonov

Added subscriber: @AndrewSemjonov

I've had these issues for 1-2 years so far on the GTX 1080. Randomly the rendering will crash with illegal address error. My first guess was that perhaps it is a faulty GPU, but I never had anything like it in other software even when working on intense scenes (marmoset, unreal, substance painter). It happens with Optix denoiser on and off and seems extremely random. Sometimes it will let me render out heavy scenes with multiple 8k textures and memory literally over GPU budget somehow, but now it crashes in a 900 mb scene from time to time.

I've had these issues for 1-2 years so far on the GTX 1080. Randomly the rendering will crash with illegal address error. My first guess was that perhaps it is a faulty GPU, but I never had anything like it in other software even when working on intense scenes (marmoset, unreal, substance painter). It happens with Optix denoiser on and off and seems extremely random. Sometimes it will let me render out heavy scenes with multiple 8k textures and memory literally over GPU budget somehow, but now it crashes in a 900 mb scene from time to time.

Added subscriber: @yunaffxqq

Added subscriber: @yunaffxqq

Teach you How Fix Resolve Blender Optix Denoising Cycles Rendering Ilegal address CUDA_ERROR_ILLEGAL

https://youtu.be/c1LPcFtlmRc

Teach you How Fix Resolve Blender Optix Denoising Cycles Rendering Ilegal address CUDA_ERROR_ILLEGAL https://youtu.be/c1LPcFtlmRc

Nice tricks, it seems great but could you explain the actions you made on the file in english. Unfortunaly I don't speak coreen.

Nice tricks, it seems great but could you explain the actions you made on the file in english. Unfortunaly I don't speak coreen.

Added subscriber: @angri

Added subscriber: @angri

Added subscriber: @sergofc

Added subscriber: @sergofc

I had overclocked my 2080super through MSI Afterburner and found out that it was causing CUDA_ERROR_ILLEGAL_ADDRESS. So would guess probably any GPU overclocks or laptop "boost modes" may cause a similar error.

I had overclocked my 2080super through MSI Afterburner and found out that it was causing CUDA_ERROR_ILLEGAL_ADDRESS. So would guess probably any GPU overclocks or laptop "boost modes" may cause a similar error.

Added subscriber: @RichardCulver

Added subscriber: @RichardCulver

In #79996#1169424, @Grou_Grou wrote:
Nice tricks, it seems great but could you explain the actions you made on the file in english. Unfortunaly I don't speak coreen.

In the Korean Video, from what I can tell, all that was done was to change the viewport to a non-material or shaded view to free up the GPU from having to display the viewport while also rendering.

> In #79996#1169424, @Grou_Grou wrote: > Nice tricks, it seems great but could you explain the actions you made on the file in english. Unfortunaly I don't speak coreen. In the Korean Video, from what I can tell, all that was done was to change the viewport to a non-material or shaded view to free up the GPU from having to display the viewport while also rendering.

Yes, that is what I gathered as well. However it does not really work. Blender rendering sometimes crashes rendering a 800 vram mb scene on a 8 vram gb card. Downclocking the card sometimes helps, but most of the time not. It might be related to some gpu flaws, but it's still very strange because in all other software everything is perfect. Semi considering switching to full time cpu rendering. It's slower but at least it's stable.

Yes, that is what I gathered as well. However it does not really work. Blender rendering sometimes crashes rendering a 800 vram mb scene on a 8 vram gb card. Downclocking the card sometimes helps, but most of the time not. It might be related to some gpu flaws, but it's still very strange because in all other software everything is perfect. Semi considering switching to full time cpu rendering. It's slower but at least it's stable.
Author

I recently had some issues with my GPU and I think it might be relevant to this thread. After 1 year of normal usage, sometimes when the PC was booting the GPU wouldn't turn on. Also, the card started having some problems playing videos. I believe it was a faulty VRAM, but there could be something else. In 3D programs and games, the GPU was still working correctly and performance didn't change a bit. Perhaps Blender was being affected by the faulty VRAM or other defective GPU components.

EDIT: The GPU was not overclocked.

I recently had some issues with my GPU and I think it might be relevant to this thread. After 1 year of normal usage, sometimes when the PC was booting the GPU wouldn't turn on. Also, the card started having some problems playing videos. I believe it was a faulty VRAM, but there could be something else. In 3D programs and games, the GPU was still working correctly and performance didn't change a bit. Perhaps Blender was being affected by the faulty VRAM or other defective GPU components. EDIT: The GPU was not overclocked.

In #79996#1183010, @AndrewSemjonov wrote:
Yes, that is what I gathered as well. However it does not really work. Blender rendering sometimes crashes rendering a 800 vram mb scene on a 8 vram gb card. Downclocking the card sometimes helps, but most of the time not. It might be related to some gpu flaws, but it's still very strange because in all other software everything is perfect. Semi considering switching to full time cpu rendering. It's slower but at least it's stable.

Right. I haven't tested it yet fully. I have been considering CPU as well but denoise is no where near as nice from my testing.

Would be nice to get this issue resolved.

> In #79996#1183010, @AndrewSemjonov wrote: > Yes, that is what I gathered as well. However it does not really work. Blender rendering sometimes crashes rendering a 800 vram mb scene on a 8 vram gb card. Downclocking the card sometimes helps, but most of the time not. It might be related to some gpu flaws, but it's still very strange because in all other software everything is perfect. Semi considering switching to full time cpu rendering. It's slower but at least it's stable. Right. I haven't tested it yet fully. I have been considering CPU as well but denoise is no where near as nice from my testing. Would be nice to get this issue resolved.

So I know that this issue has to do with Optix specifically. But it does not seem to be getting addressed as a bug. or is it? Because it is pervasive.

The only solution I have found that does not crash is to use GPU compute but use OpenImage Denoiser which is CPU based and maybe a little slower. But it works well. And it is stable. Optix has always been unstable for me anyway. So I am going to stop using it altogether until someone, either from Blender development or Nvidia comes out with a fix. It should be noted that if you are using a render farm with various GPU configs (as I have) it might be a more stable solution over all. Currently I am running several Intel and AMD machines with a variety of AMD GPUs and using OpenImage with no issues thus far.

Not a fix for this, but a workaround for now.

So I know that this issue has to do with Optix specifically. But it does not seem to be getting addressed as a bug. or is it? Because it is pervasive. The only solution I have found that does not crash is to use GPU compute but use OpenImage Denoiser which is CPU based and maybe a little slower. But it works well. And it is stable. Optix has always been unstable for me anyway. So I am going to stop using it altogether until someone, either from Blender development or Nvidia comes out with a fix. It should be noted that if you are using a render farm with various GPU configs (as I have) it might be a more stable solution over all. Currently I am running several Intel and AMD machines with a variety of AMD GPUs and using OpenImage with no issues thus far. Not a fix for this, but a workaround for now.

Removed subscriber: @chadking

Removed subscriber: @chadking

Added subscriber: @Ed-H

Added subscriber: @Ed-H

Same here NVIDIA driver 466.27 / GTX 980 Ti on Blender 2.93.1 - External Render Cycles

Here are some highlights

Illegal address in cuMemcpyHtoD((CUdeviceptr)mem.device_pointer, mem.host_pointer, mem.memory_size()) (device_cuda_impl.cpp:951)CUDA_ERROR_ILLEGAL_ADDRESS in cuStreamSynchronize(0) (device_optix.cpp:1074)

Illegal address in cuMemHostGetDevicePointer_v2(&device_pointer, shared_pointer, 0) (device_cuda_impl.cpp:873)Illegal address in cuMemFree(mem.device_pointer) (device_cuda_impl.cpp:981)

Had to reload Blender after that last one no rendering possible until

Same here NVIDIA driver 466.27 / GTX 980 Ti on Blender 2.93.1 - External Render Cycles Here are some highlights Illegal address in cuMemcpyHtoD((CUdeviceptr)mem.device_pointer, mem.host_pointer, mem.memory_size()) (device_cuda_impl.cpp:951)CUDA_ERROR_ILLEGAL_ADDRESS in cuStreamSynchronize(0) (device_optix.cpp:1074) Illegal address in cuMemHostGetDevicePointer_v2(&device_pointer, shared_pointer, 0) (device_cuda_impl.cpp:873)Illegal address in cuMemFree(mem.device_pointer) (device_cuda_impl.cpp:981) Had to reload Blender after that last one no rendering possible until

In #79996#1184702, @Ed-H wrote:
Same here NVIDIA driver 466.27 / GTX 980 Ti on Blender 2.93.1 - External Render Cycles

Here are some highlights

Illegal address in cuMemcpyHtoD((CUdeviceptr)mem.device_pointer, mem.host_pointer, mem.memory_size()) (device_cuda_impl.cpp:951)CUDA_ERROR_ILLEGAL_ADDRESS in cuStreamSynchronize(0) (device_optix.cpp:1074)

Illegal address in cuMemHostGetDevicePointer_v2(&device_pointer, shared_pointer, 0) (device_cuda_impl.cpp:873)Illegal address in cuMemFree(mem.device_pointer) (device_cuda_impl.cpp:981)

Had to reload Blender after that last one no rendering possible until

But I do find even if you reload, the error eventually comes back.

> In #79996#1184702, @Ed-H wrote: > Same here NVIDIA driver 466.27 / GTX 980 Ti on Blender 2.93.1 - External Render Cycles > > Here are some highlights > > Illegal address in cuMemcpyHtoD((CUdeviceptr)mem.device_pointer, mem.host_pointer, mem.memory_size()) (device_cuda_impl.cpp:951)CUDA_ERROR_ILLEGAL_ADDRESS in cuStreamSynchronize(0) (device_optix.cpp:1074) > > Illegal address in cuMemHostGetDevicePointer_v2(&device_pointer, shared_pointer, 0) (device_cuda_impl.cpp:873)Illegal address in cuMemFree(mem.device_pointer) (device_cuda_impl.cpp:981) > > Had to reload Blender after that last one no rendering possible until But I do find even if you reload, the error eventually comes back.

Added subscriber: @APEC

Added subscriber: @APEC

Got the same error with 2.93.1 today.
"Cycles" just stopped rendering in overview.
GTX 1650 Sup

Illegal address in cuMemFree(mem.device_pointer) (device_cuda_impl.cpp:981)
Illegal address in cuGraphicsUnregisterResource(pmem.cuPBOresource) (device_cuda_impl.cpp:2226)

after close/open blender it started to work fine.

Got the same error with 2.93.1 today. "Cycles" just stopped rendering in overview. GTX 1650 Sup ``` Illegal address in cuMemFree(mem.device_pointer) (device_cuda_impl.cpp:981) Illegal address in cuGraphicsUnregisterResource(pmem.cuPBOresource) (device_cuda_impl.cpp:2226) ``` after close/open blender it started to work fine.
Member

Added subscribers: @Hoorkie, @PratikPB2123

Added subscribers: @Hoorkie, @PratikPB2123

Added subscriber: @GavinWyatt

Added subscriber: @GavinWyatt

Changed status from 'Needs Developer To Reproduce' to: 'Needs Triage'

Changed status from 'Needs Developer To Reproduce' to: 'Needs Triage'

CUDA_ERROR_ILLEGAL_ADDRESS in cuStreamSynchronize(cuda_stream[thread_index]) (device_optix.cpp:821)CUDA_ERROR_ILLEGAL_ADDRESS in cuStreamSynchronize(0) (device_optix.cpp:1074)

The second I used a 2kHDRI environment texture it crashed

2.93 blender 3d
2700 RTX super
32 gig ram
AMD Ryzen 3900x

CUDA_ERROR_ILLEGAL_ADDRESS in cuStreamSynchronize(cuda_stream[thread_index]) (device_optix.cpp:821)CUDA_ERROR_ILLEGAL_ADDRESS in cuStreamSynchronize(0) (device_optix.cpp:1074) The second I used a 2kHDRI environment texture it crashed 2.93 blender 3d 2700 RTX super 32 gig ram AMD Ryzen 3900x
Member

Changed status from 'Needs Triage' to: 'Needs Developer To Reproduce'

Changed status from 'Needs Triage' to: 'Needs Developer To Reproduce'

Added subscriber: @Shiki-1

Added subscriber: @Shiki-1

Error: CUDA_ERROR_ILLEGAL_ADDRESS in cuStreamSynchronize(cuda_stream[thread_index]) (device_optix.cpp:821)

Same problem happened when I use multi-viewlayer rendering, even though I tried to switch OPTIX to CUDA in cycles panel, the error was still there.
What's more confusing is that sometimes I changed nothing but restart my .blend file, the error was gone.

2.93LTS blender

Ryzen5 3600
RTX 2080 super
32g RAM

Error: CUDA_ERROR_ILLEGAL_ADDRESS in cuStreamSynchronize(cuda_stream[thread_index]) (device_optix.cpp:821) Same problem happened when I use multi-viewlayer rendering, even though I tried to switch OPTIX to CUDA in cycles panel, the error was still there. What's more confusing is that sometimes I changed nothing but restart my .blend file, the error was gone. 2.93LTS blender Ryzen5 3600 RTX 2080 super 32g RAM

Added subscriber: @ManBlender

Added subscriber: @ManBlender

System Information
Operating system: Windows-10-10.0.18362-SP0 64 Bits
Graphics card: NVIDIA GeForce GTX 1650 Ti/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 466.77

Blender Version
Broken: version: 2.91.2, branch: master, commit date: 2021-01-19 16:15, hash: 5be9ef4177
Worked: (newest version of Blender that worked as expected)

Short description of error
I getting this error when image is in high resolution 4096x2160 as 4K, in lower normal. Also this bug looks correlating with RAM memory management.
After close and run blender again, then working on 4K in normal.

**System Information** Operating system: Windows-10-10.0.18362-SP0 64 Bits Graphics card: NVIDIA GeForce GTX 1650 Ti/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 466.77 **Blender Version** Broken: version: 2.91.2, branch: master, commit date: 2021-01-19 16:15, hash: `5be9ef4177` Worked: (newest version of Blender that worked as expected) **Short description of error** I getting this error when image is in high resolution 4096x2160 as 4K, in lower normal. Also this bug looks correlating with RAM memory management. After close and run blender again, then working on 4K in normal.

Added subscriber: @chris.sheldon

Added subscriber: @chris.sheldon

Error: CUDA_ERROR_ILLEGAL_ADDRESS in cuStreamSynchronize(cuda_stream[thread_index]) (device_optix.cpp:821)CUDA_ERROR_ILLEGAL_ADDRESS in cuStreamSynchronize(cuda_stream[thread_index]) (device_optix.cpp:821)

Same issue as reported here. Error usualy appears after running a few renders & viewpoert rendering then running a render. Quitting and restarting Blender seems to temporarly fix the issue.

System Info:

Edition Windows 10 Pro
Version 20H2
OS build 19042.1165
Processor AMD Ryzen Threadripper 3960X 24-Core Processor 3.80 GHz
Installed RAM 128 GB (128 GB usable)
System type 64-bit operating system, x64-based processor
GPU 2 X Nvidia RTX A6000 (Driver 462.59)

Error: CUDA_ERROR_ILLEGAL_ADDRESS in cuStreamSynchronize(cuda_stream[thread_index]) (device_optix.cpp:821)CUDA_ERROR_ILLEGAL_ADDRESS in cuStreamSynchronize(cuda_stream[thread_index]) (device_optix.cpp:821) Same issue as reported here. Error usualy appears after running a few renders & viewpoert rendering then running a render. Quitting and restarting Blender seems to temporarly fix the issue. System Info: Edition Windows 10 Pro Version 20H2 OS build 19042.1165 Processor AMD Ryzen Threadripper 3960X 24-Core Processor 3.80 GHz Installed RAM 128 GB (128 GB usable) System type 64-bit operating system, x64-based processor GPU 2 X Nvidia RTX A6000 (Driver 462.59)

Added subscriber: @kosblend

Added subscriber: @kosblend

Backing with the problem..
https://blenderartists.org/t/failed-to-create-cuda-context-illegal-adress/1278322
https://blenderartists.org/t/cuda-error-failed-to-create-cuda-context-illegal-address/1300749
https://blender.stackexchange.com/questions/194291/cuda-error-illegal-adress-when-rendering

For problem is not important resolution, in any of can hit this error.

Also meet this on:
Blender Version
Broken: version: 3.0.0 Alpha, branch: master, commit date: 2021-09-17 15:08, hash: 6cf734a2e5
Worked: (newest version of Blender that worked as expected)

The problem is that, if error exist, and OptiX turned of for render and viewport, then blender still have problem. Need close and open again.
Even change GPU to CPU, illegal address still exist.

Want recommend to put this type graphic card error in Script logs. By this errors users don't have option to copy and putting images about errors on boards and hard to find and it is difficult to assess the scale of the problem.
There is popup with this error, but quick dispersing accidental due error.

blender_system_info.txt

blender_debug_output.txt

Backing with the problem.. https://blenderartists.org/t/failed-to-create-cuda-context-illegal-adress/1278322 https://blenderartists.org/t/cuda-error-failed-to-create-cuda-context-illegal-address/1300749 https://blender.stackexchange.com/questions/194291/cuda-error-illegal-adress-when-rendering For problem is not important resolution, in any of can hit this error. Also meet this on: **Blender Version** Broken: version: 3.0.0 Alpha, branch: master, commit date: 2021-09-17 15:08, hash: `6cf734a2e5` Worked: (newest version of Blender that worked as expected) The problem is that, if error exist, and OptiX turned of for render and viewport, then blender still have problem. Need close and open again. Even change GPU to CPU, illegal address still exist. **Want recommend to put this type graphic card error in Script logs**. By this errors users don't have option to copy and putting images about errors on boards and hard to find and it is difficult to assess the scale of the problem. There is popup with this error, but quick dispersing accidental due error. [blender_system_info.txt](https://archive.blender.org/developer/F10511756/blender_system_info.txt) [blender_debug_output.txt](https://archive.blender.org/developer/F10511757/blender_debug_output.txt)
Member

Removed subscriber: @pmoursnv

Removed subscriber: @pmoursnv

Added subscriber: @dodeqaa

Added subscriber: @dodeqaa

{F11646027}System Info :

Windows Pro 10.0.19043
Threadripper 3970
128gb RAM
RTX A6000 Driver 471.68

See attached screencap for error. Unable to use Optix as render solution.

Update: Choosing CUDA in System will work with OPTIX as denoise. Error occurs when choosing OPTIX in System.

{[F11646027](https://archive.blender.org/developer/F11646027/Screenshot__21_.png)}System Info : Windows Pro 10.0.19043 Threadripper 3970 128gb RAM RTX A6000 Driver 471.68 See attached screencap for error. Unable to use Optix as render solution. Update: Choosing CUDA in System will work with OPTIX as denoise. Error occurs when choosing OPTIX in System.

errors that briefly display, but go away can be captured in the INFO panel.

errors that briefly display, but go away can be captured in the INFO panel.

Added subscriber: @Peter-Sampson

Added subscriber: @Peter-Sampson

Added subscriber: @ThomasDinges

Added subscriber: @ThomasDinges

I this still an issue in Blender 3.3, 3.4?

I this still an issue in Blender 3.3, 3.4?

No, looks solved.

No, looks solved.

Changed status from 'Needs Developer To Reproduce' to: 'Resolved'

Changed status from 'Needs Developer To Reproduce' to: 'Resolved'
Thomas Dinges self-assigned this 2022-11-28 09:27:17 +01:00

Thanks, closing then.

Thanks, closing then.
Sign in to join this conversation.
No Label
Interest
Alembic
Interest
Animation & Rigging
Interest
Asset Browser
Interest
Asset Browser Project Overview
Interest
Audio
Interest
Automated Testing
Interest
Blender Asset Bundle
Interest
BlendFile
Interest
Collada
Interest
Compatibility
Interest
Compositing
Interest
Core
Interest
Cycles
Interest
Dependency Graph
Interest
Development Management
Interest
EEVEE
Interest
EEVEE & Viewport
Interest
Freestyle
Interest
Geometry Nodes
Interest
Grease Pencil
Interest
ID Management
Interest
Images & Movies
Interest
Import Export
Interest
Line Art
Interest
Masking
Interest
Metal
Interest
Modeling
Interest
Modifiers
Interest
Motion Tracking
Interest
Nodes & Physics
Interest
OpenGL
Interest
Overlay
Interest
Overrides
Interest
Performance
Interest
Physics
Interest
Pipeline, Assets & IO
Interest
Platforms, Builds & Tests
Interest
Python API
Interest
Render & Cycles
Interest
Render Pipeline
Interest
Sculpt, Paint & Texture
Interest
Text Editor
Interest
Translations
Interest
Triaging
Interest
Undo
Interest
USD
Interest
User Interface
Interest
UV Editing
Interest
VFX & Video
Interest
Video Sequencer
Interest
Virtual Reality
Interest
Vulkan
Interest
Wayland
Interest
Workbench
Interest: X11
Legacy
Blender 2.8 Project
Legacy
Milestone 1: Basic, Local Asset Browser
Legacy
OpenGL Error
Meta
Good First Issue
Meta
Papercut
Meta
Retrospective
Meta
Security
Module
Animation & Rigging
Module
Core
Module
Development Management
Module
EEVEE & Viewport
Module
Grease Pencil
Module
Modeling
Module
Nodes & Physics
Module
Pipeline, Assets & IO
Module
Platforms, Builds & Tests
Module
Python API
Module
Render & Cycles
Module
Sculpt, Paint & Texture
Module
Triaging
Module
User Interface
Module
VFX & Video
Platform
FreeBSD
Platform
Linux
Platform
macOS
Platform
Windows
Priority
High
Priority
Low
Priority
Normal
Priority
Unbreak Now!
Status
Archived
Status
Confirmed
Status
Duplicate
Status
Needs Info from Developers
Status
Needs Information from User
Status
Needs Triage
Status
Resolved
Type
Bug
Type
Design
Type
Known Issue
Type
Patch
Type
Report
Type
To Do
No Milestone
No project
No Assignees
43 Participants
Notifications
Due Date
The due date is invalid or out of range. Please use the format 'yyyy-mm-dd'.

No due date set.

Dependencies

No dependencies set.

Reference: blender/blender#79996
No description provided.