VMware Communities
SimArchitect
Contributor
Contributor
Jump to solution

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

The computer just crashes wish the Green Screen of Death showing the error KERNEL_SECURITY_CHECK_FAILURE anytime I try to run a Virtual Machine, no matter which guest operating system I try to run.

Same problem with VMWare Workstation 14 and 15.

20181201_221028.jpg

1 Solution

Accepted Solutions
briantimp
Contributor
Contributor
Jump to solution

Yes, for me the latest insider build resolved the issue!

View solution in original post

32 Replies
JXHUANG
Contributor
Contributor
Jump to solution

I also got the same issue.:smileyconfused:

MichaelVach
Contributor
Contributor
Jump to solution

Same here

gaussgun
Contributor
Contributor
Jump to solution

+1, same issue

JXHUANG
Contributor
Contributor
Jump to solution

If it's urgency, can use virtualbox first.

Sl4dd0
Contributor
Contributor
Jump to solution

Same issue here. What's everyone else running on? My specs below:

PRIME Z270-K rev.00 Mainboard

Intel(R) Core(TM) i7-7700 CPU @ 3.60GHz (Using onboard Intel HD Graphics 630 only)

Kingston RAM DDR4-2400 32 GB (KHX2400C15/16G)

Microsoft Windows 10 Professional 64-bit 1809 (Build 18290)

Scillonian
Hot Shot
Hot Shot
Jump to solution

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.

This may or may not be relevant, but this laptop is old enough not to have any hardware based security features such as TPM and SecureBoot.

What does the GSOD entry in the Windows Event Viewer say?

Sl4dd0
Contributor
Contributor
Jump to solution

The computer has rebooted from a bugcheck.  The bugcheck was: 0x00000139 (0x000000000000003b, 0xffffc081ec560e10, 0xffffc081ec560d68, 0x0000000000000000). A dump was saved in: C:\WINDOWS\MEMORY.DMP. Report Id: fd58491a-bdf0-41d4-b3b6-4a4379275284.

AdrianRutter71
Contributor
Contributor
Jump to solution

I have the same the same issue, I recovered back to 18282 and my VM's are working fine, so I have switched to the Slow lane until I find it has been resolved on the Fast lane.

I reverted overnight initially, but the preview reinstalled 18290, so I had to revert interactively, to allow me time to switch lanes.

jemibu
Contributor
Contributor
Jump to solution

Same issue for me with 14.5.1. Lenovo M900 (Core i7 2.8, 32gb Kingston, 1TB crucial SSD) and Surface Book Pro.

This issue was added to the Feedback Hub on 11/30 and was marked as "we've got it" by Microsoft within the past few days (https://aka.ms/AA3dxql). I'm skeptical Smiley Wink

Windows recovery was my workaround. I'm holding at 18277 on my workstation but will keep my laptop in fast ring to test this issue against future updates.

SimArchitect
Contributor
Contributor
Jump to solution

I had also reported the bug on the Feedback Hub: https://aka.ms/AA3f8sd

Reply
0 Kudos
jemibu
Contributor
Contributor
Jump to solution

upvoted Smiley Happy

anderswallgren
Contributor
Contributor
Jump to solution

+1

Reply
0 Kudos
patboyBell
Contributor
Contributor
Jump to solution

+1

Reply
0 Kudos
Malkolmisiek
Contributor
Contributor
Jump to solution

I have the same issue after update. I tried installing VMWare 12.x, 14.x, currently have installed Pro 15.0.2 build-10952284 evaluation copy.

Each one with same result when I try to run guest windows crashes with dump info:

Crash dumps are enabled on your computer.

Crash dump directories:

C:\WINDOWS

C:\WINDOWS\Minidump

On Sat 08.12.2018 13:16:21 your computer crashed or a problem was reported
crash dump file: C:\WINDOWS\Minidump\120818-8718-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x1BFF00)
Bugcheck code: 0x139 (0x3B, 0xFFFFDF0494379060, 0xFFFFDF0494378FB8, 0x0)
Error: KERNEL_SECURITY_CHECK_FAILURE
file path: C:\WINDOWS\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: The kernel has detected the corruption of a critical data structure.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.


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

Any ideas someone?

I'm running:

System Information (local)


