I can't believe what I read here, since mid last year such a catastrophic situation and no fix. I can't tell of course how many users are affected by this, but in my case it is the same for both Win10 VMs, and it is not an occasional/rare freeze, it is a continuous threat pending above your work. So desastorous that I thought this cannot be a Parallels problem, it mus be a flaw in my local system. But then I read descriptions of symptoms here that are soo similar to mine: mainly use VS 2017 - get a crash with a horribly sound dhing-dhing-dhing (See DaniloD2) - this is exactly my case, and these are pretty specific symptoms. I can add from my side, that I store the images on a external drive connected via usb3 - and that drive is a raid0 drive... Frankly, I think this is a scandal. (but I'll try the TRIM suggestion now)
PS: just looked and found that trim was *not* enabled on both of my Win 10 VMs
PPS: I should mention the situation did not change at all through the 13->14 update, nor through the minor version update of 14 since then... I repeat: a scandal!
Last edited: Feb 12, 2019