"Cdrom has bad block" error in System log, but device works fine

[Guest]

Windows XP-home, sp2 - Computer less than 1 month old.

I haven't tried burning anything, but am not having trouble using the DVD/CD
device. Discovered by chance that there's several groupings of 30-60 error
#7's in succession in the system log, with information messages before and
after the errors saying that the "CD-burning service was successfully sent a
start control". Next message is that it "entered the running state", and the
next msg is that it "entered the stopped state" - all of these only 2-3
seconds apart.

I'm pretty challenged when it comes to the workings of computers, but in
snooping around I noticed this: when I look in Computer Management/Device
Manager, then pull up 'properties' for DVD/CD-Rom Drives, it says "this
device is working properly", but under 'Location', it says 0(0). Curious, I
checked both my hard drives and the floppy properties. Floppy disk drive had
a location, as did 1 of the hard drives, which was 1(1). (The other hard
drive location was 0(0) but I'm guessing that's because it's where I put all
of my junk, whereas the other drive is where all of the system stuff is).

So ... I'm wondering if I'm getting those errors due to a configuration
mixup? Or maybe 'location' has nothing to do with anything, in which case
I've just confused the issue.

sonsie

 

[Rick \Nutcase\ Rogers]

Hi,

The location reference is just where the drive is located on the hardware
bus. 0,0 refers to the first device on the primary ide cable. It is not of
consequence. The problem will be the "bad block" reference. It could mean
that the ide cable is not fully seated. It could also mean that the drive is
bad, or that the slot on the motherboard is.

--
Best of Luck,

Rick Rogers, aka "Nutcase" - Microsoft MVP

Associate Expert - WindowsXP Expert Zone

Windows help - www.rickrogers.org

 

[Guest]

Hi Rick,

So, whether it's a loose cable, bad drive, problem with motherboard (or
whatever else), it sounds like a trip to the shop is in order. Not what I
wanted to hear. <smile> At T'giving my computer went into the shop and
stayed 2 weeks. They replaced a bad ram stick. Got it home and had the same
original multiple, erratic (and weird!) problems. So back the next day for
another 3 days, at which point I pretty much gave up and they admitted not
being able to find a problem. They kind of figured it was an intermittant
motherboard problem since I got the "setting defaults" message on a CMOS
screen at startup a couple of times. Ha! I was beginning to wonder if I was a
jynx since my car was in the shop twice during the same time period, and they
couldn't narrow down the cause of multiple and erratic problems, either!

At any rate, since this computer's less than a month old, I was hoping that
my errors weren't genuine. It's strange because the DVD/CD player works!

Thank you very much for responding. This was my first time writing in to a
forum and it was a positive experience. Oh, and thanks for the education re:
location. Every little bit is a piece of the computer puzzle. <s>

sonsie

 

[Rick \Nutcase\ Rogers]

Hi,

If it's only a month old, use your warranty and request that they replace
the system with one that does not act erratically. These sorts of things
only get worse, not better. From what you describe, I'd guess it's a faulty
motherboard.

--
Best of Luck,

Rick Rogers, aka "Nutcase" - Microsoft MVP

Associate Expert - WindowsXP Expert Zone

Windows help - www.rickrogers.org

 

[S. Taylor]

The IMAPI CD-Burning COM Service only needs to run when you're acyually
burning
CD/DVD's . and you can probably set the service to manual.
otherwise the message is probably informative in nature and nothing to worry
about.

The error message mentioned in the Sunject of your post was probably caused
by
leaving a cd/dvd disk in the drive when you shutdown windows.
The bad block was probably detected at startup, may have been the part of
the disk's maker's anti-piracy method.
Basically, if the cd/dvd disk that caused the error is useable, you can
ignore the error.