New build harrassment BSOD


  1. Posts : 4
    windows 7 home 64bit
       #1

    New build harrassment BSOD


    recently bought a new PC, it suffered a couple of BSOD then the graphics card stopped working. I asked for a replacement, got it installed today and after 3 hours another BSOD, I dont know the source of the problem and the people I bought the PC are useless. I'm attaching the minidump, if anyone has any ideas whats causing the problems please tell. I spend £600 on this PC and so far in two weeks I've only gotten about 5 hours of gaming out of it.
      My Computer


  2. Posts : 8,383
    Windows 10 Pro x64, Arch Linux
       #2

    Did you test your RAM
    RAM - Test with Memtest86+

    STOP 0x116: VIDEO_TDR_ERROR troubleshooting
    Code:
    *******************************************************************************
    *                                                                             *
    *                        Bugcheck Analysis                                    *
    *                                                                             *
    *******************************************************************************
    
    Use !analyze -v to get detailed debugging information.
    
    BugCheck 116, {fffffa8007036420, fffff88003c0740c, 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+740c )
    
    VIDEO_TDR_FAILURE (116)
    Attempt to reset the display driver and recover from timeout failed.
    Arguments:
    Arg1: fffffa8007036420, Optional pointer to internal TDR recovery context (TDR_RECOVERY_CONTEXT).
    Arg2: fffff88003c0740c, 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+740c
    fffff880`03c0740c 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`01f5d9c8 fffff880`03ea2000 : 00000000`00000116 fffffa80`07036420 fffff880`03c0740c 00000000`00000000 : nt!KeBugCheckEx
    fffff880`01f5d9d0 fffff880`03ea1d0a : fffff880`03c0740c fffffa80`07036420 fffffa80`06387c00 fffffa80`0633b010 : dxgkrnl!TdrBugcheckOnTimeout+0xec
    fffff880`01f5da10 fffff880`03f48f07 : fffffa80`07036420 00000000`00000000 fffffa80`06387c00 fffffa80`0633b010 : dxgkrnl!TdrIsRecoveryRequired+0x1a2
    fffff880`01f5da40 fffff880`03f72b75 : 00000000`ffffffff 00000000`00047f0d 00000000`00000000 00000000`00000002 : dxgmms1!VidSchiReportHwHang+0x40b
    fffff880`01f5db20 fffff880`03f712bb : 00000000`00000102 00000000`00000001 00000000`00047f0d 00000000`00000000 : dxgmms1!VidSchiCheckHwProgress+0x71
    fffff880`01f5db50 fffff880`03f442c6 : ffffffff`ff676980 fffffa80`0633b010 00000000`00000000 00000000`00000000 : dxgmms1!VidSchiWaitForSchedulerEvents+0x1fb
    fffff880`01f5dbf0 fffff880`03f70e7a : 00000000`00000000 fffffa80`06381d50 00000000`00000080 fffffa80`0633b010 : dxgmms1!VidSchiScheduleCommandToRun+0x1da
    fffff880`01f5dd00 fffff800`02f287c6 : 00000000`fffffc32 fffffa80`06335060 fffffa80`0396e9e0 fffffa80`06335060 : dxgmms1!VidSchiWorkerThread+0xba
    fffff880`01f5dd40 fffff800`02c63c26 : fffff880`02d63180 fffffa80`06335060 fffff880`02d6dfc0 00000000`00000000 : nt!PspSystemThreadStartup+0x5a
    fffff880`01f5dd80 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KxStartSystemThread+0x16
    
    
    STACK_COMMAND:  .bugcheck ; kb
    
    FOLLOWUP_IP: 
    atikmpag+740c
    fffff880`03c0740c 4883ec28        sub     rsp,28h
    
    SYMBOL_NAME:  atikmpag+740c
    
    FOLLOWUP_NAME:  MachineOwner
    
    MODULE_NAME: atikmpag
    
    IMAGE_NAME:  atikmpag.sys
    
    DEBUG_FLR_IMAGE_TIMESTAMP:  4d76ff66
    
    FAILURE_BUCKET_ID:  X64_0x116_IMAGE_atikmpag.sys
    
    BUCKET_ID:  X64_0x116_IMAGE_atikmpag.sys
    
    Followup: MachineOwner
    ---------
      My Computer


  3. Posts : 4
    windows 7 home 64bit
    Thread Starter
       #3

    thanks it looks graphics related from all the ATI bumf on the page, I'll run the memtest now anyway.
      My Computer


  4. Posts : 8,383
    Windows 10 Pro x64, Arch Linux
       #4

    g7g7g7g7 said:
    thanks it looks graphics related from all the ATI bumf on the page, I'll run the memtest now anyway.
    BC TDR116 is also caused by defective RAM or PSU :)
      My Computer


  5. Posts : 4
    windows 7 home 64bit
    Thread Starter
       #5

    do you think this could be caused by the power supply overheating?
      My Computer


  6. Posts : 8,383
    Windows 10 Pro x64, Arch Linux
       #6

    g7g7g7g7 said:
    do you think this could be caused by the power supply overheating?
    PSU rarely overheats so I don't think its the cause
      My Computer


  7. Posts : 4
    windows 7 home 64bit
    Thread Starter
       #7

    cheers for that, I'll run some tests for now.
      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 23:06.
Find Us