I had this issue too. I traced it back to using compression for the Blender files, at least for the time being that seemed to be the issue. Do you happen to save your Blender file as a compressed file?

In T90929#1211540, @kursad k (kursadk) wrote:

I had this issue too. I traced it back to using compression for the Blender files, at least for the time being that seemed to be the issue. Do you happen to save your Blender file as a compressed file?

The project I was working on was in fact not saved at all, it was a new project, so this cannot be the cause in my case. And no, I normally do not save in a compressed format (unless .blend is such a format).

The Blender file can be saved as a compressed .blend file. It is an option in the save window.

In T90929#1211552, @kursad k (kursadk) wrote:

The Blender file can be saved as a compressed .blend file. It is an option in the save window.

Alright, good to know. Not what's causing my problem (once again it occurs for me when working with a new unsaved project), but if that also causes the problem, perhaps some of the previous bug reports I mentioned were due to that and not the same bug that I'm experiencing, which means it might only be a bug in newer versions of Blender.

And looking at previous bug reports, it seems to be a Windows-only bug.

Hi, thanks reporting the issue. Could you please mention those bug reports?

While I don't have the .blend file saved, I can attach it to this report the next time I encounter it.

Without .blend file and exacts steps to redo the crash, it will be hard to triage the this report (at least for me).
I tried with provided steps but failed to recreate the situation for crash

Some of the reports I saw were T61527, T22834, T39119, T60849, T68373, T54598, there are more you can find by googling for "blender ctrl-z closes program" or something similar. The common factor seems to be Windows (but not necessarily Windows 10, as some had Windows 8 as well) and Nvidia GPUs. This is likely some rare bug resulting from the combination of Windows + Nvidia + Blender, so that's likely why the bug hasn't been solved even though it seems to have existed for a while.

@Andrew M. (realandrew) Did you have any progress with this? I happened to have this thing crash again here.

@kursad k (kursadk) Unfortunately I haven't had any progress, we need a .blend that we know causes the crash so that the problem is somewhat reproducible. I haven't used Blender since reporting this bug due to being busy, but if you or anyone has a .blend saved that was open when the crash occurs if you could supply it here that would be great. Other than that, I think the problem is narrowed down to Windows (7/8/10) computers with Nvidia GPUs. One question I do want to ask for others who are experiencing this bug: Do you have Nvidia Geforce Experience installed? Not just the standard graphics control panel, but Geforce Experience (which lets you update your drivers and also has an in-game overlay and such). I'm wondering if maybe that is related to the crash in some way.

In my case it happens with complicated project files which I can't share here. Obviously this makes it hard to track the issue.

I do not use the Geforce Experience option. I only update the bare driver.

I'm having the same issue, lost my unsaved work a number of times. The undo just closes blender, no hanging or freezing just instantly closes.

After a bit of work, I figured out I could reproduce it consistently with a brand new file :

1. Open up blender.
2. Scale the default cube a couple of times (has to change geometry, just moving it doesn't work).
3. Rapidly tap ctrl+z in quick succession. Single undos rarely cause it to crash (that only happened once while I was testing).

Happens on Blender 2.9.1 and 3.0
I'm running windows 11, with an NVIDIA GeForce RTX 2060.
I use Geforce Experience, and the graphics drivers are all up to date.

Also, a list of things I tested that I thought might have contributed to it, but ended up not affecting the outcome:

• Having multiple viewports open
• Viewing a rendered view
• Saving the document vs a completely new unsaved document
• Other things in the scene (camera, empties, etc.)

OK, so I should have done this first, but I went through all my addons to see if they were causing issues, and one of them appears to be the culprit, for me anyhow.
I was using an addon called Alice/LG for creating renders for a holographic display, and if I disable it, I haven't been able to crash Blender. I'll update if that changes.

That is interesting, when the crashes occurred for me I don't have any extra add-ons (not quite true I use an add-on called Unreal Right Click, but I don't think that was the cause for me). It seems perhaps this bug has multiple conditions that enable it to occur (compressed save files, certain add-ons, and something unknown which caused it for me). Still, the common factor is Windows (7/8/10/11) and Nvidia GPU, which means the bug is somehow related to that. I wish I could test more but I have trouble intentionally reproducing the bug, it usually crops up when I'm many minutes into a project, I haven't been able to get it to appear when scaling a cube many times and then undoing many times as you were able to.

In T90929#1296825, @Pratik Borhade (PratikPB2123) wrote:

Hi @Andrew M. (realandrew) , did you manage to get similar crash after reporting this bug?
There can be many reason for the crash. Crash logs may help to identify the problem: https://docs.blender.org/manual/en/dev/troubleshooting/crash.html#crash-log
We cannot help much without reproducing the issue.

Hi @Pratik Borhade (PratikPB2123), Unfortunately, I haven't managed to get any crash logs. I'm primarily a programmer so I rarely use Blender and thus have been unable to reproduce so I can submit the crash logs. If I do get the crash again I will be sure to post the logs.