The Unofficial ASUS P5N-E SLI 650i Board Thread

[AZDude]

Originally posted by: Core2

Originally posted by: AZDude

Originally posted by: Core2

Originally posted by: AZDude
[Well that worked. I now have the Vcore at 1.4000 (or something close to that, I have noticed on this board that what I have the Vcore set in the BIOS, windows shows it lower) and the NB at 1.56. Seems stable in windows, but I haven't ran any stress tests as of yet.

Thanks for your help

http://valid.x86-secret.com/show_oc?id=163110
http://usera.imagecave.com/bear254/2977OC.JPG

Not to bad at all. Good job! Everything else looks good. You have good cooling on the NB SB, right?

2 1/2 hours on orthos with no errors.

I have this on the NB http://www.newegg.com/Product/Product.asp?Item=N82E16835116018

and this on thSB
http://www.newegg.com/Product/Product.asp?Item=N82E16835118002

Sorry, I didn't look at your sig. I probably said already that I liked your NB cooler. Lot of copper thats nice. Does it get real hot to the touch? When you going to try 1800/800? Keep us posted. Nice job planning your setup :thumbsup:

I'm going to let it run on this for a couple days. I just got a new case (better cooling case) and am waiting for some different 120 MM fans for the front and rear. Will be moving this PC into the new case on Friday afternoon. Once I have that up and running, I'm going to push it harder. I'd like to get to 3.1GHz or 3.2GHz stable before I tweak the memory.

I still have the vid card to OC. I be messing with that also.

 

[shapkahead]

Originally posted by: Core2

Originally posted by: shapkahead

Originally posted by: Core2

Thanks for the advice, but I'm still having trouble. I put 0401 on again to test stability, and I made sure to clear the CMOS and take out the battery. It appears marginally more stable, but it still crashes as soon as I try to run Prime95. Why is nobody else having trouble with this BIOS, I wonder? I'm running everything at default settings, except I'm setting the memory to 2T. RAM is in the black slots.

Try the yellow slots. Try setting your ram to spec timings and voltage Crucial Ballistix 2x1GB PC6400 4-4-4-12 2T 1.92 - 2.2

Tried it, same result. Boots XP, but totally unstable.

 

[adder1971]

Originally posted by: shapkahead

Originally posted by: Core2

Originally posted by: shapkahead

Originally posted by: Core2

Thanks for the advice, but I'm still having trouble. I put 0401 on again to test stability, and I made sure to clear the CMOS and take out the battery. It appears marginally more stable, but it still crashes as soon as I try to run Prime95. Why is nobody else having trouble with this BIOS, I wonder? I'm running everything at default settings, except I'm setting the memory to 2T. RAM is in the black slots.

Try the yellow slots. Try setting your ram to spec timings and voltage Crucial Ballistix 2x1GB PC6400 4-4-4-12 2T 1.92 - 2.2

Tried it, same result. Boots XP, but totally unstable.

try one stick of ram

 

[Core2]

Originally posted by: JustaGeek

Originally posted by: acivick
Just wanted to chime in on removing thermal grease. I've been using Arctic Clean (2 step solvents) which makes it incredibly easy to remove that gunk. I'd recommend it, as the small bottles have lasted numerous applications, and only cost about $8.

Also, I'm still working on my memory, I had it running ORTHOS for 14 hours, no incident, rebooted, had a winlogon error and then ORTHOS failed within an hour and a half. Very strange. Right now, I'm testing 5-6-5-18-2T @1000MHz to see what happens.

Hi acivick,

I believe that these unexpected failures could be attributed to Windows XP - it has not been designed to run Dual Core processors! Ther is a fix published on Microsoft web site:

http://support.microsoft.com/kb/896256

Also, you can google Article ID: 896256 - there is a lot of forums referring to failures caused by this flaw of XP, and people replacing memory, Video Cards etc., while the problem was the operating system.

It helped me with the games - no throttling between the cores means more uniform load on the processor, which translates into smooth gaming.

Hope this helps.

The weird thing is that the only time I had memory problems was when I stress tested them in DOS. They never error-ed in Windows. Now I'm not saying that your information won't work so don't get me wrong. Its that I still think the memory controller has issues when stressed and heated. These slot issues are confusing me too. This should not be happening

 

[acivick]

Originally posted by: Core2

Good tip there acivick I added it to the Tips page 92 that we started. I still think when the memory controller gets really hot is when your going to see more errors. Have you tried running a loop session of 3Dmark 06 for an hour or two. I would think that would be more than enough stress that the normal person is going to put on his machine. Orthos is more like a burn in utility IMO.

Originally posted by: JustaGeek

I believe that these unexpected failures could be attributed to Windows XP - it has not been designed to run Dual Core processors! Ther is a fix published on Microsoft web site:

http://support.microsoft.com/kb/896256

I've got the 3dmark basic edition, but I didn't think you could loop that. Is there a command line option or something, or would I need to get the pro version?

Also, I installed that update a while ago. Doesn't seem to have helped much. Though it does make sense that XP wasn't really designed for this kind of hardware configuration. I just have a nagging feeling that this is more a hardware issue, given that most people do not appear to have these problems.

 

[Punchy01]

Originally posted by: Core2

Originally posted by: Punchy01

Originally posted by: Core2

Originally posted by: adder1971

Originally posted by: Punchy01

manually set all ram timings except keep at 2T regardless. set vdimm to manu spec? cd and hdd on different ide channels? i suggest making them both master drives on primary and secondary ide.

i believe John had that same mem. follow his suggestions for the timings for that.

Which CosairPC6400 C4 or C5
CosairPC6400 C4 4-4-4-12 2T 1.92 - 2.1
CosairPC6400 C5 5-5-5-12 2T 1.92 - 2.1
What band hard drives I usually format them with the utility program that the HD manufacture use. Windows takes to long

Sorry, was away for a bit working on some things. Back on the computer. Guys, I tried changing the primary and secondaries, I've switched the jumpers to both CS, manually entered all memory timings (I have the C5's) and manually entered the voltage (listed as Memory Voltage under Voltage Control?) Timings now manually set to 5-5-5-12 2T 1.920v. Ran WindowsXP setup twice now with the same BSOD--both time after it goes through the lengthy format process.
Truly lost, suggestions?

