New
#1
BSOD on XP after Avira autoscan
My girlfriend's sister is having a problem with her HP Pavillion XP computer. Twice now it's crashed after Avira pops up to do an autoscan. The first time I wasn't there for it but yesterday I was starting up her computer when it happened. Once the computer was booted up, the Avira Luke Filewalker popup came up and started to do an autoscan. She told me that at the end of the scan it crashes to a BSOD. I let the scan continue which took a couple minutes and then sure enough I got the BSOD. I booted again and the computer froze up after a few minutes as I was looking in the error logs. After another reboot, everything seemed to run okay and I managed to follow the instructions here for the SF_Diagnostic_Tool. I'm attaching the results here. I ran Avira manually not yesterday but after the first time she told me it crashed and it ran and completed fine. I also ran Spybot and yesterday after the crashes I ran Windows update which ran the malicious software removal tool, and again nothing was found. Any help would be appreciated.
One other thing - In one of the logs I saw the error "Bad Pool Caller". Also, the date was still saying it was the 6th yesterday and for some reason I had to manually change the date before windows reset the time properly. Another strange coincidence is no more than an hour or two after that first happened to her last week, her HP monitor died too. She bought a new monitor yesterday which we connected before the second BSOD I saw yesterday. She has a surge protector but it's older and not the best. Could a surge be responsible for having damaged the pc and fried the monitor? My girlfriend also said at work the last week 11 of their XP PCs have had virus issues that targeted their Malwarebytes software and removed it and caused other issues. She said their Windows 7 PCs are fine. I wonder if this is her issue?
Quote
Do not start the trial version of MalwareBytes 