Regression: Crashes default cube scene when rendering #112838

Closed
opened 2023-09-25 11:33:29 +02:00 by Mark Lucas · 5 comments

System Information
Operating system: Windows 11 Home 22H2 Build: 22621.2283
Graphics card: NVIDIA Geforce RTX 4090

Blender Version
Broken: 3.6.3, d3e6b08276, 3.6.1, 8bda729ef4, 4.0.0 Alpha
Worked: 3.3.11 (master, Hash 6a3240da1d)

Short description of error
Over the last six months, Blender has become less stable with more crashes/BDOS. I could have put this down to throwing the kitchen sink at it. I stopped using it daily. After the last update (3.6.3) I now find that it crashes when I render using Cycles. (EVEE seems fine)

I have a lot of add-ons, first thing I did was uninstall and reinstall Blender so that none of my add-ons are possibly the cause.

Steps to reproduce

  1. From the default startup, switch to Cycles rendering (tested with GPU and CPU separately; both crash)
  2. Render cube
  3. Render begins. There's usually a pause in the sample count, then either crash to desktop, occasionally BSOD. With Blender 4 I tested a large scene and got a hardware reset.)

My first assumption was a GPU bug:
I reinstalled the GPU driver
I then cleaned out the driver and manually rolled back to an earlier driver.
I then realised that crashing occurred even when using Cycles with the CPU

I performed some load testing on the GPU, nonetheless. No issues were found.

I believe that when first testing 3.6.3 I did get some completed renders, then maybe after crashes, it now always fails to render with cycles.

Logging is chatty but I don't know if the message "INFO (gpu.debug): Notification : Texture state usage warning: The texture object (0) bound to texture image unit 0 does not have a defined base level and cannot be used for texture mapping." is even related to the problem.

Thanks in advance!

**System Information** Operating system: Windows 11 Home 22H2 Build: 22621.2283 Graphics card: NVIDIA Geforce RTX 4090 **Blender Version** Broken: 3.6.3, d3e6b08276ba, 3.6.1, 8bda729ef4dc, 4.0.0 Alpha Worked: 3.3.11 (master, Hash 6a3240da1dc8) **Short description of error** Over the last six months, Blender has become less stable with more crashes/BDOS. I could have put this down to throwing the kitchen sink at it. I stopped using it daily. After the last update (3.6.3) I now find that it crashes when I render using Cycles. (EVEE seems fine) I have a lot of add-ons, first thing I did was uninstall and reinstall Blender so that none of my add-ons are possibly the cause. **Steps to reproduce** 1. From the default startup, switch to Cycles rendering (tested with GPU and CPU separately; both crash) 2. Render cube 3. Render begins. There's usually a pause in the sample count, then either crash to desktop, occasionally BSOD. With Blender 4 I tested a large scene and got a hardware reset.) My first assumption was a GPU bug: I reinstalled the GPU driver I then cleaned out the driver and manually rolled back to an earlier driver. I then realised that crashing occurred even when using Cycles with the CPU I performed some load testing on the GPU, nonetheless. No issues were found. I believe that when first testing 3.6.3 I did get some completed renders, then maybe after crashes, it now always fails to render with cycles. Logging is chatty but I don't know if the message "INFO (gpu.debug): Notification : Texture state usage warning: The texture object (0) bound to texture image unit 0 does not have a defined base level and cannot be used for texture mapping." is even related to the problem. Thanks in advance!
Mark Lucas added the
Status
Needs Triage
Type
Report
Priority
Normal
labels 2023-09-25 11:33:29 +02:00
Iliya Katushenock changed title from Blender 3.6.x crashes (default cube scene) when rendering with cycles (both GPU and CPU) to Regression: Crashes default cube scene when rendering 2023-09-25 13:25:01 +02:00
Iliya Katushenock added the
Interest
Render & Cycles
label 2023-09-25 13:25:04 +02:00
Iliya Katushenock added this to the 3.6 LTS milestone 2023-09-25 13:25:09 +02:00
Author

