Windows 10 crashing when powering on VM on VMware workstation

nhsk4u — Wed, 01 Dec 2021 12:49:10 GMT

I got new desktop installed with Windows 10 and have installed it with up to date patches. I have installed VMware workstation and created VM. When I poweron the VM on workstation. Base windows 10 is crashing with below errors

I tried removing Mcafee antivirus, tried disabling VMware USB arbitrator service, enabled virtualization technology on VM settings also but issue persists. Have tried performing dump analysis but couldnt figure out the problem but I believe it is due to VMware workstation only as that is the only action I am performing when bsod happens. I have tried different versions of VMware workstation and result is same

another observation is that I am getting below popup that some files are deleted.

Kindly check below debug analysis and guide me. Thanks for your help

systeminfo:

C:\Windows\system32>systeminfo

Host Name: PRASANNA

OS Name: Microsoft Windows 10 Home

OS Version: 10.0.19044 N/A Build 19044

OS Manufacturer: Microsoft Corporation

OS Configuration: Standalone Workstation

OS Build Type: Multiprocessor Free

Registered Owner: admin

Registered Organization:

Product ID: 00326-00883-55405-AAOEM

Original Install Date: 19/8/2021, 2:24:35 pm

System Boot Time: 1/12/2021, 8:00:49 pm

System Manufacturer: Gigabyte Technology Co., Ltd.

System Model: B550 AORUS ELITE V2

System Type: x64-based PC

Processor(s): 1 Processor(s) Installed.

[01]: AMD64 Family 25 Model 33 Stepping 0 AuthenticAMD ~3401 Mhz

BIOS Version: American Megatrends International, LLC. F13, 8/7/2021

Windows Directory: C:\Windows

System Directory: C:\Windows\system32

Boot Device: \Device\HarddiskVolume2

System Locale: en-us;English (United States)

Input Locale: en-us;English (United States)

Time Zone: (UTC+08:00) Kuala Lumpur, Singapore

Total Physical Memory: 65,479 MB

Available Physical Memory: 59,697 MB

Virtual Memory: Max Size: 75,207 MB

Virtual Memory: Available: 68,267 MB

Virtual Memory: In Use: 6,940 MB

Page File Location(s): C:\pagefile.sys

Domain: WORKGROUP

Logon Server: \\PRASANNA

Hotfix(s): 7 Hotfix(s) Installed.

[01]: KB5007289

[02]: KB5000736

[03]: KB5003791

[04]: KB5007253

[05]: KB5006753

[06]: KB5007273

[07]: KB5005260

Network Card(s): 6 NIC(s) Installed.

[01]: Realtek Gaming 2.5GbE Family Controller

Connection Name: Ethernet 2

Status: Media disconnected

[02]: Intel(R) Wi-Fi 6 AX200 160MHz

Connection Name: Wi-Fi 2

DHCP Enabled: Yes

DHCP Server: 192.168.1.254

IP address(es)

[01]: 192.168.1.98

[02]: fe80::d9f:75f9:bda4:f2fc

[03]: Bluetooth Device (Personal Area Network)

Connection Name: Bluetooth Network Connection 2

Status: Media disconnected

[04]: VMware Virtual Ethernet Adapter for VMnet1

Connection Name: VMware Network Adapter VMnet1

DHCP Enabled: Yes

DHCP Server: 192.168.138.254

IP address(es)

[01]: 192.168.138.1

[02]: fe80::7c9c:c86d:885a:1ac7

[05]: VMware Virtual Ethernet Adapter for VMnet8

Connection Name: VMware Network Adapter VMnet8

DHCP Enabled: Yes

DHCP Server: 192.168.29.254

IP address(es)

[01]: 192.168.29.1

[02]: fe80::b4b3:a232:1c7:40db

[06]: VirtualBox Host-Only Ethernet Adapter

Connection Name: VirtualBox Host-Only Network

DHCP Enabled: No

IP address(es)

[01]: 192.168.56.1

