Mr. Fox

Have you seen this way of managing update filth? Looks like it gives a lot of control over what occurs, and I am old enough that I still like using a command line interface. I tested it today on my crash dummy OS that allows update filth and it is preferred over the Winduws Update GUI. It will give you a list of available updates and let you choose which ones you wish to install. https://pureinfotech.com/install-windows-10-update-powershell/

Keep us posted on how that goes and we'll keep you in our prayers for the best outcome. It's very exciting to hear that "career upgrade" is on your horizon. Congratulations to you and your wife. What a huge blessing to have your second on the way, and also that your wife will be able to bless your kids with a strong foundation as a stay-at-home mom. That job is a harder and more taxing position than any job I've ever had, and also more important than any position I have held, but the benefits last for a lifetime.

It didn't take me very long after I went back to desktops until I didn't really want to have anything to do with laptops anymore. And, that was before the only option available was a BGA turdbook. At that time you could still buy something at least partially respectable. I literally had to ask myself why I put up with mobile trash for as long as I did. And, now I no longer do and I find them all repulsive. You're showing symptoms now. It is a glorious disease, and you will not want to be cured.

Here is this for anyone that needs it. @echo off net stop AsusUpdateCheck net stop asComSvc net stop asus net stop asusm net stop AsusROGLSLService SLEEP 10 sc delete AsusUpdateCheck sc delete asComSvc sc delete asus sc delete asusm sc delete AsusROGLSLService ASUS Crap Remover.bat

If they could get the features and drivers to work right consistently and manufacture GPUs with long life spans they might actually have a winner one day. They seem to do a good job of producing half baked solutions that get them close to the finish line but not across it. After having nothing but a stack of bad experiences with their products for more than a decade I'm not sure what it's going to take for me to ever think they deserve another chance to empty my wallet. That sure as hell didn't work out for me when I tried to bury the hatchet earlier this year. That sucked more than words can say.

They don't care about gamers or miners. They care about money. They're going to pretend to love whatever market gives them the most of it. The moment their darling stops putting out like a slot machine they become the next red-headed stepchild.

Chances are high that the hardware is OK and the problems revolve around a firmware dumpster fire covered in feces. The best hardware in the world is as worthless as the tits on a boar if the firmware is junk. You are not going to win any races in a Top Fuel dragster with a malfunctioning transmission no matter how much horsepower it has.

I said to ignore part 1. Maybe you should go watch part 1. Luumi does not demonstrate it as GamersNexus did, but he talks about that process sometimes damaging the modules. It might be more fun to do it that way though. The way I have always done it works and causes no damage to the memory but it ruins the original adhesives and pads in the process. If you need to sell or RMA the memory and any point that part is less than ideal because it makes putting them back together more difficult and costs something more than zero.

Setting the water block on top with no thermal pad (direct metal-to-metal contact) dropped the temps yet another 3°~4°C instantly.

Wow, that worked flawlessly. I put my memory sticks in laquer thinner standing on the connector edge in a shallow plastic container so that the specification label (the one that has "warranty void if removed" on it, LOL) was not submerged or damaged by the solvent. I made the thinner deep enough to reach all of the the adhesives though not deep enough to reach that label. Within about 5 minutes I was able to easily separate the heat sink from the modules. I did it gently so that the original adhesive remained on the heat sinks and slowly peeled away from the PCB. After letting them dry, I put waxed paper on the adhesives and pads so that if I ever need to RMA the modules I can reinstall the stock heat sinks and there will be no visible evidence of removal or modification. All of the factory adhesives and thermal pads are exactly where they belong on the heat sinks. Now I have the water cooling jackets back on them again and they are much, much cooler, even without the water block. Temps dropped from ~51°C to ~42°C in the TM5 1usmus_v3 test. This is enough improvement to mean the difference between zero errors and failing the stress test and instability due to high memory temps running identical memory overclock settings.

Easy heat sink removal... ignore part 1 video. Such a funny maniacal laugh. I have been doing it the hard way. This should also require less cleanup effort.

I love watching this young lady pound away on those drums. She is really good at it.

Here's a new one from Brother Tom... @ryan Nice to see something new from Disturbed, too.

Looks like the internet gremilns found your router. 😉

Yup, I actually already did that. The only reason I waste any drive space on any version of Windows now is because I enjoy benching and using whatever OS works best. Apart from that hobby, Linux meets nearly all of my OS needs as well as Windows does, and better in some ways. For work, the only reason I need to use Windows is because I have to use PowerBI, and the alternatives to Micro$lop Office universally suck, especially Outlook. It has no acceptable substitute. Otherwise, LibreOffice Write and Calc are essentially adequate as replacements for Word and Excel. If I could bridge that gap, I would probably even seriously consider walking away from the benching hobby and find another form of entertainment.

