F5F Stay Refreshed Software Operating Systems Latest problems with bsod and unexpected crashes (minidump analysis shared)

Latest problems with bsod and unexpected crashes (minidump analysis shared)

Latest problems with bsod and unexpected crashes (minidump analysis shared)

I
Increte
Junior Member
Find
9
03-03-2023, 11:33 PM
#1
Hello, the past month I've been having issues on and off with my system either crashing with a bsod or just everything going black and restarting under load, I've never seen this happen when just browsing the net, it's always when gaming. The crashes goes away once i disable CPB which makes me think one of the cores might be screwed and i just need to rma the CPU, would like a confirmation if possible Spoiler ************* Preparing the environment for Debugger Extensions Gallery repositories ************** ExtensionRepository : Implicit UseExperimentalFeatureForNugetShare : true AllowNugetExeUpdate : true NonInteractiveNuget : true AllowNugetMSCredentialProviderInstall : true AllowParallelInitializationOfLocalRepositories : true EnableRedirectToChakraJsProvider : false -- Configuring repositories ----> Repository : LocalInstalled, Enabled: true ----> Repository : UserExtensions, Enabled: true >>>>>>>>>>>>> Preparing the environment for Debugger Extensions Gallery repositories completed, duration 0.000 seconds ************* Waiting for Debugger Extensions Gallery to Initialize ************** >>>>>>>>>>>>> Waiting for Debugger Extensions Gallery to Initialize completed, duration 0.032 seconds ----> Repository : UserExtensions, Enabled: true, Packages count: 0 ----> Repository : LocalInstalled, Enabled: true, Packages count: 42 Microsoft ® Windows Debugger Version 10.0.27725.1000 AMD64 Copyright © Microsoft Corporation. All rights reserved. Loading Dump File [C:\Windows\Minidump\110524-6406-01.dmp] Mini Kernel Dump File: Only registers and stack trace are available ************* Path validation summary ************** Response Time (ms) Location Deferred srv* Symbol search path is: srv* Executable search path is: Windows 10 Kernel Version 19041 MP (16 procs) Free x64 Product: WinNt, suite: TerminalServer SingleUserTS Personal Edition build lab: 19041.1.amd64fre.vb_release.191206-1406 Kernel base = 0xfffff803`3ca00000 PsLoadedModuleList = 0xfffff803`3d62a7c0 Debug session time: Tue Nov 5 17:34:18.047 2024 (UTC + 2:00) System Uptime: 0 days 1:06:01.669 Loading Kernel Symbols ............................................................... ................................................................ ...................................................... Loading User Symbols PEB is paged out (Peb.Ldr = 00000071`56ed5018). Type ".hh dbgerr001" for details Loading unloaded module list ....... For analysis of this file, run !analyze -v nt!KeBugCheckEx: fffff803`3cdfe310 48894c2408 mov qword ptr [rsp+8],rcx ss:ffffe700`f7cee950=0000000000000124 12: 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 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: ffff85014882b028, Address of the nt!_WHEA_ERROR_RECORD structure. Arg3: 00000000fc800800, High order 32-bits of the MCi_STATUS value. Arg4: 00000000060c0859, 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: 2359 Key : Analysis.Elapsed.mSec Value: 7844 Key : Analysis.IO.Other.Mb Value: 1 Key : Analysis.IO.Read.Mb Value: 1 Key : Analysis.IO.Write.Mb Value: 4 Key : Analysis.Init.CPU.mSec Value: 437 Key : Analysis.Init.Elapsed.mSec Value: 3199 Key : Analysis.Memory.CommitPeak.Mb Value: 95 Key : Analysis.Version.DbgEng Value: 10.0.27725.1000 Key : Analysis.Version.Description Value: 10.2408.27.01 amd64fre Key : Analysis.Version.Ext Value: 1.2408.27.1 Key : Bugcheck.Code.LegacyAPI Value: 0x124 Key : Bugcheck.Code.TargetModel Value: 0x124 Key : Failure.Bucket Value: 0x124_0_AuthenticAMD_PROCESSOR__UNKNOWN_IMAGE_AuthenticAMD.sys Key : Failure.Hash Value: {035dcc87-485b-74b3-1c1b-ee50cb0c2865} Key : WER.OS.Branch Value: vb_release Key : WER.OS.Version Value: 10.0.19041.1 BUGCHECK_CODE: 124 BUGCHECK_P1: 0 BUGCHECK_P2: ffff85014882b028 BUGCHECK_P3: fc800800 BUGCHECK_P4: 60c0859 FILE_IN_CAB: 110524-6406-01.dmp FAULTING_THREAD: ffff8501581b2080 BLACKBOXBSD: 1 (!blackboxbsd) BLACKBOXNTFS: 1 (!blackboxntfs) BLACKBOXWINLOGON: 1 CUSTOMER_CRASH_COUNT: 1 PROCESS_NAME: TL.exe STACK_TEXT: ffffe700`f7cee948 fffff803`3ceba21a : 00000000`00000124 00000000`00000000 ffff8501`4882b028 00000000`fc800800 : nt!KeBugCheckEx ffffe700`f7cee950 fffff803`38d115b0 : 00000000`00000000 ffff8501`4882b028 ffff8501`473f3cb0 ffff8501`4882b028 : nt!HalBugCheckSystem+0xca ffffe700`f7cee990 fffff803`3cfbc82d : 00000000`00000000 ffffe700`f7ceea29 ffff8501`4882b028 ffff8501`473f3cb0 : PSHED!PshedBugCheckSystem+0x10 ffffe700`f7cee9c0 fffff803`3cebbb41 : ffff8501`4d47a900 ffff8501`4d47a900 ffff8501`473f3d00 ffff8501`473f3cb0 : nt!WheaReportHwError+0x3dd ffffe700`f7ceea90 fffff803`3cebbeb3 : 00000000`0000000c ffff8501`473f3d00 ffff8501`473f3cb0 00000000`0000000c : nt!HalpMcaReportError+0xb1 ffffe700`f7ceec00 fffff803`3cebbd90 : ffff8501`45cfe8a0 00000000`00000000 ffffe700`f7ceee00 00000000`00000000 : nt!HalpMceHandlerCore+0xef ffffe700`f7ceec50 fffff803`3cebb2d5 : ffff8501`45cfe8a0 ffffe700`f7ceeef0 00000000`00000000 00000000`00000000 : nt!HalpMceHandler+0xe0 ffffe700`f7ceec90 fffff803`3cebda95 : ffff8501`45cfe8a0 00000000`00000000 00000000`00000000 00000000`00000000 : nt!HalpHandleMachineCheck+0xe9 ffffe700`f7ceecc0 fffff803`3cf13919 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!HalHandleMcheck+0x35 ffffe700`f7ceecf0 fffff803`3ce0f57a : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiHandleMcheck+0x9 ffffe700`f7ceed20 fffff803`3ce0f237 : 00000000`00000000 00000000`00000000 00000071`41b5f890 00000000`00000000 : nt!KxMcheckAbort+0x7a ffffe700`f7ceee60 00007ffb`5bf490aa : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiMcheckAbort+0x277 00000071`41b5f818 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x00007ffb`5bf490aa MODULE_NAME: AuthenticAMD IMAGE_NAME: AuthenticAMD.sys STACK_COMMAND: .process /r /p 0xffff85015d047340; .thread 0xffff8501581b2080 ; kb FAILURE_BUCKET_ID: 0x124_0_AuthenticAMD_PROCESSOR__UNKNOWN_IMAGE_AuthenticAMD.sys OS_VERSION: 10.0.19041.1 BUILDLAB_STR: vb_release OSPLATFORM_TYPE: x64 OSNAME: Windows 10 Spoiler ************* Preparing the environment for Debugger Extensions Gallery repositories ************** ExtensionRepository : Implicit UseExperimentalFeatureForNugetShare : true AllowNugetExeUpdate : true NonInteractiveNuget : true AllowNugetMSCredentialProviderInstall : true AllowParallelInitializationOfLocalRepositories : true EnableRedirectToChakraJsProvider : false -- Configuring repositories ----> Repository : LocalInstalled, Enabled: true ----> Repository : UserExtensions, Enabled: true >>>>>>>>>>>>> Preparing the environment for Debugger Extensions Gallery repositories completed, duration 0.000 seconds ************* Waiting for Debugger Extensions Gallery to Initialize ************** >>>>>>>>>>>>> Waiting for Debugger Extensions Gallery to Initialize completed, duration 0.032 seconds ----> Repository : UserExtensions, Enabled: true, Packages count: 0 ----> Repository : LocalInstalled, Enabled: true, Packages count: 42 Microsoft ® Windows Debugger Version 10.0.27725.1000 AMD64 Copyright © Microsoft Corporation. All rights reserved. Loading Dump File [C:\Windows\Minidump\110524-10125-01.dmp] Mini Kernel Dump File: Only registers and stack trace are available ************* Path validation summary ************** Response Time (ms) Location Deferred srv* Symbol search path is: srv* Executable search path is: Windows 10 Kernel Version 19041 MP (16 procs) Free x64 Product: WinNt, suite: TerminalServer SingleUserTS Personal Edition build lab: 19041.1.amd64fre.vb_release.191206-1406 Kernel base = 0xfffff800`56c00000 PsLoadedModuleList = 0xfffff800`5782a7c0 Debug session time: Tue Nov 5 22:59:28.601 2024 (UTC + 2:00) System Uptime: 0 days 0:21:58.186 Loading Kernel Symbols ............................................................... ................................................................ ...................................................... Loading User Symbols PEB is paged out (Peb.Ldr = 00000024`a8961018). Type ".hh dbgerr001" for details Loading unloaded module list ....... For analysis of this file, run !analyze -v nt!KeBugCheckEx: fffff800`56ffe310 48894c2408 mov qword ptr [rsp+8],rcx ss:ffff8380`87e9b950=0000000000000124 6: 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 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: ffffe0850d82b028, Address of the nt!_WHEA_ERROR_RECORD structure. Arg3: 00000000bc000800, High order 32-bits of the MCi_STATUS value. Arg4: 0000000001010135, 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: 2140 Key : Analysis.Elapsed.mSec Value: 3093 Key : Analysis.IO.Other.Mb Value: 0 Key : Analysis.IO.Read.Mb Value: 1 Key : Analysis.IO.Write.Mb Value: 0 Key : Analysis.Init.CPU.mSec Value: 421 Key : Analysis.Init.Elapsed.mSec Value: 2629 Key : Analysis.Memory.CommitPeak.Mb Value: 94 Key : Analysis.Version.DbgEng Value: 10.0.27725.1000 Key : Analysis.Version.Description Value: 10.2408.27.01 amd64fre Key : Analysis.Version.Ext Value: 1.2408.27.1 Key : Bugcheck.Code.LegacyAPI Value: 0x124 Key : Bugcheck.Code.TargetModel Value: 0x124 Key : Failure.Bucket Value: 0x124_0_AuthenticAMD_PROCESSOR__UNKNOWN_IMAGE_AuthenticAMD.sys Key : Failure.Hash Value: {035dcc87-485b-74b3-1c1b-ee50cb0c2865} Key : WER.OS.Branch Value: vb_release Key : WER.OS.Version Value: 10.0.19041.1 BUGCHECK_CODE: 124 BUGCHECK_P1: 0 BUGCHECK_P2: ffffe0850d82b028 BUGCHECK_P3: bc000800 BUGCHECK_P4: 1010135 FILE_IN_CAB: 110524-10125-01.dmp FAULTING_THREAD: ffffe0851ea4d080 BLACKBOXBSD: 1 (!blackboxbsd) BLACKBOXNTFS: 1 (!blackboxntfs) BLACKBOXWINLOGON: 1 CUSTOMER_CRASH_COUNT: 1 PROCESS_NAME: cs2.exe STACK_TEXT: ffff8380`87e9b948 fffff800`570ba21a : 00000000`00000124 00000000`00000000 ffffe085`0d82b028 00000000`bc000800 : nt!KeBugCheckEx ffff8380`87e9b950 fffff800`53c815b0 : 00000000`00000000 ffffe085`0d82b028 ffffe085`0afebd60 ffffe085`0d82b028 : nt!HalBugCheckSystem+0xca ffff8380`87e9b990 fffff800`571bc82d : 00000000`00000000 ffff8380`87e9ba29 ffffe085`0d82b028 ffffe085`0afebd60 : PSHED!PshedBugCheckSystem+0x10 ffff8380`87e9b9c0 fffff800`570bbb41 : ffffe085`0ae68ac0 ffffe085`0ae68ac0 ffffe085`0afebdb0 ffffe085`0afebd60 : nt!WheaReportHwError+0x3dd ffff8380`87e9ba90 fffff800`570bbeb3 : 00000000`00000006 ffffe085`0afebdb0 ffffe085`0afebd60 00000000`00000006 : nt!HalpMcaReportError+0xb1 ffff8380`87e9bc00 fffff800`570bbd90 : ffffe085`0acfe450 8b48d68b`00000000 ffff8380`87e9be00 880fc085`44244489 : nt!HalpMceHandlerCore+0xef ffff8380`87e9bc50 fffff800`570bb2d5 : ffffe085`0acfe450 ffff8380`87e9bef0 00000000`00000000 7402a850`478b003b : nt!HalpMceHandler+0xe0 ffff8380`87e9bc90 fffff800`570bda95 : ffffe085`0acfe450 ffc4ba50`e8cf8b48 ffc4b588`e8cf8b48 f60b8b68`24448948 : nt!HalpHandleMachineCheck+0xe9 ffff8380`87e9bcc0 fffff800`57113919 : 8b480d75`c0854850 8ce9ffc5`b482e8cf 8d41c033`45000001 242ee8c8`8b480150 : nt!HalHandleMcheck+0x35 ffff8380`87e9bcf0 fffff800`5700f57a : 0fc03345`000000b8 4de8c88b`484c50b6 8948d88b`48ffc4b6 2475c085`48782444 : nt!KiHandleMcheck+0x9 ffff8380`87e9bd20 fffff800`5700f237 : 00000000`00000000 00000000`00000000 0000016a`2ac4e130 00000000`00000000 : nt!KxMcheckAbort+0x7a ffff8380`87e9be60 00007ff8`5e76a418 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiMcheckAbort+0x277 00000024`a9f7b280 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x00007ff8`5e76a418 MODULE_NAME: AuthenticAMD IMAGE_NAME: AuthenticAMD.sys STACK_COMMAND: .process /r /p 0xffffe0851e14e340; .thread 0xffffe0851ea4d080 ; kb FAILURE_BUCKET_ID: 0x124_0_AuthenticAMD_PROCESSOR__UNKNOWN_IMAGE_AuthenticAMD.sys OS_VERSION: 10.0.19041.1 BUILDLAB_STR: vb_release OSPLATFORM_TYPE: x64 OSNAME: Windows 10 FAILURE_ID_HASH: {035dcc87-485b-74b3-1c1b-ee50cb0c2865} Followup: MachineOwner --------- PC Specs Ryen 5800x RTX 3070 GSkill DDR4 3000mhz Corsair rm850 b450 gaming x
Reply
Reply
I
Increte
03-03-2023, 11:33 PM #1

