Yeah, sandy = san diego core.
Unfortunately, I couldn't tell you how to recover your files, or exactly why they got corrupted... any number of things can go wrong while overclocking and cause problems like that, but I couldn't say for sure exactly what happened. If I had to guess though, I'd guess that it has to do with the RAM. I unfortunately don't have any experience trying to recover damaged files... so I can't really help you with this, and I don't even know how possible it is really.
My best advice to you, honestly, is maybe you shouldn't do this unless you are willing to take the risk of losing your hardware and data. Nothing personal or anything, just make sure you really want to to this.
If you do decide to continue, you really should bookmark/read through this:
http://www.dfi-street.com/forum/showthread.php?t=20823
That will explain everything you're going to want to do... far better than I could possibly explain. Again, some of this might be specific for DFI boards, but the general idea will be the same.
Now, as for the divider: basically this allows you to lower the speed of your ram. Your ram speed and cpu speed are based on your FSB.
CPU speed = FSB * CPU multiplier
RAM speed is approx. = FSB * divider * 2 (if your ram is DDR)
The ram divider can be anywhere from 1/2 to 1/1, I believe.
Normally your divider is set to 1/1 so your ram speed is:
200 FSB * 1 divider * 2 (DDR) = 400 mhz
So say you set your divider to 3/4 (this may be labeled as 150) and your FSB is set to 200. Your ram speed would be approximated by:
200 * 3/4 * 2 = 300 mhz<---- this is not exact (also explained in the link above)
Last thing: you're going to want a couple programs. I don't have the links handy but they should be in that link I posted above as well, or from google. The programs are:
motherboard monitor <-- allows you to monitor your temperatures
prime95 <-- stresses your system once you have a bootable overclock, run a torture test for at least 12 hours to make sure it's stable
memtest86 <-- makes sure that your ram isn't making errors that could corrupt data
occt <-- torture test, like prime95
a64memfreq <-- allows you to calculate ram dividers