Already registered? Login
Home > TechZone > Forums > Metadot 
Message details Author
Subject: Re: Parent: child process exited with status 3221225725
Posted On: Mar 9, 2015, 7:11:35 PM
User photograph ZH (ZH ZH)
Itīs an old post, but as i just ran into the same problem, i like to post my solution here:

I got the same problem using Windows Server 2003 and installing Apache 2.4.

I always got this error message and Apache is always shutting down and restarting multiple times per second when i try to start it with "httpd -k start":

[Mon Mar 09 19:14:14.031250 2015] [mpm_winnt:notice] [pid 888:tid 416] AH00455: Apache/2.4.12 (Win32) configured -- resuming normal operations
[Mon Mar 09 19:14:14.031250 2015] [mpm_winnt:notice] [pid 888:tid 416] AH00456: Apache Lounge VC9 Server built: Jan 30 2015 11:29:54
[Mon Mar 09 19:14:14.031250 2015] [core:notice] [pid 888:tid 416] AH00094: Command line: 'D:\\Apache24\\bin\\httpd.exe -d D:/Apache24'
[Mon Mar 09 19:14:14.031250 2015] [mpm_winnt:notice] [pid 888:tid 416] AH00418: Parent: Created child process 1692
[Mon Mar 09 19:14:14.609375 2015] [mpm_winnt:notice] [pid 1692:tid 1684] AH00354: Child: Starting 64 worker threads.
[Mon Mar 09 19:14:16.234375 2015] [mpm_winnt:notice] [pid 888:tid 416] AH00428: Parent: child process 1692 exited with status 3221225725 -- Restarting.

A long search (a ful day!) then finally got me onto the right trace:

Itīs the "nVidia Forceware Network Access Manager" that is causing this problem (old Supermicro H8DAE-2 Opteron Board that runs an nVidia MCP55 Pro Chipset), and that causes Apache to crash (the C++ redistributable package cant open network sockets and crashes). I never believed a mainboard driver that I installed in 2007 (8 years ago!) now causes this problem in 2015. In some forums you can read that this error number 3221225725 can be solved by using a "ThreadSize 8888888", but thatīs a totally different story.

If you receive this error message "exited with status 3221225725" on your system, you can easily verify it by looking into the Windows Event Viewer / Application.

Each Apache shutdown leaves an error message there. In my case, it shows:

"Faulting application httpd.exe, version, faulting module nvappfilter.dll, version, fault address 0x0000a467.", where nvappfilter.dll is the NVidia Network Access Manager i installed 8 years ago.

Backup your system before trying to remove this driver, it can cause severe damage (you may lose all internet connectivity or it may mess around with other networking stuff, network bridges, SSH tunnels, firewall and so on)

See here how to do it:

In my case, I just did an uninstall of the "NVIDIA ForceWare Network Access Manager" in the Add/Remove Programs.

Apache finally works after I removed the Network Access Manager on my Windows Server 2003 (same should apply to Windows XP)!
Subscribe to this discussion Return to discussion

Messages in this thread: < Previous thread Next thread >
Subject Author Date
CallmeFriend (Cesar Vallenilla)
User photograph
2012-03-13 14:17:18
User photograph
2015-03-09 19:11:35