Daily BSOD no matter what is running


  1. Posts : 4
    Windows 7 Home Premium 64 bit
       #1

    Daily BSOD no matter what is running


    I quit using this PC about a year ago because everytime I turned it on it would end in BSOD. This happens whether any user applications are running or not. I'd really like to get it fixed because I miss this PC!

    I have run memory and disk checks with no obvious problems identified.

    Diagnostic File Attached.

    Thanks for any help you can provide!
      My Computer


  2. Posts : 15,026
    Windows 10 Home 64Bit
       #2

    Welcome to the Forum.

    Your ATI drivers require update: Download Drivers

    Perform a clean install of a driver following: How to Clean Left Over Driver Files with Driver Sweeper

    Code:
    Microsoft (R) Windows Debugger Version 6.2.9200.20512 AMD64
    Copyright (c) Microsoft Corporation. All rights reserved.
    
    
    Loading Dump File [C:\Users\USER\Downloads\SF_16-01-2014\SF_16-01-2014\011514-17472-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 7600 MP (6 procs) Free x64
    Product: WinNt, suite: TerminalServer SingleUserTS Personal
    Built by: 7600.16841.amd64fre.win7_gdr.110622-1503
    Machine Name:
    Kernel base = 0xfffff800`02c5b000 PsLoadedModuleList = 0xfffff800`02e98e70
    Debug session time: Thu Jan 16 04:15:24.611 2014 (UTC + 6:00)
    System Uptime: 0 days 1:22:44.953
    Loading Kernel Symbols
    ...............................................................
    ................................................................
    ....................
    Loading User Symbols
    Loading unloaded module list
    ...........
    *******************************************************************************
    *                                                                             *
    *                        Bugcheck Analysis                                    *
    *                                                                             *
    *******************************************************************************
    
    Use !analyze -v to get detailed debugging information.
    
    BugCheck 116, {fffffa800b3e1010, fffff88004072c08, 0, d}
    
    *** 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+6c08 )
    
    Followup: MachineOwner
    ---------
    
    0: kd> !analyze -v
    *******************************************************************************
    *                                                                             *
    *                        Bugcheck Analysis                                    *
    *                                                                             *
    *******************************************************************************
    
    VIDEO_TDR_FAILURE (116)
    Attempt to reset the display driver and recover from timeout failed.
    Arguments:
    Arg1: fffffa800b3e1010, Optional pointer to internal TDR recovery context (TDR_RECOVERY_CONTEXT).
    Arg2: fffff88004072c08, The pointer into responsible device driver module (e.g. owner tag).
    Arg3: 0000000000000000, Optional error code (NTSTATUS) of the last failed operation.
    Arg4: 000000000000000d, Optional internal context dependent data.
    
    Debugging Details:
    ------------------
    
    
    FAULTING_IP: 
    atikmpag+6c08
    fffff880`04072c08 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`0280ea68 fffff880`0410f000 : 00000000`00000116 fffffa80`0b3e1010 fffff880`04072c08 00000000`00000000 : nt!KeBugCheckEx
    fffff880`0280ea70 fffff880`0410ed87 : fffff880`04072c08 fffffa80`0b3e1010 00000000`00000000 fffffa80`09e50010 : dxgkrnl!TdrBugcheckOnTimeout+0xec
    fffff880`0280eab0 fffff880`05d5ef07 : fffffa80`0b3e1010 00000000`00000000 00000000`00000000 fffffa80`09e50010 : dxgkrnl!TdrIsRecoveryRequired+0x21f
    fffff880`0280eae0 fffff880`05d88bd4 : fffffa80`00000000 00000000`0004da96 00000000`00000000 00000000`00000000 : dxgmms1!VidSchiReportHwHang+0x40b
    fffff880`0280ebc0 fffff880`05d5a2d5 : fffffa80`09e50010 fffffa80`00000000 00000000`0004da96 00000000`00000000 : dxgmms1!VidSchiCheckHwProgress+0xd0
    fffff880`0280ebf0 fffff880`05d86e7a : 00000000`00000000 fffffa80`0b072750 00000000`00000080 fffffa80`09e50010 : dxgmms1!VidSchiScheduleCommandToRun+0x1e9
    fffff880`0280ed00 fffff800`02f6b6fa : 00000000`fffffc32 fffffa80`09e7c8c0 fffffa80`06a0a040 fffffa80`09e7c8c0 : dxgmms1!VidSchiWorkerThread+0xba
    fffff880`0280ed40 fffff800`02ca9b46 : fffff800`02e45e80 fffffa80`09e7c8c0 fffff800`02e53c40 fffff880`01060810 : nt!PspSystemThreadStartup+0x5a
    fffff880`0280ed80 00000000`00000000 : fffff880`0280f000 fffff880`02809000 fffff880`0280d690 00000000`00000000 : nt!KxStartSystemThread+0x16
    
    
    STACK_COMMAND:  .bugcheck ; kb
    
    FOLLOWUP_IP: 
    atikmpag+6c08
    fffff880`04072c08 4883ec28        sub     rsp,28h
    
    SYMBOL_NAME:  atikmpag+6c08
    
    FOLLOWUP_NAME:  MachineOwner
    
    MODULE_NAME: atikmpag
    
    IMAGE_NAME:  atikmpag.sys
    
    DEBUG_FLR_IMAGE_TIMESTAMP:  4bf1b572
    
    FAILURE_BUCKET_ID:  X64_0x116_IMAGE_atikmpag.sys
    
    BUCKET_ID:  X64_0x116_IMAGE_atikmpag.sys
    
    Followup: MachineOwner
    ---------
    
    0: kd> lmvm atikmpag
    start             end                 module name
    fffff880`0406c000 fffff880`040b2000   atikmpag T (no symbols)           
        Loaded symbol image file: atikmpag.sys
        Image path: atikmpag.sys
        Image name: atikmpag.sys
        Timestamp:        Tue May 18 03:30:26 2010 (4BF1B572)
        CheckSum:         0004D7D7
        ImageSize:        00046000
        Translations:     0000.04b0 0000.04e4 0409.04b0 0409.04e4
    Code:
    Driver	c:\windows\system32\drivers\atikmpag.sys (8.14.1.6117, 257.50 KB (263,680 bytes), 1/14/2011 2:13 PM)

    Reduce items at start-up: Startup Programs - Change

    Perform a clean boot: Troubleshoot Application Conflicts by Performing a Clean Startup

    ESET contributes to BSOD. Please remove it for testing purpose. Use Microsoft Security Essentials.

    Recommended from a strict BSOD perspective, compatibility & stability compared to other security software:

    Microsoft Security Essentials - Free Antivirus for Windows

    Malwarebytes - Free

    Good and Free system security combination.

    Run a System file check (SFC): SFC /SCANNOW Command - System File Checker

    Scan with Kaspersky TDSSKiller:Anti-rootkit utility TDSSKiller

    ESET online scanner: Free Online Virus Scanner | ESET

    Install all windows updates including Service pack 1: Learn how to install Windows 7 Service Pack 1 (SP1)
      My Computer


  3. Posts : 4
    Windows 7 Home Premium 64 bit
    Thread Starter
       #3

    Thank You KoolKat77!!

    Updating the driver was an adventure. AMD Catalyst Control Center tried to load all kinds of stuff. Got BSOD in middle of install. Had to go to system restore point. Eventually got ATI driver updated and ran driver sweeper.

    Now almost 24 hours without BSOD. Keeping fingers crossed!

    Thank you for identifying the driver issue.
      My Computer


  4. Posts : 15,026
    Windows 10 Home 64Bit
       #4

    Thanks for letting us know. Good luck.

    :)
      My Computer


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

    Uh Oh! Another BSOD 3 days after updating ATI display driver and cleaning leftover files with Display Driver Uninstaller.

    Any advice on whether this is a new issue or if I somehow didn't get the above changes done correctly?

    Thanks!
      My Computer


  6. Posts : 15,026
    Windows 10 Home 64Bit
       #6

    The last dump is of 21st Jan. Reconfigure to collect "small memory dumps": Dump Files - Configure Windows to Create on BSOD
      My Computer


  7. Posts : 4
    Windows 7 Home Premium 64 bit
    Thread Starter
       #7

    The January 21st mini-dump is the one that was 3 days after the driver update.
      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 20:38.
Find Us