The Unofficial ASUS P5N-E SLI 650i Board Thread

[JonDoms]

Originally posted by: Core2
I get about 3000 kbps out my old router now how much improvement would I see with the Dlink. I am also on a cable modern but, I share it with my wife and two kids.

Yea I live with roommates now and a GF who all share the cable connection.
I have zero problems playing games while they are on youtube and surfing the web.
Plus when I had a miniLAN a lot of peeps would torrent and I still have no problems because the router prioritizes games over everything else Automatically.
Now if you are not into games you can also set it to prioritize your traffic based on IP over everyone else's in the house.

Compared this to the KillerNic the KillerNic will only prioritize traffic coming out of your box. If you live in a house with others you will get hosed anyways by them. Rather spend the $80 some dollars for a DLINK gaming router than the DeadNic.

Originally posted by: Core2
I am the person who was posting to you over at the Asus Forum. Welcome aboard.
John

Yup Thanks for all the pointers John.

 

[adder1971]

fyi....... everything was going fine until i hit 1650fsb

kept locking up getting into windows

raised NB back to 1.56 after having run the previos 1500-1600fsb at 1.39

bios wouldn't post

only showed me cpu frequency and cpu type no more info, no mem timings or anything else
turned it back off and on again same deal

now i get no vodeo, no post beep, fans are all on, hdd access light is on solid, cd access ligt flashes once a second.

me thinks i'm hosed.

using a backup pc to type this and search for solutions

 

[Core2]

Originally posted by: JonDoms

Now if you are not into games you can also set it to prioritize your traffic based on IP over everyone else's in the house.

I am mostly doing it for my Boys there always on Xbox Live or WoW. Would it make me type any faster????
Thanks for the info

 

[Core2]

Originally posted by: adder1971
fyi....... everything was going fine until i hit 1650fsb

kept locking up getting into windows

raised NB back to 1.56 after having run the previos 1500-1600fsb at 1.39

bios wouldn't post

only showed me cpu frequency and cpu type no more info, no mem timings or anything else
turned it back off and on again same deal

now i get no vodeo, no post beep, fans are all on, hdd access light is on solid, cd access ligt flashes once a second.

me thinks i'm hosed.

using a backup pc to type this and search for solutions

Don't get nervous, Pull the plug Remove the Battery (hate that part) and Clear the CMOS jump the pins for 30 sec. Your timings are to tight, remember thats were the strap change is. Try 5-5-5-15. Remember timings are the last things to adjust when looking for higher clocks

 

[adder1971]

shouldnt at least have an error beep or something?

the memory frequency has been 800mhz the whole time plus or minus 25mhz.

and i'm having a heck of a time removing the battery looks different than the clips i am used to......

dont want to break it

 

[Core2]

Originally posted by: adder1971
shouldnt at least have an error beep or something?

the memory frequency has been 800mhz the whole time plus or minus 25mhz.

and i'm having a heck of a time removing the battery looks different than the clips i am used to......

dont want to break it

I used a lolly pop stick. all I had that was non conductive. Make sure you ground yourself.

 

[adder1971]

Kudos to you John, I owe ya one.

We are back in business!!!

Setting all mem timings now to 4-4-4-12 2t as recommended previously in this post.

Resuming tests.

 

[Core2]

Originally posted by: adder1971
Kudos to you John, I owe ya one.

We are back in business!!!

Setting all mem timings now to 4-4-4-12 2t as recommended previously in this post.

Resuming tests.

Still to tight. Do you have another lolly pop stick handy and don't use the wet side could arc

 

[adder1971]

hahaha, too late now :-0

5-5-5-15 2t ?

 

[Core2]

Originally posted by: adder1971
hahaha, too late now :-0

5-5-5-15 2t ?

Have to eat my dinner Wife's yelling. Your on your own.

 

[adder1971]

Originally posted by: Core2

Originally posted by: adder1971
hahaha, too late now :-0

5-5-5-15 2t ?

Have to eat my dinner Wife's yelling. Your on your own.

5-5-5-15 no good either. went from 1650 to 1700 works beautifully. changed mem timings back to 4-4-3-8 2t. 1650 is a black hole. made a perfectly stable system crash and crash hard. i dont know if it is just my board but i higly advise people to bypass that completely and either stick with 1600 or 1700. will narrow where exactly the dropoff is later. moving to 1750.

 

[adder1971]

Originally posted by: Core2

Originally posted by: adder1971
hahaha, too late now :-0

5-5-5-15 2t ?

Have to eat my dinner Wife's yelling. Your on your own.

Enjoy and thanks again for your help.

 

[Core2]

Originally posted by: adder1971

Originally posted by: Core2

Originally posted by: adder1971
hahaha, too late now :-0

5-5-5-15 2t ?

Have to eat my dinner Wife's yelling. Your on your own.

