Re: memory stick??



Again, thanks.

Working fine with either and/or both. Someone else said I wouldn't see any
difference so unless I need the 512 somewhere else, I'll leave it in. That
way I know where it is. :)

L.

"JS" <@> wrote in message news:OqW8BjN9JHA.1880@xxxxxxxxxxxxxxxxxxxxxxx
Your limited by the CPU's FSB speed so
check the specs for your CPU.

Using DDR400 will not speed things up any
and as long as the memory specs meet your motherboards
requirements and the motherboard can properly detect
and read the memory stick's SPD values you should be OK.

As for mixing with both DDR333 and DDR400 it should work
but that's not a certainty.

IOW- more memory (1.5g, 400 & 333) vs. speed (400 only).

DDR333 is designed for CPUs with a memory clock of 166MHz
DDR400 is designed for CPUs with a memory clock of 200MHz

Using DDR400 does not speed up your CPU's clock frequency so
you will not get any speed advantage buy just using DDR400.

1.0GB of memory vs. 1.5GB
Unless you are doing some high end photo editing or gaming
you will not see any improvement in your PC's performance
as for most users 512MB of ram is more than enough.

If you planning to "Overclock" your PC then that's another
story but it's also another question.

--
JS
http://www.pagestart.com



"L.S." <notgood@xxxxxxxxxxx> wrote in message
news:OwFOELN9JHA.4176@xxxxxxxxxxxxxxxxxxxxxxx
Thanks for all the suggestions.
I've learned over the years to keep 'everything' that comes with the
system. :)
The MB, according to the specs, should be able to run the 400mhz stick.
Spec state the MB can handle up to 3gig and 400m.

Generally speaking, is there a problem running a 333m with the 400m stick
on the same board at the same time? Or would be 'better/faster' to run
with the 400m only?
IOW- more memory (1.5g, 400 & 333) vs speed (400 only).

Will run test's' and report back if problem.

Again thanks,,

"JS" <@> wrote in message news:%23qayTxH9JHA.4948@xxxxxxxxxxxxxxxxxxxxxxx
Download and create a Memtest86+ boot disk or CD
See: http://www.memtest.org/

Turn off the PC, remove the AC power cord.
Wait 5 minutes or until the green motherboard LED (if there is one) goes
out.

Now remove the 512MB stick, insert the 1GB stick.
Power up the PC and running Memtest86+,
this runs from the boot disk or CD you created and
should eliminate or confirm if your ram is bad.
Let it run for as long as you can, 2,4,6,8 or more hours,
if no errors by then your ram is OK.

Again turn off the PC, remove the AC power cord.
and wait 5 minutes or until the green motherboard LED goes out.

Insert the 512MB stick so you now have both sticks installed.
Run Memtest86+ again.

Last test is Prime95
http://www.mersenne.org/freesoft/

It's a stand alone .exe file contained in a .zip archive.
Just choose to run the "stress test" option for 3 hours.
If your PC can pass this test both your memory and CPU
are fine (close the case cover to maintain proper ventilation)

--
JS
http://www.pagestart.com



"L.S." <Pat@xxxxxxxxxxx> wrote in message
news:OYkFX5G9JHA.2604@xxxxxxxxxxxxxxxxxxxxxxx
I have an older system, nvidia geforce2 board, amd sempron 3300+ @
1.8mhz and
one 512m stick on memory, ddr333 64x64.
I have an extra stick 1gb, pc3200 ddr @ 400mhz.
Can I run both or not and will the pc3200 run ok in the system?

thanks for any help/advise,










.



Relevant Pages

  • Next July 27: boot failure(hang) on x86_64 box.
    ... Freeing unused kernel memory: 1360k freed ... ACPI: PM-Timer IO Port: 0x488 ... CPU: L2 Cache: 1024K ... # AX.25 network device drivers ...
    (Linux-Kernel)
  • Re: CPU Core Voltage Too Low -> Crash?
    ... >> sure I really trust AIDA32 to accurately monitor CPU voltages. ... >> the CPU makers web site and get the specs for your CPU. ... found my chip and it shows the spec for Core Voltage ... It may even be memory related. ...
    (microsoft.public.windowsxp.help_and_support)
  • Re: CPU Core Voltage Too Low -> Crash?
    ... >> sure I really trust AIDA32 to accurately monitor CPU voltages. ... >> the CPU makers web site and get the specs for your CPU. ... found my chip and it shows the spec for Core Voltage ... It may even be memory related. ...
    (microsoft.public.windowsxp.general)
  • [PATCH] Document Linuxs memory barriers [try #3]
    ... The attached patch documents the Linux kernel's memory barriers. ... I've tried to get rid of the concept of memory accesses appearing on the bus; ... barring implicit enforcement by the CPU. ...
    (Linux-Kernel)
  • Oops in 2.6.28-rc9 and -rc8 -- mtrr issues / e1000e
    ... Bios 1.04beta did show correct memory sizing in dmidecode, ... I hope this is as simple as me doing something glaringly wrong in the kernel ... DMI present. ... CPU: L2 cache: 6144K ...
    (Linux-Kernel)

Quantcast