Yesterday (and for a couple weeks) it worked without any crashes, today it doesn't work at all.

It shows the logo, and then just as it's showing the power armor suit with the green text to press any button, it crashes to desktop.

I did run some standard Windows updates today. I guess the latest Windows updates have screwed up the game?!

Verified game files with Steam.

Windows 7 Pro 64-bit.

AMD drivers are all up to date.

Time of this report: 11/28/2015, 21:00:48   Operating System: Windows 7 Professional 64-bit (6.1, Build 7601) Service Pack 1 (7601.win7sp1_gdr.151019-1254)System Manufacturer: ASUS          Processor: Intel(R) Core(TM) i7-4770 CPU @ 3.40GHz (8 CPUs), ~3.4GHz             Memory: 16384MB RAMAvailable OS Memory: 16322MB RAM          Page File: 3419MB used, 29224MB available    DirectX Version: DirectX 11     DxDiag Version: 6.01.7601.17514 64bit Unicode          Card name: AMD Radeon HD 7800 Series       Manufacturer: Advanced Micro Devices, Inc.          Chip type: AMD Radeon Graphics Processor (0x6818)        Driver Name: aticfx64.dll,aticfx64.dll,aticfx64.dll,aticfx32,aticfx32,aticfx32,atiumd64.dll,atidxx64.dll,atidxx64.dll,atiumdag,atidxx32,atidxx32,atiumdva,atiumd6a.cap,atitmm64.dllDriver File Version: 8.17.0010.1230 (English)     Driver Version: 13.152.0.0        DDI Version: 11

So strange that it would be working fine and then cease to work. That's the part that gets me.

But I updated from the latest AMD driver I already had to the Beta driver, and that solved the issue.

This wouldn't happen to have something to do with the Winsock update, would it? Someone else mentioned that in another thread.

Kind of a shot in the dark here, but is one of the updates you installed KB3092601? Someone else reported that after installing this security update, the game wouldn't launch successfully.

Here's a easy guide to checking update history.

http://www.sevenforums.com/tutorials/24367-windows-update-view-update-history-details.html

I'm unsure why a winsock security update would cause the game from starting, unless it's related to the code used to run the pip boy app.

Worth a look. Hope it helps in some way!

EDIT: Saw the responses after I posted... hadn't refreshed this thread it seems. Interesting that the other person who had the issue with that update also had amd hardware. Nowhere near any meaning should be pulled from that yet, but I wonder if any other AMD users have run into the same thing in the last week.