Blue Screen error 0x0000007B in Windows XP after installing KB977165 (MS10-015 – February 2010)

I have read this entire posting, only to find that there still seems to be no true resolution to the problem. The only difference that I can note prior to the installation of the updates, is that I was getting errors when opening EXCEL and WORD noting that they weren't genuine Microsoft (which was totally incorrect). These errors occurred shortly after the updates downloaded. Then, when my system shut down last week, I attempted everything .... even to the point of accusing my motherboard manufacturer of sending me a piece of junk. Looks like I owe them an apology. Someone noted that it was a Trojan virus, which it might very well be, however, the Trojan was obviously targeted at the Microsoft update, otherwise, this type of failure would not have resulted, especially to the extent that it has. And, then the question as to how long has this Trojan existed? Was it new? Did it download with the Update? Was it a part of the Update? Who knows....probably only Microsoft. The question that I have is what does Microsoft plan to do to correct the problem and how long? Thank goodness, I have my laptop, but can't access any of my children's homeschooling records or studies. Meanwhile, I have to recreate everything possible, until Microsoft gets their act together. And yes...I'm venting. Microsoft should have notified consumers last week of this issue. I have spent almost a week working to resolve my computer issue, only to find out that it is total software, not hardware. This is ridiculous for a company like Microsoft. My system runs Windows XP Pro with tons of memory, a hugh HD, and all sorts of other really nice things I put in it when I built it last year. And I choose not to use Vista or Windows 7 until all the bugs are out of it. Consumers shouldn't have to be the troubleshooters.

MUDGUTTS, 

I have seen this on 2 XP systems, both had malware also (Trojans) on them! So your point about this being caused BY the Trojans instead of the patches could be valid.  Also, my 2 cents:

Scenario 1. Running anti-malware scanner inside an infected OS.

Scenario 2. Running anti-malware scanner on HEALTHY OS, then scanning an infected OS on a separate 2nd HDD.

It can be a little risky to run an anti-malware scanner on an infected 2nd HDD (that has a Windows OS on it)  that is then attached to another PC as a slave or a secondary drive as you suggest in Scenario 2 above. All the information about anti-virus/anti-malware software that I read says to run a scanner INSIDE or ON the OS and HDD of the affected drive (as in Scenario 1) because then removal of an infection can be done properly with the Windows environment by removing the infection FROM a system file or process etc. Of course if you can't get the infected drive to boot in order to run a scanner in it, that's a different case.

If an anti-malware scanner is run in Scenario 2, and it finds an infection on the 2nd HDD, it might rip out an entire system file causing more damage. If all you want to do is scan the secondary drive to get rid of the infection w/o worrying about trying to get that 2nd HDD to boot it's ok.