Frequent Reboots - How to Correct?

  • Thread starter Thread starter Adam Smith
  • Start date Start date
A

Adam Smith

Hello,

Windows Professional 2000 on Pentium MMX vintage platform, new Hard
Drives, perfect NND and other analytical tests. Reboots constantly.

Administrative tools ==> Bug check cause of event:Ex -
The computer has rebooted from a bugcheck. The bugcheck was:
0x00000050 (0xe40c7000, 0x00000000, 0xa000e77f, 0x00000001).
Microsoft Windows 2000 [v15.2195]. A dump was saved in:
C:\WINNT\Minidump\Mini072006-01.dmp.

Running Support Tools to analyze dump file ==>

C:\Program Files\Support Tools>C:\WINNT\Minidump\Mini072006-01.dmp
****************************************************************
**
** Windows 2000 Crash Dump Analysis
**
****************************************************************
*
Filename . . . . . . .C:\WINNT\Minidump\Mini072006-01.dmp
Signature. . . . . . .PAGE
ValidDump. . . . . . .DUMP
MajorVersion . . . . .free system
MinorVersion . . . . .2195
DirectoryTableBase . .0x031ea000
PfnDataBase. . . . . .0x818d7000
PsLoadedModuleList . .0x80481580
PsActiveProcessHead. .0x80483008
MachineImageType . . .i386
NumberProcessors . . .1
BugCheckCode . . . . .0x00000050
BugCheckParameter1 . .0xe40c7000
BugCheckParameter2 . .0x00000000
BugCheckParameter3 . .0xa000e77f
BugCheckParameter4 . .0x00000001

ExceptionCode. . . . .0x80000003
ExceptionFlags . . . .0x00000001
ExceptionAddress . . .0x80449d15

C:\Program Files\Support Tools>

