Page MenuHome

Windows crash when closing Blender 2.79
Open, NormalPublic

Description

System Information
Windows 10 x64 (Feature update to Windows 10, version 1803, November 27 2018)
Renderer: GeForce GTX 860M/PCIe/SSE2

Blender Version
Broken: 2.79b release and a9bd7883484 master builds
Works: 2.8 925380050d0

Short description of error
Quitting Blender 2.79 causes Windows to crash after recent Windows update.
I could not reproduce that with 2.8 version.

I know that is probably Microsoft's fault, but other programs do not cause system crash (including Blender 2.8), so there is clearly something within current Blender version that could be tweaked.

Exact steps for others to reproduce the error

  1. Make sure you on latest Windows 10 update (not the developer preview).
  2. Open Blender 2.79 (release or master build).
  3. Wait 20 seconds and then close Blender using window X button.
  4. Blender window closes but system console stay up with Blender quit message for a second or two, then blue screen appears SYSTEM_THREAD_EXCEPTION_NOT_HANDLED.

Minidump (I can provide full memory dump if requested):

Important notes:

  • Following my own steps I reproduced the crash five times in a row.
  • If I open Blender and wait 5 seconds before quitting, crash does not occur.
  • I could work all day in Blender rendering, modeling, animating, but crash occurs only when I quit Blender.
  • I updated all drivers, checked RAM and system drive for errors, ran Windows troubleshoot utility—all with no result.
  • WhoCrashed analysis of full memory dump showed no driver issues, it seems the issue is between Blender 2.79 and updated Windows kernel.
  • I uninstalled the last update, and now quitting Blender does not crash Windows anymore, so the issue is 100% in this update, not the drivers or the hardware.

Details

Type
Bug

Event Timeline

Mikhail Rachinskiy (alm) renamed this task from Windows crash when closing Blender to Windows crash when closing Blender 2.79.Sun, Dec 2, 7:53 PM
Mikhail Rachinskiy (alm) updated the task description. (Show Details)

Have you tried installing the latest drivers from the NVIDIA website? This kind of Windows update breakage may get fixed quickly in the NVIDIA drivers, the latest update was December 3.

This seems like a crash somewhere in the drivers, but it's hard to tell what causes it. The OpenGL handling was completely rewritten in 2.8, and finding out the difference will likely require a developer to be able to reproduce the problem and investigate.

I think we should wait a little bit to see if it gets fixed in NVIDIA or Windows updates, or if other developers/users run into the same issue, before we look into this.

the crashdump seems to imply dxgmms2.sys is at fault, which is a microsoft driver , you appear to be running the april 2018 update of windows 10, updating to the latest (october) would probably not be the worst thing to try.

Have you tried installing the latest drivers from the NVIDIA website?

That was the first thing I tried, at the time that did not helped, but now there are new drivers available I have not yet tried.

I think we should wait a little bit to see if it gets fixed in NVIDIA or Windows updates, or if other developers/users run into the same issue, before we look into this.

I think it is reasonable, I will wait one week (or how long Windows update will let me wait) and install latest Windows updates along with Nvidia drivers.

you appear to be running the april 2018 update of windows 10, updating to the latest (october) would probably not be the worst thing to try.

Recently Microsoft lifted update block to 1809 update, but that happened around the time I got my October update, so I do not know for sure if I had cumulative or feature update.