Xampp VC15 Apache Crashing

The last couple of days, I've had problems getting Apache running on my Windows 10 (Enterprise) 64-bit machine.

This is the version of Apache that is problematic. Apache/2.4.29 (Win32) OpenSSL/1.1.0g PHP/7.2.0

I've read the thread below and it seems to put forth a solution for port conflicts. XAMPP, Apache - Error: Apache shutdown unexpectedly

Changing the ports in httpd.conf and httpd-ssl.conf does resolve the problem but it complicates other things because I can no longer access local development installations with a simple "http://localhost/example" address.

It is not a port conflict for me. I know this because have multiple versions of Xampp installed on this machine, all of them using the default ports of 80 and 443. (For the record, I do not run these simultaneously.) I can start the older versions of Xampp without problems. I always launch Xampp with admin privileges. I have changed default Skype ports. I am not running a Virtual Host. I disabled IIS and World Wide Web Publishing services.

There was a Windows Cumulative Update installed between the dates that this was working reliably and now.

This is the Xampp error that appears a few seconds later, when I try to start Apache after installing the service.

12:29:08 PM  [Apache]   Error: Apache shutdown unexpectedly.
12:29:08 PM  [Apache]   This may be due to a blocked port, missing dependencies, 
12:29:08 PM  [Apache]   improper privileges, a crash, or a shutdown by another method.
12:29:08 PM  [Apache]   Press the Logs button to view error logs and check
12:29:08 PM  [Apache]   the Windows Event Viewer for more clues
12:29:08 PM  [Apache]   If you need more help, copy and post this
12:29:08 PM  [Apache]   entire log window on the forums

Here is related content from the error log examples from this morning when this failure occurs

[Mon Oct 22 10:29:42.713491 2018] [mpm_winnt:notice] [pid 9184:tid 908] AH00455: Apache/2.4.29 (Win32) OpenSSL/1.1.0g PHP/7.2.0 configured -- resuming normal operations
[Mon Oct 22 10:29:42.713491 2018] [mpm_winnt:notice] [pid 9184:tid 908] AH00456: Apache Lounge VC15 Server built: Nov  3 2017 10:30:36
[Mon Oct 22 10:29:42.713491 2018] [core:notice] [pid 9184:tid 908] AH00094: Command line: 'C:\\xampp-vc15\\apache\\bin\\httpd.exe -d C:/xampp-VC15/apache'
[Mon Oct 22 10:29:42.761465 2018] [mpm_winnt:notice] [pid 9184:tid 908] AH00418: Parent: Created child process 2872
[Mon Oct 22 10:29:46.004088 2018] [mpm_winnt:crit] [pid 9184:tid 908] AH00419: master_main: create child process failed. Exiting.

And, after fretting and rebooting a couple of times, here are the related log entries from a success, having changed nothing.

[Mon Oct 22 10:49:00.267967 2018] [mpm_winnt:notice] [pid 12960:tid 908] AH00455: Apache/2.4.29 (Win32) OpenSSL/1.1.0g PHP/7.2.0 configured -- resuming normal operations
[Mon Oct 22 10:49:00.283591 2018] [mpm_winnt:notice] [pid 12960:tid 908] AH00456: Apache Lounge VC15 Server built: Nov  3 2017 10:30:36
[Mon Oct 22 10:49:00.283591 2018] [core:notice] [pid 12960:tid 908] AH00094: Command line: 'C:\\xampp-vc15\\apache\\bin\\httpd.exe -d C:/xampp-VC15/apache'
[Mon Oct 22 10:49:00.337006 2018] [mpm_winnt:notice] [pid 12960:tid 908] AH00418: Parent: Created child process 13012
[Mon Oct 22 10:49:02.489373 2018] [mpm_winnt:notice] [pid 13012:tid 980] AH00354: Child: Starting 150 worker threads.

Here is the Windows Event Viewer information related to the failure of Apache

Faulting application name: httpd.exe, version: 2.4.29.0, time stamp: 0x59fc34e9
Faulting module name: ntdll.dll, version: 10.0.17134.254, time stamp: 0xbf2f8c99
Exception code: 0xc0000005
Fault offset: 0x00042154
Faulting process id: 0xb38
Faulting application start time: 0x01d46a2cd18bfad4
Faulting application path: C:\xampp-vc15\apache\bin\httpd.exe
Faulting module path: C:\WINDOWS\SYSTEM32\ntdll.dll
Report Id: 14413693-3372-4d50-93a6-f8933327f6ea
Faulting package full name: 
Faulting package-relative application ID: 

So, I'm stumped. I cannot explain, nor do I know how to troubleshoot, this intermittent problem. It's running without changing ports as I write this but, after a reboot, I suspect the problem will occur again so I'd sure appreciate some help.