I looked at the minidump myself, but I wasn't sure how to interpret it. I'm pretty sure it's telling me that the BSOD is being caused by a driver, but not sure which one it could be. Anyone have any ideas?
Hello Monolith.
Please enable something called Driver Verifier, you can enable it like this:
Start > type verifier in the Search programs and files box and press "Enter" > Create standard settings > Next > Select driver names from a list > then select all non-Microsoft drivers > Finish
Restart the computer.
Continue to use the computer normally but if you experience any BSODs make available the minidump files.
Information: Driver Verifier will stress test third party drivers that might have caused your BSODs!
Cheers, Boris :)
I actually enabled it already! I'll post again if I get another BSOD.
Thanks.
Not sure if I enabled the driver verifier correctly, as this minidump looks the same as before. My computer must have tried installing updates last night and failed, woke up to a recovery screen. I'm in safe mode right now, but got the same BSOD when I tried starting normally earlier. After I started entering safe mode, Windows reverted the last update.
Yes I think you did because this time there is actually a file that BSOD is pointing at as faulty.
The previous BSOD was caused HIDCLASS.sys which means that there is a problem with a HID device and that is either your mouse or your keyboard!
I see through the msinfo32 file in your first upload that you have a Saitek keyboard and mouse setup, so I would recommend that you visit Saitek's support site to look for driver updates etc., also it is safe to disable Driver Verifier unless there has been more crashes!
And sorry for not responding sooner!
Cheers, Boris :)
Aha, thanks! The Saitek device is actually my HOTAS, not my keyboard/mouse, but I'll check for driver updates for both. Thanks!
Quote