<<When you say ntoskrnl.exe errors don't have much resolution, I take that to mean that your experience is that such errors typically corrupt a system permanently.>>
No...that just means that I'm often not smart enough to look at the data presented and make heads or tails of it
There's nothing that corrupts a system permanently, since any operating system, program, file, or hardware component can be replaced or reinstalled.
There's no info that I can see...which points to a specific driver (I'm willing to guess that it's a driver issue, not a memory issue).
You've never really verified that your system is clean.
Users who have malware problems often think that all they have to do is delete a few files and all is well. It's not that easy because the user has no idea of what has been done to the system by the malware or during the cleanup effort.
I can't go any farther with what I'm presented with, I don't have any expertise of any sort.
But...if I ever had a system that was infected with unknown effects...I would surely do a clean install.
Let's see what others have to offer.