Well, it's hard to give exact details of what to do. It definitely takes some trial and error...
That said, you can find some good guides. Here's one:
http://www.tomshardware.com/forum/256144-29-1156-core-o...
The gist of it tho would be that you increase the base clock, which in turn will increase the CPU, QPI, and RAM speed. You don't need to worry much about the QPI unless you take the base clock up to 190+ (which is high). You definitely need to worry about RAM speed. You can easily google the suggested timings for your RAM (run it's full number). If it's 1600mhz CL9 let's say, then you can't run it at 1670mhz CL9. At most, maybe 1620mhz CL9 or something... it's finiky. The good news is you have more options, like 1400mhz CL8, or 1800mhz CL9. I know this probably doesn't make a lot of sense right now... CL means "cas latency"... represented as 8-8-8-24 or 9-9-9-27, or 7-7-7-21 etc... you'll find these generally are the first 3 numbers in the "timings" section of your RAM. You can usually leave the other timings to auto.
Umm... CPU, RAM, and QPI speeds are all based of a multiplier of the base clock...
As CPU speed goes up, it can require more voltage. Take the voltages off auto. Vcore and VTT (also sometimes known as IMC) are the two which affect CPU stability. After raising the CPU speed you can save and try to boot to windows then run a test program like Intel Burn Test. If it gets errors, reboot into BIOS and add more voltage... maybe 0.02V Vcore. If it doesn't work, raise again. If still not working, you might need to raise the VTT/IMC by a similar amount.
Just to try something simple, you probably have 1600mhz RAM. Stock base clock is 133 so to get the RAM at it's rated speed, that needs to be 160. The RAM is multiplied by 10, 8, or 6... so 160x10=1600mhz. This will also boost the CPU speed nicely. I found at 160 base clock I could leave everything on auto with no problems but that might not be the case for you.
I hope I haven't confused you. That guide has a lot of good info and there's more out there. Just remember to test when you make changes.