Consistent crashing while rendering with RTX Titan #74754

System Information
Operating system: Win 10 64 bit
Graphics card: Dual Titan RTXs, rendering with CUDA

Blender Version
Broken: 2.82a

Short description of error
Crashes after rendering attached scene after 20-40 frames.

Exact steps for others to reproduce the error
Open this blend and render animation: https://www.dropbox.com/s/9j6np0qs1066hxd/texturing%20tiling%20tutorial_packed.blend?dl=0 (434mb, sorry it's big)

With my dual RTX Titans it constantly crashes after 20-40 frames and gives this as the reason:
//Error : EXCEPTION_ACCESS_VIOLATION
Address : 0x00007FF6A2E4D132//
Updated to latest graphics driver but makes no difference.

However it renders fine on a spare laptop, which makes me think it's a problem with the RTX.

Added subscriber: @AndrewPrice

Added subscriber: @tmoneygames

If it's not compiled with cuda 10 support then it won't work with RTX cards. You can compile your own version in visual studio, I think, and set it to support cuda 10. I posted a link on your twitter message as well as here. https://blender.stackexchange.com/questions/119837/how-can-one-do-rendering-with-cycles-using-an-nvidia-rtx-gpu

@tmoneygames
Unless I'm mistaken, that is no longer true. In the link you posted the top voted answer is:

Update as of July 29th 2019: NVIDIA RTX GPUs are now officially supported and can be used to accelerate renderings in Cycles using the raytracing cores of RTX cards.

Developer blog post about it

Added subscriber: @iss

Changed status from 'Needs Triage' to: 'Needs User Info'

@AndrewPrice does this happen if you click on File > Defaults > Load Factory Settings?
Can you check if this happens with version 2.83? https://builder.blender.org/download/

Added subscribers: @CharlieJolly, @EAW

I tried rendering the file in an MSVC debug mode build.

Run-Time Check Failure #3 - The variable 'c' is being used without being initialized. occurred

blender.exe!ccl::svm_node_vector_math(ccl::KernelGlobals * kg, ccl::ShaderData * sd, float * stack, unsigned int type, unsigned int inputs_stack_offsets, unsigned int outputs_stack_offsets, int * offset) Line 66
	at C:\blender-git\blender\intern\cycles\kernel\svm\svm_math.h(66)
blender.exe!ccl::svm_eval_nodes(ccl::KernelGlobals * kg, ccl::ShaderData * sd, ccl::PathState * state, float * buffer, ccl::ShaderType type, int path_flag) Line 389
	at C:\blender-git\blender\intern\cycles\kernel\svm\svm.h(389)
blender.exe!ccl::shader_eval_surface(ccl::KernelGlobals * kg, ccl::ShaderData * sd, ccl::PathState * state, float * buffer, int path_flag) Line 1117
	at C:\blender-git\blender\intern\cycles\kernel\kernel_shader.h(1117)
blender.exe!ccl::kernel_background_evaluate(ccl::KernelGlobals * kg, ccl::uint4 * input, ccl::float4 * output, int i) Line 512
	at C:\blender-git\blender\intern\cycles\kernel\kernel_bake.h(512)
blender.exe!ccl::kernel_cpu_sse41_shader(ccl::KernelGlobals * kg, ccl::uint4 * input, ccl::float4 * output, int type, int filter, int i, int offset, int sample) Line 161
	at C:\blender-git\blender\intern\cycles\kernel\kernels\cpu\kernel_cpu_impl.h(161)
blender.exe!ccl::CPUDevice::thread_shader(ccl::DeviceTask & task) Line 1096
	at C:\blender-git\blender\intern\cycles\device\device_cpu.cpp(1096)
blender.exe!ccl::CPUDevice::thread_run(ccl::DeviceTask * task) Line 533
	at C:\blender-git\blender\intern\cycles\device\device_cpu.cpp(533)
[External Code]
blender.exe!ccl::TaskScheduler::thread_run(int thread_id) Line 399
	at C:\blender-git\blender\intern\cycles\util\util_task.cpp(399)
[External Code]
blender.exe!ccl::thread::run(void * arg) Line 53
	at C:\blender-git\blender\intern\cycles\util\util_thread.cpp(53)
[External Code]

