Sorry, but your problem does not imply a bug in PHP itself.  For a
list of more appropriate places to ask for help using PHP, please
visit http://www.php.net/support.php as this bug system is not the
appropriate forum for asking support questions. 

Thank you for your interest in PHP.

.

We just upgraded from php 4.3.4 to 4.3.7 and are having the same problem under Windows 2000, IIS 5.0, MS SQL Server 2000.

A reset of the iis solves the problem just temporarliy.

We have the same problem with our IIS 5/Win2k/MySQL. This is a 4.3.7 regression that needs to be addressed. I'm moving us back to 4.3.6.

I get the same problem.
I'm using win2k3/iis6
upgrade from php 4.3.4 to 4.3.7
error show at the end of php pages.

upgraded from 4.3.6 to 4.3.7,

platform: win2k server/IIS (ISAPI)/Mysql

Seeing this "PHP Access Violation" error now intermittently. Didn't use to get his problem. Might go back to 4.3.6 for the time being.

Same here. I've always gotten this error (PHP has encountered an Access Violation at xxxxxxx) when running PHP 4.3.x (any version and for both CGI and ISAPI) on Windows 2000 or Windows 2003 that connects to MySQL. I have other sites on same machines connecting to MSSQL that works fine. In Windows 2003 I've isolated the servers in different applications pools (to be able to restart them seperately) and it's only sites using MySQL where this error occur. It can be a few hours between but sometimes it's days.

For example on same machine I've set up two phpbb (http://www.phpbb.com) forums, one using a MySQL 4.0.16 database and the other a MSSQL 2000 SP3 database. Both sites in different application pools. Rest of the config is identical (Win 2003, PHP 4.3.5, ISAPI) and it's only the forum site using MySQL that will get this error every couple of days.

I've read on other posts that it could be related to pconnect() or that PHP gets "unloaded" but I don't know what that is supposed to mean.

Seems to be an issue when you combine IIS,PHP,MySQL on Windows. I've never seen a final soultion for this.

We have same problem now on our webserver.
Win2003/MySQL and PHP 4.3.7

http://www.techconnect.nl/info.php

the info.... problem exists sometimes (but not always)
on: www.tcmagazine.net, www.tcdsl.nl, www.nk-halo.nl and www.gameconnect.nl

Same problem here since upgrade to 4.3.7 ... I'm moving back to 4.3.6

PHP5 RC3, 
windows xp pro IIS 5.1

Access Violation: every time at the same memory address, on every page

same problem on WIN 2000

Is someone looking into this? It's obviously a bug in PHP itself since it's been confirmed on several different sites where and upgrade from 4.3.6 or older to 4.3.7 is giving this error ( and also is in the 5.0 series according to some of the comments ). 

It also seems to be related to using MySQL; is this limited to PHP's builtin MySQL support or does it also encompass the PEAR DB module?

This is going to hurt PHP 5 adoption on Windows if this isn't taken care of.

I can confirm that with PHP5 running as ISAPI on IIS 6 on Windows Server 2003 SE the access violation "bug" if indeed that's what it is, is present:

"PHP has encountered an Access Violation at 016F73DD"

appears at the end of every page.

This bug is still in PHP 5.0.0 final build too!
I think it was not good idea to release final version with this actual bug :(

I recently installed a 4.x version of php on IIS6 / Windows 2003 without problems. Today I upgraded to PHP 5 Final, and started having the same errors mentioned above. I did some of my own troubleshooting, after exhausting all of my searches for fixes. I used the php.ini-recommended and it seemed to work fine. No Access errors. However the images generated on the phpionfo page were not working as intended. I experimented with a few different settings for 'output_buffering =' , and finally settled on 1024 which seemed to make the phpinfo page work as intended.

I am not absilutely sure that this is the perfect method for fixing whatever is causing this error, but I would be interested to see others try this method and let me (and others) know if you encounter any issues with test code. I do not have any production php to try right now to verify that everything will work ok, but personally I find it daunting that I would have to make so many security changes and buffer size changes to get this to work. 4.x PHP worked as-is with little editing of the php.ini.

For troubleshooting purposes, I am using the PHP 5.0 Final release, with no extra modules.

It seems fixed in last CVS :)
I get last build at http://snaps.php.net/ and there are no more "Access violation" errors :)