stop codes

Thread view:

Enable EMail Alerts

Start New Thread

Thread rating:

Frode skoknes - 23 Mar 2004 15:08 GMT

Hi!
I have a Windows NT 4.0 server and today I discovered that
it had rebooted during the weekend. I checked in Event
Viewer and the error said "The computer has rebooted from
a bugcheck. The bugcheck was : 0xc0000000a". This is a
stopcode from what I have heard, but this stop code and
it's paramters (left out) are unexplainable to me. I have
searched the Microsoft knowledge base, but no luck. Can
anyone help me explain this error?

kind regards Frode

Reply to this Message

Scott Harding - MS MVP - 23 Mar 2004 16:51 GMT

This is one of the most common errors and it is usually caused by hardware.
I would replace RAM as a start. Also did you add any new hardware? Does the
system currently boot? These can randomaly occur and the machine may be fine
but if this is a regular occurence than you need to track down the cause.
There are several articles about this...do a search for "Stop 0xA" at the
knowledge base and you will find lots of things to try....

Signature

Scott Harding
MCSE, MCSA, A+, Network+
Microsoft MVP - Windows NT Server

> Hi!
> I have a Windows NT 4.0 server and today I discovered that
[quoted text clipped - 7 lines]
>
> kind regards Frode

Reply to this Message

anonymous@discussions.microsoft.com - 24 Mar 2004 12:34 GMT

Hi!
Thanx for the reply.
I have not added any new hardware and the system is
currently up and running and I think the reboot has only
accured once. This is 1 of 2 simmilar servers that runs
the exact same hardware and software and they both have
had problems with error pop ups like this one:
"servicename-DLL Initialization Failed. Initialization of
the dynamic library C:\\WINNT\system32\user32.dll failed.
The process is terminating abnormally".
Do you think this could be a link to why the server
booted? This error causes the server to not to be able to
start new applications and the only solution is to either
stop some of the currently running applications or reboot
the server.

Kind regards Frode Skoknes

>-----Original Message-----
>This is one of the most common errors and it is usually caused by hardware.
[quoted text clipped - 17 lines]
>
>.

Reply to this Message

xe77 - 25 Mar 2004 06:04 GMT

There can be a lot of reasons for a STOP 0x0A code, but an
occasional Stop code isn't something to get worried about.
Gentlemen, this is Windows NT, if you haven't had to
reboot in a couple of weeks then something isn't right!<G>
But seriously, if you have the *same*, problem on two
computers it's most likely a configuration change, patch or
update, or new application that was added to both
computers, or the unlikely failure of some similar piece of
hardware in the same time frame. (not so uncommon for PCs
from the same batches)

>-----Original Message-----
>Hi!
[quoted text clipped - 48 lines]
>>
>.

Reply to this Message