I have seen this before. If memory serves me correct, its a profile issue. Delete the profile and the computer seems to work just fine thereafter! I suspect its some orphaned temp files or something messing up the kix execution process. Anyway deleting the profile seems to fix the problem when its very rarely occurred.