Server Re Boots on it's own

Group;

I have a HP Netserver LPr dual P3 server running Windows SBS2003. It has
re-booted by itself twice in 4 months.

Has anyone an idea why a server would re-boot? Hasn't lost power; I have
other machines sitting right next to it running.

Thanks

Doug

What does the System event log say? If it is blank then I recommend
changing settings so you can get a full MEMORY.DMP file and examine it
for errors. Something should be logged somewhere.

I looked for a memory.dmp file but the "search" doggie couldn't find it.
It's supposed to be in the %system root% directory (where is that really?).
C:\???

The event lof doesn't state what happened.

Thanks for the reply.

BTW could mis-matched memory do this? I have an IBM eServer 256 stick, 2
Micron sticks (256 & 128) and a true HP 64 stick. All parity. All
recognized. Just a thought.

Doug

"joshsackett" <> wrote in message
news: oups.com...
> What does the System event log say? If it is blank then I recommend
> changing settings so you can get a full MEMORY.DMP file and examine it
> for errors. Something should be logged somewhere.
>

Doug,

I've always been queasy about mismatched memory sticks, especially in servers.
Can you run the server with just the pair of 256MB ??? ... Ben Myers

On Fri, 10 Jun 2005 02:55:28 GMT, "Doug Holtz" <> wrote:

>I looked for a memory.dmp file but the "search" doggie couldn't find it.
>It's supposed to be in the %system root% directory (where is that really?).
>C:\???
>
>The event lof doesn't state what happened.
>
>Thanks for the reply.
>
>BTW could mis-matched memory do this? I have an IBM eServer 256 stick, 2
>Micron sticks (256 & 128) and a true HP 64 stick. All parity. All
>recognized. Just a thought.
>
>Doug
>
>"joshsackett" <> wrote in message
>news: roups.com...
>> What does the System event log say? If it is blank then I recommend
>> changing settings so you can get a full MEMORY.DMP file and examine it
>> for errors. Something should be logged somewhere.
>>
>
>

If you don't have MEMORY.DMP on the system then you are probably
configured only for mini dumps. Search for mini*.dmp. You now need a
program named dumpchk.exe from the Windows 2000 Resource Kit (you may
be able to find it online).

This page
http://support.microsoft.com/default...b;en-us;254649 and this
page
http://support.microsoft.com/default...307973&sd=tech
will give you lots of information on how to create the dump files and
read their contents. You may find information there.

Or else stick with Ben's idea and get matched memory sticks

Hi Ben;

I can try it. The machine came with an HP 64, abd 2 Micron's - 128 and 256.
All was well for a while. Now I have a hardware issue HP is helping me
with. The management controller needs an update. If only I could get this
puppy to boot from a floppy Should do it just fine. Only need to have
the scsi driver for the symbios controller, which should be on the floppy,
but then all of them are remmed out in config.sys, so it's trial and error.

Doug
<ben_myers_spam_me_not @ charter.net (Ben Myers)> wrote in message
news:...
> Doug,
>
> I've always been queasy about mismatched memory sticks, especially in
> servers.
> Can you run the server with just the pair of 256MB ??? ... Ben Myers
>
> On Fri, 10 Jun 2005 02:55:28 GMT, "Doug Holtz" <>
> wrote:
>
>>I looked for a memory.dmp file but the "search" doggie couldn't find it.
>>It's supposed to be in the %system root% directory (where is that
>>really?).
>>C:\???
>>
>>The event lof doesn't state what happened.
>>
>>Thanks for the reply.
>>
>>BTW could mis-matched memory do this? I have an IBM eServer 256 stick, 2
>>Micron sticks (256 & 128) and a true HP 64 stick. All parity. All
>>recognized. Just a thought.
>>
>>Doug
>>
>>"joshsackett" <> wrote in message
>>news: groups.com...
>>> What does the System event log say? If it is blank then I recommend
>>> changing settings so you can get a full MEMORY.DMP file and examine it
>>> for errors. Something should be logged somewhere.
>>>
>>
>>
>