Windows 10: My VMware Player has been crashing a lot

My VMware Player has been crashing a lot. In fact once there was a series of about 5 fatal error dialogs which cascaded in a rather aesthetic and soothing fashion. Before I go to VMware for help, does anyone here have any advice which might smooth out the process.

:)

 

After upgrade to Windows 10 (from Windows 8.1) I get frequent BSOD events

Windows reset that removes all the applications and re-installs Windows 10 has worked fine. No more crashes.

I later traced log files that the problematic driver was for the VMWare Player. After reinstalling VMWare Player into Windows 10, Windows is still working fine - no crashes.

So, my problem is resolved.

 

BSOD when running VMWare Player after Creators Update

I've tried that as well, and have posted over in vmware communities about the issue with no response yet. I don't see how it can be a vmware issue myself, as vmware has been running absolutely fine on my machine for years, only crashing the system after
MS issued it's Creators Update.

 

(Sorry for posting the OP in the wrong place.)

I narrowed down the cause of the crashes to the USB ports. I'm going to try changing the ports from 3.0 to 2.0. I can't find any information on this type of issue in the PDF docs or at the website. Maybe it'll crash again soon and generate a report/log which I can submit to VMware.

Edited to add:

Good news and bad new. The good news is that I now have an error report. The bad news obviously is that switching to 2.0 didn't work.

 

I'm a firm believer in the maxim, "If all else fails, read the instructions," but, in this case, the instructions didn't tell me anything I didn't already figure out. I uninstalled the Player and reinstalled it, to no avail. I did discover that, if I ignore the fact that the docs and the menus say that it's possible to switch the USB back to the host system, and leave it connected to the VM, things work just fine. Switching the USB back and forth worked when I first installed the Player. I don't know what changed.

 

This is really annoying - it's a VC++ runtime error regarding virtual protection - strangely enough USB swapping does not work on VMWare 12.1 on Linux either ( no error, just does not appear as a connected device on reconnect)

 

Thanks for the information. Fortunately, right now, I don't need the USB ports on the VM; it's easier to transfer files with copy/paste. I just need to make sure that the VM isn't infected first.

 

My VMware Workstation 12 gets the C++ errors when I try using a USB device (that doesn't exist, but is labeled as one that does). Only fix: end the vmware process in taskmanager, which causes the VMware to think it's "running" and so I have to restart my PC because I can't take over the running but not running vm. I also get this error when trying to update MSDOS to Win 95...