1. You are viewing our forum as a guest. For full access please Register. WindowsBBS.com is completely free, paid for by advertisers and donations.

Resolved I think my Graphics card is fried: 0x00000116

Discussion in 'PC Hardware' started by ese123, 2015/01/31.

  1. 2015/01/31
    ese123

    ese123 Inactive Thread Starter

    Joined:
    2015/01/31
    Messages:
    6
    Likes Received:
    0
    Hi, first post. My system specs:
    Intel 2500k
    Asus P8z77 Pro
    Nvidia 580 GTX THE CULPRIT
    2x 4gb ram
    Antec HCG 750 psu
    Windows 7 x64
    1x SSD, 1 HDD

    BSOD:0x00000116
    caused by driver: dxgkrnl.sys

    My system has been flawless for a years. Suddenly, graphical artifacts appeared in windows while not running any intensive graphics applications. About 5 seconds later and I got a BSOD - DMP file below. Now I have artifacts everywhere and the graphics card isn't really recognized. My resolution is reset (although I somehow updated my graphics driver) and I can't read GPU temperatures from the card. CPUZ does not recognize the graphics card.

    I don't think it was ever overheating since I have a big case and have monitored temps when I overclocked my CPU. I think the card is fried, I was just wondering if there were any additional tests I could run to be sure.

    link to the dmp file.
    https://www.dropbox.com/s/0aeoy74qqqxcewy/013115-8330-01.dmp?dl=0

    Please help! Thanks!
     
  2. 2015/01/31
    MrBill

    MrBill SuperGeek WindowsBBS Team Member

    Joined:
    2006/01/14
    Messages:
    4,292
    Likes Received:
    266
    Well, I for one will not open the file you have linked to. Have no idea if it is clean or not. Won't take the chance.

    Do you have an on board Graphics card? If so try it or try another graphics card. That would be the best test.
     

  3. to hide this advert.

  4. 2015/02/01
    ese123

    ese123 Inactive Thread Starter

    Joined:
    2015/01/31
    Messages:
    6
    Likes Received:
    0
    Yep, I can enable the HD 3000 on my 2500K and everything is back to normal - this leads me to think the card is busted. Is there another way to upload the dmp file? I'd be happy to send it any other way, I just figured dropbox would be the easiest!
     
  5. 2015/02/01
    Evan Omo

    Evan Omo Computer Support Technician Staff

    Joined:
    2006/09/10
    Messages:
    7,899
    Likes Received:
    510
    Hi ese123, Welcome to Windowsbbs! :)

    Follow these instructions to post a Dump Data Log.

    If you do not have a dump, ensure that your machine is configured to write out a dump by following the directions from microsoft.

    If your computer works with the integrated video chip and you have tested your video card in another computer and the same thing happens then the video card has most likely failed and you will need to get it replaced.

    If you are overclocking any components, return them to their stock values and see if the issue is still present with the video card.

    Also please enter your System Details. It helps us in answering your questions.

    Note: A common error is to forget to show your System Details in your profile:

    Make sure to do the above when entering your System Details, thanks.
     
  6. 2015/02/01
    ese123

    ese123 Inactive Thread Starter

    Joined:
    2015/01/31
    Messages:
    6
    Likes Received:
    0
    Voila! I hope this is legible enough

    Opened log file 'c:debuglog.txt'

    ************* Symbol Path validation summary **************
    Response Time (ms) Location
    Deferred SRV*c:\symbols*http://msdl.microsoft.com/download/symbols

    ************* Symbol Path validation summary **************
    Response Time (ms) Location
    OK C:\Windows
    OK C:\Windows\system32
    OK C:\Windows\system32\drivers

    Microsoft (R) Windows Debugger Version 6.3.9600.17298 AMD64
    Copyright (c) Microsoft Corporation. All rights reserved.


    Loading Dump File [C:\Windows\Minidump\013115-8330-01.dmp]
    Mini Kernel Dump File: Only registers and stack trace are available


    ************* Symbol Path validation summary **************
    Response Time (ms) Location
    OK C:\Windows
    OK C:\Windows\system32
    OK C:\Windows\system32\drivers

    ************* Symbol Path validation summary **************
    Response Time (ms) Location
    Deferred SRV*c:\symbols*http://msdl.microsoft.com/download/symbols
    Symbol search path is: SRV*c:\symbols*http://msdl.microsoft.com/download/symbols
    Executable search path is: C:\Windows;C:\Windows\system32;C:\Windows\system32\drivers
    Windows 7 Kernel Version 7601 (Service Pack 1) MP (4 procs) Free x64
    Product: WinNt, suite: TerminalServer SingleUserTS
    Built by: 7601.18700.amd64fre.win7sp1_gdr.141211-1742
    Machine Name:
    Kernel base = 0xfffff800`02c0d000 PsLoadedModuleList = 0xfffff800`02e50890
    Debug session time: Sat Jan 31 09:47:53.286 2015 (UTC - 5:00)
    System Uptime: 0 days 0:00:31.130
    Loading Kernel Symbols
    ...............................................................
    ................................................................
    .............................
    Loading User Symbols
    Loading unloaded module list
    ....
    *******************************************************************************
    * *
    * Bugcheck Analysis *
    * *
    *******************************************************************************

    Use !analyze -v to get detailed debugging information.

    BugCheck 116, {fffffa800e261010, fffff8800f9aa51c, ffffffffc000009a, 4}

    *** ERROR: Symbol file could not be found. Defaulted to export symbols for nvlddmkm.sys -
    Probably caused by : nvlddmkm.sys ( nvlddmkm!nvDumpConfig+1ff74c )

    Followup: MachineOwner
    ---------

    3: kd> !analyze -v;r;kv;lmtn;.logclose;q
    *******************************************************************************
    * *
    * Bugcheck Analysis *
    * *
    *******************************************************************************

    VIDEO_TDR_FAILURE (116)
    Attempt to reset the display driver and recover from timeout failed.
    Arguments:
    Arg1: fffffa800e261010, Optional pointer to internal TDR recovery context (TDR_RECOVERY_CONTEXT).
    Arg2: fffff8800f9aa51c, 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!nvDumpConfig+1ff74c
    fffff880`0f9aa51c 48ff255dc9ecff jmp qword ptr [nvlddmkm!nvDumpConfig+0xcc0b0 (fffff880`0f876e80)]

    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.17298 (debuggers(dbg).141024-1500) amd64fre

    STACK_TEXT:
    fffff880`025f7a48 fffff880`03b44134 : 00000000`00000116 fffffa80`0e261010 fffff880`0f9aa51c ffffffff`c000009a : nt!KeBugCheckEx
    fffff880`025f7a50 fffff880`03b17867 : fffff880`0f9aa51c fffffa80`09efa000 00000000`00000000 ffffffff`c000009a : dxgkrnl!TdrBugcheckOnTimeout+0xec
    fffff880`025f7a90 fffff880`03b43f43 : fffffa80`ffffd846 ffffffff`fffe7960 fffffa80`0e261010 00000000`00000000 : dxgkrnl!DXGADAPTER::Reset+0x2a3
    fffff880`025f7b40 fffff880`0fd9d03d : fffffa80`0cb6f6c0 00000000`00000080 00000000`00000000 fffffa80`09eda410 : dxgkrnl!TdrResetFromTimeout+0x23
    fffff880`025f7bc0 fffff800`02f200ca : 00000000`01b41e25 fffffa80`08ac7a00 fffffa80`066f21b0 fffffa80`08ac7a00 : dxgmms1!VidSchiWorkerThread+0x101
    fffff880`025f7c00 fffff800`02c74be6 : fffff880`02fd7180 fffffa80`08ac7a00 fffff880`02fe1fc0 00000000`00000000 : nt!PspSystemThreadStartup+0x5a
    fffff880`025f7c40 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KxStartSystemThread+0x16


    STACK_COMMAND: .bugcheck ; kb

    FOLLOWUP_IP:
    nvlddmkm!nvDumpConfig+1ff74c
    fffff880`0f9aa51c 48ff255dc9ecff jmp qword ptr [nvlddmkm!nvDumpConfig+0xcc0b0 (fffff880`0f876e80)]

    SYMBOL_NAME: nvlddmkm!nvDumpConfig+1ff74c

    FOLLOWUP_NAME: MachineOwner

    MODULE_NAME: nvlddmkm

    IMAGE_NAME: nvlddmkm.sys

    DEBUG_FLR_IMAGE_TIMESTAMP: 5414a236

    IMAGE_VERSION: 9.18.13.4411

    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
    ---------

    rax=fffffa800e056670 rbx=fffffa800e261010 rcx=0000000000000116
    rdx=fffffa800e261010 rsi=0000000000000004 rdi=fffffa800e270000
    rip=fffff80002c83e80 rsp=fffff880025f7a48 rbp=ffffffffc000009a
    r8=fffff8800f9aa51c r9=ffffffffc000009a r10=fffff80002c0d000
    r11=00000000000001b5 r12=fffffa8009eda410 r13=0000000000000001
    r14=0000000000000002 r15=0000000000000000
    iopl=0 nv up ei ng nz na pe nc
    cs=0010 ss=0018 ds=002b es=002b fs=0053 gs=002b efl=00000282
    nt!KeBugCheckEx:
    fffff800`02c83e80 48894c2408 mov qword ptr [rsp+8],rcx ss:0018:fffff880`025f7a50=0000000000000116
    Child-SP RetAddr : Args to Child : Call Site
    fffff880`025f7a48 fffff880`03b44134 : 00000000`00000116 fffffa80`0e261010 fffff880`0f9aa51c ffffffff`c000009a : nt!KeBugCheckEx
    fffff880`025f7a50 fffff880`03b17867 : fffff880`0f9aa51c fffffa80`09efa000 00000000`00000000 ffffffff`c000009a : dxgkrnl!TdrBugcheckOnTimeout+0xec
    fffff880`025f7a90 fffff880`03b43f43 : fffffa80`ffffd846 ffffffff`fffe7960 fffffa80`0e261010 00000000`00000000 : dxgkrnl!DXGADAPTER::Reset+0x2a3
    fffff880`025f7b40 fffff880`0fd9d03d : fffffa80`0cb6f6c0 00000000`00000080 00000000`00000000 fffffa80`09eda410 : dxgkrnl!TdrResetFromTimeout+0x23
    fffff880`025f7bc0 fffff800`02f200ca : 00000000`01b41e25 fffffa80`08ac7a00 fffffa80`066f21b0 fffffa80`08ac7a00 : dxgmms1!VidSchiWorkerThread+0x101
    fffff880`025f7c00 fffff800`02c74be6 : fffff880`02fd7180 fffffa80`08ac7a00 fffff880`02fe1fc0 00000000`00000000 : nt!PspSystemThreadStartup+0x5a
    fffff880`025f7c40 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KxStartSystemThread+0x16
    start end module name
    fffff800`00b97000 fffff800`00ba1000 kdcom kdcom.dll Sat Feb 05 11:52:49 2011 (4D4D8061)
    fffff800`02c0d000 fffff800`031f3000 nt ntkrnlmp.exe Thu Dec 11 23:25:12 2014 (548A6E28)
    fffff800`031f3000 fffff800`0323c000 hal hal.dll Sat Nov 20 08:00:25 2010 (4CE7C669)
    fffff880`00c39000 fffff880`00c88000 mcupdate_GenuineIntel mcupdate_GenuineIntel.dll Sat Nov 20 08:03:51 2010 (4CE7C737)
    fffff880`00c88000 fffff880`00c9c000 PSHED PSHED.dll Mon Jul 13 21:32:23 2009 (4A5BE027)
    fffff880`00c9c000 fffff880`00cfa000 CLFS CLFS.SYS Mon Jul 13 19:19:57 2009 (4A5BC11D)
    fffff880`00cfa000 fffff880`00dba000 CI CI.dll Sat Nov 20 08:12:36 2010 (4CE7C944)
    fffff880`00dba000 fffff880`00dc9000 mouclass mouclass.sys Mon Jul 13 19:19:50 2009 (4A5BC116)
    fffff880`00dc9000 fffff880`00de2000 HIDCLASS HIDCLASS.SYS Wed Jul 03 00:05:05 2013 (51D3A2F1)
    fffff880`00e00000 fffff880`00e09000 WMILIB WMILIB.SYS Mon Jul 13 19:19:51 2009 (4A5BC117)
    fffff880`00e09000 fffff880`00e13000 msisadrv msisadrv.sys Mon Jul 13 19:19:26 2009 (4A5BC0FE)
    fffff880`00e13000 fffff880`00e46000 pci pci.sys Sat Nov 20 04:19:11 2010 (4CE7928F)
    fffff880`00e46000 fffff880`00e53000 vdrvroot vdrvroot.sys Mon Jul 13 20:01:31 2009 (4A5BCADB)
    fffff880`00e53000 fffff880`00e68000 partmgr partmgr.sys Sat Mar 17 01:06:09 2012 (4F641BC1)
    fffff880`00e68000 fffff880`00e7d000 volmgr volmgr.sys Sat Nov 20 04:19:28 2010 (4CE792A0)
    fffff880`00e7d000 fffff880`00ea2000 VIDEOPRT VIDEOPRT.SYS Mon Jul 13 19:38:51 2009 (4A5BC58B)
    fffff880`00ea2000 fffff880`00ec4000 tdx tdx.sys Mon Nov 10 20:46:26 2014 (54616A72)
    fffff880`00ec4000 fffff880`00ed1000 TDI TDI.SYS Sat Nov 20 04:22:06 2010 (4CE7933E)
    fffff880`00ed6000 fffff880`00f98000 Wdf01000 Wdf01000.sys Fri Jun 21 23:13:05 2013 (51C51641)
    fffff880`00f98000 fffff880`00fa8000 WDFLDR WDFLDR.SYS Wed Jul 25 22:29:04 2012 (5010AB70)
    fffff880`00fa8000 fffff880`00fff000 ACPI ACPI.sys Sat Nov 20 04:19:16 2010 (4CE79294)
    fffff880`01000000 fffff880`01014000 fileinfo fileinfo.sys Mon Jul 13 19:34:25 2009 (4A5BC481)
    fffff880`01014000 fffff880`01056000 MpFilter MpFilter.sys Wed Jul 09 22:43:06 2014 (53BDFDBA)
    fffff880`01056000 fffff880`010b4000 msrpc msrpc.sys Sat Nov 20 04:21:56 2010 (4CE79334)
    fffff880`010b4000 fffff880`010bd000 rdpencdd rdpencdd.sys Mon Jul 13 20:16:34 2009 (4A5BCE62)
    fffff880`010bd000 fffff880`010c6000 rdprefmp rdprefmp.sys Mon Jul 13 20:16:35 2009 (4A5BCE63)
    fffff880`010c6000 fffff880`010d1000 Msfs Msfs.SYS Mon Jul 13 19:19:47 2009 (4A5BC113)
    fffff880`010d2000 fffff880`0112e000 volmgrx volmgrx.sys Sat Nov 20 04:20:43 2010 (4CE792EB)
    fffff880`0112e000 fffff880`01148000 mountmgr mountmgr.sys Sat Nov 20 04:19:21 2010 (4CE79299)
    fffff880`01148000 fffff880`01151000 atapi atapi.sys Mon Jul 13 19:19:47 2009 (4A5BC113)
    fffff880`01151000 fffff880`0117b000 ataport ataport.SYS Sun Aug 04 21:02:45 2013 (51FEF9B5)
    fffff880`0117b000 fffff880`01186000 msahci msahci.sys Sat Nov 20 05:33:58 2010 (4CE7A416)
    fffff880`01186000 fffff880`01196000 PCIIDEX PCIIDEX.SYS Mon Jul 13 19:19:48 2009 (4A5BC114)
    fffff880`01196000 fffff880`011a1000 amdxata amdxata.sys Fri Mar 19 12:18:18 2010 (4BA3A3CA)
    fffff880`011a1000 fffff880`011ed000 fltmgr fltmgr.sys Sat Nov 20 04:19:24 2010 (4CE7929C)
    fffff880`011ed000 fffff880`011fe000 Npfs Npfs.SYS Mon Jul 13 19:19:48 2009 (4A5BC114)
    fffff880`01200000 fffff880`01210000 watchdog watchdog.sys Mon Jul 13 19:37:35 2009 (4A5BC53F)
    fffff880`01212000 fffff880`013bb000 Ntfs Ntfs.sys Thu Jan 23 20:14:50 2014 (52E1BE8A)
    fffff880`013bb000 fffff880`013d6000 ksecdd ksecdd.sys Fri Apr 11 21:08:30 2014 (5348920E)
    fffff880`013d6000 fffff880`01400000 cdrom cdrom.sys Sat Nov 20 04:19:20 2010 (4CE79298)
    fffff880`01400000 fffff880`0143a000 fvevol fvevol.sys Wed Jan 23 22:11:24 2013 (5100A65C)
    fffff880`0143a000 fffff880`01450000 disk disk.sys Mon Jul 13 19:19:57 2009 (4A5BC11D)
    fffff880`01450000 fffff880`01480000 CLASSPNP CLASSPNP.SYS Sat Nov 20 04:19:23 2010 (4CE7929B)
    fffff880`01480000 fffff880`0149d000 usbccgp usbccgp.sys Tue Nov 26 20:41:15 2013 (52954DBB)
    fffff880`0149d000 fffff880`014ab000 hidusb hidusb.sys Sat Nov 20 05:43:49 2010 (4CE7A665)
    fffff880`014ac000 fffff880`014b5000 Null Null.SYS Mon Jul 13 19:19:37 2009 (4A5BC109)
    fffff880`014b5000 fffff880`014bc000 Beep Beep.SYS Mon Jul 13 20:00:13 2009 (4A5BCA8D)
    fffff880`014bc000 fffff880`014ca000 vga vga.sys Mon Jul 13 19:38:47 2009 (4A5BC587)
    fffff880`014ca000 fffff880`014d3000 RDPCDD RDPCDD.sys Mon Jul 13 20:16:34 2009 (4A5BCE62)
    fffff880`014d4000 fffff880`01546000 cng cng.sys Wed Aug 01 11:48:07 2012 (50194FB7)
    fffff880`01546000 fffff880`01557000 pcw pcw.sys Mon Jul 13 19:19:27 2009 (4A5BC0FF)
    fffff880`01557000 fffff880`01561000 Fs_Rec Fs_Rec.sys Wed Feb 29 22:41:06 2012 (4F4EEFD2)
    fffff880`01561000 fffff880`015ad000 volsnap volsnap.sys Thu Feb 24 22:38:18 2011 (4D67242A)
    fffff880`015ad000 fffff880`015e7000 rdyboost rdyboost.sys Sat Nov 20 04:43:10 2010 (4CE7982E)
    fffff880`015e7000 fffff880`015f9000 mup mup.sys Mon Jul 13 19:23:45 2009 (4A5BC201)
    fffff880`01600000 fffff880`01660000 NETIO NETIO.SYS Tue Nov 26 05:21:01 2013 (5294760D)
    fffff880`01660000 fffff880`0168c000 ksecpkg ksecpkg.sys Mon Oct 13 21:08:32 2014 (543C7790)
    fffff880`0168c000 fffff880`016d5000 fwpkclnt fwpkclnt.sys Fri Apr 04 21:23:21 2014 (533F5B09)
    fffff880`016e1000 fffff880`017d3000 ndis ndis.sys Wed Aug 22 11:11:46 2012 (5034F6B2)
    fffff880`017d3000 fffff880`017e3000 vmstorfl vmstorfl.sys Sat Nov 20 04:57:30 2010 (4CE79B8A)
    fffff880`017e3000 fffff880`017eb000 spldr spldr.sys Mon May 11 12:56:27 2009 (4A0858BB)
     
  7. 2015/02/02
    Evan Omo

    Evan Omo Computer Support Technician Staff

    Joined:
    2006/09/10
    Messages:
    7,899
    Likes Received:
    510
    Your blue screen is being caused by the nvlddmkm.sys file which is your Nvidia driver.

    Have you installed the latest display driver from Nvidia's website?
     
  8. 2015/02/02
    ese123

    ese123 Inactive Thread Starter

    Joined:
    2015/01/31
    Messages:
    6
    Likes Received:
    0
    Yep, uninstalled old drivers and installed the latest available. Again, I can still use the card with artifacts all over the screen, but it's not recognized by the system so I can't use it for DirectX, etc.
     
  9. 2015/02/02
    Evan Omo

    Evan Omo Computer Support Technician Staff

    Joined:
    2006/09/10
    Messages:
    7,899
    Likes Received:
    510
    Well if the latest driver doesn't resolve the problem with the card then most likely the video card has failed and you will need to get a replacement.

    You can try installing the video card into another computer and seeing if the same issue happens but more than likely the same problem will occur even in another system.
     
  10. 2015/02/26
    ese123

    ese123 Inactive Thread Starter

    Joined:
    2015/01/31
    Messages:
    6
    Likes Received:
    0
    card is fried :(
     
  11. 2015/02/27
    Evan Omo

    Evan Omo Computer Support Technician Staff

    Joined:
    2006/09/10
    Messages:
    7,899
    Likes Received:
    510
    Ok thanks for letting me know. Do you need assistance with getting a replacement card?
     
  12. 2015/03/03
    ese123

    ese123 Inactive Thread Starter

    Joined:
    2015/01/31
    Messages:
    6
    Likes Received:
    0
    Nope, plopped in a brand new nvidia card without even changing the drivers just to see what the issue was. Pretty unfortunate the card only lasted 3 years...kinda deters me from buying another hot/high end video card.
     

Share This Page

  1. This site uses cookies to help personalise content, tailor your experience and to keep you logged in if you register.
    By continuing to use this site, you are consenting to our use of cookies.