Dump çıktısı sorun olarak CPU'yu işaret ediyor. OC var mıydı acaba? Emin olamadığımdan soruyorum.
[CODE title="Dökümler"]*******************************************************************************
* *
* 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: ffffd98b5f6a1a90, Address of the nt!_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:
------------------
*************************************************************************
*** ***
*** ***
*** 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 ***
*** ***
*************************************************************************
KEY_VALUES_STRING: 1
Key : Analysis.CPU.mSec
Value: 8202.
Key : Analysis.DebugAnalysisManager
Value: Create.
Key : Analysis.Elapsed.mSec
Value: 16765.
Key : Analysis.Init.CPU.mSec
Value: 1077.
Key : Analysis.Init.Elapsed.mSec
Value: 10143.
Key : Analysis.Memory.CommitPeak.Mb
Value: 83.
FILE_IN_CAB: WHEA-20220501-0111.dmp
DUMP_FILE_ATTRIBUTES: 0x18.
Kernel Generated Triage Dump.
Live Generated Dump.
BUGCHECK_CODE: 124.
BUGCHECK_P1: 0
BUGCHECK_P2: ffffd98b5f6a1a90.
BUGCHECK_P3: bea00000.
BUGCHECK_P4: 108.
PROCESS_NAME: smss.exe
STACK_TEXT:
ffffec08`9099a190 fffff804`7ef5ba3f : ffffd98b`5f6a1a70 00000000`00000000 ffffd98b`5f6a1a90 00000000`00000022 : nt!LkmdTelCreateReport+0x13e
ffffec08`9099a6d0 fffff804`7ef5b936 : ffffd98b`5f6a1a70 fffff804`00000000 0000009a`00000000 0000009a`aab7f5c0 : nt!WheapReportLiveDump+0x7b
ffffec08`9099a710 fffff804`7edc360d : 00000000`00000001 ffffec08`9099ab80 0000009a`aab7f5c0 00000000`00000210 : nt!WheapReportDeferredLiveDumps+0x7a
ffffec08`9099a740 fffff804`7ecac347 : 00000000`00000000 ffffd98b`5be73030 00000000`00000103 00000000`00000000 : nt!WheaCrashDumpInitializationComplete+0x59
ffffec08`9099a770 fffff804`7ea092b8 : ffffd98b`61080000 ffffd98b`6108b6b0 ffffec08`9099ab80 ffffd98b`00000000 : nt!NtSetSystemInformation+0x1f7
ffffec08`9099ab00 00007ffe`232502a4 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceCopyEnd+0x28
0000009a`aab7f568 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x00007ffe`232502a4
MODULE_NAME: AuthenticAMD.
IMAGE_NAME: AuthenticAMD.sys
STACK_COMMAND: .cxr; .ecxr ; kb.
FAILURE_BUCKET_ID: LKD_0x124_0_AuthenticAMD_PROCESSOR__UNKNOWN_IMAGE_AuthenticAMD.sys
OSPLATFORM_TYPE: x64.
OSNAME: Windows 10.
FAILURE_ID_HASH: {f59f17e7-f24e-04f5-3f16-e9425b2acba5}
Followup: MachineOwner.
---------[/CODE]