Update: It's possible that my CPU (i9-13900k) has a subtle fault. I'm currently investigating.
Windows is reporting WHEA-Logger event 19s:

Reported by component: Processor Core
Error Source: Corrected Machine Check
Error Type: Translation Lookaside Buffer Error
Processor APIC ID: 16

Reported by component: Processor Core
Error Source: Corrected Machine Check
Error Type: Internal parity error
Processor APIC ID: 40

Update: It's possible that my CPU (i9-13900k) has a subtle fault. I'm currently investigating. Windows is reporting WHEA-Logger event 19s: Reported by component: Processor Core Error Source: Corrected Machine Check Error Type: Translation Lookaside Buffer Error Processor APIC ID: 16 Reported by component: Processor Core Error Source: Corrected Machine Check Error Type: Internal parity error Processor APIC ID: 40

Thanks for the report, @MarkLucas.

From the attached logs, what seems most relevant to identifying the problem is the blender3.6.1.crash.txt

Apparently the crash happens on the CPU. But it still doesn't seem like enough information to us confirm the bug and forward to the developers :\

  • Is this problem consistent and always happens with the default Cube?
  • Can you try with Factory Settings? Go to File → Defaults → Load Factory Settings and then load your file to see if you still can reproduce this issue.
Thanks for the report, @MarkLucas. From the attached logs, what seems most relevant to identifying the problem is the [blender3.6.1.crash.txt](/attachments/31425740-2077-47f8-a99e-7c8190117006) Apparently the crash happens on the CPU. But it still doesn't seem like enough information to us confirm the bug and forward to the developers :\ - Is this problem consistent and always happens with the default Cube? - Can you try with Factory Settings? Go to File → Defaults → Load Factory Settings and then load your file to see if you still can reproduce this issue.
Germano Cavalcante added
Status
Needs Information from User
and removed
Status
Needs Triage
labels 2023-09-25 23:22:37 +02:00
Author

Sorry, Germano

I hadn't clarified that one of the tests was conducted using the factory defaults shell script in the installation directory.

Here goes, using 3.6.1 again.

  1. Start Blender.
  2. Load Factory Settings.
  3. Render (No problem, as Evee is the default, which seems to work okay).
  4. Switch to Cycles, Supported, CPU under the Properties Render tab.
  5. Render (the render completes successfully).
  6. Switch to GPU, Supported under the Properties Render tab, selecting CUDA Render Device under Properties.
  7. Render ( the render completes successfully).
  8. Open up a slightly larger scene with a high poly mesh.
  9. Render (the render completes successfully).

I declare this NOT A BUG. Clearly, I had a persistent corruption that has now either fixed itself or has been fixed by my latest round of driver and BIOS refreshes.

Many thanks for your time and diligence.

Sorry, Germano I hadn't clarified that one of the tests was conducted using the factory defaults shell script in the installation directory. Here goes, using 3.6.1 again. 1. Start Blender. 2. Load Factory Settings. 3. Render (No problem, as Evee is the default, which seems to work okay). 4. Switch to Cycles, Supported, CPU under the Properties Render tab. 5. Render (the render completes successfully). 6. Switch to GPU, Supported under the Properties Render tab, selecting CUDA Render Device under Properties. 7. Render ( the render completes successfully). 8. Open up a slightly larger scene with a high poly mesh. 9. Render (the render completes successfully). I declare this **NOT A BUG**. Clearly, I had a persistent corruption that has now either fixed itself or has been fixed by my latest round of driver and BIOS refreshes. Many thanks for your time and diligence.
Blender Bot added
Status
Archived
and removed
Status
Needs Information from User
labels 2023-09-26 00:49:35 +02:00

Please check if this happens with alpha build from https://builder.blender.org/download/daily/

Well nevermind :) glad you found solution.

Please check if this happens with alpha build from https://builder.blender.org/download/daily/ Well nevermind :) glad you found solution.
Author

blender-4.0.0-alpha+main.2aa393e72771\blender

Tested and working!

blender-4.0.0-alpha+main.2aa393e72771\\blender Tested and working!
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#112838
No description provided.