locked
windows minidump error RRS feed

  • Question

  • Hi I could really do with some help

    I keep having a recurring error message, windows 7 blue screen shut down. Some days it's fine and others days I could be in the middle of doing something and my PC shuts down on it's own accord and goes into a power safe mode and restarts up again with the message windows was unable to shut down and gives me the option to startup in normal mode or safe mode.  

    This could happen once a day and sometimes 3 or 4 times a day. After I get an message "Windows has recovered from an unexpected shutdown" "windows can check online for a solution to this problem" it then gives you an option to check or cancel...when I ask to check it doesn't come up with a solution. The detail's are

    Problem signature:
      Problem Event Name: BlueScreen
      OS Version: 6.1.7601.2.1.0.768.3
      Locale ID: 3081

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

    Files that help describe the problem:
      C:\Windows\Minidump\070815-20077-01.dmp
      C:\Users\Angela\AppData\Local\Temp\WER-56815-0.sysdata.xml


    Wednesday, July 8, 2015 1:35 AM

Answers

  • These crashes were called BCC116 and are related to your video sub system.  Please follow the instructions in this wiki

    Microsoft (R) Windows Debugger Version 10.0.10166.9 AMD64
    Copyright (c) Microsoft Corporation. All rights reserved.
    
    
    Loading Dump File [C:\Users\zigza\Desktop\071415-26894-01.dmp]
    Mini Kernel Dump File: Only registers and stack trace are available
    
    
    ************* Symbol Path validation summary **************
    Response                         Time (ms)     Location
    Deferred                                       SRV*E:\Symbols*http://msdl.microsoft.com/download/symbols
    Symbol search path is: SRV*E:\Symbols*http://msdl.microsoft.com/download/symbols
    Executable search path is: 
    No .natvis files found at C:\Program Files (x86)\Windows Kits\10\Debuggers\x64\Visualizers.
    Windows 7 Kernel Version 7601 (Service Pack 1) MP (8 procs) Free x64
    Product: WinNt, suite: TerminalServer SingleUserTS Personal
    Built by: 7601.18869.amd64fre.win7sp1_gdr.150525-0603
    Machine Name:
    Kernel base = 0xfffff800`03e1f000 PsLoadedModuleList = 0xfffff800`04066730
    Debug session time: Tue Jul 14 01:01:17.565 2015 (UTC - 4:00)
    System Uptime: 0 days 1:35:10.377
    Loading Kernel Symbols
    ...............................................................
    ................................................................
    .......................................................
    Loading User Symbols
    Loading unloaded module list
    ..........
    *******************************************************************************
    *                                                                             *
    *                        Bugcheck Analysis                                    *
    *                                                                             *
    *******************************************************************************
    
    Use !analyze -v to get detailed debugging information.
    
    BugCheck 116, {fffffa80168a24e0, fffff8800f9e7340, ffffffffc000009a, 4}
    
    *** WARNING: Unable to verify timestamp for nvlddmkm.sys
    *** ERROR: Module load completed but symbols could not be loaded for nvlddmkm.sys
    Probably caused by : nvlddmkm.sys ( nvlddmkm+921340 )
    
    Followup:     MachineOwner
    ---------
    
    7: kd> !analyze -v
    *******************************************************************************
    *                                                                             *
    *                        Bugcheck Analysis                                    *
    *                                                                             *
    *******************************************************************************
    
    VIDEO_TDR_FAILURE (116)
    Attempt to reset the display driver and recover from timeout failed.
    Arguments:
    Arg1: fffffa80168a24e0, Optional pointer to internal TDR recovery context (TDR_RECOVERY_CONTEXT).
    Arg2: fffff8800f9e7340, 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:
    ------------------
    
    
    SYSTEM_SKU:  Alienware X51
    
    SYSTEM_VERSION:  00
    
    BIOS_DATE:  11/04/2013
    
    BASEBOARD_PRODUCT:  06G6JW
    
    BASEBOARD_VERSION:  A00
    
    BUGCHECK_P1: fffffa80168a24e0
    
    BUGCHECK_P2: fffff8800f9e7340
    
    BUGCHECK_P3: ffffffffc000009a
    
    BUGCHECK_P4: 4
    
    FAULTING_IP: 
    nvlddmkm+921340
    fffff880`0f9e7340 48ff25f9bfecff  jmp     qword ptr [nvlddmkm+0x7ed340 (fffff880`0f8b3340)]
    
    DEFAULT_BUCKET_ID:  GRAPHICS_DRIVER_TDR_FAULT
    
    CPU_COUNT: 8
    
    CPU_MHZ: d40
    
    CPU_VENDOR:  GenuineIntel
    
    CPU_FAMILY: 6
    
    CPU_MODEL: 3a
    
    CPU_STEPPING: 9
    
    CUSTOMER_CRASH_COUNT:  1
    
    BUGCHECK_STR:  0x116
    
    PROCESS_NAME:  System
    
    CURRENT_IRQL:  0
    
    ANALYSIS_VERSION: 10.0.10166.9 amd64fre
    
    STACK_TEXT:  
    fffff880`027c7a48 fffff880`04537134 : 00000000`00000116 fffffa80`168a24e0 fffff880`0f9e7340 ffffffff`c000009a : nt!KeBugCheckEx
    fffff880`027c7a50 fffff880`0450a867 : fffff880`0f9e7340 fffffa80`0ff79000 00000000`00000000 ffffffff`c000009a : dxgkrnl!TdrBugcheckOnTimeout+0xec
    fffff880`027c7a90 fffff880`04536f43 : fffffa80`ffffd846 ffffffff`fffe7960 fffffa80`168a24e0 00000000`00000000 : dxgkrnl!DXGADAPTER::Reset+0x2a3
    fffff880`027c7b40 fffff880`0443803d : fffffa80`0fcd6150 00000000`00000080 00000000`00000000 fffffa80`0ff6a280 : dxgkrnl!TdrResetFromTimeout+0x23
    fffff880`027c7bc0 fffff800`0412d456 : 00000000`048f5567 fffffa80`0ff9ba00 fffffa80`0ca069c0 fffffa80`0ff9ba00 : dxgmms1!VidSchiWorkerThread+0x101
    fffff880`027c7c00 fffff800`03e852c6 : fffff800`04012e80 fffffa80`0ff9ba00 fffff800`04020cc0 00000000`00000000 : nt!PspSystemThreadStartup+0x5a
    fffff880`027c7c40 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KxStartSystemThread+0x16
    
    
    STACK_COMMAND:  kb
    
    FOLLOWUP_IP: 
    nvlddmkm+921340
    fffff880`0f9e7340 48ff25f9bfecff  jmp     qword ptr [nvlddmkm+0x7ed340 (fffff880`0f8b3340)]
    
    SYMBOL_NAME:  nvlddmkm+921340
    
    FOLLOWUP_NAME:  MachineOwner
    
    MODULE_NAME: nvlddmkm
    
    IMAGE_NAME:  nvlddmkm.sys
    
    DEBUG_FLR_IMAGE_TIMESTAMP:  5457e833
    
    FAILURE_BUCKET_ID:  X64_0x116_IMAGE_nvlddmkm.sys
    
    BUCKET_ID:  X64_0x116_IMAGE_nvlddmkm.sys
    
    PRIMARY_PROBLEM_CLASS:  X64_0x116_IMAGE_nvlddmkm.sys
    
    ANALYSIS_SOURCE:  KM
    
    FAILURE_ID_HASH_STRING:  km:x64_0x116_image_nvlddmkm.sys
    
    FAILURE_ID_HASH:  {1f9e0448-3238-5868-3678-c8e526bb1edc}
    
    Followup:     MachineOwner
    ---------
    
    


    Wanikiya and Dyami--Team Zigzag

    Wednesday, July 15, 2015 10:06 AM

All replies

  •  
    We do need the actual log files (called a DMP files) as they contain the only record of the sequence of events leading up to the crash, what drivers were loaded, and what was responsible.  


    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



    Wanikiya and Dyami--Team Zigzag

    Wednesday, July 8, 2015 1:37 AM
  • Wednesday, July 8, 2015 1:51 AM
  • hi thank you I hope I've done it right, here is the link to the files http://1drv.ms/1Hf1lbE
    Wednesday, July 8, 2015 5:50 AM
  • Hi,

    According to the dump file, the BSOD caused by nvlddmkm.sys which belongs to Nvidia driver. Please try to reinstall the driver for test to fix this problem.


    Please remember to mark the replies as answers if they help, and unmark the answers if they provide no help. If you have feedback for TechNet Support, contact tnmff@microsoft.com.

    Friday, July 10, 2015 2:54 AM
  • These crashes were called BCC116 and are related to your video sub system.  Please follow the instructions in this wiki

    Wanikiya and Dyami--Team Zigzag

    Friday, July 10, 2015 10:44 AM
  • ok so when I go to Device manager and then go to Nvidia driver's and ask for an update it tells me that it's update...I downloaded a program called DriverAgent and tells me that it is not up to date...when I try to ask to update the driver it asks for payment...aren't there's updates supposed to be free...how am I supposed to know what i should do...help??? please

     
    Monday, July 13, 2015 1:57 AM
  • no my PC is not hot? how do i update the driver?

    Monday, July 13, 2015 1:58 AM
  • Hi,

    For Nvidia driver payment, you'd better contact Nvidia support for further assistance.

    On the other hand, since upgrade driver from Device Manager encounter this problem, you can try to access the Nvidia official website to download the driver instead for test.


    Please remember to mark the replies as answers if they help, and unmark the answers if they provide no help. If you have feedback for TechNet Support, contact tnmff@microsoft.com.

    Monday, July 13, 2015 2:16 AM
  • Please read all about updating drivers by my partner JMH3143 here http://answers.microsoft.com/en-us/windows/wiki/windows_other-hardware/updating-a-driver/a5e6345e-af9b-4099-bef0-8d22254aa1c1?tm=1436753520149

    Wanikiya and Dyami--Team Zigzag

    Monday, July 13, 2015 10:54 AM
  • thank's I've downloaded the divers all was ok...until this morning sigh...just another question would windows 10 fix this problem?
    Tuesday, July 14, 2015 3:59 AM
  • It is a driver issue and you may well be using the same driver in win 10 so no it would not.  If you are still crashing upload the DMPS

    Wanikiya and Dyami--Team Zigzag

    Tuesday, July 14, 2015 11:03 AM
  • I went to the dell site, it goes through ur pc n tells u what updates you need...downloaded all the updates but one, I'm have problems with one download chipset...can some tell me what i'm doing wrong and is this what is causing the shut downs...or is it still the driver ? I have shots n dump files n you can tell me if it the same issues as before...files are 14/7/2015 ive only had one crush this morning... https://onedrive.live.com/?id=FA1E13BFB67BBF67%212326&cid=FA1E13BFB67BBF67&group=0
    Wednesday, July 15, 2015 1:44 AM
  • Your link is broken.   Try it again


    Wanikiya and Dyami--Team Zigzag

    Wednesday, July 15, 2015 2:34 AM
  • https://onedrive.live.com/redir?resid=FA1E13BFB67BBF67!2326&authkey=!ADUt5BVN3sfbi_0&ithint=folder%2cnfo

    sorry just had another crush.. 

    Wednesday, July 15, 2015 3:31 AM
  • These crashes were called BCC116 and are related to your video sub system.  Please follow the instructions in this wiki

    Microsoft (R) Windows Debugger Version 10.0.10166.9 AMD64
    Copyright (c) Microsoft Corporation. All rights reserved.
    
    
    Loading Dump File [C:\Users\zigza\Desktop\071415-26894-01.dmp]
    Mini Kernel Dump File: Only registers and stack trace are available
    
    
    ************* Symbol Path validation summary **************
    Response                         Time (ms)     Location
    Deferred                                       SRV*E:\Symbols*http://msdl.microsoft.com/download/symbols
    Symbol search path is: SRV*E:\Symbols*http://msdl.microsoft.com/download/symbols
    Executable search path is: 
    No .natvis files found at C:\Program Files (x86)\Windows Kits\10\Debuggers\x64\Visualizers.
    Windows 7 Kernel Version 7601 (Service Pack 1) MP (8 procs) Free x64
    Product: WinNt, suite: TerminalServer SingleUserTS Personal
    Built by: 7601.18869.amd64fre.win7sp1_gdr.150525-0603
    Machine Name:
    Kernel base = 0xfffff800`03e1f000 PsLoadedModuleList = 0xfffff800`04066730
    Debug session time: Tue Jul 14 01:01:17.565 2015 (UTC - 4:00)
    System Uptime: 0 days 1:35:10.377
    Loading Kernel Symbols
    ...............................................................
    ................................................................
    .......................................................
    Loading User Symbols
    Loading unloaded module list
    ..........
    *******************************************************************************
    *                                                                             *
    *                        Bugcheck Analysis                                    *
    *                                                                             *
    *******************************************************************************
    
    Use !analyze -v to get detailed debugging information.
    
    BugCheck 116, {fffffa80168a24e0, fffff8800f9e7340, ffffffffc000009a, 4}
    
    *** WARNING: Unable to verify timestamp for nvlddmkm.sys
    *** ERROR: Module load completed but symbols could not be loaded for nvlddmkm.sys
    Probably caused by : nvlddmkm.sys ( nvlddmkm+921340 )
    
    Followup:     MachineOwner
    ---------
    
    7: kd> !analyze -v
    *******************************************************************************
    *                                                                             *
    *                        Bugcheck Analysis                                    *
    *                                                                             *
    *******************************************************************************
    
    VIDEO_TDR_FAILURE (116)
    Attempt to reset the display driver and recover from timeout failed.
    Arguments:
    Arg1: fffffa80168a24e0, Optional pointer to internal TDR recovery context (TDR_RECOVERY_CONTEXT).
    Arg2: fffff8800f9e7340, 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:
    ------------------
    
    
    SYSTEM_SKU:  Alienware X51
    
    SYSTEM_VERSION:  00
    
    BIOS_DATE:  11/04/2013
    
    BASEBOARD_PRODUCT:  06G6JW
    
    BASEBOARD_VERSION:  A00
    
    BUGCHECK_P1: fffffa80168a24e0
    
    BUGCHECK_P2: fffff8800f9e7340
    
    BUGCHECK_P3: ffffffffc000009a
    
    BUGCHECK_P4: 4
    
    FAULTING_IP: 
    nvlddmkm+921340
    fffff880`0f9e7340 48ff25f9bfecff  jmp     qword ptr [nvlddmkm+0x7ed340 (fffff880`0f8b3340)]
    
    DEFAULT_BUCKET_ID:  GRAPHICS_DRIVER_TDR_FAULT
    
    CPU_COUNT: 8
    
    CPU_MHZ: d40
    
    CPU_VENDOR:  GenuineIntel
    
    CPU_FAMILY: 6
    
    CPU_MODEL: 3a
    
    CPU_STEPPING: 9
    
    CUSTOMER_CRASH_COUNT:  1
    
    BUGCHECK_STR:  0x116
    
    PROCESS_NAME:  System
    
    CURRENT_IRQL:  0
    
    ANALYSIS_VERSION: 10.0.10166.9 amd64fre
    
    STACK_TEXT:  
    fffff880`027c7a48 fffff880`04537134 : 00000000`00000116 fffffa80`168a24e0 fffff880`0f9e7340 ffffffff`c000009a : nt!KeBugCheckEx
    fffff880`027c7a50 fffff880`0450a867 : fffff880`0f9e7340 fffffa80`0ff79000 00000000`00000000 ffffffff`c000009a : dxgkrnl!TdrBugcheckOnTimeout+0xec
    fffff880`027c7a90 fffff880`04536f43 : fffffa80`ffffd846 ffffffff`fffe7960 fffffa80`168a24e0 00000000`00000000 : dxgkrnl!DXGADAPTER::Reset+0x2a3
    fffff880`027c7b40 fffff880`0443803d : fffffa80`0fcd6150 00000000`00000080 00000000`00000000 fffffa80`0ff6a280 : dxgkrnl!TdrResetFromTimeout+0x23
    fffff880`027c7bc0 fffff800`0412d456 : 00000000`048f5567 fffffa80`0ff9ba00 fffffa80`0ca069c0 fffffa80`0ff9ba00 : dxgmms1!VidSchiWorkerThread+0x101
    fffff880`027c7c00 fffff800`03e852c6 : fffff800`04012e80 fffffa80`0ff9ba00 fffff800`04020cc0 00000000`00000000 : nt!PspSystemThreadStartup+0x5a
    fffff880`027c7c40 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KxStartSystemThread+0x16
    
    
    STACK_COMMAND:  kb
    
    FOLLOWUP_IP: 
    nvlddmkm+921340
    fffff880`0f9e7340 48ff25f9bfecff  jmp     qword ptr [nvlddmkm+0x7ed340 (fffff880`0f8b3340)]
    
    SYMBOL_NAME:  nvlddmkm+921340
    
    FOLLOWUP_NAME:  MachineOwner
    
    MODULE_NAME: nvlddmkm
    
    IMAGE_NAME:  nvlddmkm.sys
    
    DEBUG_FLR_IMAGE_TIMESTAMP:  5457e833
    
    FAILURE_BUCKET_ID:  X64_0x116_IMAGE_nvlddmkm.sys
    
    BUCKET_ID:  X64_0x116_IMAGE_nvlddmkm.sys
    
    PRIMARY_PROBLEM_CLASS:  X64_0x116_IMAGE_nvlddmkm.sys
    
    ANALYSIS_SOURCE:  KM
    
    FAILURE_ID_HASH_STRING:  km:x64_0x116_image_nvlddmkm.sys
    
    FAILURE_ID_HASH:  {1f9e0448-3238-5868-3678-c8e526bb1edc}
    
    Followup:     MachineOwner
    ---------
    
    


    Wanikiya and Dyami--Team Zigzag

    Wednesday, July 15, 2015 10:06 AM
  • Pls. download who crashed software and analysed dump file. I hope you got solid cause. 

    Software download link.

    http://download.cnet.com/WhoCrashed/3000-2094_4-75205821.html

    Wednesday, July 15, 2015 11:56 AM
  • Who crashed is wrong as least as often as it is correct and so is useless

    Wanikiya and Dyami--Team Zigzag

    Wednesday, July 15, 2015 12:33 PM