PDA

View Full Version : system crashing


Chris
December 11th 03, 09:33 PM
My system often crashes just as it is starting up and gives these error
codes:

0x0000000A (0x000000B0, 0x00000002, 0x00000000, 0x804EA7AB)

is there some way I can find out what they mean?

It's starting to do it more and more often.

TIA.

Gerry Cornell
December 11th 03, 09:34 PM
Chris

I would look in Event Viewer at the logged errors.

1. To open Event Viewer, click Start, click Control Panel, double-click =
Administrative Tools, double-click Event Viewer and select System for =
system errors or Application for application errors. Look for Error in =
the Type column and double click on Error to reveal a Description of the =
error. This can be copied by using Clipboard Viewer (see later).
=20
2. Part of the Description of the error will include a link, which you =
should double click for further information and you can copy using copy =
and paste.
http://go.microsoft.com/fw.link/events.asp
(Please note the hyperlink above is for illustration purposes only)

3. For some errors you will find "+ Related Knowledge Base Article", =
which if double clicked takes you to the Knowledge Base Article =
containing a suggested solution.

There always seems to be a step 2 but not always a step 3.=20

A tip for posting copies of Error Reports (Step 1). Run Event Viewer and =
double click on the error you want to copy. In the window which appears =
is a button resembling two pages. Double click the button and close =
Event Viewer. Now start your message ( email )and do a paste into the =
body of the message. This will paste the info from the Event Viewer =
Error Report complete with links into the message. Make sure this is the =
first paste after exiting from Event Viewer. It can be helpful to place =
a shortcut to Event Viewer on your Desktop.

HOW TO: View and Manage Event Logs in Event Viewer in Windows XP
http://support.microsoft.com/default.aspx?scid=3Dkb;en-us;308427

--=20
~~~~~~


Hope this helps.

Gerry
~~~~~~~~~~~~~~~~~~~~~~~~
FCA

Stourport, Worcs, England
Enquire, plan and execute.
~~~~~~~~~~~~~~~~~~~~~~~~
Please tell the newsgroup how any=20
suggested solution worked for you.
http://dts-l.org/goodpost.htm
~~~~~~~~~~~~~~~~~~~~~~~~

"Chris" > wrote in message =
...
> My system often crashes just as it is starting up and gives these =
error
> codes:
>=20
> 0x0000000A (0x000000B0, 0x00000002, 0x00000000, 0x804EA7AB)
>=20
> is there some way I can find out what they mean?
>=20
> It's starting to do it more and more often.
>=20
> TIA.
>=20
>

Chris
December 11th 03, 09:35 PM
Hi Gerry, thanks I've ran Event Viewer and found this on the errors:

Event Type: Error
Event Source: System Error
Event Category: (102)
Event ID: 1003
Date: 19/05/2003
Time: 15:47:37
User: N/A
Computer: COMPUTER
Description:
Error code 0000000a, parameter1 000000b0, parameter2 00000002, parameter3
00000000, parameter4 804ea7ab.

For more information, see Help and Support Center at
http://go.microsoft.com/fwlink/events.asp.
Data:
0000: 53 79 73 74 65 6d 20 45 System E
0008: 72 72 6f 72 20 20 45 72 rror Er
0010: 72 6f 72 20 63 6f 64 65 ror code
0018: 20 30 30 30 30 30 30 30 0000000
0020: 61 20 20 50 61 72 61 6d a Param
0028: 65 74 65 72 73 20 30 30 eters 00
0030: 30 30 30 30 62 30 2c 20 0000b0,
0038: 30 30 30 30 30 30 30 32 00000002
0040: 2c 20 30 30 30 30 30 30 , 000000
0048: 30 30 2c 20 38 30 34 65 00, 804e
0050: 61 37 61 62 a7ab



The trouble is when I try to find out more about it, I get this message:

We're sorry
There is no additional information about this issue in the Error and Event
Log Messages or Knowledge Base databases at this time. You can use the links
in the Support area to determine whether any additional information might be
available elsewhere.


and I can't find anything more about it.

But I've just tried using MSConfig to try to determine what the problem is
and it seems to go away if I boot up without my "Norton Antivirus
Autoprotect" being enabled. So does this mean the virus killer is causing
the problems? I'm not sure how to fix it now except for stopping using it
which I'd rather not do.

Gerry Cornell
December 11th 03, 09:36 PM
Chris

This link may be relevant:
Troubleshooting a Stop 0x0000000A Error in Windows XP
http://support.microsoft.com/default.aspx?scid=3Dkb;EN-US;Q314063

