Windows 8 and 8.1 Forums


DPC_WATCHDOG_VIOLATION when adding second gpu?

  1. #1


    Posts : 3
    Windows 8

    DPC_WATCHDOG_VIOLATION when adding second gpu?


    Hey guys, this morning I installed W8 - and I am getting some very strange issues. I have wiped and re-installed 3 times already with the same thing happening.
    After ALOT of troubleshooting, I have isolated the problem, but have no idea why it keeps happening.

    I currently have a GTX Titan and decided to add another one. I figure since I had to do all the work of redoing my loop, I might as well do a fresh install of W8 (been looking to move over for a bit anyways). So here's the issue:

    If I run one single card - as in the second Titan is plugged into the motherboard but no power connections running to it - I am just fine, no problems at all. When I put the power connections on the second card and reboot the computer (and also add SLI bridge), I freeze immediately after signing into W8 (every single time) - followed by a BSOD a minute later saying DPC_WATCHDOG_VIOLATION. I can log in using safe mode with both GPU's on at which point I am able to uninstall and re install drivers. I have tried the latest official drivers, the latest beta drivers, and rolled back to the latest before this one and all have the same result (doing clean installs each time).

    Any help is much appreciated - or maybe if you guys could point me in the right direction or get your buddies to take a look at the issue!

    Thanks again!

      My System SpecsSystem Spec

  2. #2


    Posts : 5,139
    Win8.1Pro - Finally!!!


    I've been seeing more and more of this sort of problem with Win8.
    I tend to think that it's either a hardware problem that's only accessed by Win8
    Or it's a driver function that only Win8 uses - so the drivers are at fault.
    FWIW - the only solution that I've seen has been to replace the card.
    If you do decide to replace the card, purchase a new one from a store that allows returns (in case you want to return it).

    Next, I have never run 2 graphics cards at a time, and have only worked on one or two systems with this configuration. You may be better off seeking more expert help in the Graphics Cards forums: Graphic Cards - Windows 8 Forums

    That being said, here's the BSOD analysis:

    All the memory dumps point at your nVidia video drivers.
    This can be the drivers, the card(s) or the thingie that connects the cards.
    Another possibility is the second slot that the second card sits in.

    That being said, start with these diagnostics: Video TDR Timeout - 0x116 + 0x117 - Sysnative Forums

    Just FYI, when I see memory dumps with few 3rd party drivers showing (such as yours are) - I suspect compatibility or hardware issues.

    Analysis:
    The following is for informational purposes only.
    Code:
    **************************Sat Oct 12 11:35:38.526 2013 (UTC - 4:00)**************************
    Loading Dump File [C:\Users\John\SysnativeBSODApps\101213-7734-01.dmp]
    Windows 8 Kernel Version 9200 MP (4 procs) Free x64
    Built by: 9200.16628.amd64fre.win8_gdr.130531-1504
    System Uptime:0 days 0:02:55.155
    *** 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+19908d )
    BugCheck 133, {1, 1e00, 0, 0}
    BugCheck Info: DPC_WATCHDOG_VIOLATION (133)
    Arguments: 
    Arg1: 0000000000000001, The system cumulatively spent an extended period of time at
        DISPATCH_LEVEL or above. The offending component can usually be
        identified with a stack trace.
    Arg2: 0000000000001e00, The watchdog period.
    Arg3: 0000000000000000
    Arg4: 0000000000000000
    BUGCHECK_STR:  0x133
    DEFAULT_BUCKET_ID:  WIN8_DRIVER_FAULT
    PROCESS_NAME:  System
    FAILURE_BUCKET_ID: 0x133_ISR_nvlddmkm+19908d
    CPUID:        "Intel(R) Core(TM) i5-3570K CPU @ 3.40GHz"
    MaxSpeed:     3400
    CurrentSpeed: 3410
      BIOS Version                  1903
      BIOS Release Date             08/19/2013
      Manufacturer                  System manufacturer
      Product Name                  System Product Name
    ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии``
    **************************Sat Oct 12 11:32:20.382 2013 (UTC - 4:00)**************************
    Loading Dump File [C:\Users\John\SysnativeBSODApps\101213-7750-01.dmp]
    Windows 8 Kernel Version 9200 MP (4 procs) Free x64
    Built by: 9200.16628.amd64fre.win8_gdr.130531-1504
    System Uptime:0 days 0:03:13.011
    *** 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+19908d )
    BugCheck 133, {1, 1e00, 0, 0}
    BugCheck Info: DPC_WATCHDOG_VIOLATION (133)
    Arguments: 
    Arg1: 0000000000000001, The system cumulatively spent an extended period of time at
        DISPATCH_LEVEL or above. The offending component can usually be
        identified with a stack trace.
    Arg2: 0000000000001e00, The watchdog period.
    Arg3: 0000000000000000
    Arg4: 0000000000000000
    BUGCHECK_STR:  0x133
    DEFAULT_BUCKET_ID:  WIN8_DRIVER_FAULT
    PROCESS_NAME:  System
    FAILURE_BUCKET_ID: 0x133_ISR_nvlddmkm+19908d
    CPUID:        "Intel(R) Core(TM) i5-3570K CPU @ 3.40GHz"
    MaxSpeed:     3400
    CurrentSpeed: 3410
      BIOS Version                  1903
      BIOS Release Date             08/19/2013
      Manufacturer                  System manufacturer
      Product Name                  System Product Name
    ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии``
    **************************Sat Oct 12 11:28:43.780 2013 (UTC - 4:00)**************************
    Loading Dump File [C:\Users\John\SysnativeBSODApps\101213-8531-01.dmp]
    Windows 8 Kernel Version 9200 MP (4 procs) Free x64
    Built by: 9200.16628.amd64fre.win8_gdr.130531-1504
    System Uptime:0 days 0:02:40.409
    *** 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+19908d )
    BugCheck 133, {1, 1e00, 0, 0}
    BugCheck Info: DPC_WATCHDOG_VIOLATION (133)
    Arguments: 
    Arg1: 0000000000000001, The system cumulatively spent an extended period of time at
        DISPATCH_LEVEL or above. The offending component can usually be
        identified with a stack trace.
    Arg2: 0000000000001e00, The watchdog period.
    Arg3: 0000000000000000
    Arg4: 0000000000000000
    BUGCHECK_STR:  0x133
    DEFAULT_BUCKET_ID:  WIN8_DRIVER_FAULT
    PROCESS_NAME:  svchost.exe
    FAILURE_BUCKET_ID: 0x133_ISR_nvlddmkm+19908d
    CPUID:        "Intel(R) Core(TM) i5-3570K CPU @ 3.40GHz"
    MaxSpeed:     3400
    CurrentSpeed: 3410
      BIOS Version                  1903
      BIOS Release Date             08/19/2013
      Manufacturer                  System manufacturer
      Product Name                  System Product Name
    ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии``
    **************************Sat Oct 12 10:21:58.507 2013 (UTC - 4:00)**************************
    Loading Dump File [C:\Users\John\SysnativeBSODApps\101213-5343-01.dmp]
    Windows 8 Kernel Version 9200 MP (4 procs) Free x64
    Built by: 9200.16384.amd64fre.win8_rtm.120725-1247
    System Uptime:0 days 0:04:17.313
    *** 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+198d65 )
    BugCheck 133, {1, 780, 0, 0}
    BugCheck Info: DPC_WATCHDOG_VIOLATION (133)
    Arguments: 
    Arg1: 0000000000000001, The system cumulatively spent an extended period of time at
        DISPATCH_LEVEL or above. The offending component can usually be
        identified with a stack trace.
    Arg2: 0000000000000780, The watchdog period.
    Arg3: 0000000000000000
    Arg4: 0000000000000000
    BUGCHECK_STR:  0x133
    DEFAULT_BUCKET_ID:  WIN8_DRIVER_FAULT
    PROCESS_NAME:  System
    FAILURE_BUCKET_ID: 0x133_ISR_nvlddmkm+198d65
    CPUID:        "Intel(R) Core(TM) i5-3570K CPU @ 3.40GHz"
    MaxSpeed:     3400
    CurrentSpeed: 3410
      BIOS Version                  1903
      BIOS Release Date             08/19/2013
      Manufacturer                  System manufacturer
      Product Name                  System Product Name
    ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии``
    **************************Sat Oct 12 10:17:17.582 2013 (UTC - 4:00)**************************
    Loading Dump File [C:\Users\John\SysnativeBSODApps\101213-5359-01.dmp]
    Windows 8 Kernel Version 9200 MP (4 procs) Free x64
    Built by: 9200.16384.amd64fre.win8_rtm.120725-1247
    System Uptime:0 days 0:01:45.212
    *** 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+198d65 )
    BugCheck 133, {1, 780, 0, 0}
    BugCheck Info: DPC_WATCHDOG_VIOLATION (133)
    Arguments: 
    Arg1: 0000000000000001, The system cumulatively spent an extended period of time at
        DISPATCH_LEVEL or above. The offending component can usually be
        identified with a stack trace.
    Arg2: 0000000000000780, The watchdog period.
    Arg3: 0000000000000000
    Arg4: 0000000000000000
    BUGCHECK_STR:  0x133
    DEFAULT_BUCKET_ID:  WIN8_DRIVER_FAULT
    PROCESS_NAME:  System
    FAILURE_BUCKET_ID: 0x133_ISR_nvlddmkm+198d65
    CPUID:        "Intel(R) Core(TM) i5-3570K CPU @ 3.40GHz"
    MaxSpeed:     3400
    CurrentSpeed: 3410
      BIOS Version                  1903
      BIOS Release Date             08/19/2013
      Manufacturer                  System manufacturer
      Product Name                  System Product Name
    ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии``
    **************************Sat Oct 12 10:15:09.375 2013 (UTC - 4:00)**************************
    Loading Dump File [C:\Users\John\SysnativeBSODApps\101213-5390-01.dmp]
    Windows 8 Kernel Version 9200 MP (4 procs) Free x64
    Built by: 9200.16384.amd64fre.win8_rtm.120725-1247
    System Uptime:0 days 0:02:51.005
    *** 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+198d65 )
    BugCheck 133, {1, 780, 0, 0}
    BugCheck Info: DPC_WATCHDOG_VIOLATION (133)
    Arguments: 
    Arg1: 0000000000000001, The system cumulatively spent an extended period of time at
        DISPATCH_LEVEL or above. The offending component can usually be
        identified with a stack trace.
    Arg2: 0000000000000780, The watchdog period.
    Arg3: 0000000000000000
    Arg4: 0000000000000000
    BUGCHECK_STR:  0x133
    DEFAULT_BUCKET_ID:  WIN8_DRIVER_FAULT
    PROCESS_NAME:  System
    FAILURE_BUCKET_ID: 0x133_ISR_nvlddmkm+198d65
    CPUID:        "Intel(R) Core(TM) i5-3570K CPU @ 3.40GHz"
    MaxSpeed:     3400
    CurrentSpeed: 3410
      BIOS Version                  1903
      BIOS Release Date             08/19/2013
      Manufacturer                  System manufacturer
      Product Name                  System Product Name
    ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии``
    **************************Sat Oct 12 10:04:13.828 2013 (UTC - 4:00)**************************
    Loading Dump File [C:\Users\John\SysnativeBSODApps\101213-4640-01.dmp]
    Windows 8 Kernel Version 9200 MP (4 procs) Free x64
    Built by: 9200.16384.amd64fre.win8_rtm.120725-1247
    System Uptime:0 days 0:01:32.465
    *** 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+198d65 )
    BugCheck 133, {1, 780, 0, 0}
    BugCheck Info: DPC_WATCHDOG_VIOLATION (133)
    Arguments: 
    Arg1: 0000000000000001, The system cumulatively spent an extended period of time at
        DISPATCH_LEVEL or above. The offending component can usually be
        identified with a stack trace.
    Arg2: 0000000000000780, The watchdog period.
    Arg3: 0000000000000000
    Arg4: 0000000000000000
    BUGCHECK_STR:  0x133
    DEFAULT_BUCKET_ID:  WIN8_DRIVER_FAULT
    PROCESS_NAME:  System
    FAILURE_BUCKET_ID: 0x133_ISR_nvlddmkm+198d65
    CPUID:        "Intel(R) Core(TM) i5-3570K CPU @ 3.40GHz"
    MaxSpeed:     3400
    CurrentSpeed: 3410
      BIOS Version                  1903
      BIOS Release Date             08/19/2013
      Manufacturer                  System manufacturer
      Product Name                  System Product Name
    ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии``
    **************************Sat Oct 12 10:02:18.557 2013 (UTC - 4:00)**************************
    Loading Dump File [C:\Users\John\SysnativeBSODApps\101213-5484-01.dmp]
    Windows 8 Kernel Version 9200 MP (4 procs) Free x64
    Built by: 9200.16384.amd64fre.win8_rtm.120725-1247
    System Uptime:0 days 0:02:00.187
    *** 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+198d65 )
    BugCheck 133, {1, 780, 0, 0}
    BugCheck Info: DPC_WATCHDOG_VIOLATION (133)
    Arguments: 
    Arg1: 0000000000000001, The system cumulatively spent an extended period of time at
        DISPATCH_LEVEL or above. The offending component can usually be
        identified with a stack trace.
    Arg2: 0000000000000780, The watchdog period.
    Arg3: 0000000000000000
    Arg4: 0000000000000000
    BUGCHECK_STR:  0x133
    DEFAULT_BUCKET_ID:  WIN8_DRIVER_FAULT
    PROCESS_NAME:  System
    FAILURE_BUCKET_ID: 0x133_ISR_nvlddmkm+198d65
    CPUID:        "Intel(R) Core(TM) i5-3570K CPU @ 3.40GHz"
    MaxSpeed:     3400
    CurrentSpeed: 3410
      BIOS Version                  1903
      BIOS Release Date             08/19/2013
      Manufacturer                  System manufacturer
      Product Name                  System Product Name
    ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии``
    **************************Sat Oct 12 09:49:53.534 2013 (UTC - 4:00)**************************
    Loading Dump File [C:\Users\John\SysnativeBSODApps\101213-6328-01.dmp]
    Windows 8 Kernel Version 9200 MP (4 procs) Free x64
    Built by: 9200.16384.amd64fre.win8_rtm.120725-1247
    System Uptime:0 days 0:01:43.163
    *** 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+198d65 )
    BugCheck 133, {1, 780, 0, 0}
    BugCheck Info: DPC_WATCHDOG_VIOLATION (133)
    Arguments: 
    Arg1: 0000000000000001, The system cumulatively spent an extended period of time at
        DISPATCH_LEVEL or above. The offending component can usually be
        identified with a stack trace.
    Arg2: 0000000000000780, The watchdog period.
    Arg3: 0000000000000000
    Arg4: 0000000000000000
    BUGCHECK_STR:  0x133
    DEFAULT_BUCKET_ID:  WIN8_DRIVER_FAULT
    PROCESS_NAME:  System
    FAILURE_BUCKET_ID: 0x133_ISR_nvlddmkm+198d65
    CPUID:        "Intel(R) Core(TM) i5-3570K CPU @ 3.40GHz"
    MaxSpeed:     3400
    CurrentSpeed: 3410
      BIOS Version                  1903
      BIOS Release Date             08/19/2013
      Manufacturer                  System manufacturer
      Product Name                  System Product Name
    ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии``
    **************************Sat Oct 12 09:47:43.461 2013 (UTC - 4:00)**************************
    Loading Dump File [C:\Users\John\SysnativeBSODApps\101213-5500-01.dmp]
    Windows 8 Kernel Version 9200 MP (4 procs) Free x64
    Built by: 9200.16384.amd64fre.win8_rtm.120725-1247
    System Uptime:0 days 0:01:32.098
    *** 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+198d65 )
    BugCheck 133, {1, 780, 0, 0}
    BugCheck Info: DPC_WATCHDOG_VIOLATION (133)
    Arguments: 
    Arg1: 0000000000000001, The system cumulatively spent an extended period of time at
        DISPATCH_LEVEL or above. The offending component can usually be
        identified with a stack trace.
    Arg2: 0000000000000780, The watchdog period.
    Arg3: 0000000000000000
    Arg4: 0000000000000000
    BUGCHECK_STR:  0x133
    DEFAULT_BUCKET_ID:  WIN8_DRIVER_FAULT
    PROCESS_NAME:  System
    FAILURE_BUCKET_ID: 0x133_ISR_nvlddmkm+198d65
    CPUID:        "Intel(R) Core(TM) i5-3570K CPU @ 3.40GHz"
    MaxSpeed:     3400
    CurrentSpeed: 3410
      BIOS Version                  1903
      BIOS Release Date             08/19/2013
      Manufacturer                  System manufacturer
      Product Name                  System Product Name
    ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии``
    **************************Sat Oct 12 09:39:17.381 2013 (UTC - 4:00)**************************
    Loading Dump File [C:\Users\John\SysnativeBSODApps\101213-4187-01.dmp]
    Windows 8 Kernel Version 9200 MP (4 procs) Free x64
    Built by: 9200.16384.amd64fre.win8_rtm.120725-1247
    System Uptime:0 days 0:01:22.011
    *** 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+198d65 )
    BugCheck 133, {1, 780, 0, 0}
    BugCheck Info: DPC_WATCHDOG_VIOLATION (133)
    Arguments: 
    Arg1: 0000000000000001, The system cumulatively spent an extended period of time at
        DISPATCH_LEVEL or above. The offending component can usually be
        identified with a stack trace.
    Arg2: 0000000000000780, The watchdog period.
    Arg3: 0000000000000000
    Arg4: 0000000000000000
    BUGCHECK_STR:  0x133
    DEFAULT_BUCKET_ID:  WIN8_DRIVER_FAULT
    PROCESS_NAME:  System
    FAILURE_BUCKET_ID: 0x133_ISR_nvlddmkm+198d65
    CPUID:        "Intel(R) Core(TM) i5-3570K CPU @ 3.40GHz"
    MaxSpeed:     3400
    CurrentSpeed: 3410
      BIOS Version                  1903
      BIOS Release Date             08/19/2013
      Manufacturer                  System manufacturer
      Product Name                  System Product Name
    ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии``
    **************************Sat Oct 12 09:36:57.830 2013 (UTC - 4:00)**************************
    Loading Dump File [C:\Users\John\SysnativeBSODApps\101213-5468-01.dmp]
    Windows 8 Kernel Version 9200 MP (4 procs) Free x64
    Built by: 9200.16384.amd64fre.win8_rtm.120725-1247
    System Uptime:0 days 0:01:22.460
    *** 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+198d65 )
    BugCheck 133, {1, 780, 0, 0}
    BugCheck Info: DPC_WATCHDOG_VIOLATION (133)
    Arguments: 
    Arg1: 0000000000000001, The system cumulatively spent an extended period of time at
        DISPATCH_LEVEL or above. The offending component can usually be
        identified with a stack trace.
    Arg2: 0000000000000780, The watchdog period.
    Arg3: 0000000000000000
    Arg4: 0000000000000000
    BUGCHECK_STR:  0x133
    DEFAULT_BUCKET_ID:  WIN8_DRIVER_FAULT
    PROCESS_NAME:  System
    FAILURE_BUCKET_ID: 0x133_ISR_nvlddmkm+198d65
    CPUID:        "Intel(R) Core(TM) i5-3570K CPU @ 3.40GHz"
    MaxSpeed:     3400
    CurrentSpeed: 3410
      BIOS Version                  1903
      BIOS Release Date             08/19/2013
      Manufacturer                  System manufacturer
      Product Name                  System Product Name
    ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии``
    **************************Sat Oct 12 09:35:12.608 2013 (UTC - 4:00)**************************
    Loading Dump File [C:\Users\John\SysnativeBSODApps\101213-5421-01.dmp]
    Windows 8 Kernel Version 9200 MP (4 procs) Free x64
    Built by: 9200.16384.amd64fre.win8_rtm.120725-1247
    System Uptime:0 days 0:03:30.237
    *** 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+198d65 )
    BugCheck 133, {1, 780, 0, 0}
    BugCheck Info: DPC_WATCHDOG_VIOLATION (133)
    Arguments: 
    Arg1: 0000000000000001, The system cumulatively spent an extended period of time at
        DISPATCH_LEVEL or above. The offending component can usually be
        identified with a stack trace.
    Arg2: 0000000000000780, The watchdog period.
    Arg3: 0000000000000000
    Arg4: 0000000000000000
    BUGCHECK_STR:  0x133
    DEFAULT_BUCKET_ID:  WIN8_DRIVER_FAULT
    PROCESS_NAME:  System
    FAILURE_BUCKET_ID: 0x133_ISR_nvlddmkm+198d65
    CPUID:        "Intel(R) Core(TM) i5-3570K CPU @ 3.40GHz"
    MaxSpeed:     3400
    CurrentSpeed: 3410
      BIOS Version                  1903
      BIOS Release Date             08/19/2013
      Manufacturer                  System manufacturer
      Product Name                  System Product Name
    ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии``
    **************************Sat Oct 12 09:31:18.425 2013 (UTC - 4:00)**************************
    Loading Dump File [C:\Users\John\SysnativeBSODApps\101213-5828-01.dmp]
    Windows 8 Kernel Version 9200 MP (4 procs) Free x64
    Built by: 9200.16384.amd64fre.win8_rtm.120725-1247
    System Uptime:0 days 0:07:24.072
    *** 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+198d65 )
    BugCheck 133, {1, 780, 0, 0}
    BugCheck Info: DPC_WATCHDOG_VIOLATION (133)
    Arguments: 
    Arg1: 0000000000000001, The system cumulatively spent an extended period of time at
        DISPATCH_LEVEL or above. The offending component can usually be
        identified with a stack trace.
    Arg2: 0000000000000780, The watchdog period.
    Arg3: 0000000000000000
    Arg4: 0000000000000000
    BUGCHECK_STR:  0x133
    DEFAULT_BUCKET_ID:  WIN8_DRIVER_FAULT
    PROCESS_NAME:  System
    FAILURE_BUCKET_ID: 0x133_ISR_nvlddmkm+198d65
    CPUID:        "Intel(R) Core(TM) i5-3570K CPU @ 3.40GHz"
    MaxSpeed:     3400
    CurrentSpeed: 3410
      BIOS Version                  1903
      BIOS Release Date             08/19/2013
      Manufacturer                  System manufacturer
      Product Name                  System Product Name
    ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии``
    
    3rd Party Drivers:
    The following is for information purposes only.
    Any drivers in red should be updated or removed from your system. And should have been discussed in the body of my post.
    Code:
    **************************Sat Oct 12 11:35:38.526 2013 (UTC - 4:00)**************************
    HECIx64.sys                 Mon Jul  2 18:14:58 2012 (4FF21D62)
    RTKVHD64.sys                Tue Aug  7 06:49:39 2012 (5020F2C3)
    e1c63x64.sys                Fri Aug 10 18:40:50 2012 (50258DF2)
    intelppm.sys                Mon Nov  5 22:55:02 2012 (50988A16)
    dump_storahci.sys           Fri Mar  1 21:15:44 2013 (513160D0)
    nvvad64v.sys                Tue Aug 20 07:29:10 2013 (52135306)
    nvlddmkm.sys                Fri Sep 27 01:45:06 2013 (52451B62)
    ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии``
    **************************Sat Oct 12 10:21:58.507 2013 (UTC - 4:00)**************************
    e1i63x64.sys                Wed Feb 29 22:25:14 2012 (4F4EEC1A)
    intelppm.sys                Wed Jul 25 22:26:48 2012 (5010AAE8)
    dump_storahci.sys           Wed Jul 25 22:30:35 2012 (5010ABCB)
    nvhda64v.sys                Sun Jun 16 08:38:07 2013 (51BDB1AF)
    nvlddmkm.sys                Thu Sep 12 01:16:00 2013 (52314E10)
    ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии``
    **************************Sat Oct 12 09:36:57.830 2013 (UTC - 4:00)**************************
    hiber_storahci.sys          Wed Jul 25 22:30:35 2012 (5010ABCB)
    
    http://www.carrona.org/drivers/driver.php?id=HECIx64.sys
    http://www.carrona.org/drivers/driver.php?id=RTKVHD64.sys
    http://www.carrona.org/drivers/driver.php?id=e1c63x64.sys
    http://www.carrona.org/drivers/driver.php?id=intelppm.sys
    http://www.carrona.org/drivers/driver.php?id=dump_storahci.sys
    http://www.carrona.org/drivers/driver.php?id=nvvad64v.sys
    http://www.carrona.org/drivers/driver.php?id=nvlddmkm.sys
    http://www.carrona.org/drivers/driver.php?id=e1i63x64.sys
    http://www.carrona.org/drivers/driver.php?id=intelppm.sys
    http://www.carrona.org/drivers/driver.php?id=dump_storahci.sys
    http://www.carrona.org/drivers/driver.php?id=nvhda64v.sys
    http://www.carrona.org/drivers/driver.php?id=nvlddmkm.sys
    http://www.carrona.org/drivers/driver.php?id=hiber_storahci.sys
      My System SpecsSystem Spec

  3. #3


    Posts : 3
    Windows 8


    Usasma,

    Thank you so much for your help. This definitely helped me pick my next course of action. I tested the second card separately and it worked fine - so it looks like it was a motherboard issue. The second PCI-E slot looks to be bad, but this helped me figure out that this wasn't a software issue. Thanks again for all your help!
      My System SpecsSystem Spec

