I can't take the credit for this because I discovered it in another forum. However, it works flawlessly. I've now reached 3.92GHz on my EP35-DS3R and no longer have to worry about cold boots wiping out my OC setttings. This should work with S3 as well because the problem with those is also FSB related.
TEMPORARY FIX FOR COLD BOOT POST FAILURES:
Find your highest bootable FSB (mine was 365 FSB). Next, find your maximum stable FSB, RAM and voltage settings in Windows. Now reduce the FSB to at least 80 less than your maximum stable Windows FSB. Enable CIA in the BIOS to Full Thrust. Your computer will boot at the lower FSB, but when CPU usage increases in Windows, CIA will raise the FSB by up to 80, depending on load.
Example:
Bootable setting: 333x9.5, 1.375v (to compensate for CIA) = 3.1GHz
After CIA OC in Windows: 413x9.5, 1.328v (vdroop) = 3.92GHz!!!!
If your bootable FSB limit was 365 like mine, this means you can use CIA to overclock in Windows to 445 FSB. An added advantage is it keeps temps down when your CPU is idle, and it works with C1E enabled.
This is certainly a great hack, unless your CPU has a low multiplier, but it is no excuse for Gigabyte's faulty BIOS. Dynamic overclocking by CIA proves this board is stable at higher FSBs, yet it still won't boot at those FSBs. I hope Gigabyte fixes this soon.
TEMPORARY FIX FOR COLD BOOT POST FAILURES:
Find your highest bootable FSB (mine was 365 FSB). Next, find your maximum stable FSB, RAM and voltage settings in Windows. Now reduce the FSB to at least 80 less than your maximum stable Windows FSB. Enable CIA in the BIOS to Full Thrust. Your computer will boot at the lower FSB, but when CPU usage increases in Windows, CIA will raise the FSB by up to 80, depending on load.
Example:
Bootable setting: 333x9.5, 1.375v (to compensate for CIA) = 3.1GHz
After CIA OC in Windows: 413x9.5, 1.328v (vdroop) = 3.92GHz!!!!
If your bootable FSB limit was 365 like mine, this means you can use CIA to overclock in Windows to 445 FSB. An added advantage is it keeps temps down when your CPU is idle, and it works with C1E enabled.
This is certainly a great hack, unless your CPU has a low multiplier, but it is no excuse for Gigabyte's faulty BIOS. Dynamic overclocking by CIA proves this board is stable at higher FSBs, yet it still won't boot at those FSBs. I hope Gigabyte fixes this soon.