Daily BSOD. Trying to Determine if Bad RAM, SSD, Motherboard, or Other

For a few weeks now i've been getting almost daily BSOD's, with many different errors given, though Memory Management seems to be the most common.

At the same time I was also starting to get a scan and repair of the C drive every time I had to restart the computer. That has since gone away but it was constant until I reinstalled Windows.

I don't know if any of the following is related but this did all start happening around the same time as the BSOD's and disk scans, so i'll mention it just in case:
I started getting errors for Riot Games' Vanguard anti-cheat software and rejecting audio drivers. The game Valorant crashed a lot the last time i tried playing.
Firefox and Edge both frequently crash on me now. Its either individual tabs or the whole browser. Neither is consistent though.

I have two 16GB RAM sticks and have tested both individually in the same slot and separate slots. Both sticks have failed tests. Neither is running at its full speed of 3600.

What I have tried for BSOD and C drive scan and repair:

• Updated Windows.
• Updated all drivers.
• Virus scan.
• Ran Windows Memory Diagnostics. Reported errors almost immediately.
• Ran Memtest64. Immediately fails the test
• Ran Memtest86 off USB booting straight from BIOS. Immediately fails the test.
• Reset BIOS to default.
• Cleared CMOS by shorting pins.
• Cleared CMOS by removing battery
• Updated BIOS to newest non beta version available to ver 4408
• In Command Shell ran: run chkdsk c: /f and then chkdsk c: /v /scan /forceofflinefix
  After running force offline fix I would go through and manually delete all the flagged files. That seemed to take care of the disk scanning.
• Clean reinstall of Windows 10 (got 3 BSOD's while attempting to do this, finally went through on 4th attempt)
• Thought Installing Windows 11 might do something, but I get BSODs during that as well. W11 did not install gave errors 0x800f081f and 0x800f0922 on two different attempts.

Still getting BSODs. Had two today and one was while running the v2 log collector to make this post. They seem to be caused by any one thing, it feels really random and hard to replicate or force to happen.


What are the odds that I have two bad sticks of RAM? Is it possible its a bad SSD? Could it be a bad motherboard? Is there a way I can determine the source of the problem? I'm expecting to have to buy new hardware, I would just like to be sure of which hardware I need to buy before doing so. I'd rather replace RAM than a motherboard but I want to be sure first.

Link to BSOD collector

Windows 10 Pro: ver 22H2 (OS build 19045.2604)
Motherboard: Asus X570 Gaming-e
CPU: AMD Ryzen 9 3900X 3.8GHz 12 core
RAM: G.Skill Trident Z RGB 32 GB (2 x 16 GB) DDR4-3600 CL16
VIDEO: ASUS Tuf Gaming RTX 3080 10GB
SSD C Drive: Western Digital Black SN750 500 GB M.2-2280 PCIe 3.0 X4 NVME

GNTSquid said:

Ran Windows Memory Diagnostics. Reported errors almost immediately.
Ran Memtest64. Immediately fails the test
Ran Memtest86 off USB booting straight from BIOS. Immediately fails the test.

asked and answered yourself :)

tomdsr said:

asked and answered yourself :)

Sure I thought that too but what are the odds I have two bad sticks that go bad at the same time? What about the C drive scan and repair or Windows not installing?

GNTSquid said:

Sure I thought that too but what are the odds I have two bad sticks that go bad at the same time? What about the C drive scan and repair or Windows not installing?

The odds of both RAM sticks being faulty are tiny, but you have said "both sticks have failed tests", and that might suggest it's some other hardware problem - the motherboard for example. Is the RAM you have on the motherboard's QVL list for example? It certainly appears that those two RAM sticks don't work in that board. Are you on the latest BIOS?

ubuysa said:

The odds of both RAM sticks being faulty are tiny, but you have said "both sticks have failed tests", and that might suggest it's some other hardware problem - the motherboard for example. Is the RAM you have on the motherboard's QVL list for example? It certainly appears that those two RAM sticks don't work in that board. Are you on the latest BIOS?

