(e-mail address removed) wrote
A complete check takes a long while indeed. But in over
90% of the cases, if the ram is bad, it will be obvious
within 5 minutes. Often times, i do abort the test early.
Still makes a lot more sense to check for bad caps and
bad power supply first, because bad memory should have
been obvious before the fault showed up, and if it wasnt,
you're going to need the longer run to see marginal memory.
And it isnt due to the memory going bad either,
it will be due to the motherboard not liking the
ram. It will work fine in a different system.
Nope, no assumption what so ever. Just checking the
possibilitys that are likely to be uneconomic to fix first
so a minimum time is wasted on those systems which
are going to be discarded.
Its only worth checking jumpering if its very likely that
the system will be economic to repair and the fault has
been identified and you want to ensure that the system
setup properly once the fault has been identified and fixed.
If I don't check, I never will. You see the problem?
Not UNTIL the fault has been identified and fixed and you are
ensuring that there arent any other minor problems still extant.
Sorry, but just because an application isn't CPU
intensive does NOT mean the CPU won't overheat.
Minor dust wont see the cpu overheat when running that diag.
Yes, once the fault has been identified and fixed it is THEN
worth doing some checks that the system doesnt have any
other outstanding problems and the best way to do that is
to monitor the cpu temp while running something cpu intensive
to check the basics like whether the heatsink and fan have
been installed properly etc.
Pointless doing that until the fault has been identified and
its clear that the system is economic to fix and that the
owner isnt going to use the fault as a good excuse to
do what its been intending to do for a while now, just
replace the system with a new one, with someone else
needing to be convinced that the new system is justified etc.
And Seatools DOES make demands on the CPU.
Like hell hit does cpu heating wise.
No assumption what so ever. It doesnt happen.
Pathetic excuse for mindless bullshit.
It accumulates heaviest on fans, and heatsinks to be sure. But
believe me, it does accumpulate on caps and every other place too.
Like hell it does.
You can spot slighter bulges, when they're clean.
Mindlessly silly.
You're wrong. The vast bulk of what is claimed to be bad ram is ram
that that motherboard doenst like much or which the motherboard hasnt
been configured for properly and which works fine in a different system.
Efficient? Half-assed is closer.
Never ever could bullshit its way out of a wet paper bag.
Nothing half arsed about initially assuming that the user isnt
a fool and only checking something like that if it looks like the
system is fine and the problem is just that the user didnt wait
long enough. When it spontaneously reboots and chkdsk locks
up, its MUCH more likely that the diag is locking up too.
AND you dont gain a damned thing by proving that the user
didnt wait long enough with the diag if its still locking up when
chkdsk is run and its still spontaneously rebooting anyway.
Its an irrelevant detail of no significance what so ever.
Hence: visual inspect first.
Pity you never said that initially, just now when your nose has
been rubbed in your terminally stupid approach to fault finding.
I put this last for more than 1 reason:
1) It's a pain in the ass to get the proper bios in a lot of cases.
Not in the particular case being discussed.
2) Small (but not zero) chace of rendering the computer
non-bootable. Not something to do "just because".
Pity you said you do that anyway with this particular motherboard.
Cant even manage a consistent line in mindless bullshit.
I don't want to have to tell a cuntomer that i accidently toasted the BIOS.
Pity you said you do that anyway with this particular motherboard.
Cant even manage a consistent line in mindless bullshit.
You have GOT to have good ram to do
a bios flash, or you're taking a big risk.
Bullshit.
I argree, which is why it's low on the list.
Shouldnt even be on the list at all with that set of symptoms
unless every other possibility has been carefully eliminated
and the only alternative is to discard the system or replace
the motherboard.
Yes I do, Bios flashing is not something to take lightly. You want to
maximise the chance of sucess by mimising potential for bad outcome.
Mindlessly silly with normal dust levels.
I didn't tell you my usual method before. You assumed.
Like hell I did, I read what you posted to the OP.
Not a shred of assumption involved whatever.
That's a bad trait in a supposed technician.
Having fun thrashing that straw man are you child ?
And a constant failure of yours: assumptions.
Not a single assumption what so ever.
Just your pathetic excuse for bullshit/lies.
Yep.
Machine is already off, time is wasted powering up a machine
to check for logs, when there is an inspection to complete.
Mindlessly silly when the event logs are very likely to have useful
information in them and should have been checked first anyway.
It takes only seconds, thirty at most. Booting can
take minutes. In due time the machine will be booted.
Makes a hell of a lot more sense to boot the system first
before even bothering to open it to check the event logs.
Another reboot cycle lost.
Taint lost a thing if the system performs fine in that config.
We can get to windows to check that shit AFTER.
Anyone with a clue does that first with those symptoms,
after the event logs and a check for bad caps.
That's a good thing to try at some point, but, the
problem is with the hard drives, concetrate there first.
Not a shred of evidence of any problem with any hard drives.
Even someone as stupid as you should have noticed that
the symptoms didnt change with two different hard drives.
Not a GREAT deal difference here.
Wrong. Its a hell of a lot easier to check for fans spinning.
As long as they're checked before it's booted into Windows.
Mindlessly silly. Thats what should be done first.
A detemination to make later.
Pity you claimed they need to be dealt with. Not necessarily.
Not yet. Especially for very occasional freezes and hangs.
Pity the OP didnt say that. And that is why the system should
be booted first, to see what the freeze and hang rate is.
You can wait hours for something to happen.
Pointless if the boot logs dont indicate anything useful and
the system worked fine while they were being inspected.
Makes a hell of a lot more sense to check for
bad caps next if the event logs arent useful.
If you're gonna spend hours waiting,
Only a fool would be stupid enough to do that.
you may as well spend it on something productive.
Pointless wasting your time on jumpers and ribbon
cables at that stage with a fault that is rarely seen.
The other real possibilitys should be elimated first,
particularly a quick check for bad caps because it
wont usually be economic to do anything more to
the system if its got bad caps.
You can't eliminate hard drive failure
until you actually test the hard drives.
Pointless testing the sound system too when
changing the drive made no difference.
Otherwise, it's being half assed.
Crap, yours is a completely stupid way to fault find
when another drive makes no difference and there
isnt a shred of evidence of any hard drive fault.
Nope, not a single assumption what so ever involved.
Just understanding what can cause particular symptoms.
It's not efficency, it's plain laziness and willful neglect.
Thanks for that completely superfluous proof that you wouldnt know
what effective fault finding was about if it bit you on your lard arse.
No surprise that no one is actually stupid enough
to employ you to fault find commercially.
Since visual inspection IDENTIFIES the most common
non-economical fault: bad caps, it's worth always doing first.
Nope, not when the fault cant be due to bad caps.
You can save a 2+ hour virus removal
project, if you would just open up the case.
You dont even need to open the case at all
if the event logs identify a software problem.
My computers STAY fixed, do yours?
Yep. And I dont waste time on systems that are going to be discarded.
When most faults that arent fixed by a power supply fault get discarded
if they are a hardware problem, its important to work out whether its
going to be economic to fix first. And that means working out whether
its actually a hardware problem at all first, and then whether its going
to be economic to fix next. Its only worth checking the other stuff like
the jumpers and cables and whether the heatsink is installed properly
etc once the fault has been identified and fixed and the system will
be returned to the owner.
)