What does this say to me, (yes they are octal addresses), but where can
I find info on the parameters, what should I do to prevent a recurrence
of the reboot (well reduce the frequency, given the system, etc., etc.

Thanks
 
OOOooooooops!!!!
Failed to include question ==>
Could this be a Power Supply problem ?
 
Adam Smith said:
OOOooooooops!!!!
Failed to include question ==>
Could this be a Power Supply problem ?
Click to expand...

Could be. Looks like bad RAM or a failing mainboard to me, though. -Dave
 
Hello,

Windows Professional 2000 on Pentium MMX vintage platform, new Hard
Drives, perfect NND and other analytical tests. Reboots constantly.

Administrative tools ==> Bug check cause of event:Ex -
The computer has rebooted from a bugcheck. The bugcheck was:
0x00000050 (0xe40c7000, 0x00000000, 0xa000e77f, 0x00000001).
Microsoft Windows 2000 [v15.2195]. A dump was saved in:
C:\WINNT\Minidump\Mini072006-01.dmp.

Running Support Tools to analyze dump file ==>
Click to expand...


That's software related, out of context in hardware groups.

Turn off windows' "automatically reboot" setting. if it
still reboots, don't bother with dump files or any other
software *thing*.

Isolate when it reboots. Certain tasks, certain amount of
time, ambient temp, etc. Investigate these further
including inspection of system, voltage readings with a
multimeter, etc. Inspect motherboard, capacitors, etc, etc.

You've done very little to actually describe the problem
besides "reboots constantly".

You've failed to provide info about what "other analytical
tests" means. We might as well assume you have done no
testing whatsoever if you can't tell us enough to rule out
anything with the testing.

Forget the testing though, focus on basics. Don't set
windows to reboot then see if it still reboots.
 
Adam Smith said:
Hello,

Windows Professional 2000 on Pentium MMX vintage platform, new Hard
Drives, perfect NND and other analytical tests. Reboots constantly.
Click to expand...
Thanks
Click to expand...

Get a copy of memtest86+ from www.memtest.org .

Boot your system with the memtest86+ floppy or CD image, and
allow two complete passes. Is you memory error free ?
If a lot of errors are reported, test the memories one at
a time, and eliminate the bad one.

If Memtest86+ is clean, next step is to get a
copy of Prime95 from mersenne.org . This test runs
in Windows (or in Linux) and runs the CPU at 100% load.
If the computer crashes instantly when the Prime95
torture test runs, then it could be power. If the
program stops and reports an error, but the OS stays running,
then it could be either the processor or the memory.
(Prime95 is a better test for flaky memory, than
memtest86+ is. But memtest86+ has the advantage of being
able to test all bytes in the memory, and memtest86+ is
most valuable when there is a permanent stuck bit in the
memory. So both types of tests have value.)

Report back how your testing goes.

If you suspect a bad disk, there are other tests, like
the disk manufacturer's test programs, that can tell you
of problems there.

Paul
 
ExceptionCode. . . . .0x80000003
ExceptionFlags . . . .0x00000001
ExceptionAddress . . .0x80449d15
Click to expand...
What does this say to me, (yes they are octal addresses) ...
Click to expand...

Hexadecimal, actually.

Anyway, if your problem really is a software issue, then, according to
the URL below, the ExceptionAddress points to the errant process. Run
pstat.exe to identify the process or driver.

See http://support.microsoft.com/kb/192463/EN-US/

- Franc Zabkar
 
memtest86+ is
most valuable when there is a permanent stuck bit in the
memory.
Click to expand...

Even the BIOS memory sizing routine should find a permanent stuck bit.
IMO memtest86+ is good at finding intermittent RAM faults, especially
those associated with refresh problems.

- Franc Zabkar
 
I came across this on TechNet. Might help get you in the right
direction:

http://www.microsoft.com/technet/prodtechnol/Windows2000Pro/reskit/part7/proch33.mspx?mfr=true

Andy M
Click to expand...
Adam said:
Hello,

Windows Professional 2000 on Pentium MMX vintage platform, new Hard
Drives, perfect NND and other analytical tests. Reboots constantly.

Administrative tools ==> Bug check cause of event:Ex -
The computer has rebooted from a bugcheck. The bugcheck was:
0x00000050 (0xe40c7000, 0x00000000, 0xa000e77f, 0x00000001).
Microsoft Windows 2000 [v15.2195]. A dump was saved in:
C:\WINNT\Minidump\Mini072006-01.dmp.

Running Support Tools to analyze dump file ==>

C:\Program Files\Support Tools>C:\WINNT\Minidump\Mini072006-01.dmp
****************************************************************
**
** Windows 2000 Crash Dump Analysis
**
****************************************************************
*
Filename . . . . . . .C:\WINNT\Minidump\Mini072006-01.dmp
Signature. . . . . . .PAGE
ValidDump. . . . . . .DUMP
MajorVersion . . . . .free system
MinorVersion . . . . .2195
DirectoryTableBase . .0x031ea000
PfnDataBase. . . . . .0x818d7000
PsLoadedModuleList . .0x80481580
PsActiveProcessHead. .0x80483008
MachineImageType . . .i386
NumberProcessors . . .1
BugCheckCode . . . . .0x00000050
Click to expand...
Click to expand...

From the above URL:

Stop 0x00000050 or PAGE_FAULT_IN_NONPAGED_AREA

"This Stop message, also known as Stop 0x50, occurs when requested
data is not found in memory. The system generates a fault, which
normally indicates that the system looks for data in the paging file.
In this circumstance, however, the missing data is identified as being
located within an area of memory that cannot be read to disk. The
system faults, but cannot find, the data and is unable to recover.
Faulty hardware, a buggy system service, antivirus software, and a
corrupted NTFS volume can all generate this type of error."

Resolving the Problem

"Faulty hardware. Stop 0x50 usually occurs after the installation of
faulty hardware or in the event of failure of installed hardware
(usually related to defective RAM, be it main memory, L2 RAM cache, or
video RAM)."

- Franc Zabkar
 
Back
Top