My friend's pc is running windows 7 x64 and its a newer pc. He can't launch x64 games. Any x64 games crash instantly on loading up. Running from the install dir causes a "Fatal Error. Steam Must Be Running to Play" and when he launches from Steam they just crash. I noticed Advanced Warfare booted up the splash but it crashed and it didnt even create a default config.cfg in the players2 folder. There are dumps but with nothing of importance in them. He has removed and re installed drivers. installed all redists. completely uninstalled steam and the games and cleaned his registry with RevoUninstaller. We have no clue what is causing this. Hes using an AMD gpu and cpu. Any ideas guys? he really doesnt wanna have to nuke it. he also has all important windows updates. We have tried Advanced Warfare and Shadow of Mordor and Ethan Carter.
Event log will provide you with info probably. If not standard tests, memtest, prime to check for stability. If everything is fine prolly is OS
Googled. www.steamcommunity.com/sharedfiles/filedetails/?id=241092849 This post was directed at Payday 2 but it's the same error. Give it a shot.
Trying uninstalling steam and re installing it . That worked for me in the past. Otherwise try installing Windows 7 without reformatting. It might just re install any missing files. Otherwise,you will have to reformat and re install windows..
Is he using any monitoring software like MSI Afterburner at all? I had a similar problem when I ran two AMD 7970Ghz ED cards.
Is it a legit copy of windows and does he have a disc? If so I would try reinstalling the OS as that sounds like the most likely culprit.
There is a repair option with Windows 7 if you have the disc or can burn one. Just make sure you have your key safely stored before you do anything drastic. It's odd that you specify it's peculiar to 64-bit games. Sorry for asking the dumb question but you know what it's like with computers, you have to start with the obvious - is it definitely Windows 64-bit? You can check by looking at the System Properties. Should say if it's 64-bit. Failing that, some sort of memory fault that only triggers with larger memory addressing? Seems unlikely but I've heard weirder things. A quick search turns up this: http://answers.microsoft.com/en-us/...tly-with/50a721df-b2b0-409c-96fa-e6c4d68d2759 There are a number of people who have had the same issue as you and several found things that fixed it for them. If nothing else, it's a handy list of things to try. To me it sounds like some sort of driver issue, triggering only when 64 bit software starts up, a DX9 issue for example.