Windows 10 Check Dump file from Borderlands in Steam?

Saltgrass

Excellent Member
Microsoft Community Contributor
Joined
Oct 16, 2009
Messages
15,156
If anyone wants to check this dump file, here it is. The situation is I start Borderlands in Steam, the Splash Screen comes up but when I click play, it just goes away, no game starts.

I see a comment about some instruction not being able to write to some memory address. If it is saying that, I do get error dialog windows saying about the same thing when I go from a Microsoft account to a Local Account.

Thanks.
 

Attachments

Solution
Code: 
This dump file has an exception of interest stored in it.
The stored exception information can be accessed via .ecxr.
(198c.18ac): Access violation - code c0000005 (first/second chance not available)
eax=00000000 ebx=ffffffff ecx=00f8ecdc edx=00000014 esi=000003b4 edi=00f8e624
eip=77119fac esp=00f8d654 ebp=00f8d660 iopl=0         nv up ei pl nz na po nc
cs=0023  ss=002b  ds=002b  es=002b  fs=0053  gs=002b             efl=00000202
ntdll!NtGetContextThread+0xc:
77119fac c20800          ret     8
Hmm... an access violation is data held in the RAM which is corrupt. I wonder if this is like the L4D2 issue we were getting? Have you considered trying the sfc fix I posted earlier?
Sort by date Sort by votes
Code: 
This dump file has an exception of interest stored in it.
The stored exception information can be accessed via .ecxr.
(198c.18ac): Access violation - code c0000005 (first/second chance not available)
eax=00000000 ebx=ffffffff ecx=00f8ecdc edx=00000014 esi=000003b4 edi=00f8e624
eip=77119fac esp=00f8d654 ebp=00f8d660 iopl=0         nv up ei pl nz na po nc
cs=0023  ss=002b  ds=002b  es=002b  fs=0053  gs=002b             efl=00000202
ntdll!NtGetContextThread+0xc:
77119fac c20800          ret     8
Hmm... an access violation is data held in the RAM which is corrupt. I wonder if this is like the L4D2 issue we were getting? Have you considered trying the sfc fix I posted earlier?
 
Upvote 0 Downvote
Solution
I would try that fix except for the problems I foresee with it. Since it has happened in all installs, even clean ones I have to assume it would not help anyway.

Can you tell where the Invalid pointer is, what memory exactly? Since both of my systems do the same thing, it is probably some situation either Steam or 2K is not ready to address.

The games will run fine after they start, but it might take two or three start attempts before they will start. In the previous build (9926) the games would BSOD after about 15 minutes, so I suppose this is progress.

Thanks for checking.
 
Upvote 0 Downvote
You must log in or register to reply here.