Category: Main Games 1st Person Shooter Bioshock Steam Version


Version 1.1 purchased from STEAM.

Application Details:

Version: Steam Version
License: Retail
Votes: 1
Latest Rating: Gold
Latest Wine Version Tested: 2.21-staging

Maintainers: About Maintainership

Free Download Bioshock (Steam)

Test Results

Old test results
The test results you have selected are very old and may not represent the current state of Wine.
Selected Test Results

What works

  • Install via steam
  • Play via steam
  • Graphics and sounds

What does not

  • Sometimes, turning to a direction with the mouse doesn't work properly.
  • Loading can be longer than usual
  • Changing resolution forces the screen to go windowed. Restart the program saves the setting and fixes the problem



What was not tested

Level "Medical Pavillon" and after

Hardware tested


  • GPU:
  • Driver:

Additional Comments

Specs: CPU Intel i3-530 2.93Ghz GPU Nvidia Geforce GT 730 (346.47 non-free driver) RAM 8Gb Resolution 1920x1200

selected in Test Results table below
Operating systemTest dateWine versionInstalls?Runs?Used
ShowUbuntu 16.04 "Xenial" amd64 (+ variants like Kubuntu)Jan 12 20182.21-stagingN/A Yes YesGoldcdoublejj 
ShowGentoo Linux x86_64Feb 26 20172.20-stagingYes Yes YesGoldRob 
ShowArch LinuxSep 14 20161.9.18Yes Yes NoGoldmanero666 
ShowGentoo Linux x86_64Mar 10 20161.9.4Yes Yes NoGoldRazrFalcon 
CurrentManjaro LinuxMar 21 20151.7.38Yes Yes NoBronzean anonymous user 

Known Bugs

Bug # Description Status Resolution Other apps affected
6971 Mouse "escapes" window or is confined to an area in the full screen program CLOSED FIXED View
30123 Mouse pointer is confined in a box lesser than the full screen REOPENED View
31373 Bioshock cause Radeon to freeze (GPU lockup) RESOLVED NOTOURBUG View
34362 Bioshock takes way way way too long to load UNCONFIRMED View
40207 Bioshock CSMT crash UNCONFIRMED View
40977 BioShock 1.1 crashes when D3D10 is used CLOSED DUPLICATE View

Show open bugs

HowTo / Notes

Test Submissions ... how to avoid a rejection notice!!

These notes were last updated: 14 May 2018

Follow these guidelines to avoid embarrassment when your Test Submission is immediately rejected!!

  • Put your PC specifications in the Extra Comments section e.g. like your CPU and system memory.1
  • When adding test results please specify video card and driver version you are using.2
  • It's also useful to mention what desktop environment you are using (e.g. KDE, Gnome, Xfce, Unity...)
  • Specify what version of the Windows compatibility option you use in your Wineprefix (e.g. Windows XP, Windows 7, etc.).
  • Add a comment about what is not working for you.
  • Specify if you made any other changes to Bioshock e.g. installing a game "Mod", an .exe patch or details of any other modifications you made to the stock configuration files for the game.
  • Please indicate if your using Wine Staging and/or any additional patches applied - to the version of Wine you are using.
  • Please, don't submit test results like "Everything is working" or "Everything isn't working".

These guidelines ensure your submitted test results are actually relevant to other users of Wine and WineHQ.

1 The console version of the lshw utility is your friend. This command will dump your System hardware specification in a clean format. Post command and output in the Extra Comments section:

sudo lshw -short | egrep -v '(volume|disk|bus)'

2 inxi can be used to display information about your graphics card, and your OpenGL/ graphics driver versions. Post the command and output in the Extra Comments section:

inxi -G -c0

How to install

You will need:

  • A recent version of Wine, it's generally recommended to use the latest development release.
  • A video card with good 3D acceleration support (on your chosen flavour of Unix).
  • The native 3D driver should be correctly installed for that card.
  • It's not necessary to install Bioshock into a clean Wineprefix - but generally it's recommended.


This game will install on a vanilla version of Wine. First install the Steam Client as per Steam AppDB page. Then install the Bioshock game from your newly installed Steam client (as per Windows). See the Known Issues section below to fix current problems with Bioshock.

Known Issues

Mouse axes confined to 360° zones

There is still a bug present with Wine that causes you mouse to lock in a fixed 360° arc whilst playing Bioshock. This issue always manifests when you play Bioshock in a Wine Virtual Desktop arrangement. It will manifest occasionally when playing Bioshock in standard Wine arrangement (i.e. non-Virtual Desktop). The symptom is that you are unable to spin you character round on the spot (it will become locked at a fixed angle) or be unable to view your characters feet.

