I work for a support company and one of our customers
called in reporting that their Windows 2003 server shut
down for no apparent reason on Friday 17th September. They
supplied the following error code and I have had no luck
tracing said code via technet or other support forums. Any
help would be much appreciated.
The error code is as follows: Error Code 000000d1,
parameter1 00000000, parameter2 00000007, parameter3
00000000, paramater4 f74da79d

This is listed as Source: system error with event ID 1003
and category (102) Once again any help or suggestions as
to the cause would be much appreciated.

Kind Regards
Derek McMillan

There is a few hotfixes out for this

please google for server 2003 crashes or crashing

also I am looking for the kb articles I will post back
shortly

Joe

Here they are this happened to me and drove me NUTS!



http://support.microsoft.com?kbid=817873 "'STOP
0x0000008E' Error Message Occurs
When You Upgrade to Windows Server 2003"
http://support.microsoft.com?kbid=829422 "'Stop
0x0000008E' Error Message When a
Terminal Services Client Prints a Document"
http://support.microsoft.com?kbid=840216 "Stop 0x0000008e
error occurs on a
server that is running Microsoft Windows Server 2003"


http://support.microsoft.com/default.aspx?scid=kb;en-
us;830098

hope I helped

Joe

Hi Derek,

I found 2 Microsoft articles about the D1 error; they may help you find out
what is causing the problem. If I were you I would look at 3rd party
drivers. For example are you using Veritas Backup Exec...

Computer Stops Responding with "DRIVER_IRQL_NOT_LESS_OR_EQUAL" Stop Error If
CD-ROM Drive or Tape Device Is Connected to SCSI Controller
http://support.microsoft.com/default...b;en-us;821138

Computer stops responding with "Stop 0x000000D1
Driver_IRQL_Not_Less_Or_Equal" error message
http://support.microsoft.com/default...b;en-us;817789

Best of luck

Ninon


"Derek McMillan" <derek.mcmillan@thom-micro.com> wrote in message
news:32b901c49cce$a783b840$a601280a@phx.gbl...

Hello Derek,

There is another suggestion you may consider. Change
the "power" option in the bios to reboot after power loss.
However it is setup in that model server.

It will keep the server up until you can apply the
hotfixes and will help protect against drive corruption
because the disks never stop spinning from a crash. (quick
shutdown)=Crash

In my experience it helped tremendously because it didn't
happen everyday. Although twice a week and I have no SCSI
controllers.

The server stayed up and operational fully with no
problems.

I have applied the hotfixes described here by both posters
and have been quite successful for about 1 month now.

Best of luck
Joe

I have been experiencing the same problem for a while, we
use Veritas Backup Exec which I have been suspecting to be
the cause of the shut down,

Any tips.

Thanks

Hi Sade!

Well I mentioned Veritas BE because of my personal experience. I had Backup
Exec installed on Windows 2003 server that have a IBM RAID Controller, the
server was giving me BSOD at almost every reboot. I tried to follow one of
Veritas 'solution' which ended up causing me more grief than anything
else... The server started on a reboot loop because of blue screen. I have
now moved Veritas to another server, bought the remote agent licence, and
the problem dissapeared!

So if I were you I would try uninstalling Veritas to see if the problem
dissapear...

Almost forgot to say that Veritas was blaming Microsoft for the crashes!

Best of luck

Ninon

"Sade" <anonymous@discussions.microsoft.com> wrote in message
news:059601c4a681$1cdfd680$a301280a@phx.gbl...

How can I get the hot fixes?

"Joe" wrote:

http://support.microsoft.com/default...;OfferProPhone

No charge for hotfixes.

--
Rod
http://thelazyadmin.com
"Jack" <Jack@discussions.microsoft.com> wrote in message
news:432E9885-5A53-4CFD-B1C5-A20153513B6B@microsoft.com...