Driver Verifier Just got done - Couldn't log in to my computer because of the dang Driver Verifier.
Thats the DMP File.
I uninstalled Daemon Tools - Since I read the dmp, and it looked like one of the files was from that.
But, I also know I had the BSOD's before I installed Daemon tools. Anyways I will add a complete list of all my dmps + System Health thing soon.
When uninstalling Daemon tools you missed one . This latest crash was driver verified and Related to dtsoftbus01.sys Virtual Bus Driver from DT Soft Ltd.
Did you use the tool to remove daemon tools?
If so you will have to find and delte the above manually.
What do you mean "Did you use the tool to remove daemon tools?"?
I just uninstalled it through the Uninstall Program/Files thing.
How exactly do I go about manually removing it?
If you mean Driver Verifier, no. I had to do restore to a system restore point. I had a BSOD on startup.
EDIT: It still gets BSODs
Last edited by Sour; 21 Oct 2011 at 00:07.
When removing daemon tools you need to run a special tool
Please remove any CD visualization programs such as Daemon Tools and Alcohol 120%.
They use a driver, found in your dmp, called sptd.sys, that is notorious for causing BSODs.
Use this SPTD uninstaller DuplexSecure - Downloads DuplexSecure - FAQ
when you're done you can use this Freeware MagicISO Virtual CD/DVD-ROM(MagicDisc) in its place.
If you didnt you can rename the driver to *.bak and it wont load or delete it
Only one of the most recent crashes was related to HIDCLASS.SYS. HID (Human Interface Device) is an external device like a keyboard, mouse, etc. Since the process that was running at the time of the crash was Teamspeak I would start looking there.
If you have not run a system file check please do so.
Run a system file check to verify and repair your system files.
To do this type cmd in search, then right click to run as administrator, then
SFC /SCANNOW
Read here for more information SFC /SCANNOW Command - System File Checker
Let us know the results from the report at the end.
Of note:This error has been linked to excessive paged pool usage and may occur due to user-mode graphics drivers crossing over and passing bad data to the kernel code.
'Did not find any violations'
I actually just reformatted in hopes of it disappearing, nope.
Anyways, I got a new compilation and I believe this could help.
The earlier dmps are most likely the Driver Verifier ones.
I recreated the average BSOD, so those should be them.
I just let my computer go to sleep, and it BSOD. Those are the DMPs.
THe three most recent point to Disk hardware
Please run a chkdsk first and download the mfr's HD test utility and run itCode:FAILURE_BUCKET_ID: X64_0xF4_IOERR_C000000E_IMAGE_hardware_disk
A- CHKDSK /R /F:
Run CHKDSK /R /F from an elevated (Run as administrator) Command Prompt.
Do this for each hard drive on your system.
When it tells you it can't do it right now - and asks you if you'd like to do it at the next reboot - answer Y (for Yes) and press Enter.
Then reboot and let the test run.
It may take a while for it to run, but keep an occasional eye on it to see if it generates any errors.
See "CHKDSK LogFile" below in order to check the results of the test.
B- Elevated Command Prompt:
Go to Start and type in "cmd.exe" (without the quotes)
At the top of the Search Box, right click on Cmd.exe and select "Run as administrator"
C-CHKDSK LogFile:
Go to Start and type in "eventvwr.msc" (without the quotes) and press Enter
Expand the Windows logs heading, then select the Application log file entry.
Double click on the Source column header.
Scroll down the list until you find the Chkdsk entry (wininit for Win7) (winlogon for XP).
Copy/paste the results into your next post.
Quote