WINDIAG errors

Hi folks

For the first time ever, I have run a memory test using WINDIAG.

My memory is 4 x 1 Gb of Corsair CM2X1024-6400C5DHX running at 4-4-4-15 Vdimm 1.968v (stock spec is 5-5-5-18 Vdimm 2.1v).

At the first attempt, the diagnostic showed a number of errors in each of the 6 standard tests. On inspection, these were confined to Bank 6/7 (slot A3) of my Gigabyte GA-P35C-DS3R mobo. I re-seated the apparently offending module and tried again. Same result. I swapped modules around. Same result. Then I took the modules out of slots A1 and A3 and tried again, hoping to find 2 x 1 Gb of RAM in dual channel mode error-free. (The mobo spec allows dual channel mode if slots A0 & A2 or A1 & A3 or all four slots are occupied).

But oh no. Now I have errors in Bank 4/5 (slot A2).

My confusion is thus: the module originally in Bank 6/7 is no longer in the system and Bank 6/7 is no longer populated. Bank 4/5 did not previously show any errors. How come I have errors where none previously existed?

I have only just started to swap things around, and will be running more tests, but I'd be grateful for any advice on what could be the possible cause/cure.

Should I:

(a) start again using stock specs (timing and voltage) (the system had passed 10 hours of Orthos without error)
(b) re-populate all but one slot and run the diagnostic again, then change the unpopulated slot and retest, and...well, you get the picture...
(c) [insert cunning ploy to make my system work beautifully - please provide detail]

Please form a disorderly queue with all the right answers.

Cheers

T42

You need to set your memory voltage to the tested setting of 2.1v. Also, with 4 modules you will likely need to increase the voltage to your memory controller, aka north bridge, aka NB. Try 1 or 2 notches above the stock value.

Thanks, Yellowbeard. I'll try that and see what happens.

Well, despite resetting the voltages and timings to stock, I still got lots of errors (within 55 seconds). But, on advice from some other people with a similar board (I googled the error fail address...) , I reverted to BIOS v F8 (from F9).

And no errors so far after 10 mins of testing. Looks like F9 has issues, and it's not the memory after all.

Hopefully a full overnight test will bear this out.

Also I missed it the first time but, your memory is stock CAS5 1.8v memory. So, instability as CAS4 is not unexpected. There is a 5% tolerance but, you are also overvolting your memory over the rated 1.8v.

Yellowbeard,

I hear what you are saying and I know that CPU-Z reports the SPD voltage recommendation as 1.8v. However, the label on each stick indicates 2.1v. Is this the max rated voltage for the RAM?

I ran Memtest86+ overnight (8 hours, 11 passes) without error. Should I now reduce the voltage and test again?

T42

Can you list the info from the stickers EXACTLY as it is written? Most likely you are seeing a typographical error or you are misinterpreting the version number. THe voltage for this memory is 1.8v, not 2.1v.

Hi Yellowbeard,

Each DIMM has a white sticker with a barcode over the orange, black and white label with the Corsair logo.

The orange, black and white labels are written thus:

Quote:

---

CM2X1024-6400C5DHX

XMS2-6400 1024MB 800MHz 5-5-5-18 XMS6405v2.1 07311496

---

The white stickers on each DIMM are written thus:

Quote:

---

SCIL-309948103

4GB Corsair Quad2x DDR2 C5DHX
Warranty void if removed
Link-[ 18576]

---

It was the v2.1 on the orange, black and white label which I took as being the correct voltage. Is that not the case?

v2.1 is the revision number or version number, not the voltage. I would suggest staying at or under 1.95v on those.

Yellowbeard,

Thank you for your continued input. When I rebuild my system (for non-memory reasons....) I will revert to the settings you have suggested. I'll let you know the outcome (but I'm now pretty sure it's not a memory problem).

Cheers.

T42

Yellowbeard,

You'll be pleased to know that, having changed my BIOS, I've had no memory problems since. I ran Memtest86+ v1.70 again without a single error. And that's at tighter timings and with a 67% overclock on my processor. BIOS was, it appears, the big issue.

Cheers

T42

Thanks for the feedback. I am glad to hear it was a bios and therefore free issue to resolve with no shipping or RMAs involved.