Crash to desktop after todays patch (2015/02/25)

Discussion in 'Player Support' started by kickasspipes, Feb 25, 2016.

Page 2 of 2

  1. Ann Ominous

    CTD at 94% as well.

    Looks like a trend...
    Ann Ominous, Feb 25, 2016
    #21

  2. toxs

    the 55mb patch ?
    toxs, Feb 25, 2016
    #22

  3. Stiggee

    Latest verified nVidia drivers installed, with no effect on the 94% CTD here.

    Cue the Jeopardy theme music. :p

    Oh, lookie here! An acknowledgment from Daybreak Staff! :)

    Status: 2/25/2016 19:42 PST - We are currently investigating an issue with logging into the game.
    Stiggee, Feb 25, 2016
    #23 Last edited by Stiggee, Feb 25, 2016

  4. Wookuza

    Seems to be working now, no CTD anymore. - 10:54pm EST
    Wookuza, Feb 25, 2016
    #24

  5. Stiggee

    Yes! I can confirm that as well. No more 94% CTD !

    Thank you Daybreak! :)
    Stiggee, Feb 25, 2016
    #25

  6. kickasspipes

    Thanks Wookuza, I just got in too :cool:
    kickasspipes, Feb 25, 2016
    #26

  7. Wolfson

    Regretfully, still getting the crash to desktop at 94%. happened 3 times, then an 'inability to connect' occured.

    Correction. It's all Sony Services. PS2, H1Z1, and DCUO. All giving me the same error.
    Wolfson, Feb 25, 2016
    #27 Last edited by Wolfson, Feb 25, 2016

  8. mlmayo

    I get CTD @ 94% loading too. Windows 10. Didn't have any issues before the automatic patch download today. I'm had Steam validate the files, and am now re-downloading ~10 GB of data. I'm not sure if this will resolve the issue.
    mlmayo, Feb 25, 2016
    #28

  9. tootoll

    Crash to desktop after todays patch (2015/02/25)
    [IMG]
    tootoll, Feb 26, 2016
    #29

  10. Pfundi

    It wont, Steam uses an outdated client and the launcher will download all patches Steam just deleted and replaced with older versions again.
    .
    Oh and when the loading bar says 94% its connecting to the login server. So its neither your fault nor your PCs. Its a connection issue.
    Pfundi, Feb 26, 2016
    #30

  11. kickasspipes

    I was so focused on using a Euro friendly timestamp that I messed up the year... :|
    kickasspipes, Feb 26, 2016
    #31
Page 2 of 2