Multiple BSOD Stop Codes, System File Corruption, RAM Issues

Nattle · 04 May 2023

Alright, new RAM is in (ended up with G.Skill Neo in the same speed, size, and nearly the same timings), memory problems presumably fixed but they've only been in a few hours. Can finally move on from that particular issue.

Now remaining is the system file corruption. SFC and DISM fail, details quoted below.
I do have some idea of what might be necessary to fix it, but am not confident enough to know for sure. Should I run CHKDSK? Should I install all the pending Windows updates* and try again to see if they come up all clear? Or is a repair install/in-place upgrade necessary?
Version is W10 Education 19044.1889 (Aug 2022).

*Due to the ongoing issues with the RAM that are now fixed I have been repeatedly pausing updates for 7 days since the last update.

Edit: excluding the multiple MEMORY_MANAGEMENT (1A) BSODs, the most recent BSODs I've had were:
PFN_LIST_CORRUPT (0x4E) - 23rd April
SYSTEM_SERVICE_EXCEPTION (0x3B) - 12th April
SYSTEM_THREAD_EXCEPTION_NOT_HANDLED (0x7E) - 11th April

The dumps for the other two are gone, but the one for 4e is there: image_name: ntkrnlmp.exe and

module_name: nt

, which googling suggests can be either memory or driver related. Time to check some drivers if it happens again?
My GPU driver is intentionally a little outdated (Aug 22) because it seems reliably stable for my now older GPU (1660S).

Code:

Microsoft Windows [Version 10.0.19044.1889]
(c) Microsoft Corporation. All rights reserved.

C:\Windows\system32>sfc /scannow

Beginning system scan.  This process will take some time.


Windows Resource Protection could not perform the requested operation.

C:\Windows\system32>DISM /Online /Cleanup-Image /CheckHealth

Deployment Image Servicing and Management tool
Version: 10.0.19041.844

Image Version: 10.0.19044.1889

The component store is repairable.
The operation completed successfully.

C:\Windows\system32>Dism /Online /Cleanup-Image /RestoreHealth

Deployment Image Servicing and Management tool
Version: 10.0.19041.844

Image Version: 10.0.19044.1889

[==                         3.8%                           ]
Error: 14098

The component store has been corrupted.

The DISM log file can be found at C:\Windows\Logs\DISM\dism.log

C:\Windows\system32>

ubuysa said:

The Windows memory test is far from ideal, and even Memtest86 (the recommended RAM tester) isn't perfect, but all the indications are that you have flaky RAM. I don't know how many RAM sticks you have but a good test (in fact the best RAM test) is to remove one stick for a few days and see whether it BSODs. If it doesn't then swap RAM sticks and run on the other one (assuming you have two).

BTW. Having plenty of free space on your system drive is VERY important. In addition, I never ever fill any SSD more than 50%. This allows the internal wear-levelling algorithm more leeway in balancing wear on the drive and they last much longer. You need a bigger system drive.

Thank you for the advice! I didn't bother testing the sticks individually and went with a new set. Both old and new are 2x16, but with at least one failing so obviously that WMD picked it up I figured I may as well just replace both.

I did some more intensive cleanup over the last couple weeks and now have 173GB free, but with 40GB or so worth of pending updates on pause it's closer to 220. So ~18% of the drive free is an improvement!
I intend to get another drive with the refund from the faulty RAM, probably just an external for now. I'll be moving about 200GB off of my system drive onto that and making rolling backups and saving large projects onto it, leaving about half of C:/ empty. System drive is a SATA (MX500) so eventually I'd like to put the M.2 slot to use.