@CharlieJolly it appears that when adding the vector math wrap function, the additional c wasn't initialized.

Not sure if this is what is causing the crash, as I was able to render a few frames in my daily build on my cpu.

I tried rendering the file in an MSVC debug mode build. ``` Run-Time Check Failure #3 - The variable 'c' is being used without being initialized. occurred``` ``` blender.exe!ccl::svm_node_vector_math(ccl::KernelGlobals * kg, ccl::ShaderData * sd, float * stack, unsigned int type, unsigned int inputs_stack_offsets, unsigned int outputs_stack_offsets, int * offset) Line 66 at C:\blender-git\blender\intern\cycles\kernel\svm\svm_math.h(66) blender.exe!ccl::svm_eval_nodes(ccl::KernelGlobals * kg, ccl::ShaderData * sd, ccl::PathState * state, float * buffer, ccl::ShaderType type, int path_flag) Line 389 at C:\blender-git\blender\intern\cycles\kernel\svm\svm.h(389) blender.exe!ccl::shader_eval_surface(ccl::KernelGlobals * kg, ccl::ShaderData * sd, ccl::PathState * state, float * buffer, int path_flag) Line 1117 at C:\blender-git\blender\intern\cycles\kernel\kernel_shader.h(1117) blender.exe!ccl::kernel_background_evaluate(ccl::KernelGlobals * kg, ccl::uint4 * input, ccl::float4 * output, int i) Line 512 at C:\blender-git\blender\intern\cycles\kernel\kernel_bake.h(512) blender.exe!ccl::kernel_cpu_sse41_shader(ccl::KernelGlobals * kg, ccl::uint4 * input, ccl::float4 * output, int type, int filter, int i, int offset, int sample) Line 161 at C:\blender-git\blender\intern\cycles\kernel\kernels\cpu\kernel_cpu_impl.h(161) blender.exe!ccl::CPUDevice::thread_shader(ccl::DeviceTask & task) Line 1096 at C:\blender-git\blender\intern\cycles\device\device_cpu.cpp(1096) blender.exe!ccl::CPUDevice::thread_run(ccl::DeviceTask * task) Line 533 at C:\blender-git\blender\intern\cycles\device\device_cpu.cpp(533) [External Code] blender.exe!ccl::TaskScheduler::thread_run(int thread_id) Line 399 at C:\blender-git\blender\intern\cycles\util\util_task.cpp(399) [External Code] blender.exe!ccl::thread::run(void * arg) Line 53 at C:\blender-git\blender\intern\cycles\util\util_thread.cpp(53) [External Code] ``` @CharlieJolly it appears that when adding the vector math wrap function, the additional `c` wasn't initialized. Not sure if this is what is causing the crash, as I was able to render a few frames in my daily build on my cpu.

Added subscriber: @ankitm

434mb, sorry it's big

I don't have the bandwidth to download that file, nor a top notch machine to render lengthy animations.
Further, after not replying for 11 days, I'm tempted to close it.

With all the covid stuff happening I've not spent much time on Blender. I don't have access to RTX but will see if I can quiet the warning.

Cleaned warning in: 1bb7d42cf6

Added subscriber: @zaster

Unfortunately I dont have a RTX card to help more.
When i had a dual GPU setup years ago it sometimes helped to render from command line.
This file also reminds me how brutally slow procedurals are in Cycles...

@ankitm
Sorry for the lack of replying. I didn't realize there was an action item for me.
I've just reformatted my machine. I'll try rendering on a clean version with factory settings of the latest build tonight. Will report back with an answer.

@CharlieJolly Not sure what cleaning or quieting a warning is, but thanks for chipping in! I'll try it tonight.

Just rendered the animation successfully without crashing. Not sure if it was factory settings, or the reformat that did it, but either way we can close this now. Thanks!

Changed status from 'Needs User Info' to: 'Archived'

Added subscriber: @smereces

I have a main workstation with the RTX 3090 and i can´t render a blender animation on it!!! because always crash after some frames rendered!! but the funny is my old workstation have 2 1080 gtx cards all working without crashing! why this is happens with the RTX cards?? :(

Download

What's New

Blender Studio

Manual

Developers Blog

Documentation

Benchmark

Blender Conference

Development Fund

One-time Donations

Consistent crashing while rendering with RTX Titan #74754