Solved BSOD and then restarts, randomly

[lamerboger]

This started happening yesterday and has happened four times since then. Randomly, the screen goes black and after 5 seconds, the system restarts.

A dialog box appears saying "Windows has recovered from a serious ...... "

All the files are in the attachment.

Any help would be great.

 

[x BlueRobot]

[COLOR="Red"]BugCheck 7F[/COLOR], {8, 80050031, 6f8, fffff800033c20f1}

Probably caused by : ntkrnlmp.exe ( nt!KiDoubleFaultAbort+b2 )

Usual causes:  Memory corruption, Hardware (memory in particular), Overclocking failure, Installing a faulty or mismatched hardware (especially memory) or a failure after installing it, 3rd party firewall, Device drivers, SCSI/network/BIOS updates needed, Improperly seated cards, Incompatible storage devices, Overclocking, Virus scanner, Backup tool, Bad motherboard, Missing Service Pack

Remove:

Start Menu\Programs\DAEMON Tools Pro

Daemon Tools is known to cause problems such as BSODs with Windows 7, alternatives include Windows own in-built features and also:

• MagicISO - Convert BIN to ISO, Create, Edit, Burn, Extract ISO file, ISO/BIN converter/extractor/editor

Follow these steps -

Test for any corrupted drivers, by running Driver Verifier for least 24 hours, stop the test if a BSOD occurs before this time frame. Driver Verifier will place stress on the drivers within your system, which will cause corrupted drivers to crash and hopefully be pinpointed.

• http://www.sevenforums.com/tutorials/101379-driver-verifier-enable-disable.html

:info: More Help and Information with Driver Verifier - http://www.sevenforums.com/crash-lo...-driver-verifier-identify-issues-drivers.html

Memory:

• http://www.sevenforums.com/tutorials/105647-ram-test-memtest86.html

Run Memtest86+ for least 7-8 passes, and preferably overnight as it can take a while to fully complete.

Test each RAM stick individually, if an error is found then move the same RAM stick into the next DIMM slot and test again, if errors are found for the same RAM stick in every available slot then you have a faulty RAM module. On the other hand, if no errors are found in the next slot or the other slots for the same RAM module, then you have a faulty DIMM slot.

Test each RAM stick and every motherboard DIMM slot available.

Run some hard-drive diagnostics and follow these steps:

• Hard Drive Diagnostic Procedure

Find your hard-drive manufacturer and run their tests.

Additional Tests:

• SeaTools for DOS | Seagate
• CrystalDiskInfo - Software - Crystal Dew World

Post a screenshot of Crystal Disk Info summary:

• http://www.sevenforums.com/tutorials/9733-screenshots-files-upload-post-seven-forums.html

:info: Make sure you have the latest firmware for SSD, and ensure all the SATA and Power cables are connected to the drive.

Check for any file system errors and bad sectors using Option #2 of:

• http://www.sevenforums.com/tutorials/433-disk-check.html

Use this command with Disk Check:

chkdsk C: /f /r

Remove (at least to test):

Start Menu\Programs\ESET
Start Menu\Programs\ESET\ESET Smart Security

Install and perform full scans with:

• Malwarebytes : Free anti-malware download
• Microsoft Security Essentials | Protect against viruses, spyware, and other malware

:info: Remember to install the free version of Malwarebytes not the free trail; untick the free trial box during installation

:warn: Do not run Malwarebytes and MSE at the same time, as it can cause conflicts between the two programs.

 

[lamerboger]

After checking the dmp file with BlueScreenView, it says caused by driver "ntoskrnl.exe". Is that incorrect?

 

[Dsprague]

Often times What happens with Blue screens is that ntoskrnl.exe gets blamed because some software is making an improper call to that particular program, but ntoskrnl.exe is rarely ever the problem, if it was you would likely not be able to boot the system at all. ntoskrnl.exe is in fact the system kernel and is there for likely just causing the crash due to another program doing something it shouldn't be doing.

 

[lamerboger]

I have removed daemon tools.

Enabling driver verifier itself brought BSOD when I restarted. Automatic repair failed to find/ repair the problem on its own twice. The BSOD while booting created another .dmp and .sysdata file(which I am attaching with this post).

I had to enter the safe mode, delete the existing settings under "verifier" and then windows booted.

Looking at the .dmp file with the BlueScreenView software shows that this time the problem was caused by "dtsoftbus01.sys" while earlier were due to "ntoskrnl.exe".

 

[lamerboger]

Often times What happens with Blue screens is that ntoskrnl.exe gets blamed because some software is making an improper call to that particular program, but ntoskrnl.exe is rarely ever the problem, if it was you would likely not be able to boot the system at all. ntoskrnl.exe is in fact the system kernel and is there for likely just causing the crash due to another program doing something it shouldn't be doing.

I see, then I shall stop using that again in my post :shock:

 

[Dsprague]

From this most recent Dump it looks like when you removed Daemon tools it did not get all of the drivers it is likely that this was the file making the improper call to ntoskrnl and thus causeing the blue screen

