The Windows Event Log is a wonderful thing. However, sometimes the output is less than complete, more than complete or unintentionally misleading.
After an exhaustive search, I did discover a means to uncover the actual cause of errors by using the DWORD code in the Data pane of Event Viewer. In an Event Viewer error:
- Click "Words".
- Copy the last DWORD to your copy buffer (it's the last 8-character string).
- Search the internet for NTStatus.h
- When you find NTStatus.h (I found it at SourceForge), click on the body of the web page, press Control-F (find) and past the DWORD string into the find box.
- Click the Find button and you should jump to a more usable error.
If you cannot find NTStatus.h, you might also search for WinError.h. Both these files are part of the NT SDK (which I didn't have installaed, so I did a web search instead).
No warranties, etc., etc.