burritonator: When I launch the game, I see a screen that looks like it might be a pip boy display. After a brief moment, I hear a click and the game closes. There is no error message.

I thought the game might be crashing when trying to play an intro video. I played around with my codecs some. I discovered that if I manually open one of the .game's bik files, it plays successfully in both the rad video tools and vlc media player. That got me thinking that a problem playing a video mught not be why the game is crashing after all.

I tried running the game both through the launcher and by clicking the .exe file. I tried running it as admin and in various compatability modes. In win xp, 7, and 8 modes that same problem occurred.

I read that the gog version of fallout 3 runs out of the box in Windows 10, and I was hoping to avoid such problems.

What else should I try?

Thanks

---

Additional Information:

I discovered in my application crash logs that each time I try to launch the game, the folowing error occurs:

Faulting application name: Fallout3.exe, version: 1.7.0.3, time stamp: 0x4a40f18b
Faulting module name: Fallout3.exe, version: 1.7.0.3, time stamp: 0x4a40f18b
Exception code: 0xc0000005

It is always followed by this information message:

Fault bucket 1384869027, type 1
Event Name: APPCRASH
Response: Not available

---

Problem Solved

Short Version: I deleted the .ini files in documents/my games/fallout3 folder and then I was able to launch the game.

Long Version: One of the .ini files was dated from last year (2017). I suspect this was left over from when I tried to get the steam version of the game to run a while back, altough I don't know that for sure. When I deleted the .ini files and ran the fallout 3 launcher, the same .exe files were placed back into the folder mentioned above. What I had to do was to delete the .ini files after I ran the launcher but before I started the game. Now I have a fallout.ini file with today's date and the game runs.

burritonator: When I launch the game, I see a screen that looks like it might be a pip boy display. After a brief moment, I hear a click and the game closes. There is no error message.

I thought the game might be crashing when trying to play an intro video. I played around with my codecs some. I discovered that if I manually open one of the .game's bik files, it plays successfully in both the rad video tools and vlc media player. That got me thinking that a problem playing a video mught not be why the game is crashing after all.

I tried running the game both through the launcher and by clicking the .exe file. I tried running it as admin and in various compatability modes. In win xp, 7, and 8 modes that same problem occurred.

I read that the gog version of fallout 3 runs out of the box in Windows 10, and I was hoping to avoid such problems.

What else should I try?

Thanks

---

Additional Information:

I discovered in my application crash logs that each time I try to launch the game, the folowing error occurs:

Faulting application name: Fallout3.exe, version: 1.7.0.3, time stamp: 0x4a40f18b
Faulting module name: Fallout3.exe, version: 1.7.0.3, time stamp: 0x4a40f18b
Exception code: 0xc0000005

It is always followed by this information message:

Fault bucket 1384869027, type 1
Event Name: APPCRASH
Response: Not available

---

Problem Solved

Short Version: I deleted the .ini files in documents/my games/fallout3 folder and then I was able to launch the game.

Long Version: One of the .ini files was dated from last year (2017). I suspect this was left over from when I tried to get the steam version of the game to run a while back, altough I don't know that for sure. When I deleted the .ini files and ran the fallout 3 launcher, the same .exe files were placed back into the folder mentioned above. What I had to do was to delete the .ini files after I ran the launcher but before I started the game. Now I have a fallout.ini file with today's date and the game runs.

KZadBhat420: I can confirm the issue isn't any problem with the previous Steam installation, a totally clean installation of the GOG version has the same problem, and deleting the fallout.ini file solves it just the same. The file as it sits from a clean install is very small and incomplete, perhaps it just convinces the program that what it needs is there and then it can't find it, when it really doesn't. But there is also a line in the fallout.ini file included with the install that isn't there in what fallout.exe creates on first run:

sResourceDataDirsFinal=

But a quick search shows that, at least in Fallout 4, this line is added to by certain mods to point to content they alter. Either way, deleting this file solves the problem.