locked
Bluescreen problem win 7 RRS feed

  • Question

  • Hello , my additional information about the problem is : C:\Windows\Minidump\102315-23025-01.dmp
      C:\Users\Giwrgos\AppData\Local\Temp\WER-38813-0.sysdata.xml
     BCCode: 116
      BCP1: FFFFFA800B401010
      BCP2: FFFFF8800F6069C8
      BCP3: 0000000000000000
      BCP4: 000000000000000D
      OS Version: 6_1_7601
      Service Pack: 1_0
      Product: 768_1 

    i got some help from videos and sites but they didnt help me , my pc info is this : hp pavilion cpu intel core i7-2600 @3.40 GHz

    3.39 GHz - Ram 6 GB    64-bit Windows home premium Nvidia Geforce Gt-545

     

    My pc can start sometimes if i turn it off-on several times but when i try to open a application or game show's no singal screen and restart .In safe mode im not have restarts or no singal screen .I make my pc i kind of format , my pc turn it to the 1st time use state but the problem continues . I cant do something else ,if u can help me plz reply (And sorry about my bad english )


    Friday, October 23, 2015 11:46 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.10563.566 AMD64
    Copyright (c) Microsoft Corporation. All rights reserved.
    
    
    Loading Dump File [C:\Users\zigza\Desktop\Minidump\102315-23025-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: 
    Windows 7 Kernel Version 7601 (Service Pack 1) MP (8 procs) Free x64
    Product: WinNt, suite: TerminalServer SingleUserTS Personal
    Built by: 7601.19018.amd64fre.win7sp1_gdr.150928-1507
    Machine Name:
    Kernel base = 0xfffff800`02c0e000 PsLoadedModuleList = 0xfffff800`02e55730
    Debug session time: Thu Oct 22 11:25:28.093 2015 (UTC - 4:00)
    System Uptime: 0 days 0:02:53.872
    Loading Kernel Symbols
    ...............................................................
    ................................................................
    ..................
    Loading User Symbols
    Loading unloaded module list
    ...
    *******************************************************************************
    *                                                                             *
    *                        Bugcheck Analysis                                    *
    *                                                                             *
    *******************************************************************************
    
    Use !analyze -v to get detailed debugging information.
    
    BugCheck 116, {fffffa800b401010, fffff8800f6069c8, 0, d}
    
    *** 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+1759c8 )
    
    Followup:     MachineOwner
    ---------
    
    6: kd> !analyze -v
    *******************************************************************************
    *                                                                             *
    *                        Bugcheck Analysis                                    *
    *                                                                             *
    *******************************************************************************
    
    VIDEO_TDR_FAILURE (116)
    Attempt to reset the display driver and recover from timeout failed.
    Arguments:
    Arg1: fffffa800b401010, Optional pointer to internal TDR recovery context (TDR_RECOVERY_CONTEXT).
    Arg2: fffff8800f6069c8, The pointer into responsible device driver module (e.g. owner tag).
    Arg3: 0000000000000000, Optional error code (NTSTATUS) of the last failed operation.
    Arg4: 000000000000000d, Optional internal context dependent data.
    
    Debugging Details:
    ------------------
    
    
    SYSTEM_SKU:  H1E00EA#AB7
    
    BIOS_DATE:  10/21/2011
    
    BASEBOARD_PRODUCT:  2ABF
    
    BASEBOARD_VERSION:  1.20
    
    BUGCHECK_P1: fffffa800b401010
    
    BUGCHECK_P2: fffff8800f6069c8
    
    BUGCHECK_P3: 0
    
    BUGCHECK_P4: d
    
    FAULTING_IP: 
    nvlddmkm+1759c8
    fffff880`0f6069c8 4883ec28        sub     rsp,28h
    
    DEFAULT_BUCKET_ID:  GRAPHICS_DRIVER_TDR_FAULT
    
    CPU_COUNT: 8
    
    CPU_MHZ: d40
    
    CPU_VENDOR:  GenuineIntel
    
    CPU_FAMILY: 6
    
    CPU_MODEL: 2a
    
    CPU_STEPPING: 7
    
    CUSTOMER_CRASH_COUNT:  1
    
    BUGCHECK_STR:  0x116
    
    PROCESS_NAME:  System
    
    CURRENT_IRQL:  0
    
    ANALYSIS_VERSION: 10.0.10563.566 amd64fre
    
    STACK_TEXT:  
    fffff880`05d9b918 fffff880`10165134 : 00000000`00000116 fffffa80`0b401010 fffff880`0f6069c8 00000000`00000000 : nt!KeBugCheckEx
    fffff880`05d9b920 fffff880`10164ebb : fffff880`0f6069c8 fffffa80`0b401010 fffffa80`0b51f1e0 fffffa80`0b59e010 : dxgkrnl!TdrBugcheckOnTimeout+0xec
    fffff880`05d9b960 fffff880`0f40ff13 : fffffa80`0b401010 00000000`00000000 fffffa80`0b51f1e0 fffffa80`0b59e010 : dxgkrnl!TdrIsRecoveryRequired+0x21f
    fffff880`05d9b990 fffff880`0f43ded6 : 00000000`ffffffff 00000000`00002b04 fffff880`05d9baf0 00000000`00000002 : dxgmms1!VidSchiReportHwHang+0x40b
    fffff880`05d9ba70 fffff880`0f40b2aa : fffffa80`0b59e010 ffffffff`feced300 fffffa80`058dc310 00000000`00000000 : dxgmms1!VidSchWaitForCompletionEvent+0x196
    fffff880`05d9bab0 fffff880`0f437ff6 : 00000000`00000000 fffffa80`0c3d6d50 00000000`00000080 fffffa80`0b59e010 : dxgmms1!VidSchiScheduleCommandToRun+0x1b2
    fffff880`05d9bbc0 fffff800`02f1bb26 : 00000000`fffffc32 fffffa80`0b5c1200 fffffa80`054feb10 fffffa80`0b5c1200 : dxgmms1!VidSchiWorkerThread+0xba
    fffff880`05d9bc00 fffff800`02c72f66 : fffff800`02e01e80 fffffa80`0b5c1200 fffff800`02e0fcc0 00000000`ffffffff : nt!PspSystemThreadStartup+0x5a
    fffff880`05d9bc40 00000000`00000000 : fffff880`05d9c000 fffff880`05d96000 fffff880`0b5b8d40 00000000`00000000 : nt!KiStartSystemThread+0x16
    
    
    STACK_COMMAND:  kb
    
    FOLLOWUP_IP: 
    nvlddmkm+1759c8
    fffff880`0f6069c8 4883ec28        sub     rsp,28h
    
    SYMBOL_NAME:  nvlddmkm+1759c8
    
    FOLLOWUP_NAME:  MachineOwner
    
    MODULE_NAME: nvlddmkm
    
    IMAGE_NAME:  nvlddmkm.sys
    
    DEBUG_FLR_IMAGE_TIMESTAMP:  4e99233b
    
    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
    ---------
    
    6: kd> lmvm nvlddmkm
    Browse full module list
    start             end                 module name
    fffff880`0f491000 fffff880`10108000   nvlddmkm T (no symbols)           
        Loaded symbol image file: nvlddmkm.sys
        Image path: nvlddmkm.sys
        Image name: nvlddmkm.sys
        Browse all global symbols  functions  data
        Timestamp:        Sat Oct 15 02:07:55 2011 (4E99233B)
        CheckSum:         00C61687
        ImageSize:        00C77000
        Translations:     0000.04b0 0000.04e4 0409.04b0 0409.04e4
    


    Wanikiya and Dyami--Team Zigzag Windows IT-PRO (MS-MVP)

    Friday, October 23, 2015 1:10 PM

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 Windows IT-PRO (MS-MVP)

    Friday, October 23, 2015 12:19 PM
  • <iframe src="https://onedrive.live.com/embed?cid=F1794609D06AD260&resid=F1794609D06AD260%21112&authkey=AKoFPUG-4kSgL8c" width="98" height="120" frameborder="0" scrolling="no"></iframe>
    Friday, October 23, 2015 12:58 PM
  • 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.10563.566 AMD64
    Copyright (c) Microsoft Corporation. All rights reserved.
    
    
    Loading Dump File [C:\Users\zigza\Desktop\Minidump\102315-23025-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: 
    Windows 7 Kernel Version 7601 (Service Pack 1) MP (8 procs) Free x64
    Product: WinNt, suite: TerminalServer SingleUserTS Personal
    Built by: 7601.19018.amd64fre.win7sp1_gdr.150928-1507
    Machine Name:
    Kernel base = 0xfffff800`02c0e000 PsLoadedModuleList = 0xfffff800`02e55730
    Debug session time: Thu Oct 22 11:25:28.093 2015 (UTC - 4:00)
    System Uptime: 0 days 0:02:53.872
    Loading Kernel Symbols
    ...............................................................
    ................................................................
    ..................
    Loading User Symbols
    Loading unloaded module list
    ...
    *******************************************************************************
    *                                                                             *
    *                        Bugcheck Analysis                                    *
    *                                                                             *
    *******************************************************************************
    
    Use !analyze -v to get detailed debugging information.
    
    BugCheck 116, {fffffa800b401010, fffff8800f6069c8, 0, d}
    
    *** 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+1759c8 )
    
    Followup:     MachineOwner
    ---------
    
    6: kd> !analyze -v
    *******************************************************************************
    *                                                                             *
    *                        Bugcheck Analysis                                    *
    *                                                                             *
    *******************************************************************************
    
    VIDEO_TDR_FAILURE (116)
    Attempt to reset the display driver and recover from timeout failed.
    Arguments:
    Arg1: fffffa800b401010, Optional pointer to internal TDR recovery context (TDR_RECOVERY_CONTEXT).
    Arg2: fffff8800f6069c8, The pointer into responsible device driver module (e.g. owner tag).
    Arg3: 0000000000000000, Optional error code (NTSTATUS) of the last failed operation.
    Arg4: 000000000000000d, Optional internal context dependent data.
    
    Debugging Details:
    ------------------
    
    
    SYSTEM_SKU:  H1E00EA#AB7
    
    BIOS_DATE:  10/21/2011
    
    BASEBOARD_PRODUCT:  2ABF
    
    BASEBOARD_VERSION:  1.20
    
    BUGCHECK_P1: fffffa800b401010
    
    BUGCHECK_P2: fffff8800f6069c8
    
    BUGCHECK_P3: 0
    
    BUGCHECK_P4: d
    
    FAULTING_IP: 
    nvlddmkm+1759c8
    fffff880`0f6069c8 4883ec28        sub     rsp,28h
    
    DEFAULT_BUCKET_ID:  GRAPHICS_DRIVER_TDR_FAULT
    
    CPU_COUNT: 8
    
    CPU_MHZ: d40
    
    CPU_VENDOR:  GenuineIntel
    
    CPU_FAMILY: 6
    
    CPU_MODEL: 2a
    
    CPU_STEPPING: 7
    
    CUSTOMER_CRASH_COUNT:  1
    
    BUGCHECK_STR:  0x116
    
    PROCESS_NAME:  System
    
    CURRENT_IRQL:  0
    
    ANALYSIS_VERSION: 10.0.10563.566 amd64fre
    
    STACK_TEXT:  
    fffff880`05d9b918 fffff880`10165134 : 00000000`00000116 fffffa80`0b401010 fffff880`0f6069c8 00000000`00000000 : nt!KeBugCheckEx
    fffff880`05d9b920 fffff880`10164ebb : fffff880`0f6069c8 fffffa80`0b401010 fffffa80`0b51f1e0 fffffa80`0b59e010 : dxgkrnl!TdrBugcheckOnTimeout+0xec
    fffff880`05d9b960 fffff880`0f40ff13 : fffffa80`0b401010 00000000`00000000 fffffa80`0b51f1e0 fffffa80`0b59e010 : dxgkrnl!TdrIsRecoveryRequired+0x21f
    fffff880`05d9b990 fffff880`0f43ded6 : 00000000`ffffffff 00000000`00002b04 fffff880`05d9baf0 00000000`00000002 : dxgmms1!VidSchiReportHwHang+0x40b
    fffff880`05d9ba70 fffff880`0f40b2aa : fffffa80`0b59e010 ffffffff`feced300 fffffa80`058dc310 00000000`00000000 : dxgmms1!VidSchWaitForCompletionEvent+0x196
    fffff880`05d9bab0 fffff880`0f437ff6 : 00000000`00000000 fffffa80`0c3d6d50 00000000`00000080 fffffa80`0b59e010 : dxgmms1!VidSchiScheduleCommandToRun+0x1b2
    fffff880`05d9bbc0 fffff800`02f1bb26 : 00000000`fffffc32 fffffa80`0b5c1200 fffffa80`054feb10 fffffa80`0b5c1200 : dxgmms1!VidSchiWorkerThread+0xba
    fffff880`05d9bc00 fffff800`02c72f66 : fffff800`02e01e80 fffffa80`0b5c1200 fffff800`02e0fcc0 00000000`ffffffff : nt!PspSystemThreadStartup+0x5a
    fffff880`05d9bc40 00000000`00000000 : fffff880`05d9c000 fffff880`05d96000 fffff880`0b5b8d40 00000000`00000000 : nt!KiStartSystemThread+0x16
    
    
    STACK_COMMAND:  kb
    
    FOLLOWUP_IP: 
    nvlddmkm+1759c8
    fffff880`0f6069c8 4883ec28        sub     rsp,28h
    
    SYMBOL_NAME:  nvlddmkm+1759c8
    
    FOLLOWUP_NAME:  MachineOwner
    
    MODULE_NAME: nvlddmkm
    
    IMAGE_NAME:  nvlddmkm.sys
    
    DEBUG_FLR_IMAGE_TIMESTAMP:  4e99233b
    
    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
    ---------
    
    6: kd> lmvm nvlddmkm
    Browse full module list
    start             end                 module name
    fffff880`0f491000 fffff880`10108000   nvlddmkm T (no symbols)           
        Loaded symbol image file: nvlddmkm.sys
        Image path: nvlddmkm.sys
        Image name: nvlddmkm.sys
        Browse all global symbols  functions  data
        Timestamp:        Sat Oct 15 02:07:55 2011 (4E99233B)
        CheckSum:         00C61687
        ImageSize:        00C77000
        Translations:     0000.04b0 0000.04e4 0409.04b0 0409.04e4
    


    Wanikiya and Dyami--Team Zigzag Windows IT-PRO (MS-MVP)

    Friday, October 23, 2015 1:10 PM