5-5-5-15 no good either. went from 1650 to 1700 works beautifully. changed mem timings back to 4-4-3-8 2t. 1650 is a black hole. made a perfectly stable system crash and crash hard. i dont know if it is just my board but i higly advise people to bypass that completely and either stick with 1600 or 1700. will narrow where exactly the dropoff is later. moving to 1750.

Try 1696 and do a Super Pi comparison to 1700

 

[adder1971]

Originally posted by: Core2

Originally posted by: adder1971

Originally posted by: Core2

Originally posted by: adder1971
hahaha, too late now :-0

5-5-5-15 2t ?

Have to eat my dinner Wife's yelling. Your on your own.

5-5-5-15 no good either. went from 1650 to 1700 works beautifully. changed mem timings back to 4-4-3-8 2t. 1650 is a black hole. made a perfectly stable system crash and crash hard. i dont know if it is just my board but i higly advise people to bypass that completely and either stick with 1600 or 1700. will narrow where exactly the dropoff is later. moving to 1750.

Try 1696 and do a Super Pi comparison to 1700

will do, i think i see what you are getting at. I am definitely finding some very interesting results.

 

[JonDoms]

I don't think we need to relax timings as long as you are running your memory at the timings and speeds and voltages it is recommended.
This is from my experience with OCing my C2D setup.
I can run fine with my 6600 @ 3.6ghz with a 1600mhz FSB and a 800mhz memory bus with my PC-6400 rated memory at rated timings and voltages 4-4-4-12-2T 2.2v.
I looked into your RAM adder1971 and it looks like you have some L33T ram that runs at 4-4-3-8-2T @ PC-6400 (800mhz) with 2.2v.

Are you applying enough voltage?

 

[Core2]

Originally posted by: JonDoms
I don't think we need to relax timings as long as you are running your memory at the timings and speeds and voltages it is recommended.
This is from my experience with OCing my C2D setup.
I can run fine with my 6600 @ 3.6ghz with a 1600mhz FSB and a 800mhz memory bus with my PC-6400 rated memory at rated timings and voltages 4-4-4-12-2T 2.2v.
I looked into your RAM adder1971 and it looks like you have some L33T ram that runs at 4-4-3-8-2T @ PC-6400 (800mhz) with 2.2v.

Are you applying enough voltage?

funny thing is I was getting better bench mark scores with 5-4-4-15 2T than 4-4-4-12 2T

 

[adder1971]

Originally posted by: JonDoms
I don't think we need to relax timings as long as you are running your memory at the timings and speeds and voltages it is recommended.
This is from my experience with OCing my C2D setup.
I can run fine with my 6600 @ 3.6ghz with a 1600mhz FSB and a 800mhz memory bus with my PC-6400 rated memory at rated timings and voltages 4-4-4-12-2T 2.2v.
I looked into your RAM adder1971 and it looks like you have some L33T ram that runs at 4-4-3-8-2T @ PC-6400 (800mhz) with 2.2v.

Are you applying enough voltage?

all the timings are set to manu specs. as you have found to be 4-4-3-8 2t and i have locked mem speed to 800mhz (fluctuates slightly based on automatic divider setting) the voltage i basically leave at auto. setting it manually seems to actually cause instability. very odd. i even bump it up a bit thinking maybe there is vdimm droop as John has noticed and it still seems unstable. auto has worked flawlwssly for me even at lower timings except for when the quad fsb was set to 1650. then all bets were off an no combination of lower timings or voltage increases would help. when i finish my testing i'm going to go back to that range to figure out exactly what fsb's to stay away from.

Ryan

 

[Core2]

Originally posted by: adder1971

Originally posted by: JonDoms
I don't think we need to relax timings as long as you are running your memory at the timings and speeds and voltages it is recommended.
This is from my experience with OCing my C2D setup.
I can run fine with my 6600 @ 3.6ghz with a 1600mhz FSB and a 800mhz memory bus with my PC-6400 rated memory at rated timings and voltages 4-4-4-12-2T 2.2v.
I looked into your RAM adder1971 and it looks like you have some L33T ram that runs at 4-4-3-8-2T @ PC-6400 (800mhz) with 2.2v.

Are you applying enough voltage?

all the timings are set to manu specs. the voltage i basically leave at auto. setting it manually seems to actually cause instability. very odd. i even bump it up a bit thinking maybe there is vdimm droop as John has noticed and it still seems unstable. auto has worked flawlwssly for me even at lower timings except for when the quad fsb was set to 1650. then all bets were off an no combination of lower timings or voltage increases would help. when i finish my testing i'm going to go back to that range to figure out exactly what fsb's to stay away from.

Ryan

ClockGen will clock down pretty good it will save you time rebooting. 422 I crash 424 is the best 412 I have no problem 400 ok 425 easy, strap change memory performance drop 462.5 more voltages but doable

 

[adder1971]

Originally posted by: Core2

Originally posted by: adder1971

