Windows 7 Forums

Welcome to Windows 7 Forums. Our forum is dedicated to helping you find support and solutions for any problems regarding your Windows 7 PC be it Dell, HP, Acer, Asus or a custom build. We also provide an extensive Windows 7 tutorial section that covers a wide range of tips and tricks.


Windows 7: Driver Verifier BSOD - NO dmp files are being created

21 Aug 2012   #1
ottomobile

Windows 7 Professional x64
 
 
Driver Verifier BSOD - NO dmp files are being created

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


My System SpecsSystem Spec
.

21 Aug 2012   #2
richc46

Microsoft Community Contributor Award Recipient

Windows 10, Home Clean Install
 
 

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.
Dump Files - Configure Windows to Create on BSOD
Submit any new BSODs after you make these changes.
My System SpecsSystem Spec
21 Aug 2012   #3
ottomobile

Windows 7 Professional x64
 
 

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.
My System SpecsSystem Spec
.


21 Aug 2012   #4
richc46

Microsoft Community Contributor Award Recipient

Windows 10, Home Clean Install
 
 

Thats good information, means that a driver is the problem.
My System SpecsSystem Spec
21 Aug 2012   #5
ottomobile

Windows 7 Professional x64
 
 

Beautiful, I like good news. So should I skip the clean boot step and continue with the security essentials and malwarebytes scans then?
My System SpecsSystem Spec
21 Aug 2012   #6
richc46

Microsoft Community Contributor Award Recipient

Windows 10, Home Clean Install
 
 

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
My System SpecsSystem Spec
21 Aug 2012   #7
ottomobile

Windows 7 Professional x64
 
 

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 Driver Verifier - Enable and Disable 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.
My System SpecsSystem Spec
21 Aug 2012   #8
richc46

Microsoft Community Contributor Award Recipient

Windows 10, Home Clean Install
 
 

No we accomplished nothing with that futile exercise.
Follow the rest of my prior post.
My System SpecsSystem Spec
21 Aug 2012   #9
ottomobile

Windows 7 Professional x64
 
 

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?
My System SpecsSystem Spec
21 Aug 2012   #10
richc46

Microsoft Community Contributor Award Recipient

Windows 10, Home Clean Install
 
 

If you have it set the way I showed you, it should write the dump reports, when you BSOD.
My System SpecsSystem Spec
Reply

 Driver Verifier BSOD - NO dmp files are being created




Thread Tools





Similar help and support threads
Thread Forum
Multiple BSOD. Driver Verifier Driver caught a driver corrupting
I have had BSOD for a while and being super busy I did not have time to look at it and get it fixed. Well Being a computer guy I assumed I could fix it myself. But with tons of research and trying to use every guide I can find I decided to try here(probably should have came here first). Today I...
BSOD Help and Support
BSOD Created Minidump with Driver Verifier. Need help to read it.
Hi, I am haunted by BSOD for some months now (approx 1-2 per week). They mostly occur during some RAM intensive things (videos, skype, image processing, antivirus check). I am pretty sure it is memory and/or driver related. I unsucessfully tried various things to fix it yet: - Changed Ram,...
BSOD Help and Support
BSOD after driver verifier
Plz check, thanks for more infos.... It's ntoskrnl.exe Searching forum and no proper solution. Startup repair doesn't help - can't fix the problem sfc /scann... no errors chkdsk /r ... no errors
BSOD Help and Support
BSOD w/ driver verifier....now what? all files included
Hey guys, first post here, sooo i've been getting random bsod's and i know its a driver so i used the verifier which caught something but i dont know what. Help! Which driver is causing this madness! Thanks in advance Windows 7 . . . - x64
BSOD Help and Support
Driver verifier BSOD
System will randomly lockup. It is very sporadic and I have tested vga, ram, and cpu using prime95, memtest as well as memtest86, furmark used for vga. 7hrs and 7 full runs of memtest 86, 0 errors. I feel hardware is solid. Upon enabling driver verifier the system bluescreens before even...
BSOD Help and Support

Our Sites

Site Links

About Us

Find Us

Windows 7 Forums is an independent web site and has not been authorized, sponsored, or otherwise approved by Microsoft Corporation. "Windows 7" and related materials are trademarks of Microsoft Corp.

Designer Media Ltd

All times are GMT -5. The time now is 14:59.

Twitter Facebook Google+



Windows 7 Forums

Seven Forums Android App Seven Forums IOS App