EAP 6.4.0 windows service was installed using jboss-eap-native-utils-6.4.0. All the configurations are checked and confirmed to be correct. When stop window service is triggered, prunsrv.exe crashes with the following in the event viewer

Faulting application name: prunsrv.exe, version: 1.0.15.0, time stamp: 0x51824c56
Faulting module name: ntdll.dll, version: 6.3.9600.18233, time stamp: 0x56bb4ebb
Exception code: 0xc0000005
Fault offset: 0x0000000000035690
Faulting process id: 0xe78
Faulting application start time: 0x01d276a101aae086
Faulting application path: C:\jboss-eap-6.4.0\modules\system\layers\base\native\sbin\prunsrv.exe
Faulting module path: C:\Windows\SYSTEM32\ntdll.dll
Report Id: 16d5998c-e319-11e6-8136-005056b981af
Faulting package full name:
Faulting package-relative application ID:

Window's service dialog showing 1053 error. However, the logs for EAP showing the server is shutting down successfully. Using procmon, we have noticed even though java.exe is marked as process exiting, it does not exit, it remains at exiting state, when using jstack to take thread dump, we get "Access Denied".

In addition, Procmon shows
java.exe – Exit Status: 0
cmd.exe – Exit Status: 19660392
prunsrv.exe – Exit Status: -1073741819

This only happens on client site, they have two environments with the same issue. One of them is the production server.