Yes, most likely all your crashes were created by that vanguard virtual driver.
WHEA_UNCORRECTABLE_ERROR BSOD
Here are my HP Laptop's specs:
Intel i5 8265u
GeForce MX130
HP 8533 Motherboard (BIOS F.48)
Samsung MK471A1K43CB1-CTD DDR4-2666 8GB
TOSHIBA KBG30ZMV256G NVME SSD
Windows 10 22H2 Build 19045.3803
I'm coming here with a somehow weird BSOD error. I got this error while browsing the internet, my system froze for about a few seconds before encountering the error. The error code is WHEA_UNCORRECTABLE_ERROR, the BSOD got stuck at %0 and the system automatically shut down after a few seconds. For some reason, the dump file hasn't been created. I got a similar BSOD error a week ago and in that case the system didn't create a dump file as well, how weird? I have just updated the BIOS 2 days ago to the most recent one, but i think that does not explain why the system fails to create a dump file because i have encountered it before updating my BIOS as well.
I checked the event viewer in some hope that i would find some information about the error and the dump file, and i found these two entries.
Also, here is the picture i took at the moment of the event.
Solutions i have tried before this: I ran Memtest86 and it encountered no errors in my memory. I also ran HD Tune Pro and it also encountered no errors. I ran sfc /scannow and DISM repair commands but that doesn't seem to prevent me getting BSOD's every now and then and doesn't explain why it does not create a dump file.
Windows for home | Windows 10 | Performance and system failures
Locked Question. This question was migrated from the Microsoft Support Community. You can vote on whether it's helpful, but you can't add comments or replies or follow the question.
Answer accepted by question author
6 additional answers
Sort by: Most helpful
-
Anonymous
2024-08-25T14:21:12+00:00 I turned on driver verifier and let the system crash 3 times however the BSOD didn't specify which driver is causing the issue. Although, there is a newly created dump file. I had to go back to the restore point i created via startup repair to access Windows again because driver verifier crashed the system in the loading screen. The link to it is below. I had to go back to the restore point i created via startup repair.
https://www.mediafire.com/file/1qqfm4hjl30hqig/082524-23250-01.dmp/file
I checked the dump file via BlueScreenView, and it reports that it was caused by vgk.sys
I am guessing this is Vanguard. I have League of Legends installed, but i was not playing it at that time. Why would it cause BSOD errors?
-
DaveM121 891.1K Reputation points Independent Advisor2024-08-25T14:04:12+00:00 Those settings are correct.
To try to force Windows 10 to create minidump files and show any faulting drivers, the best option would be to turn on Driver Verifier, let your PC crash 3 times, then you must turn off Driver Verifier, and finally, upload any newly created minidump files
Before you run Driver Verifier, please create a new System Restore Point
https://answers.microsoft.com/en-us/windows/for...
Note, if you have any difficulty getting into Windows with Driver Verifier enabled:
Start your PC, just as Windows attempts to load (spinning dots), press and hold Power Button for 5 - 10 seconds to perform a Hard Shut Down
Do this twice
On the third start Windows will boot into the Recovery Environment and from there you can access System Repair, Safe Mode, Command Prompt... etc.
Go to Troubleshoot - Advanced Option - Startup Settings and click Restart
Upon restart, press 4 to enter Safe Mode
Open Command Prompt as Administrator and run these two commands, then restart your PC.
verifier /reset
verifier /bootmode resetonbootfail
-
DaveM121 891.1K Reputation points Independent Advisor2024-08-25T13:57:41+00:00 Hi, I am Dave, I will help you with this.
Click your Start button, then just type sysdm.cpl and press Enter.
On the resulting dialog, select the Advanced tab.
In the 'Startup and Recovery' section, click Settings.
Please provide a screenshot of the next window.