[FIXED] FEAR 3 Crash to Desktop (CTD), Freezes, MSVCR80.dll error, XP/Vista/7 issues, Graphics, No sound, nVidia, ATI requirements

Fixing FEAR 3 Crash to desktop, DLL errors

FEAR 3 just made my day. I think I’m posting this a bit late since I’ve been so hooked to the game, LOL! But anyway, here’s Game Crash Fixed’s usual hotfix list for you guys having trouble installing and running this game. Please post in the comments section if you encounter issues not covered here and I’ll try to help!

First things first! Please confirm that your PC meets the minimum requirements to run FEAR 3. You can check that over at the official FEAR 3 web site.

Problem #1:  FEAR 3 crashes to desktop (CTD) whenever I reach a specific point in the game (event/location varies for some users)

Solution A. Disable HDR
Solution B. Turn down all graphics settings to minimum. If turning all graphics settings to lowest fixes this problem, try updating to the latest video card drivers available.
Solution C. If  you are getting the MSVCR80.dll error, check out the next solution below.

Problem #2:  FEAR 3 crashes to desktop (CTD) whenever I reach a specific point in the game (event/location varies for some users)

1. If you are getting an error regarding msvcr80.dll (or if you don’t know what’s wrong…), try this more involved method of reinstalling the vcredist package- (warning! This is complicated!)

-Go to Add/Remove programs (programs and features in Vista/Win7)
-Find Microsoft Visual C++ Redistributable
-Uninstall it
-Conduct a search of C:\Windows\WinSXS for msvcr80.dll
-If it appears, rename the one that is labelled as being in this folder – x86_Microsoft.VC80.CRT_1fc8b3b9a1e18e3b_8.0.50727. 762_x-ww_6b128700 (THIS IS IMPORTANT! RENAMING OTHER ONES COULD CAUSE BAD TIMES!) to something like msvcr801.dll
-Restart (IMPORTANT!)
-Reinstall vcredist_x86.exe (see tip 1 for info on where to find this)

2. If running Windows Vista/7, please note that there is a problem with the Games Explorer launch icon. Use the start menu or desktop icons to launch the game.

3. Some users have had success removing the files wblogo2.vib and monolithbumper.vib. We’re looking into why these files may be causing problems for some, but this should at least allow you to play the demo if this is the problem you are experiencing. Some have had to remove ALL of the vib files. (NOTE – if doing this allows you to launch successfully, please contact me.)

4. Some users have experienced problems running the game while running two monitors. In these situations, disconnecting one monitor has resolved the issue.

Problem #3: Problem starting up FEAR 3 / FEAR 3 black screen at startup.

Solution A.

1. Run the vcredist.exe and dxsetup.exe
If you’re running Installshield – in the installer folder (what you downloaded, not the program files folder), there is a folder called support. The vcredist.exe is found there. In that same folder, there is a DirectX11 folder. Run the dxsetup.exe in that folder.

Solution B.

One of the experiments I made in my case was removing the wb and monolith VIBs, which allowed me to access the main menu, but not launching the game as it still crashes at 50% of the first level’s loading screen. These videos must have something special because I can see the others (esrb, gamespy, main menu background) with no problem.

Solution C.

I run windows firewall and a shaw secure firewall. I use shaw secure for my antivirus Like other threads have said to do make the following exceptions in your firewall

• GameoverlayUI (its in the main steam folder )
• C:\Program Files\Steam\SteamApps\common\<FEAR3 folder>(the icon that launches FEAR 3)

Outbound set to allow, in bound i have on prompt and it works fine.

Problem #4: FEAR 3 sound problem | Only sound  you in FEAR 3 are voices (Thats one creepy FEAR 3 error you got there)

Solution A.

Update your audio drivers. I had the same problem and I did that and it works now.
Any of you have Realtek HD Audio? That’s what I had for sound and a driver update fixed that.

Solition B.

Turn your volume up (seriously).

Solution C.

1. Remove any 3rd party codec packs from your system

2. Disable all audio devices except the one you want to use (we are fixing this incorrect audio device selection, but this is a workaround)-
Note: For Windows XP

First up is to check what audio playback devices you have registered:
Go to Control Panel > Sound and Audio Devices > Audio (tab) > Sound playback section
Look at the combo-box’s list of devices and note the ones which aren’t your soundcard to help you find a matching item in the Device Manager later
–Note: ATI HD Audio rear output (HDMI out for Radeon owners) shouldn’t be a problem
Next locate the items in Device Manager to disable or uninstall them:
Right click My Computer > Properties > Hardware (tab) > Device Manager
Find and disable the extra sound devices (probably under Sound, video and game controllers or System Devices)
- If you can’t find anything that matches click View > Show hidden devices and check again
- If you still can’t find anything close Device Manager and right click My Computer > Properties > Advanced (tab) > Environment Variables and add DEVMGR_SHOW_NONPRESENT_DEVICES to System Variables with a value of 1 (this will make Device Manager show everything it has detected over the lifetime of your OS instance that are no longer installed, like cards you’ve swapped out etc..), then reopen Device Manager >..> Show hidden devices and check again
Repeat the steps in the first part to check that only your sound h/w remains, if you have a Radeon 4___ then ATI HD Audio rear output will also be there (unless you disabled it) but that shouldn’t interfere, you can go back and try disabling that as well if you still get the “Sound Acceleration Error”
Finally try the game and assuming it works, you can remove the Environment Variable now if you want to.

2a. Disable other devices that may want to output audio
-It has been reported that 56k modems are causing interference. If you have no use for a 56k modem, remove it in device manager.
-Disable bluetooth drivers (if you’re not using bluetooth audio as your default)

3. Make sure that the audio device you want to use is set to default!

Loading...