[02]: fe80::e5ea:d1f3:b91a:a725

Hyper-V Requirements: VM Monitor Mode Extensions: Yes

Virtualization Enabled In Firmware: Yes

Second Level Address Translation: Yes

Data Execution Prevention Available: Yes

eventvwr:

The computer has rebooted from a bugcheck. The bugcheck was: 0x0000003b (0x00000000c0000005, 0xfffff80311ffe4a2, 0xffff9b8174106920, 0x0000000000000000). A dump was saved in: C:\Windows\MEMORY.DMP. Report Id: e6387710-b6eb-4e33-a8e2-81efbda52575.

dump analysis:

*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

SYSTEM_SERVICE_EXCEPTION (3b)
An exception happened while executing a system service routine.
Arguments:
Arg1: 00000000c0000005, Exception code that caused the BugCheck
Arg2: fffff80311ffe4a2, Address of the instruction which caused the BugCheck
Arg3: ffff9b8174106920, Address of the context record for the exception that caused the BugCheck
Arg4: 0000000000000000, zero.

Debugging Details:
------------------

KEY_VALUES_STRING: 1

    Key  : Analysis.CPU.mSec
    Value: 3983

    Key  : Analysis.DebugAnalysisManager
    Value: Create

    Key  : Analysis.Elapsed.mSec
    Value: 4128

    Key  : Analysis.Init.CPU.mSec
    Value: 421

    Key  : Analysis.Init.Elapsed.mSec
    Value: 36369

    Key  : Analysis.Memory.CommitPeak.Mb
    Value: 99

    Key  : WER.OS.Branch
    Value: vb_release

    Key  : WER.OS.Timestamp
    Value: 2019-12-06T14:06:00Z

    Key  : WER.OS.Version
    Value: 10.0.19041.1


FILE_IN_CAB:  MEMORY.DMP

BUGCHECK_CODE:  3b

BUGCHECK_P1: c0000005

BUGCHECK_P2: fffff80311ffe4a2

BUGCHECK_P3: ffff9b8174106920

BUGCHECK_P4: 0

CONTEXT:  ffff9b8174106920 -- (.cxr 0xffff9b8174106920)
rax=0000000000000805 rbx=ffff9b81740ac180 rcx=ffff900342637c80
rdx=0000000000000000 rsi=ffffe1892096b080 rdi=ffff9b81740b7840
rip=fffff80311ffe4a2 rsp=ffff9003426372c0 rbp=000fe067bcbbbdff
 r8=0000000000000000  r9=ffff900342637298 r10=0000000000000028
