Diagnostic tools

  • Thread starter Thread starter Not Known
  • Start date Start date
N

Not Known

Hello,

What diagnostic tools do you guys run on your fresh built new PC's to check
for any issues?

Thanks
 
What diagnostic tools do you guys run on your fresh built new PC's to check
for any issues?

Simple technique: fire it up and if you see smoke you got a problem ;-)

Chris
 
Hello,

What diagnostic tools do you guys run on your fresh built new PC's to check
for any issues?

Thanks


Depends on what role the system plays in my PC army.

memtest86
Prime95
3Dmark (whichever version appropriate for video used)
Sisoft Sandra
AIDA32 (now called Everest)
HDTach
HDD manufacturer's Diagnostics
Large file copies, compression jobs, then file CRC checks.

Trying to fill PCI bus by throwing in a GbE adapter and
copying files from ramdisk or one drive while playing audio
and copying from a RAID controller or (depends on system)
other PCI device usage.

These kinds of tests apply to most systems, but specific
uses might also benefit from more specific tests of that
use, similar benchmarks and comparision to online
statistics. CRC checking is also one you'd want to do over
and over, not assuming it's OK if it passes once or twice.

Personally I test with memtest86 while the memory bus is
overclocked (or overclocked even more than my plan if i'd
planed to overclock a box) to give even higher margin, or
catch the rare error scenarios where it's just barely stable
or doesn't have errrors that show up as readily in memtest
as they would in real-world uses, even booting windows can
sometimes turn up on a box that passes memtest86, but often
it's because memtest86 didn't run long enough, a few hours
is a very short time to test a box with 512MB of memory or
more.

If the box is going to be used at something that'll keep it
near or at full load continuously, I also take temp readings
of inside after extended load, not just relying on a (chip)
system temp reading, and often o'c the CPU a little extra to
confirm that it, like memory, isn't running right at the
edge of stabilty then back it down a notch from a
tested-stable speed, for it's everyday running speed. I'd
do so even if I only planned to run it at stock speed.
More o'c and temp tests also if video card is o'c or case
has limited cooling ability for (whatever) reason, including
someone specifying their home as no AC and summertime is
expected to significantly raise ambient temps... system need
be stable at max ambient temp possible per environment it's
used in, not just an ideal temp. Also account for a few
degrees rise from dust buildup, a non-aficionado may not be
diligent in dusting out their system on a timely basis, and
some of the newer cases with filtered intake have lower flow
to begin with, may have problems after a few months in dusty
environments... plan for the worst (reasonably) possible
environement.

Then there's other things like touch-testing capacitors at
that extended full-load event to see if they're staying
relatively cool... some boards just aren't built for a good
service life with the upper speed CPUs they're spec'd to
run, especially when a board was released during earlier
lower speed CPUs and only officially supports the faster
ones with a bios update, then often it's the case that it's
not really designed to handle so many amps, it may work but
not be as robust as a later contemporary board.

This is not an exhaustive list, basically there's a lot of
little things we overlook after doing them for awhile, or
familiarlity with some, same aspects might cut down on
testing and scrutiny, but basic things like memtest86, CRC
tests, temp measurements, should always be used... nothing
worse than trying to troubleshoot a problem and not even
knowning if there are logical errors.
 
kony said:
Depends on what role the system plays in my PC army.

<snipped informative reply>

A little more specific, how would I test external cache ? Maybe I'm
barking up the wrong tree, but here's the setup I'm currently trying
to figure out:

PI 166mhz, Acer ACR19E00 mobo with ALi M1521 (HX-Pro)
chipset and 64mb RAM. For some reason the machine seems to be
running way slower than it should and even hangs up for quite a while
on the slightest whim. I've clean installed Win98, run memtest86 (for
about 7 hours), tested the hard drive and also ran a 6 hour CPU test
with "hotCPU" (free version - which does not test L1 or L2). All came
up clean. Win98 seems to have the necessary mobo drivers and a web
search for these was fruitless. I'm running out of ideas.

TIA
 
<snipped informative reply>

A little more specific, how would I test external cache ? Maybe I'm
barking up the wrong tree, but here's the setup I'm currently trying
to figure out:

