Система перезагрузилась, завершив работу с ошибками. произошел критический сбой или неожиданно отключилось питание. Как решить проблему?

Это что то даст?

******************************************************************************

* *

* 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

nt!_WHEA_ERROR_RECORD structure that describes the error condition. Try !errrec Address of the nt!_WHEA_ERROR_RECORD structure to get more details.

Arguments:

Arg1: 0000000000000000, Machine Check Exception

Arg2: ffffbf0793548028, Address of the nt!_WHEA_ERROR_RECORD structure.

Arg3: 00000000be000000, High order 32-bits of the MCi_STATUS value.

Arg4: 0000000000800400, Low order 32-bits of the MCi_STATUS value.

Debugging Details:

---

*************************************************************************

*** ***

*** ***

*** Either you specified an unqualified symbol, or your debugger ***

*** doesn't have full symbol information. Unqualified symbol ***

*** resolution is turned off by default. Please either specify a ***

*** fully qualified symbol module!symbolname, or enable resolution ***

*** of unqualified symbols by typing ".symopt- 100". Note that ***

*** enabling unqualified symbol resolution with network symbol ***

*** server shares in the symbol path may cause the debugger to ***

*** appear to hang for long periods of time when an incorrect ***

*** symbol name is typed or the network symbol server is down. ***

*** ***

*** For some commands to work properly, your symbol path ***

*** must point to .pdb files that have full type information. ***

*** ***

*** Certain .pdb files (such as the public OS symbols) do not ***

*** contain the required information. Contact the group that ***

*** provided you with these symbols if you need this command to ***

*** work. ***

*** ***

*** Type referenced: hal!_WHEA_PROCESSOR_GENERIC_ERROR_SECTION ***

*** ***

*************************************************************************

*************************************************************************

*** ***

*** ***

*** Either you specified an unqualified symbol, or your debugger ***

*** doesn't have full symbol information. Unqualified symbol ***

*** resolution is turned off by default. Please either specify a ***

*** fully qualified symbol module!symbolname, or enable resolution ***

*** of unqualified symbols by typing ".symopt- 100". Note that ***

*** enabling unqualified symbol resolution with network symbol ***

*** server shares in the symbol path may cause the debugger to ***

*** appear to hang for long periods of time when an incorrect ***

*** symbol name is typed or the network symbol server is down. ***

*** ***

*** For some commands to work properly, your symbol path ***

*** must point to .pdb files that have full type information. ***

*** ***

*** Certain .pdb files (such as the public OS symbols) do not ***

*** contain the required information. Contact the group that ***

*** provided you with these symbols if you need this command to ***

*** work. ***

*** ***

*** Type referenced: hal!_WHEA_PROCESSOR_GENERIC_ERROR_SECTION ***

*** ***

*************************************************************************

*** WARNING: Check Image - Checksum mismatch - Dump: 0x208038, File: 0x208034 - C:\ProgramData\Dbg\sym\BTHport.sys\2AFD096C202000\BTHport.sys

KEY_VALUES_STRING: 1

Key  : Analysis.CPU.mSec 

Value: 2734 

Key  : Analysis.Elapsed.mSec 

Value: 5065 

Key  : Analysis.IO.Other.Mb 

Value: 0 

Key  : Analysis.IO.Read.Mb 

Value: 0 

Key  : Analysis.IO.Write.Mb 

Value: 2 

Key  : Analysis.Init.CPU.mSec 

Value: 359 

Key  : Analysis.Init.Elapsed.mSec 

Value: 70489 

Key  : Analysis.Memory.CommitPeak.Mb 

Value: 105 

Key  : Bugcheck.Code.LegacyAPI 

Value: 0x124 

Key  : Bugcheck.Code.TargetModel 

Value: 0x124 

Key  : Dump.Attributes.AsUlong 

Value: 1008 

Key  : Dump.Attributes.DiagDataWrittenToHeader 

Value: 1 

Key  : Dump.Attributes.ErrorCode 

Value: 0 

Key  : Dump.Attributes.KernelGeneratedTriageDump 

Value: 1 

Key  : Dump.Attributes.LastLine 

Value: Dump completed successfully. 

Key  : Dump.Attributes.ProgressPercentage 

Value: 0 

Key  : Failure.Bucket 

Value: 0x124\_0\_GenuineIntel\_PROCESSOR\_\_UNKNOWN\_IMAGE\_GenuineIntel.sys 

Key  : Failure.Hash 

Value: {5371cb52-c3d9-558e-47d4-d31c09567ca2} 

BUGCHECK_CODE: 124

BUGCHECK_P1: 0

BUGCHECK_P2: ffffbf0793548028

BUGCHECK_P3: be000000

BUGCHECK_P4: 800400

