Driver Verifier BSOD - NO dmp files are being created

[ottomobile]

Hey guys,

So this is my second distinct BSOD in the last while. I turned on driver verifier to investigate the first BSOD problem because minidump files arent being created even after turning on small memory dumps (kernel dumps dont show up either). So this new BSOD appears immediately when the starting windows screen appears.

Ive attached the ntbtlog.txt file which was created through the enable boot logging option.

Any info would be awesome, Thanks a lot

 

[richc46]

Welcome
Its difficult to diagnose a BSOD without the reports, but lets try.
Uninstall your Anti Virus and replace with
Microsoft Security Essentials - Free Antivirus for Windows
Set up a clean boot. Do not restore any items until, you are instructed to do so.
Troubleshoot Application Conflicts by Performing a Clean Startup
Make a full Anti Virus scan.
: Download Malwarebytes Anti-Malware 1.62 - FileHippo.com (Full Scan)
Make sure that you are configured correctly.
http://www.sevenforums.com/tutorials/174459-dump-files-configure-windows-create-bsod.html
Submit any new BSODs after you make these changes.

 

[ottomobile]

Thanks for the reply Richard. I will do what you asked and report back but I just wanted to clarify first that if driver verifier is turned off then my computer will start fine. However, when driver verifier is on the BSOD appears before the starting windows screen finishes loading.

 

[richc46]

Thats good information, means that a driver is the problem.

 

[ottomobile]

Beautiful, I like good news. So should I skip the clean boot step and continue with the security essentials and malwarebytes scans then?

 

[richc46]

No the clean boot is more important then ever. The driver may be in the services that will be disabled by Clean Boot.
As a matter of fact, go into clean boot and leave it until you are sure you should of had a bsod, if you dont, follow the clean boot procedure to find out the cause

 

[ottomobile]

So here is where I am at.

- The BSOD will only appear when I turn on driver verifier and it appears before I can log into my account about 20 seconds after the initial dell bios screen switches over to the "starting windows" loading screen.

(I followed the instructions at http://www.sevenforums.com/tutorials/101379-driver-verifier-enable-disable.html to enable driver verifier)

So heres what happened after the clean boot
- I followed the clean boot instructions AND turned on driver verifier
- I encountered the same BSOD BEFORE i was able to log in

I did not do the clean boot with the driver verifier off because I am able to startup without issue with normal startup options when the verifier is off.

My question is if the clean boot will be able to tell us anything if the BSOD occurs before the boot.

I will continue to play around with the clean boot services to see if i can get the bsod to appear with the driver verifier OFF.

Thanks again Richard.

 

[richc46]

No we accomplished nothing with that futile exercise.
Follow the rest of my prior post.

 

[ottomobile]

Ok Malwarebytes is scanning and my dump settings are correct. I didnt change any settings so would there be any other reason why a minidump file is not being created?

 

[richc46]

If you have it set the way I showed you, it should write the dump reports, when you BSOD.

 

[ottomobile]

Odd, Ive tried every method listed on the page you linked me and had multiple BSODs for each one but no dmp files are being created.

So Ive managed to narrow down the driver issue to 3 specific drivers.

I did this with a brutal amount of trial and error with the driver verifier.

Im not sure how to proceed from here though so Id love your thoughts.

The 3 problem drivers generated 2 unique BSODs. I will attach a picture of one of the screens because it listed a different driver on it that wasnt listed in verifier.exe.

So there were two drivers from Broadcom Corporation (btwavdt.sys and btwrchid.sys) both version 6.0.1.3000.
- These both generated the same BSOD which listed hidclass.sys on the screen

The other problem driver was from IDT, Inc. (stwt.sys) version 6.10.5614.0
- This generated the original BSOD that made me post on here in the first place but this one didnt list any .sys files on the BSOD.

Hopefully thats all clear. So im just wondering how I would go about fixing these drivers

 

[richc46]

You could go to the website and hopefully they have a search and replace. They will search your computer for outdated drivers and install them.
You can also try to go to search by the start button, and type device manager. There look for the drivers and install the current ones.
Method one it the best.