"Obviously VMWare is the culprit, as I don't get blue screens at all unless I'm running a VM. I can stress test for hours, game, etc. with no issues.
Other than switching to a Linux host, what can we do? I use too many Windows-only applications for this to be a viable solution.
Has anyone reported this to VMWare? Do they even know about it? I can't even find a way to do that. Seems like it's not even on their radar, and if that's the case it's probably not going to get fixed."
Exactly. This matter has been questioned and discussed to death already within this community. How I can see the next professional steps being:
- Support taking this matter in its hand, using these Community member, how appropriate, who seem to be more than willing to help
- Case assigned to a person with enough knowledge on VMware product internals and probably access to VMware Development to discuss more
- Support creating a reproducible case with the before-mentioned actions
- Support taking into account that this might not be a Player-only problem, but might be true with Workstation Pro just as well
- Assignment to get fixed, along with VMware company process of such work (possible Product Management level decision, amount of work estimate, priority of a fix, analysis of what fixing vs. not fixing means ... and all the rest)
- Development work, Internal testing work, Support organization verification, Release
Having said this, IF this is something impossible or next to impossible to do (meaning, for instance, that possible regressions are too difficult to predict), given Windows 10 architecture (possibly also VMware architecture), we should NEVER expect an announcement of that being a case. I mean, VMware can never say aloud that Windows 10 is the fault here.
