xmilkychocolate :
Yea, I checked all my drivers and cleaned out my tower back when black ops 3 came out due to thinking it might've been that when the game initially came out (turns out it was Treyarch's poor attention to a PC port). I'd like to upgrade my card, but i'm holding out on doing any upgrades like that until Cyber Monday/Black Friday hits.
It's strange because I can't pinpoint the issue enough to replace what's causing it to happen. Sometimes it happens after 4-6 hours of gameplay, and other times it has happened 5 MINUTES after gameplay. No joke it happened to me 3 times in a row. The first time it happened was 5 minutes into gameplay. I just relaunched the game and it happened 10 minutes into it for the second time. Then after the second time was so sudden again, I did a complete reboot (thankfully on a SSD), booted the game back up, and no joke 1 minute into gameplay and it crashed. I was so frustrated a I stopped playing the game all together and went to bed. Makes it so frustrating to have to worry about quicksaving the game every 2 minutes due to worrying about a crash that would potentially lose you all your progress. I'm open to test any solutions someone has found.
Oh also, I tried a fix Microsoft posted here as well (found on another thread)
https://support.microsoft.com/en-us/kb/2665946
And increased the timeout to even longer than they suggested with no luck.
Yeah, same, tried so many different things I can hardly keep track of it. I've updated all the drivers I can think of, I've verified the game's cache, I've done a complete reinstall of the game, I've confirmed that I was on the beta that fixed xaudio crashes, I've updated to the latest AMD beta drivers when they came out, I've set the game to run in windows 7 compatibility mode, I've run a stress test on my CPU (all seem to be running fine), I've put fallout on it's own dedicated 500gb HDD. Tonight I'm planning on running a stress test on my GPU, but I can't see that being the problem either because it runs The Witcher 3 on high settings fine, no crashes over 100 hours, and that game is far more taxing than Fallout 4.
Can't pinpoint the issue either, crash logs are telling me nothing. I have temp and usage monitors running and there is nothing in danger zone levels, CPU temps are around 60, GPU around 50-60, only using ~4gb of ram while there's 8gb available. I can't imagine it's an issue with dust since I only just built the entire rig over the summer. This game is the only thing that causes the crash. The only hardware issue I can think that might be causing any issue whatsoever is my PSU is only at 550w I think, but I specifically chose the 380 4gb because of it's low power consumption.
I'm having the same issue too, crashing every ~5 mins, and it's so frustrating, I mean it's a lot of money to pay for a game that isn't playable, but I've got through 30 hours with no problem before the crashing so I can't even get a refund for it. What's even more annoying is asking about it on forums and everyone assuming that you're an idiot on a laptop who doesn't realize that 3gb of ram and integrated graphics aren't good enough to run the game, and swear at you for hating on "the best game of all time".
Anyway, going to try rolling the drivers back to 15.7.1 (even though I'm pretty sure I've already done that, might even try to roll them back to a previous version), set the fans to run high and downclock the GPU (even though I'm SURE I've tried that).
**EDIT** I just did some testing on it and it seems like I found something that works. I only had about 30 minutes so I'm not 100% sure this is a fix but so far it looks like it's working.
First I set the game to run in windows 7 compatibility mode, then I ran the game as an administrator. It worked long enough for me to roam around a bit and get killed 3 times (raiders, grenade and behemoth). Then I ran the game in Steam, crashed in less than a minute. So I
quit Steam and ran the game as administrator again, and retraced my steps exactly and voila, no crash. It might continue to crash less frequently, I have no idea, but hopefully Bethesda will address the CTD issue in next weeks update anyway, so hopefully this works as a temporary solution.