BSOD Randomly Happening


  1. Posts : 2
    Windows 7. 64 bit
       #1

    BSOD Randomly Happening


    Hi,



    This is my first post. I read the instructions and hope I am doing this right, if not I apologize. I have been getting the BSOD randomly the past week. The last thing I downloaded was LightRoom 5. I think the problem started afterward, but I can't remember for certain. My husband ran a System Restore, CHKDSK, and even reloaded Windows 7 with no luck on fixing the issue, thus why I am here. (he probably even did a few other things I am not aware of) We are not computer savvy people and I hope we didn't do any more damage trying to fix it on our own. Please bear with us computer challenged folks. :)

    We are getting this notification after a BSOD occurs.

    Problem signature:
    Problem Event Name: BlueScreen
    OS Version: 6.1.7600.2.0.0.768.3
    Locale ID: 1033

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

    Files that help describe the problem:
    C:\Windows\Minidump\112513-17862-01.dmp
    C:\Users\MissPriss\AppData\Local\Temp\WER-742081-0.sysdata.xml


    It wont let me upload MSINFO 032 or the DMP files. Am I doing something wrong?


    Thanks for your patience!!


    Priscilla
      My Computer


  2. Posts : 3,056
    Windows 10
       #2

    Hi Priscilla, welcome to SF :) .

    Misspriss623 said:
    It wont let me upload MSINFO 032 or the DMP files. Am I doing something wrong?
    Actually you are . Once you have all of your files generated by the SFDT (Click Here)
    you need to zip them all before you attempt to upload the files.

    How do I upload to Seven Forums?
      My Computer


  3. Posts : 2
    Windows 7. 64 bit
    Thread Starter
       #3

    Sorry, somehow missed that. I am a speed reader and it bites me in the butt.

    Hopefully I zipped them correctly. If there is a way to do it wrong I will find it, trust me!
      My Computer


  4. Posts : 3,056
    Windows 10
       #4

    Thanks for the files :) .

    Unintentionally by recovering back to a factory image you destroyed evidence that might have been helpful
    to debug this case, such as whether the OS had SP1 installed or not and if the latest driver was used
    to no avail, which are amongst the stings I'm about to list in the process of troubleshooting this bug check.

    A TDR (Timeout Detection Recovery) is not a bugcheck in the true sense in that something
    has went terribly wrong in the kernel which forced the machine to crash.
    TVeblen said:
    "Display driver xxxxx stopped responding and was recovered"

    Timeout Detection & Recovery (TDR) = "Display Driver Stopped Responding and was Recovered" is a useful feature that started in Vista and is also in W7 that allows the OS to try and recover from a video timeout so that the system does not crash to a bluescreen. Symptoms included a screen flash with the TDR message appearing one or more times or the screen blinking out to black. If the system cannot recover it will crash (Stop Error 116 typical). The issue is that the video card is not responding as expected. The solution is in the: why?

    There is no one-size-fits-all solution to TDR errors. But the problem is usually found in the local environment (your computer). Finding the cause is a matter of checking every possible cause and uncovering the culprit through a simple process of elimination. By methodically running down a checklist of diagnostic procedures you should be able to find the cause and can correct it.

    There are numerous reports of hardware solutions to TDR's. The most common are:

    • Poor Cooling
    • Problems with the power supply
    • Overclocking Issues
    • Bad System memory or incorrect memory timings
    • Defective PC Components



    Bugcheck:

    Code:
    BugCheck 116, {fffffa80094674e0, fffff88001bbdc08, 0, 2}
    
    Unable to load image 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+6c08 )

    The driver is very old!

    Code:
    lmvm atikmpag
    start             end                 module name
    fffff880`01bb7000 fffff880`01bfd000   atikmpag T (no symbols)           
        Loaded symbol image file: atikmpag.sys
        Image path: atikmpag.sys
        Image name: atikmpag.sys
        Timestamp:        Tue May 18 00:30:26 2010
    Please update the display driver:
    Arc said:
    During installation, you may opt for advanced installation, and install the display driver only, not the Catalyst Control Center.



    Please update to Service Pack 1:
    Code:
    Windows 7 Kernel Version 7600 MP (4 procs) Free x64




    What is the make, model and age of your PSU?
    Fill out this form and post back the result:






    Test for thermals and stability:


    • Download HWinfo and post a Screenshot of the sensors window, one at idle and another while putting load on the PC using Prime95 for the CPU side and Furmark for the GPU.
      • Before running Prime95 make sure to enable Round-off checking (see 1st post under the tutorial).





    Testing the RAM:

    koolkat77 said:
    Test and Diagnose RAM Issues with Memtest86+:


       Tip

    • Pay close attention to part 3 of the tutorial "If you have errors"
    • Test the RAM with Memtest86+ for at least 7-10 passes. It may take up to 22 passes to find problems. Make sure to run it once after the system has been on for a few hours and is warm, and then also run it again when the system has been off for a few hours and is cold.

    When done with the testing procedure take a picture and upload it here.

    Post back with the results :) .
      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:33.
Find Us