Pasting in contextual information from another topic ~ OB
Here is a little history.
March 30th A Windows problem first became evident as the CPU spiked to 100% and on reboot, Windows would not boot up stating it could be a hardware or software problem. At that time I thought it was the motherboard and had it swapped out because the error I had was different but the symtoms were the same prior to the system not booting.
April 6th got the laptop back from HP and put in my HD to boot from. It worked for a day and then the CPU spiking issue was found, only this time with no failure to boot.
Since that date I have tried to isolate the issue but to no avail. I have tried various restore dates and images, as well as manipulating the data on the master image (delete WoW before issue is active and reinstall it from scratch). None of it has worked.
My latest attempt was to restore from my oldest image available [the other night]. It was left restoring and hasn't been tested yet. I am not sure if the "issue" will be visible on it. I tested one last night 3-4 weeks later (Feb 16th date) and it was but apparently never became active for close to 2 months...
End of added material. ~ OB
This is in reference to http://www.bleepingcomputer.com/forums/topic219056.html and http://www.bleepingcomputer.com/forums/t/218815/cpu-runs-at-100-constantly/.
I have attached the log files that you requested. I had to run this from safe mode however. It still took close to 10-15 minutes to create.
I have removed SAV and installed Kaspersky. I am in the process of actually booting off of their boot scan CD to run a scan on the system. I figured it would be faster this way versus on a system that is running at 100% CPU. Thanks for your time.
Edited by Orange Blossom, 14 April 2009 - 03:45 PM.