It would run for about a week at a time before locking up and requiring a power cycle. I did some clean-up and repair, and got it to the stage where it could go for about two weeks at a time, but unless it was restarted in that time, it would eventually die again.
One of the last fixes I did was to set up a reboot script to restart the machine every Sunday morning. Yesterday the machine was working fine, and this morning I had to trek down to the basement to restart it. When I checked the logs, I saw that it had not restarted this morning like it was supposed to. I checked the schedule I had set up, and I caught my mistake there - I had not given it sufficient permissions to run when nobody is logged into the machine. I changed the settings, and I'll look in on it again next Sunday.
The issue seems to be one of resource exhaustion. A small handful of services are slowly chewing up the system resources until it does not have enough left to create a login session. I did a bit more Googling this morning, and I discovered that the swUSB process I had assumed was a Windows process is actually part of the drivers for the RealTEK LAN device I'd had hooked up to the machine when we first set it up. I was using that device until sometime after the swap to Windows 10, and I am thinking its drivers did not like the update.
I replaced it with a better ASUS device awhile back, but I guess I neglected to uninstall the RealTEK drivers. A couple of sources I read mentioned that their driver had a serious memory leak, and since it is one of the culprits that always comes up when the system runs out of resources, it was an easy hit.
Another process that keeps coming up in the list of resource-hogs is SMSvcHost.exe. It is a legitimate service (I checked to make sure it hadn't been replaced by a Trojan), but when I poked around at what it does, it did not seem especially critical. I have disabled the service for now to see what kind of an impact that has, but so far I have not noticed any difference. If I start seeing errors and warnings in the system logs about it, I'll turn it back on.
On a completely unrelated note, while I was puttering around the house this morning, I got to mulling on old friends I had in the Lion King fandom community back in the day, and it occurred to me that I have lost touch with all but a few of them. Some of them were very talented writers, and we would often bounce our stories off each other for comments and critique. One writer was a giant in the community, whose fan fictions spawned a whole genre of fan fictions of their own. When I say "he", it was actually a collaborative team. This one writer did most of the work, but he often paired up with others in the fandom to produce the stories.
I was never a huge fan of his work, but I was also not his target audience. They were very popular with the 13-21 age group, in part because each of his stories was as much an emotional roller-coaster as it was a tale. While I admired his work, and never really begrudged him his popularity... well, ok. Maybe a bit, but who isn't a bit jealous of the popular kids now and then? Anyway, I always felt that his writing was top quality, but I also found it to be somewhat manipulative. He was a master of wresting emotion out of his readers.
Anyway, he started on a fairly ambitious writing project with a mutual friend, and as he went, he often sent me chapters to review. For some reason he respected my opinion. For the most part I did not have much feedback, other than pointing out areas where the prose became a bit too purple, or minor issues like confused attributions and the like.
Then there was the chapter.
He sent me several chapters to read through, and I dutifully read through them, making minor notes, suggesting small revisions, and rolling my eyes at obvious emotional tugs here and there. Then I got to the chapter where he excruciatingly killed off one of the main characters in a very long, emotional orgy of sadness. I could tell that he had poured a lot into this chapter, because it really stood out from the others he had written. He had obviously given it a lot of thought. It looked like the chapter he had been waiting to write.
The problem was that it did not fit. It seemed to have no place in the story other than to make the readers sad. Other than that character falling out of the story from that point forward, nothing changed. It did not inspire any action on any of the others in the story, nor did it even affect the overall plot. Everybody else in the story continued on as if nothing had happened, other than expressing their sadness that the character's passing once or twice in the next couple of chapters.
When I gave him feedback, I fear that I may have been a bit too ruthless. I told him that the chapter was wonderfully written, but that it was just an interlude of pointless pathos. I asked him to explain its purpose in the story, and pointed out that if the chapter did not exist, the story would not actually change at all. He offered up some justifications for the chapter, and I pulled out the passive-aggressive card and said, "Well, it's your story; include or exclude it as you choose. You asked for my opinion, and I gave it."
In the end, he removed the chapter, but I think it hurt him to do it. I do feel a bit bad about that in retrospect, since it didn't really hurt anything by being in there, and I can't help thinking that I overstepped a bit by calling him on it. He stopped sending me stories for feedback after that. I guess I can't really blame him.