Repeated Crashes and Boot Errors Apparently Caused by Driver Updates

The bugchecks are all WHEA 0x124 which are typically caused by malfunctioning hardware.
There were only 2 dump files:
The uncorrrectable WHEA started on 5/2/2018.
The second occurred on 6/30/2018

The RAM modules are mismatched and problems with mismatched RAM may not be found running the tests.

The major hardware components will be checked: CPU, GPU, Drive, RAM.

Some steps had been performed at an earlier time however these will be all fresh tests.
The RAM/DIMM/MB testing with Memtest86+ version 5.01 and the HD Tune full error scan can each be run overnight.
The CPU and GPU testing are interactive with the end user monitoring for problems and aborting the stress testing as needed.

1) Open administrative command prompt and type or copy and paste:
2) sfc /scannow
3) dism /online /cleanup-image /restorehealth
4) chkdsk /scan
5) When these have completed > right click on the top bar or title bar of the administrative command prompt box > left click on edit then select all > right click on the top bar again > left click on edit then copy > paste into the thread

6) Make sure that there is no over clocking while troubleshooting.

7) Sometimes there are problems in the bios that produce bsod.
The BIOS: BIOS Version/Date American Megatrends Inc. X555DA.517, 11/20/2015
8) Please check to see if this is the most up to date version.

9) Open the website for the computer or motherboard manufacturer to view the drivers and post a URL or hyperlink into the thread.

10) To ensure that there are no improper bios settings please reset the bios.
11) Sometimes there can be failure to boot after resetting the bios.

12) Backup the computer files to another drive or to the cloud.

13) Make a fresh backup image using Macrium:
Macrium Software | Macrium Reflect Free:
Macrium Software | Macrium Reflect Free

14) And please create a brand new restore point.

How to Clear Your Computers CMOS to Reset BIOS Settings:
How to Clear Your Computers CMOS to Reset BIOS Settings
3 Ways to Reset Your BIOS - wikiHow:
3 Ways to Reset Your BIOS - wikiHow

15) Open Ccleaner > click windows tab > scroll down to system and advanced > post an image into the thread

16) In the left lower corner search type: system or system control > open system control panel > on the left pane click advanced system settings
a) > on the advanced tab under startup and recovery > click settings > post an image of the startup and recovery into the thread.
b) > on the advanced tab under performance > click on settings > under performance options > click on the advanced tab > under virtual memory > click on change > post an image of the virtual memory tab into the thread

Once the bios is reset and there is no overclocking:

17) Choose one of the temperature monitoring software applications: Speecy, HW monitor, Speed fan:
Speccy - Free Download - Piriform: Speccy - System Information - Free
Download Speccy | Find your computer specs, free!
HWMONITOR | Softwares | CPUID: HWMONITOR | Softwares | CPUID
HWMONITOR | Softwares | CPUID
SpeedFan - Access temperature sensor in your computer: SpeedFan - Access temperature sensor in your computer
SpeedFan - Access temperature sensor in your computer

18) Run Prime95 - Stress Test Your CPU
Prime95 - Stress Test Your CPU Windows 10 Performance Maintenance Tutorials
Prime95 - Stress Test Your CPU | Windows 10 Tutorials
a) Record the maximum temperature and post the maximum temperature into the thread
b) Record test duration and post the uninterrupted test duration into the thread
c) Aim for testing > 3 hrs and abort testing as needed for freezing, temperature changes (see link)
d) Use the Microsoft snipping tool to post images into the thread.
Take Screenshot in Windows 10 Windows 10 General Tips Tutorials
Take Screenshot in Windows 10 | Windows 10 Tutorials

19) Run memtest86+ version 5.01 for at least 8 passes.
Memtest86+ - Advanced Memory Diagnostic Tool
This may take hours so plan to run it overnight.
a) Please make sure you use the Memtest86+ version 5.01 with the link below.
Memtest86+ - Advanced Memory Diagnostic Tool
The testing is done not by time but by passes.
The more passes the better.
There are a significant number of false negatives if fewer than 8 passes are made.
A false negative is a test pass when there is malfunctioning RAM.
There is 8 GB of RAM on the computer.
Memtest86+ version 5.01 testing takes approximately 1 - 2 hours /GB RAM
Just 1 error is a fail and you can abort testing.
Then test 1 RAM module at a time in the same DIMM each for 8 or more passes.
b) When Memtest86+ version 5.01 has completed 8 or more passes use a camera or smart phone camera to take a picture and post an image into the thread.
Memory problems. - Microsoft Community
MemTest86+ - Test RAM | Windows 10 Tutorials

20) Run HD Tune: (free or trial edition)
Post images of the test results on these tabs:
a) Health (SMART)
b) Benchmark
c) Full error scan
Take Screenshot in Windows 10 Windows 10 General Tips Tutorials
Take Screenshot in Windows 10 | Windows 10 Tutorials

