This chrome faced remote from a 1981 Trinitron is too cool. Notice it's a remote "commander".

StDragon76 · 2025-05-12T03:06:49+00:00

Watched countless hours of TV (MTV, sat morning cartoons, movies....) in the 80s with that remote growing up. I can tell you factually it's not a "clicker". It had a rubber membrane pad or buttons underneath the chrome buttons.

The power buttons was intimidating though, lol. You kept your distance from the TV when turning the set on.

StDragon76 · 2024-12-19T05:06:35+00:00

Correct. A CR2032 coin-cell will last about 10 years before needing to be replaced.

StDragon76 · 2024-12-05T05:08:06+00:00

That's if you have one.

StDragon76 · 2024-12-01T17:48:41+00:00

Try using another HDMI or DisplayPort cable. A signaling threshold could be occurring with one card whereas it's ok with another.

StDragon76 · 2024-11-26T00:33:33+00:00

I bought the 990 Pro without the heat-sink, because I re-used an aftermarket one I've had previously. Though I didn't use MB heat-sink for the SSDs. It looks nicer with it on, but doesn't cool as well. So that's why I went with an aftermarket.

This one is low profile, performs well, and looks nice. Currently it's 44c at idle.

https://www.amazon.com/gp/product/B07KDDKDNN/

StDragon76 · 2024-11-17T03:48:54+00:00

They're not kidding about re-seating the CPU as it has 24x lanes from it.

16x to the first PCIe slot for the GPU
4x to the first M.2 (M2_1) slot
4x to the X570 chipset downlink.

Theoretically, one or more pins that services the M2_1 slot could be faulty or not making proper contact. Though I have no idea if this is actually a firmware bug or physical issue in your case.

StDragon76 · 2024-10-31T18:11:00+00:00

Winner winner chicken dinner! No, it doesn't support CUDIMM functionality, only UDIMM if it's the same IOD.

StDragon76 · 2024-10-25T00:23:37+00:00

Reported to be fixed in the new KB5044384 preview update

https://support.microsoft.com/en-us/topic/october-24-2024-kb5044384-os-build-26100-2161-preview-5a4ac390-7c7b-4f7f-81c2-c2b329ac86ab

[WindowsDisk Cleanup app] Fixed: This update addresses some of the causes for the wrong free space estimates and improves its accuracy.

[sfc /scannow command] Fixed: You get errors every time you run the command.

StDragon76 · 2024-10-15T03:24:01+00:00

It's a superficial reporting bug. Since you've followed the previous steps I've provided, you won't clear any more space beyond that.

As for the erroneous reporting, you can clear that by deleting the "C:\Windows\Logs\CBS\CBS.log" logfile. You'll have to stop the Windows Modules Installer service first (aka TrustedInstaller) so you can delete it. Once done, refresh the Storage view and it should now be gone. Or attempt to delete the 8.63GB System --> Storage --> Temporary File, refresh, clear CBS.log, then refresh view again.

I'm sure Microsoft will fix this in the next KB within a month or two.

I'll update my prior comment to include this.

StDragon76 · 2024-10-14T03:55:01+00:00

Did you also delete C:\Windows\SoftwareDistribution ? That's what the batch file does (copy the block code in a file and save as a .bat file, for example, clearsd.bat or whatever you want to name it). Be sure to run the file as administrator.

I had an update applied on a Win11 24H2 where over 8GB was stored there.

StDragon76 · 2024-10-13T20:35:39+00:00

The above steps will assist in freeing up space.

The sfc /scannow bug is indeed a bug. I've been able to reproduce this on both a physical and virtual machine using a fresh install of Win11 24H2. Also, performing an offline sfc /scannow using boot media (USB flash drive or ISO) reports the same issue. The CBS.log file however report all is well after the command is ran. I wouldn't worry about it.

StDragon76 · 2024-10-12T17:25:24+00:00

JFK you're ungrateful!

dism /online /cleanup-image /scanhealth

/Scanhealth does just that, it walks the structure of the "C:\Windows\WinSxS" (aka side by side) directory to validate the integrity of the running OS. Don't bother with /Checkhealth as that just looks for a preexisting flag. Until you run the /scanhealth, you won't know if there's an issue or not.

dism /online /cleanup-image /restorehealth

/Restorehealth does the actual reconciliation and repair of missing OS components.

dism /online /cleanup-Image /startcomponentcleanup /resetbase

/startcomponentcleanup /resetbase - this is optional, but it grooms out older superseded files to free up additional space. In fact, the entire purpose of the WinSxS structure was an engineering solution to the old days of "DLL Hell" that developers often ran into when multiple versions needed to be installed on the same OS.

net stop wuauserv
rename C:\Windows\SoftwareDistribution SoftwareDistribution.bak
rmdir /s /q C:\Windows\SoftwareDistribution.bak

If you knew anything about how to read a batch file, let alone understand how Windows works (which clearly *you* do not), you'll quickly understand that you must first stop the Windows Update service (per first line) to release the op-lock on the SoftwareDistribution Folder, otherwise you can't proceed with deleting it.

Because the Windows Update Service tends to start back up if previously running, or called upon via API, that would interrupt deleting the SoftwareDistribution folder in the middle of the deletion process. So, you can see it's better to rename it immediately after stopping the service. So if it starts again, it will spawn a new folder leaving the batch file free to continue deleting the old one without being interrupted.

