Startup EXCEPTION_ACCESS_VIOLATION crash on Windows 10 with newer NVidia drivers #102114

New Issue

Crowe · 2022-10-28T01:21:58+02:00

Crowe commented

2022-10-28 01:21:58 +02:00

System Information
Operating system: Windows 10 Build 19044
Graphics card: NVIDIA GeForce GTX 1060 6GB/PCIe/SSE2

Blender Version
Broken:
Win10 - 3.2.0, hash: e05e1e3691
Win10 - 3.3.2 Release Candidate, hash: 2a7b8e78e1
Win10 - 3.4.0 Alpha, hash: e75be000e3
Worked:
Win 8.1 - All versions above
Win 10 - Unknown

Short description of error

Blender will crash silently every N startups (varies with Blender and driver versions) on Windows 10. Using blender_factory_startup.cmd shows EXCEPTION_ACCESS_VIOLATION errors when it crashes.

I don't know since when it's happening, it's been a while since I've used Blender. New versions were released and I updated my GPU driver in the meanwhile. I started to try different GPU drivers after comparing the Blender behavior in Windows 8.1, where I couldn't make it crash no matter the Blender version tried.

Newer drivers and newer builds have a significantly higher chance of crashing on Win 10. There's the possibility this is not new behavior, but I didn't notice it because it's significantly harder to make it crash on older drivers. Example:

Win 8.1, 3.4.0 Alpha, NVIDIA 473.04 - 25 tries, no crash
Win 10, 3.4.0 Alpha, NVIDIA 516.59 - crash every ~3 tries
Win 10, 3.4.0 Alpha, NVIDIA 472.12 - crash every ~22 tries

I'm using the most recent driver available for Win 8.1, which was released in January. Trying a similar version for Win 10 makes Blender more stable, but the debug_output is empty when it crashes.

I ran chkdsk , dism /restorehealth , and sfc /scannow in Win 10 for good measure, no errors found.

I've attached two sample outputs from a crash in which the debug file isn't empty + another from a different crash when running the gpu debug cmd.

blender_debug_output.txt
blender_system_info.txt

blender_debug_output_(gpu).txt

**System Information** Operating system: Windows 10 Build 19044 Graphics card: NVIDIA GeForce GTX 1060 6GB/PCIe/SSE2 **Blender Version** *Broken:* Win10 - 3.2.0, hash: e05e1e369187 Win10 - 3.3.2 Release Candidate, hash: 2a7b8e78e192 Win10 - 3.4.0 Alpha, hash: e75be000e3e8 *Worked:* Win 8.1 - All versions above Win 10 - Unknown **Short description of error** Blender will crash silently every N startups (varies with Blender and driver versions) on Windows 10. Using `blender_factory_startup.cmd ` shows `EXCEPTION_ACCESS_VIOLATION ` errors when it crashes. I don't know since when it's happening, it's been a while since I've used Blender. New versions were released and I updated my GPU driver in the meanwhile. I started to try different GPU drivers after comparing the Blender behavior in Windows 8.1, where I couldn't make it crash no matter the Blender version tried. Newer drivers and newer builds have a significantly higher chance of crashing on Win 10. There's the possibility this is not new behavior, but I didn't notice it because it's significantly harder to make it crash on older drivers. Example: Win 8.1, 3.4.0 Alpha, NVIDIA 473.04 - 25 tries, no crash Win 10, 3.4.0 Alpha, NVIDIA 516.59 - crash every ~3 tries Win 10, 3.4.0 Alpha, NVIDIA 472.12 - crash every ~22 tries I'm using the most recent driver available for Win 8.1, which was released in January. Trying a similar version for Win 10 makes Blender more stable, but the debug_output is empty when it crashes. I ran `chkdsk `, `dism /restorehealth `, and `sfc /scannow` in Win 10 for good measure, no errors found. I've attached two sample outputs from a crash in which the debug file isn't empty + another from a different crash when running the gpu debug cmd. [blender_debug_output.txt](https://archive.blender.org/developer/F13785912/blender_debug_output.txt) [blender_system_info.txt](https://archive.blender.org/developer/F13785913/blender_system_info.txt) [blender_debug_output_(gpu).txt](https://archive.blender.org/developer/F13785908/blender_debug_output__gpu_.txt)

