Quote Originally Posted by geof View Post
you're right, i bought a E6400 for my 2nd ring too and i'll sell it before end april
Let us know what you can do with this E6300
Quote Originally Posted by PanteraGSTK View Post
Mine is awsome. I never thought this thing would be able to get to 3700mhz. You need to remember that the same cpu can perform totally diffirent on diffirent boards. You should be able to get to 3500mhz if your chip has no fsb wall like my first one did. Even at 400mhz it was still a good chip. Cool the NB and you will be fine.
It was a pretty tiring weekend with P5N-E.
I've spent about 2 days trying to make the stupid onboard lan to work.
I've searched around the web trying to find a solution. Learned about the RIS driver issue and NVidia. However i haven't managed to install the RIS driver that asus list on P5N-E download. Both 8.26 and 8.43 drivers result in a non functioning lan plus if u try to play with different drivers u'll end up with a CPU utilization of 100% all the time. Not even drive cleaner can do the job.
So after 3 winxp formats the only working solution for me is to install lan drivers from the install disk (which includes both NV driver and RIS) while installing the sm bus driver from 8.43's. Anyone else haven't experienced this prob?
Apart from that, I got the worst 6300 that exists. This crappy thing can go up to 2.9ghz and this with 1.6v vcore!
Right now i'm on 2.8ghz with 1.475v. FSB isn't an issue cause it's working till 470mhz with 6X multi. I would change it asap for a new one, but i'm a bit busy @ this time, so i'm going to leave it on till the April price drop and then change it for a 6400/6600.
Apart from these. The mobo is way more stable than what i have expected. Even after 3 days of testing and playing with settings, it didn't require a psu shutdown for CPR to kick (like my P5B). I've had a long time seeing such a good oc'ing behavior from a m/b. Vdrop is terrible on this board however and nb needs to be cooled asap. I'm using Coolermaster chipset hsf on mine.
I'm using 401 bios. Haven't tried 505.