You can try loading it in Windows Sandbox, Hyper-V, vmware or virtualbox.

DosFreak wrote on 2022-11-02, 20:13:

You can try loading it in Windows Sandbox, Hyper-V, vmware or virtualbox.

It crashed the same way in Sandbox as well.

You can check Event Viewer and see if any events are logged at the same time and see if they're related. Or try to use Process Explorer / Process Monitor to find out what the last thing it did before it crashed was.

ZellSF wrote on 2022-11-03, 10:45:

You can check Event Viewer and see if any events are logged at the same time and see if they're related. Or try to use Process Explorer / Process Monitor to find out what the last thing it did before it crashed was.

I used Process Monitor and saw some SMT related stuff going on before the exe crashed, so I thought that disabling all the cores in the BIOS minus four (making it a 4 core/8 thread system) would help. Did that and it started instantly, woot! So it seems like it WAS related to the CPU, but simply parking the e-cores through the game compatibility option in the BIOS wasn't enough.

Hell, even tested it by enabling all the P-Cores and only 8 E-Cores to emulate a 12900k, and it still worked! So, I was right about it being CPU related!

Hmm try leaving all cores enabled and try start /affinity 1 moha_setup.exe

DosFreak wrote on 2022-11-03, 22:45:

Hmm try leaving all cores enabled and try start /affinity 1 moha_setup.exe

That works as well.
It seems this problem starts at exactly 32 cores. Using different CPU affinity masks which result in 31 cores (such as having it launch just with all cores minus core 0/1/2/3/etc) lets it launch no problem.

*24 cores. Your CPU has 24 cores and 32 threads.

My CPU (AMD 5950x) has 32 threads too, but does not have this issue. Seems Intel really likes introducing weird compatibility issues lately? At least the fix is easy and not too harmful in terms of performance.

I wonder how older Intel 32 thread CPUs fare. I'm guessing better.

MrEWhite wrote on 2022-11-04, 00:39:

DosFreak wrote on 2022-11-03, 22:45:

Hmm try leaving all cores enabled and try start /affinity 1 moha_setup.exe

That works as well.
It seems this problem starts at exactly 32 cores. Using different CPU affinity masks which result in 31 cores (such as having it launch just with all cores minus core 0/1/2/3/etc) lets it launch no problem.

I know this thread is old but I thought replying to it was my best shot at getting a reply. I am having exactly the same issue as you were. I can use a shortcut to set the processor affinity and get MOHA_setup to launch but using the same method on the MOHA.exe just makes the EA app act like it is launching the game and then nothing. I wondered how you got past this step or do I just need to get a non ea app version?
This seems to be an issue with several old games with the i9-13900K and 32 cores.

Any help greatly appreciated.

RTX 4090 (drivers ver 555.99
i9-3900K 3.00
64Gb Ram
Windows 11 23H2

The Ms compatibility toolkit might have a flag that limits max reported cpus

https://learn.microsoft.com/en-us/windows/win … y-toolkit--act-

myne wrote on Today, 01:24:

The Ms compatibility toolkit might have a flag that limits max reported cpus

https://learn.microsoft.com/en-us/windows/win … y-toolkit--act-

This also works. Used this to fix some older Ubisoft games (Far Cry 2 & 3 and Rocksmith 2014 Remastered) that wouldn't launch on a 13900KS by just enabling the "ProcessorCountLieForHybridCPU" compatibility fix. It also works for MOHA no problem.