I've been dealing with serious issues on my PC, including multiple Blue Screen crashes with various error codes like 0x1a, 0x139, and 0x50. The problems often occur when I have memory-intensive programs open, like browsers, and I also see frequent STATUS_ACCESS_VIOLATION errors in Chrome. Recently, I tried updating from Windows 10 to 11 hoping it would resolve these issues, but it crashed again. I believe there might be some deep-rooted corruption or hardware issues since system repairs with 'sfc' and 'DISM' encountered errors. Here's a breakdown of my system specs:
- **CPU:** AMD Ryzen 7 5700X3D 8-Core Processor
- **Motherboard:** ASRock B550 Phantom Gaming 4/ac
- **BIOS Version:** L3.41 (2/22/2024)
- **RAM:** 16GB Installed
- **OS:** Windows 11 Education (Build 26200)
- **Page File:** 48 GB (C:\pagefile.sys)
I've tried a few troubleshooting methods, like using Driver Verifier on vgk.sys, which resulted in a different Blue Screen. I've also uninstalled Valorant and run Windows Memory Diagnostic, which reported no errors. The CPU temperatures seem fine too, peaking around 65°C under load. Any advice on how to handle this?
3 Answers
You’ve done a lot of good troubleshooting already! The failed DISM and SFC repairs indeed raise flags about possible file corruption. Just to be safe, ensure your backups are up to date since system changes, including BIOS tweaks, can sometimes lead to data loss. For now, check your RAM using a memory testing tool, just to rule out any physical issues with the sticks themselves. If it’s a hardware problem, we might need to look into replacing the RAM or even examining the SSD.
Running Driver Verifier on third-party drivers can often lead to more confusion, especially with drivers like Riot Vanguard. It’s also worth mentioning that the Ryzen 5000 series can behave unpredictably if there are voltage issues from your motherboard. I suggest using a tool called Spec-ify to gather detailed information about your setup, including any errors from your CPU. This should help us understand if there’s a hardware error contributing to your BSODs. Once you run it, share the link it provides.
It sounds like you might be dealing with a memory issue, given that you're seeing those BSODs and Chrome errors. You mentioned Driver Verifier triggered a violation on vgk.sys; that's pretty common for Vanguard. I wouldn't stress over that too much. Instead, let's focus on collecting some crash dump files for further analysis. These can really help pinpoint the root cause of the problem. If you can boot into Windows normally or Safe Mode, check for dump files in C:WindowsMinidump. Zipping them up and uploading could give us more clues. You can use sites like mediafire or catbox.moe for easy sharing.
Related Questions
Can't Load PhpMyadmin On After Server Update
Redirect www to non-www in Apache Conf
How To Check If Your SSL Cert Is SHA 1
Windows TrackPad Gestures