BSOD involving USB drivers

[koolkat77]

Lets enable driver verifier to rule out buggy drivers.

Driver Verifier

I'd suggest that you first backup your data and then make sure you've got access to another computer so you can contact us if problems arise. Then make a System Restore point (so you can restore the system using the Vista/Windows 7 Startup Repair feature).

In Windows 7 you can make a Startup Repair disk by going to Start....All Programs...Maintenance...Create a System Repair Disc - with Windows Vista you'll have to use your installation disk or the "Repair your computer" option at the top of the Safe Mode menu .

Then, here's the procedure:
- Go to Start and type in verifier and press Enter
- Select Create custom settings (for code developers) and click Next
- Select Select individual settings from a full list and click Next
- Select everything EXCEPT FOR Low Resource Simulation and click Next
- Select Select driver names from a list and click Next
Then select all drivers NOT provided by Microsoft and click Next
- Select Finish on the next page.

Reboot the system and wait for it to crash to the Blue Screen. Continue to use your system normally, and if you know what causes the crash, do that repeatedly. The objective here is to get the system to crash because Driver Verifier is stressing the drivers out. If it doesn't crash for you, then let it run for at least 36 hours of continuous operation (an estimate on my part).

If you can't get into Windows because it crashes too soon, try it in Safe Mode.
If you can't get into Safe Mode, try using System Restore from your installation DVD to set the system back to the previous restore point that you created.
Driver Verifier - Enable and Disable

Verifier puts extreme stress on the drivers, bad ones will cause BSOD. If we change all those drivers we hope for no more BSODs, If you get no BSODs, then its not a driver and we look to hardware. With verifier on your computer may be a little laggy, but actually..its just doing its work.

Information
Driver Verifier runs in the background, "testing" drivers for bugs. If it finds one, a Blue Screen of Death (BSOD) will result; the corresponding dump file will hopefully show the faulty driver.

Driver Verifier monitors kernel-mode drivers and graphics drivers to detect illegal function calls or actions that might corrupt the system. It can subject the drivers to a variety of stresses and tests to find improper behavior.

Continue to use your system normally, and if you know what causes the crash, do that repeatedly. The objective here is to get the system to crash because Driver Verifier is stressing the drivers out. If it doesn't crash for you, then let it run for at least 36 hours of continuous operation.

 

[BlazeDCA]

I ran Driver Verifier before and while i did have a BSOD while it was running the BSOD it followed all the symptoms of a regular BSOD that I've been suffering. I'm going to run it again though to be safe.

 

[koolkat77]

Thanks, upload the dumps that you get with verifier enabled.

 

[BlazeDCA]

Didn't even get to the login screen

 

[koolkat77]

dtsoftbus01.sys

Uninstall Daemon tools. The driver dtsoftbus01.sys is a known cause to BSoDs.
Let verifier run for 36 hours and upload the other dumps you get from it.

1: kd> lmvm dtsoftbus01
start             end                 module name
fffff880`0198a000 fffff880`019d0000   dtsoftbus01 T (no symbols)           
    Loaded symbol image file: dtsoftbus01.sys
    Image path: \SystemRoot\system32\DRIVERS\dtsoftbus01.sys
    Image name: [COLOR=Red]dtsoftbus01.sys[/COLOR]
    Timestamp:        Wed Jul 27 20:03:42 2011 (4E301ABE)
    CheckSum:         00046F3C
    ImageSize:        00046000
    Translations:     0000.04b0 0000.04e4 0409.04b0 0409.04e4

 

[BlazeDCA]

Mouse lost connection to the computer, tried plugging it in several times and the computer froze with a looping sound. Had to restart, no minidump though.

 

[koolkat77]

Did you uninstall dtsoftbus01.sys and then it restarted?

 

[BlazeDCA]

i uninstalled the driver, restarted, crashed. Then i also had the crash happen a few minutes ago.

 

[koolkat77]

Is verifier still enabled?
Upload the dumps(newest ones)

 

[BlazeDCA]

Oh boy more crash dumps! This time knmode exception not handled.
The other fixes worked untill now.

 

[koolkat77]

STOP 0x0000001E: KMODE_EXCEPTION_NOT_HANDLED
Usual causes: Device driver, hardware, System service, compatibility, Remote control programs, memory, BIOS

I'm not sure what to say right now..:

1. Whats the age of the hardware?
2. Is it under its warranty?
3. What is the date of installation of the OS?
4. Was the OS re installed?
5. Since when are you having these problems?
6. Did you clear the dust accumulated inside the PC?

 

[BlazeDCA]

1. about a year and a half old
2. I'm pretty sure most of the parts are still under warranty
3. i installed it early february last year
4. nope
5. week or two ago
6. cleaned out dust last week

I was getting KMODE errors a few months ago as well.

 

[koolkat77]

I would not want to suggest further tests since its parts are under warranty, do you want to take it to the vendor for a check up?

 

[BlazeDCA]

It's a custom built one so i cannot take it to a vendor for a checkup.

 

[koolkat77]

It's a custom built one so i cannot take it to a vendor for a checkup.

Why not? I would've if I was in your place.