e6600 and 400fsb problems

I will try and get photos of my bios up in the next week. I have given in for the time being.

I will touch the northbridge to see if it is getting hot or not:) My case is a mess of cables with poor airflow though!
 
No worries! :)

If I managed to explain it properly then you will be able to answer this question!

  • If an Intel® Core™2 E6600 is set to run at 3.5GHz (7x500) then what frequency will the NBCC be running at?
 
Another update!

Tried all fans on full pelt, including cpu fan.
Tried the intel burn test with 8x400fsb with the case open as well to see if the northbridge temperature was causing issues before. I can touch it with my finger but it feels hot (not burning hot). With the fans on silent the temperature of the nortbridge is uncomfortable to touch (at stock) but nowhere near as hot as it was on my old DS3
The intel burn test STILL failed at 20% pass over 5 tests:(

I have some photos of my bios during the overclock here. I have the FSB strap at auto but chaging it did not do anything of use. I have tried increasing all voltages but still nothing!
The cpu will boot to windows at any fsb I have tried (266-400) and any multi (7-9). The ram voltages and timings are the stock ones specified by OCZ.

EDIT: Thanks for all the help so far big wayne

DSC01101.jpg

DSC01102.jpg

DSC01104.jpg
 
Last edited:
Hey mglover070588,

I think you may need to reset the BIOS and start again leaving as much as possible on [Auto] to see if anything changes . . .

I'm thinking there may be an issue with your memory timings, FSB-Strap and perhaps voltages.

It may sound like a pain doing a reset but I find it helps in situation like these where you hit a brick wall! :p

If we get some joy you can start manually setting voltages, timings etc but for the moment it may be an idea to see how the board thinks it should be done.

Take small steps when altering the BIOS with plenty of reboots inbetween, maybe leave your memory on full [auto] and see how far you can get.

You got lots of things to try, different variables etc but the main thing is leave the memory alone until you have no choice but to switch to manual over-ride.

Sometimes in trouble-shooting you come across things that are *illogical* and assumption of these things normally work against you.

Sorry I can't help more at this time but it's pretty tricky to catch the tail end of an overclock without knowing the seperate steps involved in getting there! :p
 
Back
Top Bottom