Blender Crashes moving any object #116872

New Issue

David-Richardson · 2024-01-07T17:46:02+01:00

David-Richardson commented

2024-01-07 17:46:02 +01:00

System Information
Operating system: Windows-10-10.0.19045-SP0 64 Bits
Graphics card: NVIDIA GeForce RTX 3070 Laptop GPU/PCIe/SSE2 NVIDIA Corporation 4.6.0 NVIDIA 546.31

Blender Version
Broken: version: 4.0.2, branch: blender-v4.0-release, commit date: 2023-12-05 07:41, hash: 9be62e85b727
Worked: (newest version of Blender that worked as expected)

Short description of error
Whenever I open Blender and attempt to move the cube, Blender will crash. So far I have taken the below steps to try to resolve the issue.

Took out each stick of Ram and ran and memory test on each stick and then both together.
Attempted other versions of Blender and video card drivers.
Did a complete wipe of video card drivers and a re-install of the newest video card driver (With Nvidia support)

Exact steps for others to reproduce the error
Anytime I open Blender the problem persists.

Any help is appreciated as my son needs computer and Blender for university.

**System Information** Operating system: Windows-10-10.0.19045-SP0 64 Bits Graphics card: NVIDIA GeForce RTX 3070 Laptop GPU/PCIe/SSE2 NVIDIA Corporation 4.6.0 NVIDIA 546.31 **Blender Version** Broken: version: 4.0.2, branch: blender-v4.0-release, commit date: 2023-12-05 07:41, hash: `9be62e85b727` Worked: (newest version of Blender that worked as expected) **Short description of error** Whenever I open Blender and attempt to move the cube, Blender will crash. So far I have taken the below steps to try to resolve the issue. 1. Took out each stick of Ram and ran and memory test on each stick and then both together. 2. Attempted other versions of Blender and video card drivers. 3. Did a complete wipe of video card drivers and a re-install of the newest video card driver (With Nvidia support) **Exact steps for others to reproduce the error** Anytime I open Blender the problem persists. Any help is appreciated as my son needs computer and Blender for university.

blender_debug_output.txt

32 KiB

blender_system_info.txt

21 KiB

David-Richardson added the

labels 2024-01-07 17:46:03 +01:00

funty commented

2024-01-08 02:11:03 +01:00

Hi,

Do you know if any version of Blender has ever worked on this laptop? If so, can you install that version and see if it works.

Thanks.

Hi, Do you know if any version of Blender has ever worked on this laptop? If so, can you install that version and see if it works. Thanks.

Pratik Borhade commented

2024-01-08 05:22:51 +01:00

Hi, thanks for the report. It seems crash.txt is not generated. Can you verify the crash with GPU workarounds enabled blender_debug_gpu_glitchworkaround.cmd and with factory settings blender_factory_startup.cmd

Hi, thanks for the report. It seems `crash.txt` is not generated. Can you verify the crash with GPU workarounds enabled `blender_debug_gpu_glitchworkaround.cmd` and with factory settings `blender_factory_startup.cmd`

Pratik Borhade added

Status

Needs Information from User

and removed

Status

Needs Triage

labels 2024-01-08 05:23:01 +01:00

Pratik Borhade commented

2024-01-08 05:24:16 +01:00

Graphics card: NVIDIA GeForce RTX 3070 Laptop

Have you tried launching blender on iGPU? Does it crash after doing that?

> Graphics card: NVIDIA GeForce RTX 3070 Laptop Have you tried launching blender on iGPU? Does it crash after doing that?

David-Richardson commented

2024-01-08 17:14:48 +01:00

I had been able to use what I believe was Blender 3.5 using the onboard Intel graphics card. With this I was able to make a model in Rhino and then put the data into blender to create animation. The render time was extremely long as expected using the intel card. Unfortunately this does not work now either as I can not import data in Blender 3.5 without the program crashing.

I was able to import the project into blender 4.0, but when i go to move an object, blender 4.0 crashes also.

I have attached the logs from the Glitchworkaround and factory startup test, both which resulted in a crash when just attempting to move the initial cube.

Ultimately, I am trying to decide if something has happened with the GPU. When i run a stress test on the GPU, it preforms the entire test and keeps the temperature in the acceptable range.