Computer name: DESKTOP-17DAG0G
Windows version: Windows 10 , 10.0, build: 18290
Windows dir: C:\WINDOWS
Hardware: MS-7A82, MSI, H110M GRENADE (MS-7A82)
CPU: GenuineIntel Intel(R) Core(TM) i3-7100 CPU @ 3.90GHz Intel586, level: 6
4 logical processors, active mask: 15
RAM: 8538394624 bytes total

DennisGaida
Contributor
Contributor
Jump to solution

Same issue here - I'm glad it's also newer versions of VMWare as I was just about to update.

WINDB Output for the memory dump:

DEFAULT_BUCKET_ID:  WIN8_DRIVER_FAULT

BUGCHECK_STR:  0x139

PROCESS_NAME:  vmware-vmx.exe

CURRENT_IRQL:  2

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.

[…]

STACK_TEXT: 

ffff9484`206fee98 fffff806`57888da9 : 00000000`00000139 00000000`0000003b ffff9484`206ff1c0 ffff9484`206ff118 : nt!KeBugCheckEx

ffff9484`206feea0 fffff806`578891d0 : 00000000`00000000 fffff90a`0434c010 fffff90a`00602080 fffff806`57a0b039 : nt!KiBugCheckDispatch+0x69

ffff9484`206fefe0 fffff806`5788755f : 00000000`00880086 00000000`0084348e 00000000`0020001e 00000000`00843516 : nt!KiFastFailDispatch+0xd0

ffff9484`206ff1c0 fffff806`5787d5a4 : fffff7d4`0000b000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiRaiseSecurityCheckFailure+0x31f

ffff9484`206ff358 fffff806`562510be : fffff806`56257adb 00000000`00000f0e 00000000`00000006 00000000`00000000 : nt!KiDpcInterrupt+0x304

ffff9484`206ff4f8 fffff806`56257adb : 00000000`00000f0e 00000000`00000006 00000000`00000000 00000000`00000348 : vmx86+0x10be

ffff9484`206ff500 fffff806`56259cbe : 00000000`00000000 00000000`00000000 ffff8380`70742000 00000000`00000000 : vmx86+0x7adb

ffff9484`206ff630 fffff806`56251dcc : 00000000`00000000 00000000`00000000 ffff9484`206ff860 ffff9484`206ffa80 : vmx86+0x9cbe

ffff9484`206ff6d0 fffff806`562526ee : ffff988b`16ceee00 00000000`00000000 00000000`00000000 fffff806`576d99f4 : vmx86+0x1dcc

ffff9484`206ff780 fffff806`57cd1199 : 00000000`00000000 00000000`00000000 00000000`00000000 ffff988b`2708ece0 : vmx86+0x26ee

ffff9484`206ff7e0 fffff806`57cd0d86 : 00000000`00000f0e 00000000`00000000 00000000`00000000 00000000`00000000 : nt!IopXxxControlFile+0x3f9

ffff9484`206ff920 fffff806`578887d5 : 00000000`746c6644 ffff9484`206ffa08 00000000`00000000 00000000`00000000 : nt!NtDeviceIoControlFile+0x56

ffff9484`206ff990 00007ffd`e1119ed4 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceCopyEnd+0x25

00000000`0840f868 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x00007ffd`e1119ed4

[…]

FAILURE_BUCKET_ID: 0x139_MISSING_GSFRAME_vmx86!unknown_function

BUCKET_ID: 0x139_MISSING_GSFRAME_vmx86!unknown_function

PRIMARY_PROBLEM_CLASS:  0x139_MISSING_GSFRAME_vmx86!unknown_function

System data:

  • VMWare Workstation 12.5.9 build-7535481
  • Windows 10 1809 (Build 18290.1000)
DrJens
Contributor
Contributor
Jump to solution

Same problem. Haven't had any luck to figure out a workaround.

EDIT: Same problem with Win 10 build 18298

Reply
0 Kudos
SimArchitect
Contributor
Contributor
Jump to solution

20181211_044306.jpg

Problem persists after updating to Build 18298  

Reply
0 Kudos
AdrianRutter71
Contributor
Contributor
Jump to solution

With build 18282 expiring on the 14th December, this will kill my laptop for VMWare Workstation Player, which I use 90% of the time, so I have a vanilla OS on my host !

moejohn
Contributor
Contributor
Jump to solution

I was having the same issue after upgrading to 18290 on my AMD ryzen system, but I have a Dell laptop older with AMD that does not have the same issue, I reverted back to 18282 and my vmware works so I slowed does the build updates and skipped ahead yesterday to build 18298 and the same thing happened, I have no idea what this might be