SC II keeps crashing after a few minutes

Discussion in 'StarCraft 2 Tech Support' started by mato007, Sep 2, 2010.

SC II keeps crashing after a few minutes

Discussion in 'StarCraft 2 Tech Support' started by mato007, Sep 2, 2010.

  1. mato007

    mato007 Guest

    Hello,
    please take your time to consider the difficulty I`am having with this game.
    So after a few minutes , sometimes 5 or sometimes almost 20 minutes , the game crashes with weird graphical artifacts occuring on my LCD screen, to be exact I present you a photo of my monitor after that error
    http://tinypic.com/r/258tt2p/7
    http://tinypic.com/r/20k8vih/7
    http://tinypic.com/r/214du2o/7
    So after this strange and confusing bug my computer also stops working , it seems that it freezes at that time and won`t go back to desktop or anything else , so I need to reboot my computer and start the game over , but after few short minutes it happens again and Iam really worried , because my system specifications aren`t any low and I cannot fully enjoy this magnificient game ...
    I also tried adding the frameratecapglue=30 & frameratecap=60 to the variables.txt in the starcraft II documents folder but it didn`t help
    here are the system specs: View attachment DxDiag.zip
     

    Attached Files:

    Last edited by a moderator: Sep 2, 2010
  2. TheXev

    TheXev Active Member

    Joined:
    Jul 29, 2010
    Messages:
    1,027
    Likes received:
    4
    Trophy points:
    38
    From:
    Corry PA USA
    Do you know what your motherboard make and model are? That additional information would provide be with alot more insight as to the problem. I am still looking over the dxdiag for information.
     
  3. mato007

    mato007 Guest

    The motherboard is Asus Striker II Formula with nvidia 780i nforce chipset
     
  4. TheXev

    TheXev Active Member

    Joined:
    Jul 29, 2010
    Messages:
    1,027
    Likes received:
    4
    Trophy points:
    38
    From:
    Corry PA USA
    Good, I have hands on experience with this board. Expect me to be very helpful shortly.
     
  5. mato007

    mato007 Guest

    Ok I`am hopefully awaiting your words of wisdom to resolve this problem mister.
     
  6. TheXev

    TheXev Active Member

    Joined:
    Jul 29, 2010
    Messages:
    1,027
    Likes received:
    4
    Trophy points:
    38
    From:
    Corry PA USA
    Just for kicks... what brand of RAM is in the machine? My buddy, with the same motherboard.. had a G-Skill duel channel kit, and one of the RAM chips was bad... he also had weird crap like those crashes happening, but he couldn't even get into the OS (couldn't get the BIOS to load).

    Try removing the RAM one stick at a time and using each chip alone in slot 1 of the motherboard.

    He RMA'ed the one bad 2GB chip and it just came back. System is working great now.

    If you had the same issue he did with bad RAM.. that would be just way too weird.
     
    Last edited: Sep 2, 2010
  7. mato007

    mato007 Guest

    My bios is loading with no problems at all , my cpu is overclocked from factory default which is 3,16 GHZ up to 4,005 GHZ
    And the rams are Corsair XMS2 DHX CM2X2048-6400C4DHX DDR2-800 DDR2 SDRAM
    Yes that would be weird having the exact same issue due to the faulty memory stick :)
     
  8. TheXev

    TheXev Active Member

    Joined:
    Jul 29, 2010
    Messages:
    1,027
    Likes received:
    4
    Trophy points:
    38
    From:
    Corry PA USA
    Try pulling the machine out of overclock for now, setting it back to default settings. How are you overclocking, via the BIOS or using Asus's overclock tool?

    What BIOS are you running? 2402 (dated 2010/04/23) is the newest. The newest BIOS can be found here. BIOS's dated newer then 2009/06/18 enhance memory compatibility.

    After installing the 2402 BIOS, remain at default settings and run Memtest86+ and see if it finds any bad RAM.

    While your CM2X2048-6400C4DHX isn't on the memory compatibility list, that doesn't mean that the chips won't work. Let's rule out a bad RAM chip first.