Blender Instantly Crashes When Rendering Cycles #116277

Open
opened 2023-12-17 17:41:02 +01:00 by Treisor · 14 comments

System Information
Operating system: 13 th Gen Intel(R) Core (TM) I9 13900k
Graphics card: Nvidia 3070 TI founder edition

Blender Version
Broken: 3.4.1, master, 2023-17-12
Worked: 3.4.1

Short description of error :

as soon as I launch my rendering, the projects close by themselves without any error message, this can occur in the first frame as well as in the fifth. Whether I use optix or openimagedenoise, the rendering spits out every time

Exact steps for others to reproduce the error

Just run the render and it will happen again

Ps: I specify that I installed the latest version of the graphics driver properly, and that this also happens on another machine

**System Information** Operating system: 13 th Gen Intel(R) Core (TM) I9 13900k Graphics card: Nvidia 3070 TI founder edition **Blender Version** Broken: 3.4.1, master, 2023-17-12 Worked: 3.4.1 **Short description of error :** as soon as I launch my rendering, the projects close by themselves without any error message, this can occur in the first frame as well as in the fifth. Whether I use optix or openimagedenoise, the rendering spits out every time **Exact steps for others to reproduce the error** Just run the render and it will happen again Ps: I specify that I installed the latest version of the graphics driver properly, and that this also happens on another machine
Treisor added the
Status
Needs Triage
Priority
Normal
Type
Report
labels 2023-12-17 17:41:02 +01:00
Member

Hi, thanks for the report. I'm not able to confirm the crash in 4.1 Could it be due to denoiser? Can you share crash logs:

Please open Blender's installation directory and double click on the blender_debug_gpu.cmd. This will start Blender in debug mode and create log files. Try to reproduce the
error again. Once it crashes or you close Blender manually the Windows Explorer should open and show you up to two files, a debug log and the system information. Add them
to your bug report by clicking on the upload button as shown in the screenshot below or via drag and drop. Please also upload the crash log located in C:\Users\[your username]\AppData\Local\Temp\[project name].crash.txt (or simply type %TEMP% into the path bar of the Windows Explorer).2019_12_04_upload_icon_developer_blender_org.png

