bad block errors from SPDT device

[erikt]

Hi,

OS: Windows XP Home
Burning Software: N/A
Anti-virus Software: none
Daemon Tools version: 4.0.3 x86

I've been experiencing an issue for a while, and just recently
narrowed it to the SPDT driver. Basically, my System Log is
getting filled with "cdrom has bad block" errors. It's enough
to slow my system to a crawl, and prevents my machine from
going into suspend (I get a message about the generic CD-ROM
preventing suspend).

If I disable the device in the hardware manager, the events stop
immediately. I also have a physical DVD/RW drive and it does
not cause these issues.

I search the forums, and I only found one other person with
this problem:
Daemon-tools causes event id 7 in event log

Any help would be most appreciated.
erikt

[erikt]

Some additional information...and a workaround I hope.

I have autostart disabled. I think this issue occurs when I leave
an image mounted, exit D-tools, and go into suspend mode.
When I resume from suspend, I get the flood of errors. If I then
launch D-tools, the errors stop.

I'm going to enable autostart and see if that fixes the problem.
I suspect forcing an un-mount before suspend would also help,
I'll try that if the problem continues.

erikt

[Underheaven]

...

Try mounting a different image file. If your image file has errors in it, windows will actually think the errors came from a real CD drive and windows seems to think it a duty to log all this to the event log.

[erikt]

Thanks for the reply. I'll see if it is related to which image I
mount. It definitely happens with more than one, but perhaps
I've got a problem with the way I rip my DVDs...
erikt

[erikt]

A quick update. I enabled autostart and that hasn't cleared up
the problem. I also tried with multiple DVD images and that
doesn't seem to be a contributing factor.

My next experiment will be to try to force an un-mount of any
image before going into suspend. Any other thoughts would be
appreciated.

erikt

[Underheaven]

filter driver

See if you have CD/DVD drivers or filter drivers you don't need.


A topic which shows how to determine drivers in use: No drive letter(s) assigned to the virtual drive(s), or virtual drive(s) disappear