if your board can handle it, bios 1.0b4 or 1.0b2. but be warned, if your board cannot handle it, you will lock up, and windows will corrupt itself to an extent (it should be able to recover the sys hives on its own). You may also lock up while attempting to flash out of it. bootblock should save the day, but dont program the bootblock while flashing out of it and to a newer bios (/Sb), just to be on the safe side, and have a blind flash rescue disk on hand. then you can reflash full once your back up (you might find some wierd things with not being able to post after you make a change and having to switch off psu, unplug, wait, then plug, switch back on, then power up to POST, if you dont program the bootblock).
use awdflash via dos to flash. if you use flashmenu, that is a huge risk for corruption. please do not ever use flashmenu. you can get latest awdflash from abit's site. 8.23K is the latest for this board. you can use the /tiny string to flash back before the 12 bios.
ex: awdflash /tiny nf7d_1X.BIN
if your board only likes newer bios's like mine, you can try d22beta king or d22 3d fire. 3d fire was a bit more stable for me (with voltages, etc.). i lose 2mb/s with 3dfire against betaking. rollback to the stock memory controllers which windows installs. this will gain you about 7-10mb/s, sometimes even more, depending on where your FSB mark is. both those bios revisions should have the stable SATA version in them, so as not to cause corruption.
on 12x and betaking/3dfire you should be able to hit 228 or so if your ram can handle it. the cpu may also stop such a high fsb at that multi as well, as most everyone with mobile chips is stuck around the same fsb mark (218-225). i have only seen one chip that did 11.5x244. if you can get your ram to play close to 235-240 range, drop to 11.5. some of the multi's appear to be "borked" in d22 when pitted with the mobile chip. use diff multi's to test for max fsb. 9x was a no go for me. 8x i was able to find my max fsb. then test on 11.5 and 12.
some say for NF7, dimm slots 2&3 work best. i tried both 2&3 and 1&3 (my old asus loved 1&3). i am using 1&3 right now, as this will give more air circulation for the ram. with d22, i really dont think it matters which DC slots u use. but ill know more once my MOSFETS are sinked and i can bring the fsb up a bit more. ill reply back to this thread once thats done.
keep yourself on cas2, as this will perform the best, even if it does force your fsb clock a lil bit lower. unless of course you can hit the 240 range with cl2.5, then by all means go fer it

try to keep your timings as tight as possible, but stay loose until you can hit max. cas3 doesnt work well on nF.
if you use CH5 ram, do not go over 2.6vdimm. the ram hates voltage. especially the newer CH5 PCB's. ive heard of older twinmos CH5 loving voltage, which is wierd.. but i guess the VR implementation as per JEDEC's specifications didnt go through, as my same ram didnt have the VR implemented in the early stages. The tightest RAS to CAS can be is 3. tRAS of 11, especially on this board gives a huge boost (more then it did on my old asus).
enjoy