The RAM was part of the QVL. BIOS is the latest version as well that wasnt in beta.

zbook said:

1) This script may be able to display the bad RAM regions:

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

Post a share link into this thread using one drive, drop box, or google drive.



2) Open administrative command prompt and type or copy and paste:

chkdsk /b /v


Run on all drives using the syntax: chkdsk /b /v C: or chkdsk /b /v D: or chkdsk /b /v E: etc.


C:\WINDOWS\system32>chkdsk /b /v
The type of the file system is NTFS.
Cannot lock current drive.

Chkdsk cannot run because the volume is in use by another
process. Would you like to schedule this volume to be
checked the next time the system restarts? (Y/N)

Type: Y

Reboot


Plan to run these chkdsk switches on the Windows drive overnight while sleeping.
The other disk drives can run anytime they are not in use.

After the chkdsk switches complete please run the V2 log collector and post a new V2 share link into the newest post.

I attempted to run the script but I got a BSOD before it could finish and then BSOD'd again while restarting, and thats when I gave up. Today I got a friend to bring over some spare RAM they had and was able to test the computer with their RAM. While its only been a couple hours so far no issues and all memory tests have passed. Even other problems I was having that seemed unrelated have stopped. I dont want to claim victory too early but so far so good.

I can still a

With the new computer stability please run steps 1 and 2 in the prior post.

When the chkdsk switches have completed on all disk drives run:
https://www.tenforums.com/attachment...kfromevent.bat

Post a share link into this thread using one drive, drop box, or google drive.


Post a new V2 share link into the newest post.

GNTSquid said:

The RAM was part of the QVL. BIOS is the latest version as well that wasnt in beta.
I attempted to run the script but I got a BSOD before it could finish and then BSOD'd again while restarting, and thats when I gave up. Today I got a friend to bring over some spare RAM they had and was able to test the computer with their RAM. While its only been a couple hours so far no issues and all memory tests have passed. Even other problems I was having that seemed unrelated have stopped. I dont want to claim victory too early but so far so good.

I can still a

To me, that would suggest that your original RAM wasn't fully compatible with the motherboard.

zbook said:

With the new computer stability please run steps 1 and 2 in the prior post.

When the chkdsk switches have completed on all disk drives run:
https://www.tenforums.com/attachment...kfromevent.bat

Post a share link into this thread using one drive, drop box, or google drive.


Post a new V2 share link into the newest post.

Here's a link to the .zip from the "Tuneup_plus_log.bat" script I'll run the disk check for C tonight and update you.

ubuysa said:

To me, that would suggest that your original RAM wasn't fully compatible with the motherboard.

I'm actually having some confusion from the ASUS website in finding the right QVL list as they give multiple PDF's to look at.. Which PDF should I be looking at? Alternately this website shows my RAM is on the QVL for the Matisse family of AMD processors that mine is apart of, or is the QVL for RAM more concerned with motherboard model? I've had these sticks of RAM since 2020 and never had issues with them until the past month. If RAM isn't on the QVL list in what form do issues show themselves and does it normally take 2 years?

Processor is a AMD Ryzen 9 3900x and RAM is G.Skill TridentZ RGB F4-3600C16D-32GTZRC.

The logs reported problems with scannow, restorehealth, chkdsk, and RAM.



Overnight run chkdsk /b /v C:

Test all disk drives using the syntax: chkdsk /b /v C: or chkdsk /b /v D: or chkdsk /b /v E:, etc.


C:\WINDOWS\system32>chkdsk /b /v
The type of the file system is NTFS.
Cannot lock current drive.

Chkdsk cannot run because the volume is in use by another
process. Would you like to schedule this volume to be
checked the next time the system restarts? (Y/N)

Type: Y

Reboot as needed.


