Well, there really is no RIGHT opinion regarding the prime thing. Hell, i run a RAID 0 so I cant be that concerned about things blowing up on me - lol.
I guess my point is that there are MANY reasons Prime could crash you after 5 hours BESIDES your overclock being bad. I just can't see how running your CPU full out for hours on end does anything but wear out ur CPU.
But I'm not gonna throw away a sweet, fast, functioning OC just because it crashed after beating it senseless for 7 hours. Of course, you may feel differently and that is fine. Just a matter of taste IMHO.
MY REQUIREMENTS FOR AN OVERCLOCK:
1. Boots Windows.
2. Runs my desktop apps.
3. Plays games full out.
4. Doesn't crash while I am doing 1-3.
For me, anything more than that is overkill.
1. Your RAID0 array is more dependable than an unstable overclock, period. Bad reference.
2. Yep, Prime could crash due to many things, like an unstable IMC. Or your 2200mhz HT Link.
3. Define a "functioning" OC. Lots of OCs boot to Windows and run several low-demand apps without any visible issues, but instantly blow up in your face while attempting to multitask or run large apps or play games.
4. An unstable OC is probably not going to do 50% of your stated requirements. Memory controller errors will be quick to surface via BSOD on random occasions. Hard reboot? How's your RAID0 now? Oops.
It's in your best interest to verify the stability of your OC with testing, take the advice from people on here who have been down those roads before. It's not worth risking data corruption in a month's time (or longer), because it can be alleviated by a good testing plan over the course of a few days -- even less than a few days if you're going conservative. You want an OC, but you don't seem to want any of its benefits, only the potential shortcomings because it looks to you like everything is functioning correctly.