A7N8X-E Deluxe Dual Channel = Bad RAM? (or two modules = b..

Testing memory exhaustively is an incredibly slow process, so I haven't had a
chance to troubleshoot this _fully_ yet.

I'm running an A7N8X-E Deluxe with a "TwinX" pair of Corsair 512MB XMS PC4000
modules (250MHz/500DDR RAM running at 200MHz/400DDR, and with default
timings; nothing aggressive).

Has anyone ever heard of nForce2 motherboards having trouble running
error-free in dual channel mode? Or has anyone ever heard of two modules of
RAM being more error prone than one?

I just downloaded Half Life 2 from Steam, and it's crashing like crazy. I
can't play for more than a minute or two, it seems. I've had periodic
crashes before (two per month, maybe), with IRQL_NOT_LESS_OR_EQUAL errors,
and one with PFN_LIST_CORRUPT (WinXP BSOD errors). And the World of Warcraft
open beta was crashing on me regularly, too. Most other things work fine,
and I can usually run for quite some time with no errors. I've also found
that if I run various memory testing programs for long enough, I invariably
find an error. It's not repeatable in a given location, but I am getting
intermittent memory errors. I suspect that's the source of a lot of my
crashing problems.

So last night, I took a memory module out and ran MemTest86+. I told it to
run all tests, but unfortunately then told it to restart the test (thinking
that might be necessary to have all tests kick in), not realizing that doing
so resets the settings, and it goes back to its "quick test" (which still
takes quite awhile). This morning, I got up and checked my computer - It had
gone through the tests 14 times and found no errors (previously, I had found
errors within the first 2-3 passes using the same quick test and both RAM
modules). So I swapped out the module - putting the other module back into
its original slot, and taking the first chip out. This way, I figure I could
narrow my problem down to a bad module OR a bad slot, and then narrow it
further from there.

This time, I ran ALL tests - after 2-3 hours, it was still finishing up the
first pass (92% done or so). But so far, no errors. I'm going to keep
testing (I needed to reboot into Windows to get some information, and figured
I'd write this email while I did), but right now, it looks like NEITHER chip
is bad, and NEITHER slot is bad, but the combination is bad. Is that really
possible (or likely, for that matter)? If so, is the problem likely to be
solved by moving the modules around such that they run in single-channel
mode? Either way, is the fault with my Mobo or my RAM?

In article <8fbvp0t5qo3s0o6ohpa8s2e9a3rk7jdqe4 DeleteThis @4ax.com>, Erik Harris
<n$wsr$ader@$harrishom$.com> wrote:

 > Testing memory exhaustively is an incredibly slow process, so I haven't had a
 > chance to troubleshoot this _fully_ yet.
 >
 > I'm running an A7N8X-E Deluxe with a "TwinX" pair of Corsair 512MB XMS PC4000
 > modules (250MHz/500DDR RAM running at 200MHz/400DDR, and with default
 > timings; nothing aggressive).
 >
 > Has anyone ever heard of nForce2 motherboards having trouble running
 > error-free in dual channel mode? Or has anyone ever heard of two modules of
 > RAM being more error prone than one?
 >
<<snip>>

The Nforce2 is picky about RAM, and I consider the RAM thing to be
the biggest exposure now with using Nforce2. I had some RAM that I
thought was fine, but in a new A7N8X-E, it would work fine in dual
channel, only up to 180MHz. In single channel mode (two sticks in
slot 1 and 2), it would work up to 200MHz. My theory is, there are
too many I/Os for the number of power/ground pins on the Nvidia
Northbridge package, and the I/O timing slows down when both channels
are engaged.

Memtest86 would pass the memory, so was useless for debugging the
problem. I found Prime95 from mersenne.org was much better, and
it would detect an error in my case, within 30 minutes of testing.
(Use the "torture test".)

My solution was to buy some Ballistix PC3200, but I really don't
know what aspect of RAM (clock speed or low latency) the Nforce2
is really looking for. It is obvious in your case (and another case
I read about where someone was using PC4000 memory), that clock
speed alone seems not to be enough to fix it. Maybe the board is
looking for low latency memory ?

I'm having trouble correlating the symptoms, with
how the memory works. SDRAM and DDR are synchronous technologies.
They should only be sensitive to meeting Tsu and Th (setup and hold
time), and not be sensitive to CAS latency. In other words, if
normally you had a memory which was acting up, increasing the
CAS setting by a notch (CAS2.5 to CAS3, say), would be enough to
make a memory stable. That is a case where the internal timing is
failing, and the CAS change solves that internal problem. But in
the case of the Nforce2, that doesn't seem to help. In your case,
you are using a high clock memory, and such a memory should have a
fast clock to Q timing. But that isn't helping you. So, I'm puzzled
as to exactly what is failing here. If the failure was external
timing, then a memory capable of being clocked faster, should
have helped, or at least exhibited different symptoms.

I hate recommending a purely random purchase of RAM - you can
visit Nforcershq and see what some of the users over there
recommend, but I'm not sure that memory DIMM construction stays
constant long enough, to use such a buying recommendation
successfully. A DIMM maker can change chips at any time, which
nullifies the benefit of shopping by brand.

You've tried a high clock memory, so the only other type to
try, is a low latency memory.

HTH,
Paul<!-- ~MESSAGE_AFTER~ -->