Whea logger id 18 hatası

bilgisayar restart atıyor rastgele.Olay defterinde Whea-logger ıd 18 hatası gözüküyor.Oc yapmıyorum ve en son drivelerı ve biosu kullanıyorum.

sistemimim amd 3500x

asus b450m dragon

asus tuf 3 evo 5600xt

ripjaws 3200mhz ram x1

thermaltake 650w

mini dump analazi ise şöyle

Kod 
Yığını:
*******************************************************************************
*                                                                             *
*                        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. Try !errrec Address of the WHEA_ERROR_RECORD structure to get more details.
Arguments:
Arg1: 0000000000000000, Machine Check Exception
Arg2: ffffc80fff1b48c0, Address of the WHEA_ERROR_RECORD structure.
Arg3: 00000000bea00000, High order 32-bits of the MCi_STATUS value.
Arg4: 0000000000000108, Low order 32-bits of the MCi_STATUS value.

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

fffff8008280f340: Unable to get Flags value from nt!KdVersionBlock
fffff8008280f340: Unable to get Flags value from nt!KdVersionBlock
*************************************************************************
***                                                                   ***
***                                                                   ***
***    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                ***
***                                                                   ***
*************************************************************************
fffff8008280f340: Unable to get Flags value from nt!KdVersionBlock
*************************************************************************
***                                                                   ***
***                                                                   ***
***    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                ***
***                                                                   ***
*************************************************************************

KEY_VALUES_STRING: 1

    Key  : Analysis.CPU.mSec
    Value: 2999

    Key  : Analysis.DebugAnalysisProvider.CPP
    Value: Create: 8007007e on DESKTOP-P6ICE5U

    Key  : Analysis.DebugData
    Value: CreateObject

    Key  : Analysis.DebugModel
    Value: CreateObject

    Key  : Analysis.Elapsed.mSec
    Value: 13643

    Key  : Analysis.Memory.CommitPeak.Mb
    Value: 79

    Key  : Analysis.System
    Value: CreateObject

    Key  : WHEA.MCiStatus.Code
    Value: 0xbea0000000000108

    Key  : WHEA.MCiStatus.McaError
    Value: 0x0108

    Key  : WHEA.MCiStatus.ModelError
    Value: 0x0000

    Key  : WHEA.MCiStatus.Reserved
    Value: 0x00a00000


ADDITIONAL_XML: 1

OS_BUILD_LAYERS: 1

DUMP_FILE_ATTRIBUTES: 0x18
  Kernel Generated Triage Dump
  Live Generated Dump

BUGCHECK_CODE:  124

BUGCHECK_P1: 0

BUGCHECK_P2: ffffc80fff1b48c0

BUGCHECK_P3: bea00000

BUGCHECK_P4: 108

PROCESS_NAME:  smss.exe

STACK_TEXT:  
ffff8180`973d4190 fffff800`82559eef     : ffffc80f`ff1b48a0 00000000`00000000 ffffc80f`ff1b48c0 00000000`00000022 : nt!LkmdTelCreateReport+0x13e
ffff8180`973d46d0 fffff800`82559de6     : ffffc80f`ff1b48a0 fffff800`00000000 00000033`00000000 00000033`327df6c0 : nt!WheapReportLiveDump+0x7b
ffff8180`973d4710 fffff800`823b61dd     : 00000000`00000001 ffff8180`973d4b80 00000033`327df6c0 00000000`000001a0 : nt!WheapReportDeferredLiveDumps+0x7a
ffff8180`973d4740 fffff800`8229a467     : 00000000`00000000 ffffc80f`fcee8030 00000000`00000103 00000000`00000000 : nt!WheaCrashDumpInitializationComplete+0x59
ffff8180`973d4770 fffff800`82005fb8     : ffffc800`02600000 ffffc800`02607d00 ffff8180`973d4b80 ffffc80f`00000000 : nt!NtSetSystemInformation+0x1f7
ffff8180`973d4b00 00007ffd`947cf2c4     : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceCopyEnd+0x28
00000033`327df668 00000000`00000000     : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x00007ffd`947cf2c4


MODULE_NAME: AuthenticAMD

IMAGE_NAME:  AuthenticAMD.sys

STACK_COMMAND:  .thread ; .cxr ; kb

FAILURE_BUCKET_ID:  LKD_0x124_0_AuthenticAMD_BANK0_MSCOD0000_MCACOD0108_PCC_UC_IMAGE_AuthenticAMD.sys

OSPLATFORM_TYPE:  x64

OSNAME:  Windows 10

FAILURE_ID_HASH:  {509acb9c-038f-dfdb-adc2-7917670271d1}

Followup:     MachineOwner