Hello Joseph,
I started from top to bottom and so my post went correspondingly. However, you may want to start with section 3... as the most likely culprit may have been found.
--------- 1
Well, regarding the first suggestion to block the call to PHP, yes, given that your installation is working, even with the current problem, this makes it clear that Apache is working; then, the idea was to see if the "Faulting application name: httpd.exe" error message, which is related to Apache, was caused by some interaction with PHP or was caused by Apache itself, before having to do anything with PHP. So I wouldn't discard doing this, part of a debuggin process after all. While at it, having PHP blocked, I would place a basic index.html file at the document root, go to http://localhost and check the logs and the event viewer.
Also, you could try, with the web server stopped, running the command httpd -t to check about the configuration files, like so:
C:\path_to_apache\bin>httpd -t
Syntax OK
As shown, in my case, I get a "Syntax OK" result.
You may also try running the following:
httpd -S
which is equivalent to running httpd -D DUMP_RUN_CFG and httpd -D DUMP_VHOSTS.
There are other parameters that could be used to get some more info, like v, V, M. Anyway, this was just basic Apache checkup, so you might get some useful pointers... or not.
Just another question. Have you checked that there isn't another web server (e.g. IIS) running?
Assuming everythig OK, and back with PHP... how about placing a basic index.php at the document root, going to http://localhost and, once again, checking the logs and the event viewer. Maybe something like this:
<html>
<body>
<?php
echo "Hello World!";
phpinfo();
?>
</body>
</html>
--------- 2
Nothing else is displayed for the next 13 minutes
Whoa! What is it doing?
You missed placing the previous lines of the access.log. What was logged before that 11:26:22 line?
--------- 3
Parent: child process 2564 exited with status 3221225477 -- Restarting.
Now, that seems like a useful line, as here we have an Access violation that appeared after a 22 minute delay. Given the 13 minute lag you mentioned, I was wondering if this could be a memory related issue; this line may prove that this could actually be the reason, a faulty RAM chip... or quite a variety of other reasons. After all the tests and combinations you have gone through, the problem definitely points to some hardware problem or an OS permission (or otherwise) setting.
Please check the following two links:
1. http://compfreakstars.blogspot.mx/2011/11/0xc0000005-error-every-day-many.html
Speaking of viruses, please do consider that nowadays, this term is a very delimited or specific one; as I initially mentioned (step 4), please consider checking for a wider spectrum of possiblities, like malware, spyware and rootkits.
2. http://answers.microsoft.com/en-us/windows/forum/windows_7-windows_install/error-code-0xc0000005/fe04278b-c134-4e0c-94c9-a4fb11033e0d
--------- 4
If you are on a local machine, why are you using the https protocol (port 443)? If you have enabled SSL directives in your Apache httpd.conf configuration file, you should comment them (remember to restart the web server), at least while doing this debugging process. See that you don't have setting conflicts between all the configuration files involved (e.g. httpd.conf, httpd-vhosts.conf, httpd-ssl.conf).
--------- 5
Regarding the 150 worker threads... they are just a pool of spare threads:
https://httpd.apache.org/docs/2.4/mod/worker.html
--------- 6
Just as a final reference, currently I don't have a Win 7 machine, but last year I worked with one, Windows 7 64 bit (I guess it was a Home edition) and I had two or three Moodle installations where Moodle was always the same version (during some tests it could have changed) but the underlying web server environment was different:
** apache lounge, httpd-2.4.6-win32-VC10; php-5.4.17-Win32-VC9-x86.
** apache lounge, httpd-2.4.6-win64-VC11; php-5.5.1-Win32-VC11-x86.
I don't recall or have a file about the third one, but it must have been an older version, both for Apache (maybe a 2.2 version) and for PHP.
The database server was always MySQL 5.5.33: mysql-5.5.33-win32.
At any of my setups or tests I had the problem you are having.