From the reports in Google most suggestions for cause of the error are =
directed at drivers.=20
You could look in Start, Control Panel, System, Hardware, Device Manager =
and look for yellow question marks. Also you might use the Bootvis.exe =
tool to see if you can see which driver is playing up either by a =
noticeable delay or indication of an error -the download can be obtained =
on the link page which follows:
http://www.microsoft.com/hwdev/platform/performance/fastboot/default.asp

Who is the manufacturer of your computer and what is the model. What =
video driver is installed?=20

Your problem judging by Google could be a difficult one to resolve.


~~~~~~


Hope this helps.

Gerry
~~~~~~~~~~~~~~~~~~~~~~~~
FCA

Stourport, Worcs, England
Enquire, plan and execute.
~~~~~~~~~~~~~~~~~~~~~~~~
Please tell the newsgroup how any=20
suggested solution worked for you.
http://dts-l.org/goodpost.htm
~~~~~~~~~~~~~~~~~~~~~~~~

"Chris" > wrote in message =
...
> Hi Gerry, thanks I've ran Event Viewer and found this on the errors:
>=20
> Event Type: Error
> Event Source: System Error
> Event Category: (102)
> Event ID: 1003
> Date: 19/05/2003
> Time: 15:47:37
> User: N/A
> Computer: COMPUTER
> Description:
> Error code 0000000a, parameter1 000000b0, parameter2 00000002, =
parameter3
> 00000000, parameter4 804ea7ab.
>=20
> For more information, see Help and Support Center at
> http://go.microsoft.com/fwlink/events.asp.
> Data:
> 0000: 53 79 73 74 65 6d 20 45 System E
> 0008: 72 72 6f 72 20 20 45 72 rror Er
> 0010: 72 6f 72 20 63 6f 64 65 ror code
> 0018: 20 30 30 30 30 30 30 30 0000000
> 0020: 61 20 20 50 61 72 61 6d a Param
> 0028: 65 74 65 72 73 20 30 30 eters 00
> 0030: 30 30 30 30 62 30 2c 20 0000b0,
> 0038: 30 30 30 30 30 30 30 32 00000002
> 0040: 2c 20 30 30 30 30 30 30 , 000000
> 0048: 30 30 2c 20 38 30 34 65 00, 804e
> 0050: 61 37 61 62 a7ab
>=20
>=20
>=20
> The trouble is when I try to find out more about it, I get this =
message:
>=20
> We're sorry
> There is no additional information about this issue in the Error and =
Event
> Log Messages or Knowledge Base databases at this time. You can use the =
links
> in the Support area to determine whether any additional information =
might be
> available elsewhere.
>=20
>=20
> and I can't find anything more about it.
>=20
> But I've just tried using MSConfig to try to determine what the =
problem is
> and it seems to go away if I boot up without my "Norton Antivirus
> Autoprotect" being enabled. So does this mean the virus killer is =
causing
> the problems? I'm not sure how to fix it now except for stopping =
using it
> which I'd rather not do.
>=20
>=20
>

Chris
December 11th 03, 09:38 PM
Gerry, I found the problem was being caused by my cdudf_xp driver failing to
load for some reason.

When I got my computer it came with Roxio easy CD creator preinstalled that
I think used this driver for it's direct cd feature. I uninstalled roxio
and installed nero burning rom instead, (last december I think) and there
weren't any problems but just recently I've updated Nero and I think that
must be what's caused the problems.

I've tried uninstalling are re-installing different versions of things and
the only thing I've found that will fix the problem is to leave roxio
installed, which is strange because things had been ok for six months
without it being installed. I've got nero installed as well now and they
don't seem to cause any problems with each other so I'll probably just leave
it like that.

I don't know if there's any other way I could fix the problem.

Thanks for helping.


"Gerry Cornell" > wrote in message
...
Chris

This link may be relevant:
Troubleshooting a Stop 0x0000000A Error in Windows XP
http://support.microsoft.com/default.aspx?scid=kb;EN-US;Q314063

From the reports in Google most suggestions for cause of the error are
directed at drivers.
You could look in Start, Control Panel, System, Hardware, Device Manager and
look for yellow question marks. Also you might use the Bootvis.exe tool to
see if you can see which driver is playing up either by a noticeable delay
or indication of an error -the download can be obtained on the link page
which follows:
http://www.microsoft.com/hwdev/platform/performance/fastboot/default.asp

Who is the manufacturer of your computer and what is the model. What video
driver is installed?

Your problem judging by Google could be a difficult one to resolve.


~~~~~~


Hope this helps.

Gerry
~~~~~~~~~~~~~~~~~~~~~~~~
FCA

Stourport, Worcs, England
Enquire, plan and execute.
~~~~~~~~~~~~~~~~~~~~~~~~
Please tell the newsgroup how any
suggested solution worked for you.
http://dts-l.org/goodpost.htm
~~~~~~~~~~~~~~~~~~~~~~~~

Google