BSOD due to graphic card

Page 1 of 2 12 LastLast

  1. Posts : 6
    Win 7 64 bit
       #1

    BSOD due to graphic card


    My computer crashes at random (during hard computations or when doing nothing or something in between). I think it is the video-card. What can i do? This is the error the computer gave me last time when I got it back on (I am sorry it is in Dutch).
    Probleemhandtekening:
    Gebeurtenisnaam van probleem: BlueScreen
    Versie van besturingssysteem: 6.1.7601.2.1.0.256.48
    Landinstelling-id: 1043

    Aanvullende informatie over dit probleem:
    BCCode: 116
    BCP1: FFFFFA800804C270
    BCP2: FFFFF8800684CEFC
    BCP3: 0000000000000000
    BCP4: 0000000000000002
    OS Version: 6_1_7601
    Service Pack: 1_0
    Product: 256_1

    Bestanden die helpen bij het beschrijven van het probleem:
    C:\Windows\Minidump\030113-19297-01.dmp
    C:\Users\Dhr. Panis\AppData\Local\Temp\WER-57408-0.sysdata.xml

    Lees de onlineprivacyverklaring:
    Windows 7 Privacyverklaring - Microsoft Windows

    Als de onlineprivacyverklaring niet beschikbaar is, lees dan onze offlineprivacyverklaring:
    C:\Windows\system32\nl-NL\erofflps.txt
    I attached the result from the SF diagnostic tool.

    Thank you for possible help.



    Tags: ATI Radeon HD 2900 PRO, BSOD, win7, Windows 7 Professional 64-bit
    BSOD due to graphic card Attached Files
    Last edited by PietjePuk; 01 Mar 2013 at 06:20. Reason: tags for searching
      My Computer


  2. Posts : 544
    Windows 7 64bit
       #2

    Hi PietjePuk,

    The system appears to be crashing due to 'atikmpag.sys driver' (ATI Video driver):
    Code:
    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+8efc )
    
    0: kd> !analyze -v
    *******************************************************************************
    *                                                                             *
    *                        Bugcheck Analysis                                    *
    *                                                                             *
    *******************************************************************************
    
    VIDEO_TDR_FAILURE (116)
    Attempt to reset the display driver and recover from timeout failed.
    Please try re-installing the 'ATI drivers'. Open 'Device Manager' > Right Click and expand 'Display Adapters' > Right click to install 'ATI device driver' listed (Also confirm software removal, if prompted) > Follow through with the uninstall process > Restart the computer > Download and install a fresh set of graphic drivers (For ATI HD 2900 Pro) from this link: AMD Catalyst
    Note: If the issue persists, refrain from installing the 'Catalyst Control Center'; install only the display driver for better results.

    The crash dump also points at an outdated BIOS
    Code:
    0: kd> !sysinfo machineid
    Machine ID Information [From Smbios 2.4, DMIVersion 36, Size=2868]
    BiosVendor = Award Software International, Inc.
    BiosVersion = F2
    BiosReleaseDate = 12/25/2009
    SystemManufacturer = Gigabyte Technology Co., Ltd.
    SystemProductName = GA-770TA-UD3
    BaseBoardManufacturer = Gigabyte Technology Co., Ltd.
    BaseBoardProduct = GA-770TA-UD3
    Try updating the BIOS (At-least F3 version) that seems to work better with AMD devices: GIGABYTE - Motherboard - Socket AM3 - GA-770TA-UD3 (rev. 1.0)
    Note: You may want to verify the 'BIOS download version' with the Motherboard manufacturer to be double sure.

    Hope this helps. Do reply with the findings.

      My Computer


  3. Posts : 6
    Win 7 64 bit
    Thread Starter
       #3

    Hi Saurabh,

    as you suggested I updated my ATI drivers. I did this several times already, so I now for the first time refrained myself from installing all non-vitals in the installation. No problems so far, but I updated five minutes ago, so this does not mean much. (If the first crash happens I will report it here)

    I also tried to update the BIOS to F3 (I dont want to flash the F4 beta version). However this was not possible since the installation prompted me that I could not open or execute the FLASHSPI.exe in a 64 bit version of windows.
    Is there a way to update the BIOS at start-up before windows is started and therefore bypassing the 64 bit problem, or will this only result in an unbootable windows version on my pc?

    Thank you for the support!

    Pietje
    Last edited by PietjePuk; 08 Mar 2013 at 07:56. Reason: typo
      My Computer


  4. Posts : 544
    Windows 7 64bit
       #4

    Hi PietjePuk,

    Thank you for the reply; glad that the system looks stable now.

    Please observe the system performance and see if the issue re-occurs. Would also recommend you to wait and see how the system performs; and then check with the 'motherboard manufacturer' about the possibilities of updating the BIOS, if needed.

    Do reply with the results.

      My Computer


  5. Posts : 6
    Win 7 64 bit
    Thread Starter
       #5

    A few crashes still have occurred. For one of them I attached the result from the SF diagnostic tool.
    In regards to the observance of the system performance. I could not find extreme heating of some sort. Also I tried a different screen, which didn't help.
    I still did not update the BIOS because I do not know how to do this, since the installation prompted me that I could not open or execute the FLASHSPI.exe in a 64 bit version of windows.
    BSOD due to graphic card Attached Files
      My Computer


  6. Posts : 544
    Windows 7 64bit
       #6

    Hi PietjePuk,

    Thank you for the reply.

    Almost all crash dumps point have produced similar results:
    Code:
    Loading Dump File [C:\Errors\SF_14-03-2013\031413-21590-01.dmp]
    Mini Kernel Dump File: Only registers and stack trace are available
    
    Symbol search path is: SRV*c:\symbols*http://msdl.microsoft.com/download/symbols
    Executable search path is: 
    Windows 7 Kernel Version 7601 (Service Pack 1) MP (3 procs) Free x64
    Product: WinNt, suite: TerminalServer SingleUserTS
    Built by: 7601.18044.amd64fre.win7sp1_gdr.130104-1431
    Machine Name:
    Kernel base = 0xfffff800`0300d000 PsLoadedModuleList = 0xfffff800`03251670
    Debug session time: Thu Mar 14 14:08:11.860 2013 (UTC + 5:30)
    System Uptime: 0 days 0:11:18.047
    Loading Kernel Symbols
    ...............................................................
    ................................................................
    .....................................
    Loading User Symbols
    Loading unloaded module list
    .....
    *******************************************************************************
    *                                                                             *
    *                        Bugcheck Analysis                                    *
    *                                                                             *
    *******************************************************************************
    
    Use !analyze -v to get detailed debugging information.
    
    BugCheck 116, {fffffa80059c54e0, fffff88002c2befc, 0, 2}
    
    *** 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+8efc )
    
    Followup: MachineOwner
    ---------
    
    1: kd> !analyze -v
    *******************************************************************************
    *                                                                             *
    *                        Bugcheck Analysis                                    *
    *                                                                             *
    *******************************************************************************
    
    VIDEO_TDR_FAILURE (116)
    Attempt to reset the display driver and recover from timeout failed.
    Arguments:
    Arg1: fffffa80059c54e0, Optional pointer to internal TDR recovery context (TDR_RECOVERY_CONTEXT).
    Arg2: fffff88002c2befc, 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+8efc
    fffff880`02c2befc 4055            push    rbp
    
    DEFAULT_BUCKET_ID:  GRAPHICS_DRIVER_TDR_FAULT
    
    CUSTOMER_CRASH_COUNT:  1
    
    BUGCHECK_STR:  0x116
    
    PROCESS_NAME:  System
    
    CURRENT_IRQL:  0
    
    STACK_TEXT:  
    fffff880`023ee9c8 fffff880`02cdf000 : 00000000`00000116 fffffa80`059c54e0 fffff880`02c2befc 00000000`00000000 : nt!KeBugCheckEx
    fffff880`023ee9d0 fffff880`02cded0a : fffff880`02c2befc fffffa80`059c54e0 fffffa80`0733f370 fffffa80`05250410 : dxgkrnl!TdrBugcheckOnTimeout+0xec
    fffff880`023eea10 fffff880`02d85f07 : fffffa80`059c54e0 00000000`00000000 fffffa80`0733f370 fffffa80`05250410 : dxgkrnl!TdrIsRecoveryRequired+0x1a2
    fffff880`023eea40 fffff880`02dafb75 : 00000000`ffffffff 00000000`0000a6e3 00000000`00000000 00000000`00000002 : dxgmms1!VidSchiReportHwHang+0x40b
    fffff880`023eeb20 fffff880`02dae2bb : 00000000`00000102 00000000`00000000 00000000`0000a6e3 00000000`00000000 : dxgmms1!VidSchiCheckHwProgress+0x71
    fffff880`023eeb50 fffff880`02d812c6 : ffffffff`ff676980 fffffa80`05250410 00000000`00000000 00000000`00000000 : dxgmms1!VidSchiWaitForSchedulerEvents+0x1fb
    fffff880`023eebf0 fffff880`02dade7a : 00000000`00000000 fffffa80`07a66870 00000000`00000080 fffffa80`05250410 : dxgmms1!VidSchiScheduleCommandToRun+0x1da
    fffff880`023eed00 fffff800`0332334a : 00000000`fffffc32 fffffa80`0775cb50 fffffa80`05205400 fffffa80`0775cb50 : dxgmms1!VidSchiWorkerThread+0xba
    fffff880`023eed40 fffff800`03073946 : fffff800`031fee80 fffffa80`0775cb50 fffff800`0320ccc0 fffffa80`061b5e70 : nt!PspSystemThreadStartup+0x5a
    fffff880`023eed80 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KxStartSystemThread+0x16
    
    
    STACK_COMMAND:  .bugcheck ; kb
    
    FOLLOWUP_IP: 
    atikmpag+8efc
    fffff880`02c2befc 4055            push    rbp
    
    SYMBOL_NAME:  atikmpag+8efc
    
    FOLLOWUP_NAME:  MachineOwner
    
    MODULE_NAME: atikmpag
    
    IMAGE_NAME:  atikmpag.sys
    
    DEBUG_FLR_IMAGE_TIMESTAMP:  4ff3d05f
    
    FAILURE_BUCKET_ID:  X64_0x116_IMAGE_atikmpag.sys
    
    BUCKET_ID:  X64_0x116_IMAGE_atikmpag.sys
    
    Followup: MachineOwner
    You may also refer to this thread; contains some very useful information by 'usasma' on 'TDR failure': STOP 0x116: VIDEO_TDR_ERROR troubleshooting

    'atikmpag.sys' driver seems to be causing the error: 'VIDEO_TDR_FAILURE (116)'.
    Common issues that can cause a TDR:
    Incorrect memory timings or voltages
    Insufficient/problematic PSU
    Corrupt driver install
    Overheating
    Unstable overclocks (GPU or CPU)
    Incorrect MB voltages (generally NB/SB)
    Faulty graphics card
    A badly written driver or piece of software, but this is an unlikely cause in most cases
    Driver conflicts
    Another possibility is that you are simply asking too much of your graphics card. What I mean by this, is that if you have your settings too high and the graphics card struggles and falls to very 'low FPS'; something graphically complex occurs and the 'GPU' may not be able to respond and a 'TDR error may occur'
    Would like to know if you updated the 'display drivers' or you cleaned up the previous drivers before installing fresh ones. Existing drivers if corrupt, may not work properly on updating; need to reinstall them completely.

    Also try the following steps:

    1. Check that your RAM is running at the correct settings as defined by the manufacturer. Also run memtest86 RAM - Test with Memtest86+

    The goal is to test all the RAM sticks and all the motherboard slots.

    Check your motherboard manual to ensure the RAM sticks are in the recommended motherboard slots. Some motherboards have very specific slots required for the number of RAM sticks installed.

    If you get errors, stop the test and continue with the next step.

    1. Remove all but one stick of RAM from your computer (this will be RAM stick #1), and run Memtest86 again, for 7 passes.
    Be sure to note the RAM stick, use a piece of tape with a number, and note the motherboard slot.
    If this stick passes the test then go to step #3.

    2. If RAM stick #1 has errors, repeat the test with RAM stick #2 in the same motherboard slot.
    If RAM stick #2 passes, this indicates that RAM stick #1 may be bad. If you want to be absolutely sure, re-test RAM stick #1 in another known good slot.
    If RAM stick #2 has errors, this indicates another possible bad RAM stick, a possible motherboard slot failure or inadequate settings.
    3. Test the next stick of RAM (stick #2) in the next motherboard slot.
    If this RAM stick has errors repeat step #2 using a known good stick if possible, or another stick.
    If this RAM stick has no errors and both sticks failed in slot#1, test RAM stick #1 in this slot.
    4. If you find a stick that passes the test, test it in all the other motherboard slots.

    If Part 2 testing shows errors, and all tests in Part 3 show errors, you will need to test the RAM sticks in another computer and/or test other RAM in your computer to identify the problem.

    In this way, you can identify whether it is a bad stick of RAM, a bad motherboard, or incompatibility between the sticks.
    2. Remove 'Overclocks' (CPU & GPU); and try using the 'stock values'

    3. Test the 'nVidia adapter' with the following utility: Video Card - Stress Test with Furmark

    4. You may also try the graphics card in another computer if possible.

    5. Restore the 'BIOS Settings' to 'factory defaults'

    6. If the issue persists (and no hardware issues are detected), would recommend you to test the CPU also: CPU - Stress Test Using IntelBurnTest

    Hope this helps. Do reply with the findings.

      My Computer


  7. Posts : 6
    Win 7 64 bit
    Thread Starter
       #7

    Thank you for the reply.

    Would like to know if you updated the 'display drivers' or you cleaned up the previous drivers before installing fresh ones. Existing drivers if corrupt, may not work properly on updating; need to reinstall them completely.
    I removed the display drivers and installed fresh up-to-date drivers, installing only the essentials. (I did nothing with other drivers)

    The RAM-test is running now. No errors yet, I will report here whenn it is finished.

    Regarding point 2, I didn't overclock anything.

    Other points will strat whenn the RAM test is done.

    Thank you again for your help, I will report back to you whenn the RAM test is finished.
    Last edited by PietjePuk; 20 Mar 2013 at 06:36. Reason: Typo
      My Computer


  8. Posts : 6
    Win 7 64 bit
    Thread Starter
       #8

    I did the Stress Test with Furmark, however I stopped it whenn the alarm went off that the temperature reached 100 degrees. I'm not to sure if I was supposed to do this. I did not see any strange artifacts.
      My Computer


  9. Posts : 544
    Windows 7 64bit
       #9

    Hi PietjePuk,

    Thank you for the response.

    Good that you stopped the test at 100 degrees. Such high temperature may cause harm to the 'graphics adapter' due to overheat. You may want to check if the 'GPU fan' works properly.

    You may also want to check the 'thermal paste' on the 'GPU die'. Re-apply thermal paste spreading it in a thin layer across the 'Gpu die' and any other Dies that contact with the 'cooling plate'. Clamp it all back together so it is properly seated.

    Also follow through with the remaining steps; check the system performance and share results.
    Do reply with the findings; would be glad to assist.

      My Computer


  10. Posts : 6
    Win 7 64 bit
    Thread Starter
       #10

    What is the best way to check if the GPU fan works properly? It is turning at a rapid rate, that's all I can say about it.

    I take the GPU out this weekend and see if I can spot some rarity's on it and check if the thermal paste is properly in-place.
      My Computer


 
Page 1 of 2 12 LastLast

  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 08:37.
Find Us