Solves the unexpected termination of processes that provide services for the application pool. The process ID is **. The process exit code is & amp; #39; 0x80 &

The red-Black Internet under our company will encounter this problem.

Event Type: Warning
Event Source: W3SVC
Event Type: None
Event ID: 1009
Date: Event: XX
User: XX
COMPUTER: XXXX
Description:
The process that provides services for the application pool XXXXX is unexpectedly terminated. The process ID is XXXX. The process exit code is 0x80.
For more information, see Help and Support Center in asp "> http://go.microsoft.com/fwlink/events.asp.
Cause:
CAUSE
Together with each worker process that IIS creates under a separate identity, the system creates a new desktop object by allocating memory from the configured desktop heap. this issue occurs because, when that heap has been exhausted, IIS cannot create more worker processes. clients then receive the "service unavailable" error message in their Web browsers when they try to visit Web sites that those application pools host.
The memory heap quota of independent processes is exhausted. IIS cannot create more process workspaces for processing.
Solution:
Warning you need to modify the registry of the server. Please modify the key values of the previous backup.
Add the UseSharedWPDesktop registry key to your computer that is running IIS. This registry key permits all worker processes to run in one shared desktop, regardless of their worker process identities.
To add the UseSharedWPDesktop registry key:

1. HKEY_LOCAL_MACHINESystemCurrentControlSetServicesW3SVC
2. Create a New DWORD under the Parameters key. The name is UseSharedWPDesktop and the value is 1. Restart IIS.
MS description about this key value:
UseSharedWPDesktop
Registry path: HKEY_LOCAL_MACHINESystemCurrentControlSetServicesW3SVCParameters
Data Type: REG_DWORD
Default Value: 0
Value Range: 0-1.
If you are setting an application pool with a unique identifier, the application pool and memory resources on the server will reach the upper limit of about 60 application pools. Some system resources allocated with a single new logon session have certain restrictions. This indicates that 60 processes can run simultaneously with different accounts. IIS 6.0 allows you to run these processes on a single shared workstation or desktop. The cost is a single encapsulation of sharing a single user session between all parties. To expand to more than 60 application pools and share a single desktop, you can change UseSharedWPDesktop to DWORD Value 1. After this registry key is changed, it should be able to expand to hundreds of application pools and hundreds of working processes running at the same time.