Quote Originally Posted by turtletrax View Post
I would say it is the CPU. It is pretty hard to damage a mobo without doing it physically or running it overheated for long periods of time.

I am guessing you dont have another proc to test with? Easy way would be to find another one to test with and start to narrow down the culprit. Test with a new proc first, then if still the prob, test memory. If no go then it gets more interesting. You would then have to look into mobo, psu and so on down the line.

I havent scrapped a i7 proc yet but I did really screw a Q6600 and it exhibited extremely strange behavior close to what you describe. Zsamz has it in a family members rig running sub 2Ghz to run stable, and it was all done with a high clock, multi hours Prime run.

I hope you get it sorted
I've just finished a long gaming session with no freezes; using my old overclock of 4.2Ghz; but just using dual channel 4GB RAM. System was rock solid, I also did a LinX pass on it without a hitch. Could I be lucky enough that the RAM stick I pulled out was a bad one? I did a windows memcheck (from the F8 menu as you boot), and it said my memory was fine ....

Perhaps there is a reduced stress on my possibly damaged i7 930, I would imagine it'd be easier for the memory controller to manage 2 channels rather than 3 ...