r11=ffff8b7e41000030 r12=00000000000000cc r13=ffff9003483770c8
r14=ffffe189201ed140 r15=ffff9b81740bb000
iopl=0         nv up ei pl zr ac po cy
cs=0010  ss=0018  ds=002b  es=002b  fs=0053  gs=002b             efl=00050257
nt!SwapContext+0x372:
fffff803`11ffe4a2 0fc719          xrstors [rcx]
Resetting default scope

BLACKBOXBSD: 1 (!blackboxbsd)


BLACKBOXNTFS: 1 (!blackboxntfs)


BLACKBOXWINLOGON: 1

PROCESS_NAME:  csrss.exe

STACK_TEXT:  
ffff9003`426372c0 fffff803`11ffde56     : ffffe189`20a480c8 ffff8686`406062d0 ffffd3e3`374caa70 ffffd3e3`374caaf0 : nt!SwapContext+0x372
ffff9003`42637300 fffff803`11e0c800     : ffff9b81`ffffffff 00000000`00000000 00000000`00000000 00000000`00030d40 : nt!KiSwapContext+0x76
ffff9003`42637440 fffff803`11e0bd2f     : ffff86bc`00000015 ffff86bc`0000000c ffff9003`42637630 00000000`00000000 : nt!KiSwapThread+0x500
ffff9003`426374f0 fffff803`11e8045e     : ffffe189`00000000 ffff9003`00000000 00000000`00000100 00000000`00000000 : nt!KiCommitThreadWait+0x14f
ffff9003`42637590 ffff86bc`11c12dd8     : 00000000`00000006 ffff86bc`11e4d330 00000000`00000006 ffff8686`4067c3d0 : nt!KeWaitForMultipleObjects+0x2be
ffff9003`426376a0 ffff86bc`11f9e248     : ffff8686`4062a8a0 ffff8686`4062a8a0 00000000`00000004 00000000`00000001 : win32kbase!LegacyInputDispatcher::WaitAndDispatch+0x88
ffff9003`426377d0 ffff86bc`11f9de14     : 00000000`00000004 00000000`00000004 00000000`0000000d ffff86bc`11e4eb00 : win32kfull!xxxDesktopThreadWaiter+0x130
ffff9003`42637850 ffff86bc`11c79133     : ffffe189`2096b080 ffffe189`2096b080 00000000`00000000 00000000`00000005 : win32kfull!xxxDesktopThread+0x544
ffff9003`42637930 ffff86bc`11f72d20     : ffffe189`2096b080 00000000`00000000 00000000`00000005 00000000`00000005 : win32kbase!xxxCreateSystemThreads+0xc3
ffff9003`42637a60 ffff86bc`1248474d     : ffffe189`2096b080 ffffe189`2096b080 00000000`00000000 00000000`00000000 : win32kfull!NtUserCallNoParam+0x70
ffff9003`42637a90 fffff803`12008ab8     : ffffe189`00000005 00000000`00000005 00000221`da004220 00000000`000005c4 : win32k!NtUserCallNoParam+0x15
ffff9003`42637ac0 00007ffd`83ce10e4     : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceCopyEnd+0x28
000000c3`3c07fd38 00000000`00000000     : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x00007ffd`83ce10e4


SYMBOL_NAME:  win32kbase!LegacyInputDispatcher::WaitAndDispatch+88

MODULE_NAME: win32kbase

IMAGE_NAME:  win32kbase.sys

STACK_COMMAND:  .cxr 0xffff9b8174106920 ; kb

BUCKET_ID_FUNC_OFFSET:  88

FAILURE_BUCKET_ID:  0x3B_c0000005_win32kbase!LegacyInputDispatcher::WaitAndDispatch

OS_VERSION:  10.0.19041.1

BUILDLAB_STR:  vb_release

OSPLATFORM_TYPE:  x64

OSNAME:  Windows 10

FAILURE_ID_HASH:  {a70e38ee-0ca9-b580-2ee5-8175a879e82e}

Followup:     MachineOwner
---------

Re: Windows 10 crashing when powering on VM on VMware workstation

JesusRaf — Thu, 02 Dec 2021 17:01:24 GMT

Hola

A mi pasa exactamente lo mismo y no doy con la solucion.

Como información solo me pasa en PC´s recién comprados que ya vienen de fabrica con esta compilación 10.0.19044 (en esos si tengo el pantallazo azul y reboot del pc después de darle al "play"i para iniciar la maquina virtual)

Sin embargo en equipos antiguos los cuales se han updatado ellos a la misma compilacion 10.0.19044 no falla funciona correctamente.

Alguien conoce la forma de solucionarlo?

Un saludo

Re: Windows 10 crashing when powering on VM on VMware workstation

scott28tt — Thu, 02 Dec 2021 20:27:03 GMT

1. Expect your thread to be moved to the area for Workstation

2. Use the “spoiler” function for text dumps to prevent the thread from sprawling - a spoiler can be added by pressing the triangle icon (with ! symbol) on the post editor toolbar

Makes your thread SO much easier to scroll through eh?

topic Windows 10 crashing when powering on VM on VMware workstation in VMware Workstation Pro Discussions

Windows 10 crashing when powering on VM on VMware workstation

Re: Windows 10 crashing when powering on VM on VMware workstation

Re: Windows 10 crashing when powering on VM on VMware workstation