Page 1 of 1
(seemingly) Random Restarts
Posted: 2004-05-27 09:07pm
by darthdavid
My computer seems to be having random restarts. I'm relatively sure it's not spyware as they don't appear to be regular and they're too spaced out to prevent the elimination of malicious programs. I looked into event veiwer and found this log. What does it mean?
Code: Select all
The computer has rebooted from a bugcheck. The bugcheck was: 0x000000d1 (0x00000060, 0x00000002, 0x00000000, 0xed0211b5). Microsoft Windows 2000 [v15.2195]. A dump was saved in: C:\WINNT\Minidump\Mini052704-02.dmp.
There was also this one from a reboot that happened earlier
Code: Select all
The computer has rebooted from a bugcheck. The bugcheck was: 0x00000050 (0xffffffff, 0x00000000, 0xffffffff, 0x00000000). Microsoft Windows 2000 [v15.2195]. A dump was saved in: C:\WINNT\Minidump\Mini052704-01.dmp.
Posted: 2004-05-28 01:49am
by Uraniun235
Right-click My Computer -> Properties -> Advanced tab -> Startup and Recovery button -> Uncheck the "Automatically Reboot" checkbox.
Now you should get BSODs instead of spontaneous restarts, and you can report back what error W2K kicks back to you (and, if possible, what driver file it points to).
Posted: 2004-05-28 03:34pm
by CorSec
You could try
this program and check to make sure your ram is good. I spent the two months chasing after a random restart problem and this was my problem. (That, and then the power supply went kaput.)
Posted: 2004-05-28 04:08pm
by General Zod
possibly the MS Blaster worm or one of its variants?
Posted: 2004-05-28 04:20pm
by Vendetta
Uraniun235 wrote:Right-click My Computer -> Properties -> Advanced tab -> Startup and Recovery button -> Uncheck the "Automatically Reboot" checkbox.
Now you should get BSODs instead of spontaneous restarts, and you can report back what error W2K kicks back to you (and, if possible, what driver file it points to).
You don't need to do that, the Event Viewer has the same information (the STOP codes).
From the codes it's throwing up (DRIVER_IRQL_NOT_LESS_OR_EQUAL and PAGE_FAULT_IN_NONPAGED_AREA), you're looking at either a driver fault, so uninstall and roll back any drivers you've installed recently, or possibly a memory fault.
A memory checking program is a good idea at this point as well.
Posted: 2004-06-01 02:11am
by Uraniun235
If it's a driver fault, it should be kicking back a file name for the driver (like my system will BSOD every tenth boot or so with my RAID controller's driver listed), and I don't see any files listed in the Event Viewer logs posted. I still think he should elect to view the BSOD so he can find out just what driver is killing Windows.