21) Run FurMark - GPU Stress Test Windows 10 Performance Maintenance Tutorials
FurMark - GPU Stress Test Windows 10 Performance Maintenance Tutorials:
FurMark - GPU Stress Test | Windows 10 Tutorials
Please make note of the importance of temperature monitoring and aborting the test in the GPU link.
a) Record the maximum temperature and post the maximum temperature into the thread.
b) Record the test duration and post the uninterrupted test duration into the thread.
c) Aim for testing 1 hour.
d) Use the Microsoft snipping tool to post images into the thread.
Take Screenshot in Windows 10 Windows 10 General Tips Tutorials
Take Screenshot in Windows 10 | Windows 10 Tutorials

22) All of these test should be done with the bios reset and no over clocking.

23) For each of the above tests please record maximum temperatures.

24) And please make sure that you use the Microsoft snipping tool to post images of each into the thread.
Take Screenshot in Windows 10 Windows 10 General Tips Tutorials

25) Open administrative command prompt and type or copy and paste: chkdsk /x /f /r /v
C:\Windows\system32>chkdsk /x /f /r /v
The type of the file system is NTFS.
Cannot lock current drive.

Chkdsk cannot run because the volume is in use by another
process. Would you like to schedule this volume to be
checked the next time the system restarts? (Y/N)

Type: Y
reboot

This may take many hours to run so plan to run it overnight.

26) Use the information in this link to find the chkdsk report in the event viewer.
Copy and paste into notepad > save to desktop > post into the thread using one drive or drop box share link:
Read Chkdsk Log in Event Viewer in Windows 10 Windows 10 Performance Maintenance Tutorials
Read Chkdsk Log in Event Viewer in Windows 10 | Windows 10 Tutorials

27) Whenever there is a BSOD please run the BETA log collector and post a new zip into the thread. Also if a memory.dmp is found please zip > upload to one drive or drop box > post a share link into the thread

Code:

5/2/2018 8:59 AM    Windows Error Reporting    Fault bucket , type 0
Event Name: BlueScreen
Response: Not available
Cab Id: 0

Problem signature:
P1: 124
P2: 0
P3: ffffcf0cb8a998f8
P4: 0
P5: 0
P6: 10_0_15063
P7: 0_0
P8: 768_1
P9: 
P10: 

Attached files:
\\?\C:\windows\Minidump\050218-48656-01.dmp
\\?\C:\windows\TEMP\WER-177250-0.sysdata.xml
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER110F.tmp.WERInternalMetadata.xml
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER1130.tmp.csv
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER118E.tmp.txt

These files may be available here:
C:\ProgramData\Microsoft\Windows\WER\ReportQueue\Kernel_124_237e716332da02f73e3836eda2b863deb6ae418_00000000_03a111ba

Analysis symbol: 
Rechecking for solution: 0
Report Id: 3bed0bbe-d3f5-492e-86bb-feeaf75be431
Report Status: 4
Hashed bucket:
5/2/2018 9:01 AM    Windows Error Reporting    Fault bucket , type 0
Event Name: BlueScreen
Response: Not available
Cab Id: 0

Problem signature:
P1: 124
P2: 0
P3: ffffcf0cb8a998f8
P4: 0
P5: 0
P6: 10_0_15063
P7: 0_0
P8: 768_1
P9: 
P10: 

Attached files:
\\?\C:\windows\Minidump\050218-48656-01.dmp
\\?\C:\windows\TEMP\WER-177250-0.sysdata.xml
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER110F.tmp.WERInternalMetadata.xml
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER1130.tmp.csv
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER118E.tmp.txt

These files may be available here:
C:\ProgramData\Microsoft\Windows\WER\ReportArchive\Kernel_124_237e716332da02f73e3836eda2b863deb6ae418_00000000_cab_07be714a

Analysis symbol: 
Rechecking for solution: 0
Report Id: 3bed0bbe-d3f5-492e-86bb-feeaf75be431
Report Status: 2049
Hashed bucket:
6/30/2018 7:26 PM    Windows Error Reporting    Fault bucket , type 0
Event Name: BlueScreen
Response: Not available
Cab Id: 0

Problem signature:
P1: 124
P2: 0
P3: ffffbe08741f1038
P4: 0
P5: 0
P6: 10_0_15063
P7: 0_0
P8: 768_1
P9: 
P10: 

Attached files:
\\?\C:\windows\Minidump\063018-29187-01.dmp
\\?\C:\windows\TEMP\WER-35968-0.sysdata.xml
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER25A1.tmp.WERInternalMetadata.xml
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER260F.tmp.csv
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER26AD.tmp.txt

These files may be available here:
C:\ProgramData\Microsoft\Windows\WER\ReportQueue\Kernel_124_1d59daf8bf55e59c50ec6ec097346f338ada703_00000000_03ad26b9

