PC Drivers & Software

Ducktape · ‎11-01-2022

Hello!

I have an issue. My PC reboots randomly. Usually while not gaming (browsing or netflix etc).

Setup

CPU: AMD Ryzen 5 3600 - stock

Motherboard: MSI B450 Tomahawk Max

RAM: Corsair 2x8GB DDR4 3200MHz Vengeance LPX Red

GPU: SAPPHIRE Radeon RX 5700XT NITRO 8GB

PSU: FSP Dagger PRO 650W

Storage: 2xSamsung 1TB 860 QVO

OS: Windows 11 (same crash in windows 10)

I tried:

ddu

full windows reinstall

I got 2 types of error, one is whea, second is watchdog. Sometimes I got the whea sometimes i got the watchdog sometimes both.

WHEA error:

*******************************************************************************
*                                                                             *
*                        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: ffff82832fdf7020, 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: 3405

    Key  : Analysis.DebugAnalysisManager
    Value: Create

    Key  : Analysis.Elapsed.mSec
    Value: 3480

    Key  : Analysis.IO.Other.Mb
    Value: 0

    Key  : Analysis.IO.Read.Mb
    Value: 0

    Key  : Analysis.IO.Write.Mb
    Value: 0

    Key  : Analysis.Init.CPU.mSec
    Value: 436

    Key  : Analysis.Init.Elapsed.mSec
    Value: 23929

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

    Key  : Bugcheck.Code.DumpHeader
    Value: 0x124

    Key  : Bugcheck.Code.Register
    Value: 0xf1205f90

    Key  : Dump.Attributes.AsUlong
    Value: 18

    Key  : Dump.Attributes.KernelGeneratedTriageDump
    Value: 1


FILE_IN_CAB:  WHEA-20221016-1759.dmp

DUMP_FILE_ATTRIBUTES: 0x18
  Kernel Generated Triage Dump
  Live Generated Dump

BUGCHECK_CODE:  124

BUGCHECK_P1: 0

BUGCHECK_P2: ffff82832fdf7020

BUGCHECK_P3: bea00000

BUGCHECK_P4: 108

PROCESS_NAME:  smss.exe

