Looks like Daemon Tools is causing that...Sptd.sys is the D-Tools driver.

Try uninstalling it. If the problem goes away, download the latest version and install that.


99% of the time it's a driver causing a blue screen - they are the only pieces of 3rd party software that can directly interact with the memory and IO manager. USB devices don't cause blue screens unless they are faulty and/or have a poorly written driver ie. Doesn't have sufficient consistency checks.

In general, Windows executive will throw up a blue screen for two reasons;

• Hardware behaved in a way that caused an action that was completely unrecoverable, like it permanently lost memory.
• A piece of software caused a fault that went as far as compromising the system's ability to ensure that it is running correctly.

For example, if a driver object modified a region of memory that belonged to another object, that original object and the driver object must immediately be discarded because we can't be sure what they'll do now that they've lost the plot. If the other object is something critical the the OS core (quite probable), then Windows itself cannot be assured, and so Windows must STOP.

If a USB device did something silly, the driver should be able to detect it and will trigger the necessary ejection events. All standard Windows USB drivers are smart enough to do this, but 3rd party drivers aren't always. This is why USB has a reputation for causing blue screens; it's not really the USB device's fault even if it is defective; it's either the driver or the controller malfunctioning and being mishandled. USB is arguably the most fault tolerant interconnect the PC has.

In old Windows, there used to be a lot of bail-outs that caused blue screens, but Windows 5.0 was designed to be very fault tolerant.