I did, it was useless. The other utilities proved to be more useful. There is no CPU throttling being reported anywhere. For some reason, the BD PROCHOT signal is responsible for the throttling.
Ok, so i debugged prime95 parser by adding bogus input in local.txt. It seems that somehow it remembers old state of local.txt even after you correct the error and save the file. The reliable way is to delete local.txt and edit local.txt again.
AVX and no AVX both throttle, and there is not...
I tried Prime95 after adding CpuSupportsAVX=0 in local.txt but it seems there is no difference whether this line exists or not for everything.
Voltage, power and throttling are identical. I think the option does not work, but there is no way to confirm, nothing gets logged by the programme...
The BIOS settings are very limited, the temperature limits are way too comfortable, something like 110 degrees for the voltage regulator etc. There is really nothing relevant I can tweak, remember also that H67 is a locked chipset and 2500 is a locked chip. In theory, I'm not hitting any power...
I know it's ancient history but nonetheless I was debugging my sandy bridge system so here goes. Intel board DH67CL, core i5 2500. I was running linpack with the latest intel burn test utility, and the result is the CPU downclocking from 3.3GHz to 1.6GHz for about half the run duration. Maximum...
Maybe it's just Asrock that has the problem according to this:
http://forum.asrock.com/forum_posts.asp?TID=8333&title=any-word-on-ecc-support-for-raven-ridge
What they're saying the way I read it from their site is that:
1. Pinnacle Ridge supports ECC & non-ECC
2. Summit Ridge supports ECC & non-ECC
3. Raven Ridge supports ECC only for PRO CPUs and non-ECC for the rest
They are saying that the APUs don't support ECC, but the PRO APUs will support...
Some more questions for you guys. I just realized that those extra volts that the motherboard applied on the DRAM are actually overvolting the integrated memory controller of the CPU. Since this guy plans to keep the rig for 10 years I worry about degradation of the CPU. So how do I avoid that...
Thanks for the info, it's true I don't know anything about overclocking. What I have heard though is that if you're running the CPU memory controller out of spec you are actually overclocking the CPU.
This site uses cookies to help personalise content, tailor your experience and to keep you logged in if you register.
By continuing to use this site, you are consenting to our use of cookies.