Multiple BDOS in the last few days, all different error messages.

Page 2 of 2 FirstFirst 12
  1. axe0's Avatar
    Posts : 14,787
    Windows 10 Pro
       #11

    I would recommend to update the BIOS to the newest version 3103.
    MAXIMUS VII HERO | Motherboards | ASUS Global


    The only thing the dump shows is that because of a delay in execution, as we can see below, a hardware error occured.
    Before the crash occurs, the system attempts to handle the error unsuccessfully whereafter the WHEA provides the report (shown in the second code) to the CPU which calls the bugcheck function.
    As I mentioned, a 0x124 doesn't reveal much. I don't know if it is possible to find the instructions of the function calling KeDelayExecutionThread to find out a little more, but I doubt it.
    Code:
    STACK_TEXT: 
    fffff800`d0f21a38 fffff800`cf811f1f : 00000000`00000124 00000000`00000000 ffffe001`63148028 00000000`be000000 : nt!KeBugCheckEx
    fffff800`d0f21a40 fffff800`cf2228bc : ffffe001`63148028 ffffe001`631b7c00 ffffe001`631b7c00 ffffe001`631b7c00 : hal!HalBugCheckSystem+0xcf
    fffff800`d0f21a80 fffff800`cf81240c : 00000000`00000728 00000000`00000000 fffff800`d0f21e70 00000000`00000000 : nt!WheaReportHwError+0x258
    fffff800`d0f21ae0 fffff800`cf812764 : ffffe001`00000010 ffffe001`631b7c00 fffff800`d0f21c88 ffffe001`631b7c00 : hal!HalpMcaReportError+0x50
    fffff800`d0f21c30 fffff800`cf81264e : ffffe001`622d7b40 00000000`00000001 00000000`00000000 00000000`00000000 : hal!HalpMceHandlerCore+0xe8
    fffff800`d0f21c80 fffff800`cf81288e : 00000000`00000008 00000000`00000001 00000000`00000000 00000000`00000000 : hal!HalpMceHandler+0xda
    fffff800`d0f21cc0 fffff800`cf812a10 : ffffe001`622d7b40 fffff800`d0f21ef0 00000000`00000000 00000000`00000000 : hal!HalpMceHandlerWithRendezvous+0xce
    fffff800`d0f21cf0 fffff800`cf15e47b : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : hal!HalHandleMcheck+0x40
    fffff800`d0f21d20 fffff800`cf15e231 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KxMcheckAbort+0x7b
    fffff800`d0f21e60 fffff800`cf0e4a45 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiMcheckAbort+0x171
    ffffd000`4023ca50 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KeDelayExecutionThread+0x45
    Code:
    0: kd> !errrec ffffe00163148028
    ===============================================================================
    Common Platform Error Record @ ffffe00163148028
    -------------------------------------------------------------------------------
    Record Id     : 01d1fc885ed87b7d
    Severity      : Fatal (1)
    Length        : 928
    Creator       : Microsoft
    Notify Type   : Machine Check Exception
    Timestamp     : 8/30/2016 1:59:22 (UTC)
    Flags         : 0x00000000
    
    ===============================================================================
    Section 0     : Processor Generic
    -------------------------------------------------------------------------------
    Descriptor    @ ffffe001631480a8
    Section       @ ffffe00163148180
    Offset        : 344
    Length        : 192
    Flags         : 0x00000001 Primary
    Severity      : Fatal
    
    Proc. Type    : x86/x64
    Instr. Set    : x64
    Error Type    : Cache error
    Operation     : Generic
    Flags         : 0x00
    Level         : 2
    CPU Version   : 0x00000000000306c3
    Processor ID  : 0x0000000000000000
    
    ===============================================================================
    Section 1     : x86/x64 Processor Specific
    -------------------------------------------------------------------------------
    Descriptor    @ ffffe001631480f0
    Section       @ ffffe00163148240
    Offset        : 536
    Length        : 128
    Flags         : 0x00000000
    Severity      : Fatal
    
    Local APIC Id : 0x0000000000000000
    CPU Id        : c3 06 03 00 00 08 10 00 - bf fb fa 7f 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  @ ffffe00163148240
    
    ===============================================================================
    Section 2     : x86/x64 MCA
    -------------------------------------------------------------------------------
    Descriptor    @ ffffe00163148138
    Section       @ ffffe001631482c0
    Offset        : 664
    Length        : 264
    Flags         : 0x00000000
    Severity      : Fatal
    
    Error         : GCACHEL2_ERR_ERR (Proc 0 Bank 8)
      Status      : 0xbe0000000100110a
      Address     : 0x00000002039f2840
      Misc.       : 0x000003100e024086
      My Computers


  2. Posts : 9
    10
    Thread Starter
       #12

    man the thread went to the 2nd page and i didnt spot that so i was just checking for 3 days straight even tho you alreayd posted xD.
      My Computer


  3. Posts : 9
    10
    Thread Starter
       #13

    do you have anything clue what would cause a delay in execution? could it be bad hardware?
      My Computer

  4. axe0's Avatar
    Posts : 14,787
    Windows 10 Pro
       #14

    A 0x124 means a hardware error occured, a hardware error could occur for various reasons, the cause is very difficult to tell with a single dump having not much data.

    Asking for an execution delay for a thread isn't the problem, that is a thing that is done often.
    For proper analysis I would think that the status of the delay would be need to known and if possible also some information about what called it, but I by far know enough of debugging to find that out.
      My Computers


  5. Posts : 9
    10
    Thread Starter
       #15

    seems the bios update fixed the BSOD, i cant believe one such simple thing was such a big issue. ive havent got a BSOD since.
    Also thxs so much for the help
      My Computer

  6. axe0's Avatar
    Posts : 14,787
    Windows 10 Pro
       #16

    Good to hear :)
      My Computers


 
Page 2 of 2 FirstFirst 12

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

Designer Media Ltd
All times are GMT -5. The time now is 11:58.
Find Us




Windows 10 Forums