BSOD Playing Final Fantasy XIV: ARR (No error code?)


  1. Posts : 5
    Windows 7 Home Premium 64 Bit
       #1

    BSOD Playing Final Fantasy XIV: ARR (No error code?)


    So, this is a brand new computer, so I am flumoxed. I have installed and uninstalled drivers repeatedly, and the following happens:
    With the default drivers from the disc from the manufacturer: Random freezing and "The display driver has stopped working but recovered" a few times before locking up entirely and requiring a force shut down.
    With the newest "stable" drivers from ATI and the beta: BSOD as detailed (hopefully) in the attached file.
    I'm wondering if it's a hardware issue at this point, and if I should try taking it back in to the people who assembled it in the first place to get the card replaced, but I'm just not sure.
      My Computer


  2. Arc
    Posts : 35,373
    Microsoft Windows 10 Pro Insider Preview 64-bit
       #2

    Yes, there is a bugcheck code, BugCheck 116, which means VIDEO_TDR_FAILURE.

    It is a graphics/display related error.

    You say it is a brand new computer? Very good. Now ...... uninstall everything relating to the display driver (a BETA is installed there) using AMD Catalyst Un-install Utility. Install only the latest WHQL, 13.4 I guess.
    Update your ATI/AMD display driver.
    You can get it from the link in our forum, Latest AMD Catalyst Video Driver for Windows 7, or you may go to AMD Graphics Driver and Software and opt for Automatically Detect and Install the appropriate driver for your card.


    During installation, you may opt for advanced installation, and install the display driver only, not the Catalyst Control Center.
    And, Stress test the Graphics Card using Furmark.
    Video Card - Stress Test with Furmark

    Let us know the results. We have to know the "The display driver has stopped working but recovered" is appearing with that very version too or not.
    _______________________________________________________________________
    BSOD ANALYSIS:
    Code:
    *******************************************************************************
    *                                                                             *
    *                        Bugcheck Analysis                                    *
    *                                                                             *
    *******************************************************************************
    
    Use !analyze -v to get detailed debugging information.
    
    BugCheck 116, {fffffa800d5543e0, fffff88003cd9e80, 0, 2}
    
    Unable to load image \SystemRoot\system32\DRIVERS\atikmpag.sys, Win32 error 0n2
    *** WARNING: Unable to verify timestamp for atikmpag.sys
    *** ERROR: Module load completed but symbols could not be loaded for atikmpag.sys
    Probably caused by : atikmpag.sys ( atikmpag+ae80 )
    
    Followup: MachineOwner
    ---------
    
    2: kd> !analyze -v
    *******************************************************************************
    *                                                                             *
    *                        Bugcheck Analysis                                    *
    *                                                                             *
    *******************************************************************************
    
    VIDEO_TDR_FAILURE (116)
    Attempt to reset the display driver and recover from timeout failed.
    Arguments:
    Arg1: fffffa800d5543e0, Optional pointer to internal TDR recovery context (TDR_RECOVERY_CONTEXT).
    Arg2: fffff88003cd9e80, The pointer into responsible device driver module (e.g. owner tag).
    Arg3: 0000000000000000, Optional error code (NTSTATUS) of the last failed operation.
    Arg4: 0000000000000002, Optional internal context dependent data.
    
    Debugging Details:
    ------------------
    
    
    FAULTING_IP: 
    atikmpag+ae80
    fffff880`03cd9e80 4883ec28        sub     rsp,28h
    
    DEFAULT_BUCKET_ID:  GRAPHICS_DRIVER_TDR_FAULT
    
    CUSTOMER_CRASH_COUNT:  1
    
    BUGCHECK_STR:  0x116
    
    PROCESS_NAME:  System
    
    CURRENT_IRQL:  0
    
    STACK_TEXT:  
    fffff880`040e3888 fffff880`11d07054 : 00000000`00000116 fffffa80`0d5543e0 fffff880`03cd9e80 00000000`00000000 : nt!KeBugCheckEx
    fffff880`040e3890 fffff880`11d06d5e : fffff880`03cd9e80 fffffa80`0d5543e0 fffffa80`0f6e5560 fffffa80`0e7c8010 : dxgkrnl!TdrBugcheckOnTimeout+0xec
    fffff880`040e38d0 fffff880`11dadf13 : fffffa80`0d5543e0 00000000`00000000 fffffa80`0f6e5560 fffffa80`0e7c8010 : dxgkrnl!TdrIsRecoveryRequired+0x1a2
    fffff880`040e3900 fffff880`11dd7cf1 : 00000000`ffffffff 00000000`00002b7c 00000000`00000000 00000000`00000002 : dxgmms1!VidSchiReportHwHang+0x40b
    fffff880`040e39e0 fffff880`11dd6437 : 00000000`00000102 00000000`00000000 00000000`00002b7c 00000000`00000000 : dxgmms1!VidSchiCheckHwProgress+0x71
    fffff880`040e3a10 fffff880`11da92d2 : ffffffff`ff676980 fffffa80`0e7c8010 00000000`00000000 00000000`00000000 : dxgmms1!VidSchiWaitForSchedulerEvents+0x1fb
    fffff880`040e3ab0 fffff880`11dd5ff6 : 00000000`00000000 fffffa80`0ced9a50 00000000`00000080 fffffa80`0e7c8010 : dxgmms1!VidSchiScheduleCommandToRun+0x1da
    fffff880`040e3bc0 fffff800`0316cbae : 00000000`fffffc32 fffffa80`0f7fba00 fffffa80`0cd4bb30 fffffa80`0f7fba00 : dxgmms1!VidSchiWorkerThread+0xba
    fffff880`040e3c00 fffff800`02ebf8c6 : fffff880`02fd7180 fffffa80`0f7fba00 fffff880`02fe2040 57396a54`75654173 : nt!PspSystemThreadStartup+0x5a
    fffff880`040e3c40 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KxStartSystemThread+0x16
    
    
    STACK_COMMAND:  .bugcheck ; kb
    
    FOLLOWUP_IP: 
    atikmpag+ae80
    fffff880`03cd9e80 4883ec28        sub     rsp,28h
    
    SYMBOL_NAME:  atikmpag+ae80
    
    FOLLOWUP_NAME:  MachineOwner
    
    MODULE_NAME: atikmpag
    
    IMAGE_NAME:  atikmpag.sys
    
    DEBUG_FLR_IMAGE_TIMESTAMP:  522825be
    
    FAILURE_BUCKET_ID:  X64_0x116_IMAGE_atikmpag.sys
    
    BUCKET_ID:  X64_0x116_IMAGE_atikmpag.sys
    
    Followup: MachineOwner
    ---------
    
    2: kd> lmvm atikmpag
    start             end                 module name
    fffff880`03ccf000 fffff880`03d6d000   atikmpag T (no symbols)           
        Loaded symbol image file: atikmpag.sys
        Image path: \SystemRoot\system32\DRIVERS\atikmpag.sys
        Image name: atikmpag.sys
        Timestamp:        Thu Sep 05 12:03:34 2013 (522825BE)
        CheckSum:         0009FE87
        ImageSize:        0009E000
        Translations:     0000.04b0 0000.04e4 0409.04b0 0409.04e4
      My Computer


  3. Posts : 5
    Windows 7 Home Premium 64 Bit
    Thread Starter
       #3

    OK, so I ran the uninstaller and then ran the burn test until it leveled out (and for a while after) and...nothing happened.
    About how long should I run the burntest, anyway?
      My Computer


  4. Arc
    Posts : 35,373
    Microsoft Windows 10 Pro Insider Preview 64-bit
       #4

    At least for 15 minutes .... but if the temps go beyond 90 degrees, stop it then and there.
      My Computer


  5. Posts : 5
    Windows 7 Home Premium 64 Bit
    Thread Starter
       #5

    alright...the temps never went above 71 degrees in 21 minutes.
    So far so good and the game is running (albeit with some graphical flickering on backgrounds and landscape and such) but I've said that enough the past few days that i'm not holding my breath. If it BSODs again before the end of the day, I'll be back.
      My Computer


  6. Posts : 5
    Windows 7 Home Premium 64 Bit
    Thread Starter
       #6

    Welp...not 5 minutes after posting that :
    Problem signature:
    Problem Event Name: BlueScreen
    OS Version: 6.1.7601.2.1.0.768.3
    Locale ID: 1033

    Additional information about the problem:
    BCCode: a0000001
    BCP1: 0000000000000005
    BCP2: 0000000000000000
    BCP3: 0000000000000000
    BCP4: 0000000000000000
    OS Version: 6_1_7601
    Service Pack: 1_0
    Product: 768_1

    Attached new diagnostic folder as well.
    *EDIT* This was while running the game, not the burntest.
      My Computer


  7. Arc
    Posts : 35,373
    Microsoft Windows 10 Pro Insider Preview 64-bit
       #7

    BCCode: a0000001 ..... it is inherent in AMD/ATI display driver.

    If the latest WHQL gives you this problem, and the other drivers give various other problems, best you get a replacement of the GPU.
      My Computer


  8. Posts : 5
    Windows 7 Home Premium 64 Bit
    Thread Starter
       #8

    Off to the guys who built the thing to yell at them, then!
    Well, ok, politely ask them politely to replace an obviously defective component.
    Thank you very much, I'll mark this as solved I suppose :P
      My Computer


  9. Arc
    Posts : 35,373
    Microsoft Windows 10 Pro Insider Preview 64-bit
       #9

    As it is brand new, everything should be under warranty, and you will get a replacement for sure.
      My Computer


 

  Related Discussions
Our Sites
Site Links
About Us
Windows 7 Forums is an independent web site and has not been authorized, sponsored, or otherwise approved by Microsoft Corporation. "Windows 7" and related materials are trademarks of Microsoft Corp.

© Designer Media Ltd
All times are GMT -5. The time now is 01:04.
Find Us