I have an Intel i5 3210M CPU with an Intel HD 4000 graphics core. Since driver version 220.127.116.11.3621 (published ~May 2014) the game crashes shortly after starting CoDSP.exe (Singel Player) or CoDMP.exe (Multiplayer). So the game tries to start up and immediately crashes (black screen, Windows error sound, "hidden" error message):
"Microsoft Visual C++ Runtime Library
Program: .......(path)\Call of Duty\CoDSP.exe
A buffer overrun has been detected which has corrupted the program's internal state. The program cannot safely continue execution and must now be terminated."
Google told me that I'm not the only one with the same problem:
AMD & Nvidia had also this issue some time ago but they fixed it obviously in their drivers (e.g. Nvidia in v195.39, see changelog).
I tested a lot things which might help you to solve this problem:
1) All drivers since 18.104.22.168.3621 (inclusiv) cause this issue (also the latest 22.214.171.124.4176 ! )
2) With driver version 126.96.36.199.3412 (and older) the game works flawlessly and therefore doesn't crash.
---> There must have been a change between these two version which causes these crashes since this point in time.
3) There is a workaround for the problematic driver versions (see SteamCommunity): copying and changing the name of one of the two "game-lauchers" (CoDSP.exe/CoDMP.exe) into "mohaa.exe" solves the problem when a problematic driver version (188.8.131.52.3621 and above) is installed!!! This is quite crazy. Mohaa should stand for the computer game "Medal of Honor: Allied Assault". However when using a random name like abc.exe the game crashes again while starting...
---> It looks like renaming the .exe's to mohaa.exe forces the driver to use an internal driver profile (created by Intel for MoHAA), which is obviously also compatible with Call of Duty (1). Therefore this workaround makes it possible to use the latest Intel graphics driver(s) with Call of Duty 1. I know, this sounds quite crazy...but it is like that ;-)
Can you please have a look at this driver issue and change it in the next release? It looks like resolving this issue shouldn't be that complicated for Intel engineers.
PS: I use Windows 7 x64 Professional and the retail version of CoD1 without Steam... but Steam users are probably also bothered (see my links above).
Thank you very much!