Adding DDR3 Memory, Compatible With Existing

On Mon, 28 Jul 2014 15:30:57 +0100, Mark
wrote:

Here you can return something (by law) if you don't want it (distance
selling only) for around 10 days. Some stores have a 'better' policy
than this. If the product is faulty or unsuitable then you generally
have longer.

I range often between 3 days, 10, 45, or No Days. (Flea)Ebay, where
some merchants provide a Dirty Harry Sales Policy: "Do you feel lucky,
punk?"

Can get as bad as even methods of payment - Depending, with some
outfits - file a dispute, express dissatisfaction - Fine! (our policy
is): "We'll cancel your membership, won't answer calls/inquires and
will ignore you." Read our fine print: "Getting on your knees for
forgiveness is entirely an optional consideration."

Try making a complaint about SKYPE's automated billing CC deductions
sometime.

On Mon, 28 Jul 2014 11:37:37 -0400, Flasherly
wrote:

On Mon, 28 Jul 2014 15:30:57 +0100, Mark
wrote:

Here you can return something (by law) if you don't want it (distance
selling only) for around 10 days. Some stores have a 'better' policy
than this. If the product is faulty or unsuitable then you generally
have longer.

I range often between 3 days, 10, 45, or No Days. (Flea)Ebay, where
some merchants provide a Dirty Harry Sales Policy: "Do you feel lucky,
punk?"

Can get as bad as even methods of payment - Depending, with some
outfits - file a dispute, express dissatisfaction - Fine! (our policy
is): "We'll cancel your membership, won't answer calls/inquires and
will ignore you." Read our fine print: "Getting on your knees for
forgiveness is entirely an optional consideration."

Try making a complaint about SKYPE's automated billing CC deductions
sometime.

I don't use Skype :-)
--
(\__/) M.
(='.'=) If a man stands in a forest and no woman is around
(")_(") is he still wrong?

On Wed, 30 Jul 2014 14:47:44 -0400, Flasherly
wrote:

How's calling the boiler room at Dish NetWorks for potential customer
relations at a $19 monthly INET service advertisement come-on sound?

or just move it on over in Boondocksville

http://www.itbusinessedge.com/blogs/...ors_picks=true

Hey all... dunno if you remember me (this thread really topic-drifted). I had the Corsair Vengeance RAM that wouldn't run in either of two mobos.
I threw up my hands and RMAed the RAM back to The Egg. Just got the replacements, and they've been cooking for 1:40:58 now on Memtest86+, no errors, into the third pass.
So I guess it was a random QC problem, but...

When I got the first modules, I tried combining them with the 2GB modules that were already on the board hoping for 12GB. Didn't POST, so tried them by themselves with no success either.
Could that possibly have damaged them? I would hope that the worst thing that could happen from memory incompatibility would be just not working.
It's been fairly humid here, so don't think static killed them either.

Do I dare go for 12GB by putting the old modules into the empty slots?

Flasherly wrote in
:

On Wed, 30 Jul 2014 14:47:44 -0400, Flasherly
wrote:

How's calling the boiler room at Dish NetWorks for potential customer
relations at a $19 monthly INET service advertisement come-on sound?

or just move it on over in Boondocksville

http://www.itbusinessedge.com/blogs/...es-versus-feds
-on-municipal-broadband.html?google_editors_picks=true

On Wed, 13 Aug 2014 00:44:53 GMT, cropduster
wrote:

It's been fairly humid here, so don't think static killed them either.

Do I dare go for 12GB by putting the old modules into the empty slots?

Only way memory is damaged is overclocking it. Memory may show up
together, although may have to pull it back out if it's unstable and
won't test. There's only so many slots and ways to combine them -
sometimes a combination from that set might take, other times not.

cropduster wrote:
Hey all... dunno if you remember me (this thread really topic-drifted). I had the Corsair Vengeance RAM that wouldn't run in either of two mobos.
I threw up my hands and RMAed the RAM back to The Egg. Just got the replacements, and they've been cooking for 1:40:58 now on Memtest86+, no errors, into the third pass.
So I guess it was a random QC problem, but...

When I got the first modules, I tried combining them with the 2GB modules that were already on the board hoping for 12GB. Didn't POST, so tried them by themselves with no success either.
Could that possibly have damaged them? I would hope that the worst thing that could happen from memory incompatibility would be just not working.
It's been fairly humid here, so don't think static killed them either.

Do I dare go for 12GB by putting the old modules into the empty slots?


Give it a try.

There were a couple of motherboard or memory issues, that
could damage RAM. There were the motherboards that supported
two memory types at the same time, and the memory operated
off different voltages, where there could be a damage issue.
(Some of those relied on the user to set a voltage jumper.)

There was also the FPM/EDO era, where mixing FPM and EDO
sticks might cause bus contention.

The single slot type, advanced memory designs now are pretty safe.
All modules run the same timing. The controller knows what phase
it is in, so should not overlap data phases, causing contention.

The only remaining thing, is thermal. Depending on the coolers,
and the slot spacing, sometimes installing DIMMs in all four
slots, makes the cooling worse. One system here, I decided to
run four sticks, and lost a stick about a month later, and it
could have been the heat. On my current system, I have a fan
blowing down on the RAM area, as I checked the surface temperature
with my finger and decided it could use a bit of cooling. For
some reason, my current modules run warmer than the old ones.
The VDimm is not boosted, and neither is the clock out of
spec for the modules - they're not in an enthusiast setup
by any means. So why they're warmer is a bit of a mystery.
My current setup with four sticks, has been that way for a
year or so.

So I would just try it, stick a finger on the modules
while running, to see if they're getting overly hot.
Don't forget to power off completely (pull plug on PSU),
before modifying the memory setup. As the presence of
+5VSB, keeps voltages present in the RAM slots. You don't
want any power in the RAM slot, when plugging in the DIMM.

If you've tested both pairs of modules separately,
that should build your confidence for the 12GB test.

Paul

On Wed, 13 Aug 2014 01:12:04 -0400, Paul wrote:

The single slot type, advanced memory designs now are pretty safe.
All modules run the same timing. The controller knows what phase
it is in, so should not overlap data phases, causing contention.

There's only a few nasty practicing buggers out there...

A common misuse is to write information to certain memory regions to
bind vendor-specific memory modules to a specific system. Fujitsu
Technology Solutions is known to do this. Adding different memory
module to the system usually results in a refusal or other
counter-measures (like pressing F1 on every boot). -wiki

Most, a non-anal industry interesting in actual business, should
follow suit and be within a SPD memory base ID ROM - standardized I/O
for BIOS ID memory detection, per se, to a system-go bootstrap routine
sequence on 99.9% of all MBs .