Re: Things I Don't Need Today

On 3/9/2024 10:29 AM, Spalls Hurgenson wrote:

On Fri, 8 Mar 2024 13:46:50 -0800, Dimensional Traveler
<dtravel@sonic.net> wrote:
 

On 3/8/2024 8:20 AM, Spalls Hurgenson wrote:

PC's broke.

 

Congratulations on the impressive detective work.

 Thanks... although I'm not sure it's deserved, given how long it took
me to figure it all out. ;-)
 The primary PC is (mostly) back together now; all that's left is to
fasten the chassis covers and plug in the external peripherals. I'm
benchmarking and stress-testing it as I type this. It looks like my
computer is now 5-10% slower than it should compared to synthetic
benchmarks for its processor due to the underclocking. I may be able
to up the clock a bit, but at the moment I'm hesitant to experiment.
The difference reall isn't at all noticable anyway, except in
benchmarks. I doubt I'd notice it at all in games, especially as most
games are limited by their GPUs far more than their CPUs.
  I probably could have solved this problem faster, except
      a) since I had a functional backup PC, there was no essential need
        for a fast solve,
      b) I only had a limited amount of time every day to play
        with the computers (made even shorter by how little
        light gets into the study during winter months). At
        most, I fiddled with the busted PC an hour a day tops,
        and a lot of that time was spent just rebooting (usually
        from a slow external CD-ROM drive),
 and
      c) the whole incident just annoyed me so much that I didn't
        want to bother with it. Especially after I figured out
        the it was the default settings of the motherboard that
        had triggered the whole thing.
  I have to (grudgingly) give kudos to Microsoft's operating system.
Despite the many, many, MANY BSODs and hard shutdowns the OS suffered
through - most of them at boot-up -  when I finally did solve the
issue and reinstalled the HDD, Windows ran as if nothing had gone
awry. This despite the fact that - attempting to troubleshoot the
problem - I had instructed Windows to reset (and later do a clean
reinstall) in hopes that would solve the problem. But since the
hardware kept crashed the OS, it never got very far in that process.
Still, I fully expected I'd have to reinstall the OS. But nope,
Windows came through it all very cleanly.
  So, current plan is more stress-testing, then finally button it all
up, copy all the files I worked on using the backup PC to the
hopefully-repaired primary, stress test some more and then finally
decide it's 'safe' to use it as my primary again. After which I can
hopefully put this whole nonsense episode behind me.
 

Hey, I used to do tech support for the dispatch systems used in 911 centers.  (And this wasn't script-monkey tech support, if it was a code problem I was expected to correct the code and distribute the fix so it could be applied as part of the next regular update.)  Sometimes that kind of slow repetitive grind is how you get it done.
--
I've done good in this world. Now I'm tired and just want to be a cranky dirty old man.