It is a partial switch off, it restores ~70% of the performance in some software but not in others. Performance will still be slow, especially anything which depends on memory bandwidth/latency.
It's the same with thre BETA BIOS I mentioned actually. Perf. isn't the same with a BIOS without the patch at all (like BETA 1.3 and earlier)
So you're at +520 on 400 RAM? Have you tested Memest to see if your RAM is stable at that speed? I hope you have good RAM that can run that stable, ProMOS and Elpida chips won't, however Microns will run that and higher with ease.
The values I'm looking at are tRC and MaxAsyncLatency. They usually would need to be higher for stability of 400MHz RAM.
That's the same problem with my use of EVEREST too. I don't recommend using it apart from preliminary testing though, it doesn't test CPU/RAM as rigorously and properly as done by P95/OCCT/Memtest/gaming/Videoing and the temps/power don't reach what they do with P95/some benches/OCCT neither did it catch easy errors caught by others, so its not an ideal reflection of common day to day loads. Because when load testing, you need to simulate max core load to show the core is stable no matter what as the core load-line voltage willl fluctuate under arious loads and thats what will decide if your core is stable/unstable.
Which BIOS are you on?also speedfan does not detect cpu temps either, core temp is working fine however.
What do you mean exactly?
Opening these software made EVEREST start reading incorrect values?
If so, what exactly is being read incorrect?
Which EVEREST test did you run?
Opening AOD before oher monitoring tools is a regular thing I did because its buggy and unstable if another hardware monitoring s/w is opened before it -> not when after it though.
Same thing with many softwares, even HWMonitor.
Your choice really.![]()
Bookmarks