New
#21
I have it down to a handful of drivers. How can I disable startup of these drivers one at a time so I can see which one is causing the problem?
Thanks
I have it down to a handful of drivers. How can I disable startup of these drivers one at a time so I can see which one is causing the problem?
Thanks
I don't get what you mean... Driver verifier causes aBSOD when it encounters a faulty driver... What have you done to "have it down to a handful of drivers"?
And which are they?
I would have expected a crash from Verifier, after which we analyse that dump which, normally, gives us much more specific info on the driver that caused that crash.
Because of all of the warnings on using Verifier I was a little afraid to use it. So I looked at the drivers active in safe mode (where the system works fine) and in regular mode where it crashes. I have a list of the difference and thought if I could easily disable the drivers a group at a time I could narrow it down to one driver.
Bad idea?
I can try verifier if you think that is the best route.
Thanks
No, it's ok, I can see Verifier might look a bit daunting....
Try option three in this tut: Startup Programs - Change
I have previously tried disabling all programs and services through msconfig and that didn't help. It seems to be a driver that is not loaded in safe mode but loaded otherwise. Possibly rcmirror.sys? That showed up on hardware check the MS recommended.
That is why I am looking to see if there is a way to just disable a driver from loading.
Thanks
Ah, ok... that's a biy more difficult. The only relatively easy way is to go in devices and temporarily disable devices (that you don't need to function i.e. Smartcard readers, USB devices, modems etc)
But I don't think this will get you very far.
I'd go for Verifier.