Mr. Fox

The next time you take it apart go ahead and bake the top. Once the copper is saturated you can polish it to a mirrorlike finish and it will work better even with ordinary thermal paste versus the bare copper. It seems to improve the thermal conductivity with the added density of having the pores saturated with liquid metal.

I have had mixed results with the Rockit IHS. Sometimes better, but often worse than stock IHS. You really do not need to glue the IHS. It is not necessary whether using the stock ILM or aftermarket frame. Using the stock ILM you just need to press down on it with your thumb to keep it from sliding when latching the ILM. If you want to tack it in place, a tiny dot of T7000 under each "wing" on the IHS will suffice. More than strong enough. It is used to attach things like the back panel on a cell phone not intended for user access. But, it is not permanent. Always important to sand down the bottom of the IHS so that is moves freely sitting on the die when not glued in place. If the perimeter touches the CPU or remnants of original IHS adhesive the die contact will be impaired. If you bake the Rockit copper IHS in an oven with liquid metal applied it will accelerate the absorbing process and saturate the copper so it no longer has the ability to absorb it. It takes a couple of baking intervals, cleaning off the slag, applying fresh liquid metal and baking again.

Spot on. If a person is going to use an IHS, the best option is to have one made of pure solid silver, or at least a quality nickel plating.

That is wonderful news, and it only makes sense. I mean, anything put out by crApple is just a dumbed down de-evolved proprietary and defective version of Linux for Dummies and an unacceptable alternative to Windows, and anything put out by Micro$lop is just a screwed up mess loaded with bloat and data collection filth. And, like crApple's trash, a product dumbed down for dumb-dumbs.

They are mentally and morally incapable of doing the right thing and lack the capacity to make good decisions.

They are mentally and morally incapable of doing the right thing and lack the capacity to make good decisions.

Yeah, you are right. While they are a corrupt bunch of evil clowns, they're incompetent and probably would struggle to execute on that. They can't even effectively manage their own messes, much less orchestrate a sinister plot of that degree of complexity.

That is either a lousy CPU sample or it is not tuned properly. At 59x all P and 48x all E and 52x cache my 13900KS and both 14900KF are like 1.285-1.290 Vcore. He may be running really sloppy LLC allowing the light load voltage to skyrocket. It's definitely not what one would want. My load voltagee does go to 1.430V on VCore unless I am pushing to like 61x all P core. Because I use override voltage and Level 7 LLC there is not a huge difference between my idle and load voltage.

That's just too funny.

EVGA Dark and ASUS Maximus and Rampage boards have had the PCIe power connector for many years. I think the intent is to help keep power delivery stable and consistent, minimizing variance and fluctuation, but not increase the power delivery. Especially beneficial if multiple slots are occupied with a power-hungry component. Probably not any huge benefit if only one slot is used for the GPU and the rest are empty. But we also now have many NVMe and WiFi cards leeching power from PCIe with none of the slots except for the GPU filled, so it makes even more sense now.

It all falls under the "Defender" umbrella, but you are referring only to the malware part. Security Center is a GUI for Defender. My systems don't even have that. The scripts provided will wipe it out entirely. You need to be able to access it once to disable core isolation, tamper protection and all of the other trash first, then the scripts will totally remove everything except for firewall. There will be no services and no security center. I do that on all of my systems, and have been for several years now. Totally nukes it. Doesn't disable things, but physically removes them so they no longer exist and can't be re-enabled. It's awesome. I watched about 4 or 5 minutes of that and now I know for certain I won't be buying that game. Based on my personal preferences it looks extremely boring to me.

Here you go, brother. https://community.hwbot.org/topic/220910-asus-rog-maximus-apex-z790-apex-15/page/7/#comment-673420 Edit: Didn't see that Brother @Papusan already posted it. Was on the next page. Oh well. 🙂

Just nuke Defender completely and get that horrible cancer off your system. It is a resource hog that is inappropriately restrictive and interferes with use of your system. Destroy Defender (from my OneDrive account) If you feel compelled to have a placebo to keep you safe, ESET AV, Kasperski and Panda Free are all good options. Malwarebytes is also decent and I like the added advantage that you can close it manually and end all background services for benching. I am going to let other people spent their money and see what it produces. If it is compelling enough to even consider it, then I will look for better than average samples on overclock.net that are better than average samples after the person blowing money on binning has chosen the best one to keep for themselves. I'm not going to spend money on lottery tickets that are not guaranteed winners. I may never buy another new CPU again. I hate getting screwed with below average trash and having to fart around with RMAs. Almost every Intel and AMD CPU that I have purchased new retail has been disappointing silicon quality.

I am most assuredly not going to play ball in the way the Redmond Retards are changing the game with Winduhz changes. I am glad I began my journey of warming up to Linux. My tolerance for the nonsense of their insane clown posse is wearing very thin. They are hanging by a thread now with their Nazi control freak shenanigans. As I ponder the idea of sunsetting my benching hobby, any incentive to purchase new products is more or less eliminated. Financially, that is a huge win for me and a five finger death punch to the industry if many people have similar personal revelations.

