Hello, and welcome to the forum!
One BSOD is a 0x133 DPC_WATCHDOG_VIOLATION that may have been caused by your Nvidia graphics driver (or the graphics card itself). The version of nvlddmkm.sys (the Nvidia graphics driver) that you have installed is old, dating from 2020...
Code:
0: kd> lmvm nvlddmkm
Browse full module list
start end module name
fffff806`4c8a0000 fffff806`4e813000 nvlddmkm T (no symbols)
Loaded symbol image file: nvlddmkm.sys
Image path: \SystemRoot\System32\DriverStore\FileRepository\nv_dispi.inf_amd64_1c83a5d7cffd7bff\nvlddmkm.sys
Image name: nvlddmkm.sys
Browse all global symbols functions data
Timestamp: Thu Oct 1 07:08:42 2020 (5F75564A)
CheckSum: 01F01EC5
ImageSize: 01F73000
Translations: 0000.04b0 0000.04e4 0409.04b0 0409.04e4
Information from resource tables:
That may well be the driver version available from your motherboard vendor's website but for a desktop card you should be using the
Nvidia driver download site and install the latest driver from there (it's dated 27th June 2024). It's possible that this may be the source of all your problems, so do this first and then see how things go.
The other four dumps are all 0x123 WHEA_UNCORRECTABLE_ERROR bugchecks, as you might imagine these are typically caused by a hardware failure, although they can sometimes be caused by a bad driver. All of the dumps show the same failure bucket...
Code:
FAILURE_BUCKET_ID: 0x124_0_AuthenticAMD_MEMORY__UNKNOWN_FATAL_IMAGE_AuthenticAMD.sys
These suggest that the failing hardware may well be either RAM or possibly the CPU. Evidence from your System and Application logs makes me think that bad RAM is more likely, I can see a couple of WHEA errors in your System log...
Code:
Log Name: System
Source: Microsoft-Windows-WHEA-Logger
Date: 18/06/2024 22:34:34
Event ID: 18
Task Category: None
Level: Error
Keywords:
User: LOCAL SERVICE
Computer: AMD
Description:
A fatal hardware error has occurred.
Reported by component: Processor Core
Error Source: Machine Check Exception
Error Type: Cache Hierarchy Error
Processor APIC ID: 8
The details view of this entry contains further information.
The Cache Hierarchy Error type reported there could be bad RAM or the CPU cache, but in your Application log there are a fair number of Application errors with 0xC0000005 exception codes, this is an invalid memory access exception. These could also be CPU of course, but bad RAM is more likely and it's easier to test.
I can see that you have 32GB or RAM in two 16GB sticks. You could run Memtest86 over that RAM - the Windows memory tester is not very thorough at all - but that will take a long time and you won't be able to use the PC whilst Memtest86 is running. A better, and far more reliable, RAM test is to remove one stick of RAM and run on just the one 16GB stick for a few days (or until you get a BSOD). Check with you motherboard manual that the one stick is in the correct slot (typically A2). After a few days (or a BSOD) swap the RAM sticks over and run on just the other 16GB stick for a few days (or until you get a BSOD).
If it BSODs on one stick but not the other then you've located the problem. If it BSODs on both sticks then it's unlikely to be a RAM problem and we'll then talk about testing the CPU.
