I don't know what problems may or may not be a result of the intrusion.
Win32k.sys errors can be the result of software incompatibilities though (although no beeps would usually be generated for these and messages such as you got).
Other than overheating as a hardware issue, I don't know what else on the board you could address.
On the software side, try
clean booting and testing (antivirus, firewalls and security installations are the most likely software culprits, but graphics hardware and drivers should also be considered) >>
Start >> Run >>
msconfig and select the
Services tab. Check
Hide Microsoft Services and then disable the rest. Also uncheck
load startup group on the general page.
http://support.microsoft.com/kb/929135 << written for Vista, but applies equally well to XP
Now restart and test the issue at hand
If no problems, run msconfig and recheck half the disabled items on the Services tab. Test again. If the problem recurs, uncheck half the items you just checked to narrow down the culprit.
If the problem didn't occur, check the other half, so all the Services are enabled -- proceed to do this on the startup tab as well.
Get the idea? You want to isolate the problem to a specific startup if possible.
Note: if you already have items unchecked under msconfig >> startups and are in "selective" startup mode – you should note what these are before beginning. They will need to be unselected again.
............................................................................................Please be a GeekPolice fan on
Facebook!Have we helped you?
Help us! | Doctor by day,
ninja by night.