BSOD while running vmware workstation


  1. Posts : 17
    Windows 7 Ultimate x64
       #1

    BSOD while running vmware workstation


    I hope you guys can help me with this issue, already ran memory test 7 passes in each memory no errors.
      My Computer


  2. Posts : 15,026
    Windows 10 Home 64Bit
       #2

    A "stop 0x124" is fundamentally different to many other types of bluescreens because it stems from a hardware complaint. Stop 0x124 minidumps contain very little practical information, and it is therefore necessary to approach the problem as a case of hardware in an unknown state of distress. You can read more on this error and what to try here... Stop 0x124 - what it means and what to try: Stop 124 - What it means and what to try

    Code:
    Microsoft (R) Windows Debugger Version 6.2.9200.20512 X86
    Copyright (c) Microsoft Corporation. All rights reserved.
    
    
    Loading Dump File [C:\Users\admin\Downloads\RJ03-Mon_07_07_2014_124023_50\070714-6630-01.dmp]
    Mini Kernel Dump File: Only registers and stack trace are available
    
    Symbol search path is: SRV*c:\symbols*http://msdl.microsoft.com/download/symbols
    Executable search path is: 
    Windows 7 Kernel Version 7601 (Service Pack 1) MP (8 procs) Free x64
    Product: WinNt, suite: TerminalServer SingleUserTS
    Built by: 7601.17514.amd64fre.win7sp1_rtm.101119-1850
    Machine Name:
    Kernel base = 0xfffff800`02a58000 PsLoadedModuleList = 0xfffff800`02c9de90
    Debug session time: Mon Jul  7 21:38:00.292 2014 (UTC + 6:00)
    System Uptime: 0 days 0:00:04.120
    Loading Kernel Symbols
    .................................................
    Loading User Symbols
    Mini Kernel Dump does not contain unloaded driver list
    *******************************************************************************
    *                                                                             *
    *                        Bugcheck Analysis                                    *
    *                                                                             *
    *******************************************************************************
    
    Use !analyze -v to get detailed debugging information.
    
    BugCheck 124, {0, fffffa801ce30038, 0, 0}
    
    Probably caused by : GenuineIntel
    
    Followup: MachineOwner
    ---------
    
    5: kd> !analyze -v
    *******************************************************************************
    *                                                                             *
    *                        Bugcheck Analysis                                    *
    *                                                                             *
    *******************************************************************************
    
    WHEA_UNCORRECTABLE_ERROR (124)
    A fatal hardware error has occurred. Parameter 1 identifies the type of error
    source that reported the error. Parameter 2 holds the address of the
    WHEA_ERROR_RECORD structure that describes the error conditon.
    Arguments:
    Arg1: 0000000000000000, Machine Check Exception
    Arg2: fffffa801ce30038, Address of the WHEA_ERROR_RECORD structure.
    Arg3: 0000000000000000, High order 32-bits of the MCi_STATUS value.
    Arg4: 0000000000000000, Low order 32-bits of the MCi_STATUS value.
    
    Debugging Details:
    ------------------
    
    
    BUGCHECK_STR:  0x124_GenuineIntel
    
    CUSTOMER_CRASH_COUNT:  1
    
    DEFAULT_BUCKET_ID:  WIN7_DRIVER_FAULT
    
    PROCESS_NAME:  System
    
    CURRENT_IRQL:  0
    
    STACK_TEXT:  
    fffff880`037705b0 fffff800`02d1bd29 : fffffa80`1ce30010 fffffa80`18860b60 00000000`00000007 00000000`00000000 : nt!WheapCreateLiveTriageDump+0x6c
    fffff880`03770ad0 fffff800`02bfb217 : fffffa80`1ce30010 fffff800`02c75658 fffffa80`18860b60 00000000`00000000 : nt!WheapCreateTriageDumpFromPreviousSession+0x49
    fffff880`03770b00 fffff800`02b62865 : fffff800`02cd73a0 00000000`00000001 fffffa80`1983fdf0 fffffa80`18860b60 : nt!WheapProcessWorkQueueItem+0x57
    fffff880`03770b40 fffff800`02ae2a21 : fffff880`01230e00 fffff800`02b62840 fffffa80`18860b00 00000000`00000000 : nt!WheapWorkQueueWorkerRoutine+0x25
    fffff880`03770b70 fffff800`02d75cce : 00000000`00000000 fffffa80`18860b60 00000000`00000080 fffffa80`18835040 : nt!ExpWorkerThread+0x111
    fffff880`03770c00 fffff800`02ac9fe6 : fffff880`03574180 fffffa80`18860b60 fffff880`0357f0c0 00000000`00000000 : nt!PspSystemThreadStartup+0x5a
    fffff880`03770c40 00000000`00000000 : fffff880`03771000 fffff880`0376b000 fffff880`0390f400 00000000`00000000 : nt!KiStartSystemThread+0x16
    
    
    STACK_COMMAND:  kb
    
    FOLLOWUP_NAME:  MachineOwner
    
    MODULE_NAME: GenuineIntel
    
    IMAGE_NAME:  GenuineIntel
    
    DEBUG_FLR_IMAGE_TIMESTAMP:  0
    
    FAILURE_BUCKET_ID:  X64_0x124_GenuineIntel_PROCESSOR_MAE_PRV
    
    BUCKET_ID:  X64_0x124_GenuineIntel_PROCESSOR_MAE_PRV
    
    Followup: MachineOwner
    ---------
    Code:
    5: kd> !cpuinfo
    CP  F/M/S Manufacturer  MHz PRCB Signature    MSR 8B Signature Features
     5  6,60,3 GenuineIntel 3497 0000001200000000                   21193ffe
    5: kd> !sysinfo cpuspeed
    sysinfo: could not find necessary interfaces.
    sysinfo: note that mssmbios.sys must be loaded (XPSP2+).
      My Computer


 

  Related Discussions
Our Sites
Site Links
About Us
Windows 7 Forums is an independent web site and has not been authorized, sponsored, or otherwise approved by Microsoft Corporation. "Windows 7" and related materials are trademarks of Microsoft Corp.

© Designer Media Ltd
All times are GMT -5. The time now is 07:05.
Find Us