The only work around for  this issue is to enable the mouse warping override:

wine reg.exe ADD "HKEY_CURRENT_USER\Software\Wine\DirectInput" "/v" "MouseWarpOverride" "/t" "REG_SZ" "/d" "force"

DirectX 10.x Support

As of Wine version 1.7.53(+) there are tests enabled to see if your graphics hardware supports DirectX 10.x... Unfortunately a significant amount of the DirectX 10.x support has still to be implemented in Wine. The symptom for this issue is that Wine will crash immediately after you launch Bioshock.

The workaround is to disable support for the DirectX Graphics Infrastructure (DXGI) in Wine:

wine reg.exe ADD "HKEY_CURRENT_USER\Software\Wine\DllOverrides" "/v" "dxgi" "/t" "REG_SZ" "/d" ""

Changing Game Resolution

In game changing screen resolution can be a bit erratic. The symptom of this is that you change the screen resolution in the game menus and you end up with a "windowed version" of the game running (i.e. smaller than your full monitor real estate). This problem especially manifests when using Linux proprietary graphics drivers.

Option 1 : set game resolution manually before launching

To set the default Bioshock game resolution manually, from a terminal... Run this terminal command (changing first: Xres & Yres - as required):

export Xres=1920
export Yres=1080
sed -i -e '/^\(Fullscreen\|Menu\|Windowed\)Viewport\(X\|Y\)=/{s/X=.*$/X='"${Xres}"'/;s/Y=.*$/Y='"${Yres}"'/}' \
"$( find "${WINEPREFIX:-${HOME}/.wine}/drive_c" -type f -iname "Default.ini" )"

NB: this command won't work if you're using a separate Steam Library directory (external to your WINEPREFIX) to install Bioshock to!

Option 2 : set game resolution in-game

A rather hacky in-game workaround for this issue is to switch Bioshock to windowed mode and then back to full screen mode:

  • mouse Select Windowed Mode ON and your desired Resolution...

Graphics Options
 Resolution:   1920x1080
 Windowed Mode ON OFF

  • mouse Then set Windowed Mode OFF...
Graphics Options
 Resolution:  1920x1080
 Windowed Mode ON OFF

Audio Garbled or No Audio when using PulseAudio

If you find that your in game audio is garbled or non-existent it may be advisable to try Wine with pulseaudio support. Any supported version of Wine will provide the necessary audio driver support - if the pulseaudio flag was enabled at build time.


Bioshock red fog during game play. 

Note: this only seems to be a problem with older nVidia Geforce 7000 series cards.

Fixing this issue will involve changing 2 files in the Bioshock binaries folder with modified versions. Download the following 2 files:

Extract the files and copy the 2 files you extracted from the downloads into the directory:

"${WINEPREFIX}/drive_c/Program Files/Steam/steamapps/common/bioshock/builds/release"

... overwriting the files that are already there. Then retest.

Sound isn't working.

This issue could be related to the OpenAL library, you can fix this problem by setting the library openal32 to native (using winecfg).

General Troubleshooting.

  • Verify if your native video driver is installed properly (the 64-bit version of Wine will require the 32-bit libraries of your video driver to be installed - alongside the 64-bit version).
  • Install the Steam client and BioShock, to a separate/clean Wineprefix.
  • Set your Bioshock Wineprefix Windows version to Windows XP (using winecfg).
  • Close BioShock and Steam client, and reboot Wine by typing wineserver -k.
  • Check the integrity of the game through Steam client window, you can do that by right clicking on Bioshock (in your games list) and selecting Properties.
  • To rebuild the prefix you can reinstall Steam to a clean Wineprefix then copy over the directory:

    "${WINEPREFIX}/drive_c/Program Files/Steam/steamapps"

    ... i.e. your full Steam library that will include all the installed Bioshock files (from the existing/ old Wineprefix).


The following comments are owned by whoever posted them. WineHQ is not responsible for what they say.

Sooo, I found this strange bug
by dirtt on Thursday February 18th 2016, 7:30
And it in (maybe) Wine - or direct in Bioshock
after i reinstall ubuntu, wine, wtricks, steam, bioshock... everyone became works! And today it crashes again. ;)
The problem is in the savegame system.
There is two savegame directories of Steam's wine's Bioshock:
- (...)drive_c/users/%%username%%/Application Data/Bioshock - in wineprefix'
- (...)/home/%%username%%/Documents (in linux, with some variations)

