locked
BlueScreen Occurs even after Windows 7 reinstallation RRS feed

  • Question

  • I post a message before about this BlueScreen error, but the intructions given me is very hard to do it and understand. So now I re-install my windows 7 then after a few hours a blackscreen on my monitor but my CPU still on, So I restart my PC then it says the windows has unexpected shutdown, I click the details and I found out that it was a Bluescreen again...T_T I have uploaded two dump files one from kernel reports and one from minidump to the location below:

    https://onedrive.live.com/redir?resid=56CE63709EDBEB64!108&authkey=!AJ0GaIah4YVtEVM&ithint=folder%2cdmp

    I post this question so that everyone will know about my problem and pls...don't give me a hard instructions to fix and it makes me confuse because I'm not a tech guy. THANKS EVERYONE!!!


    • Edited by Nardoo Friday, November 13, 2015 3:14 PM
    Friday, November 13, 2015 3:12 PM

Answers

  • Hi,

    After analyzing the dump which you uploaded, I get the result below.

    Microsoft (R) Windows Debugger Version 6.12.0002.633 AMD64
    Copyright (c) Microsoft Corporation. All rights reserved.
    
    
    Loading Dump File [C:\Users\Administrator\Desktop\OneDrive-2015-11-15\WD-20151113-2047.dmp]
    Mini Kernel Dump File: Only registers and stack trace are available
    
    Symbol search path is: SRV*C:\Symbols*http://msdl.microsoft.com/download/symbols
    Executable search path is: 
    Windows 7 Kernel Version 7601 (Service Pack 1) MP (2 procs) Free x86 compatible
    Product: WinNt, suite: TerminalServer SingleUserTS Personal
    Built by: 7601.17514.x86fre.win7sp1_rtm.101119-1850
    Machine Name:
    Kernel base = 0x82a1a000 PsLoadedModuleList = 0x82b64850
    Debug session time: Fri Nov 13 20:47:13.525 2015 (UTC + 8:00)
    System Uptime: 0 days 0:44:49.977
    Loading Kernel Symbols
    ...............................................................
    ................................................................
    .............
    Loading User Symbols
    Mini Kernel Dump does not contain unloaded driver list
    *******************************************************************************
    *                                                                             *
    *                        Bugcheck Analysis                                    *
    *                                                                             *
    *******************************************************************************
    
    Use !analyze -v to get detailed debugging information.
    
    BugCheck 117, {84eba050, 8ef45036, 0, 0}
    
    Unable to load image nvlddmkm.sys, Win32 error 0n2
    *** 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+113036 )
    
    Followup: MachineOwner
    ---------
    
    0: kd> !analyze -v
    *******************************************************************************
    *                                                                             *
    *                        Bugcheck Analysis                                    *
    *                                                                             *
    *******************************************************************************
    
    VIDEO_TDR_TIMEOUT_DETECTED (117)
    The display driver failed to respond in timely fashion.
    (This code can never be used for real bugcheck).
    Arguments:
    Arg1: 84eba050, Optional pointer to internal TDR recovery context (TDR_RECOVERY_CONTEXT).
    Arg2: 8ef45036, The pointer into responsible device driver module (e.g owner tag).
    Arg3: 00000000, The secondary driver specific bucketing key.
    Arg4: 00000000, Optional internal context dependent data.
    
    Debugging Details:
    ------------------
    
    
    FAULTING_IP: 
    nvlddmkm+113036
    8ef45036 ??              ???
    
    DEFAULT_BUCKET_ID:  GRAPHICS_DRIVER_TDR_TIMEOUT
    
    TAG_NOT_DEFINED_202b:  *** Unknown TAG in analysis list 202b
    
    
    BUGCHECK_STR:  0x117
    
    PROCESS_NAME:  System
    
    CURRENT_IRQL:  0
    
    STACK_TEXT:  
    807a5cb4 8f8eb101 00000000 8ef45036 8c0a607e dxgkrnl!TdrUpdateDbgReport+0x68
    807a5cdc 8f8eacc0 00000000 82a5150e 84eba050 dxgkrnl!TdrCollectDbgInfoStage2+0x1ab
    807a5d18 8f8eb15c 84eba050 867d6788 807a5d3c dxgkrnl!DXGADAPTER::Reset+0xb6
    807a5d28 8f94b20b 84eba050 867d6788 00000000 dxgkrnl!TdrResetFromTimeout+0x12
    807a5d3c 8f94e485 867d6788 00000000 86840948 dxgmms1!VidSchiRecoverFromTDR+0x15
    807a5d50 82c23f5e 867d6788 ab1a3627 00000000 dxgmms1!VidSchiWorkerThread+0x7f
    807a5d90 82acb219 8f94e406 867d6788 00000000 nt!PspSystemThreadStartup+0x9e
    00000000 00000000 00000000 00000000 00000000 nt!KiThreadStartup+0x19
    
    
    STACK_COMMAND:  .bugcheck ; kb
    
    FOLLOWUP_IP: 
    nvlddmkm+113036
    8ef45036 ??              ???
    
    SYMBOL_NAME:  nvlddmkm+113036
    
    FOLLOWUP_NAME:  MachineOwner
    
    MODULE_NAME: nvlddmkm
    
    IMAGE_NAME:  nvlddmkm.sys
    
    DEBUG_FLR_IMAGE_TIMESTAMP:  4d9e7e9b
    
    FAILURE_BUCKET_ID:  0x117_IMAGE_nvlddmkm.sys
    
    BUCKET_ID:  0x117_IMAGE_nvlddmkm.sys
    
    Followup: MachineOwner

    I consider the issue may caused by the driver called "nvlddmkm.sys". After research, I found the driver is related to Nvidia display driver. You would better go to the Nvidia official website to download the latest driver version for your hardware and reinstall it. Pay attention to the driver needed to be matched for your system edition bit.

    Good luck to fix it.

    Best Regards

    Simon


    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, November 16, 2015 7:05 AM

