Major mugging...what happened?

Hi,
I feel like I was just mugged--my system was running perfectly, Eset anti-virus and superanti-spyware said it was clean. Then I tried to run Malware Antimalwarebytes and got the famed 732 error. So I uninstalled it, used the cleaner to get rid of debris, restarted and downloaded it again from cnet. It up -dated fine and everything seemed to be okay. Even ran a scan--I don't even know if this is related to the problem. (Let me say that my son's computer had the same error and I did the same thing with his MAMB just before I did mine, and his compute is still fine.)
Then I did windows update. Everything was fine. (XP SP3)
This morning I tried to get onto the Internet (where I work) and I couldn't connect. Tried to run an Eset Smart Security virus scan--scan failed. Tried to run MAMbytes scan--software wouldn't even come up. Superantispyware said everything was clean. So I restarted in safe mode and ran Eset from there twice. Restarted and my computer informed me that it had recovered from a serious BSOD error. Eset scans now work -everything is clean. The internet works again. But I have no idea what happened or if it will happen again. The eset log shows things like "bad archive" and AOL stuff but nothing actively evil. I will attach it if it will help.There are trojans in quarantine, but none are that recent. (I wasn't exactly sure how to permanently delete them.) The error signature on the Microsoft report said:
BCCode : 1000008e BCP1 : C0000005 BCP2 : 805C3151 BCP3 : B466F9F8
BCP4 : 00000000 OSVer : 5_1_2600 SP : 3_0 Product :256_1
Was that the windows update that smacked me down? That and MAMB are the only things I have downloaded. What should I do now? (Let me add that I need it in small words!) Thanks.

 

These semi-random BSODs can happen at any time. In this case it looks like AOL caused it, but it was probably not their fault, and there was probably no virus/malware that caused it.

If it happens again I would be more concerned however.

 

Really? Just random? Yikes--it's never happened to me before. Since the last thing I did was a windows update, I figured there was something in there. Ok, thanks. I'll just keep moving on...