I removed VMWare Tools and rebooted the system. It has now been up without a BSOD for nearly 24 hours. That means VMWare Tools is causing the BSOD.
It is more than a little distressing that I can no longer access support since I bought the product more than 18 months ago. VMWare support is the best I know of for any software product. It's really quite extraordinary. However, if I can't even submit a request it does me no good.
Can anyone suggest where I go next?
I have now deleted VMWare from the machine and re-installed it. I then re-installed VMWare Tools. The re-install reported NO irregularities.
The crash as returned exactly like before, a BSOD about 10-20 minutes after reboot and Login.
Quite doubtful that it is the VMware Tools alone causing the BSOD otherwise a lot of other users would have experienced the same problem as you have.
A couple of options to check/confirm/try:
Option 1: Verify the guest OS and hardware compatibility settings are correct
The guest OS should be Windows 10 x64 (or Windows 10 if 32-bit) - (in Settings - General - OS)
Hardware compatibility should be set to version 12 (in Settings - Compatibility)
See screenshots below.
In Workstation Pro, there has been cases where a Windows 10 VM (upgraded from Windows 7) either fail to boot or crashes during boot because the guest OS setting remained at Windows 7.
Once this all set to correctly, reinstall the VMware Tools.
Option 2: reinstall/repair Windows 10
Another possibility something went awry with the upgrade from Windows 7 to Windows 10. If option 1 was not the problem or does not fix the crashing, you could try to re-install or repair the Windows 10 using an ISO download using the Windows 10 media creation tool.
Take a full backup of the VM (not Time Machine). This will allow you to go back to a working version of the VM (even though it crashes now) in case something goes wrong with the repair/re-install.
Do not create a new Windows 10 VM as the Microsoft digital licence servers will see it as a "new machine" and will ask for a new registration/licence key. Just perform the repair/reinstall with the existing VM. Depending on the licence you have (e.g. retail licence), have the previous Windows 7 licence key in hand just in the (unlikely) case the repair/reinstall somehow re-prompts for the licence key. Generally, it should not prompt again so long as you install/repair into the same VM as the Microsoft licence servers would see it as the same machine (albeit virtual).