Build a great reporting interface using Splunk, one of the leaders in the Security Information and Event Management (SIEM) field, linking the collected Windows events to www.eventid.net. The EventId.Net for Splunk Add-on assumes that Splunk is collecting information from Windows servers and workstation via the Splunk Universal Forwarder.
The description for Event ID ( 108 ) in Source ( G550DH ) cannot be found. The local computer may not have the necessary registry information or message DLL files to display messages from a remote computer. You may be able to use the /AUXSOURCE= flag to retrieve this description; see Help and Support for details. The following information is part of the event: \Device\Video0; display; G550DHD.
|English: Request a translation of the event description in plain English.|
|Concepts to understand:|
What is a DLL?
What is causing the “The description for Event ID ( … ) in Source ( …. ) cannot be found… “?
In one case, this Event ID appeared on Windows Server 2003 SP1 and Windows Server 2003 R2 SP1 when it was installed. The computer had a Matrox Millennium G550 PCIe display adapter installed. When Windows was restarted in normal mode after the installation, the Windows graphics screen appeared, but when I logged on, the screen turned light grey/blue and the keyboard and mouse locked up. I restarted the computer with the power switch, went into Safe Mode and opened Device Manager. I found that Windows Server 2003 had installed a generic Matrox Millennium G550 driver that did not seem to be compatible with the model that I had. I installed the correct Matrox driver by running a setup program for it from the CD supplied with it. When I restarted the computer normally, the lockup problem had been fixed and this Event ID no longer appeared.
This event should normally read:
The driver G550DHD for the display device \Device\Video0 got stuck in an infinite loop. This usually indicates a problem with the device itself or with the device driver programming the hardware incorrectly. Please check with your hardware device vendor for any driver updates.
See the comments for event id 108 from ati2mtag.
|Private comment: Subscribers only. See example of private comment|
|Links: Event id 108 from ati2mtag|
|Search: Google - Bing - Microsoft - Yahoo - EventID.Net Queue (0) - More links...|
Send comments or solutions
- Notify me when updated