Computer restarts -- probable cause AuthenticAMD

Both the The 6/25 5:41 and 11:48 PM dump have the same exact error:

Code:

===============================================================================
Section 2     : x86/x64 MCA
-------------------------------------------------------------------------------
Descriptor    @ ffffce0ee74e0148
Section       @ ffffce0ee74e02d0
Offset        : 664
Length        : 264
Flags         : 0x00000000
Severity      : Fatal

Error         : BUSLG_GENERIC_ERR_*_TIMEOUT_ERR (Proc 0 Bank 4)
  Status      : 0xf600000000070f0f
  Address     : 0x00000000ff708700
  Misc.       : 0x0000000000000000

Code:

===============================================================================
Section 2     : x86/x64 MCA
-------------------------------------------------------------------------------
Descriptor    @ ffffe10722b3ba08
Section       @ ffffe10722b3bb90
Offset        : 664
Length        : 264
Flags         : 0x00000000
Severity      : Fatal

Error         : BUSLG_GENERIC_ERR_*_TIMEOUT_ERR (Proc 0 Bank 4)
  Status      : 0xf600000000070f0f
  Address     : 0x00000000ff708700
  Misc.       : 0x0000000000000000

In neither was verifier involved:

Code:

1: kd> !verifier
fffff80317a4b200: Unable to get verifier list.

Can you post the voltage values shown in BIOS? If they are okay then it's looking like the CPU is defective (has gone bad).

Have you updated any device drivers recently? That's the one thing that can cause WHEA errors but not usually this consistent. I'll ask the other folk here to take a look at this and see what they think.

Try running the built-in diags, see what they tell you.

Resolve Hardware Issues With Built-in and Online Diagnostics (ePSA or PSA Error Codes)

When you're ready to test memory, do the following please:
===================================================
Follow this tutorial: MemTest86+ - Test RAM - Windows 10 Forums

MemTest86+ is a diagnostic tool designed to test Random Access Memory (RAM) for faults. MemTest86+ will verify that:

• RAM will accept and keep random patterns of data sent to it
• There are no errors when different parts of memory try to interact
• There are no conflicts between memory addresses

Memtest86+ runs from bootable media to isolate the RAM from the system, no other components are taken into account during the test.

   Warning

MemTest86+ needs to run for at least 8 passes to be anywhere near conclusive, anything less will not give a complete analysis of the RAM.

If you are asked to run MemTest86+ by a Ten Forums member make sure you run the full 8 passes for conclusive results. If you run less than 8 passes you will be asked to run it again.

   Note

MemTest86+ has been known to discover errors in RAM in later passes than the eighth pass. This is for information only; if you feel there is a definite problem with the RAM and 8 passes have shown no errors feel free to continue for longer.

Running 8 passes of MemTest86+ is a long and drawn out exercise and the more RAM you have the longer it will take. It's recommended to run MemTest86+ just before you go to bed and leave it overnight.

Take a picture when done and post in the forum please.

An update could have been the cause, yes. Another update could fix it. Time will tell.

Good luck.

All you had to do was to disable Fast startup.
Bus Timeout error questions are common in Answers forums and all get eventually resolved by the same.
There is a slight chance that this bug might have been fixed in 1803(not quite sure)