Fallout NV no longer working after Windows 10 anniversary update

[djpolofish]

I can't get Fallout NV to run after installing windows 10 anniversary update, I've played 83 hours of the game with no problems until now. I've installed a fresh mod free version just to see if any mods where affecting the game with no luck.

System

i5 3.50 GHz

16 GB DDR4

GTX 960, 4 GB GDDR5

All drivers up to date.

Any help with this issue would be much appreciated.

[dubiousintent]

Where do you have the game installed? If to the default location of "C:\Program Files", see the wiki article "Installing Games on Windows Vista+" in my signature.

 

What are the symptoms when you attempt to run the game? Do you click on a shortcut and nothing happens, or the game starts but CTDs before reaching the main menu, or "blue screen", or what? How far does it get?

 

Have you checked the Windows Event Viewer for either "Application" or "System" errors?

 

-Dubious-

[djpolofish]

Where do you have the game installed? If to the default location of "C:\Program Files", see the wiki article "Installing Games on Windows Vista+" in my signature.

 

What are the symptoms when you attempt to run the game? Do you click on a shortcut and nothing happens, or the game starts but CTDs before reaching the main menu, or "blue screen", or what? How far does it get?

 

Have you checked the Windows Event Viewer for either "Application" or "System" errors?

 

-Dubious-

Thanks for the reply.

 

I've just done another fresh install this time I created a new folder at C:STEAMgames followed the advice on the wiki but still no luck.

 

I've tried to open the game with Steam and the shortcut each time the game starts I select new game after which I get the standard loading screen then C.T.D, no different from when the game was installed in C:\Program Files (x86).

 

I've also run "verify integrity of game cache" apart from the standard "1 file failed" it shows nothing.

 

Like I said before, this game was fine until Windows 10 anniversary patch was installed.

 

Windows event viewer...... stuff.

 

- <Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">

- <System>

<Provider Name="Application Error" />

<EventID Qualifiers="0">1000</EventID>

<Level>2</Level>

<Task>100</Task>

<Keywords>0x80000000000000</Keywords>

<TimeCreated SystemTime="2016-08-19T19:01:46.695443400Z" />

<EventRecordID>358</EventRecordID>

<Channel>Application</Channel>

<Computer>DESKTOP-***********</Computer>

<Security />

</System>

- <EventData>

<Data>FalloutNV.exe</Data>

<Data>1.4.0.525</Data>

<Data>4e0d50ed</Data>

<Data>FalloutNV.exe</Data>

<Data>1.4.0.525</Data>

<Data>4e0d50ed</Data>

<Data>c0000005</Data>

<Data>00757aa9</Data>

<Data>102c</Data>

<Data>01d1fa4c14865598</Data>

<Data>C:\STEAMgames\Steam\steamapps\common\Fallout New Vegas\FalloutNV.exe</Data>

<Data>C:\STEAMgames\Steam\steamapps\common\Fallout New Vegas\FalloutNV.exe</Data>

<Data>975aa44d-b6b5-445c-ad43-db1c68f5b314</Data>

<Data />

<Data />

</EventData>

</Event>

 

Windows event viewer (when game was in C:\Program Files (x86))

 

- <Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">

- <System>

<Provider Name="Application Error" />

<EventID Qualifiers="0">1000</EventID>

<Level>2</Level>

<Task>100</Task>

<Keywords>0x80000000000000</Keywords>

<TimeCreated SystemTime="2016-08-18T22:52:25.046677800Z" />

<EventRecordID>280</EventRecordID>

<Channel>Application</Channel>

<Computer>DESKTOP-*******</Computer>

<Security />

</System>

- <EventData>

<Data>FalloutNV.exe</Data>

<Data>1.4.0.525</Data>

<Data>4e0d50ed</Data>

<Data>FalloutNV.exe</Data>

<Data>1.4.0.525</Data>

<Data>4e0d50ed</Data>

<Data>c0000005</Data>

<Data>00757aa9</Data>

<Data>be4</Data>

<Data>01d1f9a316b05e43</Data>

