Eevee randomly causes system to crash when rendering #95091

New Issue

Malte Hillebrand · 2022-01-20T17:27:36+01:00

Malte Hillebrand commented

2022-01-20 17:27:36 +01:00

System Information
Operating system: Windows-10-10.0.19042-SP0 64 Bits
Graphics card: NVIDIA GeForce RTX 2070 SUPER/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 511.23 (8GB memory)
CPU: Intel Core i9 9900k
RAM: 32GB DDR4

Blender Version
Broken: 3.0.0

Short description of error

I'm new to Blender and currently trying to switch from my usual C4D and Redshift workflow, just to let you know.

I have a fairly simple scene with a 250 frame animation. Everytime I render the animation with Eevee as a .png sequence with an .exr file for the layers, the process causes my system to crash.
The amount of samples seems to correlate with the amount of frames I'm able to render before failure. So I guess it might have something to do with memory.

I'm not sure how that can be as more complex scenes never failed me before using Redshift as a render engine.
ocean_final.blend
The scene makes use of a lot of volumetric light and I also calculate the bloom.

There aren't a lot of vertices involved in the scene, but I'm not sure how I can display a value to give you here.

All drivers are up to date and I also reinstalled Blender.

Exact steps for others to reproduce the error
Not sure, but I attached the .blend file as well as logs created in debug mode.

blender_debug_output.txt

blender_system_info.txt

**System Information** Operating system: Windows-10-10.0.19042-SP0 64 Bits Graphics card: NVIDIA GeForce RTX 2070 SUPER/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 511.23 (8GB memory) CPU: Intel Core i9 9900k RAM: 32GB DDR4 **Blender Version** Broken: 3.0.0 **Short description of error** I'm new to Blender and currently trying to switch from my usual C4D and Redshift workflow, just to let you know. I have a fairly simple scene with a 250 frame animation. Everytime I render the animation with Eevee as a .png sequence with an .exr file for the layers, the process causes my system to crash. The amount of samples seems to correlate with the amount of frames I'm able to render before failure. So I guess it might have something to do with memory. I'm not sure how that can be as more complex scenes never failed me before using Redshift as a render engine. [ocean_final.blend](https://archive.blender.org/developer/F12812889/ocean_final.blend) The scene makes use of a lot of volumetric light and I also calculate the bloom. There aren't a lot of vertices involved in the scene, but I'm not sure how I can display a value to give you here. All drivers are up to date and I also reinstalled Blender. **Exact steps for others to reproduce the error** Not sure, but I attached the .blend file as well as logs created in debug mode. [blender_debug_output.txt](https://archive.blender.org/developer/F12812887/blender_debug_output.txt) [blender_system_info.txt](https://archive.blender.org/developer/F12812888/blender_system_info.txt)

Malte Hillebrand commented

2022-01-20 17:27:36 +01:00

Added subscriber: @etlaM21

Richard Antalik commented

2022-01-20 18:28:26 +01:00

Added subscriber: @iss

Richard Antalik commented

2022-01-20 18:28:26 +01:00

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

Richard Antalik commented

2022-01-20 18:28:26 +01:00

This takes quite a bit of time to render, so I will check later when PC would be idle

In meantime, can you check if this issue happens with latest alpha build from https://builder.blender.org/download/daily/?

This takes quite a bit of time to render, so I will check later when PC would be idle In meantime, can you check if this issue happens with latest alpha build from https://builder.blender.org/download/daily/?

Malte Hillebrand commented

2022-01-20 18:42:46 +01:00

Thank you, I will try it out and report back.

Malte Hillebrand commented

2022-01-20 19:51:22 +01:00

blender_debug_output.txt

blender_system_info.txt

The alpha version crashed before it could save the first frame. But no system shutdown this time.

Edit: Sorry, wrong information. It crashed after saving two frames of the animation.

