ntprime64.exe crashes
 

On Windows Server 2019, I'm trying to run ntprime64.exe version 30.8b15. It crashes without producing any output:


[code]
Faulting application name: ntprime64.exe, version: 0.0.0.0, time stamp: 0x6275744e
Faulting module name: libhwloc-15.dll, version: 0.0.0.0, time stamp: 0x617a58c9
Exception code: 0xc0000005
Fault offset: 0x00000000000099be
Faulting process id: 0x1030
Faulting application start time: 0x01d91355276f107e
Faulting application path: C:\prime99\ntprime64.exe
Faulting module path: C:\prime99\libhwloc-15.dll
Report Id: 736aaed3-b92d-436a-9676-f2218a877a75
Faulting package full name:
Faulting package-relative application ID:
[code]

Oddly, I have the same code running on a different Server 2019 machine without any problem. What could be the cause?

[QUOTE=mikeblas;620273]What could be the cause?[/QUOTE]

Winblows?

No idea. Does prime95 run OK?

Sorry if I'm stating the obvious.

What are the permissions on the c:\prime99 folder ?

Did you try to run Prime95 as suggested ? The readme file says one has to "install" it in the same folder and run it. (George perhaps the p95v308b15.win64.service.zip file also should contain the Prime95.exe file. An space saving alternative would be for it to contain only the ntprime64.exe and the readme.service.txt files.)

Then the readme.service.txt contains instructions and recommendations.

Since it is the failing module you could try a more recent version of libhwloc-15.dll : [url=https://www.open-mpi.org/software/hwloc/v2.7/]https://www.open-mpi.org/software/hwloc/v2.7/[/url]. But don't try version 2.8 : I tried it and it gives the error you describe.

Same issue here, still on a Server 2019 fully patched machine: I've tried to update ntprime64 from a former version (30.8.something) to 30.8b15 by running (as multiple times before, even on different machines) in a terminal with elevated privileges [CODE]ntprime64 -remove
ntprime64 -install[/CODE] and suddenly realized something was wrong since the install did not respond with the usual "NTPrimeService installed " (or something like that).

Trying to launch the service, both with elevated privileges and not, yields [CODE]NET START NTPrimeService
The service is not responding to the control function.
[/CODE] and puts [CODE]Log Name: Application
Source: Application Error
Date: <whatever>
Event ID: 1000
Task Category: (100)
Level: Error
Keywords: Classic
User: N/A
Computer: <...>
Description:
Faulting application name: ntprime64.exe, version: 0.0.0.0, time stamp: 0x6275744e
Faulting module name: libhwloc-15.dll, version: 0.0.0.0, time stamp: 0x617a58c9
Exception code: 0xc0000005
Fault offset: 0x00000000000099be
Faulting process id: 0x2874
Faulting application start time: 0x01d93583420d5a33
Faulting application path: C:\Program Files\Prime95\ntprime64.exe
Faulting module path: C:\Program Files\Prime95\libhwloc-15.dll[/CODE] into the event viewer.

Prime95 runs fine, from that same folder.

So far I've tried updating libhwloc-15.dll to the version suggested by S485122 (2.7.2), same result. As suggested by a number of Msoft posts related to "Event ID: 1000" or "Exception code: 0xc0000005", I've also run [CODE]DISM.exe /Online /Cleanup-image /Restorehealth
sfc /scannow[/CODE] again with elevated privileges, to check for corrupted items on this machine, and both commands return a clean situation. As a last resort, I've also eliminated all references to both "Prime95" and "NTPrimeService" from the registry, in order to attempt a new clean install... nope (afterwards restored from .reg files).

I'm running out of ideas... any Server 2019 pundit around, willing to help me sort this out?
TIA