If it didn't happen at the time of the FPs on that particular incident, then I highly doubt it is related, especially if it would have caused a BSOD. That would be almost immediate if a file was moved was required on boot.
So the only thing is to post as much info on the BSOD screen as I mentioned, or do a google search on the stop error number and file name that happens to have been mentioned in the info and any title.
Whilst it might be quicker to try a repair install of Windows, you would have to visit windows update as some file used in the repair install may have been the subject of a security update.
On the matter of security updates, there has been on on the last patch Tuesday, replacing some kernel files that has resulted in BSODs, KB977165
http://www.microsoft.com/technet/security/Bulletin/MS10-015.mspx.
I believe this was stated to be caused if the users system had a rootkit infection that effected one of the files to be replaced and that resulted in a BSOD.