Crash on Startup [SOLVED]

[lyricsmaniac]

Just installed it tonight.
thoughts?
I think it's some gamespy ♥♥♥♥♥♥♥♥.
---------------------------
Message
---------------------------
Can't bind to native class OnlineSubsystemGameSpy.OnlineSubsystemGameSpy



RaiseException() Address = 0x7642c42d (filename not found) [in C:\Windows\syswow64\KERNELBASE.dll]

CxxThrowException() Address = 0x73c6df60 (filename not found) [in C:\Windows\WinSxS\x86_microsoft.vc90.crt_1fc8b3b9a1e18e3b_9.0.30729.6161_none_50934f2ebcb7eb57\MSVCR90.dll]

GetOutermost() Address = 0x5ed7a8 (filename not found) [in C:\Program Files (x86)\Steam\steamapps\common\Borderlands\Binaries\Borderlands.exe]

GImage::GImage() Address = 0x5c4fcd (filename not found) [in C:\Program Files (x86)\Steam\steamapps\common\Borderlands\Binaries\Borderlands.exe]

GImage::GImage() Address = 0x57a234 (filename not found) [in C:\Program Files (x86)\Steam\steamapps\common\Borderlands\Binaries\Borderlands.exe]

GDebugger() Address = 0x1fe7d24 (filename not found) [in C:\Program Files (x86)\Steam\steamapps\common\Borderlands\Binaries\Borderlands.exe]

GAcquireInterface::TryAcquire() Address = 0x1a6b174 (filename not found) [in C:\Program Files (x86)\Steam\steamapps\common\Borderlands\Binaries\Borderlands.exe]

Address = 0x176c9fc0 (filename not found)

Address = 0x2a127764 (filename not found)

Address = 0x16a38d70 (filename not found)

Address = 0x1d142380 (filename not found)

Address = 0x1d142380 (filename not found)


---------------------------
OK
---------------------------

This issue has been solved by deleting the Borderlands folder your 'my games' folder. I probably could have deleted just the WillowEngine.ini, but I was tired and playing for keeps. Thanks to everyone for helping me play my game.

***********************

Rautakivi's contribution: I got mine working by deleting "...\windows username\documents\my games\borderlands" folder. Some file in that Borderlands folder messed up the game. If you don't use steam cloud or want to be sure with your savefiles, backup your saves before deleting from "...\my games\borderlands\savedata".


emperorike's contribution: Confirming Rautakivi's suggestion, with one caveat: you only need to delete WillowEngine.ini and WillowGame.ini from My Games \ Borderlands \ WillowGame \ Config.
There was a single line in Engine that mentioned default online subsystem still being gamespy. The other had the message of the day line about multiplayer still being offline due to gamespy shut-down.

You will have to redo your video settings, but keybinds remain intact.

I had already gone digging through those folders once, I don't know why I didn't open them up and ctrl-f gamespy before. Gah.

I'll also throw this up, for getting rid of those pesky intro movies:
http://forums.gearboxsoftware.com/showthread.php?t=79043

[emperor_ike]

Same message here, 3x in a row. Guess I'll try reinstalling.

[lyricsmaniac]

Bump. Reinstalling didn't work for me.

[emperor_ike]

Balls. Thanks for update; I guess I don't need to bother trying.
Subbing to discussion, maybe we'll see more folks with same problem, or word from Gearbox.

Will add, I have the 3 .dmp crashlogs from before and after verifying game cache, if anyone official can do anything with them, but they're all the same size and so presumably the same message as OP, since that was the window that popped up on crash.

[MINI]

Re-installing did not work out for me either!
I got an error message in the same style as the OP, and on the second try I got this message:

http://s27.postimg.org/o0k4et1qr/Untitled_2.png

Also are you running Windows 8 or 8.1 as well?

I am on 8.1 and a friend of mine is using Windows 7, and he does not seem to have this issue.

[lyricsmaniac]

General protection faults seem to be addressed here http://forums.gearboxsoftware.com/forumdisplay.php?f=93 and are easily found by a google search. My crash doesn't seem to be documented anywhere and the posts I found have no solutions.

