VMware Workstation 14 causing Blue Screens on W10

Hello Experts :)
 
I'm using an AMD 1700X PC which works fine....  but as son as I install VMware Workstation Pro, I get regular BSODs.  When I uninstall, they stop.

It can happen even when I'm not using Workstation Pro, but regularly occurs when booting up, only ever once, then working for a while before a random BSOD when I least want it to :)   It also doesn't seem to handle VM's rebooting very well and this can trigger it also.
 
I have VMware Workstation Pro 14.1.1 build-7258167 (latest) on Windows 10, 64-bit 10.0.16299 which claims to be up to date.  I've gone to the manufacturer's sites to check the latest drivers, used a driver update tool which confirms this and I've ran mem tests, and had a go at looking at some dump files, but I'll admit, I'm no SME here!  They mainly complained about IRQL errors and memory corruption, but the Workstation Pro smoking gun can't be ignored.

So, I rebuilt windows to make sure I'd not corrupted something along the way and sure enough it was back to BSODs 2 or 3 times a day.

After a bit of googling I ended up using the Microsoft Verifier tool and Windows wouldn't even boot up..  The dump file from that seems to point to vstor2-mntapi20-shared.sys, but googling further hasn't got me anywhere.
 
Here's the mini dump from that and you're welcome to ones without verifier running too.

Can anyone help me get around this?
 
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck C4, {2000, fffff8010c5812bc, 0, 32545356}
*** WARNING: Unable to verify timestamp for vstor2-mntapi20-shared.sys
*** ERROR: Module load completed but symbols could not be loaded for vstor2-mntapi20-shared.sys
Probably caused by : vstor2-mntapi20-shared.sys ( vstor2_mntapi20_shared+12bc )
Followup:     MachineOwner
---------
0: kd> !analyze -v
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************
DRIVER_VERIFIER_DETECTED_VIOLATION (c4)
A device driver attempting to corrupt the system has been caught.  This is
because the driver was specified in the registry as being suspect (by the
administrator) and the kernel has enabled substantial checking of this driver.
If the driver attempts to corrupt the system, bugchecks 0xC4, 0xC1 and 0xA will
be among the most commonly seen crashes.
Arguments:
Arg1: 0000000000002000, Code Integrity Issue: The caller specified an executable pool type. (Expected: NonPagedPoolNx)
Arg2: fffff8010c5812bc, The address in the driver's code where the error was detected.
Arg3: 0000000000000000, Pool Type.
Arg4: 0000000032545356, Pool Tag (if provided).
Debugging Details:
------------------

DUMP_CLASS: 1
DUMP_QUALIFIER: 400
BUILD_VERSION_STRING:  10.0.16299.192 (WinBuild.160101.0800)
SYSTEM_MANUFACTURER:  System manufacturer
SYSTEM_PRODUCT_NAME:  System Product Name
SYSTEM_SKU:  SKU
SYSTEM_VERSION:  System Version
BIOS_VENDOR:  American Megatrends Inc.
BIOS_VERSION:  3401
BIOS_DATE:  12/04/2017
BASEBOARD_MANUFACTURER:  ASUSTeK COMPUTER INC.
BASEBOARD_PRODUCT:  PRIME B350-PLUS
BASEBOARD_VERSION:  Rev X.0x
DUMP_TYPE:  2
DUMP_FILE_ATTRIBUTES: 0x8
  Kernel Generated Triage Dump
BUGCHECK_P1: 2000
BUGCHECK_P2: fffff8010c5812bc
BUGCHECK_P3: 0
BUGCHECK_P4: 32545356
BUGCHECK_STR:  0xc4_2000
CPU_COUNT: 10
CPU_MHZ: d42
CPU_VENDOR:  AuthenticAMD
CPU_FAMILY: 17
CPU_MODEL: 1
CPU_STEPPING: 1
CUSTOMER_CRASH_COUNT:  1
DEFAULT_BUCKET_ID:  WIN8_DRIVER_FAULT
PROCESS_NAME:  System
CURRENT_IRQL:  0
ANALYSIS_SESSION_HOST:  AMD1700X
ANALYSIS_SESSION_TIME:  01-24-2018 20:40:16.0374
ANALYSIS_VERSION: 10.0.16299.15 amd64fre
LAST_CONTROL_TRANSFER:  from fffff8010d02f2d3 to fffff8010c9fa6e0
STACK_TEXT:  
fffff687`d48767d8 fffff801`0d02f2d3 : 00000000`000000c4 00000000`00002000 fffff801`0c5812bc 00000000`00000000 : nt!KeBugCheckEx
fffff687`d48767e0 fffff801`0caf910f : fffff801`0cbdba7c 00000000`00002000 fffff801`0c5812bc 00000000`00000000 : nt!VerifierBugCheckIfAppropriate+0xdf
fffff687`d4876820 fffff801`0d02740c : 00000000`32545356 fffff801`0cbdba7c fffff801`0c5812bc 00000000`00000000 : nt!VfReportIssueWithOptions+0x103
fffff687`d4876870 fffff801`0d0251c1 : 00000000`32545356 00000000`00000000 00000000`00000000 00000000`00001001 : nt!VfCheckPoolType+0x90
fffff687`d48768b0 fffff801`0c5812bc : 00000000`0000002e ffffc30d`12a29070 ffffffff`80001930 00000000`0000002e : nt!VerifierExAllocatePoolEx+0x21
fffff687`d4876900 00000000`0000002e : ffffc30d`12a29070 ffffffff`80001930 00000000`0000002e ffffc30d`12a26160 : vstor2_mntapi20_shared+0x12bc
fffff687`d4876908 ffffc30d`12a29070 : ffffffff`80001930 00000000`0000002e ffffc30d`12a26160 fffff687`d4876a70 : 0x2e
fffff687`d4876910 ffffffff`80001930 : 00000000`0000002e ffffc30d`12a26160 fffff687`d4876a70 00000000`00000000 : 0xffffc30d`12a29070
fffff687`d4876918 00000000`0000002e : ffffc30d`12a26160 fffff687`d4876a70 00000000`00000000 fffff801`0ca0e5e0 : 0xffffffff`80001930
fffff687`d4876920 ffffc30d`12a26160 : fffff687`d4876a70 00000000`00000000 fffff801`0ca0e5e0 00000000`00000000 : 0x2e
fffff687`d4876928 fffff687`d4876a70 : 00000000`00000000 fffff801`0ca0e5e0 00000000`00000000 00000000`00000000 : 0xffffc30d`12a26160
fffff687`d4876930 00000000`00000000 : fffff801`0ca0e5e0 00000000`00000000 00000000`00000000 00000000`0000002e : 0xfffff687`d4876a70

