Problem occurs on Win7 64-bit. FEAR 1 ("fear.exe") crashes immediately after starting with the classic message "F.E.A.R. has stopped working". FWIW Windows event log says exception code 0xc0000005. This is a retail release installed from CD, not the GOG version, but I'm hoping somebody can still help me. Now, some relevant facts:

The game's been installed on this system and working fine for years, but I haven't played it in a while. Just tried again recently and now it crashes.

By fiddling with restore points, I found it works under my system as it was in April of this year, but looking at the list of affected programs, I don't see anything obvious that I've installed since then that would affect this game. (Only things installed are more games). Obviously, something I've done has broken FEAR, but what?

If I uninstall and then reinstall FEAR V1.0 fresh from the CD (no patches), it crashes on start-up if I run it from a folder named "FEAR" (the default installation folder") but if I rename the folder to something else (e.g., "FEAR v1-0") it starts and runs fine. (This suggests to me that maybe there's something in the Registry that's amiss? When I rename the folder, the Registry setting doesn't apply and the game runs. Just a guess at this point.)

After installing Extraction Point which upgrades FEAR to V1.07, FEAR crashes on start-up no matter what I name I give the folder. But Extraction Point runs fine.

Finally, installing the final patch to V1.08 had no effect. Still crashes on start-up. Also tried various compatibility settings and running as Administrator. No change.

Anybody have any idea of what I might try to figure this out? Thanks in advance for any assistance.

Cannot help much except telling that I have also seen how Microsoft have been pretty sloppy when making the patches for Windows 7 this year, affecting stability and speed.

Thanks. That's actually not a bad thought. I've had Windows Update disabled for years because its primary effect for me has been to destabilize my system. But I did install one update this year after the time when FEAR last worked: KB4019990 - D3D9Compiler needed to run GOG's System Shock. A possible culprit? Unfortunately, uninstalling the update had no effect. FEAR still crashes on startup. :-(

Update... Just discovered this game is available on GOG for $2.49 (including Extraction Point and Perseus Mandate) so I'm gonna try that version. If the problem persists, I'll be back.

After 2 days (!) of downloading, F.E.A.R. Platinum is installed and working fine. There's now no point in my spending time trying to get the original retail version running. Thanks, GOG.

My slow brain probably came up with the problem. I remember MS blocked a couple of copy protection systems on Windows, 7 included. No idea if there are ways around that though.

And this comment triggered *my* slow brain to eventually remind me of something similar to DRM that can cause this kind of problem: Data Execution Prevention. Sure enough, I added an exception for "FEAR.exe" to the DEP exception list and now the game runs just fine. Thanks for the hint!

For those who might encounter this same problem, you can find instructions for DEP on the Web. Or here's how I do it:

1. Run “sysdm.cpl”.
2. Click the “Advanced” tab, then Performance > Settings.
3. Click the “Data Execution Prevention” tab.
4. Check “Turn on DEP for all programs…except…”, click "Add", and choose the relevant EXE.

Of course, I now own own two copies of the game. C'est la vie.