Weird BSODs On Startup

[rty]

So far I'm at 3 hours 6 passes and 1 error with the good stick. The error is at same address as before. Interesting that its only on one pass out of 6. Maybe this is why it's a cold boot issue, once it warms up it works okay?

[McSteel]

Originally Posted by rty

So far I'm at 3 hours 6 passes and 1 error with the good stick. The error is at same address as before. Interesting that its only on one pass out of 6. Maybe this is why it's a cold boot issue, once it warms up it works okay?

During which test did the error occur, and on what pass?
I dunno, that's some pretty strange behavior... Maybe you should just RMA the RAM kit, if it's not too expensive. I personally wouldn't just yet, but I do have a couple of options for running different RAM in my MoBos and dodgy RAM in multiple MoBos...

[rty]

The "good" stick had 1 error on pass 0 test 7 after 4 hours of testing.

I'm running the "bad" stick right now and I'm at over 500 errors at pass 1.

[McSteel]

Originally Posted by rty

The "good" stick had 1 error on pass 0 test 7 after 4 hours of testing.

I'm running the "bad" stick right now and I'm at over 500 errors at pass 1.

According to memtest,

Test 7 [Random number sequence]

    This test writes a series of random numbers into memory.
By resetting the seed for the random number the same sequence of number can be created for a reference.
The initial pattern is checked and then complemented and checked again on the next pass.
However, unlike the moving inversions test writing and checking can only be done in the forward direction.

Having a single error in this particular test, and passing without error apart from that for hours, probably means a chance occurrence and not an indication of malfunction. The other module, however, is a different story.

So, now we know. Since one of the modules works as it should 99.9% of the time, we're basically certain that I mis-predicted, and this isn't a compatibility issue. The other DIMM is malfunctioning, and all that remains to be done now is RMA. You could ask G.Skill to send only the faulty module, so that you can use your PC while you wait for the replacement. But before you send it out, and after you type out the RMA form/email, put the working module to the test once more, 6+ hours if possible, just to be sure.

It's probably not a bad idea to link to this thread, when you submit the RMA request... This way the support crew will have a better insight into your troubleshooting methodology and the nature of the problem, without you writing a huge wall of text.

[rty]

They were both bad, 4 weeks later after sending them out I got my replacement, and it seems all is well.

Thanks for the helpful suggestions.