How to fix w3wp.exe faulting app and kernaelbase.dll effecting IIS web server.

Randy Fitchner 5 Reputation points
2025-03-07T21:45:13.21+00:00

Faulting application name: w3wp.exe, version: 8.5.9600.16384, time stamp: 0x5215df96

Faulting module name: unknown, version: 0.0.0.0, time stamp: 0x00000000

Exception code: 0x00000000

Fault offset: 0x00007ffb14f97770

Faulting process id: 0x1908

Faulting application start time: 0x01db8f3f4e7c3a7d

Faulting application path: c:\windows\system32\inetsrv\w3wp.exe

Faulting module path: unknown

Report Id: c45130b1-fb76-11ef-81be-005056ab5c24

Faulting package full name:

Faulting package-relative application ID:

Windows Server 2012
Windows Server 2012
A Microsoft server operating system that supports enterprise-level management, data storage, applications, and communications.
1,626 questions
0 comments No comments
{count} votes

2 answers

Sort by: Most helpful
  1. charles southard 0 Reputation points
    2025-03-08T09:12:06.4566667+00:00
    
    english
    
    0 comments No comments

  2. MotoX80 35,596 Reputation points
    2025-03-08T16:01:27.1166667+00:00

    You will first need to do additional troubleshooting to figure out what IIS is doing at the point that it crashes.

    What can you tell us about the web site? Does it serve up ASP, ASPX, PHP pages? Or something else? Was this code developed by someone in your organization or did you install some 3rd party software that is hosted by IIS?

    Does it crash immediately, or does it successfully serve up pages for a while and then it crashes? Has it always crashed, or did you recently install something and this problem started after that?

    Check the logs in C:\Windows\System32\LogFiles\HTTPERR to see if it identifies the URL being processed when the crash occurs. Check the application and system event logs to see if any additional diagnostic information is available.

    Two common IIS problems are hanging requests and memory leaks.

    Launch the IIS manager and from the home tab double click on Worker processes. Make note of the Private and Virtual bytes reported. Monitor those over time and see if the values continue to increase. Right click on the app pool and select View Current Requests. Look at the Time Elapsed value and see if you have requests that are running for a long time.

    User's image

    User's image

    Press F5 to refresh this display.

    User's image

    0 comments No comments

Your answer

Answers can be marked as Accepted Answers by the question author, which helps users to know the answer solved the author's problem.