FILE_IN_CAB: 083124-9031-01.dmp

DUMP_FILE_ATTRIBUTES: 0x1008

Kernel Generated Triage Dump

FAULTING_THREAD: ffffbf0791150040

BLACKBOXBSD: 1 (!blackboxbsd)

BLACKBOXNTFS: 1 (!blackboxntfs)

BLACKBOXWINLOGON: 1

CUSTOMER_CRASH_COUNT: 1

PROCESS_NAME: System

STACK_TEXT:

ffffd280521a58e8 fffff8002a8ffdfb : 0000000000000124 0000000000000000 ffffbf0793548028 00000000be000000 : nt!KeBugCheckEx

ffffd280521a58f0 fffff8002e0a10c0 : 0000000000000000 ffffd280521a59c9 ffffbf0793548028 ffffbf07916443e0 : nt!HalBugCheckSystem+0xeb

ffffd280521a5930 fffff8002aa0e60f : 0000000000000000 ffffd280521a59c9 ffffbf0793548028 244c8b0000048ce8 : PSHED!PshedBugCheckSystem+0x10

ffffd280521a5960 fffff8002a90182a : ffffbf079a31c900 ffffbf079a31c900 ffffbf0791644430 fffff8002a77d1ce : nt!WheaReportHwError+0x38f

ffffd280521a5a30 fffff8002a901c80 : 0000000000000003 ffffbf0700000003 ffff83847f271000 ffff83847f278000 : nt!HalpMcaReportError+0xb2

ffffd280521a5ba0 fffff8002a901b14 : ffffbf079115ec90 55afe81c00000001 0000000000000000 83fffe340000000c : nt!HalpMceHandlerCore+0x138

ffffd280521a5c00 fffff8002a901db9 : 000000000000000c 0000000000000001 0000000000000000 24448b66ffff56fa : nt!HalpMceHandler+0xe0

ffffd280521a5c40 fffff8002a900f72 : 0000000000000000 0000000000000000 ffffd280521a5ed0 8310c183c78bce8b : nt!HalpMceHandlerWithRendezvous+0xc9

ffffd280521a5c70 fffff8002a90372b : ffffbf079115ec90 8b00000000143044 cd8b515000d083c7 574ae8fffe3403e8 : nt!HalpHandleMachineCheck+0x62

ffffd280521a5ca0 fffff8002a969bf9 : 6a5004468d006a00 6afffe335ee85902 e8cbb1d38bff6a03 4c2474ffffff566a : nt!HalHandleMcheck+0x3b

ffffd280521a5cd0 fffff8002a82853e : cbb1d1b70f000000 ffffff5647e8ff6a ffff70c6e80c2474 b1f18b56c30cc483 : nt!KiHandleMcheck+0x9

ffffd280521a5d00 fffff8002a828153 : 0000000000000010 0000000000000000 0000000000000000 ffffd280521a5ed0 : nt!KxMcheckAbort+0x7e

ffffd280521a5e40 fffff80055ba156f : fffff80055ba15c4 0000000000000000 0000000000000000 fffff069b48edf77 : nt!KiMcheckAbort+0x2d3

ffff83847f2774c8 fffff80055ba15c4 : 0000000000000000 0000000000000000 fffff069b48edf77 0000000000000000 : intelppm!MWaitIdle+0x1f

ffff83847f2774d0 fffff8002a62dbf6 : 0000000000000000 0000000000000089 00000000ffffffff 0000000351525a4e : intelppm!AcpiCStateIdleExecute+0x24

ffff83847f277500 fffff8002a62d5a1 : ffffbf079b35f860 0000000000000000 ffffffffffffffff ffff83847f2779b0 : nt!PpmIdleExecuteTransition+0x426

ffff83847f277950 fffff8002a81af64 : 0000000000000000 0000000000000000 ffffbf0791150040 ffffbf07a4ede080 : nt!PoIdle+0x361

ffff83847f277b40 0000000000000000 : ffff83847f278000 ffff83847f271000 0000000000000000 0000000000000000 : nt!KiIdleLoop+0x54

MODULE_NAME: GenuineIntel

IMAGE_NAME: GenuineIntel.sys

STACK_COMMAND: .process /r /p 0xfffff8002b148f40; .thread 0xffffbf0791150040 ; kb

FAILURE_BUCKET_ID: 0x124_0_GenuineIntel_PROCESSOR__UNKNOWN_IMAGE_GenuineIntel.sys

OSPLATFORM_TYPE: x64

OSNAME: Windows 10

FAILURE_ID_HASH: {5371cb52-c3d9-558e-47d4-d31c09567ca2}

Followup: MachineOwner

---

А есть похожие программы?

Тоже пробывал, и ничего