Mr. Fox

I will do that later this evening. I am not at my computer right now. Just max the watts slider with PX1 and leave everything else on defaults?

I just totally spaced it off until now about the dip switches. I don't remember if I was on X570 Crosshair or Z590 Dark when I took the block apart for cleaning, but in either case that is when I changed them. At the time I thought, I should test this and see what changes. I got busy with other things and didn't do any benching for a while. Then when I came back to it all my scores were lower and the GPU core clocks were dropping like they never had before. I just pulled the GPU so I could see the dip switches and put them all back to the "off" position. So, two of the suggestions were handled in that one operation. GPU is running x16 4.0. Are your defaults in Classified and PX1 with the 520W vBIOS the same as this? Boost Lock On: Boost Lock Off (and Classified Tool reset after that change, since Boost Lock changes that in Classified):

I may try that, but I have 2 versions of W10, W11 and W7 and the behavior is the same on all of them. It is not only Port Royal, but all benchmarks right now. It is only coincidental that I am focusing on Port Royal, which is kind of ironic because it is the one I care the least about. All of the OSes are clean installs (in an effort to fix this, in fact). I just remembered another change I made when I cleaned the block. I had totally forgotten about it. Actually two changes. I can try undoing both. One is the full back plate thermal pad. The other (which I will try first) is I set all of the dip switches to the optional position. That may be conflicting with using Classified and causing something unexpected. Are your dip switches set to factory defaults? I totally forgot about changing the dip switches. That could be it right there.

If that is the case, maybe an "error" in assembly the first time I installed the Hydro Copper produced a favorable malfunction this was unfortunately corrected when I reassembled it after cleaning. Maybe I will get lucky and make the same "mistake" again, like over tightening a specific screw or shorting something out that causes it to malfunction in a highly desirable manner that neither EVGA nor NVIDIA intended. I hope so anyway. Sometimes malfunction is a good thing, LOL. Depends on whose definition applies. I certainly don't like it how it is now. I haven't been very successful at GPU benchmarks since I cleaned it. Maybe just a remnant of my streak of bad luck. At least it still works. So I can be thankful I didn't have an accident that killed it like I did the 11900K or the golden 10900K I bought from Talon.

I will turn it off when I am chasing numbers after I figure out how to get my GPU to perform as well or better than it used to and not drop clocks under load. It may be something at a hardware level because this behavior started when I disassembled and cleaned the Hydro Cooper. I didn't have the issue of not holding clocks under load before and it acts like it might be a thermal issue. It behaves like it would as the GPU gets hotter, not running on cold water, but none of the sensors suggest it is. This began before the change to Z690, so at least I don't have to wonder if it is something other than the GPU.

Rivatuner Statistics Server OSD so I can see what the core clocks, power and voltage are doing during a benchmark run.

About 1,000 points less now. Starting at 2265 on core, it runs about 1975 max and bounces around like a pinball with more than 520W vBIOS limit showing in RTSS OSD. Let me try lowering the voltage and see if it gets better or worse. Edit 1: Lowered voltage and that put me back were I was with the XOC vBIOS. About 15.5K in Port Royal. If I want to see 2100 on core, I have to set the offset for 2265 because the actual is about 150MHz less than what is requested or set. It seems like it NEVER does what you tell it to. You always get less so need to demand more than you expect. (Gee, that sounds like almost every area of life now, LOL. If you want something barely good enough you have to demand more and have ludicrous expectations.) Edit 2: So it looks like the new way is to figure out have much false information you have to use with PX1 just to get the GPU to pull a half-assed run without going too far beyond what works and what wont. Nice. (not really) I guess it's time to start over on learning what I can get away with. I just wish I knew what changed with the XOC vBIOS no longer holding boost clocks under load. I liked that a WHOLE LOT better than this gamer-boy vBIOS crap.

I am not sure that even shows as an option. That, or I just stopped looking at the Re-Bar tab because I didn't care. I ignore almost everything that is made for gaming unless I think it offers something that might bump my benchmark scores. I don't game enough to really care anymore. If there is any thought that it might hurt my benchmark scores (crap like G-Stink) then it's not only no, but hell no, LOL.

I just remembered that and did it. Thanks. That's pretty handy.

I don't know. Never tried it. I've basically ignored anything other than the XOC firmware since the day Vince sent it because my benchmarks are all pulling way beyond 520W. I have tried tons of different drives and it doesn't seem to be driver related. Is there a 520W with rebar support? I will give it a shot and see if it is the same, better or worse.

I just don't get this. More voltage, less voltage, load clock sucks. Max core temp is under 40°C. Pretty much kills benching fun.