Hello, the past month I've been having issues on and off with my system either crashing with a bsod or just everything going black and restarting under load, I've never seen this happen when just browsing the net, it's always when gaming. The crashes goes away once i disable CPB which makes me think one of the cores might be screwed and i just need to rma the CPU, would like a confirmation if possible Spoiler ************* Preparing the environment for Debugger Extensions Gallery repositories ************** ExtensionRepository : Implicit UseExperimentalFeatureForNugetShare : true AllowNugetExeUpdate : true NonInteractiveNuget : true AllowNugetMSCredentialProviderInstall : true AllowParallelInitializationOfLocalRepositories : true EnableRedirectToChakraJsProvider : false -- Configuring repositories ----> Repository : LocalInstalled, Enabled: true ----> Repository : UserExtensions, Enabled: true >>>>>>>>>>>>> Preparing the environment for Debugger Extensions Gallery repositories completed, duration 0.000 seconds ************* Waiting for Debugger Extensions Gallery to Initialize ************** >>>>>>>>>>>>> Waiting for Debugger Extensions Gallery to Initialize completed, duration 0.032 seconds ----> Repository : UserExtensions, Enabled: true, Packages count: 0 ----> Repository : LocalInstalled, Enabled: true, Packages count: 42 Microsoft ® Windows Debugger Version 10.0.27725.1000 AMD64 Copyright © Microsoft Corporation. All rights reserved. Loading Dump File [C:\Windows\Minidump\110524-6406-01.dmp] Mini Kernel Dump File: Only registers and stack trace are available ************* Path validation summary ************** Response Time (ms) Location Deferred srv* Symbol search path is: srv* Executable search path is: Windows 10 Kernel Version 19041 MP (16 procs) Free x64 Product: WinNt, suite: TerminalServer SingleUserTS Personal Edition build lab: 19041.1.amd64fre.vb_release.191206-1406 Kernel base = 0xfffff803`3ca00000 PsLoadedModuleList = 0xfffff803`3d62a7c0 Debug session time: Tue Nov 5 17:34:18.047 2024 (UTC + 2:00) System Uptime: 0 days 1:06:01.669 Loading Kernel Symbols ............................................................... ................................................................ ...................................................... Loading User Symbols PEB is paged out (Peb.Ldr = 00000071`56ed5018). Type ".hh dbgerr001" for details Loading unloaded module list ....... For analysis of this file, run !analyze -v nt!KeBugCheckEx: fffff803`3cdfe310 48894c2408 mov qword ptr [rsp+8],rcx ss:ffffe700`f7cee950=0000000000000124 12: 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 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: ffff85014882b028, Address of the nt!_WHEA_ERROR_RECORD structure. Arg3: 00000000fc800800, High order 32-bits of the MCi_STATUS value. Arg4: 00000000060c0859, 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: 2359 Key : Analysis.Elapsed.mSec Value: 7844 Key : Analysis.IO.Other.Mb Value: 1 Key : Analysis.IO.Read.Mb Value: 1 Key : Analysis.IO.Write.Mb Value: 4 Key : Analysis.Init.CPU.mSec Value: 437 Key : Analysis.Init.Elapsed.mSec Value: 3199 Key : Analysis.Memory.CommitPeak.Mb Value: 95 Key : Analysis.Version.DbgEng Value: 10.0.27725.1000 Key : Analysis.Version.Description Value: 10.2408.27.01 amd64fre Key : Analysis.Version.Ext Value: 1.2408.27.1 Key : Bugcheck.Code.LegacyAPI Value: 0x124 Key : Bugcheck.Code.TargetModel Value: 0x124 Key : Failure.Bucket Value: 0x124_0_AuthenticAMD_PROCESSOR__UNKNOWN_IMAGE_AuthenticAMD.sys Key : Failure.Hash Value: {035dcc87-485b-74b3-1c1b-ee50cb0c2865} Key : WER.OS.Branch Value: vb_release Key : WER.OS.Version Value: 10.0.19041.1 BUGCHECK_CODE: 124 BUGCHECK_P1: 0 BUGCHECK_P2: ffff85014882b028 BUGCHECK_P3: fc800800 BUGCHECK_P4: 60c0859 FILE_IN_CAB: 110524-6406-01.dmp FAULTING_THREAD: ffff8501581b2080 BLACKBOXBSD: 1 (!blackboxbsd) BLACKBOXNTFS: 1 (!blackboxntfs) BLACKBOXWINLOGON: 1 CUSTOMER_CRASH_COUNT: 1 PROCESS_NAME: TL.exe STACK_TEXT: ffffe700`f7cee948 fffff803`3ceba21a : 00000000`00000124 00000000`00000000 ffff8501`4882b028 00000000`fc800800 : nt!KeBugCheckEx ffffe700`f7cee950 fffff803`38d115b0 : 00000000`00000000 ffff8501`4882b028 ffff8501`473f3cb0 ffff8501`4882b028 : nt!HalBugCheckSystem+0xca ffffe700`f7cee990 fffff803`3cfbc82d : 00000000`00000000 ffffe700`f7ceea29 ffff8501`4882b028 ffff8501`473f3cb0 : PSHED!PshedBugCheckSystem+0x10 ffffe700`f7cee9c0 fffff803`3cebbb41 : ffff8501`4d47a900 ffff8501`4d47a900 ffff8501`473f3d00 ffff8501`473f3cb0 : nt!WheaReportHwError+0x3dd ffffe700`f7ceea90 fffff803`3cebbeb3 : 00000000`0000000c ffff8501`473f3d00 ffff8501`473f3cb0 00000000`0000000c : nt!HalpMcaReportError+0xb1 ffffe700`f7ceec00 fffff803`3cebbd90 : ffff8501`45cfe8a0 00000000`00000000 ffffe700`f7ceee00 00000000`00000000 : nt!HalpMceHandlerCore+0xef ffffe700`f7ceec50 fffff803`3cebb2d5 : ffff8501`45cfe8a0 ffffe700`f7ceeef0 00000000`00000000 00000000`00000000 : nt!HalpMceHandler+0xe0 ffffe700`f7ceec90 fffff803`3cebda95 : ffff8501`45cfe8a0 00000000`00000000 00000000`00000000 00000000`00000000 : nt!HalpHandleMachineCheck+0xe9 ffffe700`f7ceecc0 fffff803`3cf13919 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!HalHandleMcheck+0x35 ffffe700`f7ceecf0 fffff803`3ce0f57a : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiHandleMcheck+0x9 ffffe700`f7ceed20 fffff803`3ce0f237 : 00000000`00000000 00000000`00000000 00000071`41b5f890 00000000`00000000 : nt!KxMcheckAbort+0x7a ffffe700`f7ceee60 00007ffb`5bf490aa : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiMcheckAbort+0x277 00000071`41b5f818 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x00007ffb`5bf490aa MODULE_NAME: AuthenticAMD IMAGE_NAME: AuthenticAMD.sys STACK_COMMAND: .process /r /p 0xffff85015d047340; .thread 0xffff8501581b2080 ; kb FAILURE_BUCKET_ID: 0x124_0_AuthenticAMD_PROCESSOR__UNKNOWN_IMAGE_AuthenticAMD.sys OS_VERSION: 10.0.19041.1 BUILDLAB_STR: vb_release OSPLATFORM_TYPE: x64 OSNAME: Windows 10 Spoiler ************* Preparing the environment for Debugger Extensions Gallery repositories ************** ExtensionRepository : Implicit UseExperimentalFeatureForNugetShare : true AllowNugetExeUpdate : true NonInteractiveNuget : true AllowNugetMSCredentialProviderInstall : true AllowParallelInitializationOfLocalRepositories : true EnableRedirectToChakraJsProvider : false -- Configuring repositories ----> Repository : LocalInstalled, Enabled: true ----> Repository : UserExtensions, Enabled: true >>>>>>>>>>>>> Preparing the environment for Debugger Extensions Gallery repositories completed, duration 0.000 seconds ************* Waiting for Debugger Extensions Gallery to Initialize ************** >>>>>>>>>>>>> Waiting for Debugger Extensions Gallery to Initialize completed, duration 0.032 seconds ----> Repository : UserExtensions, Enabled: true, Packages count: 0 ----> Repository : LocalInstalled, Enabled: true, Packages count: 42 Microsoft ® Windows Debugger Version 10.0.27725.1000 AMD64 Copyright © Microsoft Corporation. All rights reserved. Loading Dump File [C:\Windows\Minidump\110524-10125-01.dmp] Mini Kernel Dump File: Only registers and stack trace are available ************* Path validation summary ************** Response Time (ms) Location Deferred srv* Symbol search path is: srv* Executable search path is: Windows 10 Kernel Version 19041 MP (16 procs) Free x64 Product: WinNt, suite: TerminalServer SingleUserTS Personal Edition build lab: 19041.1.amd64fre.vb_release.191206-1406 Kernel base = 0xfffff800`56c00000 PsLoadedModuleList = 0xfffff800`5782a7c0 Debug session time: Tue Nov 5 22:59:28.601 2024 (UTC + 2:00) System Uptime: 0 days 0:21:58.186 Loading Kernel Symbols ............................................................... ................................................................ ...................................................... Loading User Symbols PEB is paged out (Peb.Ldr = 00000024`a8961018). Type ".hh dbgerr001" for details Loading unloaded module list ....... For analysis of this file, run !analyze -v nt!KeBugCheckEx: fffff800`56ffe310 48894c2408 mov qword ptr [rsp+8],rcx ss:ffff8380`87e9b950=0000000000000124 6: 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 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: ffffe0850d82b028, Address of the nt!_WHEA_ERROR_RECORD structure. Arg3: 00000000bc000800, High order 32-bits of the MCi_STATUS value. Arg4: 0000000001010135, 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: 2140 Key : Analysis.Elapsed.mSec Value: 3093 Key : Analysis.IO.Other.Mb Value: 0 Key : Analysis.IO.Read.Mb Value: 1 Key : Analysis.IO.Write.Mb Value: 0 Key : Analysis.Init.CPU.mSec Value: 421 Key : Analysis.Init.Elapsed.mSec Value: 2629 Key : Analysis.Memory.CommitPeak.Mb Value: 94 Key : Analysis.Version.DbgEng Value: 10.0.27725.1000 Key : Analysis.Version.Description Value: 10.2408.27.01 amd64fre Key : Analysis.Version.Ext Value: 1.2408.27.1 Key : Bugcheck.Code.LegacyAPI Value: 0x124 Key : Bugcheck.Code.TargetModel Value: 0x124 Key : Failure.Bucket Value: 0x124_0_AuthenticAMD_PROCESSOR__UNKNOWN_IMAGE_AuthenticAMD.sys Key : Failure.Hash Value: {035dcc87-485b-74b3-1c1b-ee50cb0c2865} Key : WER.OS.Branch Value: vb_release Key : WER.OS.Version Value: 10.0.19041.1 BUGCHECK_CODE: 124 BUGCHECK_P1: 0 BUGCHECK_P2: ffffe0850d82b028 BUGCHECK_P3: bc000800 BUGCHECK_P4: 1010135 FILE_IN_CAB: 110524-10125-01.dmp FAULTING_THREAD: ffffe0851ea4d080 BLACKBOXBSD: 1 (!blackboxbsd) BLACKBOXNTFS: 1 (!blackboxntfs) BLACKBOXWINLOGON: 1 CUSTOMER_CRASH_COUNT: 1 PROCESS_NAME: cs2.exe STACK_TEXT: ffff8380`87e9b948 fffff800`570ba21a : 00000000`00000124 00000000`00000000 ffffe085`0d82b028 00000000`bc000800 : nt!KeBugCheckEx ffff8380`87e9b950 fffff800`53c815b0 : 00000000`00000000 ffffe085`0d82b028 ffffe085`0afebd60 ffffe085`0d82b028 : nt!HalBugCheckSystem+0xca ffff8380`87e9b990 fffff800`571bc82d : 00000000`00000000 ffff8380`87e9ba29 ffffe085`0d82b028 ffffe085`0afebd60 : PSHED!PshedBugCheckSystem+0x10 ffff8380`87e9b9c0 fffff800`570bbb41 : ffffe085`0ae68ac0 ffffe085`0ae68ac0 ffffe085`0afebdb0 ffffe085`0afebd60 : nt!WheaReportHwError+0x3dd ffff8380`87e9ba90 fffff800`570bbeb3 : 00000000`00000006 ffffe085`0afebdb0 ffffe085`0afebd60 00000000`00000006 : nt!HalpMcaReportError+0xb1 ffff8380`87e9bc00 fffff800`570bbd90 : ffffe085`0acfe450 8b48d68b`00000000 ffff8380`87e9be00 880fc085`44244489 : nt!HalpMceHandlerCore+0xef ffff8380`87e9bc50 fffff800`570bb2d5 : ffffe085`0acfe450 ffff8380`87e9bef0 00000000`00000000 7402a850`478b003b : nt!HalpMceHandler+0xe0 ffff8380`87e9bc90 fffff800`570bda95 : ffffe085`0acfe450 ffc4ba50`e8cf8b48 ffc4b588`e8cf8b48 f60b8b68`24448948 : nt!HalpHandleMachineCheck+0xe9 ffff8380`87e9bcc0 fffff800`57113919 : 8b480d75`c0854850 8ce9ffc5`b482e8cf 8d41c033`45000001 242ee8c8`8b480150 : nt!HalHandleMcheck+0x35 ffff8380`87e9bcf0 fffff800`5700f57a : 0fc03345`000000b8 4de8c88b`484c50b6 8948d88b`48ffc4b6 2475c085`48782444 : nt!KiHandleMcheck+0x9 ffff8380`87e9bd20 fffff800`5700f237 : 00000000`00000000 00000000`00000000 0000016a`2ac4e130 00000000`00000000 : nt!KxMcheckAbort+0x7a ffff8380`87e9be60 00007ff8`5e76a418 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiMcheckAbort+0x277 00000024`a9f7b280 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x00007ff8`5e76a418 MODULE_NAME: AuthenticAMD IMAGE_NAME: AuthenticAMD.sys STACK_COMMAND: .process /r /p 0xffffe0851e14e340; .thread 0xffffe0851ea4d080 ; kb FAILURE_BUCKET_ID: 0x124_0_AuthenticAMD_PROCESSOR__UNKNOWN_IMAGE_AuthenticAMD.sys OS_VERSION: 10.0.19041.1 BUILDLAB_STR: vb_release OSPLATFORM_TYPE: x64 OSNAME: Windows 10 FAILURE_ID_HASH: {035dcc87-485b-74b3-1c1b-ee50cb0c2865} Followup: MachineOwner --------- PC Specs Ryen 5800x RTX 3070 GSkill DDR4 3000mhz Corsair rm850 b450 gaming x

Reply
Reply