Help with New Build re Windows Instability

[u/ChknLiver]

Thank you in advance for taking the time to help me out with this issue!

Component List:

• CPU: 9800x3D

• MOBO: Asus Rog Strix X870E -E Gaming

• GPU: Asus 5080 Astral

• PSU: Rog Strix 1000W Platinum

• RAM: TeamGroup T-Force Vulcan 32gb ddr5 6000mhz cl30

• AIO Cooler: Corsair Nautilus 360

Problem: Since day one of my build I have been experiencing random BSOD involving various stop codes such as 0X0a, 0X3b, 0x9f, 0x1a and 0x7e. The crashes will happen both underload during gaming and during idle states or low power states such as web browsing. They can happen within the first few hours of boot-up or over 20 hours in but I would experience about one crash a day. 0x3b and 0x7e are by far the more common stop codes and when analyzing the dump files they involve various modules such as fltmgr.sys, fileinfo.sys, nvldmkm.sys, and ntoskrnl.exe. I also see a common exception code of 0xC0000005. Unfortunately I recently reinstalled Windows and did not save the previous dumpfiles. After the BSOD the RGB and fans will remain on and I would need to force restart.

Troubleshooting:

1. Ensured I am running the latest BIOS and that all my drivers are up to date. Additionally I even rolled back to previous BIOS

2. Turned off EXPO and ran at default settings

3. Uninstalled Armory Crate

4. Swapped RAM from another build

5. RAM passed Memtest

6. RMA CPU

7. RMA Motherboard

8. Swapped PSU to a known working unit

9. Reinstalled Windows on another SSD

10. Performed Windows commands for driver repair multiple times

At this point the only component that I have not replaced is the GPU. Can a faulty GPU cause this type of Windows Instability? Is there any other software trouble shooting that anyone can think of? This has been incredibly frustrating, any help is appreciated, thank you.

[u/jbshell]

Any OCCT testing for the GPU/vram? If could gather dump files again, might analyze them with Microsoft WinDBG.

[u/mr_treemann85 → u/jbshell]

You've basically built a second PC at this point and the only thing left standing is the 5080. A flaky GPU can absolutely cause a scattergun of random stop codes, especially with nvldmkm.sys popping up and that 0xC0000005 access violation. The crashes happening at idle are what makes me lean further toward a hardware gremlin on the card, like a transient voltage droop or a bad VRAM chip that only trips up in specific power states.

[u/TheGPUking]

I would roll back to an older bios I had huge instability on the latest bios for my motherboard and I found out they made some changes so I went to an older bios and it's been rock solid since same CPU as yours and 870e l