Here are the 3 BSOD's that were occurring (IRP's was most common at the start), just copied some here: Guess I'm not installing those Windows updates again in a while although removing them didn't help. Transferred the vm back to my server, started it. Run sfc and disk checking and rebooted a few times with shutdowns, everything just run fine. Next day I copied the virtual machine to my main machine, where it started nicely. Just mentioning it since I took a longer break going to sleep. Since I spent like 8h resolving this with long breaks I doubt just waiting would have helped. Since it was around midnight at this point I called it a day. Run sfc /scannnow and disk checking on the server. bang.Īt this point BSOD's are not even getting to the login screen in the vm anymore, from the logs I can see vmware restoring at 1%.5%.93% and bang. Start the virtual machine and BSOD.ĭownloaded the newest version of Vmware Player, rebooted, start vm.

Uninstalled the KB's Windows Update added. Ok, vmware (player) is causing a serious problem at least with this virtual machine. Run the virtual machine and within minutes, BSOD. Also, everything is just fine, until I start a virtual machine (no, I didn't start another just to check if the important one had become corrupt). I just haven't had crashes before even when copying terabytes between ssd's and normal HDD's. I doubt system stress was the reason although the first crashes were all MULTIPLE_IRP_COMPLETE_REQUESTS (and it's over 10 years since vmware had these problems before - quick check of the forum). and again.Īt this point I shut down vmware autorunning my sql server virtual machine not to destroy it. Since this is my server I often let it handle heavy tasks regardless of how inefficient it is to run much disc activity at once.Īt some point I realized the copying from my main machine had stopped and lo and behold, the server had booted. Stable for 6h now so I'll post my findings for future reference.Īfter this I performed a disc cleanup while copying 200-300G at the same time (100M/s disk speed glowing red). I had a similar issue but didn't touch Avast while attempting fixes.

W10 shut up