Windows 10: Why IIS application pool stopped frequently with error code 0x80070426 ?

Our application installed on Windows server 2016.It is build using asp.net. Application pools are getting stopped frequently.When we try to start its throwing below error. Application pools are configured with machine account.Cannot Start application pool.There was an error while performing this operation.Details:The Service has not been started error 0x80070426 Exception from HResult 0x80070426.Event Viewer:A Process serving application pool AAA terminated unexpectedly. The Process id was '53376'. The process exit code was 0xffffffff.What I have tried:I tried reset of IIS but it is not helpf

:)

 

Unable to update - Error code 0x80070426

There was a similar issue discussed here Windows Activation Error, Error Code 0x80070426 - Microsoft Community

have a look.

 

stop code bad pool caller

I've tried numerous suggestions but can't seem to fix the Stop Code Bad Pool Caller from continually coming up. I use Windows 10, with a Samsung Series 7 computer. I'm hoping to find something specific to the Bad Pool Caller error. Any suggestions? Thanks,
Steve

 

Application pool with custom account crashing

Debug Steps

• Restart the computer if you've not already in case there is a pending update, fragmented memory, etc. just to rule out common issues a simple power cycle eliminates.
  
• Check the Event Viewer logs for both Application and System logs for anything relevant to this issue to see if there's something in there are indicates what the issue may be.
  
• Turn on debug logging to the screen in the config file, restart the app pool, and then try again to see if it displays anything to the screen you may see before the app pool stops.
  
• Turn on more advanced or verbose IIS logging to see if that shows anything relevant.
  
• Set the top/main site to .NET 4.0 or the higher .NET and then set the sites/apps beneath to be the 2.0 or lower framework explicitly. Doing with the higher .NET Framework version and lower implicitly can cause problems like this
  
  • If this web app is within "a main/the default" site of IIS (like a subfolder in the hierarchical IIS structure) see what the top or main site is set to use .NET version wise. If the top level is set to 2.0 or something less than the .NET Framework this app uses, then this could crash the app pool potentially.
    
• Create a new app pool with applicable settings and then set the app to use it and see if that makes any difference.
  
• Run a Wireshark or a TCP/IP sniff of equivalence on the machine see if there are any packets of relevance indicating what the issue may be.
  

Further Resources

• Enable Debugging for ASP.NET Applications
  
• Configure Logging in IIS