[emperor_ike]

Win7 here. Friend that I've been playing with for as long as we've had the game does NOT have this crash problem.
Really weird.

[RStriker69 ♥]

Gamespy should no longer have any connection to a valid install, however, sometimes things get left behind, especially if it was installed before the conversion to steamworks.

I would look where borderlands is installed and in your user directory for borderlands references, delete everything, scour the place clean (except you might save your save files, as those will still work just fine).

There is another thing you might try that involves registry editing. It's perfectly safe as long as you follow instructions perfectly. I've posted it before and I'll paste it here once I find the post. More in a bit.

[RStriker69 ♥]

No guarantees this will work, but it's worth a try, Just be careful and do exactly as I list. If you do, literally nothing can go wrong that won't be fixed by running a progra twice.

Crossposted from another thread:

Welp, I fixed it, using an old registry edit from the last time steam (and its games) were screwing up on me.

First of all, know two things. Messing with your registry if you don't know what you're doing can make your computer not work at all, and second, that this particular fix literally cannot do anything bad as it's a compatability reference. If you delete those, and they were needed, they will be remade the next time you run them.

So, if you're still with me, press Windowkey + r (run) and type regedit. Once that's open, you want to collapse all the trees so you only see the base 5 or 6 and "computer". Right click computer, select export, this is your butt saver in case the cat runs across your keyboard and deletes windows octopus recognition software or someting similar. It'll take anywhere from several seconds to a few minutes.

Once that's done, expand HKEY_CURRENT_USER, then software, then microsoft, then windows NT, then currentversion, the appcompatflags, then look in the layers folder you see there. Somewhere on the list (it might be quite large) will be a reference to borderlands.exe. Delete the key, and you're done!

Incidentally, one can also delete anything that ends in exe from the layers folder and the persisted folder, which is one level deeper in compatability assistant. In addition, this process MAY need to be repeated in the exact same location, except HKEY_ LOCAL_MACHINE.

Remember, you're primarily looking for borderlands.exe, but if you so choose, you can delete any key there that ends in .exe, it may fix something, if you're having odd issues, and worst case is that it will be remade the next you run it, so no harm, no foul.

I certainly hope this works for you the way it did for me, but for the Love of god, BE CAREFUL editing your registry, and only touch the places I mentioned.

Good Luck and Be Well!

[lyricsmaniac]

okay Rstriker I will try this

[emperor_ike]

Forgot to update after I tried cleaning registry - no success.

[RStriker69 ♥]

Sorry mate, I'll keep an eye out for anything else to toss your way. Good Luck!

[MINI]

I just uninstalled nVidia PsysX and then re-installed it.
Fixed my problem at least.
Another note is that I also re-installed Borderlands, probably didn't have any effect, but still worth mentioning.

[lyricsmaniac]

thanks RStriker, but the registry entries were not present in the mentioned folders. Sad really. I think this game is Busted in it's current state. So far I have tried removing all Borderlands items from the computer with a program removeal tool, reinstalling the program, reinstalling PhysX, using the PhysX prereq that came with the game, doing the SecuROM removal tool, that did nothing I know of.

Now I don't really want to play the game. I just want it to run.

[Rausku]

I got mine working by deleting "...\windows username\documents\my games\borderlands" folder. Some file in that Borderlands folder messed up the game. If you don't use steam cloud or want to be sure with your savefiles, backup your saves before deleting from "...\my games\borderlands\savedata".

[emperor_ike]

Confirming Rautakivi's suggestion, with one caveat: you only need to delete WillowEngine.ini and WillowGame.ini from My Games \ Borderlands \ WillowGame \ Config.
There was a single line in Engine that mentioned default online subsystem still being gamespy. The other had the message of the day line about multiplayer still being offline due to gamespy shut-down.

You will have to redo your video settings, but keybinds remain intact.

I had already gone digging through those folders once, I don't know why I didn't open them up and ctrl-f gamespy before. Gah.

I'll also throw this up, for getting rid of those pesky intro movies:
http://forums.gearboxsoftware.com/showthread.php?t=79043