All ram can be burned in, and I don't mean killing it with alot of voltage
As for the cpu, if I got a new one well...
I would find to highest oc with either the lowest voltage, or the highest sustainable oc period.
Then drop the vcore where it's not stable, and hammer the crap out of it until it is stable.
You have to do this where it gets the least amount of errors possible, meaning no errors.
Do this by taking away cpu time from teh prog that you're using to hammer the cpu.
Prime works and s&m works.
Prime is easy simple stuff.
It fails and you try again.
If it does'nt bsod on you or reset, etc.
I myself now use s&m to do that sort of thing, and use prime to burn in memory 1st.
For my cpu, a athonxp, I use the fpu test since that's the bunk part on my cpu.
I use the lowest load %, ie 5%.
If it's to much where it gets an errors or so, I take away seom cpu time from it by running stuff in the background.
Eventually after enough passes in loop mode length, I can up the load % and I don't need to take away cpu time.
Cool it much as possible too, this helps.
But watch out, don't get your hardrives to cold, the mid 10 c's and lower are dangerous for hardrives as I found out the other day.
Keep them around 20c min.
This is all up to you really.
Best thign for soemone liek you to do is either find the highest oc with stock votlages or highest oc period, then hammer it with prime without dropping the vcore.
Just hammer it for about 30hrs or so like that.
It'll get faster and faster by doing it.
If you want to later, you can drop the vcore a step and use prime, it may fail, but you can keep trying until you get say 12hrs worth, it's all good.
But it won't be 100% stable,as prime is'nt really anythign hard to do 98% of the time.
But it'll help.
Upping the voltage on any part thinking it's gonna help it is stupid, no offence to anyone that's tried this, I tried it too.
It makes parts slower, even intel did a study on this and said so them selves.
Also it tends to kill memory, why?
Because errors = bad, breaking in using memtest tends to keill memory unless you're lucky enough to be close to the edge, and beable to pull off a breakin.
It's best not to try that.
None the less you dn have to do any of this.
But if you do, you'll find that you'll need less and less vcore down the road.
Liek I said, all you need to do is prime the crap out of it, even at a stable vcore, but no more then what's needed to pass prime.
Oh yeah, the better the psu is(ie the more cleaner power, less noise I mean), the easier this is to do.