I bought the original Fallout game today out of nostalgia but the second I click on play my whole computer crashes and I have to restart it. Anybody have any thoughts on what the issue could be?

I've seen quite a few reports of Galaxy messing up things lately, so you should try running the game from outside Galaxy before trying anything else to see if it works. Usually the easiest way is from the shortcut found in the game's installation folder.

I've been playing around with this for almost a week now and I'm convinced it's because my PC is an all AMD build. I'm going out of town for work this week so I thought I would install the game on my laptop, which is an Intel machine, and see what happens. The game loaded up no problem.

Went back to my AMD PC, where I removed galaxy and did a fresh install of the game, and immediate crash. Well, crash really isn't the right term I guess. It basically just restarts my computer.

Although I did upgrade my memory a couple of weeks ago and noticed that my PC acts different now. Maybe I'll try swapping back to my old memory when I get back into town and give it another shot. Just to see.

Thanks anyway though.

If you have tried other games and this only happens with F1, it's difficult not to blame the game, but still... a reset without even a BSOD is no joke for software to cause on its own.

If you test with the old RAM and it still resets the PC, and you have both discrete and integrated graphics, you could also try removing or disabling the video card and trying with integrated. That is just to see if there is a problem, it is no solution, of course.

If the problem persists then, maybe a little stress testing with Prime95 and monitoring with HWiNFO or similar could reveal if there is a CPU or motherboard problem (could also be just drivers or configuration, no need for it to be something "broken"), and you can continue diagnosing from there.

Good luck

You're making a lot of sense, and I appreciate your wisdom on this. I will definitely try your suggestions when I get back and report my results later this week.

Thank you again!

Definitely sounds like a hardware problem.

You might want to use BlueScreenView or a similar software first to determine cause of the blue screen and immediate reboot. At least it will be clear if some hardware is related.
You could check your Windows installation health via command: sfc /scannow and reboot. Command must be issued with elevated previleges.
Also you could try to remove ddraw.dll or/and High resolution patch from the game installation directory and see if this makes the situation better.
You could check your CPU and GPU temperature under load with something like 3D Mark.

Tried all that nothing seems to work but the BlueScreenView told me this:

Bug Check String: UNEXPECTED_KERNEL_MODE_TRAP
Bug Check Code: 0x0000007f
Parameter 1: 00000000`00000008
Parameter 2: ffffc181`055e42b0
Parameter 3: ffffe887`b778ff50
Parameter 4: fffff801`164c53cd
Caused By Driver: ntoskrnl.exe
Caused By Address: ntoskrnl.exe+1c14e0
Processor: x64
Crash Address: ntoskrnl.exe+1c14e0
Full Path: C:\WINDOWS\Minidump\112619-6656-01.dmp
Processor Count: 16
Major Version: 15
Minor Version: 18362
Dump File Size: 1,471,740

I have no idea what any of this means.

Bug Check 0x7F: UNEXPECTED_KERNEL_MODE_TRAP

One of the most common trap codes:
0x00000008, or Double Fault, indicates that an exception occurs during a call to the handler for a prior exception. Typically, the two exceptions are handled serially. However, there are several exceptions that cannot be handled serially, and in this situation the processor signals a double fault. There are two common causes of a double fault:

* A kernel stack overflow. This overflow occurs when a guard page is hit, and the kernel tries to push a trap frame. Because there is no stack left, a stack overflow results, causing the double fault. If you think this overview has occurred, use !thread to determine the stack limits, and then use kb (Display Stack Backtrace) with a large parameter (for example, kb 100) to display the full stack.
* A hardware problem.

So, the most probable causes are still either a heavy krenel memory leak or a hardware problem.

Memory leak may be caused by either broken Windows installation or by damaged or misconfigured device drivers.
Hardware problem is more likely scenario but it's harder to diagnose.

So, be I in your place, I'd first made a new clean installation of the Windows, may be, in parallel to the existing one. And see if problem persits when game is being run on that new instance of the OS.
If it's not then I'd move to the new installation and remove the old one. Since it means corrupted Windows is a culprit.
But if the problem'd still be there I'd made through burn-in test of each of the hardware components. Starting from the RAM modules. Because all possible sources of the blue screen except for the faulty computer parts are sorted out in this case.

Hi, I know this post is a few months old but I was having the exact same issue when I got the game a couple of weeks ago. I tried a ton of fixes but here's what worked for me.

I have a MSI bravo 15 with AMD processor and graphics.

Firstly I deleted the game folders, including falloutfixt etc. I also uninstalled MSI afterburner and Nahimic audio control. I then installed Fallout 2 BEFORE installing Fallout, both on an external SSD. Don't know why, but gog galaxy wouldn't even give me the option of installing Fallout till F2 was installed. I didn't bother with fix mods as these seemed to stop it loading. Also, it seems to crash if I try to display it on an external monitor, but as long as I'm using the laptop screen I'm no longer having any issues.

I don't know enough about computers to know why this worked, or if all the steps are relevant in any way