**SOLVED** [v3.0 and up] Program/computer crash when choosing Cycles, then going to Material Properties and expanding the Preview window. No problems with 2.93.8. #102626

New Issue

Ivan · 2022-11-19T20:34:25+01:00

Ivan commented

2022-11-19 20:34:25 +01:00

System Information
Operating system: Windows 10 64-bit
CPU: AMD Ryzen 9 5900X
Graphics card: NVIDIA RTX 3090 Ti (driver version: 526.98, previously had version 517.48 when I first experienced the problem. Both clean driver installs.)

Blender Version
Broken: 3.0 and up. I've tried 3.0.0, 3.2.0, and the latest 3.3.1 2022-10-04 18:35, b292cfe5a9.
Working: 2.93.8, 2022-02-01, 21:14, 09da7f489a, master

(I'm a new user so I apologize if I overlook providing certain information.)
This happens to me every time I use 3.0 and up. This is with a fresh, clean install. and a brand new general file with the default cube shown.
I have my Cycle Render settings for CUDA and OptiX with both my GPU and CPU enabled.
In the Properties, I click on Render Properties.
For Render Settings, I change Eevee to Cycles.
I change device CPU to GPU Compute.
I change nothing else.
I click on Material Properties tab.
I click on Preview to expand the window with the default sphere showing. The sphere starts pixelating into view as it tries to render as a solid image.
Then, everything crashes.
Sometimes the program crashes to the desktop. Most other times, however, it crashes my entire computer and it restarts.
I can click on Viewport Shading: Rendered in the 3D view and not have any crashes. I can pan around the cube without a problem. Only when I want to view the Preview window.

I have also included the crash log from version 3.0 along with 3.3.1. Attempting to run the blender_debug_gpu_glitchworkaround.cmd doesn't fix the issue, rather the entire computer crashes and reboots, so the only crash log I got from that was in the tmp folder. I've included it, as well. It's labeled as test.crash.txt.

test.crash.txt

blender.crash3.0.txt

blender.crash.txt

blender_debug_output.txt

blender_system_info.txt

**System Information** Operating system: Windows 10 64-bit CPU: AMD Ryzen 9 5900X Graphics card: NVIDIA RTX 3090 Ti (driver version: 526.98, previously had version 517.48 when I first experienced the problem. Both clean driver installs.) **Blender Version** Broken: **3.0** and up. I've tried **3.0.0**, **3.2.0**, and the latest **3.3.1** 2022-10-04 18:35, b292cfe5a936. Working: **2.93.8**, 2022-02-01, 21:14, 09da7f489ad9, master (I'm a new user so I apologize if I overlook providing certain information.) This happens to me every time I use 3.0 and up. This is with a fresh, clean install. and a brand new general file with the default cube shown. I have my Cycle Render settings for CUDA and OptiX with both my GPU and CPU enabled. In the **Properties**, I click on **Render Properties**. For **Render Settings**, I change **Eevee** to **Cycles**. I change device **CPU** to **GPU Compute**. I change nothing else. I click on **Material Properties** tab. I click on **Preview** to expand the window with the default sphere showing. The sphere starts pixelating into view as it tries to render as a solid image. Then, everything crashes. Sometimes the program crashes to the desktop. Most other times, however, it crashes my entire computer and it restarts. I can click on **Viewport Shading: Rendered** in the 3D view and not have any crashes. I can pan around the cube without a problem. Only when I want to view the **Preview** window. I have also included the crash log from version 3.0 along with 3.3.1. Attempting to run the **blender_debug_gpu_glitchworkaround.cmd** doesn't fix the issue, rather the entire computer crashes and reboots, so the only crash log I got from that was in the tmp folder. I've included it, as well. It's labeled as **test.crash.txt**. [test.crash.txt](https://archive.blender.org/developer/F13948039/test.crash.txt) [blender.crash3.0.txt](https://archive.blender.org/developer/F13947957/blender.crash3.0.txt) [blender.crash.txt](https://archive.blender.org/developer/F13946978/blender.crash.txt) [blender_debug_output.txt](https://archive.blender.org/developer/F13946979/blender_debug_output.txt) [blender_system_info.txt](https://archive.blender.org/developer/F13946980/blender_system_info.txt)

Ivan commented

2022-11-19 20:34:25 +01:00

Added subscriber: @ChiliBeef

Ivan changed title from ~~[v3.2 & 3.3.1] Program/computer crash when choosing Cycles, then going to Material Properties and expanding the Preview window. No problems with 2.93.8.~~ to [v3.0 and up] Program/computer crash when choosing Cycles, then going to Material Properties and expanding the Preview window. No problems with 2.93.8.

2022-11-19 22:42:04 +01:00

Ivan commented

2022-11-20 02:28:12 +01:00

I've tried one more time with the blender_debug_gpu_glitchworkaround.cmd. I can apply a texture to the cube and it'll display okay. Only expanding the Preview window will it immediately crash my computer and cause a reboot, which it did. These two crash logs are the only two I could find after that.
blender_debug_output.txt

blender_system_info.txt

I've tried one more time with the blender_debug_gpu_glitchworkaround.cmd. I can apply a texture to the cube and it'll display okay. Only expanding the Preview window will it immediately crash my computer and cause a reboot, which it did. These two crash logs are the only two I could find after that. [blender_debug_output.txt](https://archive.blender.org/developer/F13948081/blender_debug_output.txt) [blender_system_info.txt](https://archive.blender.org/developer/F13948082/blender_system_info.txt)

Ivan changed title from ~~[v3.0 and up] Program/computer crash when choosing Cycles, then going to Material Properties and expanding the Preview window. No problems with 2.93.8.~~ to **SOLVED** [v3.0 and up] Program/computer crash when choosing Cycles, then going to Material Properties and expanding the Preview window. No problems with 2.93.8.

2022-11-21 00:24:32 +01:00

Ivan commented

2022-11-21 00:25:51 +01:00

I was able to fix the issue. I went into my BIOS settings and enabled Resizable BAR. I also went to my auto overclock setting and changed it from TPU II to TPU I. Maybe one or both of those fixed the issue, but no more crashing now.