none
BSOD: WHEA_UNCORRECTABLE_ERROR (124)

    Question

  • Hi,

    A few weeks ago my company purchased some Samsung laptop NP900X3C-A05UK models.

    I built an image with Windows 7 64bit Enterprise edition for this model and have already rolled out 15 laptops. 2 machines that I rolled out experienced the BSOD with the dump details below. This BSOD only happened once on each machine and I can't recreate it. Tried googling this BSOD, but can't find any useful info. The drivers on the laptop are up to date and so is the BIOS. These are brand new laptops and are not overclocked.

    Can anyone get any more sense of the crash dump below?

    Use !analyze -v to get detailed debugging information.

    BugCheck 124, {0, fffffa8006bf9028, b2000000, 100402}

    *** ERROR: Module load completed but symbols could not be loaded for intelppm.sys
    Probably caused by : GenuineIntel

    Followup: MachineOwner
    ---------

    0: 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: fffffa8006bf9028, Address of the WHEA_ERROR_RECORD structure.
    Arg3: 00000000b2000000, High order 32-bits of the MCi_STATUS value.
    Arg4: 0000000000100402, Low order 32-bits of the MCi_STATUS value.

    Debugging Details:
    ------------------


    BUGCHECK_STR:  0x124_GenuineIntel

    DEFAULT_BUCKET_ID:  WIN7_DRIVER_FAULT

    PROCESS_NAME:  System

    CURRENT_IRQL:  f

    STACK_TEXT: 
    fffff800`04953a98 fffff800`03411a3b : 00000000`00000124 00000000`00000000 fffffa80`06bf9028 00000000`b2000000 : nt!KeBugCheckEx
    fffff800`04953aa0 fffff800`02fa4633 : 00000000`00000001 fffffa80`06895870 00000000`00000000 fffffa80`068958c0 : hal!HalBugCheckSystem+0x1e3
    fffff800`04953ae0 fffff800`03411700 : 00000000`00000728 fffffa80`06895870 fffff800`04953e70 fffff800`04953e00 : nt!WheaReportHwError+0x263
    fffff800`04953b40 fffff800`03411052 : fffffa80`06895870 fffff800`04953e70 fffffa80`06895870 00000000`00000000 : hal!HalpMcaReportError+0x4c
    fffff800`04953c90 fffff800`03410f0d : 00000000`00000004 00000000`00000001 fffff800`04953ef0 00000000`00000000 : hal!HalpMceHandler+0x9e
    fffff800`04953cd0 fffff800`03404e88 : 00000000`00000002 fffff800`03009e80 00000000`00000000 00000000`00000000 : hal!HalpMceHandlerWithRendezvous+0x55
    fffff800`04953d00 fffff800`02e8c52c : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : hal!HalHandleMcheck+0x40
    fffff800`04953d30 fffff800`02e8c393 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KxMcheckAbort+0x6c
    fffff800`04953e70 fffff880`04a11c61 : fffff800`02e967f9 00000000`0023aed3 fffffa80`038b3788 fffff800`03009e80 : nt!KiMcheckAbort+0x153
    fffff800`04947b58 fffff800`02e967f9 : 00000000`0023aed3 fffffa80`038b3788 fffff800`03009e80 00000000`00000000 : intelppm+0x2c61
    fffff800`04947b60 fffff800`02e8591c : fffff800`03009e80 fffff800`00000002 00000000`00000002 fffff880`00000000 : nt!PoIdle+0x52a
    fffff800`04947c40 00000000`00000000 : fffff800`04948000 fffff800`04942000 fffff800`04947c00 00000000`00000000 : nt!KiIdleLoop+0x2c


    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

    BUCKET_ID:  X64_0x124_GenuineIntel_PROCESSOR_MAE

    Followup: MachineOwner
    ---------

    0: kd> !errrec
    0: kd> !errrec fffffa8006bf9028
    ===============================================================================
    Common Platform Error Record @ fffffa8006bf9028
    -------------------------------------------------------------------------------
    Record Id     : 01ce614267c2b345
    Severity      : Fatal (1)
    Length        : 928
    Creator       : Microsoft
    Notify Type   : Machine Check Exception
    Timestamp     : 6/5/2013 15:34:20 (UTC)
    Flags         : 0x00000000

    ===============================================================================
    Section 0     : Processor Generic
    -------------------------------------------------------------------------------
    Descriptor    @ fffffa8006bf90a8
    Section       @ fffffa8006bf9180
    Offset        : 344
    Length        : 192
    Flags         : 0x00000001 Primary
    Severity      : Fatal

    Proc. Type    : x86/x64
    Instr. Set    : x64
    Error Type    : Micro-Architectural Error
    Flags         : 0x00
    CPU Version   : 0x00000000000306a9
    Processor ID  : 0x0000000000000000

    ===============================================================================
    Section 1     : x86/x64 Processor Specific
    -------------------------------------------------------------------------------
    Descriptor    @ fffffa8006bf90f0
    Section       @ fffffa8006bf9240
    Offset        : 536
    Length        : 128
    Flags         : 0x00000000
    Severity      : Fatal

    Local APIC Id : 0x0000000000000000
    CPU Id        : a9 06 03 00 00 08 10 00 - bf e3 ba 7d ff fb eb bf
                    00 00 00 00 00 00 00 00 - 00 00 00 00 00 00 00 00
                    00 00 00 00 00 00 00 00 - 00 00 00 00 00 00 00 00

    Proc. Info 0  @ fffffa8006bf9240

    ===============================================================================
    Section 2     : x86/x64 MCA
    -------------------------------------------------------------------------------
    Descriptor    @ fffffa8006bf9138
    Section       @ fffffa8006bf92c0
    Offset        : 664
    Length        : 264
    Flags         : 0x00000000
    Severity      : Fatal

    Error         : Internal unclassified (Proc 0 Bank 4)
      Status      : 0xb200000000100402


    • Edited by SSorga Thursday, June 06, 2013 11:38 AM
    Thursday, June 06, 2013 9:27 AM

Answers

All replies

    1. The file in the dump is Microsoft's Intel processor driver. (intelppm.sys)
    2. In these images you state you have the latest drivers and the latest bios. Do you have the latest Windows updates within the image as well?
    3. If not, you should include those updates in your images.
    4. One possible solution is a registry fix. http://blogs.msdn.com/b/virtual_pc_guy/archive/2005/10/24/484461.aspx

    If you are seeing this problem repeatedly you can manually disable these drivers (with no negative side effect) by going to the following location in the registry:

    HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\Processor

    Or

    HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\Intelppm

    And changing the 'Start' value to '4'.

    Let me know if that works


    The Motley Tech - A Tech Tutorial/Commentary Blog http://themotleytech.wordpress.com

    Thursday, June 06, 2013 1:24 PM
  • Hi,

    Thanks for the reply. The windows updates we get are from a WSUS server which approves only critical and security updates. Should I be installing other windows updates also? The only other driver update I can see when checking online for Windows updates is Intel Management Engine driver.

    The registry fix you mention is for virtual machines, also it only applies to Centrino processors, but our machines use Core-i7 processors.


    • Edited by SSorga Thursday, June 06, 2013 1:32 PM
    Thursday, June 06, 2013 1:29 PM
  • Try installing the Intel Management Driver and see if that changes anything.

    The Motley Tech - A Tech Tutorial/Commentary Blog http://themotleytech.wordpress.com

    Thursday, June 06, 2013 1:35 PM
  • Will do, thanks.
    Thursday, June 06, 2013 1:37 PM