[blender_debug_output.txt](https://archive.blender.org/developer/F12813129/blender_debug_output.txt) [blender_system_info.txt](https://archive.blender.org/developer/F12813130/blender_system_info.txt) The alpha version crashed before it could save the first frame. But no system shutdown this time. Edit: Sorry, wrong information. It crashed after saving two frames of the animation.

Vladimir commented

2022-01-20 20:26:39 +01:00

Added subscriber: @Wovchick

Malte Hillebrand commented

2022-01-21 00:04:13 +01:00

I just rendered another animation with Eevee and experienced no problems. The sample size, resolution and number of frames were higher.

The scene used volumes as well but didn't make use of fake caustics and volumetric lighting (I think, at least no "god rays").

This is a frame from the scene without problems:

This is one from the crashing scene:

I don't know if that helps, I just want to give as much information as possible. If needed, I can provide the non-crashing Blender file as well.

Also I'm not sure if I should create another post for new information or edit my last one.
Should this count as spam, I will add all the information to the latest post as an edit.

I just rendered another animation with Eevee and experienced no problems. The sample size, resolution and number of frames were higher. The scene used volumes as well but didn't make use of fake caustics and volumetric lighting (I think, at least no "god rays"). This is a frame from the scene without problems: ![outside_test_0212.png](https://archive.blender.org/developer/F12813657/outside_test_0212.png) This is one from the crashing scene: ![animtest_02_0000.png](https://archive.blender.org/developer/F12813661/animtest_02_0000.png) I don't know if that helps, I just want to give as much information as possible. If needed, I can provide the non-crashing Blender file as well. Also I'm not sure if I should create another post for new information or edit my last one. Should this count as spam, I will add all the information to the latest post as an edit.

Malte Hillebrand commented

2022-01-21 10:31:21 +01:00

Changed status from 'Needs User Info' to: 'Needs Developer To Reproduce'

Christian Clavet commented

2022-01-21 17:02:22 +01:00

Added subscriber: @christian-clavet

Christian Clavet commented

2022-01-21 17:02:22 +01:00

Hi, By curiosity, I downloaded your blender file and tried to render it on my work PC. It's running on Windows 10, has only 8Gb ram, and old I3 CPU and a Nvidia GTX1050. So far it has been rendering, and no crashes. (Using Blender 3.0)
This is frame 103

This is frame 124

Still rendering, I'll wait until it complete and report back...
Note:
Windows is telling me that Blender is not responding, but Blender is working ok. It should report more often to the OS while rendering...

Hi, By curiosity, I downloaded your blender file and tried to render it on my work PC. It's running on Windows 10, has only 8Gb ram, and old I3 CPU and a Nvidia GTX1050. So far it has been rendering, and no crashes. (Using Blender 3.0) This is frame 103 ![image.png0103.png](https://archive.blender.org/developer/F12814587/image.png0103.png) This is frame 124 ![image.png0124.png](https://archive.blender.org/developer/F12814590/image.png0124.png) Still rendering, I'll wait until it complete and report back... Note: Windows is telling me that Blender is not responding, but Blender is working ok. It should report more often to the OS while rendering... ![image.png](https://archive.blender.org/developer/F12814596/image.png)

Raimund Klink commented

2022-01-26 11:32:50 +01:00

Added subscriber: @Raimund58

Malte Hillebrand commented

2022-01-28 13:32:56 +01:00

The problem stilll persist with the newest Blender version, 3.0.1. My system shut down after 20 frames.

The **problem stilll persist with the newest Blender version, 3.0.1**. My system shut down after 20 frames.

Raimund Klink commented

2022-01-28 14:09:34 +01:00

Changed status from 'Needs Developer To Reproduce' to: 'Needs User Info'

Raimund Klink commented

2022-01-28 14:09:34 +01:00

I can not imagine why Blender would cause this. And I can not reproduce it.
Could it be thermal issues? Or is the power supply too weak?
Can you run other GPU intensive Game benchmarks without crashing the system?
Is your system also crashing if you render with Cycles for 20< minutes?

I can not imagine why Blender would cause this. And I can not reproduce it. Could it be thermal issues? Or is the power supply too weak? Can you run other GPU intensive Game benchmarks without crashing the system? Is your system also crashing if you render with Cycles for 20< minutes?

Malte Hillebrand commented

2022-01-28 14:31:29 +01:00

Changed status from 'Needs User Info' to: 'Needs Developer To Reproduce'

Malte Hillebrand commented

2022-01-28 14:31:29 +01:00

I can imagine that it is hard to reproduce, sorry about that.

When I run Unigine Heaven , my maximum GPU temp is 74°C. I average around 160FPS.
You can see the results attached.

I don't know a lot about benchmarking, so if you have another recommendation for GPU stress testing I'm willing to try and report back!

About the power supply:
I can't 100% say how much of an overhead I have, but I build a new PC in December 2019 and still remember buying a new power supply and calculating the consumption so that I would still have some room left.

This specific scene I haven't tried with Cycles for more than 20 minutes. I first rendered it with Cycles and it took about 6 minutes for a frame, so I killed it after two frames and switched to Eevee (just so I could produce it in time).
I did however render other scenes with Cycles for a couple of hours.

Do you want me to try Cycles on this scene as well?

Unigine_Heaven_Benchmark_4.0_20220128_1420.html

I can imagine that it is hard to reproduce, sorry about that. When I run [Unigine Heaven ](https://benchmark.unigine.com/heaven), my maximum GPU temp is 74°C. I average around 160FPS. You can see the results attached. I don't know a lot about benchmarking, so if you have another recommendation for GPU stress testing I'm willing to try and report back! About the power supply: I can't 100% say how much of an overhead I have, but I build a new PC in December 2019 and still remember buying a new power supply and calculating the consumption so that I would still have some room left. This specific scene I haven't tried with Cycles for more than 20 minutes. I first rendered it with Cycles and it took about 6 minutes for a frame, so I killed it after two frames and switched to Eevee (just so I could produce it in time). I did however render other scenes with Cycles for a couple of hours. Do you want me to try Cycles on this scene as well? [Unigine_Heaven_Benchmark_4.0_20220128_1420.html](https://archive.blender.org/developer/F12831015/Unigine_Heaven_Benchmark_4.0_20220128_1420.html)

Raimund Klink commented

2022-01-28 14:35:39 +01:00

I did however render other scenes with Cycles for a couple of hours.
Do you want me to try Cycles on this scene as well?

No, that should be fine.

>I did however render other scenes with Cycles for a couple of hours. >Do you want me to try Cycles on this scene as well? No, that should be fine.

Malte Hillebrand commented

2022-01-28 17:22:30 +01:00

I also used the 3DMark Demo now for benchmarking, the Time Spy test.
I didn't have any visual problems, my GPU temp went to 73°C max.

Results are attached, as well as the HWMonitor stats.

I know that Blender stats would be of more use probably, but unfortunately,

HWMonitor.txt

I don't know a tool to log all the stats and save them so I can access them after crashing.

I also used the 3DMark Demo now for benchmarking, the Time Spy test. I didn't have any visual problems, my GPU temp went to 73°C max. Results are attached, as well as the HWMonitor stats. I know that Blender stats would be of more use probably, but unfortunately,![3DMark_01.PNG](https://archive.blender.org/developer/F12831355/3DMark_01.PNG) ![3DMark_03.PNG](https://archive.blender.org/developer/F12831354/3DMark_03.PNG) [HWMonitor.txt](https://archive.blender.org/developer/F12831353/HWMonitor.txt) ![3DMark_02.PNG](https://archive.blender.org/developer/F12831352/3DMark_02.PNG) I don't know a tool to log all the stats and save them so I can access them after crashing.

Malte Hillebrand commented

2022-01-28 17:48:58 +01:00

I also just tried rendering the same scene with both LTS versions and experienced the same problem.

Malte Hillebrand commented

2022-01-28 17:56:45 +01:00

In #95091#1296956, @Raimund58 wrote:
Is your system also crashing if you render with Cycles for 20< minutes?

Correction, sorry for the misinformation before: It now also crashes with Cycles (GPU compute), after the second frame.
So it must be something I changed while switching from real caustics and volumetric lighting to fake ones for Eevee.
I don't have the old .blend file anymore, so I can't make out the exact cause of it.

Logs are attached.

Edit: With Cycles there is no system shutdown, just Blender crashing.

blender_debug_output.txt

blender_system_info.txt

> In #95091#1296956, @Raimund58 wrote: > Is your system also crashing if you render with Cycles for 20< minutes? Correction, sorry for the misinformation before: It now also crashes with Cycles (GPU compute), after the second frame. So it must be something I changed while switching from real caustics and volumetric lighting to fake ones for Eevee. I don't have the old .blend file anymore, so I can't make out the exact cause of it. Logs are attached. Edit: With Cycles there is no system shutdown, just Blender crashing. [blender_debug_output.txt](https://archive.blender.org/developer/F12831402/blender_debug_output.txt) [blender_system_info.txt](https://archive.blender.org/developer/F12831401/blender_system_info.txt)

Malte Hillebrand commented

2022-01-28 18:24:34 +01:00

Now I also tried rendering it with Eevee in 3.0,1 again, this time with ALL add-ons disabled and got no system crash at least.
But Blender crashes after two frames (was after ~20 frames with add-ons before).

Logs:
blender_system_info.txt

blender_debug_output.txt

I'm sorry, but I really have no clue what to do anymore.
It seems to always crash after saving the latest frame when restarting the render process on the next frame.

The last thing I will now try is rendering it with Cycles and the integrated graphics.
If someone can tell me how to disable my NVIDIA card for Eevee rendering as well, I will try that to and report back.

Now I also tried rendering it with Eevee in 3.0,1 again, this time with ALL add-ons disabled and got no system crash at least. But Blender crashes after two frames (was after ~20 frames with add-ons before). Logs: [blender_system_info.txt](https://archive.blender.org/developer/F12831425/blender_system_info.txt) [blender_debug_output.txt](https://archive.blender.org/developer/F12831424/blender_debug_output.txt) I'm sorry, but I really have no clue what to do anymore. It seems to always crash after saving the latest frame when restarting the render process on the next frame. The last thing I will now try is rendering it with Cycles and the integrated graphics. If someone can tell me how to disable my NVIDIA card for Eevee rendering as well, I will try that to and report back.

Raimund Klink commented

2022-01-29 00:44:19 +01:00

Added subscribers: @fclem, @Jeroen-Bakker

Raimund Klink commented

2022-01-29 00:44:19 +01:00

Maybe we can call @fclem or @Jeroen-Bakker for help.
I at least am out of ideas.

Maybe we can call @fclem or @Jeroen-Bakker for help. I at least am out of ideas.

Malte Hillebrand commented

2022-01-29 17:05:31 +01:00

Thank you for trying so far Raimund!

It got even scarier, as it does not seem to be an issue related to my graphics card:

I tried rendering it with Cycles and the integrated graphicsand it crashed after saving the second frame again. No add-ons enabled.

Logs are attached.

blender_debug_output.txt

blender_system_info.txt

Thank you for trying so far Raimund! It got even scarier, as it does not seem to be an issue related to my graphics card: I tried **rendering it with Cycles and the integrated graphics**and it **crashed after saving the second frame** again. No add-ons enabled. Logs are attached. [blender_debug_output.txt](https://archive.blender.org/developer/F12833308/blender_debug_output.txt) [blender_system_info.txt](https://archive.blender.org/developer/F12833307/blender_system_info.txt)

Raimund Klink commented

2022-01-29 19:34:38 +01:00

Wait, you have an integrated GPU?
Please disable it (in the device manager) and try again.

Wait, you have an integrated GPU? Please disable it (in the device manager) and try again.

Malte Hillebrand commented

2022-01-29 20:19:15 +01:00

In #95091#1297565, @Raimund58 wrote:
Wait, you have an integrated GPU?
Please disable it (in the device manager) and try again.

I think I misinterpreted the Cycles settings, I can't find an integrated GPU in the device manager:

What I meant was, that I only rendered with the i9900k here in Cycles and it still crashed:

> In #95091#1297565, @Raimund58 wrote: > Wait, you have an integrated GPU? > Please disable it (in the device manager) and try again. I think I misinterpreted the Cycles settings, I can't find an integrated GPU in the device manager: ![devicemanager.PNG](https://archive.blender.org/developer/F12833865/devicemanager.PNG) What I meant was, that I only rendered with the i9900k here in Cycles and it still crashed: ![cycles.PNG](https://archive.blender.org/developer/F12833859/cycles.PNG)

Malte Hillebrand commented

2022-02-02 23:46:30 +01:00

I finally completed my first render of the 250 frames without any crash!

For this I turned down a bunch of settings, so I'm still not sure of the exact cause:

Volumetrics End down to 250m (was 500m)
Volumetic Lighting Light Clamping down to 256 (was 1024 I believe)
Volumetric Shadows Samples down to 32 (was 256 I think)

My logical guess would be that the Light Clamping would make sense as it could be responsible for a cache overflow?

I finally completed my first render of the 250 frames without any crash! For this I turned down a bunch of settings, so I'm still not sure of the exact cause: - Volumetrics End down to 250m (was 500m) - Volumetic Lighting Light Clamping down to 256 (was 1024 I believe) - Volumetric Shadows Samples down to 32 (was 256 I think) My logical guess would be that the Light Clamping would make sense as it could be responsible for a cache overflow?

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

Eevee randomly causes system to crash when rendering #95091