Looking for clues as to why a customer's installed system, which uses an embedded PC running XP, is occasionally "freezing up" such that it stops working, the NIC LEDs are off, and when a monitor is plugged in it just says "No Signal" (no video output). I see some entries in the Event Viewer logs that are related to the NI stuff. The product uses NI DAQmx (usb - 6212 I think). There are a couple of things odd -- the timestamps seem to go back in time, about 26 minutes before the previously-logged message, and the status code given is sometimes associated with a BSOD. Can anyone tell me what any of these NIPALK messages means? I'm supplying the next messages on either end to show the time-stamp issue (this is exported text, so it goes from most recent to older messages):
6/3/2014 9:36:29 AM analog Information None 5 N/A hostnameRemoved The description for Event ID ( 5 ) in Source ( analog ) 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\analog. 6/3/2014 9:36:28 AM Serial Error None 18 N/A hostnameRemoved No Parameters subkey was found for user defined data. This is odd, and it also means no user configuration can be found. 6/3/2014 9:36:28 AM NIPALK Warning None 8192 N/A hostnameRemovedviceObjectPointer failed ntStatus = 0xc0000034 6/3/2014 9:36:28 AM NIPALK Warning None 8192 N/A hostnameRemovedows.cpp:71 - queryPCIBridgeFilterDriver: IoGetDe... 6/3/2014 9:36:28 AM NIPALK Warning None 8192 N/A hostnameRemoved[nipalk] Warning: .\source\bus\windows\pdbmWind... 6/3/2014 9:36:58 AM W32Time Error None 29 N/A hostnameRemoved The time provider NtpClient is configured to acquire time from one or more time sources, however none of the sources are currently accessible. No attempt to contact a source will be made for 15 minutes. NtpClient has no source of accurate time.
A coworker saw the NtpClient issue, which I would have thought was no big deal, and he tells me that in a different product, the NTP attempts to update the system clock had to be turned off, because otherwise it would interact with the NI DAQmx driver and would cause a system freeze which could last about 7 or 8 minutes. I had assumed we see these because the LAN is just a direct connect between the device and a server -- no broader internet connectivity is needed nor available.
I'm not asking anyone to solve the problem; rather, I would like to know what these cryptic NIPALK messages are really able to tell us, if only we had the secret decoder ring.
--