I can see myself, and some other fine people of equal intelligence, (like a lot of us here,) potentially going through a long dry spell and not finding any good reason to purchase new computer tech. Maybe even never finding a good reason in the foreseeable future if the trend continues on its current undesirable downward trajectory. That would actually be a blessing in disguise in some respects. No point in wasting money on downgrades when the result is only newer is better newer.

If it performs the same or better as 13900KS/14900K/KF/KS and ditches the crappy smartphone cores I would be open for the change, but I am skeptical about silicon quality. If it is a voltage pig with insane thermals that limit overclocking, and leave no headroom for overclocking, then probably not. I do love the idea of adding performance cores and eliminating Atom cores as long as benchmark scores are equal to or greater than what I have now. A big monolithic processor with matching cores under a single die, in my opinion, is the only right way to do things. I do not like the elimination of hyperthreading and I would want to see the elimination of Atom cores result in reinstatement of AVX. The E-core crap is why AVX was removed. As usual, we need to wait and see. I'm not crazy about speculation and predictions. I prefer to see tangible evidence. Jose is going to feel slighted that you only mentioned Manuel. 😜 No shifting. Just wide open throttle.

That is sad. But, your involvement for PremaMod Partners remains priceless. I have not noticed anything because I only went from MC 11F to 129 only to fix the SA bug on one CPU. If not for the SA bug fix I would still be using old firmware. The only reason I considered updating to 129 is because it was being reported at overclock.net that MC 129 BIOS fixed the SA bug. One of my five LGA1700 CPUs is a fantastic sample with the SA bug. The others are very good and have no SA bug. Same is/was true for @electrosoft. He has a super chip with the SA bug that 129 fixed. Even so, I probably would not notice the eTVB bug because I manually overclock everything and have eTVB options disabled in the BIOS because I hate that kind of approach to overclocking. I find the "old school" way of doing things to always be the best approach.

Happy Thursday, Brother @Prema. It has been nice seeing you here. I noticed the same. I had manually set it in the BIOS for less than default (Auto) and had to set it back to Auto to make the 8400 memory clock stable. You know me. I'm not going to let the Redmond Reprobates make decisions for me. I, and I alone, will decide what runs on my PC. Much better that way. EULA be damned. Posted this in another thread yesterday... A "secure" system (actually a myth) that doesn't do what you want it to do is worthless. Function and performance always trump security as far as I am concerned. All the patches and security fixes in the world won't fix the DIMM-wit using the keyboard. (Yeah, you saw what I did there, LOL.) The biggest security risk with any computer is a stupid user. Simple fix... for unwanted updates, not for stupid users or stupid employees working on the Windoze Support Team (can't fix stupid)... just tweak the registry and hit "Advanced options" on the Windoze Updates page in settings and delay them for 10 years. Hint: You'll need to scroll a LOOOONG way down to reach the 10 year mark. Windows Registry Editor Version 5.00 [HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\WindowsUpdate\UX\Settings] "ActiveHoursEnd"=dword:00000011 "ActiveHoursStart"=dword:00000008 "AllowAutoWindowsUpdateDownloadOverMeteredNetwork"=dword:00000000 "ExcludeWUDriversInQualityUpdate"=dword:00000001 "FlightCommitted"=dword:00000000 "IsExpedited"=dword:00000000 "LastToastAction"=dword:00000000 "UxOption"=dword:00000004 "InsiderProgramEnabled"=dword:00000000 "SvDismissedState"=dword:00000001 "SmartActiveHoursSuggestionState"=dword:00000001 "SmartActiveHoursTimestamp"=hex(b):b9,80,63,7c,b6,73,da,01 "HideMCTLink"=dword:00000001 "RestartNotificationsAllowed2"=dword:00000000 "SmartActiveHoursStart"=dword:00000007 "SmartActiveHoursEnd"=dword:00000010 "FlightSettingsMaxPauseDays"=dword:00000e42 [HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\WindowsUpdate\UX\Settings\ModelState] "SignalRegistered"="::2F1AAFCACF" No need to worry about stupid crap like this (below) ruining your day when you're calling all of the shots and keeping the numbskulls at Micro$lop out of your business.

