Overclocking question

[Fattysharp]

Hey folks, I haven't seen this before and hopefully someone here has. I am sure it is something simple that i am missing. I have been a forums lurker for a while, although I rarely post.

I am working on finding an mid-high overclock for my c2d e6400. I am using a gigabyte board with the latest f9 bios. I was starting out with a 333fsb and 7x multipler as a starting point with everything else underclocked and it would POST, then give a boot device failure. No longer recognized my HDD.

I tried it with a 333fsb and 6x (everything else underclocked still) and still the same issue. My board should handle a 333fsb no problem, so I am unsure why i am getting a failed boot device. OS is vista home premium, Clean install this past weekend.

As soon as i reset the fsb back to 266 boots fine.

Any ideas ? PC stats are in my sig.

 

[spinejam]

make sure your memory / fsb ratio is set properly and check memory timings are correct.

 

[Fattysharp]

Originally posted by: spinejam
make sure your memory / fsb ratio is set properly and check memory timings are correct.

Timings are set to 5-5-5-18. The adata modules are set loosely by default. They are also underclocked, 667mhz.

I have also tried it with a 2gig kit of ocz 5-5-5-15 also underclocked at 667mhz, same boot device failure error.

 

[Markfw]

set the memory multiplier to 2.0/

 

[betasub]

OP: your sig doesn't show your storage devices or boot order. Your overclock may have changed the clock setting for whatever timing the controller for your storage device uses e.g. PCIe.

 

[Fattysharp]

Originally posted by: betasub
OP: your sig doesn't show your storage devices or boot order. Your overclock may have changed the clock setting for whatever timing the controller for your storage device uses e.g. PCIe.

Storage device is the 320gig baracuda in my sig. PCIE was set to 100 static to avoid it moving when i changed the fsb. Boot sequence is HD/CDrom/CDrom. Should also mention i am using a Scythe rev.b cooler.

I was doing some more testing, and turns out it is the fsb setting that was causing the issue. No idea why it did not like 333, but with all the same settings it booted fine with 315fsb.

I have now tested it out, and i am getting a clean boot with ..

315fsb
e6400 x 8 @ 2.5ghz
memory 5-5-5-18 945mhz @ 2.0v

I had to up my chipset voltage by .1 and my memory voltage .1 and cpu voltage raised .0025v (I think that was it)

Not an amazing overclock, but seems moderately decent for the parts. Going to check for stabiltiy and temps now.

Still curious about the device boot failure though. First time i had seen that one.