VMware Communities
biowizard
Enthusiast
Enthusiast

Workstation Pro 17 Crashes Windows 7 (32-bit)

Yesterday I purchased my Workstation Pro 17 / Fusion Pro 13 serial number, and set about installing the former on my WIndows 10 22H2 PC. Installation when smoothly, and after some some jiggery pokery with shared folders, I had my most important VMs up and running smoothly. Or so I thought.

In testing Windows 7 (32-bit), which I use as part of my workflow for legacy applications, and to pass files to/from my MS-DOS 8 VM, I decided to run my favourite pass-the-time game, Chess Titans.

OOPS! Bang, crash, I dialog popped up which I tried to capture with "Print Screen", but could not paste into my Windows 10 environment; the last items on the VMWARE,LOG file before a message about how to contact support, are shown below.

While Chess Titans isn't the be-all and end-all of my VM life, the total (and repeatable) collapse of this application left my VM in a bit of a mess (luckily, I had a recent backup), and in short, for now, I have reverted to Workstation Pro 16.

Who/which dept at VMware would be the best person to send the entire logfile to?

2023-02-11T00:28:11.543Z Wa(03) mks Win32 object usage: GDI 7, USER 20
2023-02-11T00:28:11.543Z In(05) mks Writing monitor `vmmcores.gz`
2023-02-11T00:28:11.549Z Wa(03) mks Dumping core for vcpu-0
2023-02-11T00:28:11.549Z In(05) mks Beginning monitor coredump
2023-02-11T00:28:11.633Z In(05) mks CoreDump error: Read, page 0xa00 (0x8523ff) Invalid access to memory location
2023-02-11T00:28:11.633Z In(05) mks CoreDump error: Read, page 0xa01 (0x21aefe) Invalid access to memory location
2023-02-11T00:28:11.642Z In(05) mks CoreDump error: Read, page 0xb34 (0) Invalid access to memory location
2023-02-11T00:28:11.643Z In(05) mks CoreDump error: Read, page 0xb35 (0) Invalid access to memory location
2023-02-11T00:28:11.643Z In(05) mks CoreDump error: Read, page 0xb36 (0) Invalid access to memory location
2023-02-11T00:28:11.643Z In(05) mks CoreDump error: Read, page 0xb37 (0) Invalid access to memory location
2023-02-11T00:28:11.857Z In(05) mks End monitor coredump
2023-02-11T00:28:12.857Z In(05) mks Msg_Post: Error
2023-02-11T00:28:12.857Z In(05) mks [msg.log.error.unrecoverable] VMware Workstation unrecoverable error: (mks)
2023-02-11T00:28:12.857Z In(05)+ mks ISBRendererComm: Lost connection to mksSandbox (3093)

Labels (1)
Tags (2)
Reply
0 Kudos
2 Replies
MichaelNealy
Contributor
Contributor

Same here.

I purchased my Workstation Pro 17 / Fusion Pro 13 serial number because I want to set about installing the former on my Windows 10 22H2 PC. I was so happy when I found your post but it makes me sad when I can't find my answer over here. Please reply to me soon. I am waiting for your reply. Now, I am gonna visit https://gamblebeaver.com/1-dollar-deposit-casinos/ here to read reviews on those sites through which I can make money. I want to make money because I am facing a financial problems.
Reply
0 Kudos
biowizard
Enthusiast
Enthusiast

Nobody else had any experiences like this in Workstation 17?

Just wondering ...

Brian

Reply
0 Kudos