...and maybe when someday savefiles will crashes (in Neptune's Bounty level - crashes everywhere, usual when saving) - This crashes start of Bioshock.

I just renamed '/home/.../Documents/Bishock' -> "Bioshock1", that allows Bioshock to start... without saves:) ... :(
Now I'm trying to repair savegames =/
RE: Sooo, I found this strange bug
by Rob on Thursday February 18th 2016, 9:07

I'd recommend running:
winetricks sandbox

That will remove the auto-generated "Documents", etc. symlinks from your WINEPREFIX to your Linux user's home folder. You would need to manually add back in the drive link mapping to / (Linux root) - if you need to run .exe's from outside of the WINEPREFIX. This is (typically) going to be a more "robust" setup!!

Take a peek in "${WINEPREFIX}/dosdevices" if that's unclear! For the default WINEPREFIX:
ls -ahl ~/.wine/dosdevices/

I'll check out - if Bisoshock saved games are still working - but they were last time I checked.

What version of Wine are you using btw?
RE: Sooo, I found this strange bug
by dirtt on Thursday February 18th 2016, 9:47
Deleting last savegame from '/home/%%username%%/Documents/Bioshock/SaveGames/' solved problem.
I think that this crashing damages last savefile in save moment (sometimes just crashes game, w/o saving, and game restars normally). And last save (which must become a "continue game"-savegame) - crash Bioshock at the start moment.

So... I have anyway uncomfortable regular crashes at that level, maybe because it's gigantic. There's almost no crashes before it.

Before reinstalling ubuntu I used 1.9.2 version of wine.
Now there is winehq 1.9.3~ubuntu15.10.1 (devel-release).
RE: Sooo, I found this strange bug
by Rob on Thursday February 18th 2016, 10:44
>> So... I have anyway uncomfortable regular crashes at that level, maybe because it's gigantic. There's almost no crashes before it.

I find Bioshock a bit tedious - so I haven't done very extensive gameplay!!

When playing Black Mesa Source on my Desktop's very old 8800 GTX I hit the GPU VRAM ceiling (768Mb) during gameplay. That was playing (on top of KDE4 - with compositing off) and at 1440p... On Windows 7 the VRAM usage would drop off sharply after level load points and then slowly rise. Under Wine the VRAM usage just seemed to keep slowly rising continuously... :-(

If you can - get a backtrace, from wine, up to the point of failure. It would be worth filing a bug for this issue. Have you tested monitoring your VRAM usage? It might be worth checking if it is exhausted when wine fails...

I keep all my saved games in the WINEPREFIX - along with my Steam games (when not in the Steam cloud). I tar-xz them up and back them up (shock horror) to my NAS - as regularly as possibly. If you're going to play through the whole of S.T.A.L.K.E.R.: SOC (like I did) your saved games represent many hours of "work"!!
Can't Run
by dirtt on Saturday February 6th 2016, 23:59
Ubuntu 15.10 x64 || Gallium 0.4 on NVE4 (drivers)
wine x32 prefix (XP), version of wine 1.9.2
Previously everything was good. Bioshock was flying well, sometimes crashes down when saving in Fishener's level.
It was discontinue to start someday.
Tried to setup on new clean prefix - steam - then bioshock... same problem.

When it's running - there is blackscreen, some artifacts on border. no start text, no sounds. Pressing any keys ends that and returns into Unity.
RE: Can't Run
by Rob on Sunday February 7th 2016, 7:23
OK. So lets approach this logically - something has changed!!

Bioshock won't change (unless you actively install a mod).

The Steam client will constantly get updates... But if you can launch games from Steam - then it's likely(!!) that isn't an issue in your case.

Did you update Ubuntu prior to the problem developing?

(1) If so did you change graphics driver stack in any way? Different versions of: kernel, mesa, your GPU driver, etc.?
(2) Did you change to a different version of Wine?

What console output do you get from running Bioshock? To check this you'd need to launch the game seperately from the Steam client (so that Wine attaches the game to your console)...

A "hack" I often to use is just to launch Steam in one tab of a terminal and launch "your game" in another tab of your terminal client. Setting up the Wineprefix variable in each tab - of course!!

The "proper way" to get console output from a Steam game is of course to launch the game directly - passing the game id to Steam. I think this avoids the game forking off in the background (and not writing to your terminal console).
RE: Can't Run
by dirtt on Sunday February 7th 2016, 9:12
About Steamclient - yes, I tried. I can't start one another game... So, I think there is a problem in GPU drivers. Nouveau drivers. I tried to get newest nouveau from experimental ppa's... nothing changes.

Yes, all of these have updates just everyday: ubuntu, drivers, steam.

I have no idea how can I get old version of drivers. Maybe this will solve the problem.
Broken in Wine 1.7.53+
by Julian James on Monday November 9th 2015, 0:34
I tried playing Bioshock with Wine 1.7.54 on Arch, and as soon as it opens a window it crashes. Rolling back Wine to 1.7.53 doesn't fix the problem, but in version 1.7.52 it works fine. A little bit of debugging shows the last call before it crashes:

0053:Call KERNEL32.WaitForSingleObject(00000138,0000003c) ret=7dc0c86c

But I don't know what I'm doing enough to figure out what's wrong.
RE: Broken in Wine 1.7.53+
by Rob on Wednesday November 11th 2015, 9:50

I did a a full regression test on Bioshock. It runs fine with the latest version of Wine (or Wine Staging) - but it needs the following library: d3d10 - to be disabled (easiest to do using winecfg / Libraries tab).

I'll update the Wiki later on...

Wine has started to expose the Direct 3D 10.x code paths (i.e. checking to see if your graphics card is comptabible). But most of the code to implement this (shim layer between DirectX 10.x & OpenGL) hasn't been written yet!! I suppose technically this isn't a bug...

This is the commit that introduced the offending GPU Adapter checks...
RE: Broken in Wine 1.7.53+
by Rob on Friday November 13th 2015, 10:12
FYI I've updated the Wiki with this info. Thanks again :-)
Works With Wine 1.7.12
by Carlos Rodriguez on Saturday February 15th 2014, 21:09
Tested on:

Wine 1.7.12 (compilado)
Nvidia Drivers 334.16 (.run package)
Linux Mint 16 KDE Edition 32Bit - Kernel PAE
CPU: INTEL Pentium G3220 (Nucleo Haswell a 22nm) 3.0Ghz (Dual-Core) Stock Clock
MEM: 8GB DDR3 1333 (2x4) Patriot value (128 bit dual channel: 21.3 gb/s)
GPU: Zotac Nvidia Geforce GT630 (GK208 28nm: 384 Shaders / 8 ROPS) Zone Edition Passive Cooling 2GB DDR3 1800Mhz a 64Bit (14.4Gb/s)
Game crashes after intro movie
by Joseph Bartolo on Sunday November 24th 2013, 8:04
Using wine 1.7.6, the game ceases to continue after the plane crash scene, along with some graphical artifacts if the resolution isn't altered.
Mouse sticks at edge of screen
by Michael Abbott on Wednesday September 25th 2013, 11:38
Back to the good old days (this with wine 1.7.2, no less): can't rotate in game more than about one full turn. Interestingly, I then find the mouse in the menu screen won't move past the middle of the screen!

Used to work about six to nine months ago.
RE: Mouse sticks at edge of screen
by Carlos Rodriguez on Saturday February 15th 2014, 21:08
try run game on window and this problem solve, and this tip works with many other gmes with similar problem

Thanks to for tip
RE: Mouse sticks at edge of screen
by rod cockerell on Monday November 10th 2014, 23:45
I use Wineskin and i used wine tricks and added WMO=FORCE and now it's fine.
No sound, or else game won't start
by Michael Abbott on Tuesday September 24th 2013, 13:50
I haven't tried playing Bioshock for a few months, now it will not start (very little reported in the console) unless I either disable sound with -nosound or else reassign the AudioDevice setting in default.ini, as advised by Rezkeh here:

Unfortunately in neither of these cases do I get any in-game sound.
RE: No sound, or else game won't start
by Michael Abbott on Tuesday September 24th 2013, 13:51
Drat, forgot some fundamentals:

Bioshock: Steam version
Wine: wine-1.6
Os: Xubuntu 13.04
RE: No sound, or else game won't start
by Michael Abbott on Wednesday September 25th 2013, 11:35
Ok, updated to wine 1.7, here's a startup log:

fixme:advapi:EventRegister {47a9201e-73b0-42ce-9821-7e134361bc6f}, 0x10035550, 0x10080c68, 0x10080c60
fixme:advapi:EventRegister {58a9201e-73b0-42ce-9821-7e134361bc70}, 0x10035550, 0x10080ca0, 0x10080c98
fixme:advapi:EventRegister {3fa9201e-73b0-43fe-9821-7e145359bc6f}, 0x10035550, 0x10080c30, 0x10080c28
fixme:advapi:EventRegister {1432afee-73b0-42ce-9821-7e134361b433}, 0x10035550, 0x10080cd8, 0x10080cd0
fixme:advapi:EventRegister {4372afee-73b0-42ce-9821-7e134361b519}, 0x10035550, 0x10080d10, 0x10080d08
fixme:process:GetProcessWorkingSetSize (0xffffffff,0x53e7f4,0x53e7f0): stub
fixme:thread:SetThreadIdealProcessor (0x124): stub
fixme:thread:SetThreadIdealProcessor (0x14c): stub
fixme:thread:SetThreadIdealProcessor (0x158): stub
fixme:win:EnumDisplayDevicesW ((null),0,0x53ef68,0x00000000), stub!
fixme:system:SystemParametersInfoW Unimplemented action: 59 (SPI_SETSTICKYKEYS)
fixme:thread:start_thread Started native thread 0000004f
fixme:thread:start_thread Started native thread 00000063
fixme:thread:start_thread Started native thread 0000005d
fixme:thread:start_thread Started native thread 0000005f
fixme:thread:start_thread Started native thread 00000058
fixme:avrt:AvSetMmThreadCharacteristicsW (L"Pro Audio",0x53ce2c): stub
fixme:thread:start_thread Started native thread 00000034
fixme:thread:start_thread Started native thread 00000052
fixme:thread:start_thread Started native thread 00000046
fixme:thread:start_thread Started native thread 00000044
fixme:thread:start_thread Started native thread 00000066
err:seh:raise_exception Unhandled exception code c0000005 flags 0 addr (nil)
err:ntdll:RtlpWaitForCriticalSection section 0xe37c94 "?" wait timed out in thread 0033, blocked by 001e, retrying (60 sec)

As above, switching [Engine.Engine]AudioDevice from FMODAudio.FMODAudioSubsystem to D3DDrv.D3DAudioDevice eliminates the crash, but there's no in-game sound.
RE: No sound, or else game won't start
by Rob on Wednesday September 25th 2013, 18:37
I checked out Bioshock on Wine 1.7.0 (Arch) and Wine 1.7.1-158-g88c2a18 (Gentoo) - latest Git build I made. The game runs OK (even on the radeon driver). Sound is dependent on my having a multilib Linux-native OpenAL package installed. The OpenAL ebuild have for Gentoo is 64-bit only and so I get no sound...

I am not seeing any crashing - except when I exit the game with "Exit to Windows". I get a Wine crash dialog popup at this point. Otherwise not seeing any significant problems on either OS (except the lack of sound on Gentoo).

I am not using any DLL overrides except for dwrite.dll (for Steam font rendering compatibility)... On Arch I have not had to create any Linux OpenAL configuration files at all (just using the defaults)...

What software have you installed in your Wineprefix?? What DLL overrides are you using?

Are you pulling Wine from the Ubuntu PPA? Does BioShock still crash if you set openal32.dll to builtin and install the 32-bit OpenAL package (alongside the 64-bit build of course)?
RE: No sound, or else game won't start
by Michael Abbott on Thursday September 26th 2013, 11:01
I have libopenal1 and libopenal1:i386 installed, version 1:1.14-4ubuntu1 (as reported through synaptic).

The only installed application in my Wineprefix is Steam ... together with all the games under that application, so that's a fair number.

I appear to have rather a lot of DLL overrides, don't know where they came from. All of these are overridden to native: devenum, dxdiag.exe, dxdiagn, quartz; and this one is disabled: d3d11. Guess I should try some changes there.

Removing all the DLL overrides makes no difference, nor does setting openal.dll to builtin.

My PPA (from which Wine is installed) is, which I presume is the standard PPA for the development 1.7 version. I'm running wine-1.7.2.

I think I've tried everything you've suggested, alas, thanks for the suggestions.
RE: No sound, or else game won't start
by Rob on Thursday September 26th 2013, 16:45
I had a little play on my Mint KDE install (basically Kubuntu 13.04). Jeez what a trainwreck Ubuntu is these days... Broken packages all over the place - the need to add in PPA's to stay current is really annoying... The Desktop experience is very poor in general. Reminds me why I stick to Arch and Gentoo these days... :-)

Steam doesn't render properly (with the Ubuntu Wine 1.7.2 PPA)... Bioshock won't launch... Looks more like a distro/ packaging issue - rather than anything to do with Wine. Mind you I can't get Mesa updated to 9.3 (due to the afore-mentioned package issues) - which won't help OpenGL rendering...

Btw I would highly recommend Arch as a Desktop distro. It's a painful learning curve, that takes a few months - to get used to using systemd and Package Management / Updates, etc... But this pays off in day-to-day usage: it's both stable and really fast...
RE: No sound, or else game won't start
by Michael Abbott on Friday September 27th 2013, 0:36
How interesting ... and depressing. In fact, I ran with Arch for about a year, but it was the constant churn of system breaking updates and finally the shift to systemd that drove me away. I'm tired of constant system maintenance, and I *liked* the old single file config and sysvinit.

Would I be any better off with Debian? Haven't tried running a Debian desktop for a some years.
RE: No sound, or else game won't start
by Rob on Friday September 27th 2013, 8:27
Michael, I'm genuinely one of the few unbiased folk out here!! I multiboot distros and keep them all current. So I have reasonable idea which is running the best.

Sadly I am biased to Desktop Environments - so I don't do Gnome 3/Cinnamon or Unity!! I occasionally dabble in Xfce (which is quite nice) and mainly use KDE.

In my experience once you learn how to use systemd properly it is beyond totally awesome. The people who rant about it simply haven't used it long enough / explored it enough. I switched to it early on - before Arch had even made it the default init daemon. It was quite hard to use initially. In my experience as systemd matured (and become much more stable) it now runs rings around Upstart - where the lack of any Canonical development effort shows.

With Arch I've learnt the hard way. Subscribe to RSS Update feed (where they tell you what is going to break next!!) Day to day usage (in between the updates!!) it's stable as a rock - even compared to Ubuntu (+derivatives)...

These days I prefer to use OpenSUSE (+Tumbleweed), Gentoo, or Arch. It's just easier to stay current. The OpenSUSE (Yast) package management is superior to Synaptic.

I understand that pure Debian doesn't give a good KDE experience. But I am tempted to test out SolydK (Debian-based KDE distro spin) in place of Kubuntu...
RE: No sound, or else game won't start
by Rob on Friday September 27th 2013, 9:13
Whoops forgot to mention. Solyd-XK (Xfce and KDE variants) has a good review here...

Main website...

The developer has been interviewed on the Mintcast podcast and is not a d**kw*d - like some people that come to mind (SolusOS!!)

I would be interested to see if it's the Canonical repackaging of stuff that's breaking Wine :-)

