I had exactly the same problem when upgrading from v13 to v14. A perfectly usable Parallels session using my Boot Camp partition, together with a perfect native Boot Camp operation turned into the DanO1's type of blue screens. I was advised to run chkdsk, etc., etc, but this should not be necessary when everything works perfectly in v13! So, eventually, after a few friendly emails with support, I have deleted v14 (and my upgrade payment was immediately refunded - thanks, Parallels), reverted to v13 and it all works like a charm. A real nuisance was having to speak to Microsoft to re-activate Windows 10 for the VM, but they were very helpful, even though it's a lengthy process. I don't mind using terminal, even having to do Calaska's solution - but I can't face buying the upgrade again, it not working, and having to try and revert - and then have another session with Microsoft. For my usage, it isn't worth the trouble. What does surprise me is that Parallels obviously know there is something wrong, but don't appear to have addressed it. One really shouldn't need to go through a load of stages, including fairly complex Terminal instructions, to get things going. One is supposed to click and go..... Never mind.