Mr. Fox

Even if we lived in a perfect world that had no cheaters, the rules must be applied consistently to all submissions to maintain the integrity of the leaderboards. Submissions without proper validation should never be allowed for anyone.

None of that actually matters. Just create your ISO with Rufus and configure Windows setup to bypass all of the idiotic system requirements like TPM and Secure Boot. You can install Windows 11 on any hardware if you really want to. Set up with local account. https://github.com/christitustech/bypassnro

If you are still having this issue and the 990 Pro is detected in other M.2 slots maybe try a different NVMe in the slot. It may be something with the 990 Pro, but you can determine if that is the case with a different NVMe. I would suggest a Gen3 or Gen4 to see if it is detected or not. If not detected then the issue is the M.2 slot.

That is odd. It is probably something with USB ports. I would try disconnecting everything and connect only the keyboard one USB port at a time, starting with the BIOS flashback port on the rear I/O. Do not connect anything else and see if it boots normally. If not move it to a different USB port not associated with that USB controller. I had random issues with the Z790 Apex USB ports not working and getting stuck on B4 randomly and unplugging the keyboard and mouse and connecting them to different ports usually solved the problem. That was quite some time ago. It did not seem connect to the BIOS version, but it may have been.

That's pretty cool. Thanks for sharing the working link. Have a nice weekend.

That example link does not seem to work. Access Denied - Error 403

I don't have the motherboard anymore, but I had not deleted all of the files for it. Z790 APEX v0071

Sorry I did not see you had tagged me. Not sure if you ever solved this or not. If your BIOS version was never changed coincidental to the malfunction and you allow automatic updates I would be looking at a Windows 11 cancer update being the most likely culprit for the broken memory tools. If you are using Defender and have everything enabled in Security Center, it could also be something in Windows 11 "security" that is borking the function of proven safe-to-use software.

Probably because it is modded firmware. The only way to flash firmware mods and bypass that silly safeguard is to use the BIOS Flashback feature. Have you already tried that?

You are correct. What is in red is required. What is in green is optional. The Port Royal rules example screenshot does not have the red and green boxes and it includes an extra CPU-Z and an extra GPU-Z that are not necessary, so you have to rely on what is written in the table above. I know many people post a second instance of GPU-Z showing the sensors for max core and memory clocks. The rules can vary a little bit between benchmarks so it is always good to check before posting. The Port Royal rules validation requires a valid URL to correspond with the screenshot. CPU-Z CPU tab, CPU-Z memory tab, GPU-Z tab for GPU. All benchmarks as far as I know now require a full desktop screenshot including the Windows taskbar. No clipped, snipped or cropped desktop shots.

For me it is because I used an OS on my AMD platform that was previously running on Intel hardware and the OpenCL was installed on Intel hardware.

I noticed none of my old submissions appear looking at my submissions histroy. I cannot tell you have much I HATE the new UI. Everything so SO bloated, huge and ugly. Feels like I am using a damned tablet or smartphone. Really sucks how it looks now. Amen to that, brother!

I have one 14900KF (out of many 13th and 14th Gen) with the SA bug and anything 1.200V or higher VCCSA would cause lockups, which obviously hinders RAM overclocking. That CPU maxed out at 8200 CL38 with 1.190V on VCCSA. BIOS 1503 with 0x129 MC fixed that for me. I tested up to 1.400V on VCCSA and no more freezes. The SA bug was a problem on ASUS and MSI boards I tested it on. I tested the ASUS XOC BIOS that @safedisk posted (v9933) and the SA bug returned to that CPU even with 0x129 MC. I am going back to BIOS v1503 and hope the SA bug goes away again. It was nice having a CPU that worked right. I'm going to be sad if the fix was undone by 9933. It is a better than average CPU sample except for that flaw. Has a really nice VF curve and low voltage requirements for the P/E cores and cache and strong IMC.

What laptop CPUs will work with desktop LGA-1700? Aren't all of them BGA?

I'd really like to see something in Systeminfo that identifies GPU benchmark runs as "Stock" and "Overclocked" based on NVIDIA and AMD reference boost clock, with a corresponding filter available for search results. The actual boost clock will vary with temperatures, as will the boost clock of "OC" versions of non-reference designs, but the base boost clock will remain constant regardless of the actual boost clock on reference cards. The moment you overclock the GPU even a little bit, the base clock value will change. You can see this in GPU-Z. Once that is in place you can create a filter based on stock versus overclock and exclude anything from HOF ranking that isn't an overclocked submission. Conversely there would be times that it would be very useful knowledge to know what stock performance should look like based on averages. You could also more easily quantify how things like CPU clock, memory clock and BCLK, and OS tweaks, affect benchmark scores with stock GPU runs. It would also be nice to see a filter added to search results based on GPU brands and models as identified by the firmware. This data is already captured, so why not include those as options in the filtering menus for selection? Because so many of the 3DMark submissions are overclocked systems, which all of us here absolutely love doing, the UL database has little or no value in terms of identifying, with any level of accuracy, what appropriate stock performance should look like and thus it becomes more difficult to evaluate (from that data UL is compiling). (Note: I am speaking of UL/3DMark search results in my comments above and not HWBOT.)