Quote Originally Posted by raju View Post
memtest and prime are 2 entirely different beasts, and passing in one will not guarantee passing with the other. Just stressing one area of the board at a time never guarantee's stability upon simultaneous load of CPU, memory and pcie lanes. I don't run prime anymore, as I can generally dial in where I can run 24/7 without it, part of what put me off was looking back over prime history to realise the code has needed slowing down or speeding up based upon new topologies, and at times the changes were not made fast enough. That being said the shutdown issue is something I have seen myself, your best option is just to OC that processor by feel of what you run day to day, once you have been oc'ing for a while, it's not too difficult to do..
I don't know if we are on the same page here, but I'll try and explain again why i don't believe it is memory. Memory is running as we speak with the E6600 at 950 4-3-3-6-2t 2.2v with prime running in background. I have used this same memory on 6 EVGA's, 2 Stikers, 2 Gigabytes 680i's, 2 Abit 680's and a foxconn 680i lt. Never any shutdowns. I stated in previous post it even shuts down at 700mhz. It's sold as 1200mhz memory so 700 is way under clocked. It also shuts down with the mushkin 2x2gb kit installed. I've used that memory in half of the above boards with never any issues. It shuts down at default settings as well, that is no overclock on memory or cpu. It runs memtest86 at better than rated timings with no errors. If i was basing stability on just one of the above statements i could understand why you would say it could be memory. but taking all of the above statements in to consideration, I can say with certainty that memory is not causing the shutdowns.