Massman
Members
-
Joined
-
Last visited
Everything posted by Massman
-
-
-
-
-
-
-
-
Ah. Yea, FLL OC Mode to enable high OC frequency is only supported from ucode 0x12. So not supported in the 0x9 ucode you're using for non-K OC. That's probably why setting it in BIOS doesn't do anything. As far as I know, CPU-Z has server-side checks for FLL and microcode to ensure the proper configuration is used for validations (to weed out any of those false high frequencies). My guess is that your validation got blocked because it lacks the proper ucode/FLL OC configuration (not because someone manually intervened).
-
-
-
-
Thanks Shamino for the invitation. Sapphire Rapids is a lot of fun!
-
In case you're interested, I dug through the archives and found the helium invoice from the when we hosted the liquid helium event in Taipei during Computex 2017. I don't know what the rate is today, but back then we paid TW$150K ~ US$5K for 200L. I think this session we only had 100L. Maybe the original plan was to purchase 2x 4090 for 3D benching but that didn't fit the budget ?
-
-
Awesome result, nice to see a Core i5 topping the leaderboards! Also great photo of a group with nothing but talented overclockers and zeropluszero!
-
Thanks to Shamino for his patience towards me :)
-
-
-
-
-
You can use the following settings in the Extreme Tweaker Menu: AVX Related Controls AVX2 Ratio Offset to per-core Ratio Limit -> User Specify AVX2 Ratio Offset Value = 3 AVX512 Ratio Offset to per-core Ratio Limit -> User Specify AVX512 Ratio Offset Value = 3 CPU Core Ratio -> By Core Usage 1-Core Ratio limit = 54 2-Core Ratio limit = 54 3-Core Ratio limit = 54 (up to 3 active cores it will run 5.4G) 4-Core Ratio limit = 53 5-Core Ratio limit = 53 6-Core Ratio limit = 53 7-Core Ratio limit = 53 (up to 7 active cores it will run 5.3G) 8-Core Ratio limit = 51 (if 8 active cores then runs 5.1G) Specific Core -> set the cores that are good enough for 5.4G to 54X and all others to 53X or lower depending on their capability Note that for AVX offsets on Rocket Lake it's a bit different than previous platform. When AVX is detected, it will drop the ratio on per core basis and not all core. For example, if 3 cores are active the ratio will be 54X for those cores. When AVX is detected, it will drop it to 51X. On previous platforms AVX offset was always based on the all core ratio (so 51X-3X=48X)
Before hwbot was hwbot, it was called "mbot". This was Frederik's school project. Forum users could report their overclocking result in a forum thread and the "mbot" would update the opening post with the rankings. It would also show the results from other forums. The first Mbot submission should be in April 2004. Frederik used his "home" forum to set up the Mbot test thread http://www.madshrimps.be/vbulletin/f14/mbot-test-thread-4716/. Some forums still have the original thread up as well. For example the Portuguese forum Zwame still has the original forum thread with submissions from May 2004 https://forum.zwame.pt/threads/hwbot-3dmark01-ranking.36163/. Frederik registered the hwbot.org domain name in June 2005 http://www.madshrimps.be/vbulletin/f10/mbot-hwbot-launches-hwbot-org-15601/. Key features of the first site were: browse results, watch how other teams are doing, and edit bot settings. Later on you could also create an HWBOT account and link your forum accounts to your hwbot account. Then you'd automatically have access to all the scores you posted in the different forums and update information. One year in, the site had 2500 users and about 10000 results http://www.madshrimps.be/vbulletin/f10/mbot-hwbot-launches-hwbot-org-15601/#post127977 I don't remember exactly what happened in March 2006, but if I recall correctly HWBOT moved to a different database model and the original submission dates were not imported in the new database. All the scores submitted prior to this day would have the same date in the database. That's why you'll find a lot of old submissions around March. Submission IDs don't necessarily reflect their date of submission. TLDR: around April 27, 2004
