Looks like I posted in the wrong thread, my apologies. Your all okay. Sorry to make you waste your time.
Now I need to find the thread my post belonged in.
I looked at both dumps and they show WHEA 124 errors.
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: !errrec , Address of the WHEA_ERROR_RECORD structure.
Arg3: 00000000ba000000, High order 32-bits of the MCi_STATUS value.
Arg4: 0000000081000402, Low order 32-bits of the MCi_STATUS value.
Getting Symbol errors which makes some of the info less than helpful:
Code:
*************************************************************************
*** ***
*** ***
*** 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 ***
*** ***
*************************************************************************
Code:
1: kd> !errrec ffffe38b07274028
===============================================================================
Common Platform Error Record @ ffffe38b07274028
-------------------------------------------------------------------------------
Record Id : 01d6ab5c3f0f7f9b
Severity : Fatal (1)
Length : 936
Creator : Microsoft
Notify Type : Machine Check Exception
Timestamp : 10/26/2020 7:32:44 (UTC)
Flags : 0x00000000
===============================================================================
Section 0 : Processor Generic
-------------------------------------------------------------------------------
Descriptor @ ffffe38b072740a8
Section @ ffffe38b07274180
Offset : 344
Length : 192
Flags : 0x00000001 Primary
Severity : Fatal
Descriptor @ ffffe38b072740f0
Section @ ffffe38b07274240
Offset : 536
Length : 128
Flags : 0x00000000
Severity : Fatal
===============================================================================
Section 2 : x86/x64 MCA
-------------------------------------------------------------------------------
Descriptor @ ffffe38b07274138
Section @ ffffe38b072742c0
Offset : 664
Length : 272
Flags : 0x00000000
Severity : Fatal
Error : Unknown (Proc 0 Bank 0)
Status : 0x0000000000000000
Cause
This bug check is typically related to physical hardware failures. It can be heat related, defective hardware, memory or even a processor that is beginning to fail or has failed. If over-clocking has been enabled, try disabling it. Confirm that any cooling systems such as fans are functional. Run system diagnostics to confirm that the system memory is not defective. It is less likely, but possible that a driver is causing the hardware to fail with this bug check.
Check temperatures in BIOS then install a program like HWINFO to monitor temps while using the system.
Do the following as time permits:
===================================================
Follow this tutorial to stress test your CPU:
Prime95 - Stress Test Your CPU - Windows 10 Forums
OCCT: OCBASE / OCCT
For both the above, read the instructions carefully and watch your system when testing.
If it starts spitting out problems and you can't shut it down - simply turn the system off/unplug it from the wall
For Intel CPUs (32 and 64 bit): Intel® Processor Diagnostic Tool
The purpose of the Intel® Processor Diagnostic Tool is to verify the functionality of an Intel® microprocessor. The diagnostic tool checks for brand identification, verifies the processor operating frequency, tests specific processor features, and performs a stress test on the processor.
===================================================
Follow this tutorials to stress test your GPU:
FurMark - GPU Stress Test - Windows 10 Forums
If you have a AMD APU instead of a discreet GPU, try UNIGINE 3D Benchmark..
===================================================
Up through DDR3, follow this tutorial: MemTest86+ - Test RAM - Windows 10 Forums
DDR4, follow this tutorial: MemTest86 v8.1 Free Memory Testing Tool Review
Both of these are diagnostic tools designed to test Random Access Memory (RAM) for faults. They 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
They run from bootable media to isolate the RAM from the system, no other components are taken into account during the test.
Warning
MemTest86+ and Memtest86 need to run for at least 8 passes to be anywhere near conclusive, anything less will not give a complete analysis of the RAM. The new version of Memtest86 only allows 4 passes for the free version so run it twice, back to back.
If you are asked to run MemTest86+ or Memtest86 by a Ten Forums member make sure you run the full 8 (or 4+4) passes for conclusive results. If you run less than 8 passes you will be asked to run it again.
Note
Both of these diagnostics 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+ or 4+4 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 it overnight, starting just before you go to bed and leave it overnight.
Take a picture when done and post in the forum please.
Read the instructions carefully and watch your system when testing.
If it starts spitting out problems and you can't shut it down - simply turn the system off/unplug it from the wall
===================================================
Diagnostics Test 
HDD TEST
Run HDTune to
- check the health,
- scan for errors, not quick scan but full scan
- run a benchmark.
Run CrystalDiskInfo Portable and CrystalDiskMark Portable to
- Check health of drive
- Check performance of drive
Run SeaGate SeaTools for Windows (test ALL hard drives - HDD/SSD/USB/etc)
You can also try the various options available with chkdsk.
===================================================
Run Driver Verifier
Driver Verifier-- tracking down a mis-behaving driver.
Following the instructions in the above link will check for problems in all non-Microsoft drivers.
What we're looking for is a verifier generated BSOD with a mini dump that will tell us what driver caused it. If you get a BSOD, rerun the V2 log collector as soon as possible and upload the resulting zip file. Also see if there is a new C:\Windows \MEMORY.DMP file. If there is, copy it to another location then zip it an upload to a file sharing site like OneDrive and post a link to it here.
To check if verifier is active, open a Command Prompt and enter:
verifier /query
If not active it will respond with
No drivers are currently verified.
Follow instructions here to decide which drivers you want to test. 3-5 is a good start. Add 3-5 more every two hours until all are selected or you get a BSOD.
Enable and Disable Driver Verifier in Windows 10
Familiarize yourself with how to get out of Driver verifier from the above link and from the first link.
Quote