The description of the event ID (54) (in Resources (HTTP)) could not find the _win server

This is always seen in the log of Event Viewer:

Event Type: Warning
Event Source: HTTP
Event Type: None
Event id:54
Date: 2008-7-1
Event: 10:52:59
Users: N/A
Computer: YONGFA365
Describe:
The description of the event ID (54) (in Resources (HTTP)) cannot be found. The local computer may not have the necessary registration information or a message DLL file to display messages from a remote computer. You may be able to use the/auxsource= identity to retrieve word descriptions, and to view Help and support for more information. The following information is part of the event: \device\http\apppool.
Data:
0000:00 00 00 00 01 00 52 00 ... R.
0008:00 00 00 00 36 00 04 80 .... 6..?
0010:00 00 00 00 00 00 00 00 ...
0018:00 00 00 00 00 00 00 00 ...
0020:00 00 00 00 00 00 00 00 ...


Solutions available online:

Believe this is due to improper setting of the recycle process, it is recommended to turn off the following process recycle settings:
Recycle worker process (minutes): 1200
Recycle worker process (number of requests): 10000
Enable CPU monitoring, maximum CPU utilization: 90%
Due to the process of automatic recycling, and when every 10,000 clicks, or more than 100% CPU, will forcibly recycle application, causing the client will appear sevice unavailable error. (In fact, 10,000 clicks, the average number of visits to the site, a few minutes is enough.) It is recommended that you enable counter logs to monitor CPU utilization and asp.net metrics to help you locate whether this is the cause of each 5-10-minute occurrence.

Also, do not open the Recycle worker process and use the worker process pool without justification. General reasons are usually unexplained memory leaks, thread hangs, and so on.

After debugging found that the above way is useless, finally found the reason and solution:
Reset the C:\Windows\Temp folder permissions, plus everyone read and write permission, this problem can be resolved, the general people want to see the effect of immediate, so changed the direct observation, or found that there are always related records, you can restart the server or not when the Internet peak restart, The observation will find no such records. OK, problem solved.