Nobody here disagreed with you that I know of. You are correct. I don't think it will ever work well. It will always have flaws because the entire concept is flawed and was invented by goofballs. AMD started the abomination with their cobbled together mini CPUs and Infinity Fabric crap. People bought it and were excited about the mess, so Intel jumped on the bandwagon with their smartphone core crap. Now we all have to deal with messy doo-doo on both sides of the fence. The moral to the story is this: If it is what the sheeple want and believe in, there is at least a 50% chance that it is trash. It doesn't matter which school they attend, newer is always better newer. Computer technology is circling the drain, regressing rather than progressing. And, the demons that want to drag us into their pit don't care whether we are wearing red or blue pants. Seems to mirror other facets of life beyond technology to a great degree. The world we live in is pretty screwed up. Are the SP ratings deceptively good and not matching nasty details the VF curve, or is all of the information, including what it shows on the VF curve and SP ratings, not the reality of how it behaves? That is pretty sad, but it may have been that way new. The 14900K/KF CPUs I returned to Amazon, NewEgg and the 14900KS returned to Central Computer were the absolute worst silicon samples I have ever had in my possession before. Bad enough there was no way I would try to use them or sell them to someone else at a loss, so I insisted on refunds and got my money back. The KS needed like 1.550V to run Cinebench on BIOS defaults and stock turbo with no ASUS enhancements. I think I remember seeing posts by the guy selling it that he was struggling to get it to behave acceptable. I might have him mistaken for someone else and can't swear to it, but that's why I did not reply to your post if it was the same CPU that you were commenting about how good the predictions looked. This is why I have stocked up on 13th and 14th Gen CPUs of good bin quality. AMD brought nothing worth buying and I expect Intel will have nothing worth buying in their next gen. All the focus is on wrong things. Quality, integrity and customer experience are no longer main points of focus. The focus is developing AI to further the tech syndicate's theft of information and crimes against humanity, a resource for governments to rule by manipulation and fiat, with funding sourced by selling grossly overpriced broken crap to silly people that are addicted to electronics feces and believe everything they see, read and hear on TV and social media.

Nice. Makes me want to do more SMD soldering. No reason in particular, but it's just a cool hot talent. I wondered how she was going to pay for it. Now we know.

A "secure" system (actually a myth) that doesn't do what you want it to do is worthless. Function and performance always trump security as far as I am concerned. All the patches and security fixes in the world won't fix the DIMM-wit using the keyboard. (Yeah, you saw what I did there, LOL.) The biggest security risk with any computer is a stupid user. Simple fix... for unwanted updates, not for stupid users or stupid employees working on the Windoze Support Team (can't fix stupid)... just tweak the registry and hit "Advanced options" on the Windoze Updates page in settings and delay them for 10 years. Hint: You'll need to scroll a LOOOONG way down to reach the 10 year mark. Windows Registry Editor Version 5.00 [HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\WindowsUpdate\UX\Settings] "ActiveHoursEnd"=dword:00000011 "ActiveHoursStart"=dword:00000008 "AllowAutoWindowsUpdateDownloadOverMeteredNetwork"=dword:00000000 "ExcludeWUDriversInQualityUpdate"=dword:00000001 "FlightCommitted"=dword:00000000 "IsExpedited"=dword:00000000 "LastToastAction"=dword:00000000 "UxOption"=dword:00000004 "InsiderProgramEnabled"=dword:00000000 "SvDismissedState"=dword:00000001 "SmartActiveHoursSuggestionState"=dword:00000001 "SmartActiveHoursTimestamp"=hex(b):b9,80,63,7c,b6,73,da,01 "HideMCTLink"=dword:00000001 "RestartNotificationsAllowed2"=dword:00000000 "SmartActiveHoursStart"=dword:00000007 "SmartActiveHoursEnd"=dword:00000010 "FlightSettingsMaxPauseDays"=dword:00000e42 [HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\WindowsUpdate\UX\Settings\ModelState] "SignalRegistered"="::2F1AAFCACF" No need to worry about stupid crap like this (below) ruining your day when you're calling all of the shots and keeping the numbskulls at Micro$lop out of your business.

I do not do use CMO files across BIOS versions. That is why I save a text file for the profiles I use. Then I can recreate them manually for a newer or older BIOS version. That fixed it. Something from 9933 did not revert back to what it was with 1503 using the in-BIOS flash tool. If you run into weirdness after an in-BIOS update, or going back to a better older version, run BIOS flashback from USB using the button on the rear I/O. Now I can use XMP Tweaked again and no lockups and confirmed no SA bug. It flashed everything doing it that way instead of keeping crap in some regions with a newer timestamp. It takes over twice as long to flash that way, but it does a better job. Back to normal... all settings that worked before still work after BIOS flashback. No SA bug with MC 0x129. It did nothing to help my 81°F (27°C) ambient temperatures in my office. 🤣 Water in my loop is 28°C. 😡

They'll deny it, but I would not be surprised if it was a deliberate act of sabotage rather than a mistake. They are losing market share to older versions of Windows and Linux due to their filthy new cancer OS and what better way to block it than preventing users from booting into Linux when they don't want to deal with Micro$haft's garbage. They are not an honorable company and their lack of integrity is evident to anyone paying attention.

Awesome. I hope they get finanically raped by the litigation and left for dead. Then we can hope the same for lots of their evil accomplices in the tech space to suffer similar tragedies. We need to see some fortunes lost, empires ruined and some key decision-making people criminially prosecuted in order for a lot of this nonsense to get smashed for good.