Keep Server Online
If you find the Apache Lounge, the downloads and overall help useful, please express your satisfaction with a donation.
or
A donation makes a contribution towards the costs, the time and effort that's going in this site and building.
Thank You! Steffen
Your donations will help to keep this site alive and well, and continuing building binaries. Apache Lounge is not sponsored.
| |
|
Topic: Apache 2.4.66 VS18 httpd crashes PHP 8.5.1 |
Page Previous 1, 2 |
| Author |
|
danielruf
Joined: 07 Jan 2026 Posts: 6
|
Posted: Fri 13 Feb '26 8:52 Post subject: |
|
|
Maybe my information was incomplete, but I did not just start and stop but also thouroughly tested my application.
I will keep an eye on my setup and come back here, if I see the same crashes.
To me it sounds like some memory leak or something else that takes some time to occur.
So far I did not see further reports, so at least it seems to be some isolated issue (at least this is my current assumption).
Not sure if any httpd.conf related issue is relevant, maybe the Windows error logging has more details. |
|
| Back to top |
|
axel.kam

Joined: 11 Jul 2023 Posts: 11
|
Posted: Fri 13 Feb '26 10:33 Post subject: |
|
|
httpd 2.4.66 ( Apache Lounge VS18 erver built: Jan 30 2026 15:51:08 ) crash once or twice per day, in log: exited with status 3221226356, or sometimes 255.
in windows log: httpd.exe and ntdll.dll
I've been experimenting for two weeks now, httpd still crashed periodicaly
not sure, that problem with php module or fcgid |
|
| Back to top |
|
RikasMalinka
Joined: 07 Jan 2026 Posts: 6 Location: Poland
|
|
| Back to top |
|
danielruf
Joined: 07 Jan 2026 Posts: 6
|
|
| Back to top |
|
RikasMalinka
Joined: 07 Jan 2026 Posts: 6 Location: Poland
|
Posted: Sat 14 Feb '26 15:56 Post subject: |
|
|
FAIL
| Quote: |
Nazwa aplikacji powodującej błąd: httpd.exe, wersja: 2.4.66.0, sygnatura czasowa: 0x697cc5aa
Nazwa modułu powodującego błąd: ntdll.dll, wersja: 10.0.17763.8276, sygnatura czasowa: 0x6960ed42
Kod wyjątku: 0xc0000374
Przesunięcie błędu: 0x00000000000fb499
Identyfikator procesu powodującego błąd: 0x4d80
Godzina uruchomienia aplikacji powodującej błąd: 0x01dc9ce54b985fa1
Ścieżka aplikacji powodującej błąd: D:\xampp\apache\bin\httpd.exe
Ścieżka modułu powodującego błąd: C:\Windows\SYSTEM32\ntdll.dll
Identyfikator raportu: 86c167b9-e22b-4421-a88b-aed49ca78d61
Pełna nazwa pakietu powodującego błąd:
Identyfikator aplikacji względem pakietu powodującego błąd:
Pakiet błędów 1695703728024279616, typ 4
Nazwa zdarzenia: APPCRASH
Odpowiedź: Niedostępny
Identyfikator pliku CAB: 0
Podpis problemu:
P1: httpd.exe
P2: 2.4.66.0
P3: 697cc5aa
P4: StackHash_effe
P5: 10.0.17763.8276
P6: 6960ed42
P7: c0000374
P8: PCH_0D_FROM_ntdll+0x00000000000A0E24
P9:
P10:
|
|
|
| Back to top |
|
Crafted

Joined: 04 Feb 2026 Posts: 9
|
Posted: Sat 14 Feb '26 17:05 Post subject: |
|
|
| that was to be expected, if you really wanna try something you probably gonna recompile the whole package most likely and replace there openssl, however I just gived up, just waiting for a proper version. |
|
| Back to top |
|
admin Site Admin

Joined: 15 Oct 2005 Posts: 723
|
Posted: Sun 15 Feb '26 14:45 Post subject: |
|
|
| What about other versions of PHP ? |
|
| Back to top |
|
tangent Moderator
Joined: 16 Aug 2020 Posts: 419 Location: UK
|
Posted: Sun 15 Feb '26 20:52 Post subject: |
|
|
Re this "heap" problem, and who's responsible for the HTTPD process crashing; OpenSSL, PHP, other?
RikasMalinka's initial post shows an event log entry with ntdll.dll as the culprit, but we know that kernel based DLL is at the end of the line. A stack trace of the calling processes would help here, so a dump of the process at crash time is required.
In the absence of complex debugging tools, I'd consider using SysInternals ProcDump and MS WinDbg utilities to try and localise which module is to blame.
If possible, starting with ProcDump (https://download.sysinternals.com/files/Procdump.zip), configure it to create a dump file. In an administrator command window, enable ProcDump and then set it up to capture an unhandled exception from the running httpd.exe process.
| Code: | C:\>procdump -i
C:\>procdump -e -ma httpd.exe
|
Sit back and wait for the crash...
Once you've got your dump file (default location is C:\), uninstall ProcDump.
Next, install MS WinDbg
| Code: | C:\>winget install Microsoft.WinDbg
|
Run WinDbg and open the dump file, and then within WinDbg run the command:
Even without module symbols, the resulting raw stacktrace will hopefully show which module triggered the problem (addresses translate to module names).
Unfortunately build symbols would be needed to find the precise function call within a given module. |
|
| Back to top |
|
|
|
|
|
|