Hi,
I installed the latest version of Wampserver on to a newly deployed Windows 2019 server (Amazon) including all runtime packages (also downloaded from wampserver) but when I try to run some scripts (php), Apache httpd service is crashing with this error:
Faulting application name: httpd.exe, version: 2.4.62.0, time stamp: 0x66d81b2d
Faulting module name: VCRUNTIME140.dll, version: 14.42.34433.0, time stamp: 0x98c03cc5
Exception code: 0xc0000005
Fault offset: 0x0000000000011504
Faulting process id: 0xd48
Faulting application start time: 0x01db76ef31fd56d7
Faulting application path: D:\wamp64\bin\apache\apache2.4.62.1\bin\httpd.exe
Faulting module path: C:\Windows\SYSTEM32\VCRUNTIME140.dll
Report Id: e043a631-70b1-4471-a899-9d308404de85
Faulting package full name:
Faulting package-relative application ID:
It's crashing a bit randomly, it does not matter which php scripts I run, sometimes it runs fine (50%), but it fails many times.
I also did the same installation on a Windows 2022 server (also on Amazon), but I get the same error.
Any idea what's causing this ...?
Thanks,
Jos.
I installed the latest version of Wampserver on to a newly deployed Windows 2019 server (Amazon) including all runtime packages (also downloaded from wampserver) but when I try to run some scripts (php), Apache httpd service is crashing with this error:
Faulting application name: httpd.exe, version: 2.4.62.0, time stamp: 0x66d81b2d
Faulting module name: VCRUNTIME140.dll, version: 14.42.34433.0, time stamp: 0x98c03cc5
Exception code: 0xc0000005
Fault offset: 0x0000000000011504
Faulting process id: 0xd48
Faulting application start time: 0x01db76ef31fd56d7
Faulting application path: D:\wamp64\bin\apache\apache2.4.62.1\bin\httpd.exe
Faulting module path: C:\Windows\SYSTEM32\VCRUNTIME140.dll
Report Id: e043a631-70b1-4471-a899-9d308404de85
Faulting package full name:
Faulting package-relative application ID:
It's crashing a bit randomly, it does not matter which php scripts I run, sometimes it runs fine (50%), but it fails many times.
I also did the same installation on a Windows 2022 server (also on Amazon), but I get the same error.
Any idea what's causing this ...?
Thanks,
Jos.