BSOD on Win 7 64bit - dxgkrnl.sys

Discussion in 'Windows 7 Blue Screen of Death (BSOD)' started by John Holliday, May 20, 2011.

  1. John Holliday

    John Holliday New Member

    Joined:
    May 20, 2011
    Messages:
    10
    Likes Received:
    0
    Hi, first time poster long term luker!

    If anyone can help me with this, I'd appreciate it. I have currently been plagued by this BSOD for a week or two now, and it's getting to the point where I need to ask for help, as it's driving me mad.

    Firstly the common file that crashes seems to be dxgkrnl.sys, however NLDDMKM.sys (Nvida drivers) would crash sometimes, leading to the imfamous "nvlddmkm stopped responding"


    Firstly the Windows bsod pop up.

    Problem signature:
    Problem Event Name: BlueScreen
    OS Version: 6.1.7600.2.0.0.256.1
    Locale ID: 1033

    Additional information about the problem:
    BCCode: 116
    BCP1: FFFFFA800843A0E0
    BCP2: FFFFF880106C6970
    BCP3: FFFFFFFFC000009A
    BCP4: 0000000000000004
    OS Version: 6_1_7600
    Service Pack: 0_0
    Product: 256_1

    I know I haven't got SP1 installed, but I was going to get around to it after I got the computer up and running, then I ran into this headache!

    My set up is:

    Intel i7 950
    6gb Cosair 1333Mhz Ram.
    Foxconn Flaming Blade GTI
    Zotac GTS 450 1gb AMP edition (factory overclocked)
    2x 250gb HDDs
    1x 500gb HDD

    What I've done so far:

    I have currently ran Memtest86 outside of Windows for 10 attempts, and have got no errors. Also used the windows memory tester - though not sure how accurate that is. Either way both have come back negative.

    SFC/Scannow

    Have run it quite a few times, and has not picked up anything.

    Chkdsk

    Also ran it when I started to get the BSOD, but haven't since, so maybe need to again.

    Gts 450 1gb Amp edition by Zotac

    Like I mentioned above, this is a factory overclocked card, so I used MSI afterburner to scale the core and shader clocks back to stock settings.

    Reinstall Drivers for graphics card

    The time I started to get this was around the release of GeForce/ION Driver v270.61, as I was playing Crysis at the time and I thought new drivers might give me a FPS boost. Since then it's been somewhat unstable. I have tried driver cleaner (safe mode) to remove traces of the drivers, and downgrade to older ones, but I still get the BSOD.


    What I haven't done"

    Have not opened the case to reseat the graphics card, if needed as that was going to be my next step over the weekend. Nor have I have reinstalled Windows 7, as iwas giving me issues. Starting and stopping and setup etc.

    I have added a zip file containing all the mini dumps that have been created recently as well as a screenshot from CPUZ. And if anyone can assist me, I'd be grateful.

    Thank you.

    Edit: Sorry, I didn't know which area of the forum this would go in. Here or the graphics area, as it's both to do with BSOD and Graphics (possibly)
     

    Attached Files:

    #1 John Holliday, May 20, 2011
    Last edited: May 20, 2011
  2. kaos

    kaos Senior Member

    Joined:
    May 9, 2011
    Messages:
    1,747
    Likes Received:
    33
    THIS IS THE LATEST DUMP FILE
    Code:
    ....
    *******************************************************************************
    *                                                                             *
    *                        Bugcheck Analysis                                    *
    *                                                                             *
    *******************************************************************************
    
    Use !analyze -v to get detailed debugging information.
    
    BugCheck 116, {fffffa800843a0e0, fffff880106c6970, 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+7e4970 )
    
    Followup: MachineOwner
    ---------
    
    7: kd> !analyze -v
    *******************************************************************************
    *                                                                             *
    *                        Bugcheck Analysis                                    *
    *                                                                             *
    *******************************************************************************
    
    VIDEO_TDR_FAILURE (116)
    Attempt to reset the display driver and recover from timeout failed.
    Arguments:
    Arg1: fffffa800843a0e0, Optional pointer to internal TDR recovery context (TDR_RECOVERY_CONTEXT).
    Arg2: fffff880106c6970, 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+7e4970
    fffff880`106c6970 4883ec28        sub     rsp,28h
    
    DEFAULT_BUCKET_ID:  GRAPHICS_DRIVER_TDR_FAULT
    
    CUSTOMER_CRASH_COUNT:  1
    
    BUGCHECK_STR:  0x116
    
    PROCESS_NAME:  System
    
    CURRENT_IRQL:  0
    
    STACK_TEXT:  
    fffff880`056e2b88 fffff880`04279000 : 00000000`00000116 fffffa80`0843a0e0 fffff880`106c6970 ffffffff`c000009a : nt!KeBugCheckEx
    fffff880`056e2b90 fffff880`0424c867 : fffff880`106c6970 fffffa80`07da9000 00000000`00000000 ffffffff`c000009a : dxgkrnl!TdrBugcheckOnTimeout+0xec
    fffff880`056e2bd0 fffff880`04278e0f : fffffa80`ffffd84d 00000000`00000000 fffffa80`0843a0e0 00000000`00000000 : dxgkrnl!DXGADAPTER::Reset+0x2a3
    fffff880`056e2c80 fffff880`04347ec1 : fffffa80`068ff210 00000000`00000080 00000000`00000000 fffffa80`07da4010 : dxgkrnl!TdrResetFromTimeout+0x23
    fffff880`056e2d00 fffff800`0316abc6 : 00000000`031496a0 fffffa80`07dc7060 fffffa80`05df2040 fffffa80`07dc7060 : dxgmms1!VidSchiWorkerThread+0x101
    fffff880`056e2d40 fffff800`02ea5bc6 : fffff800`03041e80 fffffa80`07dc7060 fffff800`0304fc40 fffff880`0125c2b4 : nt!PspSystemThreadStartup+0x5a
    fffff880`056e2d80 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiStartSystemThread+0x16
    
    
    STACK_COMMAND:  .bugcheck ; kb
    
    FOLLOWUP_IP: 
    nvlddmkm+7e4970
    fffff880`106c6970 4883ec28        sub     rsp,28h
    
    SYMBOL_NAME:  nvlddmkm+7e4970
    
    FOLLOWUP_NAME:  MachineOwner
    
    MODULE_NAME: nvlddmkm
    
    IMAGE_NAME:  nvlddmkm.sys
    
    DEBUG_FLR_IMAGE_TIMESTAMP:  4d9e7f64
    
    FAILURE_BUCKET_ID:  X64_0x116_IMAGE_nvlddmkm.sys
    
    BUCKET_ID:  X64_0x116_IMAGE_nvlddmkm.sys
    
    Followup: MachineOwner
    

    its definatly related to the graphics card,

    are u overclocking your card?
     
  3. John Holliday

    John Holliday New Member

    Joined:
    May 20, 2011
    Messages:
    10
    Likes Received:
    0
    Hi, Kaos, and thanks for the reply.

    The graphics card is a 1gb Zotac GTS 450 AMP! Edition. Which, as far as I was aware came factory overclocked. A couple of days ago I scaled back the core and shader clock to the settings a stock - none over clocked GTS 450 - would have.

    I did change the memory clock, but immediately unchanged it, as I was worried I was biting off more than I can chew, as over, and underclocking is not really my forte. The only reason I had MSI afterburner in the first place, was because the GTS standard fan speed seems to be 30 percent, and I needed it higher to keep it cool.

    Thanks for the reply, appreciated.
     
    #3 John Holliday, May 20, 2011
    Last edited: May 20, 2011
  4. Saltgrass

    Saltgrass Excellent Member
    Microsoft Community Contributor

    Joined:
    Oct 16, 2009
    Messages:
    15,157
    Likes Received:
    393
    You show a driver that seems to be related to the EVGA Precision software. RTCore64 shows as 2005 on your system, but I just downloaded a new version and it shows 5/2011. Maybe you could update that utility. If you have already, then it did not replace the older file version, or so it appears. Maybe you need to clean the old install prior to installing again.
     
  5. John Holliday

    John Holliday New Member

    Joined:
    May 20, 2011
    Messages:
    10
    Likes Received:
    0
    Hi Saltgrass - thanks for the reply!

    EVGA was installed on the system, but was never used. I installed it around the same time I was playing Crysis, to try and control the temp of the graphics card. .

    I had a quick look as well, and noticed that RTCore32 with MSI Afterburner, is dated from 2005 as well:

    (copy and paste from log)
    4608 5/25/2005 8:39:06 PM "C:\Program Files (x86)\EVGA Precision\RTCore32.sys
    4608 5/25/2005 4:39:06 AM "C:\Program Files (x86)\MSI Afterburner\RTCore32.sys

    So am going to remove both, just to see.


    Thank you.
     
    #5 John Holliday, May 20, 2011
    Last edited: May 20, 2011
  6. Saltgrass

    Saltgrass Excellent Member
    Microsoft Community Contributor

    Joined:
    Oct 16, 2009
    Messages:
    15,157
    Likes Received:
    393
    The 32 bit version is still dated from 2005, it has not been updated. The 64 bit version was updated on 5/3/2011, so maybe they needed to update due to some problem.

    Hopefully some more experienced folks will come by, but it won't hurt to try removing the utility, or at least updating it.
     
  7. John Holliday

    John Holliday New Member

    Joined:
    May 20, 2011
    Messages:
    10
    Likes Received:
    0
    Hi, Saltgrass

    Yeah, that is quite odd. Not sure why that is, but removed it anyhow, as it's not needed and it's one lead to narrow down.

    Thanks!
     
  8. John Holliday

    John Holliday New Member

    Joined:
    May 20, 2011
    Messages:
    10
    Likes Received:
    0
    Dam just done it again while playing Crysis. Instead of a blue screen it was like an orange screen, but with no BSOD writing.

    Thought it was working better than it was anyhow. Oh well :(
     

Share This Page

Loading...