I'm going to have to take the position that if 4090 and beyond won't have working Windows 7 drivers I will not be looking at a GPU upgrade for a long time. At least not for my benching rig. I might get a 3090 to upgrade from my 2080 Ti someday. Maybe when I can get a nice used 3090 for $500-750. The notion of giving up Windows 7 permanently doesn't register anywhere on my radar at this time.

Just to be clear, he is using a new version of TB that is not 100% working with DDR5 and the versions we have access to does not. I hope he has a version of TB for DDR5 that we will be able to get soon so we don't have to worry about this. Save a copy of the memory firmware and we're good for recovery if this is a common DDR5 issue once we have a DDR5-compatible version of TB. I hope yours is not messed up, too. Given that one stick of the Corsair stopped booting, I am tempted to reset BIOS defaults and drop back down to A30 or A40. MSI can pretend the problem is somehow a failure on TeamGroup's product, but there is no way it was a coincidence. It might have been a one-off glitch that is rare, but the memory didn't decide to corrupt itself at exactly the moment I flashed A60, LOL.

I already did that, but I did not copy/paste my reply to MSI when I posted their response. I gave them a copy of the invoice for replacement memory and offered to send them the corrupted modules and their response was to RMA the memory, LOL. They have not responded (yet) to the information I shared with them for Vitaliy's email. I will not be surprised if they do not respond.

OK. As expected, MSI passed the buck and shirks their responsibility. Typical loser OEM, just like ASUS. "Generally speaking, BIOS update does not cause damage to memory SPD..." But, let's have TeamGroup pay for it... nice solution for MSI. EVGA FTW! Our friend at Thaiphoon Burner replied. He is such a great guy... and, very smart. ------------------------------------ From: Vitaliy Jungle Sent: Tuesday, July 19, 2022 2:57 AM To: Mr. Fox Subject: Re: "Thaiphoon Burner PRO Corporative Edition" Hello Mr. Fox, Thank you for the reports sent! I have examined the SPD dumps from your Team Group memory modules. They are both corrupted indeed. However the first module with the corrupted Part Number "ŠEAMGROUP-UD5-620›" has only 1 error in the first 512 bytes. This means DRAM and module organization, timings, voltages and other electrical parameters are not corrupted. The Part Number also needs to be fixed. As to the second SPD dump, it has more random errors in the first 512 SPD bytes. Both of the SPD dumps have a corrupted XMP header. This is why BIOS doesn't find XMP profiles. Here is how the XMP header looks like in the SPD of your Corsair modules: It is not corrupted like the other part of XMP bytes. And here is the XMP header of your Team Group modules: The header is corrupted. As you can see many of the XMP bytes are set to "20". This is a "blank" code and it is related to a string code. And it is not an error. So, if the Thaiphoon Burner was ready, you could restore your SPD easily. But at this moment I am unable to help you. Anyway, thank you for sending me reports! I felt much better when I saw that my program is already capable of decoding some parts of DDR5 SPD without issues. With best regards, Vitaliy. @johnksss@Rage Set

Yes, I did it as Brother @jaybee83 suggested. Packed it in from the large open end.

I am sorry to hear that. I am not sure what to suggest at this point.

Got an new ssd to put in more OS's. From what I have read. After 5= quintuple boot then we will have 6 = sextuple, 7 = septuple, 8 = octuple 🙂 You probably already know this but for the benefit of anyone else reading that may not, it is always best to install the OS with only the drive you wish to install it on. All others should be physically removed or disabled in the bios. That way each operating system will have its own unique BCD/MBR. Then you can add and remove anytime you want to without having to worry about whether or not it will affect one of the other installed operating systems. If you install multiple Windows version with a previous there will be only one bootloader on one drive, and the function of all OSes will be dependent upon the presence of the drive where the first OS was installed because the bootloader for all of them is on that drive. @Tenoroon if this is not the one I shared with you before, try it first. XTU 4.2.0.8 AW18 This is probably the one I gave you before, but I do not recall for certain.

It was set to anyone with the link can access but maybe that didn't work. I approved your request anyway.

Recheck my post. I added a link to an archive with several older versions. It is difficult to find older versions of XTU to download.

It's a long shot, but have you tried XTU? It is hit or miss whether it allows you to adjust it. Here is a link to download older versions that I have archive. Try one with a date close to when your CPU was released.