Random BSOD always seems to be when afk

Page 1 of 3 123 LastLast

  1. Posts : 11
    Win 7 Prof x64
       #1

    Random BSOD always seems to be when afk


    Hi there,

    Hoping somebody will be able to help with finding out where my problem lies. The problem has only been happening since fitting my new graphics card so assume the problem lies there but are completely unsure.

    Problem details are:

    Problem signature:
    Problem Event Name: BlueScreen
    OS Version: 6.1.7600.2.0.0.256.48
    Locale ID: 2057

    Additional information about the problem:
    BCCode: 116
    BCP1: FFFFFA8007B10010
    BCP2: FFFFF88003E0ACF0
    BCP3: 0000000000000000
    BCP4: 0000000000000002
    OS Version: 6_1_7600
    Service Pack: 0_0
    Product: 256_1

    Files that help describe the problem:
    C:\Windows\Minidump\071913-17316-01.dmp
    C:\Users\Stacie\AppData\Local\Temp\WER-30373-0.sysdata.xml

    I have tried to zip up the dump files but am currently having problems doing this saying that access is denied, this also makes no sense since my account is set as administrator. Any further information required please ask.
      My Computer


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

    Staz said:

    I have tried to zip up the dump files but am currently having problems doing this saying that access is denied, this also makes no sense since my account is set as administrator. Any further information required please ask.
    It may happen. That is why we ask to post it following the Blue Screen of Death (BSOD) Posting Instructions.
      My Computer


  3. Posts : 11
    Win 7 Prof x64
    Thread Starter
       #3

    Hi arc,

    Sorry about that I noticed the instructions after posting and have now zipped the files and attached them with this post.

    Again any help is much appreciated
      My Computer


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

    Install Service pack 1 and all other windows updates. Otherwise the system will remain vulnerable to threats.
    Code:
    Windows 7 Kernel Version 7600 MP (4 procs) Free x64
    Product: WinNt, suite: TerminalServer SingleUserTS
    Built by: 7600.16385.amd64fre.win7_rtm.090713-1255
    Learn how to install Windows 7 Service Pack 1 (SP1)
    Service Pack Center - Microsoft Windows

    It is a display/ graphics related BSOD. Whereas the installed display driver is the latest version.

    In that situation, I would suggest you the following:

    Stress test the Graphics Card using Furmark.
    Video Card - Stress Test with Furmark

    Are you overclocking? As you are getting BSODs, you should stop overclocking and run all the hardware components like CPU, GPU and RAM to their default settings. Also set the BIOS to default, too.
    How To Clear CMOS (Reset BIOS)

    Check if the Power Supply Unit (PSU) supplying adequate power to the computer or not.
    eXtreme Power Supply Calculator
    At least 30% extra is safe. Also let us know the wattage of the PSU.

    Is the computer hot? Report us the heat of the computer after a couple of hours of your normal usage. Upload a screenshot of the summery tab of Speccy.
    Better you do it twice. One shot after one hour of usage and the second shot after two hours of usage.

    How old your Logitech gaming accessories are? The drivers are showing a very old date.
    Code:
    fffff880`07946000 fffff880`07948480   LGVirHid   (deferred)             
        Image path: \SystemRoot\system32\drivers\LGVirHid.sys
        Image name: LGVirHid.sys
        Timestamp:        Tue Nov 24 07:06:48 2009 (4B0B38B0)
        CheckSum:         00012CDE
        ImageSize:        00002480
        Translations:     0000.04b0 0000.04e4 0409.04b0 0409.04e4
    Try to update those from Logitech Support - Downloads, Manuals, FAQs & More

    Let us know the results.
    _____________________________________________________________________________
    BSOD ANALYSIS:
    Code:
    ......
    *******************************************************************************
    *                                                                             *
    *                        Bugcheck Analysis                                    *
    *                                                                             *
    *******************************************************************************
    
    Use !analyze -v to get detailed debugging information.
    
    BugCheck 116, {fffffa8007b10010, fffff88003e0acf0, 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+acf0 )
    
    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: fffffa8007b10010, Optional pointer to internal TDR recovery context (TDR_RECOVERY_CONTEXT).
    Arg2: fffff88003e0acf0, 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+acf0
    fffff880`03e0acf0 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`03cbe988 fffff880`040bacbc : 00000000`00000116 fffffa80`07b10010 fffff880`03e0acf0 00000000`00000000 : nt!KeBugCheckEx
    fffff880`03cbe990 fffff880`040ba9c6 : fffff880`03e0acf0 fffffa80`07b10010 fffffa80`07a3b180 fffffa80`09edc410 : dxgkrnl!TdrBugcheckOnTimeout+0xec
    fffff880`03cbe9d0 fffff880`04161f07 : fffffa80`07b10010 00000000`00000000 fffffa80`07a3b180 fffffa80`09edc410 : dxgkrnl!TdrIsRecoveryRequired+0x1a2
    fffff880`03cbea00 fffff880`0418bb75 : 00000000`ffffffff 00000000`0000b187 00000000`00000000 00000000`00000002 : dxgmms1!VidSchiReportHwHang+0x40b
    fffff880`03cbeae0 fffff880`0418a2bb : 00000000`00000102 00000000`00000000 00000000`0000b187 00000000`00000000 : dxgmms1!VidSchiCheckHwProgress+0x71
    fffff880`03cbeb10 fffff880`0415d2c6 : ffffffff`ff676980 fffffa80`09edc410 00000000`00000000 00000000`00000000 : dxgmms1!VidSchiWaitForSchedulerEvents+0x1fb
    fffff880`03cbebb0 fffff880`04189e7a : 00000000`00000000 fffffa80`07a3b180 00000000`00000080 fffffa80`09edc410 : dxgmms1!VidSchiScheduleCommandToRun+0x1da
    fffff880`03cbecc0 fffff800`03369166 : 00000000`fffffc32 fffffa80`09ccfb60 fffffa80`07919040 fffffa80`09ccfb60 : dxgmms1!VidSchiWorkerThread+0xba
    fffff880`03cbed00 fffff800`030a4486 : fffff800`0323ee80 fffffa80`09ccfb60 fffff800`0324cc40 75446231`502f4b77 : nt!PspSystemThreadStartup+0x5a
    fffff880`03cbed40 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiStartSystemThread+0x16
    
    
    STACK_COMMAND:  .bugcheck ; kb
    
    FOLLOWUP_IP: 
    atikmpag+acf0
    fffff880`03e0acf0 4055            push    rbp
    
    SYMBOL_NAME:  atikmpag+acf0
    
    FOLLOWUP_NAME:  MachineOwner
    
    MODULE_NAME: atikmpag
    
    IMAGE_NAME:  atikmpag.sys
    
    DEBUG_FLR_IMAGE_TIMESTAMP:  5154e9d9
    
    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`03e00000 fffff880`03e94000   atikmpag T (no symbols)           
        Loaded symbol image file: atikmpag.sys
        Image path: \SystemRoot\system32\DRIVERS\atikmpag.sys
        Image name: atikmpag.sys
        Timestamp:        Fri Mar 29 06:39:45 2013 (5154E9D9)
        CheckSum:         00091A60
        ImageSize:        00094000
        Translations:     0000.04b0 0000.04e4 0409.04b0 0409.04e4
      My Computer


  5. Posts : 11
    Win 7 Prof x64
    Thread Starter
       #5

    Hi arc,

    Thanks for the speedy response. I shall post what information I have easily been able to retrieve from your suggestions and will post the rest when my partner gets home as he built the computer so knows all the components for things like the power supply calculator. It will also allow my computer to be off for a while so that I can do the speccy screenshots as the computer has been on all day.

    The fur-mark test showed no artifacts and leveled out at a temperature of 85 degrees celsius.

    The computer is not overclocked at all everything is running at standard settings.

    My logitec component is the G15 keyboard and also at the latest driver installed from the website a few weeks ago when the computer was set up.

    I have also uploaded a screeny of speccy as it is at the moment whether this will help or not but it's something until I get the 1 and 2 hour ones taken.

    Many thanks
    Last edited by Staz; 19 Jul 2013 at 11:08. Reason: Didnt realise could take a napshot in speccy
      My Computer


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

    All are fine till now.
    Let us know about the PSU when your partner comes back.

    And, ask him to install the SP1 too :)
      My Computer


  7. Posts : 11
    Win 7 Prof x64
    Thread Starter
       #7

    PSU is a cooler master 850 watt, the check says at worst case 360 w recommended so have way more than necessary.

    Getting started on the SP1 install.
      My Computer


  8. Posts : 11
    Win 7 Prof x64
    Thread Starter
       #8

    Well SP1 is now also installed so guessing its a wait and see if we have any more BSOD unless there is anything else to do.
      My Computer


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

    If all the suggested steps are already taken (think it again) then now observe how it is going.
      My Computer


  10. Posts : 11
    Win 7 Prof x64
    Thread Starter
       #10

    Well after coming back from making my dinner computer had restarted itself yet again. This time however no windows unexpected error window pop up and no file created in the mini dump folder. If there are any ideas for any more testing to be carried out r what the problem could be it is much appreciated.
      My Computer


 
Page 1 of 3 123 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 23:51.
Find Us