Borderlands worked 5 hours ago and now General Protection Fault

[Vryce]

I believe that Microsoft pushed something out today and I have done a cold start of my box.
My box specs are for current games and easily run Borderlands, all flavors, in fact as noted I was playing earlier today getting ready for my grandsons.
Now I am getting a General Protection Fault and have done the following:
Verified my files through my Steam account/library.
Searched for others having the same problem and tried the cudart/physcudart solution as well as running as Administrator with no solution.
I took a look at the event logs and found this:
Faulting application name: Borderlands.exe, version: 1.5.0.0, time stamp: 0x53ed3bb3
Faulting module name: Borderlands.exe, version: 1.5.0.0, time stamp: 0x53ed3bb3
Exception code: 0xc0000005
Fault offset: 0x009c0fd9
Faulting process id: 0x165c
Faulting application start time: 0x01d4997acc47ad39
Faulting application path: D:\Program Files (x86)\Steam\steamapps\common\Borderlands\Binaries\Borderlands.exe
Faulting module path: D:\Program Files (x86)\Steam\steamapps\common\Borderlands\Binaries\Borderlands.exe
Report Id: 9ca22803-cb6a-4652-988c-7fa3e22a3add
Faulting package full name:
Faulting package-relative application ID:
Then:
System

- Provider

[ Name] Application Error

- EventID 1000

[ Qualifiers] 0

Level 2

Task 100

Keywords 0x80000000000000

- TimeCreated

[ SystemTime] 2018-12-21T22:16:26.942338100Z

EventRecordID 21846

Channel Application

Computer Natarthos

Security

and:

EventData

Borderlands.exe
1.5.0.0
53ed3bb3
Borderlands.exe
1.5.0.0
53ed3bb3
c0000005
009c0fd9
165c
01d4997acc47ad39
D:\Program Files (x86)\Steam\steamapps\common\Borderlands\Binaries\Borderlands.exe
D:\Program Files (x86)\Steam\steamapps\common\Borderlands\Binaries\Borderlands.exe
9ca22803-cb6a-4652-988c-7fa3e22a3add

Yes, I noted the Security at the end but I was running as an Administrator; I right clicked on Borderlands.exe and "Run as administrator:
Here is the strange part, Borderlands 2 and the Pre-quel both work just fine.

If anyone has any ideas it would be greatly appreciated. I had just started on my second playthrough when all this happened.
Regards,
Nat

PS The actual message that popped up was: (could not paste the image)
General Protection fault:
History: GetPluginCount() Address = 0xdc0fd9 (filename not found) in D:]Program Files (x86)\Steam\steamapps\common\Borderlands\Binaries\Borderlands.exe)
GetPluginCount() Address = 0xdc6d0a (filename not found) in D:]Program Files (x86)\Steam\steamapps\common\Borderlands\Binaries\Borderlands.exe)
MsgRelease() Address = 0x6abf726 (filename not found) (in C:\WINDOWS\SYSTEM32\CoreMessaging.dll)
Is it possible/probable that Microsoft deleted some file but then the others run but they were developed under different Windows versions I believe?

Nat

[Vryce]

Mystery solved!
Beloved Microsoft strikes again!
I did a repair of my Windows 10 installation and all is right with the messed up world of Borderlands 1 again!
Nat

[Vryce]

I just knew it would not last. Here is the pattern:
Uninstall
Install
Play (works!!!!)
Quit game and save
Borderlands will not start up again; we go back to the General Fault.

I have repeated this process three times now and tried multiple ways to get around whatever the problem. My latest, perhaps fatigued idea is to copy the binaries file if this one works and then try copying the binaries file back if I get the General Fault after a save. My sort of theory is that something is getting bombed in the binaries. I singled out Microsoft too early and for that I apologize. If anyone has any ideas they would be greatly appreciated. I realize this is an old game but this old game is now being enjoyed by a third generation of gamer!
Nat

[Vryce]

Okay, I can now reporduce the problem.
I uninstalled/reinstalled and then started the game and saved. No problem restarting.
I did something in the Borderlands world that would update my inventory, i.e. cause some other data to save and no problems, I quit and Borderlands restarted just fine.
IF I change the resolution to the maximum, quit and save Borderlands WILL NOT restart. I have to uninstall and reinstall.
My plan is to see if a resolution somewhere below maximum might allow me to continue playing. All this happened today. Perhaps there was a driver update and we are getting a bad method call?
Nat
'

[Draekus]

try one or both of these :
https://steamcommunity.com/sharedfiles/filedetails/?id=475142385
https://steamcommunity.com/sharedfiles/filedetails/?id=754572934

[Arkangel Michael]

Data Execution Prevention is the most common cause of 0xc0000005 (memory read: ACCESS DENIED).

For Windows 10:
Start > Exploit Protection > Program Settings > Click the '+' left of 'Add Program to Customize > Add by Program Name > Type 'borderlands.exe' > Click 'Add'

WARNING: Adding by 'Choose exact file path' is more secure.
WARNING: This makes you more vulnerable to hacking if the game code is compromsied.

Find any setting that is turned 'On' and check the box left of 'Override system settings', then click the button that says 'On', and it will toggle to 'Off'.

For Windows XP, Vista, 7, 8, 8.1:
Start > Run > 'sysdm.cpl' > 'Advanced' (Tab) > Under 'Performance' click the 'Settings' button > 'Data Execution Prevention' (Tab) > :

There are two settings:
Turn on DEP for essential Windows programs and services only
Turn on DEP for all programs and services except those I specify

The second is more secure (assuming this is selected) click 'Add' > navigate to 'borderlands.exe' > click 'Open'

OR

change the setting to
Turn on DEP for essential Windows programs and services only

OR

Start > Type 'cmd.exe', Right click, and select 'Run as Administrator' > Type 'bcdedit.exe /set {current} nx AlwaysOff'

WARNING: This will disable DEP for the whole computer, and is not recomended from a security standpoint.

If these don't work then it is possible you have DEP enabled forcibly via either the EMET, or via Group Policy.

Doing the above, and installing vcredist_64.exe (Visual C Redistributable), along with PhysX_8.10.29_SystemSoftware.exe (NVIDIA PhysX) from the prerequisites folder solved my problem.