BSOD playing LoL, nvlddmkm.sys, dxgkrnl.sys


  1. Posts : 53
    Microsoft Windows 7 Ultimate 64-bit 7601 Multiprocessor Free Service Pack 1
       #1

    BSOD playing LoL, nvlddmkm.sys, dxgkrnl.sys


    Hi,

    These are my computer specs: (from website i bought it from)

    Specification:
    ## Intel sandy bridge Core i5 2500K 3.3GHz 6M LGA1155 Processor
    ## COOLER MASTER HYPER 212 EVO 120MM PWM Fan, 4 Direct Heat Pipes CPU Cooler
    ## Asus P8Z68-V/GEN3 Intel Z68 ATX Socket 1155 full speed CrossfireX/SLi Supported Motherboard
    > True USB 3.0 -10X Faster Date Rates!
    > True SATA 6Gb/s RAID Support - Experience the Future of Storage!
    ## Corsair Vengeance 8GB (2x4GB) DDR3 1600MHz CL9 Unbuffered Dual Channel DDR3 Memory
    ## Western Digital Blue Edition 1TB 3.5" SATA3 7200RPM 32M Cache Hard Drive
    ## LG 24x Speed internal SATAII DVD Writer
    ## EVGA GeForce GTX580 SC version 1.5GB GDDR5 PCIE Graphic Card
    ## NZXT Lexa S Black Steel Mid Tower Chassis
    ## FSP Aurum Serise 700W 80 PLUS Gold Certification >90% efficiency Power Supply

    So..I was playing couple of games of league of legends then suddenly the screen went fuzzy and my monitor had no signal. after 5 seconds BSOD popped up, i had to take a photo with my phone which displayed Stop 0x00000116 and nv1ddmkm.sys error.

    After looking around there is so many different ways to fix this problem and i would like specific help.

    I've tried installing latest video drivers but will cause BSOD upon "starting windows" screen (so i cant get into desktop). I can get into safe mode and once i delete the display driver i can start the computer normally but without the grahpics card.

    I have cleaned my computer, the graphics card fan runs upon turning on the computer and such.

    oh I have followed the instructions where i should delete installed driver, use driver sweeper, then install latest graphics card drive (tried variations but nothing works) but doesn't work.

    I just dont know where to go from here.
      My Computer


  2. Posts : 53
    Microsoft Windows 7 Ultimate 64-bit 7601 Multiprocessor Free Service Pack 1
    Thread Starter
       #2

    Bump
      My Computer


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

    2) No useless posts, e.g., thread bumping, useless one liners, junk posting to increase post count, and identical multi-postings in different forums.
    https://www.sevenforums.com/general-d...ad.html#post15

    A stop 0x117 is a display related error. It may occur due to various reasons. Display driver is one of them. And your display driver installed is not the latest one.

    Install the latest 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 320.49 WHQL. While installing, Select Custom (Advanced) install. In the next page, follow this settings:


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


    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)


    Check if the Power Supply Unit (PSU) supplying adequate power to the computer or not.
    eXtreme Power Supply Calculator
    At least 30% extra is safe. Also let us know about the wattage of the PSU.
    -----------------------------------------------------------------------------------
    BSOD ANALYSIS
    Code:
    *******************************************************************************
    *                                                                             *
    *                        Bugcheck Analysis                                    *
    *                                                                             *
    *******************************************************************************
    
    Use !analyze -v to get detailed debugging information.
    
    BugCheck 117, {fffffa80095974e0, fffff880049d3198, 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+139198 )
    
    Followup: MachineOwner
    ---------
    
    2: 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: fffffa80095974e0, Optional pointer to internal TDR recovery context (TDR_RECOVERY_CONTEXT).
    Arg2: fffff880049d3198, The pointer into responsible device driver module (e.g owner tag).
    Arg3: 0000000000000000, The secondary driver specific bucketing key.
    Arg4: 0000000000000000, Optional internal context dependent data.
    
    Debugging Details:
    ------------------
    
    
    FAULTING_IP: 
    nvlddmkm+139198
    fffff880`049d3198 ??              ???
    
    DEFAULT_BUCKET_ID:  GRAPHICS_DRIVER_TDR_TIMEOUT
    
    TAG_NOT_DEFINED_202b:  *** Unknown TAG in analysis list 202b
    
    
    CUSTOMER_CRASH_COUNT:  1
    
    BUGCHECK_STR:  0x117
    
    PROCESS_NAME:  System
    
    CURRENT_IRQL:  0
    
    STACK_TEXT:  
    fffff880`0210e2c0 fffff880`0429264b : fffffa80`095974e0 102906c9`a00038bf 00000000`00000000 fffffa80`08aed901 : watchdog!WdDbgReportRecreate+0xa3
    fffff880`0210e7e0 fffff880`042930c9 : fffff8a0`02d5cffc fffff8a0`02b45e70 fffff8a0`02c10b4f 00000000`0014c4ad : dxgkrnl!TdrUpdateDbgReport+0xcb
    fffff880`0210e830 fffff880`04293d36 : fffffa80`095974e0 fffffa80`095974e0 fffffa80`08af7d50 fffffa80`08aed010 : dxgkrnl!TdrCollectDbgInfoStage1+0x92d
    fffff880`0210e8d0 fffff880`0433af13 : fffffa80`095974e0 00000000`00000000 fffffa80`08af7d50 fffffa80`08aed010 : dxgkrnl!TdrIsRecoveryRequired+0x17a
    fffff880`0210e900 fffff880`04364cf1 : 00000000`ffffffff 00000000`0000070c 00000000`00000000 00000000`00000002 : dxgmms1!VidSchiReportHwHang+0x40b
    fffff880`0210e9e0 fffff880`04363437 : 00000000`00000102 00000000`00000006 00000000`0000070c 00000000`00000000 : dxgmms1!VidSchiCheckHwProgress+0x71
    fffff880`0210ea10 fffff880`043362d2 : ffffffff`ff676980 fffffa80`08aed010 00000000`00000000 00000000`00000000 : dxgmms1!VidSchiWaitForSchedulerEvents+0x1fb
    fffff880`0210eab0 fffff880`04362ff6 : 00000000`00000000 00000000`0000000f 00000000`00000080 fffffa80`0823d168 : dxgmms1!VidSchiScheduleCommandToRun+0x1da
    fffff880`0210ebc0 fffff800`03f1aede : 00000000`028955bb fffffa80`08b8d060 fffffa80`06718890 fffffa80`08b8d060 : dxgmms1!VidSchiWorkerThread+0xba
    fffff880`0210ec00 fffff800`03c6d906 : fffff800`03df7e80 fffffa80`08b8d060 fffff800`03e05cc0 fffff800`03e0c580 : nt!PspSystemThreadStartup+0x5a
    fffff880`0210ec40 00000000`00000000 : fffff880`0210f000 fffff880`02109000 fffff880`023cbaa0 00000000`00000000 : nt!KiStartSystemThread+0x16
    
    
    STACK_COMMAND:  .bugcheck ; kb
    
    FOLLOWUP_IP: 
    nvlddmkm+139198
    fffff880`049d3198 ??              ???
    
    SYMBOL_NAME:  nvlddmkm+139198
    
    FOLLOWUP_NAME:  MachineOwner
    
    MODULE_NAME: nvlddmkm
    
    IMAGE_NAME:  nvlddmkm.sys
    
    DEBUG_FLR_IMAGE_TIMESTAMP:  5116d804
    
    FAILURE_BUCKET_ID:  X64_0x117_IMAGE_nvlddmkm.sys
    
    BUCKET_ID:  X64_0x117_IMAGE_nvlddmkm.sys
    
    Followup: MachineOwner
    ---------
    
    2: kd> lmvm nvlddmkm
    start             end                 module name
    fffff880`0489a000 fffff880`05342000   nvlddmkm T (no symbols)           
        Loaded symbol image file: nvlddmkm.sys
        Image path: nvlddmkm.sys
        Image name: nvlddmkm.sys
        Timestamp:        Sun Feb 10 04:43:08 2013 (5116D804)
        CheckSum:         00A90CB0
        ImageSize:        00AA8000
        Translations:     0000.04b0 0000.04e4 0409.04b0 0409.04e4
    Mini Kernel Dump does not contain unloaded driver list
      My Computer


  4. Posts : 53
    Microsoft Windows 7 Ultimate 64-bit 7601 Multiprocessor Free Service Pack 1
    Thread Starter
       #4

    Arc said:
    2) No useless posts, e.g., thread bumping, useless one liners, junk posting to increase post count, and identical multi-postings in different forums.
    https://www.sevenforums.com/general-d...ad.html#post15

    A stop 0x117 is a display related error. It may occur due to various reasons. Display driver is one of them. And your display driver installed is not the latest one.

    Install the latest 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 320.49 WHQL. While installing, Select Custom (Advanced) install. In the next page, follow this settings:

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


    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)


    Check if the Power Supply Unit (PSU) supplying adequate power to the computer or not.
    eXtreme Power Supply Calculator
    At least 30% extra is safe. Also let us know about the wattage of the PSU.
    -----------------------------------------------------------------------------------
    BSOD ANALYSIS
    Code:
    *******************************************************************************
    *                                                                             *
    *                        Bugcheck Analysis                                    *
    *                                                                             *
    *******************************************************************************
     
    Use !analyze -v to get detailed debugging information.
     
    BugCheck 117, {fffffa80095974e0, fffff880049d3198, 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+139198 )
     
    Followup: MachineOwner
    ---------
     
    2: 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: fffffa80095974e0, Optional pointer to internal TDR recovery context (TDR_RECOVERY_CONTEXT).
    Arg2: fffff880049d3198, The pointer into responsible device driver module (e.g owner tag).
    Arg3: 0000000000000000, The secondary driver specific bucketing key.
    Arg4: 0000000000000000, Optional internal context dependent data.
     
    Debugging Details:
    ------------------
     
     
    FAULTING_IP: 
    nvlddmkm+139198
    fffff880`049d3198 ??              ???
     
    DEFAULT_BUCKET_ID:  GRAPHICS_DRIVER_TDR_TIMEOUT
     
    TAG_NOT_DEFINED_202b:  *** Unknown TAG in analysis list 202b
     
     
    CUSTOMER_CRASH_COUNT:  1
     
    BUGCHECK_STR:  0x117
     
    PROCESS_NAME:  System
     
    CURRENT_IRQL:  0
     
    STACK_TEXT:  
    fffff880`0210e2c0 fffff880`0429264b : fffffa80`095974e0 102906c9`a00038bf 00000000`00000000 fffffa80`08aed901 : watchdog!WdDbgReportRecreate+0xa3
    fffff880`0210e7e0 fffff880`042930c9 : fffff8a0`02d5cffc fffff8a0`02b45e70 fffff8a0`02c10b4f 00000000`0014c4ad : dxgkrnl!TdrUpdateDbgReport+0xcb
    fffff880`0210e830 fffff880`04293d36 : fffffa80`095974e0 fffffa80`095974e0 fffffa80`08af7d50 fffffa80`08aed010 : dxgkrnl!TdrCollectDbgInfoStage1+0x92d
    fffff880`0210e8d0 fffff880`0433af13 : fffffa80`095974e0 00000000`00000000 fffffa80`08af7d50 fffffa80`08aed010 : dxgkrnl!TdrIsRecoveryRequired+0x17a
    fffff880`0210e900 fffff880`04364cf1 : 00000000`ffffffff 00000000`0000070c 00000000`00000000 00000000`00000002 : dxgmms1!VidSchiReportHwHang+0x40b
    fffff880`0210e9e0 fffff880`04363437 : 00000000`00000102 00000000`00000006 00000000`0000070c 00000000`00000000 : dxgmms1!VidSchiCheckHwProgress+0x71
    fffff880`0210ea10 fffff880`043362d2 : ffffffff`ff676980 fffffa80`08aed010 00000000`00000000 00000000`00000000 : dxgmms1!VidSchiWaitForSchedulerEvents+0x1fb
    fffff880`0210eab0 fffff880`04362ff6 : 00000000`00000000 00000000`0000000f 00000000`00000080 fffffa80`0823d168 : dxgmms1!VidSchiScheduleCommandToRun+0x1da
    fffff880`0210ebc0 fffff800`03f1aede : 00000000`028955bb fffffa80`08b8d060 fffffa80`06718890 fffffa80`08b8d060 : dxgmms1!VidSchiWorkerThread+0xba
    fffff880`0210ec00 fffff800`03c6d906 : fffff800`03df7e80 fffffa80`08b8d060 fffff800`03e05cc0 fffff800`03e0c580 : nt!PspSystemThreadStartup+0x5a
    fffff880`0210ec40 00000000`00000000 : fffff880`0210f000 fffff880`02109000 fffff880`023cbaa0 00000000`00000000 : nt!KiStartSystemThread+0x16
     
     
    STACK_COMMAND:  .bugcheck ; kb
     
    FOLLOWUP_IP: 
    nvlddmkm+139198
    fffff880`049d3198 ??              ???
     
    SYMBOL_NAME:  nvlddmkm+139198
     
    FOLLOWUP_NAME:  MachineOwner
     
    MODULE_NAME: nvlddmkm
     
    IMAGE_NAME:  nvlddmkm.sys
     
    DEBUG_FLR_IMAGE_TIMESTAMP:  5116d804
     
    FAILURE_BUCKET_ID:  X64_0x117_IMAGE_nvlddmkm.sys
     
    BUCKET_ID:  X64_0x117_IMAGE_nvlddmkm.sys
     
    Followup: MachineOwner
    ---------
     
    2: kd> lmvm nvlddmkm
    start             end                 module name
    fffff880`0489a000 fffff880`05342000   nvlddmkm T (no symbols)           
        Loaded symbol image file: nvlddmkm.sys
        Image path: nvlddmkm.sys
        Image name: nvlddmkm.sys
        Timestamp:        Sun Feb 10 04:43:08 2013 (5116D804)
        CheckSum:         00A90CB0
        ImageSize:        00AA8000
        Translations:     0000.04b0 0000.04e4 0409.04b0 0409.04e4
    Mini Kernel Dump does not contain unloaded driver list
    Thanks for the reply.

    Like i said in my first post if i have the display driver installed I can't boot in normal mode. I have done what you have asked to the third bullet point. got the latest display driver 320.49 and installed like in the picture. after restarting, it will cause BSOD in the windows logo screen (where it is black and windows comes up).

    Don't think i can stress test the video card in safe mode? or can i?

    My computer isn't overclocked so I skipped the next part.

    For the power the site recommends i use 477 Watts but I use a 700W power supply so i dont think that is the issue here.

    Edit: oh and I had this computer for nearly two years now and never had any problems with it until now. pretty strange. maybe there is actual hardware damage?

    and i can't find the new dumpfiles, old ones are still there but new ones aren't being created for the new display driver bsod.

    and if i do windows update, BSOD is still there but can't get into safe mode so i have to go to a restore point before windows update.
    Last edited by kimboy; 09 Jul 2013 at 14:10.
      My Computer


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

    kimboy said:

    Like i said in my first post if i have the display driver installed I can't boot in normal mode. I have done what you have asked to the third bullet point. got the latest display driver 320.49 and installed like in the picture. after restarting, it will cause BSOD in the windows logo screen (where it is black and windows comes up).
    It will cause BSOD, or it caused BSOD?
    If the situation is the same irrespective of the driver version including the latest one, it is the GPU that is failing. Get the GPU replaced.
      My Computer


  6. Posts : 53
    Microsoft Windows 7 Ultimate 64-bit 7601 Multiprocessor Free Service Pack 1
    Thread Starter
       #6

    Arc said:
    kimboy said:

    Like i said in my first post if i have the display driver installed I can't boot in normal mode. I have done what you have asked to the third bullet point. got the latest display driver 320.49 and installed like in the picture. after restarting, it will cause BSOD in the windows logo screen (where it is black and windows comes up).
    It will cause BSOD, or it caused BSOD?
    If the situation is the same irrespective of the driver version including the latest one, it is the GPU that is failing. Get the GPU replaced.
    I originally had 310.xx then switched to 314.xx and now 320.49 which is the latest one and still causing the same problem. Can the GPU suddenly break down in the middle of gaming?
      My Computer


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

    kimboy said:
    Like i said in my first post if i have the display driver installed I can't boot in normal mode.
    ----------------------------------------------------------------------------------------
    I originally had 310.xx then switched to 314.xx and now 320.49 which is the latest one and still causing the same problem. Can the GPU suddenly break down in the middle of gaming?
    You said you cannot boot in normal mode with the display driver installed? And the situation is same with three different driver versions? Then it is the failure from the part of the GPU only.

    It may sound illogical that a GPU breaks down in the middle of a game all of a sudden, but machine depreciates slowly over time.... and machine breaks down. And for a GPU nearly two years old, if it fails it is not anything very strange.
      My Computer


  8. Posts : 53
    Microsoft Windows 7 Ultimate 64-bit 7601 Multiprocessor Free Service Pack 1
    Thread Starter
       #8

    Arc said:
    kimboy said:
    Like i said in my first post if i have the display driver installed I can't boot in normal mode.
    ----------------------------------------------------------------------------------------
    I originally had 310.xx then switched to 314.xx and now 320.49 which is the latest one and still causing the same problem. Can the GPU suddenly break down in the middle of gaming?
    You said you cannot boot in normal mode with the display driver installed? And the situation is same with three different driver versions? Then it is the failure from the part of the GPU only.

    It may sound illogical that a GPU breaks down in the middle of a game all of a sudden, but machine depreciates slowly over time.... and machine breaks down. And for a GPU nearly two years old, if it fails it is not anything very strange.
    I see, thanks for the help. I'll let you know if changing the GPU will finish the problem.
      My Computer


  9. Posts : 53
    Microsoft Windows 7 Ultimate 64-bit 7601 Multiprocessor Free Service Pack 1
    Thread Starter
       #9

    Replaced the gtx 580 for HD7970. works fine now
      My Computer


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

    Good to know :)
    For any further issue, 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 03:54.
Find Us