I have relatives that are school teachers, and some of them are very intelligent, so there are always exceptions. But, the concept here is similar to the old cliché, "Those who can do, those who cannot teach." Another way of putting it, "When you have no go, focus on show." It is the sleepers you should be worried about. They'll catch you off guard and the outcome can be lethal. RGB is like sword-rattling... using a toy sword.

I think where it has the potential to be most misleading is where overclocking headroom is concerned. I've noticed that to some extent where the CPU binning process is concerned. I've also seen it in the past with GPU ASIC scores. The silicon with the better numbers almost always runs cooler with lower voltage at stock or near stock. But once in a while the "better" silicon doesn't overclock very well or as high no matter how much voltage you give to it. If you mostly play games or if you're running a turdbook with horrible thermal management, overclocking probably isn't something that you're going to lose a lot of sleep over. But, if you're into overclocking more than anything else it's kind of tragic. I'd rather have a sample that overclocks higher and performs better even though it takes more voltage and it's harder to cool. But I wouldn't if I was the kind of person I just described and overclocking wasn't my primary interest.

OK, the BIOS and vBIOS changes didn't break my Linux installation, so that is good.

That did it. I guess the latest version with DWM is the problem. Thank you.

It's this one. I think the latest version.

Darn it. Something seems bugged with it. Profile Inspector crashes at launch, and if select "Continue" the unknown features button is grayed out. Maybe it is because I don't have the Rebar vBIOS installed?

That's nice. Thank you. 🙂 Yeah, that Green Goblin often makes AMD look like something that might be interesting, but I don't think I am that I am anywhere near that desperate yet.

I did not know that Inspector and Profile Inspector were recently updated. Thanks for mentioning it. I just downloaded both and will check it out. It had gone so many years without an update I just figured the guy wasn't supporting it any more. Speaking of support, I wonder if Unwinder is done now or what. Afterburner and RTSS haven't been updated for a long time.

I suppose I could put the XOC Rebar vBIOS on another BIOS position and temporarily switch to UEFI mode. But, I need to figure out why more core clocks won't stay above 2175 under load. I think (hope) it is because I can't get the core cold enough. I ran RTSS OSD to see why my Port Royal and other 3DMark scores suck now and noticed it doing that.

I am not sure what that means. Is there a new version of NVIDIA Inspector that forces ReBar? I can't use the vBIOS with ReBar support because it is incompatible with CSM and I refuse to run pure UEFI mode. Plus, that won't work with W7. If you enable CSM you'll have a black screen with no video output with a ReBar vBIOS.

I think the SP rating is very useful to identify poorly binned CPUs that need to be returned due to poor quality silicon, but I don't think it is 100% accurate past a certain point, and the fact that it changes with temperature and firmware revision makes it even more suspect as being reliable measurement for a whole lot more than spotting on first boot if you have a CPU that needs to be RMA'd immediately.

Yes it does. LEDs can generate quick a bit of added warmth. I have MSI's UWP Control Center feces install on my W11 feces OS so I can turn it off with the trash software. (Since it is garbage, I use W11 for garbage collection for things exactly like that. Then I don't have to worry about my W10 getting digital cancer.) 100%. If there was a way to turn it off in the BIOS or without installing UWP Store trash software, I wouldn't loathe it so vehemently.

Nice score, and that KS seems like a good sample to me. If CPU-Z is not bugged because of the new CPU 1.225V for 56x all P-core is really good. Is that where you have the BIOS set for voltage, or is it 56x on a couple of cores? Don't have to worry about me taking that crown from you. My 3090 KPE can't seem to hold more than about 2175 under load even on chilled water, so I am unable to even hit 16K. I may pull the block off and replace the KPX with liquid metal and see if that helps (keeping the core colder).

I finally pulled off the crappy (and ugly) T-Force heat sinks and replaced them with the RAM jackets and finned heat sink that I had on my GSKILL DDR4. I was getting errors in TM5 due to overheating right near the end of the test run and now no errors and 12°C cooler. I am also glad that the RGB puke rainbow is gone with the LEDs hidden under the heat sinks now. I never have cared much for RGB memory... chintzy gimmick that requires bloatware filth to control. Thanks, but no thanks. I honestly don't know how memory manufacturers think they are doing us a favor by slapping thin aluminum sheets with an adhesive foam "blanket" to snuggle the ICs in their own heat. The stock ones are never much good, but they'd probably be good enough to leave alone if they actually used good thermal pads instead of that adhesive foam rubber crap to trap heat. It also makes them a real pain in the butt to remove from the modules. They make them so difficult to remove, maybe they are scared someone might discover a memory module hiding under the tacky dress.