Subj : Re: Dell 780 Problem:
To   : All
From : nospam@needed.invalid
Date : Thu Jan 31 2019 19:16:25

Path:
eternal-september.org!reader02.eternal-september.org!feeder.eternal-september.o
rg!.POSTED!not-for-mail
From: Paul <nospam@needed.invalid>
Newsgroups: microsoft.public.windowsxp.general
Subject: Re: Dell 780 Problem:
Date: Thu, 16 Nov 2017 07:17:33 -0500
Organization: A noiseless patient Spider
Lines: 62
Message-ID: <oujvks$lqs$1@dont-email.me>
References: <7f18b466-63df-408a-bab7-4c3213a16544@googlegroups.com>
<oui2bc$1hg1$1@gioia.aioe.org>
<dc2e0772-a4b9-405b-81df-236f8eb3f8a0@googlegroups.com>
<oui89r$1q4a$1@gioia.aioe.org>
<d4d8a048-99c8-4220-b4df-0cb8ba8dccb2@googlegroups.com>
<d63d886d-434f-4c76-944f-0f84a037ff8d@googlegroups.com>
<ouihp0$jit$1@dont-email.me>
<c12efa5c-a5cc-4971-a440-8282b843278e@googlegroups.com>
<oujgdc$k54$1@dont-email.me>
<8345d835-0287-455c-97b6-6237156b2d5b@googlegroups.com>
<6aefd384-fdc4-4307-9162-6ac9652ff82e@googlegroups.com>
Mime-Version: 1.0
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 7bit
Injection-Date: Thu, 16 Nov 2017 12:17:32 -0000 (UTC)
Injection-Info: reader02.eternal-september.org;
posting-host="adef6719b56f5ef366e75a8307d0ab34";
 logging-data="22364"; mail-complaints-to="abuse@eternal-september.org";
posting-account="U2FsdGVkX18Tr3Gg1Fus6Sj9stV3eA9KBwk006Wnk54="
User-Agent: Ratcatcher/2.0.0.25 (Windows/20130802)
In-Reply-To: <6aefd384-fdc4-4307-9162-6ac9652ff82e@googlegroups.com>
Cancel-Lock: sha1:sObgkp+y9Mn8uzU80PhtMSmllu0=
Xref: feeder.eternal-september.org microsoft.public.windowsxp.general:134586

Mark Twain wrote:
> After re-boot Assessment 34521 ran it said 
> it needed to re-start the system and came 
> back with my normal sign-on page with icons
> and everything. 
> 
> So how do I proceed? replace this DIMM with
> the other? or put both in since it's now 
> working?
> 
> Thoughts/suggestions
> Robert

So it's not dead then. That's good news.

I'm not familiar with the response you're getting,
but it is an Optiplex, a "business" machine, and
maybe it's designed to detect the surreptitious
removal of hardware.

You haven't indicated the count of items, but
my test sequence would be:

1) Assume two DIMMs are present, one good, one defective.
2) Assume a four DIMM slot motherboard (two DIMM slots
    on each channel).

Take the "good news" DIMM, the one that worked, and test
it in each slot separately. This tells you which slots
work. That would be four test cases, with four power
removals, four boot cycles and so on. Maybe the snotty
message will appear on the screen four times too.

Now, say only one slot worked, and the other three
were dead. You could then take the (presumed-dead)
DIMM and put it in the one good slot. As a means
to test whether the bad DIMM is really bad or not.

You need to work out how many bad slots you have,
and how many bad DIMMs you have. You only need to
test enough slots, to get on with life - Paul would
test all four, but suit yourself. When I test new
computers here, it's an "epic undertaking" with
lots of test cycles.

If mixing the bad DIMM with a good slot yields
"no-workie", then you know the DIMM needs to be
replaced, or you might just run the machine with
the one DIMM. Those are your choices.

Once you know how many good slots you've got
and how many good DIMMs, you can plan accordingly.

But at least you've gotten a positive response
from your testing, and that's good news indeed.
No serious damage yet :-) A blown DIMM, you can
deal with. Replacing a motherboard wouldn't
be quite as much fun. I hate having to take
all that stuff out of the machine, to do one
of those.

    Paul
--- Platinum Xpress/Win/WINServer v3.1
 * Origin: Prison Board BBS Mesquite Tx  //telnet.RDFIG.NET www. (1:124/5013)

.