PI 166mhz, Acer ACR19E00 mobo with ALi M1521 (HX-Pro)
chipset and 64mb RAM. For some reason the machine seems to be
running way slower than it should and even hangs up for quite a while
on the slightest whim. I've clean installed Win98, run memtest86 (for
about 7 hours), tested the hard drive and also ran a 6 hour CPU test
with "hotCPU" (free version - which does not test L1 or L2). All came
up clean. Win98 seems to have the necessary mobo drivers and a web
search for these was fruitless. I'm running out of ideas.


Look at exactly what it's doing when it hangs, try to find a
commonality. It's a bit hard to expand from there, many
possibilities from HDD not using DMA to virus to damaged IDE
cables to insufficient memory for tasks or even old buggy
software or drivers. There were a few old L2 cache test
programs but I don't recall the name of them, a Google
search should find some.
 
jona:
PI 166mhz, Acer ACR19E00 mobo with ALi M1521 (HX-Pro)
chipset and 64mb RAM. For some reason the machine seems to be
running way slower than it should and even hangs up for quite a while
on the slightest whim. I've clean installed Win98, run memtest86 (for
about 7 hours), tested the hard drive and also ran a 6 hour CPU test
with "hotCPU" (free version - which does not test L1 or L2). All came
up clean. Win98 seems to have the necessary mobo drivers and a web
search for these was fruitless. I'm running out of ideas.

A few years ago I was stuck with a 166Mhz machine with 64MB ram, running
Win95, at work (yes really). All I used it for was email, Word and Excel
and it was slow as hell. I bitched long and loud until it was replaced
with a something more modern but in the meantime I bumped the memory to
128MB and overclocked the CPU to 233Mhz and it felt twice as fast.

I've purged most of what I knew about older machines and Win 95/98 from
my brain, but you may want to check what mode the drives are running in
(should be Ultra DMA not PIO), defrag the hard drive and run some
benchmarks to determine objectively if the machine is slower than it
should be.

You might take a look at this:
http://www.majorgeeks.com/download3846.html
 
Thanks guys



Mac Cool said:
jona:

A few years ago I was stuck with a 166Mhz machine with 64MB ram, running
Win95, at work (yes really). All I used it for was email, Word and Excel
and it was slow as hell. I bitched long and loud until it was replaced
with a something more modern but in the meantime I bumped the memory to
128MB and overclocked the CPU to 233Mhz and it felt twice as fast.

I've purged most of what I knew about older machines and Win 95/98 from
my brain, but you may want to check what mode the drives are running in
(should be Ultra DMA not PIO), defrag the hard drive and run some
benchmarks to determine objectively if the machine is slower than it
should be.

You might take a look at this:
http://www.majorgeeks.com/download3846.html
 
kony said:
Look at exactly what it's doing when it hangs, try to find a
commonality. It's a bit hard to expand from there, many
possibilities from HDD not using DMA to virus to damaged IDE
cables to insufficient memory for tasks or even old buggy
software or drivers. There were a few old L2 cache test
programs but I don't recall the name of them, a Google
search should find some.

Been out of town for a coupla days - late reply.
Ruling out virus, and buggy software or drivers since it was a
fresh win98 install, I downloaded a few cache utilities (mainly
DOS based) and got varied results, most of which didn't really
enlighten me. Well, not directly... "nucache" told me that it was
not a pentium processor at all. PCwizard (as suggested by one
other poster) gave me a 'SMBios/DMI error' and "cachechk"
reported everything OK (I think). Anyway, at one stage the
floppy decided not to work in DOS mode at which point my
attention was drawn to the underpowered PSU (145W) and
ultimately the fact that the mobo wouldn't let me up the CPU
clock from 66 to 75 mhz, made me dump the board and CPU
for another. Fortunately I have quite a few discards laying around.
I consider fart-assing around with old hardware/systems a means
to help out folks who can't afford new computers as well as a part
of my learning curve, albeits, a fustrating one at times. So what
did I learn this time round ? Nothing really, except maybe that
the CPU should rather be one of the first items on my check list.

Thanks for your and 'Mac Cool's' input.
 
Back
Top