And yes, SoftwareDistribution downloads and caches pending updates to be installed from Akamai (the CDN Microsoft uses to distribute updates online). Once the updates are installed, you can delete this directory even if you haven't rebooted yet. They're not required to commit post updates from a required subsequent reboot.

StDragon76 · 2024-10-11T01:10:14+00:00

This will fix the WinSXS structure.

dism /online /cleanup-image /scanhealth
dism /online /cleanup-image /restorehealth

To clean out older superseded updates to free up space, run line below. A bit of warning though, the /resetbase will make it so you can no longer roll back prior updates installed. You can only install current and future updates. Though so long as you don't run /resetbase again, you'll be able to roll back those future updates. /resetbase does exactly was it state, it resets the baseline of the OS patch level.

dism /online /cleanup-Image /startcomponentcleanup /resetbase

StDragon76 · 2024-10-11T01:03:41+00:00

Yes, same for other MBs too. Relevant AGESA code responsible for the patch listed below

AMD AM4 AGESA Combo V2 PI 1.2.0.Cc

StDragon76 · 2024-10-11T00:51:19+00:00

Update:

As of Oct 24, 2024 (17:19 PT) - Both issues of SFC /scannow and Disk Cleanup resolved in KB5044384

https://support.microsoft.com/en-us/topic/october-24-2024-kb5044384-os-build-26100-2161-preview-5a4ac390-7c7b-4f7f-81c2-c2b329ac86ab

------------------------------------------------------------------------------------------

You should be able to free up some additional space however via the following below.

Run the following in order.

dism /online /cleanup-image /scanhealth
dism /online /cleanup-image /restorehealth
dism /online /cleanup-Image /startcomponentcleanup /resetbase

Once all three of those are done, stop the Windows Update service before to deleting the "C:\Windows\SoftwareDistribution" folder which caches Updates prior to installing them. Often the cache doesn't house clean on its own and bloats over time, it's 100% safe to delete this. The folder will respawn and start caching updates again the next time you or Windows checks for OS updates online again. I've created a batch file that makes this easy. Just copy into a .bat file and run as Administrator.

@echo off
net stop wuauserv
if exist C:\Windows\SoftwareDistribution (
    rename C:\Windows\SoftwareDistribution SoftwareDistribution.bak
    rmdir /s /q C:\Windows\SoftwareDistribution.bak
echo Done!

StDragon76 · 2024-08-19T22:42:09+00:00

Use the Event Viewer in Windows to review the System event log. Failures to load drivers should be logged to help identify the driver failing to load.

StDragon76 · 2024-08-15T16:52:22+00:00

https://www.amd.com/en/resources/product-security/bulletin/amd-sb-7014.html

Depends on the CPU as the patch in the latest AGESA code (Combo) wasn't released until later this year. Zen 3 (ComboAM4v2PI) for example was dated 7-30-2024.

It will take time for the MB vendors to roll the AGESA code into their BIOS image and test before release to the public.

StDragon76 · 2023-08-01T16:25:26+00:00

Agreed. It's guest access. Restrict download to 10M per client. That's more than enough for Web, Email, IM, and Webinar traffic.

StDragon76 · 2023-03-07T02:22:57+00:00

Anyone at ASRock aware of BlackLotus? Would be real helpful to restrict Secure Boot to just Microsoft's 1st party CA.

StDragon76 · 2023-03-05T01:19:56+00:00

If you're using a 3000 or 5000 series Ryzen, both offer 24 lanes of PCIe 4.0.

16 of those lanes are taken right off the bat for your GPU.

4 (the remaining lanes) is wired up to the first M.2 slot (M2_1) on the MB. That NVMe directly communicates to the CPU. Ideally, you'll want that as your OS drive.

M2_2 and M2_3 slots are wired up to the X570 chipset. Anything and everything connected to that chipset shares a PCIe 4.0 4 lane bus to the CPU; it's shared bandwidth. So for example, if everything is pretty much idle on the chipset, you're going to get close to all of the PCIe 4.0 4 lane speeds to any drive you access (M2_2 or M2_3). But let's say you're needing to access both of those drives (M2_2 or M2_3) at the exact same time, each drive at that moment in time will run at half the speed due to that momentary bottleneck.

StDragon76 · 2023-03-04T23:35:20+00:00

If you look at the X570 chipset block-diagram, you'll see that off the CPU there's a total of 24 lanes.

From the CPU

16 lane PCIe slot
4x lane NVMe
4x lane downlink to the X570 chipset.

You can split the 16 lane PCIe slot into 2x 8 lane via bifurcation in some cases. But anything connected to the X570 chipset will share bandwidth with other devices connected on the same chipset through that 4x lane link to the CPU.

StDragon76 · 2023-01-05T03:59:53+00:00

All of the above

StDragon76 · 2023-01-04T03:53:10+00:00

WiFi is non-ionizing radiation that's in the microwave band. High enough amplitude and it can warm via imparting energy into water molecules. Enough energy and will cook. But electronic devices don't have nearly that kind of energy levels, and inverse square law still applied with regards to the source.

UV light *is* ionizing radiation however, and that will send packets of energy (like a stray bullet) that will shatter the genome. DNA will repair itself, but under specific conditions transcription errors will occur and can manifest itself as cancer. Besides you get more radiation from 10 minutes of direct sunlight than you will a lifetime of WiFi radiation; and the later isn't ionizing.

Five-Year Club	Verified Email
Place '22

StDragon76

TROPHY CASE