I was replying to the thread when another crash happened (I am assuming it did since I was remotely accessing the computer and now it's gone...). Thus, I will have to wait until I get home later today to be able to upload.
There was a C:\Windows\memory.dmp file about 700MB in size -- I think that is a full kernel dump -- I had opened it in WinDbg and the message stated something to that effect. Of course, it is probably now replaced with a new one based on the last crash. I was running Driver Verifier this time, fortunately.
Regarding the inpoutx64.sys driver, this refreshed my memory with the following potentially relevant info:
I purchased and installed a parallel port PCI card, probably around the time the crashes started, but I am not 100% sure. I removed it since, thinking it might be the culprit, but I still got BSOD after it was removed, so I ruled it out. Perhaps the drivers left behind during that installation could still be causing the problem even though the physical card is gone. More specifically, the reason I installed the card was to connect a special kind of adaptor called a JP1 cable used to program TV remotes. It turns out the JP1 software was not working correctly with a parallel port in Windows 7, so someone in the JP1 forum uploaded a new InpOut32.dll driver that fixed the problem. I downloaded and installed the driver, and it fixed it for me -- perhaps this is what started the BSODs. If it helps, the forum page where he describes the changes is:
JP1 Remotes :: View topic - Parallel Port JP1 on Win7-64bit?
What is the frame access driver for? Broadcom is probably the manufacturer of the NIC card so of course I wouldn't want to lose network connectivity.
