darry wrote on 2026-08-01, 16:33:
Good luck on the undervolting and dealing with badly designed resets. I have some power bars with a side-mounted main power button that is not recessed or otherwise protected against accidental triggering, so I know the feeling (I did not think to check for something that bone-headed before buying). Anyway, for things like settings in BIOS or TV service menus, I take photos with my phone and try to remember to tag them for easy access.
Yeah, I should have logged that somewhere. I don't even remember what voltage I was changing, but I remember that Ryzen Master needed to restart every time I changed it from software.
darry wrote on 2026-08-01, 16:33:
Without knowing more about your Avisynth setup and potential bottlenecks/issues (threading, thermal throttling, etc), I couldn't really guess why your QTGMC run feels so slow. Last time I ran that or other filters (like deshake) on a 5700x and later 5900 XT, it felt much snappier than whatever I had been running it on before (most likely an i9 9900k, AFAICR). I did run some apples to apples benchmarks (same video file and same settings), which I no longer remember, back in the day and, from what I recall, there was a significant performance gain on my then new AMD CPU. If your Avisynth build and associated plugins used by your QTGMC script are quite old, it may be worth trying newer versions with better support for newer CPU instructions and architectures and threading.
Now that I think about it, the whole setup is a mess. My Avisynth version and plugins are six years old, and I didn't use the AVX2-optimized versions. I'll have to update those some day. I tried the Avisynth and plugin versions that were in the AUR a while back (before the malicious attacks), and it just exits without displaying any errors. I had to use Wine, and because I don't know if I can access the Wine version from native Linux software, I'm doing other edits in VirtualDub2 (the 64-bit version) inside Wine as well. I never figured out how to build a native Linux version because the AviSynth developers only provide Ubuntu-specific instructions.
QTGMC is single-threaded. There's a multithreading option, but no matter how many threads I set, it would crash after a few seconds. I don't think I'm throttling, but with the final video encoding step using all 16 threads, the CPU runs at 4.6GHz instead of the single-core maximum (I think it was 5.5GHz by default). The maximum temperature I saw was 72°C (using a 120mm single-tower Thermalright cooler), so it doesn't seem to be throttling.
Since I mentioned the AUR, apparently a package I installed using standard pacman pulled a dependency from the AUR without my knowledge, and it's one of the affected packages from the malicious attack. I don't think I updated during the malicious campaign, but it's flagged by the package checking script I ran.
darry wrote on 2026-08-01, 16:33:
As for your aversion to added fans to your i5 setup, that is obviously your decision to make, but I personally would not trust an OEM's tolerances and thresholds in terms of thermal management on any hardware that is not relatively "high end", and even then. OEMs typically design their PCs, especially baseline office ones, for "a reasonable lifespan with an acceptable performance profile while staying within safe temperature ranges and acceptable at the lowest cost possible". I design my builds to always operate well below maximum component temperature specs in all but the most demanding scenarios, and use high end, low noise fans as needed to avoid hot spots and throttling. I aim for acceptable noise levels and maximum reasonable longevity without compromising performance. All the words in italic can have vastly different meanings depending on if one is an OEM or a user. I do not know how long I might want or need to use a given machine, so I do not compromise on thermals, even on arguably pedestrian builds, but that is just my opinion.
It always ran hot, but now the room temperature is higher than before. I said several weeks ago that I wanted to try a front fan, but I never did it. Gigabyte's heatsink on this H370 HD3 is a joke (a flat metal plate about 4mm thick with no fins), and it uses a weird mounting hole pattern. Maybe there's a clip-on heatsink (the kind that clips directly onto the chip package) that fits, but Intel says that it's a non-square package (23x24mm instead of 23x23mm).