Prev: Can I replace my Nvidia Geforce 2 mx 200 with a new matrox milleniumG550?
Next: SPAM ME PLEASE cklee@lgm.gov.my
From: kony on 11 Apr 2008 17:01
On Fri, 11 Apr 2008 07:55:17 -0700 (PDT),
penang(a)freemail.c3.hu wrote:


>> read your mainboard's specifications carefully.
>> some boards will require that one slot be less capacity than the
>> other(s) when paired with one or more module, or have other niggling
>> details that you might need to ponder over.
>
>
>Re-read the owner's manual, no such mention at all. Got online and
>check the mobo manufacturer's site, also no such mention.
>
>The mobo got 2 slots for DDR2 module. Maximum is 2GB X 2, for a total
>of 4GB.
>
>On my PC, I populate it with 1GB X 2.


That should work, and usually motherboards are now *meant*
to run two equal modules (in dual channel mode), certainly 2
x 1GB.
From: kony on 11 Apr 2008 17:04
On Fri, 11 Apr 2008 08:02:58 -0700 (PDT),
penang(a)freemail.c3.hu wrote:


>I'm going to get 2 new DDR2 modules this weekend. I will run the tests
>again and will see if the problem is still there. If it's there, then
>it's the mobo. If the problems go away, then it is in the RAM module
>(one or both).

It's not necessarily so simple. If you replaced those
modules with some that default to different timings or have
more margin over JEDEC values (assuming the other modules do
meet spec), it could still be a motherboard problem that
causes this fault and yet the higher margins on the
replacement modules might mask, eliminate the instability.
For practical purposes that is an acceptable result, but for
returning the memory that doesn't work to the manufacturer
for a warranty replacement it could be futile as you might
get back exact same or equivalent modules.
From: kony on 11 Apr 2008 17:08
On Fri, 11 Apr 2008 12:29:39 -0700 (PDT), zach
<zachvek(a)hotmail.com> wrote:

<snip>

> I was stumped for
>ever and about to give up, when i came across a new memory test,
>called Orthos, you can just google search it, "Orthos memory test" the
>application also will over clock CPU, which in your case you won't
>probably need, and you can set options so it won't, I had mem test
>come clean over 36hours w/o errors, this ran for about 10minuts, and
>picked up errors, i hope this helps, good luck


While Orthos would pick up on limited memory errors, it is
mostly a test of processor and a failure is most typically
an indication of instable or insufficient processor voltage,
overheating northbridge, overheating CPU, or overclocking
pushed too far (incompatible manually set variables or
overclocking as related to a need for more cooling or higher
than stock voltage).

Main point being, if Memtest86+ runs that long w/o error
then orthos fails when one isn't overclocking and is using
bios defaults, it tends to be an overheating or failing
motherboard problem. Other things are possible, but
probably less likely.
From: kony on 11 Apr 2008 17:22
On Thu, 10 Apr 2008 21:37:42 -0700 (PDT),
penang(a)freemail.c3.hu wrote:

>Need help here !
>
>My PC has 2 DDR2 memory modules, 1GB each, for a total of 2GB RAM.
>
>The OS is WinXP.
>
>For the past few days, the PC kind of halting. Sometimes the cursor
>kind of not responding, sometimes some other things happened,
>indicating that something is terribly wrong --- most probably a MEMORY
>error.
>

While it seems that one of the programs found memory errors,
I would not be so certain that is the cause. If there were
a fault in the one testing under windows, in the design of
the program, that could result in it indicating errors that
wouldn't have occurred otherwise.

Generally, if a system is stable enough it can run
memtest86+ (one of the other 2 test programs) for several
hours without any faults appearing, your errors are
infrequent enough that they would not cause the kind of
symptoms you're seeing. It might be possible, but other
things seem possible like a failing network connection or
hard drive (whether drive be physically failing or a bad
cable connection, etc, an interruption in disk subsystem).
Be sure to check all windows logs including event viewer, to
set windows to not reboot on error, and to write down stop
code messages if you get bluescreens.

It's also possible you have more than one problem. Memory
errors just don't usually cause hesitation but then
everything still seems to keep working, it tends to cause
crashing instead, not just OS, GUI stalls. If your video
card has a fan you might check to ensure it's working, and
generally check temps as well, inspect whole system.
From: Franc Zabkar on 11 Apr 2008 18:15
On Thu, 10 Apr 2008 21:37:42 -0700 (PDT), penang(a)freemail.c3.hu put
finger to keyboard and composed:

>I drop XP to safe mode with command prompt, then call up 2 instances
>of the memtest from http://hcidesign.com/memtest/, each checking
>918MB.
>
>Result - Errors !
>
> Memory Errors Detected !
> Copying between 4c21c71 and 4c2193a did not result in accurate copy.
>
> Memory Errors Detected !
> Pair 19897713 does not store values accurately.
>
> Memory Errors Detected !
> Copying between 5547871 and 5547832 did not result in accurate copy.
>
> Memory Errors Detected !
> Copying between 4c32471 and 4c323a2 did not result in accurate copy.
>
> Memory Errors Detected !
> Copying between 36f8071 and 36f8060a did not result in accurate copy.
>
> Memory Errors Detected !
> Copying between 4c32471 and 4c322d9 did not result in accurate copy.
>
>Conclusion:
> Something wrong with the DDR2 memory module !
>
>Problem:
> Which module giving out errors?
>
>I got one of the DDR2 module out. Ran the memtest from http://hcidesign.com/memtest/
>-- no error.
>
>Switch the sticks to test the other DDR2 module. Ran the memtest from
>http://hcidesign.com/memtest/ -- again no error !

IME RAM testing software often doesn't properly test refresh. Refresh
errors usually show up in normal operation because, unlike most RAM
diagnostic software, the OS may not read a memory location immediately
after writing it, thus giving the data some time to decay.

See http://www.memtest86.com/tech.html

======================================================================
Test 9 [Bit fade test, 90 min, 2 patterns]

The bit fade test initializes all of memory with a pattern and then
sleeps for 90 minutes. Then memory is examined to see if any memory
bits have changed. All ones and all zero patterns are used. This test
takes 3 hours to complete. The Bit Fade test is not included in the
normal test sequence and must be run manually via the runtime
configuration menu.
======================================================================

FWIW, I notice that the failing memory addresses all end in "71" which
makes me wonder whether you have an addressing error. It's a pity that
HCI Design didn't see fit to report the bit differences in the failing
data patterns. :-(

- Franc Zabkar
--
Please remove one 'i' from my address when replying by email.
First  |  Prev  |  Next  |  Last
Pages: 1 2 3 4
Prev: Can I replace my Nvidia Geforce 2 mx 200 with a new matrox milleniumG550?
Next: SPAM ME PLEASE cklee@lgm.gov.my