Blender 2.91 and 2.92 crashes

Has anyone been having a lot of crashes lately with Blender? Since Blender 2.91 Blender has been crashing quite a lot. I thought it would improve with 2.92 but had some random crash today.

Simple thing like rotating an object or moving an object causes blender to crash. This has happened even with scenes without a lot models.

Hi, Blender never crash for me often, maybe once a month or so.
If you can reproduce a crash every time report it to the bug tracker from Help menu.
You can start Blender from a command shell, then you get error messages after crash.
I mostly work on Linux but sometime on Windows 10, too.

Cheers, mib

Thanks for reply. I’ll see if I can any error message

An update on the crashing issue. I still have them and after some research found that other people are reporting the same things as me.

Seems that it concerns Nvidia graphic cards. Other people who has reported it has different graphic cards than me.

The Dev, for what I have read do think its a graphic card issue. But even with the latest drivers random crashes still occur.

Crash erro log has this :
Exception Address : 0x00007FFB0901B14D
Exception Module : nvoglv64.dll
Exception Flags : 0x00000000
Exception Parameters : 0x2
** Parameters[0] : 0x0000000000000000**
** Parameters[1] : 0x00000000000074F0**

Stack trace:
nvoglv64.dll :0x00007FFB08DF9470 DrvPresentBuffers
nvoglv64.dll :0x00007FFB08CCF2A8 Symbols not available

Not sure what other step to take has this has been reported several times.

Hi, can you add your system specs, please?
I use GTX 760 for Years now and add RTX 2060 a few month ago.

Windows 10 Pro
Driver 456.71
Intel i5 3570K 16 GB RAM
GTX 760 4 GB /Display card
RTX 2060
Opensuse Tumbleweed x86_64
Driver 460.79

1 Like

Hello I have an MSI laptop and the specs are as follows :

Windows 10 Home
Intel® Core™ i7-10750H CPU @ 2.60GHz 16 GB RAM
Geforce RTX 2060 16 GB RAM / Driver 461.72
Intel® UHD graphic / uses share ram with the system

If you search for nvoglv64.dll you will get a lot of error and crash reports for different software.
It is an OpenGL error, OpenGL is used to draw the whole Blender user interface.
I guess it is a conflict between your Intel and your Nvidia GPU.
You can try to open the context menu with right mouse button on the Blender desktop short cut.
There is an entry OpenGL render. If an entry Intel UHD exist use this.
I have my Intel GPU disabled in BIOS but laptops often not support this, they switch between Intel and Nvidia all the time for power saving.
If this does not help you should report it to the Blender bug tracker with the error message and so forth.

Cheers, mib

Thanks for taking the time to help me on this. Unfortunately I do not see the option you are saying to me. I will try to report that as a bug. Taking some of your explanation to the Dev. Hope that they will be able to fix it.

1 Like

If you want to report use link from Blender help menu, it include system info, Blender version and so forth.

Cheers, mib

1 Like

please contribute here:

OK. If you people are on Windows 10 1903 and up (from May 2020 update) and have Blender Crashes in Machines that have Nvidia/AMD and Intel switchable graphics (usually notebooks) then this is for all of ya:

Microsoft changed the way switchable graphics works in the OS. Basically, now they can switch on the fly the GPU used based on the energy usage of the Notebook or PC (if have switchable graphics enabled). This is enabled by default, and for what i’ve experienced, this makes such system far more prone to crashes. And the controls are pretty much hidden from the users.

Ironically, AMD has more instructions on how to make windows choose the right driver here:

It solved the problem for me. Hopefully it works out there. If you are on Nvidia, try their creation driver.

Thanks for the info. But this do not happen to me with Blender 2.83. Only with 2.91 and 2.92 . But I’ll try to test if things gets better if I found out, how to do it as I use Intel.

2.90 was quite stable but 2.92 for the same kind of things crashes often.

On bakes for example, it appears some conditions ( or meshes ) make blender crash & quit.

I don’t know yet how to 100% reproduce the thing but i’ll dig.
Also when baking textures, target textures are not always updated…

1 Like

I noticed that crashes occur when baking multiple objects in a raw…

And this seems to depend on the active object. Unforyunately i need those bakes done and have no time for simplifying my scene for a bug report…

Nothing more for now :confused:

Replying to myself with very few info…

This morning while baking this objects lightmap to a 8K texture

Direct crash at clicking on the bake button.
Relaunch blender, reopened the file, and crash again.
Relaunch blender, reopened the file and blender finally kept running.
Hit the bake button and the bake is in currently progress…

This kind of behaviour ( random crashes with no obvious reason ) is typical of shitty pointer handling in a C or C++ program. A pointer goes over a buffer and the app behaviour depends on what is over this buffer.

Would there be a way to launch blender in a more verbose mode that could tell at least where the app crashed ? showing the registers, the stack and the later run few lines of code ?
This would help devs ( who have the symbols table ) to find the code sequence in the compiled files and then in the original code…

Thanks and happy blending !
Running blender with

Hi, Blender create a crash log in /tmp, path is in Preferences > File Path.
You need a debug build to get the full error messages, you have to build it yourself but the regular messages are a hint, at least.

Cheers, mib

1 Like

great ! thanks a bunch @mib2berlin :slight_smile:

i got the file:
carc_4nitelite_place&bake.crash.txt (30.6 KB)

It’s an access violation. typically a pointer accessing out of it’s buffers in the bm_select_history_store_notest function or method.
I guess this would give enough info to start investigating the bug :wink:

thanks and happy blending !

1 Like

repying to myself…

My bake went up to the end.
It seems that when it starts, if it don’t crash right away, baking processe finishes properly.

Saved both the texture and the .blend then selected new mesh for a bake…
and crash…

2nd.txt (45.2 KB) 3rd.txt (30.6 KB)

2 successive crash logs ( and several crashes at loading the .blend file )

The BMesh func always seem to be se same where the app crashes…
I deleted the mesh sculpt data…
Crashes again…

i deleted all but the mesh:

and ran a bake; no crash. stopped, reloaded, rebake… 5 or 6 times and there was no crashes.
This appears not to come from this mesh^^

Some infos at the next episode XD

Happy blending !

well some more info…

for the file that is problematic:
The mesh i want to bake is selected and it has been saved as is.
load - crash
load - crash
load - OK
bake - crash
load - crash
load - OK
bake - crash
load - ok
select another mesh, the select the mesh to bake,
bake - OK ( currently in progress )

I got no more info… :frowning:

Hi, if you get 8 from 10 to crash may be report it to the bug tracker with a simplified file from Blender Help Menu. Crash issues can often better to fix than other bugs, may the developer can fix it for 2.93 and backport it to the LTS versions.

Cheers, mib