SurfaceOemPanel cannot be found Error in Event Log

These are legacy Event IDs which shouldn't be used by the Surface Panel firmware developers.

Event ID 514 is "An authentication package has been loaded by the Local Security Authority."

Event ID 513 is "Windows is shutting down"

Event ID 512 is "Windows is starting up".

In sequence, you're just performing a standard reboot. The errors are saying the Event Descriptions are not present for those IDs, which would be correct. It should be safe to ignore, as the error is with the lack of a description not that the event itself is the error.

For a list of events check out https://docs.microsoft.com/en-us/windows-server/identity/ad-ds/plan/appendix-l--events-to-monitor

For anyone hitting issues, the actual error would be before these events.

Did you have Bitlocker on that machine? I have found that opening the laptop when rebooting or starting it is a decent work around for my environment, but I would like to find a fix.

Did you have Bitlocker on that machine? I have found that opening the laptop when rebooting or starting it is a decent work around for my environment, but I would like to find a fix.

Hi, 

I have a Surface Pro X, and I was checking the event log, and I can see many errors from SurfaceOemPanel, but they all state that "The description for Event ID 512 from source SurfaceOemPanel cannot be found. Either the component that raises this event is not installed on your local computer or the installation is corrupted. You can install or repair the component on the local computer."

Same for Event ID 514.

Not sure what this error is, and what is the issue, but I have been facing problems with Skye For Business, and I think these events are related.

Thanks

surface pro x, brand new bought on May/2021, I have the event ID 514 and then the surface pro X will shut down. I have another thread to record what I see. No solution yet. The surface pro X will shut down randomly.

surface pro x without surface keyboard randomly enters hibernation - Microsoft Community

Same error, brand new out the box. No docking station no external monitor ever connected.