drcwils said:
Computer started rebooting on its own - i think the computer recently
installed Sp3 service pack but am not sure, some error messages would
include: registry corrupt - had to restore from previous backup, at
startup - overclocking failed select f1 to enter setup or f2 to select
default - (i didn't attempt to overclock), error reporting information
is as follows - WER46e3.dir00\Mini100207-03.dmp
\WER46e3.dir00\sysdata.xml these were in my document section under a
TEMP folder. All but one of my hard drive attachements and a floopy
combo drive are not recognized in explorer. I have read that it is
the Sp3 install that did it while Anti-virus was running, to its a
hardware issue from mobo to memory to cpu. Cpu is running 55-59
degrees with stock cooler. I have a Quad 6600 from intel. Mobo is Aus
P5K - memory is dominator 4 - 2G sticks with WinXp pro OS.
Has anyone run into something similar to this. I have thought about
backing up and reinstalling OS, I also have run a registry repair
software (StompSoft), I have tried the fix suggested by microsoft,
nothing is working. I am also not able to access sound card on mobo
along with other devices.
"overclocking failed select f1 to enter setup or f2 to select default"
That message is coming from the Asus BIOS. You don't have to be
overclocking, to see the message. The message can happen, because
of a computer crash or power failure, where the computer does not
shut down properly. On the next restart, the message may appear.
The Asus BIOS may also respond, by reducing settings to stock settings
for the CPU, so any applied overclock may be removed so the motherboard
can recover.
Is the computer running at stock speed ? Have you verified, via the
BIOS settings, that the computer is set up properly ?
The first test to run, would be a memory test. Memory does fail,
even when you take care of it. Try memtest86+ from memtest.org
and especially note the results from Test #5. That is where you
might first see memory errors. Allow the test to run for two
full passes as a minimum. Memtest86+ tests all but about 1MB
of memory (which is reserved space), so gives good test coverage.
What it lacks, is a strenuous enough test to highlight other
problems. No memory errors are acceptable. You want a computer
that can run memtest86+ forever, without reporting a problem.
It could be that your other symptoms are a side effect of bad memory.
Bad memory can cause the registry to be corrupted. And registry corruption
is not something that a registry cleaner can repair. A registry
cleaner can "remove" malformed entries, but the results may not
be sufficiently functional for the OS to be able to run properly.
Say it removes a whole hive for example - the OS may stop right there.
The registry cleaner may only add to your problems. It would work
best on a fully functional computer, not one with problems.
1) Make sure the memory is tested, before you do anything else.
No errors are acceptable. Replace the memory or use the warranty
provided with the memory, to get working memory.
2) Backup all data files. If you're reinstalling the OS, just about
anything can happen. Make sure your email database and other files
are some place safe.
3) Disconnect all drives not needed for the re-installation of Windows.
4) Reinstall Windows. Add SP3. Do Windows Update. Test. Is the system stable ?
Don't add the AV or plug in the other drive(s), until you've done
some basic testing. What you're doing in this step, is testing
the computer with stock Microsoft software present.
If the problem is processor stability, you can use Prime95 (mersenne.org)
to test for that. There is a "stress test" and the multithreaded version
of Prime95 can test all four cores. There is also a Linux version,
and if you boot a Linux LiveCD, you can do Prime95 testing from there.
(That way, it is possible to test the processor, before you install Windows.)
But preparing a Linux LiveCD is a 700MB download, so I didn't include
that in my list of test procedures above, because some people are
on dialup and cannot do such a large download and have it finish.
So the basic approach, is to test the computer hardware first. The
"Press F1" thing means there is a hardware problem of some sort.
It could be the result of crashing at the OS level. Or it could be
an actual hardware issue. Testing the memory and the CPU is how
you get some idea what you're dealing with.
You can also download a diagnostic for the hard drive, from the
hard drive manufacturers web site, but at this point, I don't see
any indication the hard drive is a cause of the problem.
Paul
