Hi ;
I have been using PB since version 0.8 Alpha in 1989 and have never had this happen. I have also been using PB 2017 for almost a year now ( since its early internal Beta ), compile code daily and have never had this happen with PB 2017. It seems to me that there might be other factors at work here like: Hardware issues, Anti-virus, Malware, etc. I run PB on pure MS-Windows 10 installs on real PC's with AMD processors.
Another big issue (and no, no) is to make sure that all your App's resources - mainly PBL's - are located on the same PC as the PB install. Accessing PBL's across a network when you get a failure has been known to corrupt libraries. Other aspects to consider are running the PB IDE on another machine via RDT or running PB IDE on Citrix instead of a pure MS-Window installation and/or VM.
HTH
Regards ... Chris