BSOD playing CSGO WHEA_UNCORRECTABLE_ERROR

Page 1 of 2 12 LastLast

  1. fus
    Posts : 23
    Windows 10
       #1

    BSOD playing CSGO WHEA_UNCORRECTABLE_ERROR


    I got this error while playing csgo and while I was using google chrome.

    thanks if anyone can help
    Last edited by fus; 02 Aug 2015 at 17:53.
      My Computer


  2. Posts : 1,625
    W7 Pro x64 | W10 IP x64 | Linux Mint VM
       #2

    A 0x124 usually denotes a failing piece of hardware but, as is normally the case the dump offeres no clue as to what. Before we dive into hardware stress and diagnostic tests can you uninstall Chrome please and use an alternative such as Edge, IE or Firefox for example. Uninstalling Chrome has cured BSODs recently so it's worth ruling that out first.

    Code:
    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: ffffe000240d5028, Address of the WHEA_ERROR_RECORD structure.
    Arg3: 00000000b0800000, High order 32-bits of the MCi_STATUS value.
    Arg4: 0000000000040151, Low order 32-bits of the MCi_STATUS value.
    
    Debugging Details:
    ------------------
    
    
    BUGCHECK_STR:  0x124_AuthenticAMD
    
    CUSTOMER_CRASH_COUNT:  1
    
    DEFAULT_BUCKET_ID:  WIN8_DRIVER_FAULT
    
    PROCESS_NAME:  chrome.exe
    
    CURRENT_IRQL:  f
    
    ANALYSIS_VERSION: 6.3.9600.17336 (debuggers(dbg).150226-1500) amd64fre
    
    STACK_TEXT:  
    ffffd001`3cd59728 fffff803`73a5394f : 00000000`00000124 00000000`00000000 ffffe000`240d5028 00000000`b0800000 : nt!KeBugCheckEx
    ffffd001`3cd59730 fffff803`73ce226c : ffffe000`240d5028 ffffe000`23294580 ffffe000`23294580 ffffe000`23294580 : hal!HalBugCheckSystem+0xcf
    ffffd001`3cd59770 fffff803`73a53e3c : 00000000`00000728 00000000`00000004 ffffd001`3cd59b30 00000000`00000000 : nt!WheaReportHwError+0x258
    ffffd001`3cd597d0 fffff803`73a5419c : ffffe000`00000010 ffffe000`23294580 ffffd001`3cd59978 ffffe000`23294580 : hal!HalpMcaReportError+0x50
    ffffd001`3cd59920 fffff803`73a54088 : ffffe000`23293e10 00000000`00000001 00000000`00000004 00000000`00000000 : hal!HalpMceHandlerCore+0xe8
    ffffd001`3cd59970 fffff803`73a54459 : ffffe000`23293e10 ffffd001`3cd59bb0 00000000`00000000 00000000`00000000 : hal!HalpMceHandler+0xe4
    ffffd001`3cd599b0 fffff803`73be5b7b : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : hal!HalHandleMcheck+0x49
    ffffd001`3cd599e0 fffff803`73be5931 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KxMcheckAbort+0x7b
    ffffd001`3cd59b20 00000000`516c47e6 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiMcheckAbort+0x171
    00000000`02e2f9ec 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x516c47e6
    
    
    STACK_COMMAND:  kb
    
    FOLLOWUP_NAME:  MachineOwner
    
    MODULE_NAME: AuthenticAMD
    
    IMAGE_NAME:  AuthenticAMD
    
    DEBUG_FLR_IMAGE_TIMESTAMP:  0
    
    IMAGE_VERSION:  
    
    FAILURE_BUCKET_ID:  0x124_AuthenticAMD_PROCESSOR_CACHE
    
    BUCKET_ID:  0x124_AuthenticAMD_PROCESSOR_CACHE
    
    ANALYSIS_SOURCE:  KM
    
    FAILURE_ID_HASH_STRING:  km:0x124_authenticamd_processor_cache
    
    FAILURE_ID_HASH:  {b533751b-676e-7546-bcdc-24e6c40d0064}
    
    Followup: MachineOwner
    ---------
    
    4: kd> !errrec ffffe000240d5028
    ===============================================================================
    Common Platform Error Record @ ffffe000240d5028
    -------------------------------------------------------------------------------
    Record Id     : 01d0ccee1d216130
    Severity      : Fatal (1)
    Length        : 928
    Creator       : Microsoft
    Notify Type   : Machine Check Exception
    Timestamp     : 8/2/2015 20:11:31 (UTC)
    Flags         : 0x00000000
    
    ===============================================================================
    Section 0     : Processor Generic
    -------------------------------------------------------------------------------
    Descriptor    @ ffffe000240d50a8
    Section       @ ffffe000240d5180
    Offset        : 344
    Length        : 192
    Flags         : 0x00000001 Primary
    Severity      : Fatal
    
    Proc. Type    : x86/x64
    Instr. Set    : x64
    Error Type    : Cache error
    Operation     : Instruction Execute
    Flags         : 0x00
    Level         : 1
    CPU Version   : 0x0000000000600f20
    Processor ID  : 0x0000000000000004
    
    ===============================================================================
    Section 1     : x86/x64 Processor Specific
    -------------------------------------------------------------------------------
    Descriptor    @ ffffe000240d50f0
    Section       @ ffffe000240d5240
    Offset        : 536
    Length        : 128
    Flags         : 0x00000000
    Severity      : Fatal
    
    Local APIC Id : 0x0000000000000004
    CPU Id        : 20 0f 60 00 00 08 08 04 - 0b 32 98 3e ff fb 8b 17
                    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  @ ffffe000240d5240
    
    ===============================================================================
    Section 2     : x86/x64 MCA
    -------------------------------------------------------------------------------
    Descriptor    @ ffffe000240d5138
    Section       @ ffffe000240d52c0
    Offset        : 664
    Length        : 264
    Flags         : 0x00000000
    Severity      : Fatal
    
    Error         : ICACHEL1_IRD_ERR (Proc 4 Bank 1)
      Status      : 0xb080000000040151
      My Computer


  3. fus
    Posts : 23
    Windows 10
    Thread Starter
       #3

    Boozad said:
    A 0x124 usually denotes a failing piece of hardware but, as is normally the case the dump offeres no clue as to what. Before we dive into hardware stress and diagnostic tests can you uninstall Chrome please and use an alternative such as Edge, IE or Firefox for example. Uninstalling Chrome has cured BSODs recently so it's worth ruling that out first.

    Code:
    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: ffffe000240d5028, Address of the WHEA_ERROR_RECORD structure.
    Arg3: 00000000b0800000, High order 32-bits of the MCi_STATUS value.
    Arg4: 0000000000040151, Low order 32-bits of the MCi_STATUS value.
    
    Debugging Details:
    ------------------
    
    
    BUGCHECK_STR:  0x124_AuthenticAMD
    
    CUSTOMER_CRASH_COUNT:  1
    
    DEFAULT_BUCKET_ID:  WIN8_DRIVER_FAULT
    
    PROCESS_NAME:  chrome.exe
    
    CURRENT_IRQL:  f
    
    ANALYSIS_VERSION: 6.3.9600.17336 (debuggers(dbg).150226-1500) amd64fre
    
    STACK_TEXT:  
    ffffd001`3cd59728 fffff803`73a5394f : 00000000`00000124 00000000`00000000 ffffe000`240d5028 00000000`b0800000 : nt!KeBugCheckEx
    ffffd001`3cd59730 fffff803`73ce226c : ffffe000`240d5028 ffffe000`23294580 ffffe000`23294580 ffffe000`23294580 : hal!HalBugCheckSystem+0xcf
    ffffd001`3cd59770 fffff803`73a53e3c : 00000000`00000728 00000000`00000004 ffffd001`3cd59b30 00000000`00000000 : nt!WheaReportHwError+0x258
    ffffd001`3cd597d0 fffff803`73a5419c : ffffe000`00000010 ffffe000`23294580 ffffd001`3cd59978 ffffe000`23294580 : hal!HalpMcaReportError+0x50
    ffffd001`3cd59920 fffff803`73a54088 : ffffe000`23293e10 00000000`00000001 00000000`00000004 00000000`00000000 : hal!HalpMceHandlerCore+0xe8
    ffffd001`3cd59970 fffff803`73a54459 : ffffe000`23293e10 ffffd001`3cd59bb0 00000000`00000000 00000000`00000000 : hal!HalpMceHandler+0xe4
    ffffd001`3cd599b0 fffff803`73be5b7b : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : hal!HalHandleMcheck+0x49
    ffffd001`3cd599e0 fffff803`73be5931 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KxMcheckAbort+0x7b
    ffffd001`3cd59b20 00000000`516c47e6 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiMcheckAbort+0x171
    00000000`02e2f9ec 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x516c47e6
    
    
    STACK_COMMAND:  kb
    
    FOLLOWUP_NAME:  MachineOwner
    
    MODULE_NAME: AuthenticAMD
    
    IMAGE_NAME:  AuthenticAMD
    
    DEBUG_FLR_IMAGE_TIMESTAMP:  0
    
    IMAGE_VERSION:  
    
    FAILURE_BUCKET_ID:  0x124_AuthenticAMD_PROCESSOR_CACHE
    
    BUCKET_ID:  0x124_AuthenticAMD_PROCESSOR_CACHE
    
    ANALYSIS_SOURCE:  KM
    
    FAILURE_ID_HASH_STRING:  km:0x124_authenticamd_processor_cache
    
    FAILURE_ID_HASH:  {b533751b-676e-7546-bcdc-24e6c40d0064}
    
    Followup: MachineOwner
    ---------
    
    4: kd> !errrec ffffe000240d5028
    ===============================================================================
    Common Platform Error Record @ ffffe000240d5028
    -------------------------------------------------------------------------------
    Record Id     : 01d0ccee1d216130
    Severity      : Fatal (1)
    Length        : 928
    Creator       : Microsoft
    Notify Type   : Machine Check Exception
    Timestamp     : 8/2/2015 20:11:31 (UTC)
    Flags         : 0x00000000
    
    ===============================================================================
    Section 0     : Processor Generic
    -------------------------------------------------------------------------------
    Descriptor    @ ffffe000240d50a8
    Section       @ ffffe000240d5180
    Offset        : 344
    Length        : 192
    Flags         : 0x00000001 Primary
    Severity      : Fatal
    
    Proc. Type    : x86/x64
    Instr. Set    : x64
    Error Type    : Cache error
    Operation     : Instruction Execute
    Flags         : 0x00
    Level         : 1
    CPU Version   : 0x0000000000600f20
    Processor ID  : 0x0000000000000004
    
    ===============================================================================
    Section 1     : x86/x64 Processor Specific
    -------------------------------------------------------------------------------
    Descriptor    @ ffffe000240d50f0
    Section       @ ffffe000240d5240
    Offset        : 536
    Length        : 128
    Flags         : 0x00000000
    Severity      : Fatal
    
    Local APIC Id : 0x0000000000000004
    CPU Id        : 20 0f 60 00 00 08 08 04 - 0b 32 98 3e ff fb 8b 17
                    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  @ ffffe000240d5240
    
    ===============================================================================
    Section 2     : x86/x64 MCA
    -------------------------------------------------------------------------------
    Descriptor    @ ffffe000240d5138
    Section       @ ffffe000240d52c0
    Offset        : 664
    Length        : 264
    Flags         : 0x00000000
    Severity      : Fatal
    
    Error         : ICACHEL1_IRD_ERR (Proc 4 Bank 1)
      Status      : 0xb080000000040151
    Thanks a lot I've switch my browser to Firefox
      My Computer


  4. Posts : 1,625
    W7 Pro x64 | W10 IP x64 | Linux Mint VM
       #4

    Did it solve the issue?
      My Computer


  5. fus
    Posts : 23
    Windows 10
    Thread Starter
       #5

    Boozad said:
    Did it solve the issue?
    I think so I haven't gotten a BSOD
      My Computer


  6. Posts : 1,625
    W7 Pro x64 | W10 IP x64 | Linux Mint VM
       #6

    Good to hear.
      My Computer


  7. fus
    Posts : 23
    Windows 10
    Thread Starter
       #7

    Boozad said:
    Good to hear.
    Sorry I got another BSOD but a different error message It's called SYSTEM_SERVICE_EXCEPTION Attachment 28460

    I was on skype with a friend with firefox open
      My Computer


  8. Posts : 1,625
    W7 Pro x64 | W10 IP x64 | Linux Mint VM
       #8

    I'll take a look as soon as I can, it may be a while before I'm back at my PC.
      My Computer


  9. fus
    Posts : 23
    Windows 10
    Thread Starter
       #9

    Boozad said:
    I'll take a look as soon as I can, it may be a while before I'm back at my PC.
    Thanks
      My Computer


  10. Posts : 1,625
    W7 Pro x64 | W10 IP x64 | Linux Mint VM
       #10

    This one's blaming the nVidia driver. Can you let me know which driver you have installed? Given the previous 0x124 I'm starting to wonder about the card itself.

    Code:
    ffffd000`239c8048  fffff800`4b3404dfUnable to load image \SystemRoot\system32\DRIVERS\nvlddmkm.sys, Win32 error 0n2
    *** WARNING: Unable to verify timestamp for nvlddmkm.sys
    *** ERROR: Module load completed but symbols could not be loaded for nvlddmkm.sys
     nvlddmkm+0xf04df
    
    7: kd> lmvm nvlddmkm
    start             end                 module name
    fffff800`4b250000 fffff800`4bd38000   nvlddmkm T (no symbols)           
        Loaded symbol image file: nvlddmkm.sys
        Image path: \SystemRoot\system32\DRIVERS\nvlddmkm.sys
        Image name: nvlddmkm.sys
        Timestamp:        Thu Jul 23 01:15:19 2015 (55B03217)
        CheckSum:         00AAF49B
        ImageSize:        00AE8000
        Translations:     0000.04b0 0000.04e4 0409.04b0 0409.04e4
      My Computer


 

  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 22:45.
Find Us




Windows 10 Forums