If the WPF service is set to manual try setting the service to Disabled then rebooting.

Check your CPU temps after doing so.  If they return to normal you can be pretty sure a corrupt font cache is to blame.

CCleaner is a tool that can help with stuff like this as it will actually delete your font cache allowing it to be rebuilt as part of your weekly maintenance.

http://www.piriform.com/CCLEANER

It's pretty safe to use and it's the only thing I'd recommend.

I deleted part of  WPF so that it would be rebuilt, actually. And it still runs as described temps. [presently between 60-67C as I write.

Delete all the “FontCache…dat” files you find, such as “FontCache-System.dat” or “FontCache3.0.0.0.dat”.This will cause the WPF font cache to rebuild itself. However, if the problem persists, you might need to shut down the WPF font cache permanently.


The overheating continues, apparently, but 20 degrees cooler than before, when the cache was in an infinite loop. 


Can I actually DELETE the WPF permanently, though, without causing problems for some apps?

Solution #2: Shutting down the WPF font cache If all else fails, you have no choice but to disable the font cache. This may cause a slight slowdown when loading applications that heavily rely on fonts or offer a font picker (which loads hundreds or even thousands of your installed fonts). But, it’s a lot less painful then working under 50% CPU stress and hearing a fan working on overdrive. So how do you get rid of WPF font cache? It’s simple—go to “Control Panel”, and click on “System and Security”, “Administrative Tools” and “Services”. Scroll all of the way down until you see “Windows Presentation Foundation Font Cache”. Double-click on this entry, and select “Disabled” from the “Startup type” list.

You may encounter some slight delays in your WPF applications, but at least your PC will be running at full speed again.
-----------------------------------------------------------------


Is the above advice substantiated and advisable? I guess I could try it and do a system restore?

I wouldn't sweat it just leave it disabled unless something that requires it is suffering as a result.

It could be caused by a corrupt font so everytime the cache gets rebuilt it is causing trouble.  Removing some fonts that you know are not needed can help here.

Thanks Jonbuoy. I think you're right. It could be a corrupt font, and I have many fonts because I do all sorts of DTP and film editing. I won't sweat it- I'll just set it and forget it.