Results 1 to 5 of 5

Thread: Bioshock crashes to desktop + ALL custom settings are lost!

Hybrid View

  1. #1
    Join Date
    May 2008
    Posts
    3

    Bioshock crashes to desktop + ALL custom settings are lost!

    I started having this problem right around the tree farm level. I have done some Bios tweaking and some mild OCing, seems like BioShock doesnt respond well to overclocking. Anyways I am crashing to desktop with all settings lost upon reload afrer about 5 to 20 min of gameplay.

    Here is my system;

    MY SYSTEM!

    OS – Windows Vista 64 bit SP 1
    CASE - NZXT Zero Black/Silver Aluminum ATX Full Tower
    Power Supply - Kingwin ABT-800MA1S ATX 12V Ver.2.2 800W
    Video Card – 2x in SLI ZOTAC ZT-88TES3P-FCP GeForce 8800 GT 512MB 256-bit GDDR3 PCI Express 2.0 x16 HDCP
    CPU - Intel Core 2 Quad EE QX6700 SL9UL
    CPU FAN - ZALMAN CNPS9700 LED 110mm 2 Ball CPU Cooler (Always on Max Speed)
    Motherboard - EVGA 132-CK-NF78-A1 LGA 775 NVIDIA nForce 780i SLI ATX Intel Motherboard
    RAM - 2x 8GB total --- CORSAIR XMS2 4GB (2 x 2GB) 240-Pin DDR2 SDRAM DDR2 800 (PC2 6400) Dual Channel Kit Desktop Memory Model TWIN2X4096-6400C5DHX
    Optical Drive - SATA Pioneer DVD-RW & Samsung IDE CD-RW

    And here are my new BIOS settings.

    PCIe X16_3 10

    SPP <-> MCP Ref Clock. MHz 200.0

    FSB Mem Clock Mode Linked
    FSB Mem Ratio Synced Mode
    FSB QDR MHz 1600

    And Voltages Settings
    CPU Core 1.30000
    CPU FSB Auto
    Mem Auto
    nForce SPP Auto
    nForce MCP Auto
    SPP <-> MCP Auto

    MY SYSTEM!

    OS – Windows Vista 64 bit SP 1
    CASE - NZXT Zero Black/Silver Aluminum ATX Full Tower
    Power Supply - Kingwin ABT-800MA1S ATX 12V Ver.2.2 800W
    Video Card – 2x in SLI ZOTAC ZT-88TES3P-FCP GeForce 8800 GT 512MB 256-bit GDDR3 PCI Express 2.0 x16 HDCP
    CPU - Intel Core 2 Quad EE QX6700 SL9UL
    CPU FAN - ZALMAN CNPS9700 LED 110mm 2 Ball CPU Cooler (Always on Max Speed)
    Motherboard - EVGA 132-CK-NF78-A1 LGA 775 NVIDIA nForce 780i SLI ATX Intel Motherboard
    RAM - 2x 8GB total --- CORSAIR XMS2 4GB (2 x 2GB) 240-Pin DDR2 SDRAM DDR2 800 (PC2 6400) Dual Channel Kit Desktop Memory Model TWIN2X4096-6400C5DHX
    Optical Drive - SATA Pioneer DVD-RW & Samsung IDE CD-RW

    NOTE: I understand that all CPUs are like finger prints when it comes to oc’ing but Im still hoping that more advanced folk on this forum will give me a few pointers here and there. I also would like to run Prime95 overnight to see how my settings are reflecting on my system.


    And here are my new BIOS settings.

    PCIe X16_3 105

    SPP <-> MCP Ref Clock. MHz 200.0

    FSB Mem Clock Mode Linked
    FSB Mem Ratio Synced Mode
    FSB QDR MHz 1600

    And Voltages Settings
    CPU Core 1.42500
    CPU FSB 1.3
    Mem 2.1
    nForce SPP 1.35
    nForce MCP 1.5
    SPP <-> MCP 1.30




    This is what BIOS was indicating about 5 min after the GoW test.

    CPU 36c/97f
    Board 32c//90f
    MCP 49c/120f

    I am only experiencing these erros in BIOSHOCK, all other games are fine.
    What gives?

  2. #2
    What Nvidea driver do you use? I have the same card overcloacked from 300 mb to 500 and it works fine.

  3. #3
    Join Date
    May 2008
    Posts
    3
    Quote Originally Posted by Would You Kindly? View Post
    What Nvidea driver do you use? I have the same card overcloacked from 300 mb to 500 and it works fine.
    I am using Geforce 175.16, released on 5/16/08.

  4. #4
    Join Date
    Oct 2007
    Location
    Canada, eh.
    Posts
    4,116
    Bioshock is one of the very few games that will push a system to it's limits. I can't quote the exact source but I read a while back that one reviewer stated that Bioshock was the first game OR application that he had seen actually max out to 100% all his cores. What this means is that even though other software may be fine Bioshock because of its high resource utilization may just push your system over the fine line when you're overclocking. I do not recommened you overclock, quite the opposite I implore you to set your clocks back to where they are supposed to be. I once fried a very expensive graphics card through overclocking and the lesson has kept with me.

    For your settings going back to defaults after the crash, Bioshock creates a file called "running.ini" when you start it and deletes this file upon successful exit. If this file exists the next time Bioshock is started it takes it as an indicator that Bioshock crashed on the last run and will reload the default settings. This file can be found in the following locations:

    XP: C:\Documents and Settings\[Username]\Application Data\Bioshock
    Vista: C:\Users\[Username]\AppData\Roaming\Bioshock

    Again, please don't overclock! In the Celeron days there were wide margins for that, today you risk your system.

  5. #5
    Join Date
    May 2008
    Posts
    3
    Quote Originally Posted by headkase View Post
    Bioshock is one of the very few games that will push a system to it's limits. I can't quote the exact source but I read a while back that one reviewer stated that Bioshock was the first game OR application that he had seen actually max out to 100% all his cores. What this means is that even though other software may be fine Bioshock because of its high resource utilization may just push your system over the fine line when you're overclocking. I do not recommened you overclock, quite the opposite I implore you to set your clocks back to where they are supposed to be. I once fried a very expensive graphics card through overclocking and the lesson has kept with me.

    For your settings going back to defaults after the crash, Bioshock creates a file called "running.ini" when you start it and deletes this file upon successful exit. If this file exists the next time Bioshock is started it takes it as an indicator that Bioshock crashed on the last run and will reload the default settings. This file can be found in the following locations:

    XP: C:\Documents and Settings\[Username]\Application Data\Bioshock
    Vista: C:\Users\[Username]\AppData\Roaming\Bioshock

    Again, please don't overclock! In the Celeron days there were wide margins for that, today you risk your system.
    Well I kind of went back to default, I just dont understand why it started crashing so soon, even after only about 2 min of playing. SOmetimes even with BSOD. As usual all settings are lost.

Posting Permissions

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