Run Memtest86 1.7 on your ram. Try one stick at a time. Timings now manually set to 5-5-5-12 2T 1.920v is good. Try using only one IDE controller and disable the other ( switch controllers if that doesn't work and disable the other). Disable the JMicron controller. Disable USB Legacy. Make sure the raid is disabled.
What slots have you tried? Switch them.

Core, thanks for the suggestions. I'll give them a whirl tomorrow after work, winding down for tonight. My ram is in the yellow slots BTW.

 

[Core2]

Originally posted by: acivick

Originally posted by: Core2

Good tip there acivick I added it to the Tips page 92 that we started. I still think when the memory controller gets really hot is when your going to see more errors. Have you tried running a loop session of 3Dmark 06 for an hour or two. I would think that would be more than enough stress that the normal person is going to put on his machine. Orthos is more like a burn in utility IMO.

Originally posted by: JustaGeek

I believe that these unexpected failures could be attributed to Windows XP - it has not been designed to run Dual Core processors! Ther is a fix published on Microsoft web site:

http://support.microsoft.com/kb/896256

I've got the 3dmark basic edition, but I didn't think you could loop that. Is there a command line option or something, or would I need to get the pro version?

Also, I installed that update a while ago. Doesn't seem to have helped much. Though it does make sense that XP wasn't really designed for this kind of hardware configuration. I just have a nagging feeling that this is more a hardware issue, given that most people do not appear to have these problems.

I'm sorry acivick I have the 3DMark06 Advanced version $19.95. I bought it bundled with PCMark05 $39.00 I think. Its does give you a lot more options in both programs

 

[Punchy01]

Can Memtest be run without an OS?

 

[JustaGeek]

Originally posted by: Core2

Originally posted by: JustaGeek

Originally posted by: acivick
Just wanted to chime in on removing thermal grease. I've been using Arctic Clean (2 step solvents) which makes it incredibly easy to remove that gunk. I'd recommend it, as the small bottles have lasted numerous applications, and only cost about $8.

Also, I'm still working on my memory, I had it running ORTHOS for 14 hours, no incident, rebooted, had a winlogon error and then ORTHOS failed within an hour and a half. Very strange. Right now, I'm testing 5-6-5-18-2T @1000MHz to see what happens.

Hi acivick,

I believe that these unexpected failures could be attributed to Windows XP - it has not been designed to run Dual Core processors! Ther is a fix published on Microsoft web site:

http://support.microsoft.com/kb/896256

Also, you can google Article ID: 896256 - there is a lot of forums referring to failures caused by this flaw of XP, and people replacing memory, Video Cards etc., while the problem was the operating system.

It helped me with the games - no throttling between the cores means more uniform load on the processor, which translates into smooth gaming.

Hope this helps.

The weird thing is that the only time I had memory problems was when I stress tested them in DOS. They never error-ed in Windows. Now I'm not saying that your information won't work so don't get me wrong. Its that I still think the memory controller has issues when stressed and heated. These slot issues are confusing me too. This should not be happening

Honestly, I have not had any memory problems, but again, I am running DDR2 667, so it does not put too much stress on the NB, especially at stock.
I have had a bit of a problem trying to run it at 533 on my previous MB 775Dual-VSTA, but never at recommended 667 and 4-4-4-12. The OCZ support recommended increasing the voltage, hence I set it on P5N-E SLI to ~2.0V. And the memory would always have to be set manually - the manufacturers, aware of the problems, relax the timings so the computer can boot-up the first time. SPD on mine shows 5-5-5-15, but it is spec'd at 4-4-4-12.
I had problems with games - they ran jittery, especially sports, where the smooth flow is very important. The Microsoft patch seems to have solved that problem.
Thanks for your input, Core 2.

 

[Core2]

Originally posted by: Punchy01
Can Memtest be run without an OS?

Yes, read the directions on their web site. All you need is a windows boot disk and Memtest on another disk or you might be able to fit it all on one disk

 

[Punchy01]

Originally posted by: Core2

Originally posted by: Punchy01
Can Memtest be run without an OS?

Yes, read the directions on their web site. All you need is a windows boot disk and Memtest on another disk or you might be able to fit it all on one disk

OK, I see it now -- thanks Core

 

[Core2]

Originally posted by: JustaGeek

Originally posted by: Core2

Originally posted by: JustaGeek

Originally posted by: acivick
Just wanted to chime in on removing thermal grease. I've been using Arctic Clean (2 step solvents) which makes it incredibly easy to remove that gunk. I'd recommend it, as the small bottles have lasted numerous applications, and only cost about $8.

Also, I'm still working on my memory, I had it running ORTHOS for 14 hours, no incident, rebooted, had a winlogon error and then ORTHOS failed within an hour and a half. Very strange. Right now, I'm testing 5-6-5-18-2T @1000MHz to see what happens.

Hi acivick,

I believe that these unexpected failures could be attributed to Windows XP - it has not been designed to run Dual Core processors! Ther is a fix published on Microsoft web site:

http://support.microsoft.com/kb/896256

Also, you can google Article ID: 896256 - there is a lot of forums referring to failures caused by this flaw of XP, and people replacing memory, Video Cards etc., while the problem was the operating system.

It helped me with the games - no throttling between the cores means more uniform load on the processor, which translates into smooth gaming.

Hope this helps.

The weird thing is that the only time I had memory problems was when I stress tested them in DOS. They never error-ed in Windows. Now I'm not saying that your information won't work so don't get me wrong. Its that I still think the memory controller has issues when stressed and heated. These slot issues are confusing me too. This should not be happening

Honestly, I have not had any memory problems, but again, I am running DDR2 667, so it does not put too much stress on the NB, especially at stock.
I have had a bit of a problem trying to run it at 533 on my previous MB 775Dual-VSTA, but never at recommended 667 and 4-4-4-12. The OCZ support recommended increasing the voltage, hence I set it on P5N-E SLI to ~2.0V. And the memory would always have to be set manually - the manufacturers, aware of the problems, relax the timings so the computer can boot-up the first time. SPD on mine shows 5-5-5-15, but it is spec'd at 4-4-4-12.
I had problems with games - they ran jittery, especially sports, where the smooth flow is very important. The Microsoft patch seems to have solved that problem.
Thanks for your input, Core 2.

I should have said this was at 1066MHz I never had problems at 800MHz - 1020 MHz and thank you for your information it was well taken.

 

[Nevets Drassel]

OK Gonna need some help here Core2.

I finally relented and put the Ballistics into the computer. Problem is is that I don't really have a clue as to how to OC the memory on this puppy and the GEIL I was using would not let me OC it above 409 so I never worried about achieving 1:1, just the highest stable OC. This left the memory pretty much out of the process. Now that I have the Ballistics installed, I am in a whole new ballpark and need some advice.

This is where I am at right now:

Linked at 1700/850 for 3400 1:1 @1T
Memory is set to 5-5-5-15 1T

I do not know whether to increase the mem some more or unlink and up the FSB.

It is really pitiful that such good memory is being wasted on an inexperienced intel OC like myself, but its here and its in my machine so I guess that I will try to make the best of it.

TIA

Edit: I just wanted to add that I was in SYNC mode @ 1:1

Also, I just booted at 3780 (8X472) mem at 420 9:8 FSB:MEM. First time I crack under 16 seconds for SuperPi. My new record is now 15.984. When I was linked and in SYNC I was having trouble staying in windows. I guess that this is an early indication that mem much over 850 is not going to work out too well. That has yet to be seen though.

 

[JustaGeek]

I have a little "theory" of my own, but being a relative "newbie", correct me if I'm wrong.

I believe that Core 2 is right - most of the problems are heat related. With the higher memory frequency in the DDR2 800 and up plus the overclocked processor, NB heatsink and possibly the components around the processor cannot handle all the heat; someone has also mentioned a pretty poor application of the NB stock thermal grease, most likely magnifying the problem.

Now my theory... the best cooling for this MB, since it is missing all the heatpipes and heatsinks of its more expensive cousins in the 680i family, is the processor Heatsink/Fan combination BLOWING ON THE PROCESSOR. This should allow for the good flow of air towards all the capacitors/NB/components in the vicinity of the processor. And, of course, the case must be well ventilated, too, to keep the steady airflow in and out of the case. Any additional fan on NB and HS on South Bridge will help a lot, too.

I have the stock Intel HS/Fan blowing on the processor, plus the side fan blowing directly on the non-overclocked E6600. Core temps are ~41C idle (ASUS probe ~35C), but without the Side Fan were around ~44C. I have not had any reboots or other problems for over 1 month now, and did the Windows Repair, not even fresh install. I just hope it continues... especially when I do my first overclock LOL.

Does it make sense...???

 

[DeadMan3000]

OK I am up and running. Not sure what good temps are. Speedfan beta 8 just crashes when I run it. Everest shows idle temps of 39-41 on each core. Board temp is a high 46. I have 2 x Asus 7600GT Silent's on there. The layout is such it's causing probs as they have bigass swivel heatsinks on top. Will have to fiddle another time. Heat dispersion is all clogged in cables.

One thing I have noticed is the stock heatsink and fan on the CPU is LOUD! Might have to get a better cooler sooner than later. I hate noise (Which is why I got the silent viddy cards).

Not going to overclock for now. Happy with it running and it seems to play all my HD videos which is what I wanted.

 

[JustaGeek]

Originally posted by: DeadMan3000
OK I am up and running. Not sure what good temps are. Speedfan beta 8 just crashes when I run it. Everest shows idle temps of 39-41 on each core. Board temp is a high 46. I have 2 x Asus 7600GT Silent's on there. The layout is such it's causing probs as they have bigass swivel heatsinks on top. Will have to fiddle another time. Heat dispersion is all clogged in cables.

One thing I have noticed is the stock heatsink and fan on the CPU is LOUD! Might have to get a better cooler sooner than later. I hate noise (Which is why I got the silent viddy cards).

Not going to overclock for now. Happy with it running and it seems to play all my HD videos which is what I wanted.

My board temperature shows stable 39C-40C in Everest - 46C seems really high.

By the way - where is the sensor for MB temps located...? Is it the North Bridge temp...?

 

[dlxmax]

VDROOP MOD IS DONE!!!
http://www.xtremesystems.org/forums/showpost.php?p=1986142&postcount=53
All you need is a multimeter and pencil. Trimmers are optional but desirable for easy adjustment.

Also, I saw that somebody else with an E4300 posted their 3.6ghz Super-Pi results a few pages back. Think it was stable? Hell no! You can run off one Super-Pi, but if you want to reboot all you have to do is run ORTHOS and wait a couple seconds.

So, I tried my hand. I got up to 3.71ghz (1649fsb/825ram/x9 mult) and scored a 16.063sec score. Couldn't drop below 16 no matter what! Of course, unstable as all hell. Voltage was somewhere approaching 1.6v.

3.256ghz is 15-hour ORTHOS stable for me at a decent 1.40v. 3.264ghz is appearing stable, able may just be the last rung on the ladder before the voltages required start to become ridiculous.

 

[Core2]

Originally posted by: Nevets Drassel
OK Gonna need some help here Core2.

I finally relented and put the Ballistics into the computer. Problem is is that I don't really have a clue as to how to OC the memory on this puppy and the GEIL I was using would not let me OC it above 409 so I never worried about achieving 1:1, just the highest stable OC. This left the memory pretty much out of the process. Now that I have the Ballistics installed, I am in a whole new ballpark and need some advice.

This is where I am at right now:

Linked at 1700/850 for 3400 1:1 @1T
Memory is set to 5-5-5-15 1T

I do not know whether to increase the mem some more or unlink and up the FSB.

It is really pitiful that such good memory is being wasted on an inexperienced intel OC like myself, but its here and its in my machine so I guess that I will try to make the best of it.

TIA

Edit: I just wanted to add that I was in SYNC mode @ 1:1

Also, I just booted at 3780 (8X472) mem at 420 9:8 FSB:MEM. First time I crack under 16 seconds for SuperPi. My new record is now 15.984. When I was linked and in SYNC I was having trouble staying in windows. I guess that this is an early indication that mem much over 850 is not going to work out too well. That has yet to be seen though.

It is really pitiful that such good memory is being wasted on an inexperienced intel OC like myself, but its here and its in my machine so I guess that I will try to make the best of it.

Now, now I don't want to hear any talk like that. There are no Experts here. Every board reacts different so its trial and error for everyone.
There are a few ways to clock good memory. Lower FSB with low latencies and 1T Memory 1:1. Higher FSB looser latencies 1T Memory 1:1 ( That's what I seen you do above). Very high FSB looser latencies memory 1:1 2T. They are all close in performance. You have to run some experiments and benchmarks to see which has the best stability with highest performance output.

Also your memory is SLI certified 2GB kit (1GBx2), Ballistix 240-pin DIMM, DDR2 PC2-6400 memory module so it gives you even more good options to explore

 

[Core2]

Originally posted by: dlxmax
VDROOP MOD IS DONE!!!
http://www.xtremesystems.org/forums/showpost.php?p=1986142&postcount=53
All you need is a multimeter and pencil. Trimmers are optional but desirable for easy adjustment.

Also, I saw that somebody else with an E4300 posted their 3.6ghz Super-Pi results a few pages back. Think it was stable? Hell no! You can run off one Super-Pi, but if you want to reboot all you have to do is run ORTHOS and wait a couple seconds.

So, I tried my hand. I got up to 3.71ghz (1649fsb/825ram/x9 mult) and scored a 16.063sec score. Couldn't drop below 16 no matter what! Of course, unstable as all hell. Voltage was somewhere approaching 1.6v.

3.256ghz is 15-hour ORTHOS stable for me at a decent 1.40v. 3.264ghz is appearing stable, able may just be the last rung on the ladder before the voltages required start to become ridiculous.

So what was the percentage gained with the mod? Seems voltages are getting a little high for my likings. 3.246GHz is a nice clock for that E4300. Good job!

 

[DeadMan3000]

Originally posted by: JustaGeek

Originally posted by: DeadMan3000
OK I am up and running. Not sure what good temps are. Speedfan beta 8 just crashes when I run it. Everest shows idle temps of 39-41 on each core. Board temp is a high 46. I have 2 x Asus 7600GT Silent's on there. The layout is such it's causing probs as they have bigass swivel heatsinks on top. Will have to fiddle another time. Heat dispersion is all clogged in cables.

One thing I have noticed is the stock heatsink and fan on the CPU is LOUD! Might have to get a better cooler sooner than later. I hate noise (Which is why I got the silent viddy cards).

Not going to overclock for now. Happy with it running and it seems to play all my HD videos which is what I wanted.

My board temperature shows stable 39C-40C in Everest - 46C seems really high.

By the way - where is the sensor for MB temps located...? Is it the North Bridge temp...?

No idea. But as to why my temps are so high. Well my layout and the amount of gear I have in it plus the untidy cable layout right now plus the fact I have my case fans on minimum plus 2 fanless viddy cards all add up to more heat than most I guess. I may put the fans on full for a while to see how much it reduces that temp.

 

[Core2]

Originally posted by: DeadMan3000

Originally posted by: JustaGeek

Originally posted by: DeadMan3000
OK I am up and running. Not sure what good temps are. Speedfan beta 8 just crashes when I run it.

Did you install the non beta Speedfan first. You have to do that then replace ( swap out ) the non beta executable with the beta executable

 

[DeadMan3000]

OK with fans full on motherboard temp goes down to 43 and no lower. CPU cores are 37 and 40. I am still unsure if Everest is giving accurate temps. Can anyone verify or suggest another prog? As stated Speedfan beta crashes.

 

[DeadMan3000]

Originally posted by: Core2

Originally posted by: DeadMan3000

Originally posted by: JustaGeek

Originally posted by: DeadMan3000
OK I am up and running. Not sure what good temps are. Speedfan beta 8 just crashes when I run it.

Did you install the non beta Speedfan first. You have to do that then replace ( swap out ) the non beta executable with the beta executable

Ah did not know that. Probably why. Will give it a spin thanks.

EDIT: That works. But it freezes up on 'Configure' also the fan speed only shows 1 fan and remains static at a high RPM. Don't think that's right somehow.

 

[Genuine Imitation]

Another update, I've managed to get my cpu up to 3.5 which is 1556fsb. Sad thing is that I hit the 1:1 mem divider and the ram is about 20mhz under stock. But 3.5 is about the max for this 6600 I think. It's taking 1.49 vcore to get it stable. With the droop it settles at around 1.41. I had to ramp the vcore pretty quick to reach 3.5 so I'll probably drop it to around 3.4 to 3.45 and lower the vcore for everyday speed. I'll try to get around to posting a OC screenie.

What are your guys' everyday vcore settings?

Next up, ballistix overclocking!

 

[Hackendorn]

Originally posted by: Core2

Originally posted by: Hackendorn
Core2,

Do you have a pictures of the inside of your case and what you had trimmed off the fan housing? When I put it on the normal way, it seemed like the bottom of the AF7 Pro heatsink was touching the top of the NB heatsink. Also, is there a way to get more of the MX-1 stuff?

If the bottom fin of the freezer hits the NB heatsink just bend it up a little ( I had to do that too ). You have trim the lower left hand corner of the fan housing off so it will fit with out hitting the NB

MX-1

Hey Core2,

I bent the heatsink on the Freezer & trimmed the bottom left-hand side of the fan housing and it fits nicely. Now it blows the hot air out the back of my case instead up into my PS.
Plus, it dropped my temp from 43C to 34C using AS5. I ordered the MX-1 and will post how much lower it gets later. Once I am fine with the temperatures, then I can start overclocking. Thanks for the help!