IIS version is 5.1.

Please try using this CVS snapshot:

  http://snaps.php.net/php5.2-latest.tar.gz
 
For Windows:
 
  http://snaps.php.net/win32/php5.2-win32-latest.zip

Thank you, Tony.  I tried it.  I'm still getting the same result -- but the memory address that's trying to write to itself is different.  

Should it help you to track this down, I am noticing that each time it aborts, the memory location is different, but it's always some location trying to write to itself that is failing.  

In my initial report, I was mistaked about where the error occurs.  It is in the very last phase, after "Windows is shutting down" is displayed on the screen.  Sorry.

I was exploring the registry, and noticed two things I thought I'd bring to your attention.  I've never been a registry expert.  But, these two struck me as curious:

HKEY_LOCAL_MACHINE
 SYSTEM
  ControlSet001
   Control
    Nls
     MUILanguages
      RCV2

This contains a rather long list of .dlls and .exes, but php5isapi.dll is not in the list.

HKEY_LOCAL_MACHINE
 SYSTEM
  ControlSet001
   Services
    W3SVC
     Parameters
      Script Map
       .php = [PUT PATH HERE]\php5isapi.dll

That is the exact text for the value.  It has to be finding the API, or phpinfo.php wouldn't be running, right?  But, "put path here" when I specifically browsed out to it when I entered it into IIS?  That doesn't seem right.  Honestly, neither does the fact that I have to put php.ini in C:\WINDOWS when C:\PHP5 is in my path in environment variables.

Thank you again for your efforts.  Please let me know if there is anything else I can try.

Could you try the same test with a script without a call to phpinfo();

A simple echo "Hello World"; or something simple like that.

Thank you all for your efforts.  I can't afford to be without PHP, any longer.  I've installed the CGI interface, and that works without issue, including running the phpinfo() shell. 

I honestly would like to try to help you to track this down, but I have to have a stable production environment, I only have the one machine, and I don't have a serious dump generator anyway. I started life on mainframes, all the way back in the 1980s. I haven't forgotten how useful a good PMD dump can be. Since this is a rather low-level issue, we both know that being able to get one is probably going to be the only way to locate the problem efficiently.

Since so many of us seem to be affected by this, and have been for some time, I would like to ask you to continue working on this. It can't be a configuration issue specific to any one machine (e.g., a driver conflict with some obscure utility that no one else would ever install). Too many of us have reported it. You really should be able to see this on any Windows XP box with IIS enabled. And, on one of your machines, you'll have access to a PMD.

I'm sure I'm not the first to run out of time for experimenting, and to give up and install the CGI interface. I realise IIS on any flavor of Windows doesn't compare to Apache on Unix. I realise Microsoft would like for us to use ASP when we develop for this environment. But, some of us may be stuck with IIS in a few specific situations, for various reasons, and aren't about to write ASP just for these boxes. I'm sure we would all appreciate your tracking this down and fixing it.

Thank you again, and good luck!

Cynthia

.