Loading User Symbols
Loading unloaded module list
..
ERROR: FindPlugIns 80070005
ERROR: Some plugins may not be available [80070005]
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck C9, {23e, fffff8800142c324, fffff980066aaee0, 0}

*** WARNING: Unable to verify timestamp for dtsoftbus01.sys
*** ERROR: Module load completed but symbols could not be loaded for dtsoftbus01.sys
Probably caused by : [COLOR=Red]dtsoftbus01.sys[/COLOR] ( dtsoftbus01+1324 )

Followup: MachineOwner
---------

I would suggest following this tutorial to make sure that the Drivers are completely gone from your system.

Driver Sweeper

 

[lamerboger]

I didn't uninstall daemon at the time of that new dmp file. I forgot that I did it afterwards when i disabled verifier.

Looking at the list of drivers in driver sweeper, I am unsure about what to select to clean. I think the daemon has been removed successfully and has been cleaned as well. But your opinion will help.

 

[Dsprague]

It appears to be gone now I would let the system run for say 24 hours with driver verifier enabled and see if there are any more crashes just to be safe though post back and let us know if anything else happens.

 

[lamerboger]

Will get back to you after 24 hours. But if BSOD doesn't occur again, then can I consider this problem as solved or I shall consider that the drivers are not the place to look for?

 

[Dsprague]

If you get another BSOD post your new dump files and we will have a look at them for you and see if we can figure things out. Otherwise I would say you could consider the problem solved.

 

[lamerboger]

The problem still persists. After removing the daemon, I had set the settings of "verifier" and restarted but again got the BSOD and a new dump file. Attaching it with this post.

 

[Dsprague]

It looks like this BSOD is being caused by your broad band adapter it is prduced by a company called Huawei I would either go to their site or To your computer manufacturers site and see if you can get an updated driver

*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck D5, {fffff98006c85003, 1, fffff88002ad5770, 0}

Unable to load image \SystemRoot\system32\DRIVERS\ew_usbenumfilter.sys, Win32 error 0n2
*** ERROR: Module load completed but symbols could not be loaded for ew_usbenumfilter.sys

Could not read faulting driver name
[COLOR=Red]Probably caused by : ew_usbenumfilter.sys[/COLOR] ( ew_usbenumfilter+770 )

Followup: MachineOwner
---------

Last driver update was 2010 probably needs to be updated

start             end                 module name
fffff880`02ad5000 fffff880`02ad8680   ew_usbenumfilter   (no symbols)           
    Loaded symbol image file: ew_usbenumfilter.sys
    Image path: \SystemRoot\system32\DRIVERS\ew_usbenumfilter.sys
    Image name: ew_usbenumfilter.sys
    [COLOR=Red]Timestamp:        Fri Mar 19 23:08:08 2010 (4BA43C18)[/COLOR]
    CheckSum:         00011E8B
    ImageSize:        00003680
    Translations:     0000.04b0 0000.04e4 0409.04b0 0409.04e4

links to Dell and Huawei

 

[lamerboger]

Ok, so now finally unplugging the USB adapter has started my computer. I have searched for any updates for the device driver but there aren't any.

After reboot, i plugged the adapter and have been using it since then, works fine without BSOD for now.

What next?

 

[Dsprague]

My best advice at this point would be to uninstall the software for the mobile broadband and then re-install it just to rule out the possibility that it has some how become corrupted. If the blue screen continues after the re-install of the software I would say the next test would be to see if plugging anything else into that particular USB port causes a blue screen just to rule out hardware failure.

 

[lamerboger]

I have re-installed the software and have been using it for quite sometime. and the port seems fine too.

Should i wait for BSOD or should check a few other things out as well?

 

[Dsprague]

For the moment I would wait And keep running the driver verify to see if it Blue screens again.

 

[x BlueRobot]

[COLOR="red"]BugCheck D5[/COLOR], {fffff98006c85003, 1, fffff88002ad5770, 0}

Unable to load image \SystemRoot\system32\DRIVERS\ew_usbenumfilter.sys, Win32 error 0n2
*** ERROR: Module load completed but symbols could not be loaded for ew_usbenumfilter.sys

Could not read faulting driver name
Probably caused by : [COLOR="Red"]ew_usbenumfilter.sys[/COLOR] ( ew_usbenumfilter+770 )

Usual causes:  Device driver

In my opinion you may now disable Driver Verifier, and then leave this thread open for about a week, posting back any other problems or BSODs.

 

[lamerboger]

Taking "Dsprague"'s advice, I'll stop driver verifier after a day and then will see if any BSOD occurs.

I too think that there is a problem with the driver of the huawei adapter. When I start the computer with the verifier ON and the adapter connected, <b>it hangs</b> either when I enter my password or as soon as the accounts are displayed or in the start itself. However, attaching the device after booting is the right way I am guessing since it hasn't given me any problems so far.

Taking "x BlueRobot"'s advice on the second case, I'll leave this thread open for a week and will come back if any BSOD occurs again.

Thanks guys and Merry Christmas

 

[x BlueRobot]

Your welcome, and have a great Christmas!