大家好，近來小弟碰上系統會無故重啟的問題，尤其是看網絡視頻的時候，點擊另一頁視頻的時候就出現，奇怪的是玩遊戲不會發生。看起來好像是處理器錯誤，如果是真的話應該怎麽辦？
Microsoft (R) Windows Debugger Version 10.0.18303.1000 AMD64
Copyright (c) Microsoft Corporation. All rights reserved.
Loading Dump File [C:\Windows\Minidump\021019-36515-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available
Symbol search path is: srv*
Executable search path is:
Windows 10 Kernel Version 17763 MP (12 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Machine Name:
Kernel base = 0xfffff804`6bc1c000 PsLoadedModuleList = 0xfffff804`6c037ad0
Debug session time: Sun Feb 10 20:51:18.408 2019 (UTC + 8:00)
System Uptime: 0 days 0:00:23.182
Loading Kernel Symbols
.
Press ctrl-c (cdb, kd, ntsd) or ctrl-break (windbg) to abort symbol loads that take too long.
Run !sym noisy before .reload to track down problems loading symbols.
..............................................................
...
Loading User Symbols
Mini Kernel Dump does not contain unloaded driver list
For analysis of this file, run !analyze -v
nt!WheapCreateLiveTriageDump+0x7b:
fffff804`6c4f8a37 48895c2438 mov qword ptr [rsp+38h],rbx ss:0018:ffffe70e`d94ae5d8=ffff930700000a60
8: 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: ffff93074ce6c8c8, 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:
------------------
KEY_VALUES_STRING: 1
PROCESSES_ANALYSIS: 1
STACKHASH_ANALYSIS: 1
TIMELINE_ANALYSIS: 1
DUMP_CLASS: 1
DUMP_QUALIFIER: 400
BUILD_VERSION_STRING: 10.0.17763.292 (WinBuild.160101.0800)
DUMP_TYPE: 2
BUGCHECK_P1: 0
BUGCHECK_P2: ffff93074ce6c8c8
BUGCHECK_P3: 0
BUGCHECK_P4: 0
BUGCHECK_STR: 0x124_AuthenticAMD
CPU_COUNT: c
CPU_MHZ: d42
CPU_VENDOR: AuthenticAMD
CPU_FAMILY: 17
CPU_MODEL: 8
CPU_STEPPING: 2
CUSTOMER_CRASH_COUNT: 1
DEFAULT_BUCKET_ID: WIN8_DRIVER_FAULT
PROCESS_NAME: System
CURRENT_IRQL: 0
ANALYSIS_SESSION_HOST: DESKTOP-CTJE3BB
ANALYSIS_SESSION_TIME: 02-10-2019 21:37:23.0155
ANALYSIS_VERSION: 10.0.18303.1000 amd64fre
STACK_TEXT:
ffffe70e`d94ae5a0 fffff804`6c19aa29 : ffff9307`4cf9b0c0 ffff9307`4ce6c8a0 fffff804`6c023600 fffff804`00000000 : nt!WheapCreateLiveTriageDump+0x7b
ffffe70e`d94aead0 fffff804`6bf3ad78 : ffff9307`4ce6c8a0 fffff804`6bc7c811 00000000`00000000 ffffd384`00000000 : nt!WheapCreateTriageDumpFromPreviousSession+0x2d
ffffe70e`d94aeb00 fffff804`6bf3ba8b : fffff804`6c0235a0 fffff804`6c023600 ffff9307`50ff63b8 ffff9307`4bc50720 : nt!WheapProcessWorkQueueItem+0x48
ffffe70e`d94aeb40 fffff804`6bcd01ea : ffff9307`4bc62ca0 ffff9307`4cf9b0c0 ffff9307`50ff6300 ffff9307`00000000 : nt!WheapWorkQueueWorkerRoutine+0x2b
ffffe70e`d94aeb70 fffff804`6bca2bc5 : ffff9307`4cf9b0c0 ffff9307`4bc70080 ffff9307`4cf9b0c0 00000065`b4bbbdff : nt!ExpWorkerThread+0x16a
ffffe70e`d94aec10 fffff804`6bdd689c : ffff8300`3a880180 ffff9307`4cf9b0c0 fffff804`6bca2b70 ffffffff`ffffffff : nt!PspSystemThreadStartup+0x55
ffffe70e`d94aec60 00000000`00000000 : ffffe70e`d94af000 ffffe70e`d94a9000 00000000`00000000 00000000`00000000 : nt!KiStartSystemThread+0x1c
THREAD_SHA1_HASH_MOD_FUNC: 26acd050bd9f055d0a04825d57b9e0e6be9c1a07
THREAD_SHA1_HASH_MOD_FUNC_OFFSET: 2d7687bc4d9a24dd51c507635bc4ce8aa00fde94
THREAD_SHA1_HASH_MOD: 30a3e915496deaace47137d5b90c3ecc03746bf6
FOLLOWUP_NAME: MachineOwner
MODULE_NAME: AuthenticAMD
IMAGE_NAME: AuthenticAMD
DEBUG_FLR_IMAGE_TIMESTAMP: 0
STACK_COMMAND: .thread ; .cxr ; kb
FAILURE_BUCKET_ID: 0x124_AuthenticAMD_PROCESSOR_CACHE
BUCKET_ID: 0x124_AuthenticAMD_PROCESSOR_CACHE
PRIMARY_PROBLEM_CLASS: 0x124_AuthenticAMD_PROCESSOR_CACHE
TARGET_TIME: 2019-02-10T12:51:18.000Z
OSBUILD: 17763
OSSERVICEPACK: 292
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: unknown_date
BUILDDATESTAMP_STR: 160101.0800
BUILDLAB_STR: WinBuild
BUILDOSVER_STR: 10.0.17763.292
ANALYSIS_SESSION_ELAPSED_TIME: 1d02
ANALYSIS_SOURCE: KM
FAILURE_ID_HASH_STRING: km:0x124_authenticamd_processor_cache
FAILURE_ID_HASH: {b533751b-676e-7546-bcdc-24e6c40d0064}
Microsoft (R) Windows Debugger Version 10.0.18303.1000 AMD64
Copyright (c) Microsoft Corporation. All rights reserved.
Loading Dump File [C:\Windows\Minidump\021019-36515-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available
Symbol search path is: srv*
Executable search path is:
Windows 10 Kernel Version 17763 MP (12 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Machine Name:
Kernel base = 0xfffff804`6bc1c000 PsLoadedModuleList = 0xfffff804`6c037ad0
Debug session time: Sun Feb 10 20:51:18.408 2019 (UTC + 8:00)
System Uptime: 0 days 0:00:23.182
Loading Kernel Symbols
.
Press ctrl-c (cdb, kd, ntsd) or ctrl-break (windbg) to abort symbol loads that take too long.
Run !sym noisy before .reload to track down problems loading symbols.
..............................................................
...
Loading User Symbols
Mini Kernel Dump does not contain unloaded driver list
For analysis of this file, run !analyze -v
nt!WheapCreateLiveTriageDump+0x7b:
fffff804`6c4f8a37 48895c2438 mov qword ptr [rsp+38h],rbx ss:0018:ffffe70e`d94ae5d8=ffff930700000a60
8: 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: ffff93074ce6c8c8, 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:
------------------
KEY_VALUES_STRING: 1
PROCESSES_ANALYSIS: 1
STACKHASH_ANALYSIS: 1
TIMELINE_ANALYSIS: 1
DUMP_CLASS: 1
DUMP_QUALIFIER: 400
BUILD_VERSION_STRING: 10.0.17763.292 (WinBuild.160101.0800)
DUMP_TYPE: 2
BUGCHECK_P1: 0
BUGCHECK_P2: ffff93074ce6c8c8
BUGCHECK_P3: 0
BUGCHECK_P4: 0
BUGCHECK_STR: 0x124_AuthenticAMD
CPU_COUNT: c
CPU_MHZ: d42
CPU_VENDOR: AuthenticAMD
CPU_FAMILY: 17
CPU_MODEL: 8
CPU_STEPPING: 2
CUSTOMER_CRASH_COUNT: 1
DEFAULT_BUCKET_ID: WIN8_DRIVER_FAULT
PROCESS_NAME: System
CURRENT_IRQL: 0
ANALYSIS_SESSION_HOST: DESKTOP-CTJE3BB
ANALYSIS_SESSION_TIME: 02-10-2019 21:37:23.0155
ANALYSIS_VERSION: 10.0.18303.1000 amd64fre
STACK_TEXT:
ffffe70e`d94ae5a0 fffff804`6c19aa29 : ffff9307`4cf9b0c0 ffff9307`4ce6c8a0 fffff804`6c023600 fffff804`00000000 : nt!WheapCreateLiveTriageDump+0x7b
ffffe70e`d94aead0 fffff804`6bf3ad78 : ffff9307`4ce6c8a0 fffff804`6bc7c811 00000000`00000000 ffffd384`00000000 : nt!WheapCreateTriageDumpFromPreviousSession+0x2d
ffffe70e`d94aeb00 fffff804`6bf3ba8b : fffff804`6c0235a0 fffff804`6c023600 ffff9307`50ff63b8 ffff9307`4bc50720 : nt!WheapProcessWorkQueueItem+0x48
ffffe70e`d94aeb40 fffff804`6bcd01ea : ffff9307`4bc62ca0 ffff9307`4cf9b0c0 ffff9307`50ff6300 ffff9307`00000000 : nt!WheapWorkQueueWorkerRoutine+0x2b
ffffe70e`d94aeb70 fffff804`6bca2bc5 : ffff9307`4cf9b0c0 ffff9307`4bc70080 ffff9307`4cf9b0c0 00000065`b4bbbdff : nt!ExpWorkerThread+0x16a
ffffe70e`d94aec10 fffff804`6bdd689c : ffff8300`3a880180 ffff9307`4cf9b0c0 fffff804`6bca2b70 ffffffff`ffffffff : nt!PspSystemThreadStartup+0x55
ffffe70e`d94aec60 00000000`00000000 : ffffe70e`d94af000 ffffe70e`d94a9000 00000000`00000000 00000000`00000000 : nt!KiStartSystemThread+0x1c
THREAD_SHA1_HASH_MOD_FUNC: 26acd050bd9f055d0a04825d57b9e0e6be9c1a07
THREAD_SHA1_HASH_MOD_FUNC_OFFSET: 2d7687bc4d9a24dd51c507635bc4ce8aa00fde94
THREAD_SHA1_HASH_MOD: 30a3e915496deaace47137d5b90c3ecc03746bf6
FOLLOWUP_NAME: MachineOwner
MODULE_NAME: AuthenticAMD
IMAGE_NAME: AuthenticAMD
DEBUG_FLR_IMAGE_TIMESTAMP: 0
STACK_COMMAND: .thread ; .cxr ; kb
FAILURE_BUCKET_ID: 0x124_AuthenticAMD_PROCESSOR_CACHE
BUCKET_ID: 0x124_AuthenticAMD_PROCESSOR_CACHE
PRIMARY_PROBLEM_CLASS: 0x124_AuthenticAMD_PROCESSOR_CACHE
TARGET_TIME: 2019-02-10T12:51:18.000Z
OSBUILD: 17763
OSSERVICEPACK: 292
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: unknown_date
BUILDDATESTAMP_STR: 160101.0800
BUILDLAB_STR: WinBuild
BUILDOSVER_STR: 10.0.17763.292
ANALYSIS_SESSION_ELAPSED_TIME: 1d02
ANALYSIS_SOURCE: KM
FAILURE_ID_HASH_STRING: km:0x124_authenticamd_processor_cache
FAILURE_ID_HASH: {b533751b-676e-7546-bcdc-24e6c40d0064}