After the chkdsk switches have completed on all disk drives please run V2 and post a new share link into the newest post.

Also run:
https://www.tenforums.com/attachment...kfromevent.bat

Post a share link into the newest post using one drive, drop box, or google drive.




Find a flash drive that you can format (> or = 8 GB)

On a working computer create a new bootable Windows 10 Media Creation Tool (MCT) (Windows 10 iso)

Download Windows 10 ISO File

https://www.microsoft.com/en-us/soft...load/windows10

Code:

Found 0x1 clusters allocated to file "\$Recycle.Bin\S-1-5-21-2064338347-902527081-80780878-1001\$RKI5BH1\AMD_Chipset_Software.exe <0x2,0x1b097>" at offset "0x300f" marked as free
        ... repaired online.
    Found 0x1 clusters allocated to file "\$Recycle.Bin\S-1-5-21-2064338347-902527081-80780878-1001\$RSBYFQK\Packages\Drivers\Display\WT6A_INF\B380668\amdvlk32.dll <0x2,0x1bd27>" at offset "0x389" marked as free
        ... repaired online.
    Found 0x1 clusters allocated to file "\$Recycle.Bin\S-1-5-21-2064338347-902527081-80780878-1001\$RSBYFQK\Packages\Drivers\Display\WT6A_INF\B380668\amdvlk32.dll <0x2,0x1bd27>" at offset "0x11c9" marked as free
        ... repaired online.
                                                                                       
    Found corrupt basic file structure for "\Windows\Logs\WindowsUpdate\WindowsUpdate.20230312.163133.890.3.etl <0x2d,0x71048>"
        ... queued for offline repair.
    Found 0x1 clusters allocated to file "\ProgramData\NVIDIA\MessageBus_11940_0x2763E277A60.log <0x5,0x716b2>" at offset "0" marked as free
        ... repaired online.
                                                                                       
    File "\$Recycle.Bin\S-1-5-21-2064338347-902527081-80780878-1001\$RSBYFQK\Packages\Drivers\Display\WT6A_INF\B380668\amdvlk32.dll <0x2,0x1bd27>" and file "\Windows\Logs\WindowsUpdate\WindowsUpdate.20230312.163133.890.3.etl <0x2d,0x71048>" both own logical cluster 0x2e877f
        ... queued for offline repair.

Code:

 12 unindexed files recovered to lost and found.                    

    Found missing Index entry for file "\Users\Kyle\AppData\Local\Microsoft\Edge\User Data\Default\Extension Scripts\LOG <0x5,0x7169e>" from index "\??\C:\found.001" of directory "$I30"
        ... repaired online.
    Found 6 missing entries (\Users\Kyle\AppData\Local\Microsoft\Edge\User Data\Default\Code Cache\js\f174afedb7fe1a8a_0 <0x1,0xaabdb>, ...) in index "$I30" of directory "\Users\Kyle\AppData\Local\Microsoft\Edge\User Data\Default\Code Cache\js <0x2,0x1a0ab>"
        ... repaired online.
    Found 2 lost files (...\000007.log <0x1,0xaabe8>, ...\000008.ldb <0x1,0xaabe9>); requesting reconnection to index "$I30" of directory "\??\C:\found.002"
        ... repaired online.
    Found lost file "\Users\Kyle\AppData\Local\Microsoft\Edge\User Data\Default\Extension Scripts\LOG.old <0x3,0x1a0dc>"; requesting reconnection to index "$I30" of directory "\Users\Kyle\AppData\Local\Microsoft\Edge\User Data\Default\Extension Scripts <0x2,0x1a0da>"
        ... repaired online.
    Found 9 lost files (...\f_000077 <0x1,0xaabc3>, ...\f_000078 <0x1,0xaabc7>, ...); requesting reconnection to index "$I30" of directory "\??\C:\found.003"
        ... repaired online.

Code:

Windows has found problems and some were fixed online;
the remaining problems must be fixed offline.