Frequent BSODs happening at any time


  1. Posts : 3
    Windows 7 64bit Homre Premium
       #1

    Frequent BSODs happening at any time


    Hi, I was experiencing many BSODs about a week ago, the cause was highlighted to be my NVIDIA drivers so I rolled back to a previous version and it appeared to have fixed the problem. However now they have come back with a vengeance, I assumed it might be the drivers again so I redownloaded the previous version which didn't solve the problem I then did a clean install to the most recent version which also didn't work, it BSOD'd on startup twice in a row and then as I was writing this post.

    Could someone please help to identify the cause using the dump files and if possible suggest a fix? Any help is massively appreaciated, at this point I'm preparing myself to wipe everything and do a windows 7 re-install/ repair :/

    The dump files include all of my BSOD crashes, the most useful ones would probably be the last 4 or 5 I think.
      My Computer


  2. Arc
    Posts : 35,373
    Microsoft Windows 10 Pro Insider Preview 64-bit
       #2

    All the BSODs are reporting display failure, and all those are with the driver version 353.30 WHQL.

    Test the situation with another version of the display driver installed. Uninstall the installed display driver using Display Driver Uninstaller. Then install an earlier WHQL version. Drivers | GeForce

    See how it goes. Let us know. Further troubleshooting will be needed depending on the situation.
    ___________________________________________________________
    Code:
    BugCheck 116, {fffffa8008080010, fffff88006296128, ffffffffc000009a, 4}
    
    Unable to load image \SystemRoot\system32\DRIVERS\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+833128 )
    
    Followup: MachineOwner
    ---------
    
    3: kd> !analyze -v
    *******************************************************************************
    *                                                                             *
    *                        Bugcheck Analysis                                    *
    *                                                                             *
    *******************************************************************************
    
    VIDEO_TDR_FAILURE (116)
    Attempt to reset the display driver and recover from timeout failed.
    Arguments:
    Arg1: fffffa8008080010, Optional pointer to internal TDR recovery context (TDR_RECOVERY_CONTEXT).
    Arg2: fffff88006296128, 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+833128
    fffff880`06296128 48ff2511ddebff  jmp     qword ptr [nvlddmkm+0x6f0e40 (fffff880`06153e40)]
    
    DEFAULT_BUCKET_ID:  GRAPHICS_DRIVER_TDR_FAULT
    
    CUSTOMER_CRASH_COUNT:  1
    
    BUGCHECK_STR:  0x116
    
    PROCESS_NAME:  System
    
    CURRENT_IRQL:  0
    
    ANALYSIS_VERSION: 6.3.9600.17336 (debuggers(dbg).150226-1500) amd64fre
    
    STACK_TEXT:  
    fffff880`082c4a48 fffff880`042af134 : 00000000`00000116 fffffa80`08080010 fffff880`06296128 ffffffff`c000009a : nt!KeBugCheckEx
    fffff880`082c4a50 fffff880`04282867 : fffff880`06296128 fffffa80`0c2b1000 00000000`00000000 ffffffff`c000009a : dxgkrnl!TdrBugcheckOnTimeout+0xec
    fffff880`082c4a90 fffff880`042aef43 : 00000000`ffffd846 00000000`00000080 fffffa80`08080010 00000000`0000000f : dxgkrnl!DXGADAPTER::Reset+0x2a3
    fffff880`082c4b40 fffff880`0437f03d : fffffa80`0c371720 00000000`00000080 00000000`00000000 fffffa80`0c29f410 : dxgkrnl!TdrResetFromTimeout+0x23
    fffff880`082c4bc0 fffff800`03169456 : 00000000`0768469d fffffa80`0b891350 fffffa80`06948870 fffffa80`0b891350 : dxgmms1!VidSchiWorkerThread+0x101
    fffff880`082c4c00 fffff800`02ec12c6 : fffff800`0304ee80 fffffa80`0b891350 fffff800`0305ccc0 00000000`00000002 : nt!PspSystemThreadStartup+0x5a
    fffff880`082c4c40 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KxStartSystemThread+0x16
    
    
    STACK_COMMAND:  .bugcheck ; kb
    
    FOLLOWUP_IP: 
    nvlddmkm+833128
    fffff880`06296128 48ff2511ddebff  jmp     qword ptr [nvlddmkm+0x6f0e40 (fffff880`06153e40)]
    
    SYMBOL_NAME:  nvlddmkm+833128
    
    FOLLOWUP_NAME:  MachineOwner
    
    MODULE_NAME: nvlddmkm
    
    IMAGE_NAME:  nvlddmkm.sys
    
    DEBUG_FLR_IMAGE_TIMESTAMP:  5581075a
    
    FAILURE_BUCKET_ID:  X64_0x116_IMAGE_nvlddmkm.sys
    
    BUCKET_ID:  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
    ---------
    
    3: kd> lmvm nvlddmkm
    start             end                 module name
    fffff880`05a63000 fffff880`0652c000   nvlddmkm T (no symbols)           
        Loaded symbol image file: nvlddmkm.sys
        Image path: \SystemRoot\system32\DRIVERS\nvlddmkm.sys
        Image name: nvlddmkm.sys
        Timestamp:        Wed Jun 17 11:06:26 2015 (5581075A)
        CheckSum:         00A850BE
        ImageSize:        00AC9000
        Translations:     0000.04b0 0000.04e4 0409.04b0 0409.04e4
      My Computer


 

  Related Discussions
Our Sites
Site Links
About Us
Windows 7 Forums is an independent web site and has not been authorized, sponsored, or otherwise approved by Microsoft Corporation. "Windows 7" and related materials are trademarks of Microsoft Corp.

© Designer Media Ltd
All times are GMT -5. The time now is 03:11.
Find Us