View Full Version : E6600 + P5B clocking really bad..
Bergstrom
08-27-2006, 02:29 PM
Got myself a E6600 and a P5b Deluxe Wifi, with a pair of 1 Gb Corsair TWIN2X-6400 memory, supplied by a Tagan 530 EasyCon. Ohh btw, CPU cooled by a Scythe Ninja.. MB bios 0507.
It doens't seem to clock any good at all, even if the multi is 6x the board wont post at 300 fsb and will black screen after a few minutes at 290 fsb, memory divider is 1:1. Tried raising all the voltages, no luck. Anyone has got any ideas?
dominick32
08-27-2006, 02:43 PM
Got myself a E6600 and a P5b Deluxe Wifi, with a pair of 1 Gb Corsair TWIN2X-6400 memory, supplied by a Tagan 530 EasyCon. Ohh btw, CPU cooled by a Scythe Ninja.. MB bios 0507.
It doens't seem to clock any good at all, even if the multi is 6x the board wont post at 300 fsb and will black screen after a few minutes at 290 fsb, memory divider is 1:1. Tried raising all the voltages, no luck. Anyone has got any ideas?
Disable Speedstep Technology in the bios.
Disable C1E in the bios.
Make sure memory voltage is manually entered in its required spec. (Mine wouldnt achieve stability until I did this)
I'm experiencing some problem with 300Mhz FSB with my P5B (no deluxe)
Try something else. (300Mhz give me error, 301Mhz pass ok..)
dissident
08-27-2006, 04:12 PM
try setting the multiplier at 8x and setting the FSB to 400 and setting the vcore voltage to 1.45 to 1.5 volts (auto if you want, but the motherboard will seriously overvolt), leave everything else on auto, and see if it works.
I've found the Gigabyte DS3 to be much easier to overclock.. for some reason the P5B boards will be unstable at certain FSB settings, like in the 300's mainly... 400 will work fine but 399 won't boot to windows.
aamsel
08-27-2006, 07:39 PM
The P5B Deluxe I just returned to FRY's would not "play ball" at all with two E6600's that I tried in it. It bluescreened during several Windows install attempt at even stock settings. Kept saying it had a bad or missing file, or that it had recovered from a serious error. It corrupted another Windows boot drive I had. It also had a VERY, VERY hard time loading the Windows XP install files from a known-good CD and CD drive. Took just forever to load the files needed onto a hard drive.
Every time I tried to boot Windows it either reported a corrupted file, said it had recovered from a registry error, and rebooted itself. It rebooted out of Windows at least 20 times, and I did 3 Windows installs that failed.
The ASUS utility CD was also problematic.
Not for me, whatever its idiocyncrasies are, I am not further intrested.
Maybe it would have worked ok at 400+ X 8 or 7, or maybe I just had a dud.
Don't know.
Andrew
pcdoc1
08-27-2006, 07:44 PM
The P5B Deluxe I just returned to FRY's would not "play ball" at all with two E6600's that I tried in it. It bluescreened during several Windows install attempt at even stock settings. Kept saying it had a bad or missing file, or that it had recovered from a serious error. It corrupted another Windows boot drive I had. It also had a VERY, VERY hard time loading the Windows XP install files from a known-good CD and CD drive. Took just forever to load the files needed onto a hard drive.
Every time I tried to boot Windows it either reported a corrupted file, said it had recovered from a registry error, and rebooted itself. It rebooted out of Windows at least 20 times, and I did 3 Windows installs that failed.
The ASUS utility CD was also problematic.
Not for me, whatever its idiocyncrasies are, I am not further intrested.
Maybe it would have worked ok at 400+ X 8 or 7, or maybe I just had a dud.
Don't know.
AndrewAll of the above are a result of memory problems....
aamsel
08-27-2006, 10:39 PM
ok, thx
aggybong
08-27-2006, 10:45 PM
Many people experience the same issues, aamsel. For some anything in the 300 range will completely suck, but moving to 410+ results in stable machines. Why? Who knows :(
aamsel
08-27-2006, 10:50 PM
I may pick up another one tomorrow, and try again.
Thanks,
Andrew
vBulletin® v3.7.0, Copyright ©2000-2009, Jelsoft Enterprises Ltd.