Buffer overrun detected! when starting Call of Duty (1.0)

[MMust7]

Hello Intel,

I have an Intel i5 3210M CPU with an Intel HD 4000 graphics core. Since driver version 15.33.22.64.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:

http://forums.steampowered.com/forums/showthread.php?t=3238163 Call of Duty 1 Buffer Overrun Detected - Steam Users' Forums

http://steamcommunity.com/app/2620/discussions/0/558756256323756242/?insideModal=1# c540743032455384127 Buffer Overrun Error :: Call of Duty General Discussions

http://answers.microsoft.com/en-us/windows/forum/windows_other-gaming/microsoft-visual-c-runtime-library-buffer-overrun/bb1cb707-622d-4fc6-b46d-c2bb4dec6207 Microsoft Visual C++ Runtime Library: Buffer Overrun - Microsoft Community

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 15.33.22.64.3621 (inclusiv) cause this issue (also the latest 15.33.35.64.4176 ! )

2) With driver version 15.33.14.64.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 (http://steamcommunity.com/app/2620/discussions/0/558756256323756242/?insideModal=1# c540743032455384127 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 (15.33.22.64.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!

[VHrob]

I have also a problem. Lenovo G50-30 ( Intel Pentium N3530, HD Graphics Bay trail) .Waiting for solving this problem. ! !

[SMarí]

Guys,

I managed to workaround this issue. I uninstalled the lastest version of the drivers, Windows took the previous installed (as I have a MacBook Pro with Boot Camp, the drivers that Apple provides) and that solved it.

I believe, then, you could try at first to install a previous version of the drivers as fix until Intel update newer ones with a fix for us.

[GGehr]

Hallo pustekuchen, habe leider dasselbe Problem.

Hello pustekuchen, unfortunately i've the same problem.

Hello Intel!

I've still the same problem with the newest driver for Windows 10 (Version: 15.33.38.64.4252 (Latest))

I've a Lenovo Thinkpad Helix (N4B49GE) with a i5-3337U and Intel HD 4000 graphics.

PS.: Something different, i googled the i5-3337U and i found this site: http://ark.intel.com/de/products/72055/Intel-Core-i5-3337U-Processor-3M-Cache-up-to-2_70-GHz ARK | Intel® Core™ i5-3337U Processor (3M Cache, up to 2.70 GHz)

but when i click on "Softwaredownloads >" i get directed to the wrong driver: https://downloadcenter.intel.com/product/81496/Intel-HD-Graphics-4600-for-4th-Generation-Intel-Core-Processors Intel® Download Center

Greetings Ray

[CMaur]

Same problem here, Windows 10 64 bits with drivers

Please fix this, i want play CoD 1, and KOTOR 1, this have graphics glitches activating some efects and low fps...

Sorry for my english

[Ricardo_G_Intel1]

The feature request was passed to engineering team and if there are news, they will post them there.

[JP10]

HaHa..we can simply fix this problem....

Just rename the CoDMP.exe to MOHAA.exe

You are done....TRY it working 100%

[Allan_J_Intel1]

Thanks for the workaround.

Allan.

[mnyhe]

That is not true at all.

That only solves the problem if you have the retail version of the game. Not the Steam-version

Now, to you Intel

I am amazed how bad your customer service is. This is a problem within your software, and I'm guessing it would take only minutes for you guys to fix this.

How hard can it really be?

Put it in gear, and do something about it!

And please, don't tell me that the feature request was passed to engineering team and if there are news, they will post them there.

[mmav]

"Just rename the CoDMP.exe to MOHAA.exe"

it actually Worked for retail version!!!!! LOL

I can't believe how simple that was!!

Also gests COD working under WINDOWS 10, just rename the file.. that's it!

thanks Junaidkuttur

[CYoun12]

this issue still isn't fixed...

Intel(R) Core(TM) i5-4278U CPU @ 2.60GHZ

Intel(R) Iris(TM) Graphics 5100

Windows 10 with Steam CoD

[THiek]

I have just (4th of Jan 2016) installed Steam and CoD 1 and I have the same error. My computer is:

Intel i5-3437U

Intel HD Graphics 4000 (Driver version 10.18.10.4226, Date: 25.5.2015)

Windows 7 64-bit

Please Intel support, fix this, this is a minor issue for you, but a major issue for Intel/CoD fans and users! Thanks!

[kterr]

This problem is not resolved.

Attempt to launch Call of Duty with wine gives: Buffer overrun detected!

System: Host: AHC-DESK2 Kernel: 3.19.0-32-generic x86_64 (64 bit) Desktop: Cinnamon 2.8.8

Distro: Linux Mint 17.3 Rosa

Machine: System: Hewlett-Packard product: HP Compaq 8200 Elite SFF PC

Mobo: Hewlett-Packard model: 1495 Bios: Hewlett-Packard v: J01 v02.06 date: 06/09/2011

CPU: Quad core Intel Core i5-2400 (-MCP-) speed/max: 1612/3400 MHz

Graphics: Card: Intel 2nd Generation Core Processor Family Integrated Graphics Controller

Display Server: X.Org 1.17.1 drivers: intel (unloaded: fbdev,vesa) Resolution: 1920x1080@60.0hz

GLX Renderer: Mesa DRI Intel Sandybridge Desktop GLX Version: 3.0 Mesa 10.5.9

Network: Card: Intel 82579LM Gigabit Network Connection driver: e1000e

Drives: HDD Total Size: 2999.9GB (13.6% used)

Info: Processes: 194 Uptime: 4:00 Memory: 1310.3/15936.2MB Client: Shell (bash) inxi: 2.2.28

[Allan_J_Intel1]

keithterrill

Have you tried checking through Linux communities?

https://01.org/community https://01.org/community

Allan.

[kterr]

That is how I ended up on this thread.

thank you

keith

[Allan_J_Intel1]

Is your game compatible with the version of the Linux distribution you are currently running on the computer?

Allan.

[kterr]

As far as I know, the answer is yes, CoD1 runs on Linux Mint.... and runs on the flavor I have installed. Interesting comments from those that have it running is that it runs better than on their Windows systems.

Not that it is Apples to Apples comparison, but I have successfully installed and run the following programs that I used to run on my Windows 7 system:

e-Sword

SimCity 4

Chessmaster Grandmaster Edition

Call of Duty installs, both disks. But, when I launch it with wine it gives this error immediately. I have no idea if it is software, hardware, or some combination. I do know that it runs on my older AMD Windows 7 system, it runs on other Linux Mint systems... but on this HP I5 box it won't run.

[Allan_J_Intel1]

Please bear in mind that Intel provides limited support for Linux operating system. You will need to keep on checking at https://01.org/community Community | 01.org for available drivers for your graphics controller.

Allan.

[Bryce__Intel]

Hi all,

I've received notice this is resolved in 15.40 drivers though for older platforms fix is still in progress, we tried to port the fix back and it was not compatible. Not as simple to fix as I had hoped. Just wanted to let you know where we're at and let you know there's progress though still working through it.