It seems that you're using an outdated browser. Some things may not work as they should (or don't work at all).
We suggest you upgrade newer and better browser like: Chrome, Firefox, Internet Explorer or Opera

×
avatar
LordAbstellhaken: It's an 11 year old game. Get over it.

EDIT: Bioshock 2 has random crashes. I was fighting against a Big Sister and it just crashed out of the blue. This happened twice. So do not go easy on that Quicksave button
Maybe you just suck. Get over it.
avatar
LordAbstellhaken: EDIT: Bioshock 2 has random crashes. I was fighting against a Big Sister and it just crashed out of the blue. This happened twice. So do not go easy on that Quicksave button

EDIT2: It crashed 3 times in 20 minutes. Always in a fight. So, I can confirm this version is just as bad as the steam version. Wait for the Classic release and don't buy this, yet.
Thanks for the heads-up. I've heard several people complain that the Remasters still randomly crash during combat even with keyboard + mouse so the instability isn't just caused by that "using a controller on the map screen" known bug, but rather the Classic (Unreal 2) to Remastered (Unreal 3) 'upgrade' still has multiple other unfixed bugs on all versions (Steam & GOG). Like you, I'm still waiting for GOG to add the Classic versions too. Hopefully it's the same as Humble's DRM-Free Bioshock 1 version which has been very stable all these years.
avatar
22raider: MSVCR110.dll belongs to Microsoft Visual C++ redistributable libraries. I don't know what version of these libraries Bioshock needs. Try to reinstall all of them: 2005, 2008, 2010, 2012, 2013, and 2017. In addition, install both 32 and 64 bits versions.
avatar
servobeupstry: The GOG standalone installer is supposed to install the MSVC libraries for you. In my case it installed:
- 2010 x86 10.0.40219
- 2012 x86 11.0.61030
- 2017 x86 14.14.26429
Thanks for the suggestions. According to the MSVCR110.dll properties, it belongs to Visual C++ 2012. Just in case, though, I reinstalled:
- 2010
- 2012 update 4
- 2013 update 5
- 2015 update 3
- 2017

This has possibly fixed the MSVCR110.dll error in the sense I haven't seen it again but I still encounter random crashes including during saving, one error type from BioshockHD.exe itself, the other from d3d11.dll, in addition to freezes which require a reboot and does not result in an error report. I've given up trying to fix it and just living with it.
There is frequent crash-to-desktop in Bioshock 2 that always occurs randomly during fights. I happens to me, too.

There is possible fix for this, that removes this crash or at least makes it less frequent (as in my case):

You open up the bioshock.ini under Appdata/Roaming/BioshockHD and look for the entries

TextureStreamingDistanceLimit
TextureStreamingMemoryLimit

There you set the MemoryLimit as high as you want, but not higher than your Graphics Card can support.
512.000 is the default and you might wanna set it to 2048. Higher if the game keeps crashing as often as before.

The DistanceLimit should be reduced to about 9000 to 10000, (Default is like 30k !!??) lower it even more if the game keeps crashing.

Another thing you could try, in tandem or as an alternative to tinkering with the ini file is adding the start-up command

-dx9

You can do it with gog Galaxy under the preference tab on the games library entry.
Hopefully this helps some of you guys, because as of myself it only reduced the frequency of crashes.
Try setting resolution to 1366×768. Worked for me so far.


quote_24]
I have been playing the GOG Bioshock HD remaster for about 10 hours. It either crashes to the desktop or freezes every 30 to 60 minutes. Frequently this is whilst saving a game. The Windows event viewer image attached shows the fault.
avatar
twistedpony: I have been playing the GOG Bioshock HD remaster for about 10 hours. It either crashes to the desktop or freezes every 30 to 60 minutes. Frequently this is whilst saving a game. The Windows event viewer image attached shows the fault.

Things that have not helped:
- updating graphics drivers to latest
- running in windowed mode or full screen mode
- disabling ful screen optimization on BioshockHD.exe
- running in Windows 8 compatibility mode
- running in Windows 7 compatibility mode. Would not start because it complained about a missing Windows 7 SP 1

Configuration:
- Windows 10, latest updates
- Core i5-6600
- NVidia GTX 750 Ti
- Asus Xonar DX

The crashing is really annoying but I am enjoying the game otherwise. I have taken to saving very, very, very frequently. I also back up the saves regularly just in case. I may also start quitting and restarting every 30 minutes or so because when it crashes during saving of a game is the most annoying. It's quite annoyingly confusing to try and remember what one was doing in the previous save, even when saving frequently.

Has anyone managed to play the GOG version for a decent number of hours without problems?
Have you tired the fixes at:

https://pcgamingwiki.com/wiki/BioShock_Remastered

