|  support |  documentation |  report a bug |  advanced search |  search howto |  statistics |  random bug |  login
Bug #28898 PHP has encountered an Access Violation at 01350AFD
Submitted: 2004-06-23 21:13 UTC Modified: 2004-07-06 15:38 UTC
Avg. Score:4.7 ± 0.6
Reproduced:11 of 11 (100.0%)
Same Version:11 (100.0%)
Same OS:7 (63.6%)
From: sam at freepeers dot com Assigned:
Status: Not a bug Package: IIS related
PHP Version: 4.3.7 OS: Windows 2000
Private report: No CVE-ID: None
 [2004-06-23 21:13 UTC] sam at freepeers dot com
When loading a webpage, it occasionally shows "PHP has encountered an Access Violation at 01350AFD" within the body of the page.

Windows 2000 Advanced Server cluster
PHP 4.3.7
Running as ISAPI module 

Server Info:

Display errors is turned off on this server, and errors are being logged to the Event Log.  The main problem here is that an error is being DISPLAYED to the end user.  It should be going to the Event Log instead.

I am reporting this because some other similar bug reports have been closed because the user did not provide enough information.  I am willing to provide plenty of information if I can help to get this bug solved.

Reproduce code:

Expected result:
Observe at

(hit refresh many times to get the error)

The expected result is a normal page of text and graphics.  The actual result is that embedded within the text is an error message "PHP has encountered an Access Violation at 01350AFD" , along with the expected output.


Add a Patch

Pull Requests

Add a Pull Request


AllCommentsChangesGit/SVN commitsRelated reports
 [2004-06-28 10:22 UTC] miho at centrum dot cz
Same problem here.

Windows 2003
PHP 4.3.7

SMP machine (Dual Xeon, HT disabled)

Application: phpBB. Problem occurs mainly on first loaded page (user not logged in, cookie authentization). Perhaps session related problem.
 [2004-06-28 16:10 UTC] sam at freepeers dot com
I have stopped using ISAPI for now, this seems to prevent the bug from appearing.
 [2004-06-29 17:59 UTC]
What extensions are you loading into your PHP? 
 [2004-06-30 03:35 UTC] louis at spamisbad dot steelbytes dot com dot veryevil
> What extensions are you loading into your PHP? 

Hi, I've got very similar bug (28954)

I load the following extensions in the php.ini
 [2004-06-30 15:50 UTC] sam at freepeers dot com
I am not loading any extensions.
 [2004-07-02 13:26 UTC] miho at centrum dot cz
Downgrading to 4.3.6 solved that problem for me.

 [2004-07-03 21:05 UTC] renato at ostorero dot it
Same problem here, downgrade to 4.3.6 or 4.3.5 doesn't solve it, the only way is to set memory recycling in IIS 6 to very low level such 20 mb for max used memory and 30 for max virtual memory.
This way of work permits to recycle often the working processes and limit PHP access violation but in some cases cause event id 1013 "exceed of time during shut down".

Windows 2003 Enterprise

PHP 4.3.5 / 4.3.6 / 4.3.7


 [2004-07-06 15:38 UTC]
The isapi module is unstable at it's best anyway, use CGI if you need stable environment. (or rather, install Apache..)

 [2004-07-08 10:11 UTC] renato at ostorero dot it
 [2004-07-22 19:33 UTC] bugs-php-net at remember dot dk
I have the same problem with
Windows 2000 Server
IIS5 PHP 4.3.7 & 4.3.8
Running as ISAPI module

PHP info here:

If i downgrade to PHP 4.3.6 it works fine again, the only change i have made in php.ini from 4.3.6 to 4.3.7 / 4.3.8 is that i have changed from mysql.trace_mode = On to Off

I have this problem on multiple servers.

The php4isapi.dll module has been quite stabe until PHP 4.3.7
PHP Copyright © 2001-2024 The PHP Group
All rights reserved.
Last updated: Mon May 20 20:01:32 2024 UTC