As title say,
it’s quite random and can sometime result in weird stuff like corrupting the scene and prefab assets.
I have a month old RTX2060, never had any blue screen in games or softwares
These are the settings I use:
Hi, sorry to hear that it is unstable. Do you have the same problem on the latest drivers and the 2019.3 beta or 2020 alpha? If possible please create a bug report after a crash so we will get access to the editor logs, driver information etc.
Yeah it still happens with 2019.3 beta, I’ll try to report the bug, but I don’t get a unity report bug like: unity has ceased to function prompt, I get a total blue screen, my computer restart… but I guess I could still send the editor log. Would you also need the windows crash report?
Yes please, the more info the better 
Ok, already did!
Also I switched graphic card with a collegue (also rtx 2060) and it still happens, so it’s not from a specific cards, maybe specific to these models however idk.
FWIW - I had the same problem before and when I started using Substance Painter indirectly found a fix for my situation.
https://docs.substance3d.com/spdoc/gpu-drivers-crash-with-long-computations-128745489.html
Edit: worth noting I was using progressive CPU, but had the same symptoms.
// WildStyle
Are you 100% sure it’s fixed? I use substance since a while and I edited the keys in registry before I started using the progressive GPU lightmapper in unity.
OK - well it was worth checking, I didn’t realize you were already a Substance user.
This definitely fixed things for me… I was unable to lightmap my game before. Seems like perhaps it’s something else for you, in this case.
// WildStyle
I’ll look into the settings, maybe I’ve entered an overkill value or something…
Yeah - by the way Windows reverted this setting for me one time in an update, then I had to re-apply it again.
// WildStyle
My values where set at decimal 120 (substance recommend 60). I’ll see if it happens again. If I get no crash by friday, I guess it’s fixed… I’ll keep the post udated.
I already crashed 2 times so I guess it’s something else 
What is the case number for the bug report you filed?
Case 1186909
1 Like