If you start a heavy AVX workload like Prime95 small-ffts with AVX or LinpackXtreme, the system always crashes with an “AVX Light” tested profile.
Even though only a very small part of the user base might have a use for this, such edge cases can often become critical. If I could find fault with anything, it would only be the persistent lack of an “AVX Heavy” test mode.
This imperfect ‘light test only’ is made more complicated by the lack of AVX heavy mode, workaround for which is to: “increase the voltage … by 75-100mV and then manually test stability for these cases.” The issue is compounded here, as the light testing does not stress the CPU enough to warn CTR away from higher voltages, so adding more voltage will just compound the high-load temperature situation more: When higher loads kick in, these ‘test stable’ settings then overwhelm the CPU and cooling system with excessive clock speed and voltage resulting in high temperatures. This is especially important for higher core count CPUs on setups with good enough cooling to mask the issue while testing at these low loads. The issue with this default/limitation is that it allows for potentially impossible clock speeds and settings that aren’t stable at heavier loads, meaning under CPU stress you face an almost guaranteed possibility of overheating. Instead of defaulting to a safer and more rigorous Heavy AVX option, it instead defaults to-and indeed only allows-the aptly named Light AVX mode. Revisiting the topic of CTR’s safety, our first point of investigation is CTR 2.0’s built-in stability testing.ĬTR 2.0, the version we originally tested in our first article, is lacking the ability to select different levels of AVX workload intensity that it can use during it’s built-in tests. Last and certainly not least of all, our continuing balanced assessment of CTR for you, the reader. “1usmus”), more testing results, responses from respected overclocking experts, and an official statement from AMD. You can look forward to some responses from the author of CTR, (Yuri Bubliy a.k.a. Today in this follow-up article, we will share some of the developments in the situation and do our best to address some of the passionate questions and hot topics that arose in the debate following our original CTR article. Guys, gals, and non-binary pals, I think we just had one of those exciting moments. It’s all very normal, but good journalism is trying to keep things objective in pursuit of the truth, to the benefit of our readers. If you write critically about a product’s flaws, then creators are upset and you’re biased again (or incompetent). If you write glowingly about how great a product is, the competition cries foul and suddenly you’re biased. Unfortunately, those are often the exact situations where emotions run high.
Your team writes something important, people engage with it and it generates a large response. There are times when being a journalist is exciting.
0 kommentar(er)