THREAD_SHA1_HASH_MOD_FUNC:  33f778527ba02c5eaf57132bc47d05644b07d4bb
THREAD_SHA1_HASH_MOD_FUNC_OFFSET:  0a1cb83a57a0c9339944ee80d98c604f02890fd0
THREAD_SHA1_HASH_MOD:  011cf14e782a04b4077aa08c74782e0c58ddcb02
FOLLOWUP_IP:
vstor2_mntapi20_shared+12bc
fffff801`0c5812bc 440fb705644e0000 movzx   r8d,word ptr [vstor2_mntapi20_shared+0x6128 (fffff801`0c586128)]
FAULT_INSTR_CODE:  5b70f44
SYMBOL_STACK_INDEX:  5
SYMBOL_NAME:  vstor2_mntapi20_shared+12bc
FOLLOWUP_NAME:  MachineOwner
MODULE_NAME: vstor2_mntapi20_shared
IMAGE_NAME:  vstor2-mntapi20-shared.sys
DEBUG_FLR_IMAGE_TIMESTAMP:  590c2a38
STACK_COMMAND:  .thread ; .cxr ; kb
BUCKET_ID_FUNC_OFFSET:  12bc
FAILURE_BUCKET_ID:  0xc4_2000_vstor2_mntapi20_shared!unknown_function
BUCKET_ID:  0xc4_2000_vstor2_mntapi20_shared!unknown_function
PRIMARY_PROBLEM_CLASS:  0xc4_2000_vstor2_mntapi20_shared!unknown_function
TARGET_TIME:  2018-01-24T18:49:46.000Z
OSBUILD:  16299
OSSERVICEPACK:  192
SERVICEPACK_NUMBER: 0
OS_REVISION: 0
SUITE_MASK:  272
PRODUCT_TYPE:  1
OSPLATFORM_TYPE:  x64
OSNAME:  Windows 10
OSEDITION:  Windows 10 WinNt TerminalServer SingleUserTS
OS_LOCALE:  
USER_LCID:  0
OSBUILD_TIMESTAMP:  2018-01-01 11:07:05
BUILDDATESTAMP_STR:  160101.0800
BUILDLAB_STR:  WinBuild
BUILDOSVER_STR:  10.0.16299.192
ANALYSIS_SESSION_ELAPSED_TIME:  770
ANALYSIS_SOURCE:  KM
FAILURE_ID_HASH_STRING:  km:0xc4_2000_vstor2_mntapi20_shared!unknown_function
FAILURE_ID_HASH:  {c7515f44-1811-26dc-3653-401fab8093dc}
Followup:     MachineOwner
---------
Barry BeaverAsked:
Who is Participating?
 
Barry BeaverAuthor Commented:
Hi guys,

Thought I'd close this one off in case anyone else comes across the same problem (and by the looks of things, anyone who installs the current WS14.1 release on a clean copy of W10 will!)

Someone on the VMware Communities got back to me, it seems vstor2-mntapi20-shared.sys  isn't compatible with Win10, but WS14.1 installs it and tries to use it anyway!

The file we actually need here is vstor2-x64.sys, and to get this, I had to:

uninstall VM Workstation
install VMware-converter-en-6.2.0-7348398.exe
re-install VM Workstation

VMWS14 still installs the wrong driver, but it's already associated the correct driver in the registry to the service.

Full transcript can be found here:

https://communities.vmware.com/message/2741361
0
 
JohnBusiness Consultant (Owner)Commented:
I have VMware Workstation V14.1.1.7528167 on my Windows 10 Pro 64-bit machine and several versions before that back to Version 12 and I do not see this issue.

1. Uninstall VMware Workstation
2. Update your BIOS, Chipset, Video and network drivers.  Then restart.
3. Now install VMware Workstation and test.
1
 
Seth SimmonsSr. Systems AdministratorCommented:
i would uninstall and reinstall
that file is the vmware virtual storage volume driver
if it still crashes after reinstalling, i would open a case with vmware since your hardware is supported by version 14
don't downgrade though since version 14 is the first to support your processor
1
Cloud Class® Course: MCSA MCSE Windows Server 2012

This course teaches how to install and configure Windows Server 2012 R2.  It is the first step on your path to becoming a Microsoft Certified Solutions Expert (MCSE).

 
Barry BeaverAuthor Commented:
Hi thanks for the replies, I've un-installed, updated BIOS and drivers a few times now, even tried from a clean OS-install once I was 100% sure I had the latest drivers, patches and firmware.    No luck...

I went to raise a call with VMware but Workstation Pro doesn't seem to have support (unless I give them £50).  I posted on their community forums too but didn't get anything there either.  Unless you have a link to a support section I've missed Seth?
0
 
Seth SimmonsSr. Systems AdministratorCommented:
no...i meant open a support case
isn't free but could save a lot of hassle since there shouldn't be any reason for it not to work out of the box - especially since you've already done your due diligence with firmware/driver updates
0
 
JohnBusiness Consultant (Owner)Commented:
This page:

https://docs.vmware.com/en/VMware-Workstation-Pro/14/rn/workstation-14-release-notes.html

says AMD Ryzen is supported so yes, you need to contact VMware Support.
0
 
Barry BeaverAuthor Commented:
Resolved with a little help from the VMware Communities forum.
0
Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.

All Courses

From novice to tech pro — start learning today.