none
Windows 10 Pro crashes with BSOD MEMORY_MANAGEMENT on start of a virtual machine in VMware Workstation 8

    Question

  • Hi all,

    I have just upgraded my PC from Windows 8.1 Pro to Windows 10 Pro and I am facing an annoying problem: Starting a virtual machine in VMware Workstation 8 repeatedly crashes Windows 10 with a Bluescreen and keyword MEMORY_MANAGEMENT. Even after fresh installation of VMware Workstation 8.0.6. Any ideas about a fix without upgrading to VMware Workstation 11 or 12?

    Thanks in advance!

    Regards,
    Peter


    Thursday, August 27, 2015 7:12 PM

Answers

  • Hi Zimmp,

    First I noticed many similar issues on VMware forum, hope VMware has noticed this to publish some driver updates to compatible Windows 10 well.

    Also, some OPs find this can help to solve their issue, please check it also:

    Solved: Shutting down VMWare Workstation Virtual Machines on Windows 10 Tech Preview
    http://www.wictorwilen.se/solved-shutting-down-vmware-workstation-virtual-machines-on-windows-10-tech-preview

    Please Note: Since the website is not hosted by Microsoft, the link may change without notice. Microsoft does not guarantee the accuracy of this information.


    Please remember to mark the replies as answers if they help, and unmark the answers if they provide no help. If you have feedback for TechNet Support, contact tnmff@microsoft.com.

    Tuesday, September 01, 2015 1:18 PM
    Moderator

