xbadwolfx :
...
Also, please don't treat me like a retard, ...
No retardation implied -- it's just that you only listed a few items in your "specs" when you need to list the model numbers of everything in your system to help give us an idea of your setup. It'll also help a lot if you could clarify your meaning of "safely" OCing. If you need pretty much absolute assurance that the CPU won't be damaged and that wrong calculations won't be made, then OCing is not for you. Otherwise, good first steps are to download various "standard" tools, including:
1) memtest86+ (basic memory test, any errors during an overnight run indicate a problem)
2) Orthos (or similar Prime95 variant setup to automatically test multiple cores), to be run in both "small FFT" and "blend" modes.
3) CPU/system ID/setting reporting tools such as CPU-Z (this will also help you figure out your CPU VID).
4) Temperature reporting tools such as coretemp.
Also, realize that your CPU does not have the best OC potential because of its 1333MHz FSB. Briefly, how fast you can OC the *core* of the CPU depends mostly on the design of the CPU; with 65nm Core2Duo CPUs like yours that *core* potential is probably in the 3-3.5GHz range without heroic efforts. However, the circuitry involved with the FSB places another limit on OCing potential, and this involves the MB design and RAM as well. Running the FSB up to 1333MHz shouldn't be a problem on any recent MB, as they were designed for that speed, but running faster than that could cause problems. You have an excellent-quality MB, so this risk is lessened. However, your CPU has a native 1333MHz FSB, so OCing it (which involves increasing the FSB further) may run into FSB/RAM related OC limits even if your CPU *core* could otherwise handle the speed.
That's why CPUs with 800MHz or even 1066MHz native FSBs are better OC candidates, as OCing them to a 1333MHz FSB (a 66% or 25% core speed increase, respectively) should avoid FSB/RAM issues.