I could have sworn the last time someone had this problem it was the desktop command widget, but that's just off the to of my head.

As suggested, the best bet is to use top in x terminal or Conky, to see EXACTLY what is using up the CPU like that.