[SOLVED] Call of Duty 1 [Non-Steam CD] not working on Windows 10 - RS3 Fall Creators Update

[perropequeño2222]

I've just installed the non-steam edition (disc) of COD onto my PC (running Windows 10 RS3 Fall Creators Update). I opened CoD Singleplayer and nothing happened. I opened CoD Multiplayer and I saw a small black box in the middle of the screen that had the logo and said "LOADING..." below it. Then I saw an error that said "CoDMP.exe has stopped working"

PLS HELP!
EDIT - 17/12/2017: I've installed a Windows XP VM in VMware Workstation Player, and it works flawlessly. CoD is currently installing. I will update when it works or not.

How I solved this

I got a CD-less fixed EXE. This is NOT pirating because it only came with the game EXE, and other files are required. These other files can only be aqquired from getting the game on CD or buying it from Steam.

[Melody]

Please check your Event Log, in order to do so:

• Open the Event Viewer: press Windows Key + R Key together, type in "eventvwr", without quotes, and press Enter.
  
• In the "Application" category, search for "Error" events that refer to the game executable and post the content here.

[perropequeño2222]

Originally posted by Melody~:

Please check your Event Log, in order to do so:

• Open the Event Viewer: press Windows Key + R Key together, type in "eventvwr", without quotes, and press Enter.
  
• In the "Application" category, search for "Error" events that refer to the game executable and post the content here.

Ok, I got it:

Faulting application name: CoDMP.exe, version: 0.0.0.0, time stamp: 0x3f84a964
Faulting module name: CoDMP.exe, version: 0.0.0.0, time stamp: 0x3f84a964
Exception code: 0xc0000005
Fault offset: 0x0004b1aa
Faulting process ID: 0x3cc4
Faulting application start time: 0x01d376af2137a07e
Faulting application path: C:\PROGRA~2\CALLOF~1\CoDMP.exe
Faulting module path: C:\PROGRA~2\CALLOF~1\CoDMP.exe
Report ID: 0a93659b-5803-4957-92e4-20af7bd9cea3
Faulting package full name: 
Faulting package-relative application ID: 

[Melody]

Originally posted by FestiveDiseGames:

Originally posted by Melody~:

Please check your Event Log, in order to do so:

• Open the Event Viewer: press Windows Key + R Key together, type in "eventvwr", without quotes, and press Enter.
  
• In the "Application" category, search for "Error" events that refer to the game executable and post the content here.

Ok, I got it:

Faulting application name: CoDMP.exe, version: 0.0.0.0, time stamp: 0x3f84a964
Faulting module name: CoDMP.exe, version: 0.0.0.0, time stamp: 0x3f84a964
Exception code: 0xc0000005
Fault offset: 0x0004b1aa
Faulting process ID: 0x3cc4
Faulting application start time: 0x01d376af2137a07e
Faulting application path: C:\PROGRA~2\CALLOF~1\CoDMP.exe
Faulting module path: C:\PROGRA~2\CALLOF~1\CoDMP.exe
Report ID: 0a93659b-5803-4957-92e4-20af7bd9cea3
Faulting package full name: 
Faulting package-relative application ID: 

Looks like an access violation problem caused by the game itself (not a driver issue or caused by external modules). An undocumented workaround for old games is to rename their executables to "mohaa". Can you try renaming the executable to "mohaa" (with .exe extension of course) and try running the game again?

[perropequeño2222]

Originally posted by Melody~:

Originally posted by FestiveDiseGames:

Ok, I got it:

Faulting application name: CoDMP.exe, version: 0.0.0.0, time stamp: 0x3f84a964
Faulting module name: CoDMP.exe, version: 0.0.0.0, time stamp: 0x3f84a964
Exception code: 0xc0000005
Fault offset: 0x0004b1aa
Faulting process ID: 0x3cc4
Faulting application start time: 0x01d376af2137a07e
Faulting application path: C:\PROGRA~2\CALLOF~1\CoDMP.exe
Faulting module path: C:\PROGRA~2\CALLOF~1\CoDMP.exe
Report ID: 0a93659b-5803-4957-92e4-20af7bd9cea3
Faulting package full name: 
Faulting package-relative application ID: 

Looks like an access violation problem caused by the game itself (not a driver issue or caused by external modules). An undocumented workaround for old games is to rename their executables to "mohaa". Can you try renaming the executable to "mohaa" (with .exe extension of course) and try running the game again?

Okay

[perropequeño2222]

Originally posted by FestiveDiseGames:

Originally posted by Melody~:

Looks like an access violation problem caused by the game itself (not a driver issue or caused by external modules). An undocumented workaround for old games is to rename their executables to "mohaa". Can you try renaming the executable to "mohaa" (with .exe extension of course) and try running the game again?

Okay

It's not working.

[Melody]

Originally posted by FestiveDiseGames:

Originally posted by FestiveDiseGames:

Okay

It's not working.

Go to "Add/Remove Windows Features" and enable Legacy Components.

• Press Windows Key + R Key, type in "appwiz.cpl", without quotes, and press Enter.
  
• Go to "Add/Remove Windows Features".
  
• Enable "Legacy Features" and click OK.

Check if it works.

[perropequeño2222]

Originally posted by Melody~:

Originally posted by FestiveDiseGames:

It's not working.

Go to "Add/Remove Windows Features" and enable Legacy Components.

• Press Windows Key + R Key, type in "appwiz.cpl", without quotes, and press Enter.
  
• Go to "Add/Remove Windows Features".
  
• Enable "Legacy Features" and click OK.

Check if it works.

For me, it seems to say "Legacy Components" and is already checked.

[perropequeño2222]

Originally posted by FestiveDiseGames:

Originally posted by Melody~:

Go to "Add/Remove Windows Features" and enable Legacy Components.

• Press Windows Key + R Key, type in "appwiz.cpl", without quotes, and press Enter.
  
• Go to "Add/Remove Windows Features".
  
• Enable "Legacy Features" and click OK.

Check if it works.

For me, it seems to say "Legacy Components" and is already checked.

Tried to boot up a VM, this happened.

The virtual machine 'Windows XP' has terminated unexpectedly during startup with exit code 1 (0x1). More details may be available in 'C:\Users\SABIA\VirtualBox VMs\Windows XP\Logs\VBoxHardening.log'.


Result Code: 
E_FAIL (0x80004005)
Component: 
MachineWrap
Interface: 
IMachine {b2547866-a0a1-4391-8b86-6952d82efaa0}

[Melody]

Originally posted by FestiveDiseGames:

Originally posted by FestiveDiseGames:

For me, it seems to say "Legacy Components" and is already checked.

Tried to boot up a VM, this happened.

The virtual machine 'Windows XP' has terminated unexpectedly during startup with exit code 1 (0x1). More details may be available in 'C:\Users\SABIA\VirtualBox VMs\Windows XP\Logs\VBoxHardening.log'.


Result Code: 
E_FAIL (0x80004005)
Component: 
MachineWrap
Interface: 
IMachine {b2547866-a0a1-4391-8b86-6952d82efaa0}

You're gonna need VMware Play in order to get Direct3D support. Games won't work properly with VirtualBox.

[Melody]

After searching on Google I found the reason of the issue.
The solution is simple but not acceptable in Steam Forums, so I'll tell you in private.
The other solution is creating a Virtual Machine and playing the game there.