win2k randomly rebooting.

C

colin.

Three times today my Windows 2000 computer has rebooted of its' own accord.
It is scanned for virii every night and the disks are defragmented
regularly. I have no idea why it is doing this.

This is from the event log:

Event Type: Information
Event Source: Save Dump
Event Category: None
Event ID: 1001
Date: 29/08/2004
Time: 9.06.43 PM
User: N/A
Computer: COLIN
Description:
The computer has rebooted from a bugcheck. The bugcheck was: 0x000000d1
(0x01736114, 0x00000002, 0x00000000, 0xbfed3c5c). Microsoft Windows 2000
[v15.2195]. A dump was saved in: C:\WINNT\Minidump\Mini082904-02.dmp.

What exactly does this mean? Is there a serious error? If so, can I fix
it?

Many thanks

Colin
 
L

Lanwench [MVP - Exchange]

Go to control panel, system, advanced - find the option not to reboot after
a fatal error (I'm paraphrasing as I don't have W2k handy). That will let
you see the actual blue screen and get more info about the error - usually
the first line includes the file name having the problem.
 
C

colin.

"Lanwench [MVP - Exchange]"
| Go to control panel, system, advanced - find the option not to reboot
after
| a fatal error (I'm paraphrasing as I don't have W2k handy). That will let
| you see the actual blue screen and get more info about the error - usually
| the first line includes the file name having the problem.

I did that, and it didn't work. Since I posted my original message it has
happened a further five times.

I have spent several hours looking for a resolution and I cannot find one.
If this continues to happen then I will just go back to using Linux. I
should never have damn well stopped.
 
L

Lanwench [MVP - Exchange]

colin. said:
"Lanwench [MVP - Exchange]"
Go to control panel, system, advanced - find the option not to
reboot after a fatal error (I'm paraphrasing as I don't have W2k
handy). That will let you see the actual blue screen and get more
info about the error - usually the first line includes the file name
having the problem.

I did that, and it didn't work.

Meaning, you didn't get a blue screen?
Since I posted my original message
it has happened a further five times.

It could well be a hardware problem, you know.
 
C

colin.

Meaning, you didn't get a blue screen?


Yes. Meaning it still just reboots automatically. No bluescreen, no other
error message of any kind. Nothing.

I have just reformatted and yet I am still getting the same problem. Might
this be symptomatic of a screwed hard drive?
 

Ask a Question

Want to reply to this thread or ask your own question?

You'll need to choose a username for the site, which only take a couple of moments. After that, you can post your question and our members will help you out.

Ask a Question

Top