Sign in with
Sign up | Sign in
Your question

windows 2000 crash troubleshooting

Tags:
  • Windows 2000
  • Servers
  • Database
  • Windows
Last response: in Windows 2000/NT
Share
Anonymous
June 1, 2005 5:40:03 PM

Archived from groups: microsoft.public.win2000.security (More info?)

Hello,

I have a windows 2000 server used for our main database, this is an older
database, unidata. I recently had some odd crashes of the server, basically
the server froze and I had to reboot the server. I found no log entries and
nothing in the dr watson logs.
any idea of where else I could look, or any other method of trying to find
what could have caused the crash?

Thanks

More about : windows 2000 crash troubleshooting

Anonymous
June 1, 2005 8:53:36 PM

Archived from groups: microsoft.public.win2000.security (More info?)

Take a look at Task Manager periodically to see how much memory is being
used. If it steadily is increasing you may have a memory leak for a
application/process and that may become obvious when you look at the
processes and the amount of memory they are using.

Freezes can also be hardware related. The main culprit being on overheating
cpu due to a failing cpu fan or dust clogged heatsink. Failing/flaky power
supplies are also a common cause of computer freezes or random reboots. If
the computer has not been maintained lately at the very least the case cover
should be pulled off and the insides blown out with compressed air including
the cpu heatsink, verifying the cpu can case fans are working properly, and
that all internal cables and component cards are tightly connected. ---
Steve

"mcwe_admin" <mcweadmin@discussions.microsoft.com> wrote in message
news:AE24BE6E-93FA-44BE-BA74-5CAEE1357C83@microsoft.com...
> Hello,
>
> I have a windows 2000 server used for our main database, this is an older
> database, unidata. I recently had some odd crashes of the server,
> basically
> the server froze and I had to reboot the server. I found no log entries
> and
> nothing in the dr watson logs.
> any idea of where else I could look, or any other method of trying to find
> what could have caused the crash?
>
> Thanks
!