Aside from the fact that you have not asked a clear question, the article points to two things that should be addressed.
1) Does YOUR instance of these match what the article says; i.e. occurring only after a reboot, and apparently not having any other effect? I’d recommend a closer examination of your event logs to see if Microsoft’s observation is accurate.
2) Since some of your error messages bear IDs different than specified by MS, you should use the comment/feedback field at the bottom of the article to point out to them that you are getting a particular error message which points to a somewhat different set of circumstances. And then specify what you’re seeing.
If users do not hold vendors accountable by pointing out inconsistencies such as these, the vendor has little incentive to fix the problem.