dc8flyer

bcavnaugh
Both my cards have shown 7000 in all versions on PX1 and Before Installing any PX1 in GPU-Z as well as GPUShark that are Active.

I see you have two 2080 ti's. I only have one 2080 but comparing your PX1 readings to mine at idle:
 
Adjustments:
Memory Clock +700
GPU Clock +170
Voltage = 80
Target Power = 120
 Idle:
Memory MHz = 405
GPU Clock MHz = 300
Voltage = 719 mV
Power 8%
 
Before 3.10 and stressing then unloading the Card, the readings would drop back down to idle loads. After 3.10 the Card would never return to idle loads and I would have to reboot the computer to stop the Card from running high with no loads. The loads would stay at Memory 7000 MHz and GPU Clock well above 1000 (cant remember exact number)
 
That is why I think your readings are high for idle even with two cards. Should try one Card and check PX1 again at idle after reboot then idle again after load.
 
Seems something in Card isn't allowing Card to rest after releasing it from a load. I did go back to 3.9 but the issue remains after 3.10 changed something that did not correct after going back to 3.9

dc8flyer
Do you think the memory being set at 7000 MHz or above while idle and no load is correct. The one card not monitored by PX1 dropped to 405 MHz. I wonder what the memory MHz would show with only one card installed after a fresh reboot vs gaming for awhile then closing out the game and seeing what the memory MHz would be.

With my one card after a fresh reboot and PX1 on the memory shows 405 or so. After gaming and closing out the game the memory hangs at 7000 MHz. It still seems to me that PX1 is forcing a higher memory MHz when it no longer needs to. I noticed this change after 3.10. Before after closing out a game the MHz would drop back down to 405. I went back to 3.9 but the memory hang continues. Not sure what would cause this memory hang.

I did notice your one card not monitored dropped to 405 MHz which is where I think both of your cards should be after a fresh reboot / no load state with PX1 on. During gaming the MHz should increase but after closing out the memory should drop back down and not stall at 7000.

Just seems something got programmed into 3.10 that keeps memory from recovering.

dc8flyer
Still doesn’t explain why the memory is so high. As I mentioned, in the past idle memory would drop back to 405 after closing out gaming. Now it freezes at 7000 until I reboot. We shouldn’t have to reboot to get the memory to settle back down to 405.

Maybe next version.

Sajin
video shows you how to get to the vf curve turner/oc scanner.

golfking
bcavnaugh
Gave 3.11   a test run in the post 3days ago ...do you think it could be a small  client left behind ....like the LED issue were we needed to go into the add/delete and reinstall.
because frame time/rate  worked on the first version i installed? 3.9
i reinstalled 3.9 and no frame rate/time on that one 3.9 now
 
also a very strange thing is happening on my HDMI port out. total unrelated frame rate
i have dual 4k monitors setup
DP YAMAKASI 27 inch. run @ 4k x 2k, 3840 x 2160 (native) 60hz
 
and the other HDMI Sharp 4k sharp 42 inch. run @ 4k x 2k, 3840 x 2160 (native) 60hz
when i turn the sharp 42 on i get a blue haze, i have to reset the refresh rate to make the picture clear again
 
any thoughts? 

bcavnaugh
I am staying or running Version 0.3.9 and works for my needs, 0.3.10 dropped the LED Menu and never tested with 0.3.11.(I guess I should)