Crowe commented

2022-10-28 01:21:58 +02:00

Added subscriber: @crowe

Omar Emara commented

2022-10-28 13:39:57 +02:00

Added subscriber: @OmarEmaraDev

Omar Emara commented

2022-10-28 13:39:57 +02:00

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

Omar Emara commented

2022-10-28 13:39:57 +02:00

Can you attach the actual crash file found in C:\Users\Crowe\AppData\Local\Temp\blender.crash.txt?

Can you attach the actual crash file found in `C:\Users\Crowe\AppData\Local\Temp\blender.crash.txt`?

Crowe commented

2022-10-28 16:46:42 +02:00

Sorry, forgot to attach these! Unfortunately all stack traces show Symbols not available, but I've automated the blender startup and log collection proccess if it crashes, so here are two crash startup log examples with files containing most info.

1

blender.crash.txt
blender_debug_output.txt
blender_system_info.txt

2

blender.crash.txt
blender_debug_output.txt
blender_system_info.txt

Sorry, forgot to attach these! Unfortunately all stack traces show **Symbols not available**, but I've automated the blender startup and log collection proccess if it crashes, so here are two crash startup log examples with files containing most info. # 1 [blender.crash.txt](https://archive.blender.org/developer/F13790314/blender.crash.txt) [blender_debug_output.txt](https://archive.blender.org/developer/F13790315/blender_debug_output.txt) [blender_system_info.txt](https://archive.blender.org/developer/F13790316/blender_system_info.txt) # 2 [blender.crash.txt](https://archive.blender.org/developer/F13790311/blender.crash.txt) [blender_debug_output.txt](https://archive.blender.org/developer/F13790312/blender_debug_output.txt) [blender_system_info.txt](https://archive.blender.org/developer/F13790313/blender_system_info.txt)

Omar Emara commented

2022-10-28 16:49:47 +02:00

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

Omar Emara commented

2022-10-28 16:49:47 +02:00

I see. I am not sure what might be causing that.

Ray molenkamp commented

2022-10-28 17:33:10 +02:00

Added subscriber: @LazyDodo

Ray molenkamp commented

2022-10-28 17:33:10 +02:00

Can't reproduce on win10/516.59 on a 1660 tried about 30 times...

Pratik Borhade commented

2022-11-02 08:41:28 +01:00

Added subscriber: @PratikPB2123

Pratik Borhade commented

2022-11-02 08:41:28 +01:00

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

Pratik Borhade commented

2022-11-02 08:41:28 +01:00

Hi, thanks for the report. Does it happen in default cube file? when does this happen (I mean do you've any particular reproducing case)?
Have you recently tweaked GPU settings? Crash log doesn't contain more relevant information so not sure what is the real cause.

Hi, thanks for the report. Does it happen in default cube file? when does this happen (I mean do you've any particular reproducing case)? Have you recently tweaked GPU settings? Crash log doesn't contain more relevant information so not sure what is the real cause.

Pratik Borhade commented

2022-11-25 10:57:09 +01:00

Hi, any updates?

Thomas Dinges commented

2022-12-15 16:36:10 +01:00

Added subscriber: @ThomasDinges

Thomas Dinges commented

2022-12-15 16:36:10 +01:00

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

Thomas Dinges closed this issue

2022-12-15 16:36:10 +01:00

Thomas Dinges commented

2022-12-15 16:36:10 +01:00

No activity for more than a week. As per the tracker policy we assume the issue is gone and can be closed.

Thanks again for the report. If the problem persists please open a new report with the required information.

No activity for more than a week. As per the tracker policy we assume the issue is gone and can be closed. Thanks again for the report. If the problem persists please open a new report with the required information.

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

Startup EXCEPTION_ACCESS_VIOLATION crash on Windows 10 with newer NVidia drivers #102114

1

2