Another BSOD inquiry

You’re going to need to go the BSOD section, read the instructions, and use one of the two collectors to get help.
BSOD - Posting Instructions

BSOD - Posting Instructions

Update Windows 10 to version 1909 - https://support.microsoft.com/en-gb/...date-assistant
Test your CPU with Prime95, OCCT and Intel Processor Diagnostic Tool - Prime95 - Stress Test Your CPU OCCT With Four Options - How We Stress Test CPUs Intel CPU - Diagnose - Windows 7 Help Forums

Please update you computer specs under My Computer. Some of what's there now is wrong. Add as many details as you can.

How to fill out System Specs for tenforums.

See here: System Specs - Fill in at Ten Forums

Fill out as much as you can, especially the Manufacture and full model number of the computer if purchased or the system board if custom built.

Dump for 3/4 7:30PM shows:

Code:

5: kd> !errrec ffff8082da1d7028
===============================================================================
Common Platform Error Record @ ffff8082da1d7028
-------------------------------------------------------------------------------
Record Id     : 01d5f1b7fc25298e
Severity      : Fatal (1)
Length        : 936
Creator       : Microsoft
Notify Type   : Machine Check Exception
Timestamp     : 3/5/2020 1:29:21 (UTC)
Flags         : 0x00000000

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

Proc. Type    : x86/x64
Instr. Set    : x64
Error Type    : Cache error
Operation     : Generic
Flags         : 0x00
Level         : 0
CPU Version   : 0x00000000000306c3
Processor ID  : 0x0000000000000005

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

Local APIC Id : 0x0000000000000005
CPU Id        : c3 06 03 00 00 08 10 05 - bf fb fa 7f ff fb eb bf
                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  @ ffff8082da1d7240

===============================================================================
Section 2     : x86/x64 MCA
-------------------------------------------------------------------------------
Descriptor    @ ffff8082da1d7138
Section       @ ffff8082da1d72c0
Offset        : 664
Length        : 272
Flags         : 0x00000000
Severity      : Fatal

Error         : DCACHEL0_WR_ERR (Proc 5 Bank 1)
  Status      : 0xbf80000000000124
  Address     : 0x00000001688ef8c0
  Misc.       : 0x0000000000000086

Dumps for 2/23 3:08PM, 3/8 7:51PM, 3/8 7:10PM, 3/9 9:13PM dumps show:

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: ffffac854079c028, Address of the WHEA_ERROR_RECORD structure.
Arg3: 00000000bf800000, High order 32-bits of the MCi_STATUS value.
Arg4: 0000000000000124, Low order 32-bits of the MCi_STATUS value.

Code:

!errrec ffffac854079c028
===============================================================================
Common Platform Error Record @ ffffac854079c028
-------------------------------------------------------------------------------
Record Id     : 01d5f60bdb282ab3
Severity      : Fatal (1)
Length        : 936
Creator       : Microsoft
Notify Type   : Machine Check Exception
Timestamp     : 3/10/2020 1:10:32 (UTC)
Flags         : 0x00000000

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

Proc. Type    : x86/x64
Instr. Set    : x64
Error Type    : Cache error
Operation     : Generic
Flags         : 0x00
Level         : 0
CPU Version   : 0x00000000000306c3
Processor ID  : 0x0000000000000004

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

Local APIC Id : 0x0000000000000004
CPU Id        : c3 06 03 00 00 08 10 04 - bf fb fa 7f ff fb eb bf
                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  @ ffffac854079c240

===============================================================================
Section 2     : x86/x64 MCA
-------------------------------------------------------------------------------
Descriptor    @ ffffac854079c138
Section       @ ffffac854079c2c0
Offset        : 664
Length        : 272
Flags         : 0x00000000
Severity      : Fatal

Error         : DCACHEL0_WR_ERR (Proc 4 Bank 1)
  Status      : 0xbf80000000000124
  Address     : 0x00000003cb1bd380
  Misc.       : 0x0000000000000086

This is usually caused by a defective CPU but can be caused by a bad driver. Since this happens pretty seldom it's going to be hard to debug.
Start by checking temps of CPU, GPU, RAM, and anything else the mother board makes available. Try HWInfo or SpeedFan, see what it shows you about temps: HWInfo ..... SpeedFan

Overclocking:
If you are overclocking, set all the hardware components to their defaults.

Test RAM:
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.


Stress test the Graphics Card using Furmark.
FurMark - GPU Stress Test
Take a screenshot of the furmark window before closing it. Upload the screenshot for us. Also let us know if you have experienced any crash/BSOD and/or artifacts during the test.

Stress test the CPU.
Prime95 - Stress Test Your CPU
It saves the result as a .txt file in the prime95's folder. Upload the file for us.

Capture screen shots or take pictures of any errors and post in your thread:

Screenshots and Files - Upload and Post in Ten Forums - Windows 10 Forums

Some additional steps would be to run in Safe Mode for awhile and see if the problem still occurs.
Can also try using Clean Boot: How to Perform a Clean Boot in Windows 10 to Troubleshoot Software Conflicts
Lastly try 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 Google, Mega or 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.

If you have questions, see this additional tutorial which may help to clear things up.

Enable and Disable Driver Verifier in Windows 10

Need a reproducible scenario to try these.

It may come down to the CPU. How old is it? Is it still under warranty? If yes then you could RMA (Return Merchandise Authorization) it and try a new one.

One more thing and maybe the first you should try:

Download Intel(R) Processor Diagnostic Tool