RE: Sudden stop message when turning off system

It would be pretty easy to disable the cdrom device, to see if your shutdown
error goes away. If it does, you need a better driver for the cdrom.
Uninstalling the driver in device manager will let windows replace it
automatically. There is also a checkbox to temporarily disable it.
start/run, type:
devmgmt.msc
--
helpful? click "Yes" button. Voting helps the web interface.
Holiday Lights: http://www.geocities.com/marfer_mvp/Xmaslgt.zip
Mark L. Ferguson



"JLB" wrote:

I used the Event Viewer, and there were two problems mentioned.

Event Type: Error
Event Source: Cdrom
Event Category: None
Event ID: 7
Description:
The device, \Device\CdRom0, has a bad block.
_________________________________________________________________
Event Type: Warning
Event Source: MSSQL$MICROSOFTBCM
Event Category: (8)
Event ID: 19011
Description:
The description for Event ID ( 19011 ) in Source ( MSSQL$MICROSOFTBCM )
cannot be found. The local computer may not have the necessary registry
information or message DLL files to display messages from a remote computer.
You may be able to use the /AUXSOURCE= flag to retrieve this description; see
Help and Support for details. The following information is part of the event:
(SpnRegister) : Error 1355.


Could either of these cause the error, and if so, how can it be corrected?


"Mark L. Ferguson" wrote:

Some driver for hardware is failing. The Event Viewer might mention a name of
a file that will indicate what hardware is involved.

start/run, type:
eventvwr.msc
--
helpful? click "Yes" button. Voting helps the web interface.
Holiday Lights: http://www.geocities.com/marfer_mvp/Xmaslgt.zip
Mark L. Ferguson



"JLB" wrote:

I have Windows XP Professional (SP2) and I tried to turn off my computer when
a stop message appeared. The stop code is as follows: 0x0000008E
(0xC0000005, 0x80610303, 0xF9D21A54, 0x00000000). I have tried to find a
solution by updating Windows. The Web Response ID that is given as the
problem is 898. I have rebooted the system multiple times to see if the
error has resolved itself, but the same code and blue screen appears. Does
anyone know what is going wrong?
.