Lasnight I replaced cpu CPU with a faster chip.
Simple enough right?
Now MCE/WMP won't work right because DRM is screwed up, and lsass is constantly eating up 25-30% of the CPU. Thank you microsoft, once again your DRM system shows how horrible it is.
According to the log my AV scanner completed a scan latnight which was clean, and I don't use it to get on the net.
I ran spybot on it to be sure, and I have combofix scanning now, but that could take forever.
Besides I'm sure it's clean this obviously has something to do with hardware change,or it triggered something however you want to look at it.
I deleted the DRM files so I can jump on MS's site and generate new keys.
When I start the drm process on MS's site IE starts taking up 25% cpu time on top of lsass.
So i've got 50% in use then....
Lsass is still going crazy I'm assuming that's why the individualize isn't working because of IE's cpu usage.
Any other ideas?
Thanks,
Kenny
I was up until 5:30 this morning trying to fix it and still working on it lol