test content
What is the Arc Client?
Install Arc
Options

BSOD from ATI driver in Starbase 24

SystemSystem Member, NoReporting Posts: 178,019 Arc User
edited January 2010 in PC Gameplay Bug Reports
I'm getting a BSOD related to my ATI driver. Happens only in starbase 24 and it's consistent, though not in the same spot. I have not BSODed in any part of the game except for starbase 24. I have run other ground missions and space missions for hours on end with no issues.

I get a lot of bad lag in there, when things start shooting and running. I get to the 3rd or 4th scientist and I BSOD. After this the game forgets any progress and items I have picked up on the base.

After the crash I upgraded to the latest ATI 4000 series drivers (9.12), no luck. I decided to find the matching drivers from ASUS, the maker of my 4870, and got their version (8.69) and again, no luck, BSOD.

Also, as a side note, many of the NPC's refer to starbase 24 as starbase 13.
Post edited by Unknown User on

Comments

  • Options
    Archived PostArchived Post Member Posts: 2,264,498 Arc User
    edited January 2010
    I tried to post a DXDIAG but the forum is truncating to 11000 characters and I need 35k to post it. FYI MODS, you should open the threads up so that we can post DXDIAG info for your study.

    The offending part of my PC:
    Display Devices
    Card name: ASUS EAH4870 series
    Manufacturer: ATI Technologies Inc.
    Chip type: ATI Radeon Graphics Processor (0x9440)
    DAC type: Internal DAC(400MHz)
    Device Key: Enum\PCI\VEN_1002&DEV_9440&SUBSYS_03061043&REV_00
    Display Memory: 1024.0 MB
    Current Mode: 1680 x 1050 (32 bit) (60Hz)
    Monitor: Plug and Play Monitor
    Monitor Max Res: 1600,1200
    Driver Name: ati2dvag.dll
    Driver Version: 6.14.0010.7039 (English)
    DDI Version: 9 (or higher)
    Driver Attributes: Final Retail
    Driver Date/Size: 11/28/2009 21:41:00, 300544 bytes
    WHQL Logo'd: No
    WHQL Date Stamp: None
    VDD: n/a
    Mini VDD: ati2mtag.sys
    Mini VDD Date: 11/28/2009 23:54:00, 4524544 bytes
    Device Identifier: {D7B71EE2-D700-11CF-8C68-0C23A1C2CB35}
    Vendor ID: 0x1002
    Device ID: 0x9440
    SubSys ID: 0x03061043
    Revision ID: 0x0000
    Revision ID: 0x0000
    Video Accel: ModeMPEG2_C ModeMPEG2_D
    Deinterlace Caps: {6E8329FF-B642-418B-BCF0-BCB6591E255F}: Format(In/Out)=(YUY2,YUY2) Frames(Prev/Fwd/Back)=(0,0,1) Caps=VideoProcess_YUV2RGB VideoProcess_StretchX VideoProcess_StretchY DeinterlaceTech_PixelAdaptive
    {335AA36E-7884-43A4-9C91-7F87FAF3E37E}: Format(In/Out)=(YUY2,YUY2) Frames(Prev/Fwd/Back)=(0,0,0) Caps=VideoProcess_YUV2RGB VideoProcess_StretchX VideoProcess_StretchY DeinterlaceTech_BOBVerticalStretch
    {6E8329FF-B642-418B-BCF0-BCB6591E255F}: Format(In/Out)=(UYVY,UYVY) Frames(Prev/Fwd/Back)=(0,0,1) Caps=VideoProcess_YUV2RGB VideoProcess_StretchX VideoProcess_StretchY DeinterlaceTech_PixelAdaptive
    {335AA36E-7884-43A4-9C91-7F87FAF3E37E}: Format(In/Out)=(UYVY,UYVY) Frames(Prev/Fwd/Back)=(0,0,0) Caps=VideoProcess_YUV2RGB VideoProcess_StretchX VideoProcess_StretchY DeinterlaceTech_BOBVerticalStretch
    {3C5323C1-6FB7-44F5-9081-056BF2EE449D}: Format(In/Out)=(NV12,0x3231564e) Frames(Prev/Fwd/Back)=(0,0,2) Caps=VideoProcess_YUV2RGB VideoProcess_StretchX VideoProcess_StretchY DeinterlaceTech_PixelAdaptive
    {552C0DAD-CCBC-420B-83C8-74943CF9F1A6}: Format(In/Out)=(NV12,0x3231564e) Frames(Prev/Fwd/Back)=(0,0,2) Caps=VideoProcess_YUV2RGB VideoProcess_StretchX VideoProcess_StretchY DeinterlaceTech_PixelAdaptive
    {6E8329FF-B642-418B-BCF0-BCB6591E255F}: Format(In/Out)=(NV12,0x3231564e) Frames(Prev/Fwd/Back)=(0,0,1) Caps=VideoProcess_YUV2RGB VideoProcess_StretchX VideoProcess_StretchY DeinterlaceTech_PixelAdaptive
    {335AA36E-7884-43A4-9C91-7F87FAF3E37E}: Format(In/Out)=(NV12,0x3231564e) Frames(Prev/Fwd/Back)=(0,0,0) Caps=VideoProcess_YUV2RGB VideoProcess_StretchX VideoProcess_StretchY DeinterlaceTech_BOBVerticalStretch
    Registry: OK
    DDraw Status: Enabled
    D3D Status: Enabled
    AGP Status: Enabled
  • Options
    Archived PostArchived Post Member Posts: 2,264,498 Arc User
    edited January 2010
    This is happening with ALL ground combat, not just Starbase 24.

    I have zero issues with space combat, but ground combat = Killer lag for 30 seconds or so into any fight and during animations involving AOE weapons and explosions it seems. I don't consider my PC to be antiquated in any way so I'm wondering why the lag is so bad. My fear is that I'm looking at a similar scenario to COH where the code was not set up well to work with ATI cards. Then again, it could just be me, I don't see a ton of people complaining about blue screening.

    The odd thing is, after certain actions in the fights, I have zero lag otherwise. I know there will be some more work done to optimize the code, and I could turn some settings down. I didn't expect to see this much lag with my PC though. But again, there's still work to be done. Not complaining, just putting this up here to see if others are getting the same issues and if they found a work around? I'd love to finish the missions without a BSOD. I'm really starting to love this game, it grows on you...

    Intel quad core, 2.4
    ATI (asus) 4870
    4gb Ram
    Raptor HDD
    X-Fi sound
    XP Pro SP3 (32bit)
Sign In or Register to comment.