BSOD playing any game; ntoskrnl.exe+75c00 and dxgkrnl.exe+5d054


  1. Posts : 2
    Windows 7 home Premium 64-bit
       #1

    BSOD playing any game; ntoskrnl.exe+75c00 and dxgkrnl.exe+5d054


    Hey there,
    For last couple of days i have been recieving BSOD for unknown reason. It happens when i' m playing any kind of game. My PC just dies after like 15min playing game. I dont know what to do, so please help.
    It started like week ago and since then i have not had any chance to play a game. Before that everything was running smoothly, dunno what happened. :)

    There are some file attached, becouse instruction said i need to
      My Computer


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

    Hello Butterflyes. You are having stop 0x116 BSOD which is a graphics/display related BSOD.

    As you have the latest version of display driver installed, I would suggest you to install the 314.22 WHQL only.

    • Uninstall All nvidia items in Control Panel > Programs and features
      • 3D Vision Control Driver
      • 3D Vision Driver
      • Graphics Driver
      • HD Audio Driver
      • PhysX
      • nvidia Update

      (Are you using nvidia chipset drivers? If so, dont uninstall anything other than those are listed).
    • Now follow Drivers - Clean Left over Files after Uninstalling
    • Boot normally now. Go to Drivers - Download NVIDIA Drivers, Download 314.22 WHQL. While installing, Select Custom (Advanced) install. In the next page, follow this settings:


    The computer seems to be old by a couple of years. Is it running hot? Upload a snapshot Using Speccy.


    Stress test the Graphics Card using Furmark.
    Video Card - Stress Test with Furmark

    Check if the Power Supply Unit (PSU) supplying adequate power to the computer or not.
    eXtreme Power Supply Calculator
    Also let us know the wattage of the PSU.

    Are you overclocking? As you are getting BSODs, you should stop overclocking and run all the hardware components like CPU, GPU and RAM to their default settings. Also set the BIOS to default, too.
    How To Clear CMOS (Reset BIOS)

    Let us know the results.
    ____________________________________________________________________________
    BSOD ANALYSIS:
    Code:
    *******************************************************************************
    *                                                                             *
    *                        Bugcheck Analysis                                    *
    *                                                                             *
    *******************************************************************************
    
    Use !analyze -v to get detailed debugging information.
    
    BugCheck 116, {fffffa800af9f010, fffff880059b1e30, 0, 2}
    
    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+13be30 )
    
    Followup: MachineOwner
    ---------
    
    0: kd> !analyze -v
    *******************************************************************************
    *                                                                             *
    *                        Bugcheck Analysis                                    *
    *                                                                             *
    *******************************************************************************
    
    VIDEO_TDR_FAILURE (116)
    Attempt to reset the display driver and recover from timeout failed.
    Arguments:
    Arg1: fffffa800af9f010, Optional pointer to internal TDR recovery context (TDR_RECOVERY_CONTEXT).
    Arg2: fffff880059b1e30, The pointer into responsible device driver module (e.g. owner tag).
    Arg3: 0000000000000000, Optional error code (NTSTATUS) of the last failed operation.
    Arg4: 0000000000000002, Optional internal context dependent data.
    
    Debugging Details:
    ------------------
    
    
    FAULTING_IP: 
    nvlddmkm+13be30
    fffff880`059b1e30 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`026dd888 fffff880`04531054 : 00000000`00000116 fffffa80`0af9f010 fffff880`059b1e30 00000000`00000000 : nt!KeBugCheckEx
    fffff880`026dd890 fffff880`04530d5e : fffff880`059b1e30 fffffa80`0af9f010 fffffa80`0ab20960 fffffa80`0ae8a410 : dxgkrnl!TdrBugcheckOnTimeout+0xec
    fffff880`026dd8d0 fffff880`0440ff13 : fffffa80`0af9f010 00000000`00000000 fffffa80`0ab20960 fffffa80`0ae8a410 : dxgkrnl!TdrIsRecoveryRequired+0x1a2
    fffff880`026dd900 fffff880`04439cf1 : 00000000`ffffffff 00000000`000036e9 00000000`00000000 00000000`00000002 : dxgmms1!VidSchiReportHwHang+0x40b
    fffff880`026dd9e0 fffff880`04438437 : 00000000`00000102 00000000`00000006 00000000`000036e9 00000000`00000000 : dxgmms1!VidSchiCheckHwProgress+0x71
    fffff880`026dda10 fffff880`0440b2d2 : ffffffff`ff676980 fffffa80`0ae8a410 00000000`00000000 00000000`00000000 : dxgmms1!VidSchiWaitForSchedulerEvents+0x1fb
    fffff880`026ddab0 fffff880`04437ff6 : 00000000`00000000 fffffa80`0ab7cd50 00000000`00000080 fffffa80`0ae8a410 : dxgmms1!VidSchiScheduleCommandToRun+0x1da
    fffff880`026ddbc0 fffff800`02d75ede : 00000000`fffffc32 fffffa80`0ab23b50 fffffa80`066ebb30 fffffa80`0ab23b50 : dxgmms1!VidSchiWorkerThread+0xba
    fffff880`026ddc00 fffff800`02ac8906 : fffff880`031d7180 fffffa80`0ab23b50 fffff880`031e1fc0 00000000`00000000 : nt!PspSystemThreadStartup+0x5a
    fffff880`026ddc40 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiStartSystemThread+0x16
    
    
    STACK_COMMAND:  .bugcheck ; kb
    
    FOLLOWUP_IP: 
    nvlddmkm+13be30
    fffff880`059b1e30 4055            push    rbp
    
    SYMBOL_NAME:  nvlddmkm+13be30
    
    FOLLOWUP_NAME:  MachineOwner
    
    MODULE_NAME: nvlddmkm
    
    IMAGE_NAME:  nvlddmkm.sys
    
    DEBUG_FLR_IMAGE_TIMESTAMP:  51c41788
    
    FAILURE_BUCKET_ID:  X64_0x116_IMAGE_nvlddmkm.sys
    
    BUCKET_ID:  X64_0x116_IMAGE_nvlddmkm.sys
    
    Followup: MachineOwner
    ---------
    
    0: kd> lmvm nvlddmkm
    start             end                 module name
    fffff880`05876000 fffff880`0635b000   nvlddmkm T (no symbols)           
        Loaded symbol image file: nvlddmkm.sys
        Image path: \SystemRoot\system32\DRIVERS\nvlddmkm.sys
        Image name: nvlddmkm.sys
        Timestamp:        Fri Jun 21 14:36:16 2013 (51C41788)
        CheckSum:         00AB87FF
        ImageSize:        00AE5000
        Translations:     0000.04b0 0000.04e4 0409.04b0 0409.04e4
      My Computer


  3. Posts : 2
    Windows 7 home Premium 64-bit
    Thread Starter
       #3

    Okey, thanks for the advice, but it didn't work, becouse the version 314.22 WHQL didn' t work on my PC. i attached the error picture. + I attached zipped specy file, whit my data i guess.
    Any new ideas?
      My Computer


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

    If it is a newer GPU, the old version of th display driver may not be installed on it. You will have to wait for another release.

    Temps are not bad there.

    Take the other suggestions and let us know.
      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 08:21.
Find Us