I'm not grumpy.. and my reputation is as low as it's ever been (ie. intact).
Blue screen? Do you mean a BSOD?
Yes, BSOD--and I'm rather certain that it was my fault, as I suspect that, in trying to restore the CPU to a reasonable level of use, I killed a process that Windows Vista requires.
And now for the news at 1219 Local: I was on-line for a while early this morning, then ate breakfast, etc. When I returned to the computer, it was asleep. As soon as I awakened the machine, SuperAntiSpyware started its scheduled weekly scan.
When I left for a run, the CPU was around 40%. Upon returning to the computer, Super reported no problems found, but Process Explorer again showed the CPU at 100%.
After closing Super, only Firefox and Thunderbird were open (along, with, of course, Comodo, and other such programs.)
Looking at Process Explorer, I found two instances of cvtres.exe active; both were the file in Net/Framework. When I killed those, the CPU dropped momentarily, then went back to 100%; that's the first time that has happened.
I also found csc.exe was running, plus two instances of calcs.exe. The latter two were the basic culprits, each using forty percent or more of the CPU. A quick Google search said that calcs.exe is critical, so instead of trying to kill their processes (and likely getting another BSOD), I rebooted.
Right now, CPU is at 5%, with no instances of csc.exe, cvtres.exe, nor cacls.exe running. I'm way beyond understanding any of this, what is causing it, how to fix it (along with everything else in the world...).