Use of this function is highly encouraged. For Windows 95, calls to this function provide users with a dialog box notifying them that an error occurred. In addition, information provided as part of the NdisWriteErrorLogEntry function is written to an error log file called Ndislog.txt.
Any troubleshooting documentation provided with the driver should list all error codes passed to this function. Because it is possible to uniquely number each call to NdisWriteErrorLogEntry, it should be relatively easy to design errors that isolate specific common installation and hardware problems.
It is mandatory that this function be used only in initialization code. Use of this function at any other time may cause unexpected results.