Btw I probably delete this thread in a week or two... As it probably won't help anyone else... Perhaps file a bug (either against Wine or the Ubuntu PPA version of Wine)??
RE: No sound, or else game won't start
by Michael Abbott on Monday September 30th 2013, 0:37
I think it wold be a shame to delete this thread. Although we don't have a resolution, not really, it *is* a useful indicator to other people having problems.

Actually, Bioshock does seem to be a particularly flaky app, searching for Bioshock troubles and crashes brings up a *lot* of stuff, none of it anything to do with wine...
Failure on Wine version 1.7.1
by Harry Bullen on Sunday September 8th 2013, 16:38
I could not get Bioshock to start at all for wine version 1.7.1
When I start the game in stream I see this error.

err:winediag:wined3d_dll_init The GLSL shader backend has been disabled. You get to keep all the pieces if it breaks.
fixme:process:GetProcessWorkingSetSize (0xffffffff,0x53e7f4,0x53e7f0): stub
fixme:win:EnumDisplayDevicesW ((null),0,0x53f688,0x00000000), stub!
fixme:dxgi:dxgi_adapter_CheckInterfaceSupport iface 0x13fb08, guid {9b7e4c0f-342c-4106-a19f-4f2704f689f0}, umd_version (nil) stub!
fixme:thread:SetThreadIdealProcessor (0xa4): stub
fixme:thread:SetThreadIdealProcessor (0xcc): stub
fixme:thread:SetThreadIdealProcessor (0xd8): stub
fixme:win:EnumDisplayDevicesW ((null),0,0x53ef78,0x00000000), stub!
fixme:system:SystemParametersInfoW Unimplemented action: 59 (SPI_SETSTICKYKEYS)
fixme:thread:start_thread Started native thread 00000016
fixme:thread:start_thread Started native thread 00000018
fixme:thread:start_thread Started native thread 00000050
err:seh:raise_exception Unhandled exception code c0000005 flags 0 addr (nil)
m files\steam\steamapps\common\bioshock\Builds\Release\bioshock.exe: pthread_mutex_lock.c:326: __pthread_mutex_lock_full: Assertion `robust || (oldval & 0x40000000) == 0' failed.
err:seh:raise_exception Unhandled exception code 80000101 flags 1 addr 0xf7701425
err:ntdll:RtlpWaitForCriticalSection section 0xe3674c "?" wait timed out in thread 002f, blocked by 0030, retrying (60 sec)

I have already checked that have direct rendering turned on and have my drivers set to alsa. I'm using ubuntu 13.04
RE: Failure on Wine version 1.7.1
by Rob on Wednesday September 11th 2013, 14:50
I've just been testing Wine 1.7.1 on my Desktop Gentoo install... Mainly with a view to trying out the new D3D command stream patches...

So naturally I've got to test the "vanilla" Wine works - before testing a version with the patches... I've got Bioshock installed on Steam - so it's no biggie to test it...

Steams working OK. Tested S.T.A.L.K.E.R. SOC - all OK. Bioshock crashes with a segmentation fault - when I try and change resolution (thanks Nvidia!!) - otherwise it runs pretty well.

Can you give a bit more info about your problem?

Is Wine installed from the Wine Team PPA?

What GPU hardware and drivers are you using? Have you got the 32-bit version of the GPU driver installed?

This is not a good sign about OpenGL support...
err:winediag:wined3d_dll_init The GLSL shader backend has been disabled. You get to keep all the pieces if it breaks.

Graphic problems during gameplay
by Mike on Wednesday September 4th 2013, 3:11
I have been trying to get Bioshock to run for quite some time, and with the Catalyst 13.8 beta drivers, the game runs, but I get terrible graphical glitches. They are worst when there is movement from the Splicers within the game. I think I saw a post that said there is a problem with ATI drivers. Can anyone help?
RE: Graphic problems during gameplay
by Rob on Thursday September 5th 2013, 0:57

I've got an older AMD Radeon 4650M gpu in my laptop. I am stuck on the (even worse) "Legacy" Catalyst branch (you think you've got problems!!) So I jumped at the chance to start playing with the radeon driver - since major UVD/SMC radeon code drops are being added into the 3.10/3.11 (respectively) Linux kernel version.

In general I've found that the 3.11 power-management support works extremely well. The 3.10 UVD support is excellent (and blows away the Catalyst XVBA crap). It's also actually quite nice to have modeset graphics (plymouth splash screens work - if you want them). It's so much easier to enable/disable second monitors, etc - without all the Catalyst rebooting crap.

Now on to the bad... 3D Support. I can run most games on the ultra lowest settings on the radeon driver. Support is only fully up to OpenGL 3.0 (although support for 3.1 is being implemented just now). For example Bioshock will run - but FPS is very sucky (even if you put the quality settings through the floor).

So in summary it's unlikely the proprietary AMD driver will ever be fixed (how many years do you wait before stop flogging a dead horse)... Compared to the Windows version - the Linux proprietary driver support is definitely in the "after thought category". The choices therefore are to wait for AMD to finish patching the FOSS radeon driver or just give up and buy an Nvidia card :-(

audio issues fix
by Jonas Jelten on Tuesday March 5th 2013, 17:28
i'm using wine with pulseaudio on gentoo

i got severe sound issues: stuttering, hangs, loops, weird stuff like that.

FIX: /etc/pulse/daemon.conf: default-sample-rate = 44100

after killing pulseaudio it worked.
RE: audio issues fix
by Artur h0m3 on Wednesday July 24th 2013, 13:49
Thanks, i will add to the Troubleshoot section :)
Graphics Issues?
by Amber J. on Monday May 7th 2012, 15:24
I'm running Bioshock on Precise Pangolin LTS through Wine 1.4. Specs are: 2.13Ghz Intel Pentium M (Dual Core), 4Gb RAM, Intel Ironlake M HD Graphics card, 320Gb HD, and Steam installed through Winetricks. I've run all fixes for Bioshock described in this forum and also upgraded my graphics card drivers and libraries using the method described here:

I'm still somewhat of a Linux noob, but as far as I can tell, this should run smooth. It installed easily and without problem--patch included--but I'm running into issues on the menu screen. The menu is invisible and so is the mouse. I enabled the "show cursor on Ctrl" and saw that the invisible mouse is stuck on the middle of the screen. What the frag is wrong? The mouse is stuck on the point shown on-screen but is invisible outside of the screenshot here:
RE: Graphics Issues?
by Flo G on Friday June 8th 2012, 14:11
Same Problem here. I can't seem to so or access the menu entries. Neither mouse nor keyboard seem to respond, though ESC ans SPACE create thi typical Bioshock *ring* sound and ALT-F4 will kill it.
RE: Graphics Issues?
by Amber J. on Saturday June 9th 2012, 14:22
Try seeing if your mouse will work in-game. Enable the "Ctrl to view cursor" setting. Mine would function somewhat as a ghost but would keep snapping back to the center of the screen as soon as I varied my control. Also, what are your specs? I'm not sure if this is a graphics issue, a registry problem, or a mouse issue. I put it under graphics because of the visible nature of the error.
Saving doesn't work.
by Christopher Cope on Thursday April 28th 2011, 23:04
I have over 100GB free on my drive, but if I try to save it says that there is not enough room on my hard drive.
RE: Saving doesn't work.
by Christopher Cope on Saturday April 30th 2011, 11:09
I figured it out. Wine was linked by default to my root folder as My Documents, which didn't have very much space left.
crash on new game
by Kevin Whitaker on Thursday November 4th 2010, 16:28
On starting the Steam version of Bioshock(with vcrun2005 and native libs set and -dx9) I get to the menu fine, but in the middle of loading a new game, it crashes. Tried different wine versions(from 1.1.44 to 1.3.6) and same in all versions. Also does the same with lowering the graphics settings.
RE: crash on new game
by Kevin Whitaker on Monday November 8th 2010, 0:00
I case this helps, here is a debug log with +relay on.(trimmed to part where crashes..4gb would be way to much to post here.) : Line 96
C++ Runtime error
by Jeremy on Friday October 29th 2010, 13:43
Hi, I followed the instructions fully and after installing trying to install the game on step 2 of 2 it crashes and says "program is trying to access the runtime library incorrectly.", and the console gives me "err:module:attach_process_dlls "MSVCR80.dll" failed to initialize". I've tried re installing VCRUN2005 via winetricks and even erasing and reinstalling a new wineprefix. I've got both MSVCP80.DLL and MSVCR80.DLL applied and native in the libraries tab but it still halts at this step. Help pls?
Game gives crash error.
by Steve on Tuesday August 24th 2010, 22:44
Every time I try to load the game, it crashes on me. Sometimes it continues to load anyway, but it just means that the graphics settings are constantly reset.

Anybody know how I can get a log of the error with Wine 1.3.1?
RE: Game gives crash error.
by Kris Blackhall on Wednesday August 25th 2010, 4:39
Wine 1.3.1 is quite unstable and many users of other apps have been reporting problems with it. My best advice is that you should install wine 1.2 which is stable. wine 1.2 will be in the repositories.

We will need a lot more information if we are going to be able to help you :-

Linux Distribution
Hardware - CPU - Graphics Card - RAM
What drivers you are using for the graphics card
How you installed the game (Disk or STEAM)

As for the log, just attempt to run the program in Terminal using the wine command :-

wine where/you/installed/bioshock.exe

Then if it fails the Terminal will inform of what went wrong.
RE: Game gives crash error.
by Kris Blackhall on Wednesday August 25th 2010, 4:43
Also, make sure you have followed the above instructions in the HOWTO section exactly. Not missing out any steps.

If you have missed out any steps (such as the DLL overrides) then the game will crash immediately.
Does not start
by Eric on Sunday November 15th 2009, 10:05
Hi. I have a standard Karmic installation on a Dell XPS laptop with 8888MGTX nvidia GC. I installed Steam correctly, my other games like HL2 work well.
I installed Bioshock and then launched it. The 1st time it installs directX. Now whatever I launch it nothing happens, I do have a process running, but nothing happens:
5435 ? Sl 0:10 c:\program files\steam\steamapps\common\bioshock\Builds\Release\bioshock.exe

Please how did you do it working ? Can you give more details on how it is supposed to work ? Thanks a lot ...
RE: Does not start
by Steve on Saturday December 26th 2009, 17:17
I am having this same problem. The game will churn, a process (bioshock.exe) will run, but then the Bioshock banner will grey out and nothing will happen.

Help, folks? Tried with Playonlinux with no success.
RE: Does not start
by Benoit Pierre on Tuesday December 29th 2009, 8:52
I had the same problem. Using the wine debugger I noticed the process get stuck in a call somewhere in the openal wine replacement: it tries to connect to pulseaudio. Since I have removed pulseaudio, it fails and seems to hang. I fixed the problem by making a copy of the openal system wide settings:

cp -vi /etc/openal/alsoft.conf ~/.alsoftrc

And then editing ~/.alsoftrc so the 'drivers' line only list ALSA:

drivers = alsa