VMware

BSOD on Workstation Pro 15.5.6 (running RHEL 7…. |VMware Communities

Hi;

 

I just got a BSOD running a Windows 10 Host (1909). I was running a RHEL 7.7 Linux Guest full-screen at the time. (I had just returned from a break).

 

I got a mini-dump and a memory.dmp.

 

Running windbg against the memory.dmp calls out what looks to the casual observer like Workstation driver and process references:

 

“FAULTING_PROCESSOR: 6

 

PROCESS_NAME:  vmware-vmx.exe

 

FAULTING_THREAD:  ffffdd86e5270080″

 

and

 

STACK_TEXT: 

ffff8603`bfddf468 fffff801`4f778228 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : vmx86+0x100a

ffff8603`bfddf470 fffff801`4f77abdb : 00000000`00000000 00000000`00000000 ffff8603`bfddf938 00000000`00000000 : vmx86+0x8228

ffff8603`bfddf5b0 fffff801`4f771f13 : 00000000`000001b0 00000000`00000001 ffff8603`bfddf938 ffffdd87`01c65430 : vmx86+0xabdb

ffff8603`bfddf680 fffff801`4f77293e : 00000000`00000000 fffff801`391543a9 00000000`00000000 fffff801`38f132d4 : vmx86+0x1f13

ffff8603`bfddf860 fffff801`394b2a2b : 00000000`000003f8 fffff801`38f13269 00000000`00000000 ffffdd86`fab5d7a0 : vmx86+0x293e

ffff8603`bfddf8c0 fffff801`394b22f6 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!IopXxxControlFile+0x71b

ffff8603`bfddf9e0 fffff801`38fd3c18 : 00000000`746c6644 ffff8603`bfddfa00 00000000`00000000 ffff8f85`bb997c40 : nt!NtDeviceIoControlFile+0x56

ffff8603`bfddfa50 00007ffe`f23dc154 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceCopyEnd+0x28

00000073`dc9ff5c8 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x00007ffe`f23dc154

 

 

STACK_COMMAND:  .thread 0xffffdd86e5270080 ; kb

 

SYMBOL_NAME:  vmx86+100a

 

MODULE_NAME: vmx86

 

IMAGE_NAME:  vmx86.sys

 

BUCKET_ID_FUNC_OFFSET:  100a

 

FAILURE_BUCKET_ID:  CLOCK_WATCHDOG_TIMEOUT_INTERRUPTS_DISABLED_vmx86!unknown_function”

 

I’ll attach the entire !analyze -v output. (I’m only familiar enough with WinDbg to produce the !analyze output at this time, so I’m not sure what else would be helpful).

 

Is this an issue with the workstation driver? The system has an E5-1650 V4 Xeon CPU, for what its worth.

 

Thanks;


Source link

Related Articles

Leave a Reply

Your email address will not be published. Required fields are marked *

Close