Event ID: 12 Event Source: sfsync02 Event Type: Error Event Description: The description for Event ID ( 12 ) in Source ( sfsync02 ) 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: . Comment:

Event ID: 12 Event Source: ipnathlp Event Type: Error Event Description: The DNS proxy agent encountered while obtaining the local list of name-resolution servers. Som DNS or WNS servers maybe inaccessible to the client to the local network. The date is the error code. Comment: how to fix it...

Event ID: 12 Event Source: NAVEX15 Event Type: Error Event Description: The description for Event ID (12) in Source (NAVEX15) 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 retrive this description see Help and Support for details. Thew following information is part of the event. Comment: my friend sent me screenshot of this error it is possible that I'ld now much more about error/proplem in close future. Proplem is the computer is restarting few times when switch on and then is working fine for rest of the day another close events is about network card problems i.e. private address.

Event ID: 12 Event Source: Event Type: - Event Description: - Comment: I've also the same error with a Gigabyte GA-X48-DQ6 mainboard. I tested with different Windows 7s build and saw that the RC build 7100 is not given this error but builds 7137 and the latest 7201 are given this error when entering the S3 sleep mode. Index: 0

Event ID: 12 Event Source: w32time Event Type: - Event Description: - Comment: VERY important - any registry settings you make are overridden by Group Policy settings in Active Directory. We were chasing down this error and all of the registry settings were correct, but Group Policy was changing the server type from NTP back to NT5DS. Oops. Index: 1065

For more information see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.
Data:
0000: 00 00 00 00 ....

Comment:

Event ID: 12 Event Source: w32time Event Type: Warning Event Description: Time Provider NtpClient: This machine is configured to use the domain hierarchy to determine its time source but it is the PDC emulator for the domain at the root of the forest so there is no machine above it in the domain hierarchy to use as a time source. It is recommended that you either configure a reliable time service in the root domain or manually configure the PDC to synchronize with an external time source. Otherwise this machine will function as the authoritative time source in the domain hierarchy. If an external time source is not configured or used for this computer you may choose to disable the NtpClient. Comment:

Event ID: 12 Event Source: Google Update Event Type: Error Event Description: The description for Event ID ( 12 ) in Source ( Google Update ) 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:
Application update.
pid=3444 ver=1.2.183.39 lang=ru machine=0 extern=1
App={8A69D345-D564-463C-AFF1-A69D9E530F96} Ver=6.0.472.63 PrevVer=6.0.472.63 Status=0x00000001. Comment:

Event ID: 12 Event Source: Event Type: - Event Description: - Comment: What am I supposed to do with this? Event properties lists the error from Source Hal, Event ID: 12, level: error. I purchased EventID, but what do I do as a non-pro computer user to fix this issue? Index: 0

Event ID: 12 Event Source: W32Time Event Type: - Event Description: - Comment: I got this error after moving the PDC emulator role from a W2K3 DC to a W2K8 DC. The time service was unable to sync with the configured external NTP time source. Changing the registry value
HKLM\SYSTEM\CurrentControlSet\services\W32Time\Parameters\Type from "Nt5DS"to "NTP" fixed this issue. Index: 4644

Windows Event Log Analysis Splunk App

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.