Access violation - CUDA crashes Blender #63313

New Issue

Acrivec Cevirca · 2019-04-05T15:59:04+02:00

Acrivec Cevirca commented

2019-04-05 15:59:04 +02:00

System Information
Operating system: W10
Graphics card: 980Ti

Blender Version
Broken: 2.80 19-04-04 17:02
Worked: 2.80 19-04-02

Short description of error

After hitting Render it starts everything, and after some time (maybe 20 tiles rendered) blender crashes.

Console:

CUDA error: Illegal address in cuCtxSynchronize(), line 1545

Refer to the Cycles GPU rendering documentation for possible solutions:
https://docs.blender.org/manual/en/dev/render/cycles/gpu_rendering.html

CUDA error: Illegal address in mem_alloc_result, line 850
CUDA error: Illegal address in cuModuleGetGlobal(&cumem, &cubytes, cuModule, bind_name.c_str()), line 1060
CUDA error: Illegal address in cuMemcpyHtoD(cumem, (void*)&ptr, cubytes), line 1070
CUDA error: Illegal address in mem_alloc_result, line 850
CUDA error: Illegal address in cuMemsetD8(cuda_device_ptr(mem.device_pointer), 0, mem.memory_size()), line 986
CUDA error: Illegal address in cuMemsetD8(cuda_device_ptr(mem.device_pointer), 0, mem.memory_size()), line 986
CUDA error: Illegal address in cuModuleGetFunction(&cuFinalize, cuFilterModule, "kernel_cuda_filter_finalize"), line 1472
Error   : EXCEPTION_ACCESS_VIOLATION
Address : 0x00007FF8C34CB9AF
Module  : C:\Windows\SYSTEM32\nvcuda.dll

Exact steps for others to reproduce the error
I can't reproduce this error on new .blend file, whereas my .blend has copyrighted stuff.

**System Information** Operating system: W10 Graphics card: 980Ti **Blender Version** Broken: 2.80 19-04-04 17:02 Worked: 2.80 19-04-02 **Short description of error** After hitting Render it starts everything, and after some time (maybe 20 tiles rendered) blender crashes. Console: ``` CUDA error: Illegal address in cuCtxSynchronize(), line 1545 Refer to the Cycles GPU rendering documentation for possible solutions: https://docs.blender.org/manual/en/dev/render/cycles/gpu_rendering.html CUDA error: Illegal address in mem_alloc_result, line 850 CUDA error: Illegal address in cuModuleGetGlobal(&cumem, &cubytes, cuModule, bind_name.c_str()), line 1060 CUDA error: Illegal address in cuMemcpyHtoD(cumem, (void*)&ptr, cubytes), line 1070 CUDA error: Illegal address in mem_alloc_result, line 850 CUDA error: Illegal address in cuMemsetD8(cuda_device_ptr(mem.device_pointer), 0, mem.memory_size()), line 986 CUDA error: Illegal address in cuMemsetD8(cuda_device_ptr(mem.device_pointer), 0, mem.memory_size()), line 986 CUDA error: Illegal address in cuModuleGetFunction(&cuFinalize, cuFilterModule, "kernel_cuda_filter_finalize"), line 1472 Error : EXCEPTION_ACCESS_VIOLATION Address : 0x00007FF8C34CB9AF Module : C:\Windows\SYSTEM32\nvcuda.dll ``` **Exact steps for others to reproduce the error** I can't reproduce this error on new .blend file, whereas my .blend has copyrighted stuff.

Acrivec Cevirca commented

2019-04-05 15:59:04 +02:00

Added subscriber: @Acrivec

Brecht Van Lommel commented

2019-04-05 16:05:49 +02:00

Added subscriber: @brecht

Brecht Van Lommel commented

2019-04-05 16:05:49 +02:00

Please attach a .blend file to reproduce the issue.
Are you using GPU or CPU + GPU rendering?
From the backtrace I guess you might have denoising enabled? Does it work with denoising disabled?

* Please attach a .blend file to reproduce the issue. * Are you using GPU or CPU + GPU rendering? * From the backtrace I guess you might have denoising enabled? Does it work with denoising disabled?

Acrivec Cevirca commented

2019-04-05 16:26:40 +02:00

CPU+GPU

Yes, I'm using denoising - after disabling blender stopped crashing. Turning on again - crashing.

I hope there's all copyrighted stuff removed here:
denoiser crash.blend

CPU+GPU Yes, I'm using denoising - after disabling blender stopped crashing. Turning on again - crashing. I hope there's all copyrighted stuff removed here: [denoiser crash.blend](https://archive.blender.org/developer/F6913726/denoiser_crash.blend)

Brecht Van Lommel commented

2019-04-05 17:18:31 +02:00

The only change between these builds was in adaptive subdivision, where it was not subdividing with the right detail in some cases. It may be that this caused finer subdivision and resulting higher memory usage, after which it runs out of memory for denoising.

The .blend does not contain image textures though so it's hard to say from looking at just that.

Does it work when you disable experimental features?
Does it work when you increase the render dicing rate?
Was this render already near the memory limit for your GPU before these changes?

The only change between these builds was in adaptive subdivision, where it was not subdividing with the right detail in some cases. It may be that this caused finer subdivision and resulting higher memory usage, after which it runs out of memory for denoising. The .blend does not contain image textures though so it's hard to say from looking at just that. * Does it work when you disable experimental features? * Does it work when you increase the render dicing rate? * Was this render already near the memory limit for your GPU before these changes?

Acrivec Cevirca commented

2019-04-05 18:52:39 +02:00

Yes, it works with disabled experimenal features.

Increasing render dicing rate fixes the problem too.

I think yes, it's around 5.5gb shown by blender, whereas my card has 6GB. Although on previous blender versions where it couldn't go over this limit it wouldn't allow me go to near 6gb, having 3gb displayed by blender was top max, over that it wasn't possible to render.

Also I've been rendering it yesterday when it hit 15GB.

Yes, it works with disabled experimenal features. Increasing render dicing rate fixes the problem too. I think yes, it's around 5.5gb shown by blender, whereas my card has 6GB. Although on previous blender versions where it couldn't go over this limit it wouldn't allow me go to near 6gb, having 3gb displayed by blender was top max, over that it wasn't possible to render. Also I've been rendering it yesterday when it hit 15GB.

Acrivec Cevirca commented

2019-04-24 11:24:10 +02:00

Added subscriber: @lichtwerk

Acrivec Cevirca commented

2019-04-24 11:24:10 +02:00

@lichtwerk as far as I can see there were some commits regarding this issue and it stopped crashing after that. Can't see them though, because of builbot last changes limit, so I think it's resolved.

Philipp Oeser commented

2019-04-24 11:43:12 +02:00

Changed status from 'Open' to: 'Resolved'

Philipp Oeser closed this issue

2019-04-24 11:43:12 +02:00

Philipp Oeser self-assigned this 2019-04-24 11:43:12 +02:00

Philipp Oeser commented

2019-04-24 11:43:12 +02:00

Oki, glad to hear, closing then... (feel free to comment again if issues creep up again)

Sign in to join this conversation.

No Label

Download

What's New

Blender Studio

Manual

Developers Blog

Documentation

Benchmark

Blender Conference

Development Fund

One-time Donations

Access violation - CUDA crashes Blender #63313