BTW - Either the new bios or the mem I installed has fixed the EZClocking utility. Its now fully functional and isn,t bad as well as the rest of utilities with the exception of winbios that doesn't work with the new 1.10. HAven't checked this morning to see if it has been updated.
Haven't gotten around to playing with it because work calls, but it appears that the 1.10 fixes have done it.
I have had the same boot problem as a result of setting my mem timings to the tightest, on the Geil not the Mushkin, and all I had to do was powerdown clear cmos and reboot. The screen you see is normally associated with a corrupt bios. Its looking for you to put in a disk with the flash and bios file on it to reflash. Strange, but not uncomon.
I was fortunate enough to also buy a 2.8c that was of a later version and it has proved to be an excellant, but I now think that the 2.4c is a better buy as I have seen as high or higher oc's that alsao allow you to max out the DDR because of the lower multiplier.
"Also I don't understand how some people can get upto 250fsb on this board, I can't it stable over 240, any tips?"
You also have to realize that Shoman is using an slk with a hell of a fan on it and I am using water cooling to get to the 250FSB. Others with vapor cooling are getting oc's in the 3.7's with the same processor, so I would say that your 240 with a Zalman is damn good, especially considering the noise you don't have to suffer, and the worry you don't have about leaks like me.
Plus, as Shoman has said he has dropped down his FSB, which I will do also once I see what it can do. OCing is mostly to see how fast the car can run, not try and run it at top speed all of the time. A difference of 5-8 mhz makes no real world difference, its just trying to eek out every last mhz until you take your system right to the edge thats kinda fun. Sucks when you have to go through pains of trouble shooting like you can see portrayed in my posts, but sometimes it is the luck of the draw as far as processor, ram, et al. Plus I don't know what you consider stable, but I myself simply run Prime95 torture test for about 9 to 10 hours before I declare my system stable, most that actually use prime for its intended use run torture test x 2, by creating a seperate folder and running simultaneously at 1024k setting for about 24 hours to ensure accuracy (this is way overkill from my view point, but if your using Prime95 client it makes sense). Reviews usually run Prime95 plus another benchmark for 24 hours before they declare an OC stable. In truth, Prime95 is overkill, as there are very few programs that tax your system or require the accuracy that Prime95 does, or the others like seti@home; folding@home, et al. A practical stability test is to loop 3DMark for an hour or so and see if it crashes and then run Sandra burn in for a 12 hour period, if neither crashes then you are probably as stable as you will ever need to be.
242 FSB Shoman?