ASUS P5N-E SLI 650i Thread

[JCushing]

yeah i saw you were having troubles with it, the fact it works with 1 stick makes it appear to be memory related though.

im not saying heat was the problem, its just the only thing i could think of. i mean i was fully stable up to 3.2ghz and i was running it at 2.7 fine but then out of no were it started crashing.

also id still love to see what the NB straps are. id still love to know why my machine wont post between 2.4-2.7ghz meaning i can post / boot at 2.4 and 2.7 but not inbetween. i can still run windows at 3.3ghz though lol

[dpawl31]

Strange.
I don't know anything about NB straps so I can't help you there.
Are you stable @ 3.3? Why not stay? lol

[exnihilo]

Originally Posted by The Pook

It detected a floppy for me too.
I'm reformatting soon, so while I'm at it, I'll probably just disable the floppy connector on the mobo so it'll shut the **** up about a non-existent floppy drive.

For anyone experiencing this problem, just go to your "Device Manager", and navigate to your "Floppy Disk Controllers". Double click it and when the properties box appears, look towards the bottom for "Device Usage", click the drop down menu and select "Do not use this device (disable)". Click "ok" and your done. Worked for me. Hope it helps.

cg

[dpawl31]

Reverted to 0202...

Now I have no memory errors.

But my OC Profiles, after clearing CMOS and flashing to 0202, won't post anymore.

DAMNIT!

I believe I had the memory errors with the 04 series bios as well...
Back when 0307 or whatever came out, I flashed to it and it actually caused it to fail post... I am lost!

[JCushing]

im 9+ hours stable at 3.2, 3.3 errors right away but it prolly just needs more voltage (i was at auto volts)

honestly i didnt see a need to run it over 3, 2.7-2.8 is still real fast and runs just as cool as stock. i was using 2.7 as my 24/7 OC but then i got lockups so i put everything back to stock just to see if it was because my overclock or something else.

[dpawl31]

UGH. Seems to be OC related now.

Went to comlete stock settings via BIOS.
No errors, at all.

This blows, what happened to my OC!

So strange. Worked errorless in 0202 before, works fine with one stick of RAM. Two sticks and I get errors. In any BIOS. MAN I am so confused. No idea where to start.

[jim.e.]

hey guys.

i recently grabbed the P5NESLI due to a bad P5NSLI, and can say I love it already. My specs as follows:

e6300 @ 2.3GHz
P5NESLI
ASUS EN7600GS
Corsair VS1GB667D2 (value select 2x512 ddr2667 running at 5-5-5-15-2T)

I am kinda stumped. I am running stock voltages and as you can tell am at 2.3GHz from the stock 1.86GHz



is it possible for me to go further (Seeing as my memory is pretty much the limitation as its DDR667 and not DDR800)

I tried a fsb (quad pumped) of 1500/1550/1600 and none will work, im assuming voltage increase needed? it was running at 1450 but i lost the FSB: DRAM ratio of 1:1 and it was a bit clunky.

system passes superPI in 22seconds at fsb of 1333 and prime95 can go on flawlessly as well as Orthos

[dpawl31]

You'll be mighty happy with that rig.

Some DDR2-800 RAM would do you good.

[ericeod]

For those having problems with updateing to the 0505 P5N-E SLI BIOS and received the "Downgrade" message when flashing from within BIOS, try loading it through windows. I had to load windows and flash it with the ASUS update utility; Not preffered but it works. The system definately seems more stable.

[TriBeCa]

Hi all!

Thanks for the great thread. I've spent way too long reading, and I can't wait to start playing with my first overclock. Seems like a great board for it....

I'm having a bit of a fight getting this fresh build (see my specs, what you see there is about 10 hours old) stable though, so I haven't had a chance to start trying to OC it...I figure if I'm getting orthos errors with stock settings there's no point.

On my first full boot to windows after installing, I ran Asus InstAll to install the nvidia drivers, etc. etc. I would've gone straight with the latest from nVidia but I needed the LAN drivers installed first. This got going and very shortly windows had detected LAN and a couple other drivers. But the installation seemed to stall. I let it run for about twenty minutes, then decided this was absurd. Since I had LAN drivers now, I went to nvidia.com and grabbed their most recent drivers for the board. I also got the most recent bios update from ASUS, as well as the most recent audio drivers for the onboard sound. I then force quit.

Uh oh! Now the command interpreter isn't working...time to repair the windows install. Boot into windows, install the nvidia drivers, update the bios, and head over to www.windowsupdate.com. Ohhhhh...everything (except the mouse pointer) locks up while installing windows updates. What fun. Reboot.

Back to windowsupdate and finish those installations. Back to windowsupdate, expecting now to get SP2. But the windowsupdate page gives me an error, with no explanation. This is getting weird. So I install SAV Corp edition and start a virus scan...which hangs, just like installing those updates did.

Hmmm. After rebooting, I start fiddling in the bios. This time, the BIOS hangs!!!!! Can't say I've ever seen that before. The numlock key on the keyboard just went out, and I couldn't do a damn thing.

At any rate, through trying various things I discovered that taking one RAM chip out would make the BIOS stable. Mostly I could boot into windows, although I got (different) blue screens twice. Keep in mind all my OC settings, memory latencies, everything is on 'Auto'.

So I started running some orthos tests. Under every single BIOS I got an error in under 10 seconds. While under 03-- BIOS I tried taking out a RAM chip. Still an error. Tried another RAM chip...and this time it took almost 10 minutes to get the error. But an error nonetheless.

At any rate, I've now got both RAM chips in and I'm doing a fresh windows install under 0202 BIOS, in the hopes that the real culprit was a dodgy windows installation. There's no way heat is the culprit--my CPU temp never got above 40C while running orthos, and my case temp was typically a couple degrees cooler. I even touched all the components--the CPU and NB heatsinks weren't even *warm* to the touch, and neither was the RAM.

Any suggestions on how to proceed if the new win install doesn't work out would be greatly appreciated....