I've come across this twice in the last 2 wks. I added a
RAM module (512MB) to my father-in-law's Gateway and
after the install WinXP Home acts strange, i.e. it resets
itself (over and over). I finally resolved that issue,
but not entirely sure how I did it.

I tried to add a 256MB module to my Dell XPS T450 and
although the motherboard recognizes it, once again Win XP
(PRO for me) won'd load and resets. I removed the module
and replaced it w/ the old one 64 MB :-( and it's up and
running again.

Does anyone have an idea why this happens and what can I
do about it? I'd really like to install the larger
module.

Hello

When ever you add memory make sure that it is the same
speed, trying to mix different ram in your pc will cause problems
and one more thing make sure that your using ram that meets
your pc spec's, it may help to read your manual read.

Alvin


peter wrote:

> I've come across this twice in the last 2 wks. I added a
> RAM module (512MB) to my father-in-law's Gateway and
> after the install WinXP Home acts strange, i.e. it resets
> itself (over and over). I finally resolved that issue,
> but not entirely sure how I did it.
>
> I tried to add a 256MB module to my Dell XPS T450 and
> although the motherboard recognizes it, once again Win XP
> (PRO for me) won'd load and resets. I removed the module
> and replaced it w/ the old one 64 MB :-( and it's up and
> running again.
>
> Does anyone have an idea why this happens and what can I
> do about it? I'd really like to install the larger
> module.

"peter" <(E-Mail Removed)> wrote in message
news:008d01c377df$01c0f0e0$(E-Mail Removed)...
> I've come across this twice in the last 2 wks. I added a
> RAM module (512MB) to my father-in-law's Gateway and
> after the install WinXP Home acts strange, i.e. it resets
> itself (over and over). I finally resolved that issue,
> but not entirely sure how I did it.
>
> I tried to add a 256MB module to my Dell XPS T450 and
> although the motherboard recognizes it, once again Win XP
> (PRO for me) won'd load and resets. I removed the module
> and replaced it w/ the old one 64 MB :-( and it's up and
> running again.
>
> Does anyone have an idea why this happens and what can I
> do about it? I'd really like to install the larger
> module.

1. The specifications of all the memory modules must
match, except for size. Usually it's OK if just the speed
and CAS latency (CL=2 or CL=3) match.

2. It must be the correct memory for your computer. Use
Crucial's memory configurer at http://www.crucial.com
to check.

3. The memory must work. Download memtest86 from
http://www.memtest86.com and run it for a few passes
to check it out. You should get zero errors.

4. Don't buy "generic" memory. Get one of the top brands
such as Crucial, Kingston or Corsair. Watch out: even
some brand name memory, such as Azen, is generic
memory with a label stuck on it.

-- Bob Day

"Bob Day" <(E-Mail Removed)> wrote in message
news:OLccFh%(E-Mail Removed)...
> "peter" <(E-Mail Removed)> wrote in message
> news:008d01c377df$01c0f0e0$(E-Mail Removed)...
> > I've come across this twice in the last 2 wks. I added a
> > RAM module (512MB) to my father-in-law's Gateway and
> > after the install WinXP Home acts strange, i.e. it resets
> > itself (over and over). I finally resolved that issue,
> > but not entirely sure how I did it.
> >
> > I tried to add a 256MB module to my Dell XPS T450 and
> > although the motherboard recognizes it, once again Win XP
> > (PRO for me) won'd load and resets. I removed the module
> > and replaced it w/ the old one 64 MB :-( and it's up and
> > running again.
> >
> > Does anyone have an idea why this happens and what can I
> > do about it? I'd really like to install the larger
> > module.
>
> 1. The specifications of all the memory modules must
> match, except for size. Usually it's OK if just the speed
> and CAS latency (CL=2 or CL=3) match.
And, of course, the type: SDRAM, DDR, RDRAM, etc.
-- Bob Day

>
> 2. It must be the correct memory for your computer. Use
> Crucial's memory configurer at http://www.crucial.com
> to check.
>
> 3. The memory must work. Download memtest86 from
> http://www.memtest86.com and run it for a few passes
> to check it out. You should get zero errors.
>
> 4. Don't buy "generic" memory. Get one of the top brands
> such as Crucial, Kingston or Corsair. Watch out: even
> some brand name memory, such as Azen, is generic
> memory with a label stuck on it.
>
> -- Bob Day
>
>

"peter" <(E-Mail Removed)> wrote:

>I've come across this twice in the last 2 wks. I added a
>RAM module (512MB) to my father-in-law's Gateway and
>after the install WinXP Home acts strange, i.e. it resets
>itself (over and over). I finally resolved that issue,
>but not entirely sure how I did it.
>
>I tried to add a 256MB module to my Dell XPS T450 and
>although the motherboard recognizes it, once again Win XP
>(PRO for me) won'd load and resets. I removed the module
>and replaced it w/ the old one 64 MB :-( and it's up and
>running again.
>
>Does anyone have an idea why this happens and what can I
>do about it? I'd really like to install the larger
>module.

Windows can be very very fussy about RAM.

If you use RAM from different manufacturers, or even from the same
manufacturer but different production lots then there can be
differences in the internal layout and/or the material composition of
the RAM modules.

These differences affect the strength and the timing of the signals
returned from the RAM, and Windows is sensitive to these differences.

If you encounter a problem when adding RAM to a computer you should:

1. Run the computer with just the old RAM installed and verify that it
is working properly.

2. Run the computer with just the new RAM installed and verify that it
is working properly. A problem at this stage indicates that the new
RAM is either defective or is not compatible with your computer.

3. If both modules work okay when used by themselves then try again
with both modules installed. If there are problems then that is
pretty conclusive that the two modules are not compatible with each
other and cannot be used in the same computer.

There is no cure for this. The solution is to replace one or both
modules so that you have a matched set.

Good luck


Ron Martell Duncan B.C. Canada
--
Microsoft MVP
On-Line Help Computer Service
http://onlinehelp.bc.ca

"The reason computer chips are so small is computers don't eat much."

Greetings --

It's absolutely essential that any new RAM module be compatible
with both the motherboard and any other RAM module(s) in the system.
Additionally, there are sometimes jumper switches on older
motherboards that need to be reset for the new RAM configuration.
Consult your motherboard's manual.


Bruce Chambers

--
Help us help you:
http://dts-l.org/goodpost.htm
http://www.catb.org/~esr/faqs/smart-questions.html

You can have peace. Or you can have freedom. Don't ever count on
having both at once. -- RAH


"peter" <(E-Mail Removed)> wrote in message
news:008d01c377df$01c0f0e0$(E-Mail Removed)...
> I've come across this twice in the last 2 wks. I added a
> RAM module (512MB) to my father-in-law's Gateway and
> after the install WinXP Home acts strange, i.e. it resets
> itself (over and over). I finally resolved that issue,
> but not entirely sure how I did it.
>
> I tried to add a 256MB module to my Dell XPS T450 and
> although the motherboard recognizes it, once again Win XP
> (PRO for me) won'd load and resets. I removed the module
> and replaced it w/ the old one 64 MB :-( and it's up and
> running again.
>
> Does anyone have an idea why this happens and what can I
> do about it? I'd really like to install the larger
> module.