Noticed I was failing prime95 again and so went back to testing RAM
Tried 8 8 8 24 timing:
Still failed prime95
stick#2 failed memtest, shortly after starting, while testing it by itself (memtest error: 0003efdb658 1007.8mb (good) dfdfdfdf (bad) dedfdfdf)
Stick#1 passed with those timing settings, but I only tested it for one pass.
Changed timings back to 9 9 9 24 RAM (still at 1333mhz)
Tested with memtest86+, with both sticks in dual channel mode, 4 passes (about 3 hours?) no errors
First prime95 run: Failed after 1 hour (almost exactly) with '0.5, expected no less than 0.4' error
Second prime95 run: Failed in less than 1 minute with '0.5, expected no less than 0.4' error.
Third prime95 run: (started immediately after second run failure- no restart) ran 4 hours (almost exactly) before worker 1 fail with '0.5, expected no less than 0.4' error
Tried upping cpu voltage .1 volts and running prime95:
Failed (don't remember the time) and was running a little hot (up to 59C)
Tried underclocking cpu, HT, and NB:
Failed prime95 in a few seconds.
I'm running cpu pll voltage: Normal (2.500v)
DRAM voltage: 1.660v (default was 1.5, which we established was too low for this RAM)
NB Voltage Control: 1.170v (Normal is 1.150)
HT Link Voltage control: Normal (1.200v)
NB/PCIe/PLL Voltage control: Normal (1.800v)
CPU voltage: Normal (1.3250v)
Ram memory clock: 1333mhz
Ram timings: 9 9 9 24
Any more advice guys? The randomness of the prime95 failures has me totally confused.
I had a delay on getting all my parts, so its been about two weeks since I placed my order and I'm getting a little antsy about possibly needing to RMA before Newegg's 30 day limit runs out.
More about :prime95 rounding errors stock settings
I hate to ask, but why aren't you troubleshooting your components at stock speeds until you stabilze the system? I highly recommend you run all at default first. If the system fails at stock, default speeds I would RMA the memory at a minimum.
To explain: My initial problem was that my comp wouldn't get to windows or run stable in windows with RAM in Dual Channel mode (both sticks in slots that share the same channel). Running one stick or each stick in a seperate channel worked fine.
I was told to check my RAM voltage and that seemed to solve my issues.
I had trouble initially with the BIOS defaults because my MB default DRAM voltage was 1.54v (my RAM needs 1.65v).
It was then suggested that I change my RAM timing to 8 8 8 20, as that was supported at 1333mhz.
The only other thing changed is the NB voltage, which I upped one tick, which made the stability better- it didn't fail as quickly in Prime95.
Long story short, after further testing, I still have instability problems running prime95 and have come all the way back to setting my ram timings to 9 9 9 24, which has improved stability, but my system still isn't stable.
I'm currently running at stock speed, with the memory timing a little more loose than it should need to be for the clock speed its at (1333mhz)
The ram is 2x Corsair 2GB 1600 9 9 9 24 (That's whats on the sticker on the ram stick itself)
There are a couple of possibilities here. One your RAM may be defective, seems from your first posting on this thread that one stick passed at default speeds and the other did not. There could also be a problem with the motherboard/memory controller sub-system.
Did you try the RAM at 9-9-9-24, 1.5v, 1333Mhz (these seems to be Corsair's settings for slower 1333mhz RAM)? Your previous testing fails at any level of OCing/tweaking it seems. I would also set the NB back to default when checking this.
Are you OCing/tweaking your CPU or GPU at all? If so, go back to default and see what happens.
Understood, but you have been changing mobo/NB/RAM settings and that, in effect, is OCing. The previous suggestion I sent effectively underclocks your RAM to be the same as Corsair's 1333mhz offerings to see if that will stabilize your config. If it does, then I would RMA the RAM since it won't run reliably at 1600 settings (and wasn't what you paid for, albeit only a couple more $$$).
It ran for about an hour like this and then gave a rounding error.
1. Should I try setting the NB voltage up a notch from 1.15 to 1.17?
COLGeek: No, I don't see really doing anything to help.
2. Any other settings I should play with to see if I can get it stable at 1600mhz?
COLGeek: If the straight stock settings for 1600 aren't stable, then the RAM likely has a problem and should be returned.
3. Which is actually faster; 1600 at 9 9 9 24 T2 or 1333 at 8 8 8 20 T1?
COLGeek: The difference is largely negligible from a user perspective. You could obviously research and find that the 1600 config will have higher theoretical throughput than the 1333 settings, but you need to look at total system performance to make an effective measure. Stability is WAY more important than raw potential speed.
Apparently, newegg.com won't RMA an item if you've removed the UPC barcode from the package. This is somewhat irritating, since you have to cut out the barcode, immediately upon receiving your product, and include it with other documents in order to claim a rebate. :\
At least it's stable in its current configuration. :\