Help!! Attempted OC - now Window's won't boot

Sarduk

Sarduk

Sarduk

Permabanned
Joined
25 Mar 2007
Posts
1,784
Hi all,

So.. my brand new build and first attempted over clock. Now, when I try to load Windows (Vista x64) it fails. It gets to the green loading bar which goes past twice - then at the same point every time the system reboots itself and won't start at all. Loading Windows in safemode fails as well.

Here is the system:
Intel Quad Q6600
4GB Balistix RAM PC2-5300
Asus P5KC Motherboard
ADAPTEC RAID controller (SATA, 2 ports)
2 x WDC3200AAKS in RAID0 config using the above controller
Corsair HX 520W PSU

Here is what I did to get it into this situation;

1) Overclock the FSB to 300Mhz
2) Booted Windows, checked CPU-Z, saw my multiplier was 6 (so I actually managed to underclock to 1800MHz)
3) Changed the multiplier to 9 (300x9 = 2700MHz, nothing too spectacular for a Q6600?)
4) Didn't touch any voltages etc.
5) Started Windows again, Windows startup keeps failing at the same times as described above.


I have tried resetting all BIOS settings back to default settings and still no luck. Could I have fried some hardware? Any ideas what the symptoms are?

System seems to boot fine from Vista disk,

Thanks,

- a very sad JimpsEd :(
 
Last edited:
might wanna post in overclocking and cooling sub forum ;)

read the stickies

only clock at +40 mhz qdr on fsb at a time
 
the bios etc loads fine?

seems wierd have you tried clearing the cmos (moving the jumper on mobo)

odd it gets to the loading windows stage before it crashes out would have thought if something had fried it would had died before then unless it was a harddrive issue but then they are not effected by an overclock. but then im not good at this diagnostic stuff
 
BIOS loads fine, RAID card is loading fine and loading the array, loading from the disk loads fine too.

I have taken out all of the RAM (but one module), same results - same reboot position (few seconds into green bar).

I am baffled as to how I could have caused this through a fubar'd overclock?

I have noticed than when attempting to boot into safe mode and it attempts to load the crcdisk.sys driver, it cuts and reboots then.
 
Last edited:
Is the vcore too low for the processor ? The default my mb sets the processor too is 1.275, but the stock voltage should be 1.325. It may have been going to 6x because it was too low voltage for 9x.

I dont think theres any chance youve fried anything, you havnt really done anything that could add heat, if the heatsinks not on properly maybe it gets too hot to work ?
 
The vCore was set much lower than stock (1.2), I tried upping it to 1.3 but still no sunshine.

Thanks for your input, by the way.
 
Yeh, just looked it up and it should be able to run at that voltage anyway
Here if your intrested.

Have you tried slackening the timings on the RAM , im guessing youve made sure thats at the right voltage ? Sorry just stabbing in the dark a bit here.
 
I'm going to go down the "I corrupted my hard drive" avenue and see where that takes me. Unfortunatly, Vista's recovery console is not liking my RAID drivers so there is no way to go in there and do a chkdisk, so doing a "Media check" via the ADAPTEC RAID controller.
 
Th3D0n said:
is your ram overclocked?
Click to expand...
No, not at all - the clock is stock (533) and the timings are very undertimed (stock is 3-3-3-12 and I had it on 6-6-6-15 (I say I, but the mothoerbard did).
 
mattyrigby00 said:
if you didnt lock the pci-e and pci busses you mightve corrupted your hard drive
Click to expand...
Why would this be the case? Overclocking of the PCI bus wouldn't overclock the RAID controller would it (or cause it to do something damaging to the disks?)

What are the realistic chances that I have fried something? (No voltage changes, barely running long enough let alone under load for head issues).
 
Last edited:
Hi guys,

Thanks a lot for your help throughout this thread. The problem was data corruption caused by my overclocked RAID controller, as I did not lock the PCI bus when increasing the FSB.

I have now done a reinstall and all is ok.

One day, I hope to be able to answering questions and giving support rather than just asking them myself.

Thank you,
 
mmmalas said:
I know overclocking pci crashes the pc, but does that apply with pci-e too?
Click to expand...

It can affect anything that runs out of specification.
I seem to remember the holy grail of motherboards years ago was the Nvidia 2 (AMD socket 462)
That was the first board that allowed you to overclock the FSB without affecting the PCI bus speed.
Then they stuck 4 serial ATA ports on them, and the norm was only 2 where locked and the other 2 got corrupted easily.

You can fix pci-e to run at a certain speed..you could on the Nforce 2 boards as well (AGP)

That's why everyone stopped buying VIA.
 
You must log in or register to reply here.
Back
Top Bottom