master131's Ghosts RAM/GPU Fix v1.2
This is a simple fix to bypass the RAM limitation which forces users to have 6GB of RAM available.
This RAM fix does not require replacing any executables. This can also fix the "EXE_ERR_COULDNT_CONFIGURE" error, although it hasn't been 100% tested yet.
Instructions:
- Extract both files into the game's folder (inside the Steam/steamapps/call of duty ghosts directory).
- Double-click on
Ghosts RAM Fix.exe.
- Enable the GPU fix if required and then choose to start SP or MP. (press a number and then press Enter)
- A "Run in Safe Mode" window will appear, click
No and enjoy!
- (optional) Make a shortcut on your desktop to make it easier to start the game.
Instructions (other method, easier but might not work):
- Extract both files anywhere and double-click on
Ghosts RAM Fix.exe
- Enable the GPU fix if required and then choose to start SP or MP. (press a number and then press Enter)
- Hopefully it will work, otherwise, use the previous method.
If you get any failure messages, please try running it again as an administrator.
What's new:
Code:
Changes since v1.2 (11th November 2013):
- Fixed bug where K32EnumProcesses was reported missing on some computers
- Added an experimental GPU fix for those with the "EXE_ERR_COULDNT_CONFIGURE" message.
- Minor stability fix to prevent race condition.
Changes since v1.1 (9th November 2013):
- Added minor bug fix to ensure fake RAM is sent to the executable twice
- Removed Visual C++ 2012 runtime dependency
- Stopped the RAM fix from generating a safe-mode launch file if it was not placed in the game's directory.
Notes:
The RAM fix has 2 command line options if you wish to start a mode directly. They are: "-sp" and "-mp" (without the quotes). Also, the DLL (ghosts-ram-fix.dll) is loaded into the game temporarily. As soon as the main window of the game appears, it is unloaded to prevent false detection from the game's anti-cheat.
Known problems:
- For some people, MP gets stuck at "Connecting to online services...". If you used the Steam006 RAM Fix or any other RAM fix that replaced files (eg. steam_api64.dll, ValveAPI64.dll, etc), please Verify your game cache as described below:
1. Load Steam
2. From the Library section, right-click on the game (Call of Duty: Ghosts - Multiplayer) and select Properties from the menu.
3. Select the Local files tab and click the Verify integrity of game cache... button.
4. Steam will verify the game's files - this process may take several minutes.
5. Once the process is completed, the Check Window will automatically exit.
- The "experimental" GPU fix crashes the game. Well, it is called experimental for a reason, I don't have a card which produces the error so I haven't exactly tested it. Doesn't seem to be working with Intel HD4000 but do try and tell me if it does work.
These RAM fixes prevent the game from communicating to the game's servers via the Steam API.
Have you tested this?
Yes, I originally had 8GB of RAM installed on my computer but removed one of the sticks in order to develop this RAM fix.
Preparing to free RAM fix from memory?
This just means that it's waiting for the game's main window to appear to confirm the fix worked. Once it knows it worked, it will unload the DLL and close.
Do not close the window manually.
The RAM fix just crashes after I choose an option?
Not exactly sure why this happens (only one person I know was affected by this), try changing the compatibility settings to Windows 7. (right-click > Properties > Compatibility).
What is the experimental GPU fix?
This is an experimental fix to allow those with the "EXE_ERR_COULDNT_CONFIGURE" message to play the game. I haven't thoroughly tested it because I personally don't get the error but it seems like it should work.
Requirements:
You must have the Steam version of the game installed (all versions current and future will work), cracked versions are not supported.
Credits:
Marton Anka/Matt Conover - MHook/tDisasm
Virus Scans:
https://www.virustotal.com/en/file/0...573ae/analysis
Ghosts RAM-GPU Fix v1.2 by master131.rar - Jotti's malware scan
Thanks to @
KiDfresh510 for convincing me to make this.