Thank you for the reply.

I had been able to use what I believe was Blender 3.5 using the onboard Intel graphics card. With this I was able to make a model in Rhino and then put the data into blender to create animation. The render time was extremely long as expected using the intel card. Unfortunately this does not work now either as I can not import data in Blender 3.5 without the program crashing. I was able to import the project into blender 4.0, but when i go to move an object, blender 4.0 crashes also. I have attached the logs from the Glitchworkaround and factory startup test, both which resulted in a crash when just attempting to move the initial cube. Ultimately, I am trying to decide if something has happened with the GPU. When i run a stress test on the GPU, it preforms the entire test and keeps the temperature in the acceptable range. Thank you for the reply.

blender_debug_output.txt

143 KiB

blender_debug_output 2nd.txt

0 B

Pratik Borhade commented

2024-01-09 05:57:36 +01:00

Thanks. Can you check event-viewer or reliability monitor after crash? they might have caught some information about crash

David-Richardson commented

2024-01-09 20:57:11 +01:00

The error received is:

A TDR has been detected. Error Code 7 (pid=20056 tid=18020 blender.exe 64bit)

Says to visit Nvidia for more information. It should be noted that jest before the crash the 3D section of GPU spikes to 100% and then the program crashes.

The error received is: 1. A TDR has been detected. Error Code 7 (pid=20056 tid=18020 blender.exe 64bit) Says to visit Nvidia for more information. It should be noted that jest before the crash the 3D section of GPU spikes to 100% and then the program crashes.

funty commented

2024-01-10 17:02:57 +01:00

@David-Richardson
Regarding your old file, this may have something to do with data created in old Blender 3.5 being corrupted when being used or converted in new Blender 4. I believe Blender 4 is only backward compatible to Blender 3.6. I would recommend with what worked before. In your case, Blender 3.5. But if you have to use Blender 4 for whatever reason, then below is some information I found on google using the keywords "nvidia TDR", that may be related.

Not sure if this workaround will help (its 12 years old, but I believe it still applies for TDR issues today as per MS), though it is risky as it involves adjusting values in the registry. If you are not comfortable editing the registry, please don't try it. Remember always make a backup first. And if you do try it, and it destroys your system, you have been warned!

MS explanation of issue from 12/06/2023:
https://learn.microsoft.com/en-us/windows-hardware/drivers/display/timeout-detection-and-recovery

Issue Registry Resolution from 12 years ago:
https://www.nvidia.com/en-us/geforce/forums/game-ready-drivers/13/127945/tdr-fix-here-for-nvidia-driver-crashing-randomly-i/

@David-Richardson Regarding your old file, this may have something to do with data created in old Blender 3.5 being corrupted when being used or converted in new Blender 4. I believe Blender 4 is only backward compatible to Blender 3.6. I would recommend with what worked before. In your case, Blender 3.5. But if you have to use Blender 4 for whatever reason, then below is some information I found on google using the keywords "nvidia TDR", that may be related. Not sure if this workaround will help (its 12 years old, but I believe it still applies for TDR issues today as per MS), though it is risky as it involves adjusting values in the registry. If you are not comfortable editing the registry, please don't try it. Remember always make a backup first. And if you do try it, and it destroys your system, you have been warned! MS explanation of issue from 12/06/2023: https://learn.microsoft.com/en-us/windows-hardware/drivers/display/timeout-detection-and-recovery Issue Registry Resolution from 12 years ago: https://www.nvidia.com/en-us/geforce/forums/game-ready-drivers/13/127945/tdr-fix-here-for-nvidia-driver-crashing-randomly-i/

David-Richardson commented

2024-01-11 18:53:42 +01:00

Thank you for the information about backward compatible. I did try editing the registry and all it did was delay the time until the crash. I have heard today that an external monitor will not work at all and crashes the computer so I think it is a GPU or onboard video problem. Thank you all for the suggestions, but I don't think this is a Blender Problem any longer with the new monitor issues.

David-Richardson closed this issue

2024-01-11 18:53:45 +01:00

Blender Bot added

Status

Archived

and removed

Status

Needs Information from User

labels 2024-01-11 18:53:46 +01:00

Sign in to join this conversation.