New
#1
Certain old Steam games CTD immediately on launch
For whatever reason, some of my old Steam games refuse to run. Currently this counts
- Bioshock Infinite
- Tomb Raider (2013)
- Deus Ex: Human Revolution
All of them start to run and then immediately stop and disappear from memory. Tomb Raider loads its launcher, but it's the same issue when I try to run the actual game - starts to load and then vanishes. I bought Bioshock Infinite on GoG to play it and that version runs just fine - and AFAIK the only difference to the steam version is that SteamAuth is removed.
Tried running steam and these games in admin mode, switching the games themselves to Win7 and 8 compatibility, updating graphics drivers, running sfc and chkdsk, disabling the antivirus and firewall, but nothing helps.
Other games on steam I've tried to play run just fine - including older games. Dishonored, Dishonored 2, FS19, ATS/ETS2, and a few others all run without any issues, so at least by deduction it shouldn't be steam itself that is the problem. Sims 4 on Origin and the few Uplay games I've tried also run with no issues.
Tried installing Bioshock Infinite from Steam again tonight just to see if I can get it to work (since it's small and downloads fast), but it still refuses to run. Only this time it gave me an error when I first tried to launch it (where previously I never got any errors when trying to run these games):
Faulting application name: BioShockInfinite.exe, version: 1.1.25.5165, time stamp: 0x53263b17
Faulting module name: unknown, version: 0.0.0.0, time stamp: 0x00000000
Exception code: 0xc0000005
Fault offset: 0x01b0340c
Faulting process ID: 0x2664
Faulting application start time: 0x01d6021e5067c92c
Faulting application path: C:\Program Files (x86)\Steam\steamapps\common\BioShock Infinite\Binaries\Win32\BioShockInfinite.exe
Faulting module path: unknown
Report ID: 974835cd-9ac1-4e3a-9f81-38a81cbc3065
Faulting package full name:
Faulting package-relative application ID:
Since 0xc0000005 apparently means an access violation (though I can't decipher what it violated), I thought maybe it doesn't like running on the M.2 (although the GoG version didn't mind), so I moved it to my D-drive (4 TB platter). It still won't run from there and now it doesn't give me an error, so I have even less to go on.
Built this system in mid-February and according to the MSI download site there are no newer drivers for the motherboard yet, so I've only been able to update the graphics and mouse drivers, which hasn't helped anything.
I'm not sure what else to try to fix this when everything everyone says should fix it doesn't make any difference. Since it's basically a brand new system it's not like there's any longterm build-up of files or registry entries and even then I've always run disk cleanup monthly to purge all the temp folders etc.