Is my computer crashing a lot?
Is my computer crashing a lot?
Usually, I need to find a device driver that takes too long. The fix is usually to update the BIOS, install all the mother board drivers, and test again. Also, turn off any overclocking features. If you get a memory dump, send it over so someone with a debugger can check it quickly. Buffer flushing errors might come from the hard drive or an error in the CPU's RAM cache, like inside the CPU chip instead of on the motherboard sticks.
The Microsoft support people mentioned driver problems too. He wasn't clear and said it's not a Windows issue. I've already updated the BIOS. So you're telling me to reinstall all motherboard drivers? I don't know about memory dumps or how to put those on a server.
You can just drop those new minidump files in Dropbox or Google Drive so everyone on the forum can use links to get them. I'll probably not be able to do a deep dive into these dumps for you, though other folks here might help with that level of analysis.
Here are the newest minidump file. So this crash happened after updating my BIOS and reinstalling all drivers, including the chipset. https://drive.google.com/file/d/1Gs4IoIN...drive_link
This error message points to a driver programming issue. The bugcheck address looks like a local heap address instead of a real kernel address, which usually means the problem is with how code is written or firmware settings are wrong. If it were just bad memory (RAM), you would see an address that starts with `fff` rather than looking like a standard computer address.
Here are the two specific addresses we have:
* The starting part of my kernel address: 000000000004396d
* My guess for where this is happening: ffffc804`95299ae0 (this starts with `fff`)
It looks like the problem might be with a HID mini driver named VKbms.sys from July 10, 2014. However, it could also be caused by another driver called REDRAGON_MOUSE.sys from September 20, 2017. You can try updating your gaming mouse drivers or firmware to fix this. Or you might need to take the USB mouse out of your computer entirely and remove it completely so that Windows stops loading that specific software.
When you physically remove a USB device, Windows doesn't always actually delete the driver; it just hides it temporarily. You have to go into Device Manager (Control Panel > Devices), look for an option called "Show hidden devices," find all the greyed-out items in your list, and click Delete on them. The driver will only reinstall when you plug that specific mouse back in again at a different port.
I also found some old drivers that might need updating:
* VKbms.sys (July 2014): This is likely the main culprit for this error.
* RTKVHD64.sys (August 2021): This is your motherboard's sound driver. I noticed an old version had a bug that would make it crash when playing with GPU sound, so you should probably update this one while fixing other things.
* rtcx21x64.sys (October 2021): This is the network adapter driver. You could just update this too if you have time.
Here are some extra pieces of info about your computer:
* **Machine ID:** The BIOS shows it is from American Megatrends International, LLC running version L3.41 on an ASRock motherboard named B550M-C with a Ryzen 5 3600 processor.
most people usually don't care about finding exactly which driver causes the problem. I generally have them update all drivers and retest because the only fix they typically get is updating the BIOS and drivers. I always like to run Verifier so that it catches many programming issues, even ones that aren't the real cause of their specific issue. The biggest complaints people have had about Verifier in the past are two things: first, not knowing how to turn it off because the system runs very slowly. Second, not knowing how to get into safe mode (which is needed to stop Verifier from running). So if someone wants to use Verifier, consider doing a one-time run that automatically stops it when they reboot.
To do this: Open Command Prompt as an admin and type "verifier /reset" to turn off all Verifier functions. If you forget to do the reset, your machine will run slowly forever just from the start. Also, make sure you know how to get into safe mode; sometimes a fast SSD makes it very hard to get in, especially if you have to turn off "fast boot" in the BIOS.
Here is another command that can help: type "switch verifier.exe /bootmode resetonbootfail" and then "verifier.exe /oneboot". These commands make sure Verifier only runs on the next reboot instead of every single time it starts. If your system has bug checks, you might want to stop checking a specific driver by adding its name to an exclude list in Verifier testing. The syntax for this is: `driver.exclude "DriverName" /verifier` (using the exact commands from Microsoft help).
Here is how the Verifier command works when you run it inside Command Prompt. You can type several options on just one line at a time.
So I took out the 2 drivers you told me about that seem to be related to my RedDragon keyboard and mouse. You said I was using old ones, but you also checked my crash log back then. Since then, I posted a new log after updating the BIOS and the chipset drivers. I wonder if those "old" drivers are gone now. In any case, my PC kept crashing more times after we did everything mentioned. Here is the latest log. Maybe RAM is something to check again. What do you see? Also, it's crashing a lot right now. It crashed twice while I was writing this message and uploading that dump file.
finally I managed to take a photo of that blue screen. here is the link: https://drive.google.com/file/d/1BqQteGb...sp=sharing