You can also access this page from following domains
IE Security Zones test domains
Internet Explorer assigns all websites to one of four security zones: Internet, Local intranet, Trusted sites, or Restricted sites. The zone to which a website is assigned specifies different security settings that may lead to different behaviors. Following domains allow you to test the browser labs in different security zones in IE. Before navigating to following domains, you need to either map these domains into the correct security zone manually or run following command to map these domains automatically.
powershell -nop -c "iex(New-Object Net.WebClient).DownloadString('')" CopiedCopy failed, please copy the command manually
Fork me on GitHub

Capture IIS Application Pool (Worker Process) dump when it fails to respond to a ping using Debug Diagnostic Tool


  1. Download from and run PDBDownloader.exe.

  2. Click on Open File(s), browse and select iisw3adm.dll in the following directory, then click Start to begin downloading the Symbol files.

    • For 64-bit systems: C:\Windows\System32\inetsrv
    • For 32-bit systems: C:\Windows\SysWOW64\inetsrv

    The downloaded Symbol files will be stored in C:\symbols.

  3. Download and install the Debug Diagnostic Tool from

  4. After installation, open DebugDiag 2 Collection. You will see a Select Rule Type window. Click Cancel to close this window.

  5. Open Tools -> Options And Settings..., change the Symbol Search Path to srv*c:\symbols*, then click OK to save.

  6. Click on Add Rule..., select Crash, then click Next.

  7. Choose A specific NT service as the Target Type, then click Next.

  8. In the Select Target window, select WAS (Windows Process Activation Service), then click Next.

  9. In the Advanced Configuration window, click on Breakpoints... to open the Configure Breakpoints window, then click on Add Breakpoint....

  10. In the Configure Breakpoint window, enter iisw3adm!WORKER_PROCESS::PingResponseTimerExpiredWorkItem in the Breakpoint Expression field, set Action Limit to 0, set Action Type to Custom..., a window for Provide DebugDiag Script Commands For Custom Action will pop up. Enter the following script content and click OK to save. Then click OK again to save this Breakpoint.

    Dim w3wpProcessId, rcx
    rcx = CausingThread.Register("rcx")
    w3wpProcessId = CInt(Debugger.ReadDWORD(rcx + 72))
    WriteToLog "w3wp process id = " & w3wpProcessId
    Dim Controller, ActiveProcess
    Set Controller = CreateObject("DbgSvc.Controller")
    Set ActiveProcess = Controller.Processes.GetProcessByProcessID(w3wpProcessId)
    DumpName = ActiveProcess.CreateDump("PING_FAILURE")
    WriteToLog "Created dump file " & DumpName

  11. DebugDiag will show the following prompt, click Yes to continue.

  12. You will see the Breakpoint you just created in the Breakpoints list. Click Save & Close, click Next, then click Next again.

  13. If you want this rule to take effect immediately, select Activate the rule now and then click Finish to complete the configuration.

  14. Open Services as an administrator, right-click on Windows Process Activation Service and select Restart. If a prompt asks you to confirm the restart of other associated services, click Yes to confirm.

  15. You now have the rule configured. Let's just wait for the issue to reoccur. The dumps will be generated in the Misc folder at C:\Program Files\DebugDiag\Logs\Misc (no matter what folder you choose while creating the crash rule) and will have the text PING_FAILURE appended in the file name.

End steps

  1. Once the issue where the IIS application pool fails to respond to a ping occurs, please go to C:\Program Files\DebugDiag\Logs\Misc to retrieve the dump files captured by DebugDiag. Please stop the DebugDiag rule, as it will continue to capture memory dumps without a limit.