adding ram and windows problem

[halex2000]

Hi all, I want to add 512Mb of ram to my 512Mb equipped PC but I've had a
problem: first I bought an economic brand (different to the kingston I
already have). PC recognizes them on startup, but windows xp refuses to run:
first the pc reboots when it begins to load the OS, then some text appears
telling me that a problem occoured last time and asks me to choose which
mode to run. It doesn't matter which one I choose, it always fails to load
and the pc reboots. Then I thought these two memories where incompatibles,
and took the expensive kingston: exactly the same problem.
Is there a way to make windows run properly without having to reinstall it
(I cannot do that right now)?

 

[Joel]

Hi all, I want to add 512Mb of ram to my 512Mb equipped PC but I've hada
problem: first I bought an economic brand (different to the kingston I
already have). PC recognizes them on startup, but windows xp refuses torun:
first the pc reboots when it begins to load the OS, then some text appears
telling me that a problem occoured last time and asks me to choose which
mode to run. It doesn't matter which one I choose, it always fails to load
and the pc reboots. Then I thought these two memories where incompatibles,
and took the expensive kingston: exactly the same problem.
Is there a way to make windows run properly without having to reinstallit
(I cannot do that right now)?

I dunno why but most people with problem often leave some of the most
important (detail) information in their questions <bg>

1. Make sure to have the memory sticks right next to each other, and start
with the lowest bank #'s (I dunno if they still use this term or not
but BANK #'s was the term I learned about 3 decades ago when I first
started computing). Or insert the newer right next to the older.

