It is this..
A kernel power ID 137 event – The system firmware has changed the processor’s memory type range registers (MTRRs) across a sleep state transition (S5). This can result in reduced resume performance.
I don’t think that anything can be done about this. To come out of hibernation, I press the ‘power’ button on top of the case, and it is this ‘event’ which causes Windows to think that something is wrong. Operationally, it makes no difference to me, doesn’t put up a BSOD, and doesn’t affect anything else.
So, the upshot is that I will NEVER have an error free PC. There will always be this one and I don’t care. Here ends the quest to have an error free PC for at least a week.
The point here, and the above error shows it quite clearly, is that not all ‘errors’ are real errors. Just like the ‘one click fix’ utilities, some events are not so much errors, more about not knowing what is happening or why.
Other errors, like the recent MS Office calendar file error, are also not errors with what is being reported as being an error. There was nothing wrong with MS Office’s calendar file. Something was triggering the error message, but it wasn’t the file itself or any process which generally handles the file. I have a feeling that the hotfix released by Microsoft just stopped the reporting, and you know what that means, don’t you. There is an ERROR elsewhwre.. WAH !!
But even if that is all it did, what the eyes don’t see, the heart doesn’t grieve over, except that I have now introduced just enough doubt in your mind that MS did not 100% fix the issue..