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. :)
Code:BugCheck 7F, {8, 80050031, 6f8, fffff800033c20f1} Probably caused by : ntkrnlmp.exe ( nt!KiDoubleFaultAbort+b2 )Remove:Code: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
Daemon Tools is known to cause problems such as BSODs with Windows 7, alternatives include Windows own in-built features and also:Code:Start Menu\Programs\DAEMON Tools Pro
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.
More Help and Information with Driver Verifier - Using Driver Verifier to identify issues with Drivers
Memory:
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:
Find your hard-drive manufacturer and run their tests.
Additional Tests:
Post a screenshot of Crystal Disk Info summary:
Check for any file system errors and bad sectors using Option #2 of:
Use this command with Disk Check:
Remove (at least to test):Code:chkdsk C: /f /r
Install and perform full scans with:Code:Start Menu\Programs\ESET Start Menu\Programs\ESET\ESET Smart Security
- Malwarebytes : Free anti-malware download
- Microsoft Security Essentials | Protect against viruses, spyware, and other malware
Do not run Malwarebytes and MSE at the same time, as it can cause conflicts between the two programs.
After checking the dmp file with BlueScreenView, it says caused by driver "ntoskrnl.exe". Is that incorrect?
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 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".
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
I would suggest following this tutorial to make sure that the Drivers are completely gone from your system.Code: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 : dtsoftbus01.sys ( dtsoftbus01+1324 ) Followup: MachineOwner ---------
Driver Sweeper
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.
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.
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?
Quote