atapi 9

[Guest]

I have a users computer that doesn't seem to want to boot into Windows XP Pro
SP2 on it's own. I am able to boot it into safe mode and looked in the event
viewer and saw that the problem appears to be an atapi 9 event id. Another
thing I noticed is the CD drive appears to be spinning while trying to boot
into XP under normal conditions.

I have seen many articles on this, but they vary so much, and in trying to
follow the threads to a final conclusion I never get to a "Thanks that
worked".

Possible solutions appear to be anything from a microsoft patch, registry
setting changes, replacing the hard drive, and finally it could be the SCSI
bus controller on the motherboard (which would mean replacing the computer!)

This is a P 3 machine with 512 mb of RAM. It appears to be a custom built
machine as it's got a generic case (I don't have any history on this
particular machine).

Does anybody know of a way to run some diagnostic(s) that may be able to
determine whether it's a motherboard vs. harddrive problem on a "Generic" PC?

 

[Brian A]

To see if it is the CD drive causing the problem, either:
Disable it in the BIOS, disable it in Device Manager or disconnect it inside the
case.

You could also check the drives manufacturer support site to see if they have a CD
drive diagnostic utility.



--

Brian A. Sesko { MS MVP_Shell/User }
Conflicts start where information lacks.
http://basconotw.mvps.org/

Suggested posting do's/don'ts: http://www.dts-l.org/goodpost.htm
How to ask a question: http://support.microsoft.com/kb/555375

 

[Homer S.]

I have a users computer that doesn't seem to want to boot into Windows XP Pro
SP2 on it's own. I am able to boot it into safe mode and looked in the event
viewer and saw that the problem appears to be an atapi 9 event id. Another
thing I noticed is the CD drive appears to be spinning while trying to boot
into XP under normal conditions.

I have seen many articles on this, but they vary so much, and in trying to
follow the threads to a final conclusion I never get to a "Thanks that
worked".

Possible solutions appear to be anything from a microsoft patch, registry
setting changes, replacing the hard drive, and finally it could be the SCSI
bus controller on the motherboard (which would mean replacing the computer!)

This is a P 3 machine with 512 mb of RAM. It appears to be a custom built
machine as it's got a generic case (I don't have any history on this
particular machine).

Does anybody know of a way to run some diagnostic(s) that may be able to
determine whether it's a motherboard vs. harddrive problem on a "Generic" PC?

What happens when a normal boot is attempted?


While in Safe Mode:

did you try running a System Restore?

did you look for problems in device manager?

did you run 'msconfig' and get rid of the crap that could cause it not
to boot?

did you try running chkdsk?


Have you tried reseating all the boards and plugs, including the memory?

Are all the fans spinning?

Is the CPU heatsink clogged?


Post answers and I'll continue to help...

HJS

 

[Guest]

When I try to let it boot in normal mode it doesn't do it (well I gave it
almost 30 minutes and it never got past the XP spash screen.

did you try running a System Restore? Unfortunately that is not an option
to me because corporate makes me turn that feature off for security reasons.

did you look for problems in device manager? Yes it doesn't show any.

did you run 'msconfig' and get rid of the crap that could cause it not
to boot? No I didn't because I figured the atapi error was the cause
because the device didn't respond within the timeout period.

did you try running chkdsk? No, but I will try that to see if it fixes the
error.

Have you tried reseating all the boards and plugs, including the memory?
No, since I'm not too big a fan on working with the hardware, that is usually
the last resort. If chkdsk doesn't work will try that.

Are all the fans spinning? Yes

Is the CPU heatsink clogged? I don't know, I will check if I end up having
to crack the case.

 

[Homer S.]

did you run 'msconfig' and get rid of the crap that could cause it not
to boot? No I didn't because I figured the atapi error was the cause
because the device didn't respond within the timeout period.

I don't think Micro$haft programmers would be dumb enough to allow a
CD/DVD drive timeout to bring Windows to it's knees.....although, I
could be wrong. Have you tried removing the CD/DVD drive(s) from device
manager while in Safe Mode? This might force XP to reload a corrupted
atapi driver? In addition, I would still run msconfig and uncheck
everything.... just for shits and grins. Ya never know, it may just
help.

Good Luck,
HJS