R
J
JAD
wow all those versions of junk. please send all your memtest 'found to be
bad' modules to me.
bad' modules to me.
R
Richard Dower
JAD said:
I've found memtest to be a very good utility, it helps troubleshoot.
J
JAD
how can you diagnose a memory issue in the work piece that has a known
problem? Lots and lots of time spent for unreliable diagnosis. Try this: run
memtest and if you can put a load on the mains.
problem? Lots and lots of time spent for unreliable diagnosis. Try this: run
memtest and if you can put a load on the mains.
C
Conor
Hmm...
Two sticks of RAM. Run MEMTEST, note the location. Swap the sticks, run
again. Run it with one in and then the other.
R
Richard Dower
Conor said:
Exactly...it's called troubleshooting.
J
JAD
no one in the business of troubleshooting, tests components in a suspect
machine, its counter productive.
machine, its counter productive.
G
Guest
JAD said:
Real technicians do all the time, especially when another machine isn't
available. Only the less skilled can't do this.
J
JAD
ho hum................nice one?,,,,,,,,,,,,,,,,
C
Conor
ROFLMAO - clueless...
G
Guest
JAD said:
I strongly suspect you're not a real technician.
J
JAD
like I said HO HUM.....what you 'suspect' means nothing to me, anyone who
can support this 'junk thinking' is FAR from a tech, your just playing at
it.........Been in this forum for more years than you've been alive....how's
that for an assumption?
can support this 'junk thinking' is FAR from a tech, your just playing at
it.........Been in this forum for more years than you've been alive....how's
that for an assumption?
C
Conor
Been in a forum means **** all. Bench time is what counts and you've
got none.
And I doubt you've been here more years than I've been alive.
M
MaceFace
JAD said:
It's sometimes necessary, such as when the fault can't be duplicated
with any other machine or when there is no other machine. You'd know
that if you ever worked on something other than the most mundane
hardware, as a friend of mine has (some of that hardware is no longer
on this planet).
S
Shep©
Please explain?
How did it help you?
How long did it take to run it's tests?
How did you interpret the findings?
What conclusions did you draw?
Did you test all makes and models of RAM and mother board
configurations with the software to determine it's limitations?
These are a start.
Please answer inline as questions will be asked at the end of the test
;-)
S
Shep©
HahahahahahahaHah
You are joking aren't you?
S
Shep©
Medication still not working then,"Coner"?
C
Conor
You're as ****ing clueless as JAD then?HahahahahahahaHah
You are joking aren't you?
J
JAD
after you duplicate the fault 50 times, whats next?MaceFace said:
I have a friend who saw the first space launch, is he an expert of space or
the technology it took to get a man there? No. I once shot a model rocket
300 ft in the air, the radio transmitter I built and put in there, was
burned up.
Longevity....hmmm my first Overclocking was on a 12mhz 8086 and was
attempting a whopping 16 out of it. This involved much more than booting a
machine and enabling and disabling bios features and buying a premade
cooling solution. Besides the sentence was to provide an assumption example,
much like assuming I'm a tech of any kind in the first place. This
'troubleshooting procedure' of testing components in the suspect (or in
most cases, KNOWN , bad system) and using it to determine what component to
toss and what to keep is...well...its not done, it makes no sense. Your held
by financial restraints or the lack of connections....or not enough work to
end up with the occasional unpaid for mobo combo that you get stuck with to
use for testing, does not make this the correct thing to do.
Live in CA? send those modules this way...........
S
spodosaurus
Shep© said:
Saved me a **** of a lot of time reinstalling windows when the problem
was two bad memory modules on an old IBM system causing problems. Saved
the client money as well: cheaper to replace the modules and do a single
reinstall than keep messing around and eventually source the problem.
A couple hours, I always let it run for at least one complete pass, but
I prefer two as a minimum.
If it keeps finding errors in certain areas of the modules, pretty easy
to figure out that those areas ain't so crash hot anymore.
Time to replace the modules. In this case, though, the system was
ancient and this was enough to prompt the client to upgrade. She's never
been happier.
I presume IBM wouldn't **** around with customers by putting in RAM that
doesn't work right in their systems. You might, but then again, you're
not a multinational with a loyal client base and committment to reliability.
This is just one example. More recently it allowed me to diagnose a
problem in one of my systems from some RAM that was given to me but
obviously not handled properly: static had started the cascade of
failures. Then there was an even more recent issue where memory tested
fine in one system and faulty on a new motherboard. In fact, all memory
tested faulty on the new motherboard. Exchanged the board = happy camper.
--
spammage trappage: remove the underscores to reply
I'm going to die rather sooner than I'd like. I tried to protect my
neighbours from crime, and became the victim of it. Complications in
hospital following this resulted in a serious illness. I now need a bone
marrow transplant. Many people around the world are waiting for a marrow
transplant, too. Please volunteer to be a marrow donor:
http://www.abmdr.org.au/
http://www.marrow.org/