Crashing after load screen (Windows 10 Anniversary)

Post by **G1LT** » Thu Sep 22, 2016 12:56 am

Decided after my game got bogged down with the Windows 10 Anniversary update, I would just start over with TTW and see how it is. Even if it ran "ok" it would probably be a better experience than just NV on its own. I haven't beat either game, and really would love to seamlessly experience the two narratives... but now, like so many others, my game is back to crashing after the load screen.

I have tried the Beta NVAC patch, but it hasn't done the trick. I can't seem to roll back my video drivers, but I honestly don't think that is the main issue. This started after the Anniversary update, and my drivers were updated and running fine before. I have included my load order, I imagine the problem could potentially be there. My computer can run Fallout NV just fine on high settings (not max) so I don't see my hardware being the problem... I just don't know, I am pretty excited to experience this mod, and both the stories of Fallout 3 and NV... Any help would be greatly appreciated.

Post by **zilav** » Mon Sep 26, 2016 8:20 am

Turn on logging in NVSE and check for possible hints.

Post by **Royhr** » Mon Sep 26, 2016 12:48 pm

Weird how some people experience issues with Windows 10 Anniversary. I've been running perfectly fine with the update as well as with nVidia drivers.

Post by **RoyBatty** » Mon Sep 26, 2016 5:56 pm

It's a crash fest for most people due to microsoft changing the wddk 2.1. AMD drivers are affected now too.

Post by **jlf65** » Mon Sep 26, 2016 7:57 pm

Well, I'm glad my AMD APU hasn't had new drivers for years, then. I'm almost scared to update my computer.

Post by **khumak** » Fri Oct 07, 2016 1:27 am

This sort of thing is why I have non security updates delayed as long as possible. I just cross my fingers and hope most of the obvious bugs get fixed before I'm forced to update. I read about an earlier update they did that forced some buggy nvidia driver update which failed, caused a reboot, which forced you to update that driver again, which failed, caused a reboot, rinse, repeat forever. I would have been pretty pissed if I got hit with that, and I do use an Nvidia card.

Post by **generalmx** » Sun Oct 23, 2016 7:13 am

[quote=jlf65]

Well, I'm glad my AMD APU hasn't had new drivers for years, then. I'm almost scared to update my computer.

[/quote]

How old is your AMD APU that it doesn't have driver updates? I still help out with reloads at a computer shop and AMD APU drivers go There should be at least driver packs with updated versions of AMD CCC or whatever they're calling it these days. I'd check here: http://support.amd.com/en-us/download/mobile?os=Windows+10+-+64#2 and click on "Supported Products" and go to the APU section, as this driver package was just released 3 days ago (though your response came before this driver was released). If you have problems with it you can always rollback the driver in Windows: https://www.lifewire.com/how-to-roll-back-a-driver-in-windows-2619217. The driver package also has an option of doing a clean install, which you should do if you have issues.

Note with AMD they take ages to get a driver package out of "beta" for liability reasons, meaning critical support for updates in Windows may not come for a year if you only install the "release" versions. For ancient APUs (5000M series and older) you can still get the beta software linked here that was last updated in 3-1-2016: http://support.amd.com/en-us/download/desktop/legacy?product=legacy3&os=Windows+10+-+64

Generally you should always use the latest versions of driver packages at least for performance reasons unless you have critical problems with them--especially on an APU, where you need all the performance you can get.