- User Since
- Aug 1 2018, 11:24 AM (45 w, 4 d)
Feb 6 2019
I updated to driver version 18.104.22.16872 (from Lenovo), and the only change is that Blender crashes before I see the default workspace (today's build). Currently I'm fine knowing that I have to turn off conservative morphological anti-aliasing to make Blender work. It also seems that it is turned off by default now anyway, and can only be changed manually for a specific application. After some search across the internet, this "feature" seems to be a problem for many applications and games since 2015.
Jan 31 2019
I could fix the scene by deactivating adaptive domain, applying scale to the domain, and reactivating adaptive domain. Seems the the smoke sim does not like scaling other than 1.
Same here on Win 10 Home 64, GTX 1070, with today's build.
Ok, so far I tried it with earlier versions, and it worked without crash up till 2019-01-19 Hash b0dee09a6d55, which was the latest I had on my hard drive before 2019-01-29 Hash a1ae04d15a9f. Updated Nvidia drivers to 417.71, no success.
Downloaded latest from today (8c8979067490) and...it doesn't crash anymore!
Jan 30 2019
Jan 10 2019
I just wanted to report that I reopened the scene today and it renders fine now. Same blender build, same GPU driver. Not sure what fixed it. Perhaps a reboot or restart of Blender.
Jan 4 2019
Nov 29 2018
I found a solution to the problem, found in another thread:
Go to the intel HD Graphics Control Panel 3D Settings and turn off conservative morphological anti-aliasing.
So this seems to be an intel problem.
Oct 25 2018
Oct 22 2018
Awesome, also fixed it for me on Win10!
Oct 19 2018
Windows 10 Home 64-bit, GeForce 9600 GS 768MB (NVIDIA driver 342.01, which is the latest available for this card)
OS up to date.
Aug 17 2018
Awesome, this fixed it for me (trying 77e1942e0e1).
Thanks a lot!
Aug 1 2018
Coming from T56193 to this one (which seems to be similar). Exactly the same behaviour.
When starting blender with --factory-startup from the Windows 10 commandline (running as admin) I see the following in the command prompt after the crash: