You said to have enabled driver verifier and generated dump files and then uninstalling bad driver, why not try again?
please follow bellow steps carefully to enable driver verifier, it should pinpoint bad driver right away:
https://answers.microsoft.com/en-us/...3-c48669e4c983
Thank you!
I tried Driver Verifier before I reinstalled Windows and any Logitech driver causes an instant BSOD while it's enabled.
That was with G Hub (latest version) installed, so this time I tried downgrading to the older Logitech Gaming Software. Same thing unfortunately! Logitech drivers always cause Driver Verifier to crash.
I just find it hard to believe it's the Logitech drivers considering they're quite popular and the fact that I've been using it for years without issue.
Have you tested your computer without logitech drivers and hardware?
ex. playing games with other mose?
I'll try, I just want to see if I can get one more BSOD and see if I can get a crash dump to generate under normal circumstances. My page file was only 3GB so I've increased it as you suggested.
- - - Updated - - -
Well it's getting worse now. Just had a new one WHEA_UNCORRECTABLE_ERROR. Noticed that the game was stuttering more than usual leading up to the crash. Once again, no crash dump. It sat at the blue screen stuck at 0%.
Nothing in Event Viewer apart from Event ID 161: Dump file creation failed due to error during dump creation.
That makes sense now.
For system to create a dump file, it must read from memory and write to disk.
If either of these 2 components are not functioning properly during BSOD creating of dump file fails.
If virtual page file is not large enough generating dump file fails too, but you solved that problem already.
Last time I had BSOD it was due to SSD firmware and no dump was generated since the SSD was not operative.
I didn't know what is the problem until the drive was completely dead and had to replace it.
Thank you for your help so far!
I uninstalled the Logitech drivers and had another WHEA_UNCORRECTABLE_ERROR in game. No dumps. Nothing in event viewer apart from ID 161 and unexpected shutdown.
It's strange because DRIVER_VERIFIER_DETECTED_VIOLATION drops dump files, however if I experience a BSOD in game it never leaves a dump file.
According to Samsung Magician all 4 drives are on the latest firmware.
I'll test the memory again. When I first purchased the parts for this PC a couple of years ago the memory was faulty and was flaky enough for me not to see any errors for weeks despite extensive testing. Perhaps the same is happening here.
HWInfo log doesn't show anything untoward, apart from, once again it's showing my 5v and 3.3v rail voltages as being quite low (5v is normally at 4.8v but drops to 4.5, 3.3v is normally 3.2v but drops to 3.04v), but I don't have the means to test this yet...waiting for Corsair to send me a new Link dongle so I can monitor actual voltages).
Why don't you upload these dump files here then?It's strange because DRIVER_VERIFIER_DETECTED_VIOLATION drops dump files, however if I experience a BSOD in game it never leaves a dump file.
If the firmware is bad, then it's "latest" status means nothing.According to Samsung Magician all 4 drives are on the latest firmware.
I've attached the Log Collector output, but they were just the misbehaving Logitech drivers and according to WhoCrashed, several instances of Verifier blaming itself.
The driver caught is:
logitech gamepanel virtual something
But you said:
What I was proposing in my previous post is not just to remove logitech drivers but also stop using logitech hardware all together, then enable driver verifier and post fresh dumps.I uninstalled the Logitech drivers and had another WHEA_UNCORRECTABLE_ERROR in game. No dumps. Nothing in event viewer apart from ID 161 and unexpected shutdown.
That probably means you'll wait for BSOD while not playing games.
Okay, I'll have to dig around for another mouse as I've been using this one for about 3 years and the ones I had before were Logitech too.
Quote