STACK_TEXT:  
fffff480`f1205f40 fffff803`30206e8f     : ffff8283`2fdf7000 00000000`00000000 ffff8283`2fdf7020 000000fc`ef97f450 : nt!LkmdTelCreateReport+0x1e3
fffff480`f1206480 fffff803`30206d86     : ffff8283`2fdf7000 00000000`00000000 00000000`00000000 ffff8283`326de300 : nt!WheapReportLiveDump+0x7b
fffff480`f12064c0 fffff803`30056399     : 00000000`00000001 fffff480`f1206b60 00000000`00000000 00000000`0000024c : nt!WheapReportDeferredLiveDumps+0x7a
fffff480`f12064f0 fffff803`2ff4a502     : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000001 : nt!WheaCrashDumpInitializationComplete+0x59
fffff480`f1206520 fffff803`2fc2d278     : ffff8283`2ffcb580 00000000`00000000 00000000`0000022c 00000000`00000001 : nt!NtSetSystemInformation+0xa72
fffff480`f1206ae0 00007ffe`95b471f4     : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceCopyEnd+0x28
000000fc`ef97f3f8 00000000`00000000     : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x00007ffe`95b471f4


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
---------

Watchdog error:

*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

VIDEO_ENGINE_TIMEOUT_DETECTED (141)
One of the display engines failed to respond in timely fashion.
(This code can never be used for a real BugCheck.)
Arguments:
Arg1: ffff8f0553024010, Optional pointer to internal TDR recovery context (TDR_RECOVERY_CONTEXT).
Arg2: fffff805325c6680, The pointer into responsible device driver module (e.g. owner tag).
Arg3: 0000000000000000, The secondary driver specific bucketing key.
Arg4: 0000000000000000, Optional internal context dependent data.

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

Unable to load image amdkmdag.sys, Win32 error 0n2
*** WARNING: Unable to verify timestamp for amdkmdag.sys

KEY_VALUES_STRING: 1

    Key  : Analysis.CPU.mSec
    Value: 2217

    Key  : Analysis.DebugAnalysisManager
    Value: Create

    Key  : Analysis.Elapsed.mSec
    Value: 2877

    Key  : Analysis.IO.Other.Mb
    Value: 0

    Key  : Analysis.IO.Read.Mb
    Value: 0

    Key  : Analysis.IO.Write.Mb
    Value: 0

    Key  : Analysis.Init.CPU.mSec
    Value: 405

    Key  : Analysis.Init.Elapsed.mSec
    Value: 7400

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

    Key  : Bugcheck.Code.DumpHeader
    Value: 0x141

    Key  : Bugcheck.Code.Register
    Value: 0x186a0ae0

    Key  : Dump.Attributes.AsUlong
    Value: 18

    Key  : Dump.Attributes.KernelGeneratedTriageDump
    Value: 1


FILE_IN_CAB:  WATCHDOG-20221024-2231.dmp

DUMP_FILE_ATTRIBUTES: 0x18
  Kernel Generated Triage Dump
  Live Generated Dump

BUGCHECK_CODE:  141

BUGCHECK_P1: ffff8f0553024010

BUGCHECK_P2: fffff805325c6680

BUGCHECK_P3: 0

BUGCHECK_P4: 0

TAG_NOT_DEFINED_202b:  *** Unknown TAG in analysis list 202b


VIDEO_TDR_CONTEXT: dt dxgkrnl!_TDR_RECOVERY_CONTEXT ffff8f0553024010
Symbol dxgkrnl!_TDR_RECOVERY_CONTEXT not found.

PROCESS_NAME:  System

STACK_TEXT:  
ffff820d`e89a34d0 fffff805`1e655040     : ffff8f05`454c3030 ffff8f05`454c3030 ffff8f05`4f8077b0 ffff8f05`53024010 : watchdog!WdpDbgCaptureTriageDump+0xb7
ffff820d`e89a3540 fffff805`1e4d751d     : ffff8f05`53024010 ffff820d`e89a3700 00000000`00000000 00000000`00000002 : watchdog!WdDbgReportRecreate+0xf0
ffff820d`e89a35a0 fffff805`1e4d6702     : ffffd400`00000000 ffffd400`55124730 00000000`00000002 00000000`40000000 : dxgkrnl!TdrUpdateDbgReport+0x11d
ffff820d`e89a3600 fffff805`1dda9b26     : 00000000`00000001 00000000`00000001 ffff8f05`53024010 ffff8f05`4be26000 : dxgkrnl!TdrCollectDbgInfoStage1+0xa72
ffff820d`e89a3740 fffff805`1de647a1     : ffff8f05`4be26000 00000000`00000000 ffff8f05`4bcba000 ffff8f05`4be26001 : dxgmms2!VidSchiResetEngine+0x2da
ffff820d`e89a38f0 fffff805`1de36e5f     : ffff8f05`4bcba000 00000000`00000001 00000000`00000000 00000000`00000000 : dxgmms2!VidSchiResetEngines+0xb1
ffff820d`e89a3940 fffff805`1de06c3b     : 00000000`00000001 00000000`00000000 00000000`001f29af 00000000`00989680 : dxgmms2!VidSchiCheckHwProgress+0x301ef
ffff820d`e89a39c0 fffff805`1dd79b39     : ffff8f05`4bf32c00 ffff8f05`4bcba000 ffff820d`e89a3af9 00000000`00000002 : dxgmms2!VidSchiWaitForSchedulerEvents+0x37b
ffff820d`e89a3a90 fffff805`1de1e375     : ffff8f05`4523f900 ffff8f05`4bcba000 ffff8f05`4523f9b0 ffff8f05`4beb7820 : dxgmms2!VidSchiScheduleCommandToRun+0x2f9
ffff820d`e89a3b60 fffff805`1de1e32a     : ffff8f05`4bcba400 fffff805`1de1e260 ffff8f05`4bcba000 ffff8f05`49d73500 : dxgmms2!VidSchiRun_PriorityTable+0x35
ffff820d`e89a3bb0 fffff805`0d753175     : ffff8f05`49d73540 fffff805`00000001 ffff8f05`4bcba000 000f8067`b4bbbdff : dxgmms2!VidSchiWorkerThread+0xca
ffff820d`e89a3bf0 fffff805`0d81ed24     : ffffc081`65b8a180 ffff8f05`49d73540 fffff805`0d753120 00730065`006d0069 : nt!PspSystemThreadStartup+0x55
ffff820d`e89a3c40 00000000`00000000     : ffff820d`e89a4000 ffff820d`e899e000 00000000`00000000 00000000`00000000 : nt!KiStartSystemThread+0x34


SYMBOL_NAME:  amdkmdag+d6680

MODULE_NAME: amdkmdag

IMAGE_NAME:  amdkmdag.sys

STACK_COMMAND:  .cxr; .ecxr ; kb

FAILURE_BUCKET_ID:  LKD_0x141_IMAGE_amdkmdag.sys

OSPLATFORM_TYPE:  x64

OSNAME:  Windows 10

FAILURE_ID_HASH:  {48b738dd-5a92-7ff8-63d0-f075fc680fe0}

Followup:     MachineOwner
---------

DimkaTsv · ‎11-01-2022

As i understood it is recurring issue? Is there any consistent way to reproduce?
Does reboot happens every time only on low load? Or even at high load it can randomly reboot?

Is your system only built recently? If not had this problem only began to appear recently?
How frequently these unexpected reboots happens?

Currently i can only guess CPU instability while being at idle mode.

Ducktape · ‎11-01-2022

Its and old problem, almost 1 year. I don't know when it started happening. Currently it happens when:

I close a game and start browsing after that.
Watching online streaming example: Netflix etc. and closing that tab.
Doing random browsing
Under google meet meetings.

Its totally random. So I can't reproduce when I want. It just happen. Sometimes only once a week. Sometimes twice a day.

PC Drivers & Software

Random PC Reboot