none
WHEA_UNCORRECTABLE_ERROR (124) 藍屏問題 有DMP檔 RRS feed

  • 問題

  • 我使用WinDbg分析.dmp檔,發現這些關鍵字 Probably caused by : GenuineIntel、BUGCHECK_STR:  0x124_GenuineIntel

    、PROCESS_NAME:  League of Legends.exe,其中我重灌過,POWER、顯示卡也換新的,還有會有藍屏問題,還請幫忙解決謝謝。

    ----------------------------------------------------------------------------------------------

    Microsoft (R) Windows Debugger Version 10.0.14321.1024 AMD64
    Copyright (c) Microsoft Corporation. All rights reserved.


    Loading Dump File [C:\Windows\Minidump\070917-22140-01.dmp]
    Mini Kernel Dump File: Only registers and stack trace are available


    ************* Symbol Path validation summary **************
    Response                         Time (ms)     Location
    Deferred                                       SRV* C:\Symbols *http://msdl.microsoft.com/download/symbols
    Symbol search path is: SRV* C:\Symbols *http://msdl.microsoft.com/download/symbols
    Executable search path is: 
    Windows 10 Kernel Version 15063 MP (4 procs) Free x64
    Product: WinNt, suite: TerminalServer SingleUserTS
    Built by: 15063.0.amd64fre.rs2_release.170317-1834
    Machine Name:
    Kernel base = 0xfffff800`bbe85000 PsLoadedModuleList = 0xfffff800`bc1d15a0
    Debug session time: Sun Jul  9 23:31:52.454 2017 (UTC + 8:00)
    System Uptime: 0 days 0:51:20.204
    Loading Kernel Symbols
    ...............................................................
    ................................................................
    ...................................................
    Loading User Symbols
    Loading unloaded module list
    ..........
    *******************************************************************************
    *                                                                             *
    *                        Bugcheck Analysis                                    *
    *                                                                             *
    *******************************************************************************

    Use !analyze -v to get detailed debugging information.

    BugCheck 124, {0, ffffc3030609f028, bf800000, 124}

    Probably caused by : GenuineIntel

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

    1: 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: ffffc3030609f028, Address of the WHEA_ERROR_RECORD structure.
    Arg3: 00000000bf800000, High order 32-bits of the MCi_STATUS value.
    Arg4: 0000000000000124, Low order 32-bits of the MCi_STATUS value.

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


    DUMP_CLASS: 1

    DUMP_QUALIFIER: 400

    BUILD_VERSION_STRING:  10.0.15063.413 (WinBuild.160101.0800)

    SYSTEM_MANUFACTURER:  ASUS

    SYSTEM_PRODUCT_NAME:  All Series

    SYSTEM_SKU:  All

    SYSTEM_VERSION:  System Version

    BIOS_VENDOR:  American Megatrends Inc.

    BIOS_VERSION:  3003

    BIOS_DATE:  10/28/2015

    BASEBOARD_MANUFACTURER:  ASUSTeK COMPUTER INC.

    BASEBOARD_PRODUCT:  MAXIMUS VII GENE

    BASEBOARD_VERSION:  Rev 1.xx

    DUMP_TYPE:  2

    BUGCHECK_P1: 0

    BUGCHECK_P2: ffffc3030609f028

    BUGCHECK_P3: bf800000

    BUGCHECK_P4: 124

    BUGCHECK_STR:  0x124_GenuineIntel

    CPU_COUNT: 4

    CPU_MHZ: ce2

    CPU_VENDOR:  GenuineIntel

    CPU_FAMILY: 6

    CPU_MODEL: 3c

    CPU_STEPPING: 3

    CPU_MICROCODE: 6,3c,3,0 (F,M,S,R)  SIG: 1E'00000000 (cache) 1E'00000000 (init)

    CUSTOMER_CRASH_COUNT:  1

    DEFAULT_BUCKET_ID:  WIN8_DRIVER_FAULT

    PROCESS_NAME:  League of Legends.exe

    CURRENT_IRQL:  f

    ANALYSIS_SESSION_HOST:  DESKTOP-4PU55E5

    ANALYSIS_SESSION_TIME:  07-10-2017 00:33:44.0153

    ANALYSIS_VERSION: 10.0.14321.1024 amd64fre

    STACK_TEXT:  
    ffff9b81`b1ceb6b8 fffff800`bbe425cf : 00000000`00000124 00000000`00000000 ffffc303`0609f028 00000000`bf800000 : nt!KeBugCheckEx
    ffff9b81`b1ceb6c0 fffff800`bc0e125d : ffffc303`0609f028 ffffc303`04680490 ffffc303`04680490 ffffc303`04680490 : hal!HalBugCheckSystem+0xcf
    ffff9b81`b1ceb700 fffff800`bbe42af8 : 00000000`00000728 00000000`00000001 00000000`00000000 00000000`00000000 : nt!WheaReportHwError+0x25d
    ffff9b81`b1ceb760 fffff800`bbe42e58 : 00000000`00000010 00000000`00000001 ffff9b81`b1ceb908 00000000`00000001 : hal!HalpMcaReportError+0x50
    ffff9b81`b1ceb8b0 fffff800`bbe42d46 : ffffc303`044e7740 00000000`00000001 00000000`00000000 00000000`00000000 : hal!HalpMceHandlerCore+0xe0
    ffff9b81`b1ceb900 fffff800`bbe42f8a : 00000000`00000004 00000000`00000001 00000000`00000000 00000000`00000000 : hal!HalpMceHandler+0xda
    ffff9b81`b1ceb940 fffff800`bbe43120 : ffffc303`044e7740 ffff9b81`b1cebb70 00000000`00000000 00000000`00000000 : hal!HalpMceHandlerWithRendezvous+0xce
    ffff9b81`b1ceb970 fffff800`bbffb5bb : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : hal!HalHandleMcheck+0x40
    ffff9b81`b1ceb9a0 fffff800`bbffb32c : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KxMcheckAbort+0x7b
    ffff9b81`b1cebae0 fffff800`bbeb89e2 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiMcheckAbort+0x1ac
    ffff9b81`b711a870 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSwapThread+0xb2


    STACK_COMMAND:  kb

    THREAD_SHA1_HASH_MOD_FUNC:  0b2f08161ae5ac7f28cf96ee8e0876121ed8bc63

    THREAD_SHA1_HASH_MOD_FUNC_OFFSET:  be78ca69dc9d87fb303b783eea7545a601f0d7d0

    THREAD_SHA1_HASH_MOD:  bba6629b38ee48af58586b1285e003efb528212b

    FOLLOWUP_NAME:  MachineOwner

    MODULE_NAME: GenuineIntel

    IMAGE_NAME:  GenuineIntel

    DEBUG_FLR_IMAGE_TIMESTAMP:  0

    FAILURE_BUCKET_ID:  0x124_GenuineIntel_PROCESSOR_CACHE

    BUCKET_ID:  0x124_GenuineIntel_PROCESSOR_CACHE

    PRIMARY_PROBLEM_CLASS:  0x124_GenuineIntel_PROCESSOR_CACHE

    TARGET_TIME:  2017-07-09T15:31:52.000Z

    OSBUILD:  15063

    OSSERVICEPACK:  413

    SERVICEPACK_NUMBER: 0

    OS_REVISION: 0

    SUITE_MASK:  272

    PRODUCT_TYPE:  1

    OSPLATFORM_TYPE:  x64

    OSNAME:  Windows 10

    OSEDITION:  Windows 10 WinNt TerminalServer SingleUserTS

    OS_LOCALE:  

    USER_LCID:  0

    OSBUILD_TIMESTAMP:  2017-06-03 16:53:36

    BUILDDATESTAMP_STR:  160101.0800

    BUILDLAB_STR:  WinBuild

    BUILDOSVER_STR:  10.0.15063.413

    ANALYSIS_SESSION_ELAPSED_TIME: 475

    ANALYSIS_SOURCE:  KM

    FAILURE_ID_HASH_STRING:  km:0x124_genuineintel_processor_cache

    FAILURE_ID_HASH:  {4c8f3f5e-1af5-ed8b-df14-d42663b1dfa7}

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

    1: kd> 
    1: kd> 
    1: kd> 
    1: kd> 
    1: kd> 
    1: kd> 
    1: kd> 
    1: kd> 
    1: kd> 
    1: kd> 
    1: kd> 
    1: kd> 
    1: kd> 
    1: kd> 
    1: kd> 


    2017年7月9日 下午 04:48

所有回覆

  • 你好, 0x124_GenuineIntel_PROCESSOR_CACHE這個錯誤是Hardware方面的問題

    但比較麻煩的是這個錯誤碼在miniDump裡其實是找不到很確實是從那個部件出了問題

    通常有幾個先行的排解辦法, 

    1. 如果你的電腦CPU有做超頻, 請先把它調回出廠設定

    2. 按你的主機板去廠方看看有沒有BIOS韌體更新

    如果這兩個項目不能解決, 請繼續把電腦裡所有Hardware的驅動程式更新到最新


    邊幫助, 邊鍛鍊

    2017年7月10日 上午 01:57
  • 您好,主機板BIOS已經更新到最新,CPU沒有超頻也關閉TURBO了,驅動程式也是最新的,接上顯示卡打LOL還是藍屏,但是用內顯時沒有發生藍屏。
    2017年7月10日 上午 09:22
  • 你好, 0x124_GenuineIntel_PROCESSOR_CACHE這個錯誤是Hardware方面的問題

    但比較麻煩的是這個錯誤碼在miniDump裡其實是找不到很確實是從那個部件出了問題

    通常有幾個先行的排解辦法, 

    1. 如果你的電腦CPU有做超頻, 請先把它調回出廠設定

    2. 按你的主機板去廠方看看有沒有BIOS韌體更新

    如果這兩個項目不能解決, 請繼續把電腦裡所有Hardware的驅動程式更新到最新


    邊幫助, 邊鍛鍊

    您好,主機板BIOS已經更新到最新,CPU沒有超頻也關閉TURBO了,驅動程式也是最新的,接上顯示卡打LOL還是藍屏,但是用內顯時沒有發生藍屏。
    2017年7月10日 上午 09:23
  • 如果你已經把顯示卡都轉新的, 但仍然會因為顯示卡問題而藍屏, 可以看看是不是主板卡槽問題

    如果可以的話, 清潔一下, 或直接轉插其他卡槽, 看看有沒有改善

    再不行, 可以找找舊一點的顯示卡驅動程式來試

    有時可能是與其他Hardware不相容, 連一只滑鼠都可以是問題所在


    邊幫助, 邊鍛鍊

    2017年7月11日 上午 02:14