P5N-E SLI sucking

M

Moe.RON

Limp Gawd
Joined
Feb 15, 2007
Messages
185
As I posted in another thread, I can't get this mobo to oc worth a lick. I posted in the mobo forum by accident (long story short, rugby practice for 4 hours in 20F weather is not fun). Just trying to get this thing to OC like it should. My C2D looked really promising as it was running at 2.5ghz at about 41C, but I can't get it past there without it hardlocking and then forcing me to reset the cmos. Any suggestions would be great, thanks.
 
I would try linking your memory and run it at a low divider rather than running unlinked and see if that helps. 2T timings also.
 
james111 said:
Northbridge needs good cooling.
Click to expand...

Wheres the northbridge? - just approx. - where abouts itd be on the motherboard? coz Im struggling with my oc too, read couple of suggestions about NB and that'd should be kept cool as well.
 
Mine is doing 430Mhz w/e6300 all at stock voltages. Stock cooling on the NB, Zalman 9700 on the CPU. Unlinked w/memory @ 800 5-5-5 1T.
 
Mines running fine as well at 2.5 and ram at like 550.

I would recommend taking everything apart, take the mother board of the case, buy new heat syncs for NB and SB then put everything back together and make sure you do it the best you can, It might help because with the information given it's almost imposable for any of us to help you unless the same thing has happened to us and it looks like nobody is having the same problem.

Also check your ram manufacture for the suggested timing so ram runs funny like 4-5-4-15 or 4-5-5-18 I have even seen one say to run it at 3-4-5-12 so check ram timing with manufacture.
 
Sorry forgot to mention, I do have a fan on the NB heatsink and a copper heatsink on the SB chip. Would the unlinked ram really cause me these problems?
 
Moe.RON said:
Sorry forgot to mention, I do have a fan on the NB heatsink and a copper heatsink on the SB chip. Would the unlinked ram really cause me these problems?
Click to expand...

They might, but unlikely. Maybe try something like 801 or something just to make sure it's not just some bug with 800mhz.

Also is there a newer bios available for the board?
 
Wow guys. This board is crazy. I got pissed with it and was like, you know what, lets bump the fsb up alot. I went to 1300 and surprisingly enough it posted and loaded windows. I was straight up like, errrr...., and had no idea what was happening. At stock volts I've got almost 3ghz with the temps topping at around 48C. I knew this chip was capable of it and I just love these e4300s. Stress testing with orthos right now, only 5 minutes but I'm stable thus far. Should be a fun night. :D
For S & G
 
Moe.RON said:
Wow guys. This board is crazy. I got pissed with it and was like, you know what, lets bump the fsb up alot. I went to 1300 and surprisingly enough it posted and loaded windows. I was straight up like, errrr...., and had no idea what was happening. At stock volts I've got almost 3ghz with the temps topping at around 48C. I knew this chip was capable of it and I just love these e4300s. Stress testing with orthos right now, only 5 minutes but I'm stable thus far. Should be a fun night. :D
Click to expand...

Maybe a FSB hole...it's been known to happen ;).
 
I have a question about orthos, It ran for 15 minutes then I had an error. Does that mean my oc isn't stable or was that just an error within the program?
 
Moe.RON said:
I have a question about orthos, It ran for 15 minutes then I had an error. Does that mean my oc isn't stable or was that just an error within the program?
Click to expand...

OC isn't "Prime" stable. Usually that means add a little voltage to the CPU and you can overcome it. Might run fine doing normal Windows tasks though for days on end.
 
Well it did it again and this time i read it (imagine that) and it said "Date/Time has changed during test", so like wtf does that mean? System clock is constantly changing itself or what?
 
Moe.RON said:
Well it did it again and this time i read it (imagine that) and it said "Date/Time has changed during test", so like wtf does that mean? System clock is constantly changing itself or what?
Click to expand...

Never saw that error before. Maybe a bad CMOS battery? Did you set your time/date since you formatted your computer?
 
kirbyrj said:
Never saw that error before. Maybe a bad CMOS battery? Did you set your time/date since you formatted your computer?
Click to expand...

I can't remember if I set the bios time since I last cleared the CMOS. But the battery is brand new so I shouldn't have a problem there. I shut off windows automatic time update though to see if that is the problem. We'll see shortly.
 
Haha, orthos stable at 3150mhz for about 30 minutes now. Going to let it run overnight and see how it goes. Hopefully I can get it to go a bit higher to get a higher rank in the C2D ocing table. :D
 
I just got a p5n-e + e6400/zalman 9700 yesterday and it seems very unstable.. am using g.skill 800mhz ram in it. It doesn't like more then 2.085v applied to the ram, or having the ram clocked to more then 667mhz (async). Also having issues clocking the cpu up.
 
the best thread on the p5n-e sli is at anandtech.

i think the one dude Core2 who posts an insane amount on this mobo, he is kinda obsessed about it, but very helpful - compiled a guide on like page 92 of the thread. most of the thread is about oc'ing

if thats not the right page just look on a page or two of that thread and you will see him, and its in his sig.

http://forums.anandtech.com/messageview.aspx?catid=29&threadid=1972653&enterthread=y
 
idiotekniQues said:
the best thread on the p5n-e sli is at anandtech.

i think the one dude Core2 who posts an insane amount on this mobo, he is kinda obsessed about it, but very helpful - compiled a guide on like page 92 of the thread. most of the thread is about oc'ing

if thats not the right page just look on a page or two of that thread and you will see him, and its in his sig.

http://forums.anandtech.com/messageview.aspx?catid=29&threadid=1972653&enterthread=y
Click to expand...

After reading the posting on anand it seems that this board does not properly detect ram timings (SPD), and doesnt like to have the ram higher then 2.0volts
 
Well set the timings automatically (isn't as difficult as it looks), and roll the voltage down to 1.92 or w/e. Use the unlinked ram ratio to set the ram at the desired speed. The reason I got over the ocing problem was because some where I read to just put the fsb up to 1300 right away. It seemed to work and with the e4300 it was perfect, put it at just under 3ghz. From there I've slowly been upping the voltage and fsb to where I am now.
 
yes that thread does mention the fsb memory holes in quite a specific manner. this board is full of them but can be worked around if your mem & processor can handle it.

good luck. i havent found a more thorough thread on this mobo anywhere else.
 
I tried 1600qdr, fsb 1.57v, 1.5v cpu and 667mhz 2.03v 5-5-5-15(memory) unlinked and it booted up 3.2ghz no problem. Ran Orthos for like 10.5hours no problems. Setting 800mhz for the memory and it won't boot :(

System:
p5n-e fsb 1.57v
e6400 1.5v
zalman 9700
g.skill 2x1GB 6400 2.03v 5-5-5-15 667mhz
8800GTS 320
seasonic 650w
antec 900 case, all fans on high
 
You must log in or register to reply here.
Back
Top