VMware Communities
jimbo45
Enthusiast
Enthusiast

WKS 15.0.2 GSOD on W10 insder pro build 1809-18290-1000 (the latest)

Both Workstation and player cause Windows to abend (GSOD) -- not possible to show screen as windows dies with message : kernel - security exception. This happens on the latest Windows insider build .

The defect happens when you try to power on any GUEST - whether Windows or Linux Guests.

Any known fixes yet

Thanks

44 Replies
Scillonian
Hot Shot
Hot Shot

So recently I would expect the VMware group to solve the problem rather than Microsoft.

Personally I would say this is down to Microsoft as this only appears to affect installations with generations 6, 7, and 8 of Intel Core 'i' processors. Generation 5 and older do not appear to have this issue as well as AMD processors. (Going by how major flaws went unresolved for months in 1803 and 1809 I wouldn't hold much hope of it being fixed too soon. After all it is far more important that File Explorer gets a new icon in 18298!)

I'm running VMware Workstation Pro 15.0.2 on Windows 10 Pro Build 18290 18298 with a Core i5-2450M and Workstation still runs fine. (Build 18298 is installing.)

Well, we have complaints with both companies, hopefully one will solve the issue, otherwise VMWare is pretty much dead to users who keep their Windows up to date... 

Don't forget that we are using pre-release builds of the next version of Windows 10 here that can, and often do break, with each new build.

closerwang
Contributor
Contributor

That makes sense.

I would keep on using 18282 unless there is a fix.

Just too eager to get some updates on tablet mode even there isn't .

Reply
0 Kudos
remko_
Enthusiast
Enthusiast

Build 18282 expires 14th of December so there's little point in reverting back to the build

closerwang
Contributor
Contributor

Announcing Windows 10 Insider Preview Build 18290 - Windows Experience BlogWindows Experience Blog  says that

>Once a build expires, Insiders will be provided a warning that the build has expired and will get that warning once a day. In addition to >that, Insiders will also see User Access Control (UAC) warnings as well.

It's better facing the warnings than not powering on the guest.

remko_
Enthusiast
Enthusiast

Just curious if the various logs and dumps that were provided have turned up anything that points to the source of the error?? (/cc xishengzhang​)

xishengzhang
VMware Employee
VMware Employee

Hello, DennisGaida

Thanks a lot for your supporting and sorry for my late response. Now the dmp downloading is ongoing. Will keep you updated once there is anything found.

Thanks

Brmourato
Contributor
Contributor

Same problem here with Dell Latitude E5470 with core i7 6600U and AMD R7 M360 on windows insider 18298...

It must be some driver issue...

Reply
0 Kudos
newschapm1
Contributor
Contributor

I have the same issue on 18298.1000 and VM 14.1.5 build-10950780

A green screen of death when I try and start a VM (tried 2 different vms)

Reply
0 Kudos
skynetmiami
Contributor
Contributor

I'm surprised by VMWARE's lack of communication on this issue.  VMWARE TEAM, Where is the Solution?

Antaresbe
Contributor
Contributor

Hello; sorry for my English.

I found this topic during my research.

I wanted to install the latest Windows Insider version aka 18290.  No way to boot it for the first time (just configured it) on a Thinkpad T470p (i7 7th gen) with Windows 10 1890 and Workstation 15.0.2.   Always the same message "The firmware has encountered an unexpected exception. The VM cannot boot"  : try everything until I just checked to go bios instead of UEFI in advanced settings.

Boot and install like a charm after that.

I hope this can help someone maybe.

Reply
0 Kudos
remko_
Enthusiast
Enthusiast

Is there any update you could give us? If it helps to upload more dumps than happy to do so but there doesn't seem to be any activity or at least communication around this issue...

Reply
0 Kudos
xishengzhang
VMware Employee
VMware Employee

Hello, remko_

Thanks for the timely tracking. Now we are doing investigation based on the logs/dmps from community and it looks this is caused by something new involved in win10 insider program.

Thanks again.

remko_
Enthusiast
Enthusiast

Yes it's clearly something new as the MSDN docs for Bug Check 0x139: KERNEL_SECURITY_CHECK_FAILURE state that parameter 1 contains the type of corruption.

WinDbg shows Arg1: 000000000000003b, Type of memory safety violation

However the table on the MSDN page doesn't list any types beyond 39.

EXCEPTION_RECORD:  fffff8024e270d68 -- (.exr 0xfffff8024e270d68)

ExceptionAddress: fffff8024b5d2be1 (nt!KiInterruptSubDispatchNoLockNoEtw+0x0000000000000121)

   ExceptionCode: c0000409 (Security check failure or stack buffer overrun)

  ExceptionFlags: 00000001

NumberParameters: 1

   Parameter[0]: 000000000000003b

Subcode: 0x3b (unknown subcode)

CPU_COUNT: 8

CPU_MHZ: af8

CPU_VENDOR:  GenuineIntel

CPU_FAMILY: 6

CPU_MODEL: 9e

CPU_STEPPING: 9

CPU_MICROCODE: 6,9e,9,0 (F,M,S,R)  SIG: 8E'00000000 (cache) 8E'00000000 (init)

BLACKBOXBSD: 1 (!blackboxbsd)

BLACKBOXPNP: 1 (!blackboxpnp)

DEFAULT_BUCKET_ID:  CODE_CORRUPTION

BUGCHECK_STR:  0x139

PROCESS_NAME:  vmware-vmx.exe

CURRENT_IRQL:  d

WATSON_BKT_EVENT:  BEX

ERROR_CODE: (NTSTATUS) 0xc0000409 - The system detected an overrun of a stack-based buffer in this application. This overrun could potentially allow a malicious user to gain control of this application.

EXCEPTION_CODE: (NTSTATUS) 0xc0000409 - The system detected an overrun of a stack-based buffer in this application. This overrun could potentially allow a malicious user to gain control of this application.

EXCEPTION_CODE_STR:  c0000409

EXCEPTION_PARAMETER1:  000000000000003b

ANALYSIS_SESSION_HOST:  MYMACHINE

ANALYSIS_SESSION_TIME:  12-19-2018 00:11:56.0247

ANALYSIS_VERSION: 10.0.17134.12 amd64fre

LAST_CONTROL_TRANSFER:  from fffff8024b5e2fa9 to fffff8024b5d10a0

STACK_TEXT: 

fffff802`4e270ae8 fffff802`4b5e2fa9 : 00000000`00000139 00000000`0000003b fffff802`4e270e10 fffff802`4e270d68 : nt!KeBugCheckEx

fffff802`4e270af0 fffff802`4b5e33d0 : 00000000`00000004 fffff802`4e270cb0 fffff802`4e270cb0 fffff802`598328c4 : nt!KiBugCheckDispatch+0x69

fffff802`4e270c30 fffff802`4b5e175f : 00000000`00000000 00000000`00000000 00000000`00000018 ffff848b`b4d0b8c0 : nt!KiFastFailDispatch+0xd0

fffff802`4e270e10 fffff802`4b5d2be1 : 00000000`00000000 00000000`00000000 fffff802`4bf07cb0 ffff8108`1b97f280 : nt!KiRaiseSecurityCheckFailure+0x31f

fffff802`4e270fa8 00000000`000004e1 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiInterruptSubDispatchNoLockNoEtw+0x121

00000000`00000000 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x4e1

dosmond
Contributor
Contributor

I have same issue with the following

I am on an Alienware running Win 10 Pro and per WS 15.0.2 build-10952284 using Windows 10, 64-bit  (Build 18298) 10.0.18298 and was fine till I upgraded to 15.0.2. 

 

Host Name:                 OSMOND-17R4

OS Name:                   Microsoft Windows 10 Pro Insider Preview

OS Version:                10.0.18298 N/A Build 18298

OS Manufacturer:           Microsoft Corporation

OS Configuration:          Standalone Workstation

OS Build Type:             Multiprocessor Free

Registered Owner:          N/A

Registered Organization:   N/A

Product ID:                00330-50402-32962-AAOEM

Original Install Date:     12/11/2018, 4:28:44 PM

System Boot Time:          12/19/2018, 11:23:32 AM

System Manufacturer:       Alienware

System Model:              Alienware 17 R4

System Type:               x64-based PC

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

                           [01]: Intel64 Family 6 Model 158 Stepping 9 GenuineIntel ~2800 Mhz

BIOS Version:              Alienware 1.5.0, 9/10/2018

Windows Directory:         C:\WINDOWS

System Directory:          C:\WINDOWS\system32

Boot Device:               \Device\HarddiskVolume3

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

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

Time Zone:                 (UTC-05:00) Eastern Time (US & Canada)

Total Physical Memory:     16,257 MB

Available Physical Memory: 8,842 MB

Virtual Memory: Max Size:  18,689 MB

Virtual Memory: Available: 7,644 MB

Virtual Memory: In Use:    11,045 MB

Reply
0 Kudos
fpmurphy
Contributor
Contributor

Looks like Microsoft fixed something in their code.  The problem went away when I upgraded to Windows 10 Insider Preview 18305.1000 today.

Reply
0 Kudos
newschapm1
Contributor
Contributor

Yes good news10.0.18305.1000 fixed it for me as well. When using VMWorkstation 14.1.5 build-10950780.

I can start VMs as normal without the green screen of death.

Reply
0 Kudos
closerwang
Contributor
Contributor

  • We fixed an issue resulting in bug checks with error “KERNEL SECURITY CHECK FAILURE” while creating/launching VMs or installing/performing scans with certain AV Apps.

It seems the problem has been solved.

I will update to 18305.1003 

Reply
0 Kudos
shildebrandt
VMware Employee
VMware Employee

Don't know if it is really fixed. VM start fine now but they will freeze all the time. Connecting USB - freeze. Waking them up after suspend - freeze. Worst vmware-vmx will hang and can't be stopped in task manager.

Reply
0 Kudos
Scillonian
Hot Shot
Hot Shot

The UWP Task Manager is not very reliable when it comes to killing Win32 applications I have found. It is not only VMware Workstation that it can't kill.

You could try Process Explorer from www.sysinternals.com (redirects to the correct Microsof TechNet URL that I can never remember) Which is a Win32 application so should have no trouble killing the rogue Workstation instances.

Also so worth a check in Windows Security Center that there are no hardware security features or Virtualisation Based Security features enable that might disrupt Workstation. (All my processors are too old for these features so I can't give any first hand pointers to what might be there.)

Reply
0 Kudos
dosmond
Contributor
Contributor

Anyone having an issue with Win 10 Pro 18305 and WS 15.0.2 creating new VM for Ubuntu 16.04?  I have started the process multiple times and it just hangs indicating it is building the VM.  Yes there is no issue with the check as previously reported and current VMs will run (have not checked them all) but cannot create a new one.  This is all I get when it is installing Ubuntu but it never completes.

pastedImage_0.png

Reply
0 Kudos