Analysis symbol: 
Rechecking for solution: 0
Report Id: 0a200c0e-122d-4eb2-a416-842289efd81f
Report Status: 4
Hashed bucket:
6/30/2018 7:39 PM    Windows Error Reporting    Fault bucket , type 0
Event Name: BlueScreen
Response: Not available
Cab Id: 0

Problem signature:
P1: 124
P2: 0
P3: ffffbe08741f1038
P4: 0
P5: 0
P6: 10_0_15063
P7: 0_0
P8: 768_1
P9: 
P10: 

Attached files:
\\?\C:\windows\Minidump\063018-29187-01.dmp
\\?\C:\windows\TEMP\WER-35968-0.sysdata.xml
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER25A1.tmp.WERInternalMetadata.xml
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER260F.tmp.csv
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER26AD.tmp.txt

These files may be available here:
C:\ProgramData\Microsoft\Windows\WER\ReportArchive\Kernel_124_1d59daf8bf55e59c50ec6ec097346f338ada703_00000000_cab_41d51877

Analysis symbol: 
Rechecking for solution: 0
Report Id: 0a200c0e-122d-4eb2-a416-842289efd81f
Report Status: 2051
Hashed bucket:

Code:

Event[2288]:
  Log Name: System
  Source: Microsoft-Windows-WHEA-Logger
  Date: 2018-06-30T14:21:42.795
  Event ID: 20
  Task: N/A
  Level: Error
  Opcode: Info
  Keyword: N/A
  User: S-1-5-19
  User Name: NT AUTHORITY\LOCAL SERVICE
  Computer: DESKTOP-H2C94OF
  Description: 
A fatal hardware error has occurred.

Component: AMD Northbridge
Error Source: Machine Check Exception
Error Type: HyperTransport Watchdog Timeout Error
Processor APIC ID: 0

The details view of this entry contains further information.

Code:

Event[399]:
  Log Name: System
  Source: Application Popup
  Date: 2018-06-08T15:07:02.018
  Event ID: 26
  Task: N/A
  Level: Information
  Opcode: Info
  Keyword: N/A
  User: S-1-5-18
  User Name: NT AUTHORITY\SYSTEM
  Computer: DESKTOP-H2C94OF
  Description: 
Application popup: Windows - Out of Virtual Memory : Your system is low on virtual memory. To ensure that Windows runs properly, increase the size of your virtual memory paging file. For more information, see Help.

Code:

Event[2013]:
  Log Name: System
  Source: Disk
  Date: 2018-06-28T22:07:49.610
  Event ID: 11
  Task: N/A
  Level: Error
  Opcode: N/A
  Keyword: Classic
  User: N/A
  User Name: N/A
  Computer: DESKTOP-H2C94OF
  Description: 
The driver detected a controller error on \Device\Harddisk1\DR41.

Code:

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.
Arguments:
Arg1: 0000000000000000, Machine Check Exception
Arg2: ffffbe08741f1038, Address of the WHEA_ERROR_RECORD structure.
Arg3: 0000000000000000, High order 32-bits of the MCi_STATUS value.
Arg4: 0000000000000000, Low order 32-bits of the MCi_STATUS value.

Code:

Common Platform Error Record @ ffffcf0cb8a998f8-------------------------------------------------------------------------------
Record Id     : 01d3e1f32cad73a3
Severity      : Fatal (1)
Length        : 928
Creator       : Microsoft
Notify Type   : Machine Check Exception
Timestamp     : 5/2/2018 8:54:42 (UTC)
Flags         : 0x00000002 PreviousError


===============================================================================
Section 0     : Processor Generic
-------------------------------------------------------------------------------
Descriptor    @ ffffcf0cb8a99978
Section       @ ffffcf0cb8a99a50
Offset        : 344
Length        : 192
Flags         : 0x00000001 Primary
Severity      : Fatal


Proc. Type    : x86/x64
Instr. Set    : x64
Error Type    : BUS error
Operation     : Generic
Flags         : 0x00
Level         : 3
CPU Version   : 0x0000000000660f01
Processor ID  : 0x0000000000000000


===============================================================================
Section 1     : x86/x64 Processor Specific
-------------------------------------------------------------------------------
Descriptor    @ ffffcf0cb8a999c0
Section       @ ffffcf0cb8a99b10
Offset        : 536
Length        : 128
Flags         : 0x00000000
Severity      : Fatal


Local APIC Id : 0x0000000000000000
CPU Id        : 01 0f 66 00 00 08 04 00 - 0b 32 d8 7e ff fb 8b 17
                00 00 00 00 00 00 00 00 - 00 00 00 00 00 00 00 00
                00 00 00 00 00 00 00 00 - 00 00 00 00 00 00 00 00


Proc. Info 0  @ ffffcf0cb8a99b10


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


Error         : BUSLG_GENERIC_ERR_*_TIMEOUT_ERR (Proc 0 Bank 4)
  Status      : 0xfe00000000070f0f
  Address     : 0x00000000000200b0
  Misc.       : 0xd00a0fff01000000