Maniphest T80793

Cant render with cycles : Illegal address in cuCtxSynchronize()
Closed, Archived
Actions

Assigned To
Richard Antalik (ISS)
Authored By
tommy kho (rokai)
Sep 15 2020, 4:58 AM
Tags
  • BF Blender
Subscribers
Muhammad Ahmed (iplayerunknown)
Richard Antalik (ISS)
Simon Lohmann (simon-codes)
tommy kho (rokai)

Description

System Information
Operating system: Windows-10-10.0.18362-SP0 64 Bits
Graphics card: GeForce RTX 2060/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 452.06

Blender Version
Broken: version: 2.90.0, branch: master, commit date: 2020-08-31 11:26, hash: rB0330d1af29c0
Worked: 2.83.6

Short description of error

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

Exact steps for others to reproduce the error
i render a 6273 x 2185 pixel resolution. and it fail everytime.
but 60 -70 percent to the resolution it worked. i really need to render to those high resolution.
sometime blender just quit after my monitor is flickering for a moment. i use 2 monitor.

Event Timeline

tommy kho (rokai) created this task.Sep 15 2020, 4:58 AM
Simon Lohmann (simon-codes) added a subscriber: Simon Lohmann (simon-codes).Sep 15 2020, 12:08 PM

I tried to reproduce the fault:

  • on Linux with current 2.90.0 release, GPU: GTX 1060-MaxQ
  • on Windows with current 2.90.0 and an GTX 1070

both worked fine with your specified resolution of 6273 x 2185.

sometime blender just quit after my monitor is flickering for a moment. i use 2 monitor.

This sounds like a driver or hardware issue.

Make sure you have the latest drivers installed.
Providing an example .blend-file could also help to reproduce the issue.

tommy kho (rokai) added a comment.EditedSep 15 2020, 3:52 PM


i dont know whats wrong,
a moment before error the tile seem to spreading everywhere. then error.
i have set the tile to 32. and still got no luck.
i will try 16 later.
(*edit: i try 16 tile size and get the same error)

here is some problem with EVEE also... blender crash with a flickering at my monitor. then after monitor on air again my audio is suddenly not working. i must restart my computer to get the audio back again. it happen a lot when im viewing a big scene with evee. luckily blender got autosave every 2 min, and reboot so fast so i can go back in no time.
but still i have no idea what is this all about
i have upgrade the latest NVIDIA driver from official site its 452.06
i have 32GB RAM. proc i7 7700, Motherboard msiH270 gaming.

Richard Antalik (ISS) changed the task status from Needs Triage to Needs Information from User.Sep 17 2020, 4:16 PM
Richard Antalik (ISS) added a subscriber: Richard Antalik (ISS).

If this happens with only heavier files this could be TDR problem. See https://docs.blender.org/manual/en/latest/render/cycles/gpu_rendering.html#the-nvidia-opengl-driver-lost-connection-with-the-display-driver

Can you check that?

tommy kho (rokai) added a comment.Sep 18 2020, 5:52 AM

sorry i forgot to mention it, but i have set the TDRdelay to 16 sec, before i report this error. so this is bassically happening in 16 sec TDRdelay setting.
i just tried for default value 2 sec, and 8 sec, but nothing work

or should i just disabling the TDRdelay and adding TDRlevel to value 0?
and if i must, then what the drawback of this setting for my PC?

thanks for the respond.

tommy kho (rokai) added a comment.Sep 18 2020, 5:59 AM

*updated
so i just tried to render this with blender 2.83.6 LTS
and cycles render it perfectly!, with default TDRdelay of 2 sec.

so i think there is maybe something going wrong with 2.90 version.

tommy kho (rokai) updated the task description.Sep 18 2020, 6:00 AM
Richard Antalik (ISS) added a comment.Sep 28 2020, 7:48 AM

Sorry for late response, can you check if this happens with simple file like with default cube for example?

tommy kho (rokai) added a comment.Sep 29 2020, 5:09 PM

no problem with default cube in 2.90 version

Richard Antalik (ISS) added a comment.Oct 1 2020, 1:04 PM

Can you try to simlify file by removing as much objects as possible while making sure bug is still there and then upload simlplified file?

tommy kho (rokai) added a comment.Oct 1 2020, 1:22 PM

sorry, after i upgrade to 2.90.1 version. and i can render now.
i just couldn't go back to 2.90 version again... and troubleshooting for the bug existence, (if that is what you asking).
thanks for the assist.!

Richard Antalik (ISS) closed this task as Archived.Oct 1 2020, 1:42 PM
Richard Antalik (ISS) claimed this task.

Thanks for update. No need to troubleshoot if bug is already fixed.

Muhammad Ahmed (iplayerunknown) added a subscriber: Muhammad Ahmed (iplayerunknown).Oct 3 2021, 8:26 AM

i have almost the same problem no mater how huge the scene is while rendering blender crashes or in viewport it shows an error ( illegal address in cuctxsynchronize (device_cuda_impl.cpp1965) )
I am using Nvidia GTX 750Ti 2Gb Evga Version and i have 8 gbs of ram i have tried many things but none works for me.

i have attached the error Please Take a look at this. and if you really want to help me let me know I'll give you my discord Thanks>

Richard Antalik (ISS) added a comment.Oct 11 2021, 2:19 PM
In T80793#1229980, @Muhammad Ahmed (iplayerunknown) wrote:

i have almost the same problem no mater how huge the scene is while rendering blender crashes or in viewport it shows an error ( illegal address in cuctxsynchronize (device_cuda_impl.cpp1965) )
I am using Nvidia GTX 750Ti 2Gb Evga Version and i have 8 gbs of ram i have tried many things but none works for me.

i have attached the error Please Take a look at this. and if you really want to help me let me know I'll give you my discord Thanks>

Please make a new report if you have issues