DDR3 and P55's

[ThreeDhero]

I have the Gskill Trident 2000mhz 3x2GHz kit and having some issues with getting up to rated speeds on my P55 setup. Everything works great on my X58, I heard the IMC on the P55's aren't as strong. So I'm wondering where the best place for voltages are without killing my hardware?

[FACE]

how high have you gotten so far? (both on mhz and volts)

And welcome to the forum!

[ThreeDhero]

Thanks you Face, so far I can only boot in with the memory running at 1333mhz in bios. I try for 1600mhz with no boot, I use 1.675 Vdimm 1.35 VTT. Not sure if I should be tweaking other volts as well or upping what I have :shock:

[Hondacity]

what is your p55 mobo?

[ThreeDhero]

Msi p55 gd-65 using the i5 655k

[Patch]

I think it's also heavily mobo dependent on this platform. I'm having a much easier time with memory on this foxconn Katana Inferno than I did with my P55 Classy.

If you haven't already, try backing off on voltage to 1.65 and 1.25. Sometimes there's an overvolt threshold a mobo doesn't like cold booting with, but will tolerate with incremental increases.

[Hondacity]

ram subtimings?

[Kal-EL]

Nebber clocked that board but pch voltage always did the trick on the classy.

[ThreeDhero]

I've tried running them at 7-7-7-22-70 and back at to stock 9-9-9-24-74.
What PCH voltage should I try atm it's 1.08v.
Guess I'll have to find the mobo sweet spot.

[Hondacity]

can you take a pic of bios ram subsettings? anything memory...

[Splave]

here are some subs that work good on the classy
http://overclockaholics.com/forums/attachment.php?attachmentid=2558&d=1278354514

[Cecil]

I was reading a review on that board earlier, and it said when you manually set timings you have to do ALL sub timings, and do all of them for both channles. Other wise you let it do its SPD thing but it messes up sometimes trying to get the right timings.

[Hondacity]

I was reading a review on that board earlier,
and it said when you manually set timings you have
to do ALL sub timings, and do all of them for both channles.
Other wise you let it do its SPD thing but it messes up sometimes
trying to get the right timings.


this is what i thought too.... but theoretically you really have to set rams manually

[ThreeDhero]

Well I wanted to let my mobo dry out about a week after the DICE session so I went yesterday and went into the bios to set the ram on auto in the bios. Went to reboot and Thought I'd try the OC genie button which I shouldn't have. Whenever using it with the unlocked 655k it seems to get easily confused and won't boot into the bios just keeps restarting. The board has done this ever since I updated the bios to use the CPU unlocking multi feature in bios. Haven't felt like ripping up the clay to reseat the cpu. Last time this happened I had to put my GF's i5 750 in to get back in the bios, seems like I'll have to try that again. This board has it's up's and down's.

[Splave]

maybe just an issue of waiting for better bios support for that cpu, thats why I love evga and shammy.

[ThreeDhero]

+1 :), but I did get the board for $75 vs $300 so it's been doing alright for bot and haven't taking the volts higher than 1.64 Vcore. Might try higher next time since I got the extra 1 year warranty from Micro :ola:
Myabe even try to kill the chip :blink:

[ThreeDhero]

Thought I'd post up results with the first DICE run on this system. I didn't above 1.64 Vcore it be wise to push more Vcore and get more mhz or stay where I'm at and just tweak the ram?

http://img541.imageshack.us/img541/5439/superpi326556.th.jpg (http://img541.imageshack.us/i/superpi326556.jpg/)

Uploaded with ImageShack.us (http://imageshack.us)

http://img192.imageshack.us/img192/6821/superpi655msi13.th.jpg (http://img192.imageshack.us/i/superpi655msi13.jpg/)

Uploaded with ImageShack.us (http://imageshack.us)

http://img340.imageshack.us/img340/8148/wprime32655k31.th.jpg (http://img340.imageshack.us/i/wprime32655k31.jpg/)

Uploaded with ImageShack.us (http://imageshack.us)

http://img294.imageshack.us/img294/8148/wprime32655k31.th.jpg (http://img294.imageshack.us/i/wprime32655k31.jpg/)

Uploaded with ImageShack.us (http://imageshack.us)

http://img828.imageshack.us/img828/4415/wprime1024655k16.th.jpg (http://img828.imageshack.us/i/wprime1024655k16.jpg/)

Uploaded with ImageShack.us (http://imageshack.us)

[Splave]

any way to push the qpi multi up a bit for 32m ? other than that looks awesome

[ThreeDhero]

Thanks Splave, I'll have to look into upping the qpi. Just have a lot going on this week with starting a new IT job.
Hope to beat out a few more peeps on Ln2 :cool3:, only one so far...

[Splave]

sweet, good luck on the job mate

[ThreeDhero]

Well looks like I've run into another problem with this sytem :thumbdown: First after waiting about a week or so after my DICE session I went to boot up, got into the bios shutdown down and wanted to try the OC genie with my 655k. Now all the board does is start and re-start without going into the bios. I've tried clearing the CMOS taking out the battery and moving the jumper over still starts and re-starts. Got out my i5 750 and the board boots right away without any problems. Then put the 655k back in and starts / re-starts.
So I put my 750 in to rollback the bios to 1.7, everything worked. Put the 655k back in and starts / re-starts. Thought I could have have killed the 655k so I put it in my p55 EVGA Micro boots up with on problems. I don't know what else to do, called MSI Tech support told the guy about whats going on, he asked me what he problem was about 10 times before putting me on hold for 10mins, I hung up. At this point looks like I'm not going to be able to use my i5 655k with my P55-GD65 :blink:
Any thoughts of what I could try now???

[Hondacity]

rma the 655k...32nm die easily...

[ThreeDhero]

The 655k works in my P55 EVGA Micro without any problems

[Hondacity]

seen a couple of socket pins not getting good contact....not sure if that was your reset problem

[ThreeDhero]

Yeah I see where your coming from, also going to try heating up the socket with a hairdryer since I put vaseliene, which I won't be doing anymore. The only thing is, this issue happend once before I did all the prep. All I had to do then was put the 750 in and boot in bios then reseat the 655k and worked fine after that.