DPC_WATCHDOG_VIOLATION when adding second gpu?
Related Threads
Solved Adding RAM to Windows 8.1 PC 64 bit. in Performance & Maintenance
Hi, Hopefully someone can supply the required information to allow me to increase RAM from 4Gb to 8Gb.. My 64 bit PC has 4Gb of RAM made up from 2 of the 4 slots containing Samsung Size 2048 MBytes Max Bandwith PC3-10700 (667 MHz). I would like to increase RAM to 8Gb and would like to know if...
Adding 'old' HDD to New pc in Drivers & Hardware
I was going to add my 'old' 2 TB SATA HDD to my new pc as a secondary drive to accompany the 1 TB SSHD drive, but first I inserted it into a dock to check that everything that could be moved, was. It said that the HDD needed formatting as the format was wrong. It is NTFS. Is it saying wrong drive...
Solved Adding RAM ? in Performance & Maintenance
I have 4 GBs ram with one slot empty. You reckon it's worth the money to get another 4 GB stick ? I can get one for $45 US.
Adding tiles in General Support
is there anyway to add tiles on the desk top that would be attached to favorites I have saved:(
Solved adding to a photo in Software and Apps
ok, in my photos is a pic of a fitness chart. is there a place in here where I can transfer the thing to add words. like: incline press decline press preacher curl tri-kick backs and so on. i hate to write this by hand. anyway, any info would be of great help
I asked for help in this in the BSOD subforum and was directed here - thanks for any help and advice! --------- Hey guys, this morning I installed Windows 8 - and I am getting some very strange issues. I have wiped and re-installed 3 times already with the same thing happening. After ALOT...
Adding RAM ? in Performance & Maintenance
I received a HP 20-b014 all in one PC as a gift... It's a nice looking, space saving machine BUT it only has a 1.4 ghz processor. It also has 4gbs RAM, running Windows 8 (64 bit). My question is, will adding more ram help as far as watching videos online? Not concerned with gaming at all. Just...
Eight Forums Android App Eight Forums IOS App Follow us on Facebook