All replies

  • No to be honest. You mentioned VMware Workstation 11 or 12, VMware workstation 8 is 2013 so predates Windows 10. Not sure it you will get anymore joy posting this query on VMware forums but perhaps worth a try.
    Thursday, August 27, 2015 10:04 PM
  •  
    We do need the actual log files (called a DMP files) as they contain the only record of the sequence of events leading up to the crash, what drivers were loaded, and what was responsible.  


    Please follow our instructions for finding and uploading the files we need to help you fix your computer. They can be found here
    If you have any questions about the procedure please ask


    Wanikiya and Dyami--Team Zigzag

    Thursday, August 27, 2015 11:56 PM
    Moderator
  • Thank you Wanikiya and Dyami--Team Zigzag for your response.

    Pease find minidump file and system info at www.dropbox.com below /sh/t28r8dp6xpqfmh2/AAAuQ9PZirXFlQo7RsdlKDMJa?dl=0

    Regards,
    Peter
    Friday, August 28, 2015 8:20 PM
  • Peter

    This was Related to vmx86.sys kernel driver from VMware Inc.  Yours from 2013.  I would remove it and install the newest driver available.

    Microsoft (R) Windows Debugger Version 10.0.10240.9 AMD64
    Copyright (c) Microsoft Corporation. All rights reserved.
    
    
    Loading Dump File [C:\Users\zigza\Desktop\082815-7218-01.dmp]
    Mini Kernel Dump File: Only registers and stack trace are available
    
    
    ************* Symbol Path validation summary **************
    Response                         Time (ms)     Location
    Deferred                                       SRV*E:\Symbols*http://msdl.microsoft.com/download/symbols
    Symbol search path is: SRV*E:\Symbols*http://msdl.microsoft.com/download/symbols
    Executable search path is: 
    No .natvis files found at C:\Program Files (x86)\Windows Kits\10\Debuggers\x64\Visualizers.
    Windows 10 Kernel Version 10240 MP (8 procs) Free x64
    Product: WinNt, suite: TerminalServer SingleUserTS
    Built by: 10240.16463.amd64fre.th1.150819-1946
    Machine Name:
    Kernel base = 0xfffff801`ba805000 PsLoadedModuleList = 0xfffff801`bab2a030
    Debug session time: Fri Aug 28 15:33:42.763 2015 (UTC - 4:00)
    System Uptime: 0 days 0:00:57.462
    Loading Kernel Symbols
    ...............................................................
    ................................................................
    ................................................................
    ........
    Loading User Symbols
    *******************************************************************************
    *                                                                             *
    *                        Bugcheck Analysis                                    *
    *                                                                             *
    *******************************************************************************
    
    Use !analyze -v to get detailed debugging information.
    
    BugCheck 1A, {61948, fffffffff, 1, fffffffff}
    
    *** WARNING: Unable to verify timestamp for vmx86.sys
    *** ERROR: Module load completed but symbols could not be loaded for vmx86.sys
    Probably caused by : vmx86.sys ( vmx86+483e )
    
    Followup:     MachineOwner
    ---------
    
    1: kd> !analyze -v
    *******************************************************************************
    *                                                                             *
    *                        Bugcheck Analysis                                    *
    *                                                                             *
    *******************************************************************************
    
    MEMORY_MANAGEMENT (1a)
        # Any other values for parameter 1 must be individually examined.
    Arguments:
    Arg1: 0000000000061948, The subtype of the bugcheck.
    Arg2: 0000000fffffffff
    Arg3: 0000000000000001
    Arg4: 0000000fffffffff
    
    Debugging Details:
    ------------------
    
    
    SYSTEM_SKU:  To be filled by O.E.M.
    
    SYSTEM_VERSION:  To be filled by O.E.M.
    
    BIOS_DATE:  05/31/2012
    
    BASEBOARD_PRODUCT:  Z77X-UD5H
    
    BASEBOARD_VERSION:  x.x
    
    BUGCHECK_P1: 61948
    
    BUGCHECK_P2: fffffffff
    
    BUGCHECK_P3: 1
    
    BUGCHECK_P4: fffffffff
    
    BUGCHECK_STR:  0x1a_61948
    
    CPU_COUNT: 8
    
    CPU_MHZ: d4b
    
    CPU_VENDOR:  GenuineIntel
    
    CPU_FAMILY: 6
    
    CPU_MODEL: 3a
    
    CPU_STEPPING: 9
    
    CUSTOMER_CRASH_COUNT:  1
    
    DEFAULT_BUCKET_ID:  WIN8_DRIVER_FAULT
    
    PROCESS_NAME:  vmware-vmx.exe
    
    CURRENT_IRQL:  2
    
    ANALYSIS_VERSION: 10.0.10240.9 amd64fre
    
    LAST_CONTROL_TRANSFER:  from fffff801ba9b61c5 to fffff801ba953240
    
    STACK_TEXT:  
    ffffd001`fd24d308 fffff801`ba9b61c5 : 00000000`0000001a 00000000`00061948 0000000f`ffffffff 00000000`00000001 : nt!KeBugCheckEx
    ffffd001`fd24d310 fffff801`ba8f22dc : ffffd000`27bcafff 0000000f`ffffffff 00000000`00000001 00000000`00000000 : nt! ?? ::FNODOBFM::`string'+0x543c5
    ffffd001`fd24d3c0 fffff801`ba8f20ff : ffffe001`a810ff20 00000002`088a5863 fffff6fb`740009e8 ffffd000`27bcafff : nt!MiZeroAndFlushPtes+0x150
    ffffd001`fd24d5f0 fffff801`091b483e : 00000000`00000000 00000000`00000005 ffffe001`aa9bd6c0 ffffe001`aa9bd600 : nt!MmUnmapIoSpace+0x7b
    ffffd001`fd24d630 00000000`00000000 : 00000000`00000005 ffffe001`aa9bd6c0 ffffe001`aa9bd600 ffffffff`ffffd8f0 : vmx86+0x483e
    
    
    STACK_COMMAND:  kb
    
    FOLLOWUP_IP: 
    vmx86+483e
    fffff801`091b483e ??              ???
    
    SYMBOL_STACK_INDEX:  4
    
    SYMBOL_NAME:  vmx86+483e
    
    FOLLOWUP_NAME:  MachineOwner
    
    MODULE_NAME: vmx86
    
    IMAGE_NAME:  vmx86.sys
    
    DEBUG_FLR_IMAGE_TIMESTAMP:  51307c20
    
    BUCKET_ID_FUNC_OFFSET:  483e
    
    FAILURE_BUCKET_ID:  0x1a_61948_vmx86!Unknown_Function
    
    BUCKET_ID:  0x1a_61948_vmx86!Unknown_Function
    
    PRIMARY_PROBLEM_CLASS:  0x1a_61948_vmx86!Unknown_Function
    
    ANALYSIS_SOURCE:  KM
    
    FAILURE_ID_HASH_STRING:  km:0x1a_61948_vmx86!unknown_function
    
    FAILURE_ID_HASH:  {11840798-24d4-31cd-aa2b-86bb5102592e}
    
    Followup:     MachineOwner
    ---------
    
    1: kd> lmvm vmx86
    Browse full module list
    start             end                 module name
    fffff801`091b0000 fffff801`091c6000   vmx86    T (no symbols)           
        Loaded symbol image file: vmx86.sys
        Image path: \??\C:\WINDOWS\system32\drivers\vmx86.sys
        Image name: vmx86.sys
        Browse all global symbols  functions  data
        Timestamp:        Fri Mar 01 05:00:00 2013 (51307C20)
        CheckSum:         00011F12
        ImageSize:        00016000
        Translations:     0000.04b0 0000.04e4 0409.04b0 0409.04e4
    


    Wanikiya and Dyami--Team Zigzag

    Friday, August 28, 2015 9:45 PM
    Moderator
  • Hi all,

    thanks for the response. I have tried to isolate vmx86.sys from the VMware Workstation 12 Pro trial version and to replace the vmx86.sys installed with VMware Workstation 8, but the situation did not change: Bluescreen after the start of any virtual machine. VMware Workstation 12 Pro trial version is working. So, I will have to make a decision: Switch back to Windows 8.1 with VMware Workstation 8 or buy VMware Workstation 12 Pro (from version 8 to version 12 there seems to be no upgrade offer). Anyway, I am not amused.

    Regards,
    Peter

    Monday, August 31, 2015 6:32 PM
  • Hi Zimmp,

    First I noticed many similar issues on VMware forum, hope VMware has noticed this to publish some driver updates to compatible Windows 10 well.

    Also, some OPs find this can help to solve their issue, please check it also:

    Solved: Shutting down VMWare Workstation Virtual Machines on Windows 10 Tech Preview
    http://www.wictorwilen.se/solved-shutting-down-vmware-workstation-virtual-machines-on-windows-10-tech-preview

    Please Note: Since the website is not hosted by Microsoft, the link may change without notice. Microsoft does not guarantee the accuracy of this information.


    Please remember to mark the replies as answers if they help, and unmark the answers if they provide no help. If you have feedback for TechNet Support, contact tnmff@microsoft.com.

    Tuesday, September 01, 2015 1:18 PM
    Moderator
  • Having the same problem,

    I decided to keep one machine dedicated to Windows 7 so I could run 8.0 VMWare machines. I don't have the funds or means currently to justify 250 dollar upgrade.

    Microsoft is offering the free HyperV so I might use that instead of VMWare for now until the need arises again, depending on how much I'm "not amused" we might just post a migration solution to a different VM solution.

    Monday, November 02, 2015 6:28 PM