I clearly should have started a topic for my hardware upgrade, but it's a little late for that now...
I had been noting that a couple of games I play on a daily basis (ESO, F76) were a little crashier following the upgrade, while Civ 7 had a lot of CTDs. I didn't really dig into it until yesterday, when a problem cropped up that prevented me from running the ESO launcher. Troubleshooting the error (the launcher was failing with a cryptic "Unable to load skin" error dialogue) led me to a work-around that involved disabling a BIOS feature, at which point I found myself wondering if the BIOS was up to date. It was not. It was running version F10, whereas the latest version was F12. The worst part was that version F11 incorporated the final round of Intel's Raptor Lake microcode fixes. Oops. Luckily flashing the BIOS with the Q-Flash tool that is built in to the motherboard was super easy, barely an inconvenience. That seems to have fixed the ESO launcher issue and so far I haven't had any additional CTDs in Civ 7.
I also updated the Gigabyte Control Center utility and installed/updated the handful of drivers/utilities (except for Norton Security -- screw that shit) it manages. The moral of the story is that just because you expect the shop doing a build for you will ensure that the BIOS and drivers are all fully updated, don't assume that is actually the case and check for yourself.
GCC doesn't really provide much in the way of hardware monitoring, aside from setting alarm thresholds for things like temperature sensors and fan speeds, so I also installed the NZXT CAM utility. It's a pretty basic and easy to use hardware monitoring tool, but it has one cool trick that I really like: it has a "mini mode" that provides a transparent overlay in the top corner of the screen, which allows me to monitor things like CPU/GPU temp/load in real time while playing a game. I don't see it as something I need to be running all the time, but it's useful while I'm in burn-in troubleshooting mode.
I wanted to install Intel's Extreme Tuning Utility (I used to use it for hardware monitoring on my previous build), but it won't run because it's incompatible with Windows Virtualization-based security, which is a thing I apparently have now. I believe VBS is enabled as part of secure boot, and I'm not inclined to figure out whether it's safe to disable it just to run a utility that is overkill for what I want.