Results 1 to 7 of 7

Thread: BSOD after Bioshock Splash Screen

  1. #1
    Join Date
    Aug 2007
    Posts
    7

    BSOD after Bioshock Splash Screen

    Hi there:

    I need some help or advice. I've been playing the game with no problems so far while in game.

    The only problem I have is that SOMETIMES when I fire up Bioshock, after I see the splash screen, the system totally crashes with a BSOD. You hear a cracking noise from the audio and then I have to restart.

    It definetely has to do with audio. My sound card is a Blugears B-Enspirer which uses a Cmedia chip. I've debugged the minidump from the critical error, and it tells me that the guilty driver is cmudaxp.sys.

    Now the interesting thing is that this occurs sometimes, and ONLY when the game is about to play the cinematics of 2k games. When I'm able to get into play the game, the machine is totally stable and I'm able to play for hours with no problems whatsoever.

    Again, I get the BSOD when I fire up the game, but if it passes the videos, I can keep playing the game with no problems at all.

    Does it have to do with the codecs that the cinematics of game is using, and for some reson the sound card drivers are sensitive to them?

    I've tried using the latest drivers, and that didn't help. I've also enabled/disabled the sound echo in the options. (I'm not using EAX)

    I've also seen this post,

    "Originally Posted by Ainmer
    I was having the crash immediately after the Bioshock logo. I used Procmon to determine that immediately prior to the crash, it was accessing audio code. From there, I narrowed it down to the FMOD sound system.

    To fix -

    Edit your default.ini. Put a semi-colon in front of AudioDevice=FMODAudio.FMODAudioSubsystem, and add the following line right after it:
    AudioDevice=D3DDrv.D3DAudioDevice

    After edits, that part of the config file should look like this:

    ;AudioDevice=FMODAudio.FMODAudioSubsystem
    AudioDevice=D3DDrv.D3DAudioDevice"

    Following with the problem, I don't know if that the failure that he is talking about is a simple crash to desktop, or if it's a critical total BSOD crash.

    I think 2k should address this issue, with the sound. I play other games in my machine, and I can say it's 100% stable, and even this game is totally stable if I'm able to pass the video when you start after the splash screen.

    Is there also a way to deactivate the presentation videos?

    Thanks a bunch in advance!

  2. #2
    Join Date
    Aug 2007
    Posts
    7
    Anyone? Please help!!

  3. #3
    Join Date
    Aug 2007
    Posts
    299
    You will need to rename the files LogoVid.bik and also 2KG_Logo_720P.bik found in C:\Program Files\2kgames\Bioshock\Contents\Binkmovies . This should go straight to the main menu.

    The problem could be a Direct X directsound issue or a possible codecs.
    If you are using Windows XP here is tool that did fix a BSOD issue I had with Elder Scrolls, but you do have to use it at your own risk.
    http://nightmare2013.brashendeavors.net/
    Last edited by Tech JT; 09-04-2007 at 01:30 PM.

  4. #4
    Join Date
    Aug 2007
    Posts
    7
    Thanks so much for the reply. I will try what you tell me...

  5. #5
    Join Date
    Aug 2007
    Posts
    7
    It doesnt work!

    This is the only game that I had crashing from the beginning i Windows XP.

    I've played Lost Planet with no issues whatsoever, and many other games without BSOD.

    I made the trick to jump the initial cutscenes (bik files).
    By adding bioshock.exe -dx9 -nointro

    I'm still crashing randomnly after the Bioshock splash screen.

    Help please!!

  6. #6
    Join Date
    Aug 2007
    Posts
    1,172
    When you get the BSOD what is the error on here?

    Also please post The Specs for your PC as well as driver versions.

  7. #7
    Join Date
    Sep 2007
    Location
    london
    Posts
    6
    I did see one person who solved the Nvidia crashes by reinstalling dx9, however, a huge portion of people who were experiencing constant nvidia related crashes reported disabling high detail shaders as a viable workaround.

    http://forums.2kgames.com/forums/sho...hlight=shaders

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •