Two months of frequent BSOD on my 2021 Asus Flow x13
Two months of frequent BSOD on my 2021 Asus Flow x13
Hello everyone, as mentioned in the title, I've encountered blue screen problems at unpredictable moments while using my 2021 Flow x13 (GV301QH.415). Sometimes it only appears after waking up from sleep mode. Here are some details:
- Operating System: Windows 10 x64
- Laptop model: Second-hand, functional for a year
- OS installation status: Have you reinstalled the system?
- CPU: Ryzen 9 5980HS with integrated Radeon Graphics
- Graphics card: Nvidia GeForce GTX 1650 (Max-q)
- RAM: 32 GB
Throughout this period, I've received various error messages such as:
- KERNEL_SECURITY_CHECK_FAILURE
- Driver_Verifier_Detected_Violation
- WHEA_UNCORRECTABLE_ERROR
Other codes appeared intermittently. I adjusted Windows settings to prevent automatic restarts after a BSOD and generated a minidump file for further analysis. Most analyses ended without completion, so the dump files rarely showed up in my folder.
The only consistent occurrence was a blue screen triggered by the Driver Verifier error. After running the diagnostic output into Windbg with the command `!analyze -v`, I shared the results here. The interpretation suggested potential graphics driver issues.
I reinstalled the drivers manually, but the problem persisted. I tried additional troubleshooting steps in this order:
1. Followed ASUS's official BSOD troubleshooting guide for Windows 11/10
2. Ran other command prompt commands referenced in YouTube tutorials linked to the error codes
3. Performed a clean installation of Windows 11, then Windows 10
4. Executed an SSD scan using `chkdsk /f /r`
5. Checked all drivers for updates via Ghelper
6. Stress-tested GPU and CPU with dedicated software for 30 minutes each
7. Repeated system diagnostics using MyAsus multiple times
Notably, no physical damage was found to the laptop—no drops, spills, or other issues. I used a Razer USB mouse with a dongle; disconnecting it didn’t resolve the problem. The screen still lit up after a blue screen regardless of connected devices.
After five days at a top repair shop, they couldn’t reproduce the BSOD. Since then, I’ve experienced three random occurrences in three days. I’m unsure what’s causing this, as the laptop works perfectly for full days without errors.
Anyone has insights or recommendations? Thank you all.
Driver verification result attached.
Don’t launch Driver Verifier. It isn’t useful for diagnosing BSOD causes (except for a few rare situations that most debuggers don’t handle). While many online discussions urge its use, testing third-party drivers is largely pointless. Press Windows key + R, type "Verifier" and click OK. Choose “Delete Existing Settings.” Restart your computer. You’ll find it easier to ask your grandmother for help with dump files than to rely on AI. The fact that it can generate dump files when DV activates suggests the problem lies elsewhere—likely faulty storage. A WHEA_Uncorrectable_Error indicates the NVMe SSD is likely the culprit, especially if you have multiple drives. WHEA depends on CPU error logs and self-monitoring, but Microsoft has added PCIe errors from problematic NVMe drives as an extra layer. This can point to the slot or motherboard rather than the SSD itself. Two steps can confirm this:
1. Open Event Viewer → Windows Logs → System. Go to “Filter Current Log.” In the dropdown, pick “WHEA-logger” and apply the filter. If you press W to jump to W in the list, uncheck the first entry. Highlight any WHEA events (4–5 should appear), right-click and save. Attach the .evtx file to a post.
2. Modify the registry to display extra crash details on the BSOD screen. This helps with WHEA crashes only. If another crash occurs, this info won’t assist. To show more data during the BSOD, add a registry field under HKEY_LOCAL_MACHINE\System\CurrentControlSet\Control\CrashControl. Set its value to 1 (hex or decimal). After rebooting, the next BSOD should show these details in the top-left corner. If Arg1 equals 0x0000000000000010, Windows is pointing to the NVMe SSD as the issue. Keep in mind it can’t distinguish between SSD and M.2 hardware.