Nobody has ever attempted to tell me whether it's a fruitless exercise. The discussion brought to mind something I try and do with LinX. Better than that, OCCT seems to do a good job at trapping the errors and recognizing them in real-time, so a revisit to the BIOS screens is merely preceded by the "Shutting down" Windows screen. So just getting such guidelines for wading into the trial-and-error of it relieves the BSOD panic attacks. Eventually, someone publishes a graph for a particular processor plotting VCORE against speed settings, some showing a curve for the top-end binned processors and another curve for the "potatoes". That might be true if one goes into the enterprise half-blind to full information about the CPU, but "those people" are good guinea-pigs. I think there is still an extant opinion that enthusiasts will invariably have BSOD experiences with their over-clocking adventures. The developer - I think he's French - has done a nice job with that testing suite. I had discovered that the OCCT:CPU tests can uncover errors in an hour that wouldn't show through ten iterations of IBT or LinX. Running Prime95 for 24 hours is a huge inconvenience, even if one is replacing a machine still in service and doing it at a leisurely pace. But as i also volunteered from my own experience, it's still an addiction of sorts. Ĭlick to expand.Thanks for sharing your experience with it.Īs some of our veteran colleagues here suggest, over-clocking is becoming less and less "necessary" given the performance just from recent-generation Intel CPUs. This time, I noticed the test durations are limited to 1 hour unless you "subscribe" to it for a year, so I did that. I don't remember ever purchasing OCCT, but I was using it as much as LinX, IBT or PRime95. OCCT has built-in a LinPack test and memory tests, with settings for "data set", "Mode" (normal or extreme) and Load type (variable or steady) - as well as the instruction-set choices. Somehow the the earlier chip, I'd missed the opportunity to use the "Negative AVX Offset" feature, so this go-around taught me some "new stuff". I'd also observed over recent years the value of the OCCT:CPU tests, which can be chosen for "SSE", "AVX" and "AVX2". I've seen custom Prime-95 setups that can detect errors within an hour that could otherwise be missed. I'm always looking for reliable short-cuts to stress-testing, and this month was a special case. ![]() But upgrading from the Skylake to a Kaby was still fun. Looking at the wallet-damage, I could've been up and running for the mere price of Fed-Ex RMA and a two/three-week wait - about $88-worth. I probably wouldn't be poking around these tech forums so much over the past month, but for my vape-pen USB disaster.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |