locked
BlueScreen error RRS feed

  • Question

  • Hi there, I've had my computer running Windows 7 for about a year now and I haven't had any trouble until recently. About 5 days ago my computer screen started freezing, getting all pixel-y/chopped up looking, then the computer re-boots over and over again until the screen appears normal again. This happens almost every time I put it in sleep mode or turn it off. Today it's been even more frequent, freezing while I'm actually using the computer. The error message that pops up when I finally am able to log in says this:

     

    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:    85590510
      BCP2:    98045C26
      BCP3:    00000000
      BCP4:    00000002
      OS Version:    6_1_7600
      Service Pack:    0_0
      Product:    768_1

    Files that help describe the problem:
      C:\Windows\Minidump\110810-37533-01.dmp
      C:\Users\LindsayO\AppData\Local\Temp\WER-66643-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

    I tried to open one of the minidump files and my computer told me that it doesn't know what program to use to open it. I don't know what the error means and the only changes I've made recently was updating my Adobe reader. I'm fairly computer illiterate, so I feel like there's probably a lot more information that would be helpful, so please let me know what you need me to supply and I'll do my best.

     

    Thanks!

     

    Tuesday, November 9, 2010 4:41 AM

All replies

  • Hi,
     
    Please upload the minidump files for further analysis and post a link
    back to this thread,
     
     

    -- Mike Burr
    Tuesday, November 9, 2010 4:57 AM
  • The VIDEO_TDR_ ERROR bug check has a value of 0x00000116. This indicates that an attempt to reset the display driver and recover from a timeout failed.

    Try updating all of ur drivers but most importantly the video card driver to the latest version in case there is a problem with that.

    Make sure all updates and patches are install in windows - make sure the system is clean of viruses etc. Help to do this found here - http://www.mypchealth.co.uk/StepbystepGuide.php

    Then check your memory and harddisks to make sure they are ok. - http://www.mypchealth.co.uk/GuideTests.php

    You could also try a different graphics card if the problem all the above throws no new light on the situation. It could be related to the memory on the video card.


    www.mypchealth.co.uk
    Tuesday, November 9, 2010 2:57 PM
  • Hi Mike,

    Here's the link to my files. These are just the most recent ones, I've got plenty of others if you need them.

    http://cid-bc9e36b752814d99.skydrive.live.com/redir.aspx?resid=BC9E36B752814D99!109
    Wednesday, November 10, 2010 12:59 AM
  • Minor update: I was using the computer and it froze for a moment, then managed to get through whatever was happening and a little message popped up saying that my graphics driver failed but then recovered. I'm upgrading the driver for that now... hopefully it works.
    Wednesday, November 10, 2010 2:34 AM
  • I'd make sure that you indeed have the tx2500 (for accuracy of this link: http://h10025.www1.hp.com/ewfrf/wc/softwareCategory?os=4062&lc=en&cc=us&dlc=en&sw_lang=&product=3717593#N325 ), then I would update the BIOS and see if there is a newer ATI driver for your card (whether it is the one on HP's site, or whether you end up finding a newer one on AMD's  site, http://www.amd.com/us/Pages/AMDHomePage.aspx ).


    0: kd> !analyze -v
    *******************************************************************************
    *                                       *
    *            Bugcheck Analysis                  *
    *                                       *
    *******************************************************************************
    
    VIDEO_TDR_FAILURE (116)
    Attempt to reset the display driver and recover from timeout failed.
    Arguments:
    Arg1: 855eb510, Optional pointer to internal TDR recovery context (TDR_RECOVERY_CONTEXT).
    Arg2: 9803dc26, The pointer into responsible device driver module (e.g. owner tag).
    Arg3: 00000000, Optional error code (NTSTATUS) of the last failed operation.
    Arg4: 00000002, Optional internal context dependent data.
    
    Debugging Details:
    ------------------
    
    *** WARNING: Unable to verify timestamp for atikmdag.sys
    *** ERROR: Module load completed but symbols could not be loaded for atikmdag.sys
    
    FAULTING_IP: 
    atikmdag+fc26
    9803dc26 8bff      mov   edi,edi
    
    DEFAULT_BUCKET_ID: GRAPHICS_DRIVER_TDR_FAULT
    
    CUSTOMER_CRASH_COUNT: 1
    
    BUGCHECK_STR: 0x116
    
    PROCESS_NAME: System
    
    CURRENT_IRQL: 0
    
    STACK_TEXT: 
    8c07ab74 985cfadb 00000116 855eb510 9803dc26 nt!KeBugCheckEx+0x1e
    WARNING: Stack unwind information not available. Following frames may be wrong.
    8c07ab98 985d08fa 9803dc26 00000000 00000002 dxgkrnl+0x8cadb
    8c07abbc 97d5692c 00000000 00000102 87c54560 dxgkrnl+0x8d8fa
    8c07ac34 97d80a32 fffffcfb 003e5772 00000000 dxgmms1!VidSchiReportHwHang+0x3c0
    8c07ac5c 97d81153 00000000 00000000 00000000 dxgmms1!VidSchiCheckHwProgress+0x68
    8c07ac98 97d5d8f0 8c07ac90 87c939d8 87c9a978 dxgmms1!VidSchiWaitForSchedulerEvents+0x1b1
    8c07ad28 97d824b7 87c54560 82e4a3f1 87c54560 dxgmms1!VidSchiScheduleCommandToRun+0xaa
    8c07ad3c 97d82573 87c54560 00000000 87c59948 dxgmms1!VidSchiRun_PriorityTable+0xf
    8c07ad50 8301c6d3 87c54560 baf9d9fe 00000000 dxgmms1!VidSchiWorkerThread+0x7f
    8c07ad90 82ece0f9 97d824f4 87c54560 00000000 nt!PspSystemThreadStartup+0x9e
    00000000 00000000 00000000 00000000 00000000 nt!KiThreadStartup+0x19
    
    
    STACK_COMMAND: .bugcheck ; kb
    
    FOLLOWUP_IP: 
    atikmdag+fc26
    9803dc26 8bff      mov   edi,edi
    
    SYMBOL_NAME: atikmdag+fc26
    
    FOLLOWUP_NAME: MachineOwner
    
    MODULE_NAME: atikmdag
    
    IMAGE_NAME: atikmdag.sys
    
    DEBUG_FLR_IMAGE_TIMESTAMP: 4a8a1a1e
    
    FAILURE_BUCKET_ID: 0x116_IMAGE_atikmdag.sys
    
    BUCKET_ID: 0x116_IMAGE_atikmdag.sys
    
    Followup: MachineOwner
    ---------
    
    0: kd> lmvm atikmdag
    start  end    module name
    9802e000 98543000  atikmdag T (no symbols)      
      Loaded symbol image file: atikmdag.sys
      Image path: \SystemRoot\system32\DRIVERS\atikmdag.sys
      Image name: atikmdag.sys
      Timestamp:    Mon Aug 17 21:03:58 2009 (4A8A1A1E)
      CheckSum:     004CDCF2
      ImageSize:    00515000
      Translations:   0000.04b0 0000.04e4 0409.04b0 0409.04e4
    0: kd> !sysinfo machineid
    Machine ID Information [From Smbios 2.4, DMIVersion 36, Size=989]
    BiosVendor = Hewlett-Packard
    BiosVersion = F.05
    BiosReleaseDate = 05/21/2008
    SystemManufacturer = Hewlett-Packard
    SystemProductName = HP Pavilion tx2500 Notebook PC
    SystemFamily = 103C_5335KV
    SystemVersion = Rev 1
    SystemSKU = FE912UA#ABA
    BaseBoardManufacturer = Quanta
    BaseBoardProduct = 30F1
    BaseBoardVersion = 97.17
    

    -- Mike Burr
    • Proposed as answer by Andre.Ziegler Wednesday, November 10, 2010 11:59 AM
    Wednesday, November 10, 2010 4:32 AM
  • Well, two nights ago I updated the graphics card driver from the ATI website. Since the computer didn't crash at all last night I thought my problem was solved. Unfortunately tonight it crashed again, so I tried to check the HP site for a new BIOS update. I have the tx2000, not 2500 and I'm running Windows 7, but the HP downloads site doesn't include any updates for my computer for Windows 7. So, any ideas on my next step?

    Friday, November 12, 2010 12:54 AM
  • Hi,

    Do you have an other graphics card? If so , you can replace the existing card to have a test.

     

    Friday, November 12, 2010 5:32 AM
  • I have seen this before with my ATI card. Make sure the heatsink and fan on the card is free of excessive dust. Also my card has heat pads on the memory chips and i noticed one was falling off (they are just stuck on). I bought some new ones off ebay v cheap, and cleaned the heatsink and fan and it cleared up my issue.

     

    So just to confirm this was caused by overheating of my gpu, and a simple and cheap fix sorted it!.

     

    Many thanks

    Jules.

    Friday, November 12, 2010 11:46 AM
  • Since there isn't a specific BIOS updater for Windows 7, It might be worth trying the Vista x64 BIOS updater (since the BIOS is relatively independent of the OS, but occasionally the software that performs the flash is picky),

    http://h10025.www1.hp.com/ewfrf/wc/softwareCategory?os=2100&lc=en&cc=us&dlc=en&sw_lang=&product=3658348#N2510


    -- Mike Burr
    Sunday, November 14, 2010 3:11 AM
  • Hey Mike, i'm getting almost the exact same error as you are with the following configuration:

    - hp envy 17

    - radeon 5850

     

    The error looks like this 

    VIDEO_TDR_FAILURE (116)

    Attempt to reset the display driver and recover from timeout failed.

    Arguments:

    Arg1: fffffa800a2f04e0, Optional pointer to internal TDR recovery context (TDR_RECOVERY_CONTEXT).

    Arg2: fffff88002e06f5c, 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:

     

    Usually the error occurs after the laptop as been in standby, then i open the lid and start watching a video.

     

    I've applied all the BIOS updates that HP has given me, i'm at a loss......  Have you made any progress?

     

    Thanks

    Tuesday, November 30, 2010 5:44 AM
  • Hi Palmej2,

     

    Can you upload the dump files to skydrive and post a link for further analysis,

    http://mikemstech.blogspot.com/2010/08/skydrive-uploading-files-for-community.html


    -- Mike Burr
    MS Technologies - Development - *nix
    Tuesday, November 30, 2010 8:30 PM
  • To allow us to better support you please run the Microsoft Support Diagnostic Tool using the steps below. The tool gathers diagnostic information useful in resolving your issue. From a computer that is connected to the internet:

     

    1. Once Windows is fully loaded, Click on the Start button

    2. Type "msdt" in the "Start Search" box, then select "msdt" from the programs list

    3. Please type your support key 4847735063,  when prompted and click next.

    4. Follow the onscreen instructions to run the diagnostics on this computer, and upload the data to Microsoft when prompted.

    5.  Please reply back with your computer name after you upload the data.

    The computer name can be determined by right clicking on “My Computer” and selecting “Properties” from the menu.

     

    Friday, February 11, 2011 11:25 PM
  • Hi Craig. Do you work for MS? Do you ever get PDBs with usefull data to analyse 0x116 crashes?

    "A programmer is just a tool which converts caffeine into code" CLIP- Stellvertreter http://www.winvistaside.de/
    Friday, February 11, 2011 11:51 PM
  • The previous passkey is no longer valid.   To allow us to better support you please run the Microsoft Support Diagnostic Tool using the steps below. The tool gathers diagnostic information useful in resolving your issue. From a computer that is connected to the internet:

     

    1. Once Windows is fully loaded, Click on the Start button

    2. Type "msdt" in the "Start Search" box, then select "msdt" from the programs list

    3. Please type your support key 9971563513,  when prompted and click next.

    4. Follow the onscreen instructions to run the diagnostics on this computer, and upload the data to Microsoft when prompted.

    5.  Please reply back with your computer name after you upload the data.

    The computer name can be determined by right clicking on “My Computer” and selecting “Properties” from the menu.

    From my experience on the 0x117 and 0x116 the dumps are necessary to understand more about what is going on, although in some scenarios it can be challenging even with the dumps to pinpoint the cause.  The MSDT report will help us gather the dumps if they were within the last 30 days.

    Thanks,

    Craig Hildebrandt

    Tuesday, February 22, 2011 6:52 PM
  • I doubt that you get a response after this long time.

    "A programmer is just a tool which converts caffeine into code" CLIP- Stellvertreter http://www.winvistaside.de/
    Tuesday, February 22, 2011 7:50 PM