All replies

  • First DMP indicates that it crashed on your processor, either a bad driver or bad hardware. Second DMP indicates that its your video card driver. I would boot into safe mode if you can, completely remove the video card driver and reinstall, and then update your processor drivers as well.

    If the crashes continue, I'd run driver verifier and post a link to the DMP it generates. Instructions for verifier can be found here.

    Friday, November 13, 2015 4:27 PM
  • Hi,

    After analyzing the dump which you uploaded, I get the result below.

    Microsoft (R) Windows Debugger Version 6.12.0002.633 AMD64
    Copyright (c) Microsoft Corporation. All rights reserved.
    
    
    Loading Dump File [C:\Users\Administrator\Desktop\OneDrive-2015-11-15\WD-20151113-2047.dmp]
    Mini Kernel Dump File: Only registers and stack trace are available
    
    Symbol search path is: SRV*C:\Symbols*http://msdl.microsoft.com/download/symbols
    Executable search path is: 
    Windows 7 Kernel Version 7601 (Service Pack 1) MP (2 procs) Free x86 compatible
    Product: WinNt, suite: TerminalServer SingleUserTS Personal
    Built by: 7601.17514.x86fre.win7sp1_rtm.101119-1850
    Machine Name:
    Kernel base = 0x82a1a000 PsLoadedModuleList = 0x82b64850
    Debug session time: Fri Nov 13 20:47:13.525 2015 (UTC + 8:00)
    System Uptime: 0 days 0:44:49.977
    Loading Kernel Symbols
    ...............................................................
    ................................................................
    .............
    Loading User Symbols
    Mini Kernel Dump does not contain unloaded driver list
    *******************************************************************************
    *                                                                             *
    *                        Bugcheck Analysis                                    *
    *                                                                             *
    *******************************************************************************
    
    Use !analyze -v to get detailed debugging information.
    
    BugCheck 117, {84eba050, 8ef45036, 0, 0}
    
    Unable to load image nvlddmkm.sys, Win32 error 0n2
    *** 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+113036 )
    
    Followup: MachineOwner
    ---------
    
    0: kd> !analyze -v
    *******************************************************************************
    *                                                                             *
    *                        Bugcheck Analysis                                    *
    *                                                                             *
    *******************************************************************************
    
    VIDEO_TDR_TIMEOUT_DETECTED (117)
    The display driver failed to respond in timely fashion.
    (This code can never be used for real bugcheck).
    Arguments:
    Arg1: 84eba050, Optional pointer to internal TDR recovery context (TDR_RECOVERY_CONTEXT).
    Arg2: 8ef45036, The pointer into responsible device driver module (e.g owner tag).
    Arg3: 00000000, The secondary driver specific bucketing key.
    Arg4: 00000000, Optional internal context dependent data.
    
    Debugging Details:
    ------------------
    
    
    FAULTING_IP: 
    nvlddmkm+113036
    8ef45036 ??              ???
    
    DEFAULT_BUCKET_ID:  GRAPHICS_DRIVER_TDR_TIMEOUT
    
    TAG_NOT_DEFINED_202b:  *** Unknown TAG in analysis list 202b
    
    
    BUGCHECK_STR:  0x117
    
    PROCESS_NAME:  System
    
    CURRENT_IRQL:  0
    
    STACK_TEXT:  
    807a5cb4 8f8eb101 00000000 8ef45036 8c0a607e dxgkrnl!TdrUpdateDbgReport+0x68
    807a5cdc 8f8eacc0 00000000 82a5150e 84eba050 dxgkrnl!TdrCollectDbgInfoStage2+0x1ab
    807a5d18 8f8eb15c 84eba050 867d6788 807a5d3c dxgkrnl!DXGADAPTER::Reset+0xb6
    807a5d28 8f94b20b 84eba050 867d6788 00000000 dxgkrnl!TdrResetFromTimeout+0x12
    807a5d3c 8f94e485 867d6788 00000000 86840948 dxgmms1!VidSchiRecoverFromTDR+0x15
    807a5d50 82c23f5e 867d6788 ab1a3627 00000000 dxgmms1!VidSchiWorkerThread+0x7f
    807a5d90 82acb219 8f94e406 867d6788 00000000 nt!PspSystemThreadStartup+0x9e
    00000000 00000000 00000000 00000000 00000000 nt!KiThreadStartup+0x19
    
    
    STACK_COMMAND:  .bugcheck ; kb
    
    FOLLOWUP_IP: 
    nvlddmkm+113036
    8ef45036 ??              ???
    
    SYMBOL_NAME:  nvlddmkm+113036
    
    FOLLOWUP_NAME:  MachineOwner
    
    MODULE_NAME: nvlddmkm
    
    IMAGE_NAME:  nvlddmkm.sys
    
    DEBUG_FLR_IMAGE_TIMESTAMP:  4d9e7e9b
    
    FAILURE_BUCKET_ID:  0x117_IMAGE_nvlddmkm.sys
    
    BUCKET_ID:  0x117_IMAGE_nvlddmkm.sys
    
    Followup: MachineOwner

    I consider the issue may caused by the driver called "nvlddmkm.sys". After research, I found the driver is related to Nvidia display driver. You would better go to the Nvidia official website to download the latest driver version for your hardware and reinstall it. Pay attention to the driver needed to be matched for your system edition bit.

    Good luck to fix it.

    Best Regards

    Simon


    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, November 16, 2015 7:05 AM