locked
Windows 7 randomly crashes RRS feed

  • Question

  • I will be doing something -anything- and the computer decides to black screen and just sit there. The machine itself is still powered on, but windows will not do anything.

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

    Additional information about the problem:
      BCCode:    116
      BCP1:    FFFFFA800C0014E0
      BCP2:    FFFFF8800FBBDE2C
      BCP3:    FFFFFFFFC000009A
      BCP4:    0000000000000004
      OS Version:    6_1_7601
      Service Pack:    1_0
      Product:    256_1

    Files that help describe the problem:
      C:\Windows\Minidump\040414-51714-01.dmp
      C:\Users\Dawson\AppData\Local\Temp\WER-443916-0.sysdata.xml

    Read our privacy statement online:
      http://go.microsoft.com/fwlink/?linkid=104288&clcid=0x0409

    If the online privacy statement is not available, please read our privacy statement offline:
      C:\Windows\system32\en-US\erofflps.txt

    Friday, April 4, 2014 7:43 PM

Answers

  • DC

    We do need the actual DMP file as they contain the only record of the sequence of events leading up to the crash, what drivers were loaded, and what was responsible.  
    We prefer at least 2 DMP files to spot trends and confirm the cause.

    Please follow our instructions for finding and uploading the files we need to help you fix your computer. They can be found here
    If you have any questions about the procedure please ask

    If you are using Blue screen view, who crashed, or a similar application don't.  They are wrong at least as often as they are correct

    Generic help for the BCC116 error code.

    "It's not a true crash, in the sense that the Blue Screen was initiated only because the combination of video driver and video hardware was being unresponsive, and not because of any synchronous processing exception".

    Since Vista, the "Timeout Detection and Recovery" (TDR) components of the OS video subsystem have been capable of doing some truly impressive things to try to recover from issues which would have caused earlier OS's like XP to crash.

    As a last resort, the TDR subsystem sends the video driver a "please restart yourself now!" command and waits a few seconds.
    If there's no response, the OS concludes that the video driver/hardware combo has truly collapsed in a heap, and it fires off that stop 0x116 BSOD.


    If playing with video driver versions hasn't helped, make sure the box is not overheating.
     Try removing a side panel and aiming a big mains fan straight at the motherboard and GPU.
     Run it like that for a few hours or days - long enough to ascertain whether cooler temperatures make a difference.


    If so, it might be as simple as dust buildup and subsequently inadequate cooling.

    I would download cpu-z and gpu-z (both free) and keep an eye on the video temps


    Wanikiya and Dyami--Team Zigzag


    • Edited by ZigZag3143x Friday, April 4, 2014 9:40 PM
    • Marked as answer by ZigZag3143x Tuesday, April 8, 2014 3:12 AM
    Friday, April 4, 2014 9:39 PM