Hi, thanks for the report. I'm not able to confirm the crash in 4.1 Could it be due to denoiser? Can you share crash logs: > Please open Blender's installation directory and double click on the `blender_debug_gpu.cmd`. This will start Blender in debug mode and create log files. Try to reproduce the error again. Once it crashes or you close Blender manually the Windows Explorer should open and show you up to two files, a debug log and the system information. Add them to your bug report by clicking on the upload button as shown in the screenshot below or via drag and drop. Please also upload the crash log located in `C:\Users\[your username]\AppData\Local\Temp\[project name].crash.txt` (or simply type `%TEMP%` into the path bar of the Windows Explorer).![2019_12_04_upload_icon_developer_blender_org.png](https://archive.blender.org/developer/F8190038/2019_12_04_upload_icon_developer_blender_org.png)
Pratik Borhade added
Status
Needs Information from User
and removed
Status
Needs Triage
labels 2023-12-18 07:00:03 +01:00
Member

3.4.1 is outdated and not maintained anymore. Please check again in 3.6.x or 4.1 builds: https://builder.blender.org/download/daily/

3.4.1 is outdated and not maintained anymore. Please check again in 3.6.x or 4.1 builds: https://builder.blender.org/download/daily/
Author

Hello thank you for your feedback! I just tried this on version 3.6.7 and it happens again, I also tried on 4.1 but each time blender closes by itself as soon as I start rendering.
I think it comes from the denoiser i made sure I have the latest ndvidia update just in case.

Hello thank you for your feedback! I just tried this on version 3.6.7 and it happens again, I also tried on 4.1 but each time blender closes by itself as soon as I start rendering. I think it comes from the denoiser i made sure I have the latest ndvidia update just in case.
Blender Bot added
Status
Archived
and removed
Status
Needs Information from User
labels 2023-12-18 21:56:07 +01:00
Treisor reopened this issue 2023-12-18 21:56:21 +01:00
Blender Bot added
Status
Needs Triage
and removed
Status
Archived
labels 2023-12-18 21:56:24 +01:00
Member

Thanks. Also upload C:\Users\Micke\AppData\Local\Temp\Hair scene 11.crash.txt

Thanks. Also upload `C:\Users\Micke\AppData\Local\Temp\Hair scene 11.crash.txt`
Pratik Borhade added
Status
Needs Information from User
and removed
Status
Needs Triage
labels 2023-12-19 04:37:14 +01:00
Author

Here is the file in question, if you need anything else I remain at your disposal !

Here is the file in question, if you need anything else I remain at your disposal !
Member

Thanks. Can you launch blender on single thread from command line with -t 1 argument to verify the crash?
Threading is involved here in crash logs.

Also, can you clarify whether it occurs in viewport render or final render? If final render, is it during image render or complete animation render?
Which acceleration option is used during crash? (CUDA or OptiX)

Thanks. Can you launch blender on single thread from command line with `-t 1` argument to verify the crash? Threading is involved here in crash logs. Also, can you clarify whether it occurs in viewport render or final render? If final render, is it during image render or complete animation render? Which acceleration option is used during crash? (CUDA or OptiX)
Author

In general this happens during the final rendering of the complete animation, but it can also happen when I start playing the timeline with the optiX denoiser in final view.

I must mark the command -T1 on the cmd of blender_debug_gpu.cmd ?

In general this happens during the final rendering of the complete animation, but it can also happen when I start playing the timeline with the optiX denoiser in final view. I must mark the command -T1 on the cmd of blender_debug_gpu.cmd ?
Member

@Treisor , open directory in command line where blender.exe is installed (cd file_path)
then run blender.exe -t 1

@Treisor , open directory in command line where blender.exe is installed (`cd file_path`) then run `blender.exe -t 1`
Author

I just tried your method and I didn't have a crash during the final rendering, Any idea where this could come from?

I just tried your method and I didn't have a crash during the final rendering, Any idea where this could come from?
Member

It's threading related issue.

It's threading related issue.
Author

Hello, I hope you had a good end of year holiday and I wish you a happy new year!
Can I provide you with more information or guidance to try to find the problem?

Hello, I hope you had a good end of year holiday and I wish you a happy new year! Can I provide you with more information or guidance to try to find the problem?
Member

Guess we will have to wait until cycles devs will look at this.

Guess we will have to wait until cycles devs will look at this.

Just to add to this, I'm having the same issue - reset my Windows, reinstalled all drivers etc.

Specs:
OS: Windows 11 Home 64-bit (10.0, Build 22631)
CPU: Intel(R) Core(TM) i9-14900K (32 CPUs), 3.2 GHZ
Memory: 32 GB DDR5
GPU: Nvidia RTX 4080

I was very close to pulling all my hair out until I tried your above suggestion to run Blender.exe -t 1.

So far, I'm frame 19 of 100 without any crashes or bluescreens (Before I could not render more than a few frames of an animation I previously successfully rendered on a 1070 with 16GB Ram).

To confirm, other than it being slower, am I okay to be rendering on (I assume) one thread as a work around while we wait for the devs to comment?

Just to add to this, I'm having the same issue - reset my Windows, reinstalled all drivers etc. Specs: OS: Windows 11 Home 64-bit (10.0, Build 22631) CPU: Intel(R) Core(TM) i9-14900K (32 CPUs), 3.2 GHZ Memory: 32 GB DDR5 GPU: Nvidia RTX 4080 I was very close to pulling all my hair out until I tried your above suggestion to run Blender.exe -t 1. So far, I'm frame 19 of 100 without any crashes or bluescreens (Before I could not render more than a few frames of an animation I previously successfully rendered on a 1070 with 16GB Ram). To confirm, other than it being slower, am I okay to be rendering on (I assume) one thread as a work around while we wait for the devs to comment?
Author

Hello, I'm bringing up the topic again since I haven't received a response yet.
The problem is still there, and unfortunately, even with the "cmd blender.exe -t 1" trick,

Blender crashes without any reason during rendering but also on the viewport.
I am sending you the .txt of the crash, if you have any suggestions, I'm all ears.

I'm starting to get desperate; I've never had this kind of problem in the past.

Hello, I'm bringing up the topic again since I haven't received a response yet. The problem is still there, and unfortunately, even with the "cmd blender.exe -t 1" trick, Blender crashes without any reason during rendering but also on the viewport. I am sending you the .txt of the crash, if you have any suggestions, I'm all ears. I'm starting to get desperate; I've never had this kind of problem in the past.
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
3 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#116277
No description provided.