<Data>C:\Program Files (x86)\Steam\steamapps\common\Fallout New Vegas\FalloutNV.exe</Data>

<Data>C:\Program Files (x86)\Steam\steamapps\common\Fallout New Vegas\FalloutNV.exe</Data>

<Data>530a0c4f-794a-4168-8d15-38c1f7700bff</Data>

<Data />

<Data />

</EventData>

</Event>

Edited August 19, 2016 by djpolofish

[djpolofish]

Where do you have the game installed? If to the default location of "C:\Program Files", see the wiki article "Installing Games on Windows Vista+" in my signature.

 

What are the symptoms when you attempt to run the game? Do you click on a shortcut and nothing happens, or the game starts but CTDs before reaching the main menu, or "blue screen", or what? How far does it get?

 

Have you checked the Windows Event Viewer for either "Application" or "System" errors?

 

-Dubious-

 

 

c0000005.... do you think I should do a rollback?

Edited August 19, 2016 by djpolofish

[HeyYou]

 

Where do you have the game installed? If to the default location of "C:\Program Files", see the wiki article "Installing Games on Windows Vista+" in my signature.

 

What are the symptoms when you attempt to run the game? Do you click on a shortcut and nothing happens, or the game starts but CTDs before reaching the main menu, or "blue screen", or what? How far does it get?

 

Have you checked the Windows Event Viewer for either "Application" or "System" errors?

 

-Dubious-

 

 

c0000005.... do you think I should do a rollback?

 

If the rollback is similar to 'revert to original O/S', I wouldn't hold my breath on that working, or even leaving you with a working copy of windows.....

 

When you uninstalled, did you also remove the folders in My Games, (where ini's, and save games are held) and the folder in C:\Users\yourusername\appdata?

[djpolofish]

 

 

Where do you have the game installed? If to the default location of "C:\Program Files", see the wiki article "Installing Games on Windows Vista+" in my signature.

 

What are the symptoms when you attempt to run the game? Do you click on a shortcut and nothing happens, or the game starts but CTDs before reaching the main menu, or "blue screen", or what? How far does it get?

 

Have you checked the Windows Event Viewer for either "Application" or "System" errors?

 

-Dubious-

 

 

c0000005.... do you think I should do a rollback?

 

If the rollback is similar to 'revert to original O/S', I wouldn't hold my breath on that working, or even leaving you with a working copy of windows.....

 

When you uninstalled, did you also remove the folders in My Games, (where ini's, and save games are held) and the folder in C:\Users\yourusername\appdata?

 

Sorry man didn't see your message. Just finished rollback, the game now works fine. It seem that the Anniversary update is causing c0000005 errors with a variety of programs MS knows about this and is working on a solution.

 

But to answer your question I did remove the folders in My games

 

Thanks for the reply though, it's good to know that members here brainstorm for solutions.

Edited August 19, 2016 by djpolofish

[dubiousintent]

The "c0000005" error indicates the game tried to access some portion of memory outside of that allocated to it by the system. Given the game hasn't changed, it appears the "anniversary update" broke something on the system side. Which is what you learned from MS it appears, given other programs are having the same problem. Under the circumstances, the "rollback" to a previous "restore point" was your best move.

 

Bear it in mind if the same thing happens after another "update/patch".

 

-Dubious-

[djpolofish]

The "c0000005" error indicates the game tried to access some portion of memory outside of that allocated to it by the system. Given the game hasn't changed, it appears the "anniversary update" broke something on the system side. Which is what you learned from MS it appears, given other programs are having the same problem. Under the circumstances, the "rollback" to a previous "restore point" was your best move.

 

Bear it in mind if the same thing happens after another "update/patch".

 

-Dubious-

Thanks guys.

 

I wouldn't of known what to do if you hadn't said to check Windows Event Viewer. My first born shall be named after you, Dubiousintent.

Edited August 19, 2016 by djpolofish

[RoyBatterian]

There's been issues for some people with current nvidia drivers too. I posted a topic about reporting similar issues.