The Telltale forums are now read only. Past posts will stay available to browse, but new posts and replies have moved to our official Discord.

Join the conversation on Discord

Freezing/BSOD/general problems with playing TWD

Ok, so I bought the steam version of TWD (plus the 400 Days DLC) earlier today, and I've had some pretty big problems- that meaning I can't even get past the second dialog choice.

The problems I've had are:

The screen freezing for anywhere between 5 and 15 seconds, flickering black, then showing the screen again which is still frozen, just with everything on the screen being in the place they would if there wasn't a problem. This has happened before, but only once or twice on one other steam game (Amnesia: The Dark Descent). I think it has something to do with a driver (maybe?) crash or something, but ultimately I've never gotten around to sorting it out because it wasn't a big problem before. This only happened once out of around 10 tries (in a row) of playing TWD.

The next problem is a BSOD. Basically, I get to the point where you see Lee's face for the first time, and bam, instant BSOD in a can. After a few seconds, my computer starts up again. This happened twice.

The last problem, and the problem that took up the other seven tries is after a couple seconds of seeing Lee for the first time while he's in the police car the screen turns black for about 5 to 10 seconds, then white for 5 to 10 seconds, goes back to normal as if the screen didn't do anything weird at all for about another 5 to 10 seconds, then repeats that process.

I've tried to fix this by uninstalling and re-installing the game, verifying the game cache files, running it as an administrator, restarting my computer and changing the in-game screen resolution. No luck. This has never happened to me before with my computer, and everything else still runs as perfectly as ever, this only happens when I try to play TWD. If I haven't screwed up on something there should be a support_data_pc.zip attached, in case that will help. So, well, please help?

-
Er, apparently I did screw up on attaching that file. I think. This should work.
http://www.telltalegames.com/forums/attachment.php?attachmentid=4142&stc=1&d=1375709484

Comments

  • DjNDBDjNDB Moderator
    edited August 2013
    Card name: AMD Radeon HD 7800 Series
    Driver Date/Size: 12/20/2012 05:38:04, 1151488 bytes

    Description: Speakers (Realtek High Definition Audio)
    Date and Size: 5/24/2011 22:04:04, 2881256 bytes

    Please try installing the latest Graphics driver and Sound driver.

    I can also take a look at the Bluescreen messages.
    Please navigate to C:\Windows\Minidump
    Zip the *.dmp files, and upload the .zip archive to an instant filehoster and post the download link.
  • edited August 2013
    DjNDB wrote: »
    Please try installing the latest Graphics driver and Sound driver.

    I can also take a look at the Bluescreen messages.
    Please navigate to C:\Windows\Minidump
    Zip the *.dmp files, and upload the .zip archive to an instant filehoster and post the download link.

    Well, I updated things, and I still get a BSOD. I accidentally somehow erased the dmp files from before- no idea how, but there's one left since I just got the BSOD. My computer hates me and I hate it back. Well, here it is. Any ideas?
  • edited August 2013
    Something interesting I found out: It's only episode 1 that's giving me any problems. I played a bit through episode 2 with exactly zero problems. Seems all the blinking stuff, that being the first and third problems, comes from a display driver (the exact message I got was "Display driver amd stopped working and has recovered"), which probably should have been sorted out when I updated the driver, right? I still have no idea about why the BSOD happens, though it might have something to do with that. I thought I should mention this in case it helps.
  • DjNDBDjNDB Moderator
    edited August 2013
    The bluescreen is also graphics related. I don't know why the graphics driver crashes though. It could be a hardware or software issue.
    In case of a software issue a fresh windows installation should help. If it doesn't, it's probably a hardware problem.
    5: kd> !analyze -v
    *******************************************************************************
    * *
    * Bugcheck Analysis *
    * *
    *******************************************************************************

    Unknown bugcheck code (a0000001)
    Unknown bugcheck description
    Arguments:
    Arg1: 0000000000000005
    Arg2: 0000000000000000
    Arg3: 0000000000000000
    Arg4: 0000000000000000

    Debugging Details:


    CUSTOMER_CRASH_COUNT: 1

    DEFAULT_BUCKET_ID: WIN7_DRIVER_FAULT

    BUGCHECK_STR: 0xA0000001

    PROCESS_NAME: System

    CURRENT_IRQL: a

    TAG_NOT_DEFINED_c000000f: FFFFF880032D4FB0

    LAST_CONTROL_TRANSFER: from fffff88008229c5c to fffff800030cac00

    STACK_TEXT:
    fffff880`032cd708 fffff880`08229c5c : 00000000`a0000001 00000000`00000005 00000000`00000000 00000000`00000000 : nt!KeBugCheckEx
    fffff880`032cd710 00000000`a0000001 : 00000000`00000005 00000000`00000000 00000000`00000000 00000000`00000000 : atikmdag+0x23c5c
    fffff880`032cd718 00000000`00000005 : 00000000`00000000 00000000`00000000 00000000`00000000 fffff880`07b52127 : 0xa0000001
    fffff880`032cd720 00000000`00000000 : 00000000`00000000 00000000`00000000 fffff880`07b52127 fffff880`032cd770 : 0x5


    STACK_COMMAND: kb

    FOLLOWUP_IP:
    atikmdag+23c5c
    fffff880`08229c5c ?? ???

    SYMBOL_STACK_INDEX: 1

    SYMBOL_NAME: atikmdag+23c5c

    FOLLOWUP_NAME: MachineOwner

    MODULE_NAME: atikmdag

    IMAGE_NAME: atikmdag.sys

    DEBUG_FLR_IMAGE_TIMESTAMP: 5154fbf8

    FAILURE_BUCKET_ID: X64_0xA0000001_atikmdag+23c5c

    BUCKET_ID: X64_0xA0000001_atikmdag+23c5c

    Followup: MachineOwner
  • edited August 2013
    DjNDB wrote: »
    The bluescreen is also graphics related. I don't know why the graphics driver crashes though. It could be a hardware or software issue.
    In case of a software issue a fresh windows installation should help. If it doesn't, it's probably a hardware problem.

    I'm guessing fresh installation/hardware problem = backing everything up and then needing to reinstall the entirety of everything, eh? That sounds about right considering my luck. I guess I'll see if the guy who made my computer can do anything that doesn't require something so... terrifying for one game. I have to admit, I'm definitely not regretting having someone that I know put my computer together rather than buying a store one.

    Thanks for everything though, I really appreciate it :)
This discussion has been closed.