Don't know if this is posted in the right area. We have a Compaq Proliant
ML350, Pent III, 933, 2 GB RAM server running Exchange 2003. It has been
running fine for the longest time. Recently we've been getting a STOP
message in the middle of the night;

STOP 0x1000008e (0xc0000005, 0xe0bc4a23, 0xe0bf7090, 0x00000000)

No hardware changes have been done, all updates and bios settings checked.
No new software (except updates). I've not checked for new drivers because
the machine has been running fine for several months. It has recorded mini
dump files, but running the debugger doesn't make any sense to me. The
server closet is a bit warm so that makes me think a heat issue, but a new
Dell server we have that runs temp checks (sitting right next to the Comaq
machine) says temp is fine.
This STOP message has appeared twice in the last week, both times at or
around 12 midnight. Any ideas on how we check this out or fix it?

Microsoft can perform a debug of the mini-dump or a memory dump (if it is
configured in Startup and Recovery options). There would be a cost, but
there is a guarantee of a resolution.
Otherwise, I would suggest updating the Dell drivers, BIOS, firmware. For
any 3rd party software, verify that you the latest drivers and updates.
What 3rd party applications are on the server?

Driver Verifier is a useful tshooting tools for drivers. Below are intrux.

Steps to Enable Driver Verifier:
=========================
1. Click Run from the Start menu and type the following in the Open box and
click OK:
verifier /flags 9 /all

2. Restart the the computer.

For more information about Driver Verifier, see the following Microsoft
Knowledgebase article:
244617 How to Use Driver Verifier to Troubleshoot Device Drivers in Windows
2000
<http://support.microsoft.com/?id=244617>

**For troubleshooting purposes, we would want the server to bugcheck at
boot and provide the offending driver name. If not, then disable driver
verifier.

Steps to Disable Driver Verifier:
=========================
1. Click Run from the Start menu and type the following in the Open box and
click OK:
verifier /reset

2. Restart the the computer.


If Windows Crashes Before Logging On After Enabling Driver Verifier:
================================================== ======
If Windows will not start after enabling Driver Verifier, you can press F8
to see the Advanced Boot menu and select "Last Known Good Configuration.
You can also try pressing F8 and choosing "Safe Mode." If you are able to
start the computer in safe mode, then continue with the steps in the "Steps
to Disable Driver Verifier" section.

***
Terrence Tan [MSFT]
Microsoft Enterprise Platforms Support

"What is it that binds us to this place as to no other? It is not the well
or the bell or the stone walls or the crisp October nights...No, our love
for this place is based upon the fact that it is as it was meant to be
The University of the People." (Charles Kuralt)

NOTE: Please reply to the newsgroup and not directly to me. This
posting is provided "AS IS" without warranty either expressed or
implied, including, but not limited to, the implied warranties of
merchantability or fitness for a particular purpose. The views and
opinions expressed in this newsgroup posting are mine and do not
necessarily express or reflect the views and/or opinions of Microsoft.
--------------------
<Thread-Topic: Windows Server 2003 STOP Message
<thread-index: AcTey5edvic/TwVrS16AqZtAiKk/pw==
<X-WBNR-Posting-Host: 66.161.229.2
<From: "=?Utf-8?B?RG91Zw==?=" <Doug@discussions.microsoft.com>
<Subject: Windows Server 2003 STOP Message
<Date: Fri, 10 Dec 2004 07:19:07 -0800
<Lines: 16
<Message-ID: <86E2F3CA-2C37-406D-9AC2-3086C33A8613@microsoft.com>
<MIME-Version: 1.0
<Content-Type: text/plain;
< charset="Utf-8"
<Content-Transfer-Encoding: 7bit
<X-Newsreader: Microsoft CDO for Windows 2000
<Content-Class: urn:content-classes:message
<Importance: normal
<Priority: normal
<X-MimeOLE: Produced By Microsoft MimeOLE V6.00.3790.0
<Newsgroups: microsoft.public.windows.server.general
<NNTP-Posting-Host: TK2MSFTNGXA03.phx.gbl 10.40.1.29
<Path: cpmsftngxa10.phx.gbl!TK2MSFTNGXA03.phx.gbl
<Xref: cpmsftngxa10.phx.gbl microsoft.public.windows.server.general:52785
<X-Tomcat-NG: microsoft.public.windows.server.general
<
<Don't know if this is posted in the right area. We have a Compaq Proliant
<ML350, Pent III, 933, 2 GB RAM server running Exchange 2003. It has been
<running fine for the longest time. Recently we've been getting a STOP
<message in the middle of the night;
<
<STOP 0x1000008e (0xc0000005, 0xe0bc4a23, 0xe0bf7090, 0x00000000)
<
<No hardware changes have been done, all updates and bios settings checked.

<No new software (except updates). I've not checked for new drivers
because
<the machine has been running fine for several months. It has recorded
mini
<dump files, but running the debugger doesn't make any sense to me. The
<server closet is a bit warm so that makes me think a heat issue, but a new
<Dell server we have that runs temp checks (sitting right next to the Comaq
<machine) says temp is fine.
<This STOP message has appeared twice in the last week, both times at or
<around 12 midnight. Any ideas on how we check this out or fix it?
<

Also, any events in the system or app log that are noteworthy. Any event
9, 11, 50, 51's that may indicate hardware issue?

***
Terrence Tan [MSFT]
Microsoft Enterprise Platforms Support

--------------------
<Thread-Topic: Windows Server 2003 STOP Message
<thread-index: AcTey5edvic/TwVrS16AqZtAiKk/pw==
<X-WBNR-Posting-Host: 66.161.229.2
<From: "=?Utf-8?B?RG91Zw==?=" <Doug@discussions.microsoft.com>
<Subject: Windows Server 2003 STOP Message
<Date: Fri, 10 Dec 2004 07:19:07 -0800
<Lines: 16
<Message-ID: <86E2F3CA-2C37-406D-9AC2-3086C33A8613@microsoft.com>
<MIME-Version: 1.0
<Content-Type: text/plain;
< charset="Utf-8"
<Content-Transfer-Encoding: 7bit
<X-Newsreader: Microsoft CDO for Windows 2000
<Content-Class: urn:content-classes:message
<Importance: normal
<Priority: normal
<X-MimeOLE: Produced By Microsoft MimeOLE V6.00.3790.0
<Newsgroups: microsoft.public.windows.server.general
<NNTP-Posting-Host: TK2MSFTNGXA03.phx.gbl 10.40.1.29
<Path: cpmsftngxa10.phx.gbl!TK2MSFTNGXA03.phx.gbl
<Xref: cpmsftngxa10.phx.gbl microsoft.public.windows.server.general:52785
<X-Tomcat-NG: microsoft.public.windows.server.general
<
<Don't know if this is posted in the right area. We have a Compaq Proliant
<ML350, Pent III, 933, 2 GB RAM server running Exchange 2003. It has been
<running fine for the longest time. Recently we've been getting a STOP
<message in the middle of the night;
<
<STOP 0x1000008e (0xc0000005, 0xe0bc4a23, 0xe0bf7090, 0x00000000)
<
<No hardware changes have been done, all updates and bios settings checked.

<No new software (except updates). I've not checked for new drivers
because
<the machine has been running fine for several months. It has recorded
mini
<dump files, but running the debugger doesn't make any sense to me. The
<server closet is a bit warm so that makes me think a heat issue, but a new
<Dell server we have that runs temp checks (sitting right next to the Comaq
<machine) says temp is fine.
<This STOP message has appeared twice in the last week, both times at or
<around 12 midnight. Any ideas on how we check this out or fix it?
<