Overclocking advice

[akaliel]

I'd like to show you a copy of the manual, except Asus has no mention of the P5N-E mobo on their site, like it doesn't exist. They've had a bad web site for years and years. I remember complaining about it in 1999 with my A7M266 motherboard. But that's another story.

I had heard that making your RAM and FSB synchronous would improve performance. If you say it doesn't, I'll just go back to 800Mhz.

Vista is reporting my RAM performance as 4.5. Which is pretty low. My DDR266 RAM in my old PC gets that score, and I'd hope that this DDR2 800Mhz RAM is faster than that old generic stuff.

 

[ALECUBA]

well...wat they told me was that ram is unaffected when it is unlinked...im not sure about that synchronomous option...i guess its cuz u cant oc separately like in "unlinked"mode where u actually can....

 

[akaliel]

So I installed the leaked 100.30 Vista drivers, so I can use my 8800GTX and everything was working really well. I was overclocked to 1333 FSB. Vcore was 1.45. After about 5 minutes it locked up, it was idle at the time. So I rebooted, and increased the Vcore back to 1.50. It locked up again, about 30 minutes later, while WoW was running it's 12 hour patching process (don't get me started). So I figured that it might have been a heat issue 1.5V should be able to handle 1333FSB. I installed Asus Probe II, which came on my mobo disk and checked the CPU temp. It was 35C. So I played Oblivion for a while(which looks damn sweet now, btw) and jumped back to the desktop and the temp was 45C. So it's not a heating issue.

So then I decide to leave Probe running and since I was downloading Qarls texture mod for Oblivion anyway. I leave my PC on all night thinking that in the morning I can check the locked up screen and see exactly what the temp and voltage was at the time. So at 6:30am sharp I wake up, run downstairs, check the PC, and low and behold, it's still running.

So I left it on and came to work. I'll see if it's still running when I get home. How come it locks up when you don't want it to, but doesn't when you DO want it to. Phaw!

I also tried increasing the VCore voltage to 1.55 and gave 1600FSB another shot. Still won't post. I don't think the Nvidia 650i motherboards are very overclockable. On the Asus forums there's lots of bitching about the current BIOS. Perhaps in a few months we'll get a revision and that'll work better.

Perhaps my lockups were actually caused by those leaked 100.30 Vista drivers b/c I was running 1333FSB with 1.50Vcore for several days and didn't have any issues until last night.

 

[lopri]

akaliel, I'd suggest you not waste time troubleshooting since the lock-ups are not your faults. If you think video card drivers were a cause, then go ahead and roll-back to see if that fixes the issue. But other than that, there isn't much you can do about this issue. Because even if you somehow manage to figure it out this time, it will inevitably happen again. 100% guaranteed. Safest (note: not 'SAFE') ways of avoiding the issue at this time are:

1. Not overclocking
2. Using the least possible ammount of disks (including optical, USB, Firewire, and virtual drives)
3. Using the least possible ammount of peripherals (PCI cards, USB stuff, absolutely no RAID)
4. Not installing NV IDE drivers / Network Access Manager.
5. Not running any application that's disk-heavy - such as desktop search (lol), disk defragment (double lol), or anti-virus (triple lol), etc.

None of the above is acceptable (except #4), I know. So more practical options are:

1. RMA the board and get a replacement (until you get a board that doesn't cause such issues)
2. RMA the board and get a refund
3. Wait till NV/ASUS release a fix.

I am not at all being sarcastic here. This issue is real and NV/ASUS are aware of it. I just hope you don't waste too much of your time.

 

[ALECUBA]

he is right about the RMA, about the other stuff i cant say anythin cuz im not a pc geek and i just started in this oc world....
like i told you before, if u can get a refund and put some more coin and get urself a 680i....from what ive seen it is highly cap in terms of ocing....good luck

 

[Noubourne]

Originally posted by: akaliel
So I installed the leaked 100.30 Vista drivers, so I can use my 8800GTX and everything was working really well. I was overclocked to 1333 FSB. Vcore was 1.45. After about 5 minutes it locked up, it was idle at the time. So I rebooted, and increased the Vcore back to 1.50. It locked up again, about 30 minutes later, while WoW was running it's 12 hour patching process (don't get me started). So I figured that it might have been a heat issue 1.5V should be able to handle 1333FSB. I installed Asus Probe II, which came on my mobo disk and checked the CPU temp. It was 35C. So I played Oblivion for a while(which looks damn sweet now, btw) and jumped back to the desktop and the temp was 45C. So it's not a heating issue.

So then I decide to leave Probe running and since I was downloading Qarls texture mod for Oblivion anyway. I leave my PC on all night thinking that in the morning I can check the locked up screen and see exactly what the temp and voltage was at the time. So at 6:30am sharp I wake up, run downstairs, check the PC, and low and behold, it's still running.

So I left it on and came to work. I'll see if it's still running when I get home. How come it locks up when you don't want it to, but doesn't when you DO want it to. Phaw!

I also tried increasing the VCore voltage to 1.55 and gave 1600FSB another shot. Still won't post. I don't think the Nvidia 650i motherboards are very overclockable. On the Asus forums there's lots of bitching about the current BIOS. Perhaps in a few months we'll get a revision and that'll work better.

Perhaps my lockups were actually caused by those leaked 100.30 Vista drivers b/c I was running 1333FSB with 1.50Vcore for several days and didn't have any issues until last night.

You clearly have no idea what you're doing. Unlike most newbies, you're not following any overclocking guide, and they are about as common as air. Forgive me if I think it's you and not the board.