2. Reboot the system and I am not mistaken (have been doing so many timesso
often not paying attention to the same process) the system will boot to
CMOS setting (probably that's what I say you saw) telling you that it
detects newer change (or additional memory), and you just need to
CONFIRM it by selecting option "SAVE & EXIT"

It will exit CMOS setting window with the newer information saved and
pass to Windows or any OS (Operating System). And I am guessing the
reason Windows refuses to boot/continue because it smells something ain't
right and you refuse to confirm something new has added to system.

3. If #2 isn't the case, then you may need to SWAP the memory stick around,
or make sure they have good connection.

Well, I guess that's about all I have in my mind at the moment... and I
may need to break to think about what I am going to do with my problem <bg>

 

[halex2000]

Thank you for answering. I think I've given all the relevant infos, but if
you think that something misses, ask me please.
One thing (that I didn't mention because it shouldn't be source of problems)
is that one is DDR 333Mhz, the other DDR 400Mhz. But the fast one will run
at 333Mhz without me to specify it manually, won't it?

1. Make sure to have the memory sticks right next to each other, and start

They told me that if 4 slots are available, then they are grouped by two and
one of the modules goes on the first pair, while the second in the other. I
will try to put them in the same group.

system will boot to
CMOS setting (probably that's what I say you saw) telling you that it
detects newer change (or additional memory), and you just need to
CONFIRM it by selecting option "SAVE & EXIT"

No, it doesn't. I add the ram, then I rebot and it performs the memory check
on the whole Gb. No settings, no confirmations...

and you refuse to confirm something new has added to system.

I was not asked to confirm anything.

3. If #2 isn't the case, then you may need to SWAP the memory stick around,

or make sure they have good connection.

I checked in both orders. And even the newer alone, which works...

Thank you again,
Alessandro

 

[Pen]

I dunno why but most people with problem often leave some of the most
important (detail) information in their questions <bg>

1. Make sure to have the memory sticks right next to each other, and start
with the lowest bank #'s (I dunno if they still use this term or not
but BANK #'s was the term I learned about 3 decades ago when I first
started computing). Or insert the newer right next to the older.

2. Reboot the system and I am not mistaken (have been doing so many times so
often not paying attention to the same process) the system will boot to
CMOS setting (probably that's what I say you saw) telling you that it
detects newer change (or additional memory), and you just need to
CONFIRM it by selecting option "SAVE & EXIT"

It will exit CMOS setting window with the newer information saved and
pass to Windows or any OS (Operating System). And I am guessing the
reason Windows refuses to boot/continue because it smells something ain't
right and you refuse to confirm something new has added to system.

3. If #2 isn't the case, then you may need to SWAP the memory stick around,
or make sure they have good connection.

Well, I guess that's about all I have in my mind at the moment... and I
may need to break to think about what I am going to do with my problem <bg>

The new memory is either defective or incompatible. Check at crucual.com
for what you really need.

 

[halex2000]

I tried to put both sticks in the same pair, but nothing happened. If I try
to get access to the bios, the system halts (doesn't respond to keyboard).

 

[halex2000]

The new memory is either defective or incompatible. Check at crucual.com

for what you really need.

I own a Giga-Byte GA-7N400E and the new memory is a Kingston PC3200 400Mhz.
If used with the new ram alone, the system runs without issues. Both are
kingston, I don't see why I should have incompatibility problems. I've
already spent 120? and nothing changed, did somebody already faced this
problem?

Thank you anyway.

 

[Shep©]

Hi all, I want to add 512Mb of ram to my 512Mb equipped PC but I've had a
problem: first I bought an economic brand (different to the kingston I
already have). PC recognizes them on startup, but windows xp refuses to run:
first the pc reboots when it begins to load the OS, then some text appears
telling me that a problem occoured last time and asks me to choose which
mode to run. It doesn't matter which one I choose, it always fails to load
and the pc reboots. Then I thought these two memories where incompatibles,
and took the expensive kingston: exactly the same problem.
Is there a way to make windows run properly without having to reinstall it
(I cannot do that right now)?

Unfortunately when it comes to memory changes the BIOS,"Auto Detect"
doesn't always get it right because of the incorrectly hardware coded
bios chip on the ram(SMD).

Case in point new build for myself.

Two different brands on PC3200 512 meg of ram.Both labeled as cas 2.5
DDR 200/400 Mhz.

With auto-detect in the BIOS system will not boot with both sticks
in.Will boot with either in separately at 2.5/200X2.
This is in either single mode or dual interleave when both sticks in.

Got system working in both single and dual interleave(AMD system) by
manually setting speed to 166 and cas 3 when both sticks in.Now I've
lost the 200 Mhz speed and the cas 2.5 but because they are now
working at 1gig in dual interleave mode this is way faster than none
DI mode so I can live with that and the fact I have a full 1 gig of
ram running in Dual Interleave.Would be nice to have them both running
at 2.5/200/400 but what they hey,the sticks were cheap


Note:With each successive RAM boot failure I/you have to clear the
CMOS with the power isolated from the system because when it comes to
ram the CMOS stores corrupt/incorrect data that can only be cleared
this way as there's a charge left in the CMOS if there's power to the
mother board and you have to re-enter the settings in the BIOS
manually.

Now this is for this board but I've had to do this when fitting
mis-matched ram on many boards.

If at all possible use matched ram from the same maker(Even that is
not 100% guaranteed).This doesn't confuse the BIOS so much.

If this luxury is not available see above.

 

[halex2000]

Unfortunately when it comes to memory changes the BIOS,"Auto Detect"
doesn't always get it right because of the incorrectly hardware coded
bios chip on the ram(SMD).

Case in point new build for myself.

Two different brands on PC3200 512 meg of ram.Both labeled as cas 2.5
DDR 200/400 Mhz.

With auto-detect in the BIOS system will not boot with both sticks
in.Will boot with either in separately at 2.5/200X2.
This is in either single mode or dual interleave when both sticks in.

Got system working in both single and dual interleave(AMD system) by
manually setting speed to 166 and cas 3 when both sticks in.Now I've
lost the 200 Mhz speed and the cas 2.5 but because they are now
working at 1gig in dual interleave mode this is way faster than none
DI mode so I can live with that and the fact I have a full 1 gig of
ram running in Dual Interleave.Would be nice to have them both running
at 2.5/200/400 but what they hey,the sticks were cheap


Note:With each successive RAM boot failure I/you have to clear the
CMOS with the power isolated from the system because when it comes to
ram the CMOS stores corrupt/incorrect data that can only be cleared
this way as there's a charge left in the CMOS if there's power to the
mother board and you have to re-enter the settings in the BIOS
manually.

Now this is for this board but I've had to do this when fitting
mis-matched ram on many boards.

If at all possible use matched ram from the same maker(Even that is
not 100% guaranteed).This doesn't confuse the BIOS so much.

If this luxury is not available see above.

Thank you, I've updated the bios and I'm currently trying to download
updated drivers for my MB. After that I will try it again and I can play a
bit with bios settings, if I will be allowed to enter the bios...
I don't understand why two Kingston cannot cohexist :-(

 

[Joel]

I own a Giga-Byte GA-7N400E and the new memory is a Kingston PC3200 400Mhz.
If used with the new ram alone, the system runs without issues. Both are
kingston, I don't see why I should have incompatibility problems. I've
already spent 120? and nothing changed, did somebody already faced this
problem?

Thank you anyway.

They both may come from same manufacture but may not be same type. I am
just guessing because not long ago I found out about the Single and Duo type
memory

1x1GB = 1GB => Single
2x512MB = 1GB => Duo (I think I have the 2x512GB right?)

And my current newest mboard gave me a kick in the back of my head because
I never had this type of problem before. Yes, it supports both Single & Duo
but only allow up to 3x max. Or I can have either

(3) 1x1GB = 3GB
(1) 1x1G + (1) 2x1G = 3GB
(1) 1x1G + (1) 1x1G = 2GB

(1) 2x1G + (1) 2x1G = 2GB (I think it may allow this combination?)

I hope you will have the memory problem solved soon. And from your
message it seems like they are not compatible with each other.

 

[halex2000]

Ok, perhaps I've finally solved that. I installed the last bios available,
as well as the last drivers for my MB. In addition I've moved the second
module to another slot. Now Windows runs, and I don't even know what solved
the issue.
But I've a couple of question: in the System panel it is reported 1GB, but
in the task manager there is no indication about the total ram. There is
something like this: 367M/
without the total amount. In addition I tried creating a 700+ Mb image with
Gimp, but Windows, after a couple of minutes, reported "there is no enaugh
space on c:", and that leads me to think that after all it was using VM. Is
there a good way to know if the whole memory is Actually available?

 

[Shep©]

Ok, perhaps I've finally solved that. I installed the last bios available,
as well as the last drivers for my MB. In addition I've moved the second
module to another slot. Now Windows runs, and I don't even know what solved
the issue.
But I've a couple of question: in the System panel it is reported 1GB, but
in the task manager there is no indication about the total ram. There is
something like this: 367M/
without the total amount. In addition I tried creating a 700+ Mb image with
Gimp, but Windows, after a couple of minutes, reported "there is no enaugh
space on c:", and that leads me to think that after all it was using VM. Is
there a good way to know if the whole memory is Actually available?

My Computer/Right click/Properties.If it says the correct amount there
then don't worry.


HTH

 

[noneofyourbusiness]

Ok, perhaps I've finally solved that. I installed the last bios available,
as well as the last drivers for my MB. In addition I've moved the second
module to another slot. Now Windows runs, and I don't even know what solved
the issue.

The updated bios likely was set for "compatibility mode" instead of
"performance mode" (or what ever), OR, your original bios settings
were trying to set the timings based on the SPD chip and the settings
were just plain wrong (Have read many complaints about this online).

Also, download/read the manual for your board and verify WHICH slots
the ram should be in so you get the DDR performance.

[snip]

....

 

[halex2000]

Ok, perhaps I've finally solved that. I installed the last bios available,
as well as the last drivers for my MB. In addition I've moved the second
module to another slot. Now Windows runs, and I don't even know what
solved
the issue.

The updated bios likely was set for "compatibility mode" instead of
"performance mode" (or what ever), OR, your original bios settings
were trying to set the timings based on the SPD chip and the settings
were just plain wrong (Have read many complaints about this online).

Also, download/read the manual for your board and verify WHICH slots
the ram should be in so you get the DDR performance.

[snip]

...

Thank you all for the help!

 

[Joel]

That's what trouble-shooting is all about, sometime after all headaches

The updated bios likely was set for "compatibility mode" instead of
"performance mode" (or what ever), OR, your original bios settings
were trying to set the timings based on the SPD chip and the settings
were just plain wrong (Have read many complaints about this online).

Also, download/read the manual for your board and verify WHICH slots
the ram should be in so you get the DDR performance.

[snip]

...

Thank you all for the help!

 

[Paul]

Ok, perhaps I've finally solved that. I installed the last bios available,
as well as the last drivers for my MB. In addition I've moved the second
module to another slot. Now Windows runs, and I don't even know what
solved
the issue.

The updated bios likely was set for "compatibility mode" instead of
"performance mode" (or what ever), OR, your original bios settings
were trying to set the timings based on the SPD chip and the settings
were just plain wrong (Have read many complaints about this online).

Also, download/read the manual for your board and verify WHICH slots
the ram should be in so you get the DDR performance.

[snip]

...

Thank you all for the help!

I don't know if anyone mentioned it, but once you get into Windows,
you could try testing with Prime95 (mersenne.org). That is a free
program. You don't have to "join the search for prime numbers",
and you can use the program just for testing.

Prime95 does a calculation with a known answer. The program can detect
if something goes wrong. It is a sensitive test of CPU and memory. If
you install new memory, then it is a good idea to give it some kind of
test that can detect problems. And Prime95 is pretty good at that.

The "torture test" is the option you want to use. If a computer is
ailing, Prime will stop in a matter of seconds. If the RAM is
really OK, Prime will run for hours.

I believe your motherboard uses the Nforce2 chipset. That chipset
is picky about RAM. I tried some cheap CAS3 RAM in my Nforce2 motherboard
and had problems with it. I couldn't run DDR400 with two sticks in
dual channel mode. The memory clock would get to about 185MHz (DDR370),
and anything higher than that had errors. I ended up buying two new
sticks of CAS2 DDR400 memory, and that solved the problem. (I did spend
about a week testing the board, trying hacked BIOS, various RAM configurations,
and buying new RAM was what fixed it. The breaking point for the chipset
seems to be trying to do dual channel at DDR400. Running two sticks single
channel, or running at less than DDR400, are other ways to fix it. Using
a hacked "Command Rate 2T" BIOS will also fix it. All of the work arounds
result in less memory bandwidth.)

Paul