Endless reboots on Windows XP after Spybot Search and Destroy update and scan

[Hardball]

Yesterday, September 26, 2012, I updated my Spybot 1.6.2 as I do every Wednesday. I usually choose the Giganet mirror from the list of update sites, but it was not on the list yesterday so I chose SecurityWonks.net#1 (USA). There was only 1 file listed which was a 2MB file, which I downloaded and was installed. I rebooted into Safe Mode and ran my scan. It came back clean, so I rebooted. At this point, when the computer restarted it could not boot into Windows. It just goes into an endless loop of restarts once it gets to the point where Windows would normally load and take you to the desktop screen.

I cannot get into Safe Mode either as it does the same thing of the endless reboot. The first computer this happened on was a family member's which I had updated. I did not know there was a problem at that point because after I did the scan and rebooted, I left. It was a short time later when I was told that their computer was doing this continuous reboot thing and at that time I didn't know that the Spybot update was the cause.

When I got home I had to update my Spybot and do my weekly scan, so I did, and the exact same thing has happened to my computer. I updated from the same SecurityWonks.net#1 (USA) mirror and after the scan was complete and I rebooted, my computer is doing the same endless reboot that my family member's computer is doing. It appears that the 2MB Spybot update file on the SecurityWonks.net#1 mirror for September 26, 2012 is infected with a virus or malware or is corrupted in some way and now I have 2 computers that I cannot use at the moment. What do you suggest I do?

 

[Hardball]

I was able to get the following blue screen error message:
Stop c000021a {Fatal System Error}
The Windows Logon Process system process terminated unexpectedly with a status of
0xc0000135 (0x00000000 0x00000000) The system has shut down.

Is this any help to getting to a solution?

 

[C1]

Id pull the HDDs, install them in a good known computer (or enclosure) that has good malware protection support then try to check and clean the affected drives. This is what computer repair shops often do.

 

[chris2ferz]

I registered at this forum just to reply to this

Not sure if there is any connection to SBSD but do you have a
ws2help.dll file in your windows\system32\
directory?

If not put that file there and see if it fixes your problem. Good Luck :thumbsup:

 

[SimMike2]

It got the "destroy" part right.