There was similar problem described - "execution of the xp_readerrorlog command stops responding (hangs) and cannot finish. Additionally, the CPU usage of the CPU that is running the command increases to 100 percent."
There is hotfix from Microsoft - http://support.microsoft.com/kb/973524/en-us
But it is related to versions prior SQL 2008R2.