Originally posted by: JonDoms
I don't think we need to relax timings as long as you are running your memory at the timings and speeds and voltages it is recommended.
This is from my experience with OCing my C2D setup.
I can run fine with my 6600 @ 3.6ghz with a 1600mhz FSB and a 800mhz memory bus with my PC-6400 rated memory at rated timings and voltages 4-4-4-12-2T 2.2v.
I looked into your RAM adder1971 and it looks like you have some L33T ram that runs at 4-4-3-8-2T @ PC-6400 (800mhz) with 2.2v.

Are you applying enough voltage?

all the timings are set to manu specs. the voltage i basically leave at auto. setting it manually seems to actually cause instability. very odd. i even bump it up a bit thinking maybe there is vdimm droop as John has noticed and it still seems unstable. auto has worked flawlwssly for me even at lower timings except for when the quad fsb was set to 1650. then all bets were off an no combination of lower timings or voltage increases would help. when i finish my testing i'm going to go back to that range to figure out exactly what fsb's to stay away from.

Ryan

ClockGen will clock down pretty good it will save you time rebooting. 422 I crash 424 is the best 412 I have no problem 400 ok 425 easy, strap change memory performance drop 462.5 more voltages but doable

i think you are exactly right. NB needs 1.563 at 1950fsb.

 

[Core2]

Originally posted by: adder1971

i think you are exactly right. NB needs 1.563 at 1950fsb.

Can I get a Super PI comparison between 424 and 425 That should have taken you with your timings about 16.43 sec. What taken you so long, another debacle. By the way thanks for teaching me a new word.

 

[adder1971]

Originally posted by: Core2

Originally posted by: adder1971

Originally posted by: JonDoms
I don't think we need to relax timings as long as you are running your memory at the timings and speeds and voltages it is recommended.
This is from my experience with OCing my C2D setup.
I can run fine with my 6600 @ 3.6ghz with a 1600mhz FSB and a 800mhz memory bus with my PC-6400 rated memory at rated timings and voltages 4-4-4-12-2T 2.2v.
I looked into your RAM adder1971 and it looks like you have some L33T ram that runs at 4-4-3-8-2T @ PC-6400 (800mhz) with 2.2v.

Are you applying enough voltage?

all the timings are set to manu specs. the voltage i basically leave at auto. setting it manually seems to actually cause instability. very odd. i even bump it up a bit thinking maybe there is vdimm droop as John has noticed and it still seems unstable. auto has worked flawlwssly for me even at lower timings except for when the quad fsb was set to 1650. then all bets were off an no combination of lower timings or voltage increases would help. when i finish my testing i'm going to go back to that range to figure out exactly what fsb's to stay away from.

Ryan

ClockGen will clock down pretty good it will save you time rebooting. 422 I crash 424 is the best 412 I have no problem 400 ok 425 easy, strap change memory performance drop 462.5 more voltages but doable

those are the same results i have found as well. bandwidth at 1696fsb is almost identical to 2000fsb. super pi finishes roughly the same time. it allows me to drop the NB voltage back down to a less hot 1.39 and i will be checking to see if I can get my Vcore lower as well while keeping stable. unless someone wants to crank up more volts on core and NB and go over 500mhz 1696 (424 x4) is the sweet spot for this board.

this was done with mem unlinked and locked to 800mhz with 4-4-3-8 2t timings (manu recommended) auto voltage. going to try to increase my memory bandwidth by going synch mode. and running timings as low as possible while stable. still havent broken into 16 secs in super pi. cant even figure out what my exact time is except to whole number value.

 

[adder1971]

Originally posted by: Core2

Originally posted by: adder1971

i think you are exactly right. NB needs 1.563 at 1950fsb.

Can I get a Super PI comparison between 424 and 425 That should have taken you with your timings about 16.43 sec. What taken you so long, another debacle. By the way thanks for teaching me a new word.

haha your welcome. it certainly was at that. i thought maybe too much NB voltage caught up to me

super pi at 424 17 seconds. checking 425 now.

425 also in 17 seconds.

 

[Core2]

Try this one super_pi_mod-1.5

 

[adder1971]

Originally posted by: Core2
Try this one super_pi_mod-1.5

i will give it a shot.....

super pi doesn't seem to be effected by mem bandwidth at all.

i could be wrong but what i'm seeing so far it really seems to be more cpu core freguency and cache speed affected.

I have successfully set my mem to 1000mhz synch mode with the 2000fsb
mem bandwidth is now 8,280 but super pi has not budged??? All timings are set to auto as well as voltage set to auto. going to reduce timings till it breaks

 

[adder1971]

Originally posted by: Core2
Try this one super_pi_mod-1.5

finally into the 16's

16.953 500x7 3.5ghz mem 1000mhz 5-6-6-21 2t all voltage for mem and all other timings default. mem bandwidth 8525 integer, 8398 floating going to lower to 5-5-5-15 and see.

1.515Vcore (1.376 under load)
1.563NB