0:015> !analyze -v
*******************************************************************************
* *
* Exception Analysis *
* *
*******************************************************************************
*** ERROR: Module load completed but symbols could not be loaded for vmware-vmx.exe
FAULTING_IP:
nvd3dumx+6db8af
000007fa`6b1cb8af 83bac000000000 cmp dword ptr [rdx+0C0h],0
EXCEPTION_RECORD: ffffffffffffffff -- (.exr 0xffffffffffffffff)
ExceptionAddress: 000007fa6b1cb8af (nvd3dumx+0x00000000006db8af)
ExceptionCode: c0000005 (Access violation)
ExceptionFlags: 00000000
NumberParameters: 2
Parameter[0]: 0000000000000000
Parameter[1]: 00000000000000c0
Attempt to read from address 00000000000000c0
DEFAULT_BUCKET_ID: NULL_CLASS_PTR_READ
PROCESS_NAME: vmware-vmx.exe
ERROR_CODE: (NTSTATUS) 0xc0000005 - The instruction at 0x%08lx referenced memory at 0x%08lx. The memory could not be %s.
EXCEPTION_CODE: (NTSTATUS) 0xc0000005 - The instruction at 0x%08lx referenced memory at 0x%08lx. The memory could not be %s.
EXCEPTION_PARAMETER1: 0000000000000000
EXCEPTION_PARAMETER2: 00000000000000c0
READ_ADDRESS: 00000000000000c0
FOLLOWUP_IP:
nvd3dumx+6db8af
000007fa`6b1cb8af 83bac000000000 cmp dword ptr [rdx+0C0h],0
APPLICATION_VERIFIER_FLAGS: 0
APP: vmware-vmx.exe
FAULTING_THREAD: 0000000000001558
PRIMARY_PROBLEM_CLASS: NULL_CLASS_PTR_READ
BUGCHECK_STR: APPLICATION_FAULT_NULL_CLASS_PTR_READ
LAST_CONTROL_TRANSFER: from 000007fa6b24ed5c to 000007fa6b1cb8af
STACK_TEXT:
00000000`0eafef40 000007fa`6b24ed5c : 00000000`009733a8 00000000`00000000 00000000`00000001 00000000`00000000 : nvd3dumx+0x6db8af
00000000`0eafef70 000007fa`6b18baa7 : 00000000`05fb8700 00000000`00000000 00000000`00000000 00000000`05fbf498 : nvd3dumx+0x75ed5c
00000000`0eafefa0 000007fa`6b18850d : 00000000`00000000 00000000`00000001 000007fa`00000000 00000000`00000000 : nvd3dumx+0x69baa7
00000000`0eaff7c0 000007fa`6b1a7e43 : 00000000`00000000 00000000`05fbb290 00000000`00000000 00000000`00000000 : nvd3dumx+0x69850d
00000000`0eaff7f0 000007fa`6b42c07f : 00000000`00000000 00000000`05fbb290 00000000`00000000 00000000`00000000 : nvd3dumx+0x6b7e43
00000000`0eaff820 000007fa`6b42c2ca : 000007fa`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nvd3dumx!QueryOglResource+0x1d59bf
00000000`0eaff850 000007fa`946e1832 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nvd3dumx!QueryOglResource+0x1d5c0a
00000000`0eaff880 000007fa`96bcd609 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : kernel32!BaseThreadInitThunk+0x1a
00000000`0eaff8b0 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : ntdll!RtlUserThreadStart+0x1d
SYMBOL_STACK_INDEX: 0
SYMBOL_NAME: nvd3dumx+6db8af
FOLLOWUP_NAME: MachineOwner
MODULE_NAME: nvd3dumx
IMAGE_NAME: nvd3dumx.dll
DEBUG_FLR_IMAGE_TIMESTAMP: 5211100c
STACK_COMMAND: ~15s; .ecxr ; kb
FAILURE_BUCKET_ID: NULL_CLASS_PTR_READ_c0000005_nvd3dumx.dll!Unknown
BUCKET_ID: APPLICATION_FAULT_NULL_CLASS_PTR_READ_nvd3dumx+6db8af
Followup: MachineOwner
===
vm hardware revision is 9, running Windows 7 Enterprise x64. Host is running Windows 8. This occurs between once every two days to 3 times a day, give or take.
Current nvidia driver version is 326.80 beta. I've tried rolling back to the most recent whql version but the same issue occurs with the same parameters. I've read that disabling 3d acceleration is a workaround for the issue, so I have done so. However, I frequently use the Aero capabilities of this vm and they are now unavailable. Any ideas what is going on here and how I can resolve the issue while still retaining the 3d acceleration functionality?