Quote Originally Posted by TheOtherDave View Post
The 2 times I tried it it did require a CMOS reset

I have been using AOD to turn the TLB patch off (at least I think that's what the little button at the top of the screen does based on my reading).

Or will the 1.2 bios not allow it to be disabled at all?
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)

Quote Originally Posted by jonspd View Post
http://www.jonspd.com/jonspd_uploads...s/untitled.GIF

thats what it's at now.

I really don't want to revert to 1:1.66 divider as I said cpu clock is to far off with that divider. However I will be testing it again and post the SS of 1:1.66 in a few hours maybe.


It is totally stable at same setting as SS posted above with a 259 fsb. (prime/memtest/3dmark06/32mb super)


Edit: Shet I forgot to put the cpu-z dram pic in that ss but dram is at a 1:2 ratio ATM.


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.

Quote Originally Posted by Manicdan View Post
for those trying to help me, aka jonspd.

i installed using the cd it came with, this is a new OS and it worked fine on the last one that ended up dying due to hard drive corruption. loading up cpuz is fine, with everest's cpuid, memory testing, or any other part of everest locks the program up. i can run the stress test but i leaves the temp graph blank and the cpu load one works fine, but i cannot click on preferances, its greyed out.
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.

also speedfan does not detect cpu temps either, core temp is working fine however.
Which BIOS are you on?

Quote Originally Posted by Manicdan View Post
either way it seems windows is not detecting motherboard sensors properly and i would like to reinstall them, but since its the mobo were talking about, i wanna make sure i dont screw things up in the process.

ok so its worse than i thought

i loaded up these programs in this order and tested everest after each one
amd overdrive
cpuz
coretemp
atitool

and aparently ati tool switching from 2d to 3d clocks and back trigged everest to detect things properly
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.

Quote Originally Posted by jesteronyer6 View Post
I was thinking of getting the DFi board but after reading this thread looks like I am gonna own a Platty again.
Your choice really.