I was playing bioshock 2 remaster without problems to start with. Then it started crashing about halfway through. Not very often but enough to be annoying.
Adjusting the TextureStreamingMemoryLimit to my GPU's VRAM and setting TextureStreamingDistanceLimit to 10000 in the Bioshock.ini file located %APPDATA%\BioshockHD\Bioshock\ fixed it for me
Post edited March 19, 2019 by HG1995
avatar
HG1995: I was playing bioshock 2 remaster without problems to start with. Then it started crashing about halfway through. Not very often but enough to be annoying.
Adjusting the TextureStreamingMemoryLimit to my GPU's VRAM and setting TextureStreamingDistanceLimit to 10000 in the Bioshock.ini file located %APPDATA%\BioshockHD\Bioshock\ fixed it for me
Just placebo/luck: will crash for sure sooner or later. Those ini settings are actually useless: they only define the cache buffer for textures but won't fix the crashes.
Only 2K games can fix this broken game.
Post edited May 09, 2019 by hexaae
avatar
HG1995: I was playing bioshock 2 remaster without problems to start with. Then it started crashing about halfway through. Not very often but enough to be annoying.
Adjusting the TextureStreamingMemoryLimit to my GPU's VRAM and setting TextureStreamingDistanceLimit to 10000 in the Bioshock.ini file located %APPDATA%\BioshockHD\Bioshock\ fixed it for me
avatar
hexaae: Just placebo/luck: will crash for sure sooner or later. Those ini settings are actually useless: they only define the cache buffer for textures but won't fix the crashes.
Only 2K games can fix this broken game.
It didn't crash once after making the changes. Didn't need to try any oif the other fixes at PCGamingwiki
avatar
hexaae: Just placebo/luck: will crash for sure sooner or later. Those ini settings are actually useless: they only define the cache buffer for textures but won't fix the crashes.
Only 2K games can fix this broken game.
avatar
HG1995: It didn't crash once after making the changes. Didn't need to try any oif the other fixes at PCGamingwiki
As you can read everywhere on the net it still crashes for a lot of users and changing those settings didn't solve the issue at all. The problem with this game is in rendering engine and lighting system, not with texture buffers.
Many people posted their receipe but was actually just placebo: the crashes in these games are so randomic that just by luck you can play it without issues for 4-5 days 2 hours a day, and then all of a sudden it still crashes randomly...
I know it because I've been desperately trying to make it stable for 1 year, and I have written some help guides too about workarounds for this buggy game. At present I'm testing a combo of multiple fixes involving NVidia Profile Inspector + MS Application Compatibility Toolkit...
Post edited May 12, 2019 by hexaae
avatar
HG1995: It didn't crash once after making the changes. Didn't need to try any oif the other fixes at PCGamingwiki
avatar
hexaae: As you can read everywhere on the net it still crashes for a lot of users and changing those settings didn't solve the issue at all. The problem with this game is in rendering engine and lighting system, not with texture buffers.
Many people posted their receipe but was actually just placebo: the crashes in these games are so randomic that just by luck you can play it without issues for 4-5 days 2 hours a day, and then all of a sudden it still crashes randomly...
I know it because I've been desperately trying to make it stable for 1 year, and I have written some help guides too about workarounds for this buggy game. At present I'm testing a combo of multiple fixes involving NVidia Profile Inspector + MS Application Compatibility Toolkit...
Never claimed it would work for everyone it just worked for me. The crashes I was having were at every fight.

Plus I got the fix from steam community not pcgamingwiki.

I know your'e trying to get the remastered to run smoothly without problems but why not just play the original since that is included.

Also report it to 2K. I don't think they're keeping an eye on any forums here or steam that are listing the Remasters problems.

https://support.2k.com/hc/en-us/articles/203354487-General-Info-For-2K-Customer-Support
Post edited May 13, 2019 by HG1995
avatar
HG1995: I was playing bioshock 2 remaster without problems to start with. Then it started crashing about halfway through. Not very often but enough to be annoying.
Adjusting the TextureStreamingMemoryLimit to my GPU's VRAM and setting TextureStreamingDistanceLimit to 10000 in the Bioshock.ini file located %APPDATA%\BioshockHD\Bioshock\ fixed it for me
I finally got BS2 Classic to run under DX10 without issues by changing the first setting you listed and not touching the second. So far, I've gotten up to Siren Alley without crashing.

And I hate to beat an undead horse, but am I the only one who thinks the remaster actually looks a little bit worse than the original?

EDIT: Never mind. It crashed three times in a row once I got to Persephone. Looks like it's back to DX9 and unmastered graphics for me.
Post edited May 31, 2019 by doubleagent74
hi, im having problems with bioshock remastered , it crashes when i save or after playing a few hours
The original version of Bioshock 2 has always had crashing problems with anyting above Windows Vista.
avatar
HG1995: I was playing bioshock 2 remaster without problems to start with. Then it started crashing about halfway through. Not very often but enough to be annoying.
Adjusting the TextureStreamingMemoryLimit to my GPU's VRAM and setting TextureStreamingDistanceLimit to 10000 in the Bioshock.ini file located %APPDATA%\BioshockHD\Bioshock\ fixed it for me
avatar
doubleagent74: I finally got BS2 Classic to run under DX10 without issues by changing the first setting you listed and not touching the second. So far, I've gotten up to Siren Alley without crashing.

And I hate to beat an undead horse, but am I the only one who thinks the remaster actually looks a little bit worse than the original?

EDIT: Never mind. It crashed three times in a row once I got to Persephone. Looks like it's back to DX9 and unmastered graphics for me.
Hate to disappoint you, but the original ,urenmastered version of Bioshock 2 has crashing problems with DX 10. This is all versions, Steam or non Steam.
Post edited June 15, 2019 by dudalb
On furthrer investigation, a number of games the use the version of the Unreal engine that the originasl Bioshock 2 uese have the same issue. There are a number of fixes out there. For me adding -dx9 to the launch command fixed the problem, and I did not see any notcible change in graphic quality.
avatar
hoover1979: One issue that both remasters have is the sound completely craps itself if Windows has the audio set higher than 24bit 48,000hz (and I prefer to have my audio set to 24bit 96,000Hz 5.1) so I have to change my windows sound settings every time I play them. (The exact same issue as Doom 2016).
I'm having sound issues too with the game (BioShock Infinite Edition) and I use a SoundBlaster ZxR with highest possible settings (24 Bit, 192.000 Hz)

It's not like the game itself crashes but when I play a while the game produces "disturbance sounds" such as the one that occurs when a Windows computer shows a BSOD.

I wonder where that comes from?