RESOLVED:
As I said in the original post below I couldn't view Avg Energy Impact in Activity Monitor. Not a big deal, but annoying. The resolution for me was to whack everything in /private/var/db/systemstats and reboot like:
sudo launchctl stop com.apple.systemstatsd
sudo launchctl stop com.apple.systemstats.periodic
sudo launchctl stop com.apple.systemstats.analysis
mkdir /Users/Shared/oldsysstats
sudo mv /private/var/db/systemstats/* /Users/Shared/oldsysstats
sudo shutdown -r now
After restart, the content of the systems stats directory is reconstituted, no more crash of systemstats, and Avg Energy Impact is now working.
FWIW (not much), the boot uuid referred to by systemstats does NOT match the boot volume UUID... It must be some other UUID, but I have no idea what it is.
Original Post:
I too am having this problem. I can cleanly reproduce this crash in systemstats by opening Activity Monitor and then clicking the Energy tab.
As far as I can tell, none of you stated which application is actually crashing with this exception... Is it systemstats, or something else?
I can find very little information about "boot uuid" in OSX. All references appear to refer to the boot volume uuid, but I have no idea how or why that would be related to gathering power stats through systemstats.....
Anyone have any ideas?
EDIT: I should have added, that the result of this crash is that no average energy impact is displayed in the Activity Monitor. Not really a big deal, but this is more than a superficial problem.