Random crashes, pc becomes unresponsive, lots of 122 and 131 errors

Hello,
For the past couple of days my desktop pc has been having completely random lockups, it becomes unresponsive and always requires a hard reset. The odd time during boot up it will freeze up at the MSI mobo screen and requires another reset. The event viewer shows piles of 122 and 131 event ID errors, I'm not sure if they are related to the crashes but I am assuming they are. I have done a full scan with Malwarebytes which turned up nothing, I've also done a few system scans with sfc /scannow and they all turned up nothing as well. I have tried uninstalling the gpu driver with DDU and then installing the latest driver from Nvidia. I used Samsung Magician to do a diagnostic scan of the boot drive and it found no problems. System temps are all normal, and I have not noticed any specific issues with any of the hardware components. The couple of things that I have tried so far have not worked and I'm almost to the point of doing a fresh OS install though I would prefer not to and I am hoping someone here can offer an alternative solution or fix. TIA

Win10 22H2 build 19045.3693

https://drive.google.com/file/d/160o...usp=drive_link

Please make sure that links do not require sign in:

Share OneDrive files and folders - Microsoft Support
How to use Google Drive - Computer - Google Drive Help

zbook said:

Please make sure that links do not require sign in:

Share OneDrive files and folders - Microsoft Support
How to use Google Drive - Computer - Google Drive Help

Sorry about that. Hopefully this link will work now.
RYZEN5950X-(2023-12-06_08-57-27).zip - Google Drive

I also want to add that I just had a DPC_Watchdog_Violation BSOD. It is the second one that I've had in the past few days. Most of the time the pc just instantly freezes up and requires a hard reset without a BSOD.

Edit - The system locked up about 30 seconds after I posted the reply. So frustrating!

Can you please upload the full kernel dump? It's the file C:\Windows\Memory.dmp. This particular bugcheck can only be properly diagnosed with the full kernel dump. Both BSODs happened because a collection of DPCs (the back-end of device interrupt processing) ran for too long. The minidump only contains status for the failing processor and we need to see all processors - hence we need the full kernel dump.

That said, both of your BSODs happened during a read/write of an NVMe storage drive. We see the Windows drivers ntfs.sys. storport.sys, and stornvme.sys called in the lead up to the bugcheck. This might be a Red Herring since we can only see one processor in the minidump, but M.2 drives do cause niggly issues if they are not properly seated. Try removing the (all) NVMe drives and reseating them. It's most likely the system drive that's the problem, but if you have several NVMe drives then reseat them all.

We'll be able to tell you in detail why this BSOD happened once we have the full kernel dump.

I just updated the nvme driver and in device manager it now shows Samsung NVMe Controller. Since doing that however, my seagate hdds are constantly clicking like they are stuck in seek mode. WTH?

This system is at least 2 years old, it's watercooled with hard tubing so reseating the nvme drives will be a pita and will require a system teardown. I am in the process of uploading the memory.dmp file you requested but it is quite large and will take a bit.

Edit - I forgot to mention that Samsung Magician shows no issues with either of the nvme drives. I have done multiple diagnostic scans on both drives with the magician software and no problems have been found. Both drives are identical samsung 1TB 970 evo with 2B2QEXM7 firmware, one is used for the windows boot drive and the other is only for games.

MEMORY.DMP - Google Drive

- - - Updated - - -

Since my last post the computer froze up again. This time on restart I went into the bios and MSI has a self test feature for nvme drives. I ran the test on both of the samsung evo drives and no issues were found.

I did manage to figure out what was causing the seagate hdd's to constantly click and seek. I use a program called HWinfo64 mainly to monitor system temps. As soon as I shut it down the hdd's stopped making noise.

Today is 12/07/23.

The log files start on 12/06/2023.

Was there a very recent in place upgrade repair?

Were the log files cleaned?

When were these RAM modules installed: F4-3600C16-16GTZR
Had you seen them on the Qualified Vendor List (QVL)?


1) Run Tuneup plus > post a share link

https://www.tenforums.com/attachment...p_plus_log.bat

Batch files for use in BSOD debugging



2) The BIOS Version/Date American Megatrends International, LLC. 1.90, 3/18/2022

Upgrade the BIOS: 1.90 > 1F

MAG X570 TOMAHAWK WIFI | RETURN TO HONOR

zbook said:

Today is 12/07/23.

The log files start on 12/06/2023.

Was there a very recent in place upgrade repair?

Were the log files cleaned?

When were these RAM modules installed: F4-3600C16-16GTZR
Had you seen them on the Qualified Vendor List (QVL)?


1) Run Tuneup plus > post a share link

https://www.tenforums.com/attachment...p_plus_log.bat

Batch files for use in BSOD debugging



2) The BIOS Version/Date American Megatrends International, LLC. 1.90, 3/18/2022

Upgrade the BIOS: 1.90 > 1F

MAG X570 TOMAHAWK WIFI | RETURN TO HONOR

I built the system in May 2021 and has been running with no issues until a few days ago. The last upgrade I did was the 3080 graphics card and it was installed in July 2022. There have been no hardware upgrades since then. Earlier today I installed the latest chipset drivers on the MSI site. I've had 3 crashes since, the latest was just a few minutes ago while typing out this reply. I will update the BIOS and see if that helps.

Tuneup.log - Google Drive

How come the log files are only 1 day?

Was there a very recent in place upgrade repair?

Were the log files cleaned?


Please make sure that Windows cleanup and third party software are not used during the troubleshooting.


Once there are many log entries they can be scanned.



Since there are DISM errors and few files to scan please perform an in place upgrade repair while in clean boot.

Repair Install Windows 10 with an In-place Upgrade

Perform a Clean Boot in Windows 10 to Troubleshoot Software Conflicts

Code:

Error: 0x800f081f

The source files could not be found.