none
Blue Screen - BSOD-Windows 7 enterprise ..DMP file attached

    Question

  • Hi all,

    Need help in checking dmp files. Getting the occasional BSOD. I am guessing its related to my graphics card. 

    https://www.dropbox.com/s/hxnf5pqzpgd6j14/012613-22978-01.dmp

    https://www.dropbox.com/s/yo5mfwigbelrdcx/012613-26488-01.dmp

    Thanks for assistance

    Saturday, January 26, 2013 12:16 PM

All replies

  • *******************************************************************************
    *                                                                             *
    *                        Bugcheck Analysis                                    *
    *                                                                             *
    *******************************************************************************
    VIDEO_TDR_FAILURE (116)
    Attempt to reset the display driver and recover from timeout failed.
    Arguments:
    Arg1: fffffa8006fdb010, Optional pointer to internal TDR recovery context (TDR_RECOVERY_CONTEXT).
    Arg2: fffff8800fbdd630, The pointer into responsible device driver module (e.g. owner tag).
    Arg3: ffffffffc000009a, Optional error code (NTSTATUS) of the last failed operation.
    Arg4: 0000000000000004, Optional internal context dependent data.
    Debugging Details:
    ------------------
    FAULTING_IP: 
    nvlddmkm+ade630
    fffff880`0fbdd630 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`050d1a48 fffff880`0f05d000 : 00000000`00000116 fffffa80`06fdb010 fffff880`0fbdd630 ffffffff`c000009a : nt!KeBugCheckEx
    fffff880`050d1a50 fffff880`0f030867 : fffff880`0fbdd630 fffffa80`0952d000 00000000`00000000 ffffffff`c000009a : dxgkrnl!TdrBugcheckOnTimeout+0xec
    fffff880`050d1a90 fffff880`0f05ce0f : 00000000`ffffd84d 00000000`00000080 fffffa80`06fdb010 00000000`0000000f : dxgkrnl!DXGADAPTER::Reset+0x2a3
    fffff880`050d1b40 fffff880`02deeec1 : fffffa80`08b55400 00000000`00000080 00000000`00000000 fffffa80`09528010 : dxgkrnl!TdrResetFromTimeout+0x23
    fffff880`050d1bc0 fffff800`03527e5a : 00000000`04ae733c fffffa80`0955e200 fffffa80`066769e0 fffffa80`0955e200 : dxgmms1!VidSchiWorkerThread+0x101
    fffff880`050d1c00 fffff800`03281d26 : fffff800`03403e80 fffffa80`0955e200 fffff800`03411cc0 006f0074`00000001 : nt!PspSystemThreadStartup+0x5a
    fffff880`050d1c40 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiStartSystemThread+0x16
    STACK_COMMAND:  .bugcheck ; kb
    FOLLOWUP_IP: 
    nvlddmkm+ade630
    fffff880`0fbdd630 4055            push    rbp
    SYMBOL_NAME:  nvlddmkm+ade630
    FOLLOWUP_NAME:  MachineOwner
    MODULE_NAME: nvlddmkm
    IMAGE_NAME:  nvlddmkm.sys
    DEBUG_FLR_IMAGE_TIMESTAMP:  506b3099
    FAILURE_BUCKET_ID:  X64_0x116_IMAGE_nvlddmkm.sys
    BUCKET_ID:  X64_0x116_IMAGE_nvlddmkm.sys
    Followup: MachineOwner
    -------------------------------------------------------------------------------------------------------------------------------------------------------------

    Bug Check 0x116http://msdn.microsoft.com/en-us/library/windows/hardware/ff557263(v=vs.85).aspx

    The Blue Screen by ( nvlddmkm.sys ) , 

    Nvlddmkm.sys file information
    The process known as NVIDIA Windows Kernel Mode Driver (version 191.07, 186.27) or NVIDIA Compatible Windows Vista Kernel Mode Driver (version 158.18, 169.28) or NVIDIA Compatible Windows (version 2000 Miniport Driver, Version 100.65, 2000 Miniport Driver, Version 98.12) belongs to software NVIDIA Windows Kernel Mode Driver or NVIDIA Compatible Windows Vista Kernel Mode Driver or NVIDIA Compatible Windows (version 2000 Miniport Driver) by NVIDIA (www.nvidia.com).

    ** Please Update you Graphic Card (NVIDIA) to the latest version it solve your blue screen, if you have the latest version , install the previous version you have.

     

    Regards,



    MCT / MCITP / MCTS / MCSA / MCSE / C|EH / CCNA

    • Marked as answer by yjchan Monday, January 28, 2013 1:28 AM
    • Unmarked as answer by yjchan Saturday, February 02, 2013 1:47 AM
    Saturday, January 26, 2013 1:05 PM

  • "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


    MS-MVP 2010, 2011, 2012 Team ZigZag

    Saturday, January 26, 2013 5:29 PM
    Moderator
  • Thanks for helping out
    Sunday, January 27, 2013 1:42 AM
  • Hello there,

    Thanks for the input but i would say i use HWMonitor and i constantly see temperatures fluctuating between 40 to 55 degree Celsius depending on activity usage.

    Not sure if those are acceptable temperatures given i live in a temperate country where room temperatures are around 26-28 degree Celsius  

    Regards


    • Edited by yjchan Sunday, January 27, 2013 1:49 AM
    Sunday, January 27, 2013 1:49 AM
  • Have you tried the other things like re-installing the newest driver, and if that doesnt work rolling it back to an older one?

    MS-MVP 2010, 2011, 2012 Team ZigZag

    Sunday, January 27, 2013 5:22 PM
    Moderator
  • ya i updated the driver, its working now thanks 
    Monday, January 28, 2013 1:28 AM
  • you're welcome :)

    MCT / MCITP / MCTS / MCSA / MCSE / MCP / C|EH / CCNA

    Monday, January 28, 2013 7:58 AM
  • Hi i update the driver , it was fine for a few days. But just now while i was playing CS GO, the crash happened again. Could it be a case of graphic card overheating?

    https://www.dropbox.com/s/o6z0vu9wk8dz8wm/020213-34211-01.dmp

    Thanks all

    Saturday, February 02, 2013 1:47 AM
  • Hi i update the driver , it was fine for a few days. But just now while i was playing CS GO, the crash happened again. Could it be a case of graphic card overheating?

    https://www.dropbox.com/s/o6z0vu9wk8dz8wm/020213-34211-01.dmp

    Thanks all

    *******************************************************************************
    *                                                                             *
    *                        Bugcheck Analysis                                    *
    *                                                                             *
    *******************************************************************************
    VIDEO_TDR_FAILURE (116)
    Attempt to reset the display driver and recover from timeout failed.
    Arguments:
    Arg1: fffffa8007511010, Optional pointer to internal TDR recovery context (TDR_RECOVERY_CONTEXT).
    Arg2: fffff88005239b10, The pointer into responsible device driver module (e.g. owner tag).
    Arg3: ffffffffc000009a, Optional error code (NTSTATUS) of the last failed operation.
    Arg4: 0000000000000004, Optional internal context dependent data.

    Debugging Details:
    ------------------


    FAULTING_IP: 
    nvlddmkm+993b10
    fffff880`05239b10 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`02b98a48 fffff880`0413f000 : 00000000`00000116 fffffa80`07511010 fffff880`05239b10 ffffffff`c000009a : nt!KeBugCheckEx
    fffff880`02b98a50 fffff880`04112867 : fffff880`05239b10 fffffa80`09732000 00000000`00000000 ffffffff`c000009a : dxgkrnl!TdrBugcheckOnTimeout+0xec
    fffff880`02b98a90 fffff880`0413ee0f : fffffa80`ffffd84d 00000000`00000000 fffffa80`07511010 00000000`00000000 : dxgkrnl!DXGADAPTER::Reset+0x2a3
    fffff880`02b98b40 fffff880`04037ec1 : fffffa80`08113c70 00000000`00000080 00000000`00000000 fffffa80`09776010 : dxgkrnl!TdrResetFromTimeout+0x23
    fffff880`02b98bc0 fffff800`03733e5a : 00000000`05a01f99 fffffa80`089138b0 fffffa80`066769e0 fffffa80`089138b0 : dxgmms1!VidSchiWorkerThread+0x101
    fffff880`02b98c00 fffff800`0348dd26 : fffff800`0360fe80 fffffa80`089138b0 fffff800`0361dcc0 00000000`00000001 : nt!PspSystemThreadStartup+0x5a
    fffff880`02b98c40 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiStartSystemThread+0x16
    STACK_COMMAND:  .bugcheck ; kb
    FOLLOWUP_IP: 
    nvlddmkm+993b10
    fffff880`05239b10 4055            push    rbp
    SYMBOL_NAME:  nvlddmkm+993b10
    FOLLOWUP_NAME:  MachineOwner
    MODULE_NAME: nvlddmkm
    IMAGE_NAME:  nvlddmkm.sys
    DEBUG_FLR_IMAGE_TIMESTAMP:  50b97852
    FAILURE_BUCKET_ID:  X64_0x116_IMAGE_nvlddmkm.sys
    BUCKET_ID:  X64_0x116_IMAGE_nvlddmkm.sys
    Followup: MachineOwner
    -------------------------------------------------------------------------------------------------------------------------------------------------

    Bug Check 0x116 : http://msdn.microsoft.com/en-us/library/windows/hardware/ff557263(v=vs.85).aspx

    ** The Blue Screen caused by your Graphic Card Driver, Please Update your Graphic Card Driver to the latest version it solve your Blue Screen, if you have the latest version you should install previous version of your driver.

    Regards,


    MCT / MCITP / MCTS / MCSA / MCSE / MCP / C|EH / CCNA


    Saturday, February 02, 2013 5:41 PM
  • Whats the date on the "new" driver?  If the new driver hasnt helped the next step is to monitor the temps.  You can download cpu-z, and gpu-z (both free) and keep an eye on the temps.  If that doesnt do the trick next step is to examine the PSU.

    MS-MVP 2010, 2011, 2012 Team ZigZag

    Sunday, February 03, 2013 7:09 AM
    Moderator
  • Hi,

    Thks for helping but what do you mean by examine the PSU? Im sure the driver is the latest and temperatures are within normal range. 

    Thanks

    Sunday, February 03, 2013 1:18 PM
  • Currently i have disconnected the vga cable and i m using the motherboard graphics instead. Could it be a chance of incompatibility of windows 7 enterprise(64 bit) which is the OS i m running on? 

    Thanks again

    Sunday, February 03, 2013 1:38 PM
  • Again

    Whats the date on the driver?  Have you downloaded cpu-z & gpu-z?


    MS-MVP 2010, 2011, 2012 Team ZigZag

    Monday, February 04, 2013 2:59 AM
    Moderator
  • yes i have downloaded cpuz and gpuz.. they are running  in the background. My date of the driver is 3/12/2012..the version is 310.70.Previously i installed a more updated driver 310.90 but the system will crash and roll back the driver to 310.70. However, the system still crashes at 310.70 occasionally.

    https://www.dropbox.com/s/4dse1w38iyn4wb0/graphic%20card.png

    Thanks

    Monday, February 04, 2013 5:08 AM
  • Nice picture

    From all the previous I suspect it was and is an issue with the video.  That could be the driver, power, heat, the video card itself. 

    What were the temPs?

    What PSu do you have?

    What video card?


    MS-MVP 2010, 2011, 2012 Team ZigZag

    Tuesday, February 05, 2013 3:09 AM
    Moderator
  • Temperature ranges from around 38 degree Celsius to 70 degree Celsius depending on load.

    PSU is cooler master slient pro M2 520W

    Card is nvidia gtx550 ti

    Thanks 

    Tuesday, February 05, 2013 9:11 AM
  • The strange thing is that once i changed from using the vga port of the graphic card to the hdmi port, the problem no longer occurs. Could it be the vga port problem?

    Thanks

    Monday, February 11, 2013 3:50 PM
  • The strange thing is that once i changed from using the vga port of the graphic card to the hdmi port, the problem no longer occurs. Could it be the vga port problem?

    Thanks

    Any [possiblle explanation for this?

    Cheers

    Saturday, February 16, 2013 11:54 AM