Wow, being away from the forum for 2 days and got 500+ messages to read !!! guys calm down... I can't keep up here
So here is where I think I left off
Originally Posted by gupsterg @Benus74Post 10061
I said ignore the red box in image
, that is motherboard temp sensor, that sensor was confirmed to me by Elmor.
PCH is under red heatsink outlined in below image.
I can not confirm if PCH has internal temp sensor or one placed on mobo at close proximity, only @elmor
or another more experienced person may confirm for us.
I only know where PCH is
I think I've forgot to read that part
and seeing that red box was just claiming: I'm your PCH diode
So yeah, I should have read twice, but as @Raja@ASUS
confirmed in the asus forum, this PCH temp is just normal:
Originally Posted by gupsterg
That temp is normal for a PCH.
Originally Posted by Raja@ASUS
Two of us have found that setting ProcODT to the correct value for the memory config solves a lot of POST issues. One just needs some patience to tune it.
do you think there could be a way to measure the correct ProcODT
on my mobo using a DMM?
I know that you have to do some tweaking and long testing, but as this is a resistor value, I thought that maybe by measuring voltage and amperes at some precise points on the mobo I could then find the correct value
(the famous Ohm's law: R = V / I)
Originally Posted by nycgtr
K will give it a shot tonight. Thanks for the reply.
I've also got a 8*4 kit, so I'll be playing with this over the week-end as well.
Maybe with all of us playing with this we'll get some good stats and results
Originally Posted by Raja@ASUS
Most of my stories are lulus I've committed myself. I may share them somewhere at some point (have thought about it many times), but now is not a good time - we're trying to promote testing of a new UEFI build and trying to appear that we have a semblance of understanding the basics....capeesh?
Like seeing a MOBO committing Sudoku?
Originally Posted by gupsterg
- shutdown PC via OS
- mains still active to PSU
I will have borked boot only on 3200MHz intermittently. Each time I use 2933MHz I have not had one. Tried plenty of ROMs, ProcODT, VBOOT/VDIMM, SOC, etc, etc ...
Can not be bothered now ...
Happy with using "Sleep". I see ~4.0W from wall plug meter with shutdown as highlighted above, "Sleep" is ~5.0W. For the sake of my sanity and getting back to normal PC usage without being in UEFI all the time I can live with ~1.0W power usage
, I'd be happy with 3.9GHz @ 1.319V, defo better chip than mine, 3.8GHz is a tad higher for me than your OC. Yeah 4.0GHz is bench stable for me, using 3.9GHz voltage offset of +250mV = ~1.44V CPU Core Voltage (SVI TFN).
I wonder how @Benus74
is getting on with his R7 1700?
I've been running on 3.9GHz for a few days at +0.18750 and it's been quiet stable I'd say, the only issues I've had was with my memory running at 3200Mhz, it was giving me random boot issues, and some time 3E code right after a reboot going from linux to windows.
So for now I've been putting my memory back to 2666Mhz and it's been very stable so far, no crash, no reboot issue, no cold boot issue (even though I never let my PC go cold as I'm folding over night
I'll have to test the new BIOS and some ProcODT settings to see if it helps with my memory OC, but so far I was only able to run 3200MHz with released timings (using 20-20-20-48-78 2T) and DRAM voltage of 1.35V.
Even though the timings were released a lot I could see day to day improvement in my work
I'm a java developer and I work on a very large system with a maven build containing 831 modules (as of today), and when compiling the project using -T16 (to use 16 threads) then it takes 1m6s with the 32000 mem, and 1m18s when running at 2666Mhz with 16-16-16-39-63-2T.
So even if the timings/speed ratio is very similar it does play a lot when doing computational intensive operations like compiling code, 15% increase is really a lot to me
And for me this is the best measure I have to know if the OC is worth it or not, as I'm doing this many times a day
Originally Posted by alucardis666
Yea I did that but I didn't see it down clocking.
I've had the same issue and the problem was the windows power plan provided by AMD was keeping my CPU at top speed.
Thanks to the help from @gupsterg
I've been able to solve this with this trick:
Originally Posted by Benus74 @gupsterg
This made the trick, I've opened the power settings in windows and my Minimum processor state
was set to 90%
, but yours is 5%
Changed mine to 5% as well, and tadaam, my CPU is now switching to 1.5Ghz on Idle
Thanks a lot for your help
But I think you've found your solution for that
Originally Posted by jugs
Yes... Hi Linux developer here... You mean they could ask ASUS for a developer guide that they usually release like I did here
Thanks, I was having issues with P1/P2 as well but I haven't tried again on 0081. Will do.
What... at least 2 Linux users here !!?
I'm not sure I'll try the asus tool as I'd like all my OC done through the BIOS so I can benefit from it during most of my time when working in Linux.
For me Windows is just useful in the evenings to do some gaming.
Originally Posted by elmor
If you or someone else is up to coding a Linux version, I can help provide info on how to do it.
Yeah let's have some more feedback first, seems to be a bit buggy trying to install the service. I thought AGESA 1004a would have fixed the realtime ratio changes since Ryzen Master works now, but seems they implemented some kind of workaround rather than fix the initial issue. Will try to look into this. Anyhow, you can still use this application without HPET if you don't change the P0 ratio in the OS.
Same here... I'd be happy to get access to the doc.
I'll do some ProcODT testing, I'd love to get my memory back at 3200MHz and getting stable with lower latency, but I knew that 8*4 kits were going to be harder to get working... but I like challenges
(or maybe start coding some linux tool if we get some nice API