BSOD likely caused by drivers, only crashes when running Verify.exe

Griff01 · 22 Feb 2018

Good day ladies and gents,
As the title says, I think one of my USB drivers may be causing the issue. I don't recall why, but a long time ago I did go into verifier.exe and remove all information (shut it off). With this issue, I did go out to Etron and download the latest drivers, uninstalled and deleted the old drivers, rebooted, and installed the Etron USB 3.0 drivers. The reason I believed it was USB drivers is because after inserting a USB pen-drive into a port, no others will be recognized. This is the only issue I noted. When I turn on Verifier.exe with standard config, I get a BSOD within a few minutes. For purpose of data collection, I turned on mini-dumps (no overwrite), set Verifier to run standard config, and allowed the PC to BSOD three times today purposefully. Yesterday it BSOD'd twice before I decided to collect three dumps today for this post.

I can (and am) running my PC with Verifier not monitoring any drivers. However, if someone out there enjoys looking through the attached BSOD data files comes up with an idea, and/or cares to explain how they recognized it, that'd be great. My IT expertise has never delved into the realm of .dmp files.

I am fighting against the Win10 upgrade as long as possible. I can work on them, but I don't like the new interface or restrictions... Though the Bash interface capability is pretty cool.

Thanks!
Cody

Griff01 · 20 Mar 2018

Did I not give enough information in the above post, or too much?
Essentially my USB drivers with verifier.exe on cause BSOD. With Verifier off, Once a single USB drive is plugged into my USB ports, no other drive can go in that port unless I reboot.

**axe0** · 21 Mar 2018

Hi Griff01,

I would suggest to update or reinstall the Logitech keyboard drivers.

Code:

4: kd> lmvm LGBusEnum
Browse full module list
start             end                 module name
fffff880`04ffa000 fffff880`04ffee00   LGBusEnum T (no symbols)           
    Loaded symbol image file: LGBusEnum.sys
    Image path: LGBusEnum.sys
    Image name: LGBusEnum.sys
    Browse all global symbols  functions  data
    Timestamp:        Mon Jun 13 20:47:08 2016 (575EFFAC)
    CheckSum:         00012B72
    ImageSize:        00004E00
    Translations:     0000.04b0 0000.04e4 0409.04b0 0409.04e4

Griff01 · 21 May 2018

I tried this and several other solutions. Nothing worked. I simply turned Verify.exe off and called it a day. I'm debating whether or not to finally cave in to the Win10 rage, and simply shut off as many "spy" programs as possible by not allowing their data sharing.

Thanks anyhow!

**axe0** · 22 May 2018

Don't go to Windows 10, more often than not you will get more problems!

What other solutions have you tried?

Off-topic:
There are no 'spy' programs in Windows 10, only certain settings that you may want to tweak in the Privacy settings. I have some of them tweaked as well to disable the camera, microphone and call history since neither of them is available. I also wrote a simple powershell script to remove as much as possible preinstalled apps without causing issues, waste of storage for stuff I don't use.
Once again, Windows 10 doesn't 'spy', it only collects data with permissions that you once again may want to change asap in Windows 10. As of version 1803 that has been improved a lot, partially thanks to the Dutch privacy organization DPA (Dutch Data Protection Authority, or Autoriteit Personeelsgegevens in Dutch) who forced Microsoft into making it more clear what data is collected, how it is collected, what happens with it, etc. because Microsoft apparently broke the data privacy law in being unclear about it, see Microsoft’s response to privacy concerns in the Netherlands - Windows 10 Forums.
Although Microsoft now makes it more clear what data they collect, this is only the case with the telemetry data. However, everything can be regulated in the Privacy settings.
As a side note, I wouldn't recommend to disable the Feedback & Diagnostics data collection, problems caused by Windows won't be easily fixed without it. On account of the amount of problems and the amount of software available it can be either of the installed programs as well and Microsoft would be able to tell and fix it.

I would also want to ask what the problem is with Microsoft collecting data of their own product to improve their own product ('improve' is subjectively), but that would be too off-topic so just ignore this.