VMware Communities

Graphics errors in Win7 guest on Player Pro 14 hosted on Win10

We are developing a software suite which uses OpenGL graphics. It is Windows 32 bit code.

Development is done in a virtual Windows 7 x64 machine which was originally hosted on a Windows 7 system running VMWare Workstation PRO 12.

This worked fine and we could both code and debug in the guest.

Now after updating the host development system to Windows 10 and using VMWare Player 14 (14.0.0 build-6661328) we are experiencing graphics errors when running the software inside the guest. This happens both if run within the development IDE and standalone inside the guest.

Whenever the OpenGL data rendering starts inside the software an exception is generated.

In one of the programs in the suite there is an unhandled access violation, which provides some info:

"Access violation error at address 69F56C9D in module 'vm3dgl.dll'. Write of address 00000000"

If we move the executable built in the guest to the host system and run it there it works fine (exact same exe file) with no exceptions.

And the virtual machine still operates normally if moved back to the Windows 7 host with PRO 12. No graphics problems at all...

What could cause this behavior? Is there some graphics setting one can do in the Win10 host (Player 14), which will solve the problem?

Is there some additional data we can provide to help diagnose the problem?

Some system data


Windows 10 Pro, 2018

VMWare Workstation 14 Player

Lenovo ThinkPad T470 Signature Edition

Intel Core i7-7600U CPU 2.80GHz 2.9GHz

64-bit OS, dual core processor

Intel HD Graphics 620

Driver Version:

Driver date: 2/28/2018

Driver Provider: Intel Corporation


Windows 7 Pro x64

Guest created in Workstation PRO 12 on a Windows 7 x64 machine.

0 Kudos
2 Replies

If disable 3D excelaration does the error happen?  Would you please provide vmware.log of the VM and the dmp file if created.

0 Kudos

I need to hear from the developer using the vm. I am the source of it but not the user.

But it seems likely that the 3D rendering setting in the vm display configuration is affecting the behavior.

I hope to get a response later today (9 hour time difference).

0 Kudos