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
closerwang
Contributor
Contributor

i have the same issuse

I just rolled back to 18282 which keeps giving the warning "the build will expires in 14th December" to avoided the crash.

need a solution too.

Reply
0 Kudos
sandersf
Contributor
Contributor

I am encountering the same issue.  The Windows 10 rollback works, but then I get the warning about the build expiring.

Reply
0 Kudos
HansLiang
Contributor
Contributor

I have the network issue, when I upgrade to 15.0.2 it won't work for network. the guest unable to get the system's networking setting.

Reply
0 Kudos
Activer
Contributor
Contributor

I got the same question, here is Windows WerReport info:

<?xml version="1.0" encoding="UTF-16"?>

<WERReportMetadata>

<OSVersionInformation>

<WindowsNTVersion>10.0</WindowsNTVersion>

<Build>18290</Build>

<Product>(0x30): Windows 10 Pro</Product>

<Edition>Professional</Edition>

<BuildString>18290.1000.amd64fre.rs_prerelease.181121-1501</BuildString>

<Revision>1000</Revision>

<Flavor>Multiprocessor Free</Flavor>

<Architecture>X64</Architecture>

<LCID>2052</LCID>

</OSVersionInformation>

<ProblemSignatures>

<EventType>BlueScreen</EventType>

<Parameter0>139</Parameter0>

<Parameter1>3b</Parameter1>

<Parameter2>ffff80896f4a7060</Parameter2>

<Parameter3>ffff80896f4a6fb8</Parameter3>

<Parameter4>0</Parameter4>

<Parameter5>10_0_18290</Parameter5>

<Parameter6>0_0</Parameter6>

<Parameter7>256_1</Parameter7>

</ProblemSignatures>

<DynamicSignatures>

<Parameter1>10.0.18290.2.0.0.256.48</Parameter1>

<Parameter2>2052</Parameter2>

</DynamicSignatures>

<SystemInformation>

<MID>4661AB05-B526-413F-98C1-39782B5B722E</MID>

<SystemManufacturer>TSINGHUA TONGFANG COMPUTER</SystemManufacturer>

<SystemProductName>S760</SystemProductName>

<BIOSVersion>E006AP0</BIOSVersion>

<OSInstallDate>1543456441</OSInstallDate>

<OSInstallTime>2018-11-29T01:53:58Z</OSInstallTime>

<TimeZoneBias>-08:00</TimeZoneBias>

</SystemInformation>

<SecureBootState>

<UEFISecureBootEnabled>0</UEFISecureBootEnabled>

</SecureBootState>

<ReportInformation>

<Guid>26c0621d-42bf-4a4e-b690-cccd7c4fff2d</Guid>

<CreationTime>2018-12-03T05:59:19Z</CreationTime>

</ReportInformation>

</WERReportMetadata>

Reply
0 Kudos
xishengzhang
VMware Employee
VMware Employee

Hello, jimbo45 and All

Thanks a lot to raise this issue here. I tried to power on windows VM on host which has been upgraded to the same inside programmer build 18290.1000, however this issue cannot been reproduced. So we have to ask your help to upload the log for further analysis. Thanks.

One thing to clarify the status of the VM:

1. It can be powered on, but shown in blue-screen.

2. It cannot be powered on because of the issue.

If it is the 1st situation, we need the vmware.log under vm directory and vm dmp file in guest C:\Windows\memory.dmp, maybe you need to start up the guest in safe mode to get the dmp file.

If it is the 2nd symptom, please just upload vmware.log for investigation.

Log upload way:

  1. Log in ftpsite.vmware.com through https://ftpsite.vmware.com
  2. Username: inbound        password: inbound
  3. upload logs accordingly, then let us know the log names.
Reply
0 Kudos
xishengzhang
VMware Employee
VMware Employee

Hello, closerwang and sandersf

According to your description, this GSOD issue could disappear after roll back the host build, maybe it is caused the MS inside patches. Could you please raise this issue to MS as well. At the same time, we will do the investigation in parallel after we get the logs. Thanks.

Reply
0 Kudos
Activer
Contributor
Contributor

Hi,I meet 2nd status,

2. It cannot be powered on because of the issue.

The log this very simple because GSOD no more things can logged.

2018-12-03T13:58:28.835+08:00| vmx| I125: Log for VMware Workstation pid=7632 version=15.0.2 build=build-10952284 option=Release

2018-12-03T13:58:28.835+08:00| vmx| I125: The process is 64-bit.

2018-12-03T13:58:28.835+08:00| vmx| I125: Host codepage=windows-936 encoding=GBK

2018-12-03T13:58:28.835+08:00| vmx| I125: Host is Windows 10, 64-bit  (Build 18290)

NULL NULL NULL......

Reply
0 Kudos
Scillonian
Hot Shot
Hot Shot

This looks to me more like a specific hardware combination issue that Microsoft needs to address.

For those with this GSOD and an interest in tracking it, this is what Microsoft has to say about KERNEL_SECURITY_CHECK_FAILURE:

https://docs.microsoft.com/en-us/windows-hardware/drivers/debugger/bug-check---bug-check-0x139-kerne...

I'm running VMware Workstation Pro 15.0.2 on Windows 10 Pro Build 18290 and both Linux and Windows VMs, 32-bit and 64-bit, run without issue.

The host hardware is a circa 2012 Dell Inspiron 15 (N5050) laptop with a Core i5-2450M CPU, 8 GiB RAM, primary drive is an SSD for Windows OS (dual boot with LMDE3) and apps, and a secondary SSD in place of optical drive where the VMs live.

Reply
0 Kudos
closerwang
Contributor
Contributor

After upgrade to 18290.1000, i got the issue again and the same log with sandersf.

Maybe it's some hardware combination issue as Scillonian stated.

Here is my laptop (thinkpad x1 yoga 3rd) information:

CPU:  Core i7-8550

Mem: 16GB  LPDDR3 / soldered to systemboard, no sockets

SSD: SAMSUNG MZVLB1T0HALR-000L7 1TB

Reply
0 Kudos
Scillonian
Hot Shot
Hot Shot

Based on the reports so far that have listed the host CPU, it is the 6TH, 7TH and 8TH generation Intel Core CPUs that are affected.

xishengzhang
VMware Employee
VMware Employee

Hello Activer and closerwang

Could you please upload the dmp file under C:\Windows\memory.dmp from host?

Thanks a lot

Reply
0 Kudos
DennisGaida
Contributor
Contributor

The same issue seems to be reported here:

Kernel Security Check Failure after Updating Host to Windows 10 Build 18290 [Skip Ahead]

I tried sending you a link to the memory.dmp file xishengzhang​ but I always receive an error via private message. Send me an e-mail and I'll reply with a download link to the dump.

Also check my reply in the other thread for more memory dump info:

Re: Kernel Security Check Failure after Updating Host to Windows 10 Build 18290 [Skip Ahead]

Reply
0 Kudos
Malkolmisiek
Contributor
Contributor

I have same issue GSOD after power on guest.

Here is my memory.dmp

On Sat 08.12.2018 13:16:21 your computer crashed or a problem was reported
crash dump file: C:\WINDOWS\MEMORY.DMP
This was probably caused by the following module: vmx86.sys (vmx86+0x10BE)
Bugcheck code: 0x139 (0x3B, 0xFFFFDF0494379060, 0xFFFFDF0494378FB8, 0x0)
Error: KERNEL_SECURITY_CHECK_FAILURE
file path: C:\WINDOWS\system32\drivers\vmx86.sys
product: VMware kernel driver
company: VMware, Inc.
description: VMware kernel driver
Bug check description: The kernel has detected the corruption of a critical data structure.
A third party driver was identified as the probable root cause of this system error. It is suggested you look for an update for the following driver: vmx86.sys (VMware kernel driver, VMware, Inc.).
Google query: vmx86.sys VMware, Inc. KERNEL_SECURITY_CHECK_FAILURE

It clearly names VMware kernel driver as the culprit but updating to latest program version and running "check for updates" show no updates for vmx86.sys (VMware kernel driver, VMware, Inc.)

Reply
0 Kudos
DennisGaida
Contributor
Contributor

I have uploaded the memory.dmp file and VMware.log file to your FTP site. Filename: DennisG_20181210.zip xishengzhang

Reply
0 Kudos
remko_
Enthusiast
Enthusiast

I have issue #2 GSOD on 18290 and cannot start VM, uploaded vmware.log as vmware-remko_.zip but only has these contents:

2018-12-10T12:38:18.663+01:00| vmx| I125: Log for VMware Workstation pid=16188 version=15.0.2 build=build-10952284 option=Release

2018-12-10T12:38:18.663+01:00| vmx| I125: The process is 64-bit.

2018-12-10T12:38:18.663+01:00| vmx| I125: Host codepage=windows-1252 encoding=windows-1252

2018-12-10T12:38:18.663+01:00| vmx| I125: Host is Windows 10, 64-bit  (Build 18290)

NUL NUL NUL NUL  

Reply
0 Kudos
closerwang
Contributor
Contributor

it seems that the build 18298 has just been released.

Reply
0 Kudos
SimArchitect
Contributor
Contributor

20181211_044306.jpg

Yes. I installed it, tried it, same problem.  

Reply
0 Kudos
closerwang
Contributor
Contributor

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

Reply
0 Kudos
SimArchitect
Contributor
Contributor

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...  

Reply
0 Kudos