Windows 8 and 8.1 Forums

Dpc_watchdog_violation

  1. #1

    Dpc_watchdog_violation


    Hello.

    With increasing regularity, I've been receiving DPC_WATCHDOG_VIOLATION BSODs, crashing my computer. Usually, this tends to happen when a video of some sort is playing, but it also happens at completely unpredictable times, like immediately upon reboot or with no warning at all while sitting idle.
    If someone could assist me in remedying this issue, I'd be very thankful.

    Also, I'll also occasionally get an IRQL_NOT_LESS_OR_EQUAL BSOD. However, it happens much less regularly than the watchdog violation one, and I'm pretty sure all of the recent watchdog violation BSs over the past few days have flushed out any record of an IRQL_NOT_LESS_OR_EQUAL one. Regardless, if there's something in all of these records that hints at what might be the cause of that error, too, I would, again, be very appreciative.

    I thank all of you who do BSOD analysis.

      My System SpecsSystem Spec

  2. #2


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


    Your BIOS dates from 2010. Please check at the manufacturer's website to see if there are any BIOS updates available for your system. Also check the readme file to see if they apply to the problems that you are having. Please be advised that flashing the BIOS is a very unforgiving process - and one mistake can physically damage your motherboard.

    Only 2╜% free space on your C: drive. Windows needs about 15% free space to function properly. Please free up 15% on your hard drive ASAP.

    This appears to be an upgrade install. You may want to consider a clean install in order to keep from bringing all the old problems into your new OS.

    There's a lot of video drivers in the stack text - makes me suspect your video card or it's drivers. Please do this: ATI video cards - DRIVER ONLY installation procedure

    Please update these older drivers. Links are included to assist in looking up the source of the drivers. If unable to find an update, please remove (un-install) the program responsible for that driver. DO NOT manually delete/rename the driver as it may make the system unbootable! :

    SASDIFSV64.SYS Mon Feb 8 19:11:52 2010 (4B70A848)
    SUPERAntiSpyware
    http://www.carrona.org/drivers/driver.php?id=SASDIFSV64.SYS

    SASKUTIL64.SYS Tue Feb 9 17:27:34 2010 (4B71E156)
    SUPERAntiSpyware
    http://www.carrona.org/drivers/driver.php?id=SASKUTIL64.SYS

    SAlpham64.sys Fri Sep 16 15:00:29 2011 (4E739CCD)
    SteelSeries Engine HID Driver
    http://www.carrona.org/drivers/driver.php?id=SAlpham64.sys

    Rt630x64.sys Wed Oct 19 08:12:55 2011 (4E9EBEC7)
    Realtek PCI/PCIe Adapters
    http://www.carrona.org/drivers/driver.php?id=Rt630x64.sys

    Please post back if this doesn't fix it - there's a more difficult step to figure out the cause, but it's gonna take a bit of work on both our parts (here's the link to the "how-to" of it: Determining the source of Bug Check 0x133 (DPC_WATCHDOG_VIOLATION) errors on Windows Server 2012 - Ntdebugging Blog - Site Home - MSDN Blogs )

    Analysis:
    The following is for informational purposes only.
    Code:
    **************************Tue Jan 15 14:17:28.843 2013 (UTC - 5:00)**************************
    Loading Dump File [C:\Users\John\_jcgriff2_\dbug\__Kernel__\011513-21559-01.dmp]
    Windows 8 Kernel Version 9200 MP (2 procs) Free x64
    Built by: 9200.16461.amd64fre.win8_gdr.121119-1606
    System Uptime:0 days 0:38:43.635
    Probably caused by :ntkrnlmp.exe ( nt! ?? ::FNODOBFM::`string'+13ca8 )
    BugCheck 133, {1, 784, 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: 0000000000000784, The watchdog period.
    Arg3: 0000000000000000
    Arg4: 0000000000000000
    BUGCHECK_STR:  0x133
    DEFAULT_BUCKET_ID:  WIN8_DRIVER_FAULT
    PROCESS_NAME: System
    FAILURE_BUCKET_ID: 0x133_ISR_nt!_??_::FNODOBFM::_string_
      BIOS Version                  V8.7
      BIOS Release Date             09/04/2010
      Manufacturer                  MICRO-STAR INTERNATIONAL CO.,LTD
      Product Name                  MS-7388
    ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии``
    **************************Tue Jan 15 11:40:09.328 2013 (UTC - 5:00)**************************
    Loading Dump File [C:\Users\John\_jcgriff2_\dbug\__Kernel__\011513-22978-01.dmp]
    Windows 8 Kernel Version 9200 MP (2 procs) Free x64
    Built by: 9200.16461.amd64fre.win8_gdr.121119-1606
    System Uptime:0 days 0:00:49.120
    *** WARNING: Unable to verify timestamp for atikmdag.sys
    *** ERROR: Module load completed but symbols could not be loaded for atikmdag.sys
    Probably caused by :atikmdag.sys ( atikmdag+37e68 )
    BugCheck 133, {1, 784, 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: 0000000000000784, The watchdog period.
    Arg3: 0000000000000000
    Arg4: 0000000000000000
    BUGCHECK_STR:  0x133
    DEFAULT_BUCKET_ID:  WIN8_DRIVER_FAULT
    PROCESS_NAME: csrss.exe
    FAILURE_BUCKET_ID: 0x133_ISR_atikmdag+37e68
      BIOS Version                  V8.7
      BIOS Release Date             09/04/2010
      Manufacturer                  MICRO-STAR INTERNATIONAL CO.,LTD
      Product Name                  MS-7388
    ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии``
    **************************Tue Jan 15 11:32:18.538 2013 (UTC - 5:00)**************************
    Loading Dump File [C:\Users\John\_jcgriff2_\dbug\__Kernel__\011513-22885-01.dmp]
    Windows 8 Kernel Version 9200 MP (2 procs) Free x64
    Built by: 9200.16461.amd64fre.win8_gdr.121119-1606
    System Uptime:0 days 0:14:39.331
    Probably caused by :ntkrnlmp.exe ( nt! ?? ::FNODOBFM::`string'+13ca8 )
    BugCheck 133, {1, 784, 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: 0000000000000784, The watchdog period.
    Arg3: 0000000000000000
    Arg4: 0000000000000000
    BUGCHECK_STR:  0x133
    DEFAULT_BUCKET_ID:  WIN8_DRIVER_FAULT
    PROCESS_NAME: WmiPrvSE.exe
    FAILURE_BUCKET_ID: 0x133_ISR_nt!_??_::FNODOBFM::_string_
      BIOS Version                  V8.7
      BIOS Release Date             09/04/2010
      Manufacturer                  MICRO-STAR INTERNATIONAL CO.,LTD
      Product Name                  MS-7388
    ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии``
    **************************Tue Jan 15 11:17:08.658 2013 (UTC - 5:00)**************************
    Loading Dump File [C:\Users\John\_jcgriff2_\dbug\__Kernel__\011513-30810-01.dmp]
    Windows 8 Kernel Version 9200 MP (2 procs) Free x64
    Built by: 9200.16461.amd64fre.win8_gdr.121119-1606
    System Uptime:0 days 0:03:17.450
    Probably caused by :win32k.sys ( win32k!AllocateObject+14f )
    BugCheck 133, {1, 784, 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: 0000000000000784, The watchdog period.
    Arg3: 0000000000000000
    Arg4: 0000000000000000
    BUGCHECK_STR:  0x133
    DEFAULT_BUCKET_ID:  WIN8_DRIVER_FAULT
    PROCESS_NAME: explorer.exe
    FAILURE_BUCKET_ID: 0x133_ISR_win32k!AllocateObject
      BIOS Version                  V8.7
      BIOS Release Date             09/04/2010
      Manufacturer                  MICRO-STAR INTERNATIONAL CO.,LTD
      Product Name                  MS-7388
    ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии``
    **************************Tue Jan 15 11:13:20.494 2013 (UTC - 5:00)**************************
    Loading Dump File [C:\Users\John\_jcgriff2_\dbug\__Kernel__\011513-25958-01.dmp]
    Windows 8 Kernel Version 9200 MP (2 procs) Free x64
    Built by: 9200.16461.amd64fre.win8_gdr.121119-1606
    System Uptime:0 days 0:09:44.286
    Probably caused by :ntkrnlmp.exe ( nt! ?? ::FNODOBFM::`string'+13ca8 )
    BugCheck 133, {1, 784, 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: 0000000000000784, The watchdog period.
    Arg3: 0000000000000000
    Arg4: 0000000000000000
    BUGCHECK_STR:  0x133
    DEFAULT_BUCKET_ID:  WIN8_DRIVER_FAULT
    PROCESS_NAME: System
    FAILURE_BUCKET_ID: 0x133_ISR_nt!_??_::FNODOBFM::_string_
      BIOS Version                  V8.7
      BIOS Release Date             09/04/2010
      Manufacturer                  MICRO-STAR INTERNATIONAL CO.,LTD
      Product Name                  MS-7388
    ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии``
    **************************Tue Jan 15 11:03:04.602 2013 (UTC - 5:00)**************************
    Loading Dump File [C:\Users\John\_jcgriff2_\dbug\__Kernel__\011513-28860-01.dmp]
    Windows 8 Kernel Version 9200 MP (2 procs) Free x64
    Built by: 9200.16461.amd64fre.win8_gdr.121119-1606
    System Uptime:0 days 7:45:39.420
    Probably caused by :ntkrnlmp.exe ( nt! ?? ::FNODOBFM::`string'+13ca8 )
    BugCheck 133, {1, 784, 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: 0000000000000784, The watchdog period.
    Arg3: 0000000000000000
    Arg4: 0000000000000000
    BUGCHECK_STR:  0x133
    DEFAULT_BUCKET_ID:  WIN8_DRIVER_FAULT
    PROCESS_NAME: System
    FAILURE_BUCKET_ID: 0x133_ISR_nt!_??_::FNODOBFM::_string_
      BIOS Version                  V8.7
      BIOS Release Date             09/04/2010
      Manufacturer                  MICRO-STAR INTERNATIONAL CO.,LTD
      Product Name                  MS-7388
    ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии``
    **************************Tue Jan 15 03:16:54.640 2013 (UTC - 5:00)**************************
    Loading Dump File [C:\Users\John\_jcgriff2_\dbug\__Kernel__\011513-22807-01.dmp]
    Windows 8 Kernel Version 9200 MP (2 procs) Free x64
    Built by: 9200.16461.amd64fre.win8_gdr.121119-1606
    System Uptime:0 days 0:00:49.432
    *** WARNING: Unable to verify timestamp for atikmdag.sys
    *** ERROR: Module load completed but symbols could not be loaded for atikmdag.sys
    Probably caused by :atikmdag.sys ( atikmdag+37e68 )
    BugCheck 133, {1, 784, 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: 0000000000000784, The watchdog period.
    Arg3: 0000000000000000
    Arg4: 0000000000000000
    BUGCHECK_STR:  0x133
    DEFAULT_BUCKET_ID:  WIN8_DRIVER_FAULT
    PROCESS_NAME: csrss.exe
    FAILURE_BUCKET_ID: 0x133_ISR_atikmdag+37e68
      BIOS Version                  V8.7
      BIOS Release Date             09/04/2010
      Manufacturer                  MICRO-STAR INTERNATIONAL CO.,LTD
      Product Name                  MS-7388
    ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии``
    **************************Mon Jan 14 23:10:56.339 2013 (UTC - 5:00)**************************
    Loading Dump File [C:\Users\John\_jcgriff2_\dbug\__Kernel__\011513-20373-01.dmp]
    Windows 8 Kernel Version 9200 MP (2 procs) Free x64
    Built by: 9200.16461.amd64fre.win8_gdr.121119-1606
    System Uptime:0 days 0:34:11.085
    Probably caused by :ntkrnlmp.exe ( nt! ?? ::FNODOBFM::`string'+13ca8 )
    BugCheck 133, {1, 784, 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: 0000000000000784, The watchdog period.
    Arg3: 0000000000000000
    Arg4: 0000000000000000
    BUGCHECK_STR:  0x133
    DEFAULT_BUCKET_ID:  WIN8_DRIVER_FAULT
    PROCESS_NAME: System
    FAILURE_BUCKET_ID: 0x133_ISR_nt!_??_::FNODOBFM::_string_
      BIOS Version                  V8.7
      BIOS Release Date             09/04/2010
      Manufacturer                  MICRO-STAR INTERNATIONAL CO.,LTD
      Product Name                  MS-7388
    ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии``
    **************************Mon Jan 14 22:36:13.075 2013 (UTC - 5:00)**************************
    Loading Dump File [C:\Users\John\_jcgriff2_\dbug\__Kernel__\011413-33852-01.dmp]
    Windows 8 Kernel Version 9200 MP (2 procs) Free x64
    Built by: 9200.16461.amd64fre.win8_gdr.121119-1606
    System Uptime:0 days 0:00:40.868
    Probably caused by :ntkrnlmp.exe ( nt! ?? ::FNODOBFM::`string'+13ca8 )
    BugCheck 133, {1, 784, 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: 0000000000000784, The watchdog period.
    Arg3: 0000000000000000
    Arg4: 0000000000000000
    BUGCHECK_STR:  0x133
    DEFAULT_BUCKET_ID:  WIN8_DRIVER_FAULT
    PROCESS_NAME: System
    FAILURE_BUCKET_ID: 0x133_ISR_nt!_??_::FNODOBFM::_string_
      BIOS Version                  V8.7
      BIOS Release Date             09/04/2010
      Manufacturer                  MICRO-STAR INTERNATIONAL CO.,LTD
      Product Name                  MS-7388
    ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии``
    **************************Mon Jan 14 21:39:19.305 2013 (UTC - 5:00)**************************
    Loading Dump File [C:\Users\John\_jcgriff2_\dbug\__Kernel__\011413-19312-01.dmp]
    Windows 8 Kernel Version 9200 MP (2 procs) Free x64
    Built by: 9200.16461.amd64fre.win8_gdr.121119-1606
    System Uptime:0 days 0:10:54.097
    Probably caused by :ntkrnlmp.exe ( nt! ?? ::FNODOBFM::`string'+13ca8 )
    BugCheck 133, {1, 784, 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: 0000000000000784, The watchdog period.
    Arg3: 0000000000000000
    Arg4: 0000000000000000
    BUGCHECK_STR:  0x133
    DEFAULT_BUCKET_ID:  WIN8_DRIVER_FAULT
    PROCESS_NAME: System
    FAILURE_BUCKET_ID: 0x133_ISR_nt!_??_::FNODOBFM::_string_
      BIOS Version                  V8.7
      BIOS Release Date             09/04/2010
      Manufacturer                  MICRO-STAR INTERNATIONAL CO.,LTD
      Product Name                  MS-7388
    ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии``
    **************************Mon Jan 14 21:03:35.530 2013 (UTC - 5:00)**************************
    Loading Dump File [C:\Users\John\_jcgriff2_\dbug\__Kernel__\011413-31481-01.dmp]
    Windows 8 Kernel Version 9200 MP (2 procs) Free x64
    Built by: 9200.16461.amd64fre.win8_gdr.121119-1606
    System Uptime:0 days 1:05:12.326
    Probably caused by :ntkrnlmp.exe ( nt! ?? ::FNODOBFM::`string'+13ca8 )
    BugCheck 133, {1, 784, 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: 0000000000000784, The watchdog period.
    Arg3: 0000000000000000
    Arg4: 0000000000000000
    BUGCHECK_STR:  0x133
    DEFAULT_BUCKET_ID:  WIN8_DRIVER_FAULT
    PROCESS_NAME: System
    FAILURE_BUCKET_ID: 0x133_ISR_nt!_??_::FNODOBFM::_string_
      BIOS Version                  V8.7
      BIOS Release Date             09/04/2010
      Manufacturer                  MICRO-STAR INTERNATIONAL CO.,LTD
      Product Name                  MS-7388
    ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии``
    **************************Mon Jan 14 19:57:52.790 2013 (UTC - 5:00)**************************
    Loading Dump File [C:\Users\John\_jcgriff2_\dbug\__Kernel__\011413-32744-01.dmp]
    Windows 8 Kernel Version 9200 MP (2 procs) Free x64
    Built by: 9200.16461.amd64fre.win8_gdr.121119-1606
    System Uptime:0 days 0:39:54.592
    Probably caused by :ntkrnlmp.exe ( nt! ?? ::FNODOBFM::`string'+13ca8 )
    BugCheck 133, {1, 784, 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: 0000000000000784, The watchdog period.
    Arg3: 0000000000000000
    Arg4: 0000000000000000
    BUGCHECK_STR:  0x133
    DEFAULT_BUCKET_ID:  WIN8_DRIVER_FAULT
    PROCESS_NAME: System
    FAILURE_BUCKET_ID: 0x133_ISR_nt!_??_::FNODOBFM::_string_
      BIOS Version                  V8.7
      BIOS Release Date             09/04/2010
      Manufacturer                  MICRO-STAR INTERNATIONAL CO.,LTD
      Product Name                  MS-7388
    ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии``
    **************************Mon Jan 14 19:17:27.857 2013 (UTC - 5:00)**************************
    Loading Dump File [C:\Users\John\_jcgriff2_\dbug\__Kernel__\011413-36129-01.dmp]
    Windows 8 Kernel Version 9200 MP (2 procs) Free x64
    Built by: 9200.16461.amd64fre.win8_gdr.121119-1606
    System Uptime:0 days 0:47:51.655
    Probably caused by :ntkrnlmp.exe ( nt! ?? ::FNODOBFM::`string'+13ca8 )
    BugCheck 133, {1, 784, 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: 0000000000000784, The watchdog period.
    Arg3: 0000000000000000
    Arg4: 0000000000000000
    BUGCHECK_STR:  0x133
    DEFAULT_BUCKET_ID:  WIN8_DRIVER_FAULT
    PROCESS_NAME: WmiPrvSE.exe
    FAILURE_BUCKET_ID: 0x133_ISR_nt!_??_::FNODOBFM::_string_
      BIOS Version                  V8.7
      BIOS Release Date             09/04/2010
      Manufacturer                  MICRO-STAR INTERNATIONAL CO.,LTD
      Product Name                  MS-7388
    ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии``
    **************************Mon Jan 14 18:29:05.748 2013 (UTC - 5:00)**************************
    Loading Dump File [C:\Users\John\_jcgriff2_\dbug\__Kernel__\011413-20592-01.dmp]
    Windows 8 Kernel Version 9200 MP (2 procs) Free x64
    Built by: 9200.16461.amd64fre.win8_gdr.121119-1606
    System Uptime:0 days 0:00:40.540
    Probably caused by :ntkrnlmp.exe ( nt! ?? ::FNODOBFM::`string'+13ca8 )
    BugCheck 133, {1, 784, 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: 0000000000000784, The watchdog period.
    Arg3: 0000000000000000
    Arg4: 0000000000000000
    BUGCHECK_STR:  0x133
    DEFAULT_BUCKET_ID:  WIN8_DRIVER_FAULT
    PROCESS_NAME: System
    FAILURE_BUCKET_ID: 0x133_ISR_nt!_??_::FNODOBFM::_string_
    ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии``
    **************************Mon Jan 14 17:11:40.143 2013 (UTC - 5:00)**************************
    Loading Dump File [C:\Users\John\_jcgriff2_\dbug\__Kernel__\011413-25256-01.dmp]
    Windows 8 Kernel Version 9200 MP (2 procs) Free x64
    Built by: 9200.16461.amd64fre.win8_gdr.121119-1606
    System Uptime:0 days 0:54:56.832
    Probably caused by :ntkrnlmp.exe ( nt! ?? ::FNODOBFM::`string'+13ca8 )
    BugCheck 133, {1, 784, 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: 0000000000000784, The watchdog period.
    Arg3: 0000000000000000
    Arg4: 0000000000000000
    BUGCHECK_STR:  0x133
    DEFAULT_BUCKET_ID:  WIN8_DRIVER_FAULT
    PROCESS_NAME: System
    FAILURE_BUCKET_ID: 0x133_ISR_nt!_??_::FNODOBFM::_string_
      BIOS Version                  V8.7
      BIOS Release Date             09/04/2010
      Manufacturer                  MICRO-STAR INTERNATIONAL CO.,LTD
      Product Name                  MS-7388
    ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии``
    **************************Mon Jan 14 16:16:10.095 2013 (UTC - 5:00)**************************
    Loading Dump File [C:\Users\John\_jcgriff2_\dbug\__Kernel__\011413-19843-01.dmp]
    Windows 8 Kernel Version 9200 MP (2 procs) Free x64
    Built by: 9200.16461.amd64fre.win8_gdr.121119-1606
    System Uptime:0 days 0:46:04.900
    Probably caused by :ntkrnlmp.exe ( nt! ?? ::FNODOBFM::`string'+13ca8 )
    BugCheck 133, {1, 784, 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: 0000000000000784, The watchdog period.
    Arg3: 0000000000000000
    Arg4: 0000000000000000
    BUGCHECK_STR:  0x133
    DEFAULT_BUCKET_ID:  WIN8_DRIVER_FAULT
    PROCESS_NAME: System
    FAILURE_BUCKET_ID: 0x133_ISR_nt!_??_::FNODOBFM::_string_
      BIOS Version                  V8.7
      BIOS Release Date             09/04/2010
      Manufacturer                  MICRO-STAR INTERNATIONAL CO.,LTD
      Product Name                  MS-7388
    ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии``
    **************************Mon Jan 14 15:29:33.955 2013 (UTC - 5:00)**************************
    Loading Dump File [C:\Users\John\_jcgriff2_\dbug\__Kernel__\011413-21543-01.dmp]
    Windows 8 Kernel Version 9200 MP (2 procs) Free x64
    Built by: 9200.16461.amd64fre.win8_gdr.121119-1606
    System Uptime:0 days 0:16:00.748
    Probably caused by :ntkrnlmp.exe ( nt! ?? ::FNODOBFM::`string'+13ca8 )
    BugCheck 133, {1, 784, 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: 0000000000000784, The watchdog period.
    Arg3: 0000000000000000
    Arg4: 0000000000000000
    BUGCHECK_STR:  0x133
    DEFAULT_BUCKET_ID:  WIN8_DRIVER_FAULT
    PROCESS_NAME: backgroundTask
    FAILURE_BUCKET_ID: 0x133_ISR_nt!_??_::FNODOBFM::_string_
      BIOS Version                  V8.7
      BIOS Release Date             09/04/2010
      Manufacturer                  MICRO-STAR INTERNATIONAL CO.,LTD
      Product Name                  MS-7388
    ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии``
    **************************Mon Jan 14 15:13:01.472 2013 (UTC - 5:00)**************************
    Loading Dump File [C:\Users\John\_jcgriff2_\dbug\__Kernel__\011413-22573-01.dmp]
    Windows 8 Kernel Version 9200 MP (2 procs) Free x64
    Built by: 9200.16461.amd64fre.win8_gdr.121119-1606
    System Uptime:0 days 0:27:55.264
    Probably caused by :dxgmms1.sys ( dxgmms1!VIDMM_SEGMENT::SafeProbeAndLockPages+1bc )
    BugCheck 133, {1, 784, 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: 0000000000000784, The watchdog period.
    Arg3: 0000000000000000
    Arg4: 0000000000000000
    BUGCHECK_STR:  0x133
    DEFAULT_BUCKET_ID:  WIN8_DRIVER_FAULT
    PROCESS_NAME: Crysis.exe
    FAILURE_BUCKET_ID: 0x133_ISR_dxgmms1!VIDMM_SEGMENT::SafeProbeAndLockPages
      BIOS Version                  V8.7
      BIOS Release Date             09/04/2010
      Manufacturer                  MICRO-STAR INTERNATIONAL CO.,LTD
      Product Name                  MS-7388
    ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии``
    **************************Mon Jan 14 14:44:34.445 2013 (UTC - 5:00)**************************
    Loading Dump File [C:\Users\John\_jcgriff2_\dbug\__Kernel__\011413-37112-01.dmp]
    Windows 8 Kernel Version 9200 MP (2 procs) Free x64
    Built by: 9200.16461.amd64fre.win8_gdr.121119-1606
    System Uptime:0 days 11:10:32.237
    Probably caused by :ntkrnlmp.exe ( nt! ?? ::FNODOBFM::`string'+13ca8 )
    BugCheck 133, {1, 784, 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: 0000000000000784, The watchdog period.
    Arg3: 0000000000000000
    Arg4: 0000000000000000
    BUGCHECK_STR:  0x133
    DEFAULT_BUCKET_ID:  WIN8_DRIVER_FAULT
    PROCESS_NAME: chrome.exe
    FAILURE_BUCKET_ID: 0x133_ISR_nt!_??_::FNODOBFM::_string_
      BIOS Version                  V8.7
      BIOS Release Date             09/04/2010
      Manufacturer                  MICRO-STAR INTERNATIONAL CO.,LTD
      Product Name                  MS-7388
    ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии``
    **************************Mon Jan 14 03:29:55.337 2013 (UTC - 5:00)**************************
    Loading Dump File [C:\Users\John\_jcgriff2_\dbug\__Kernel__\011413-66425-01.dmp]
    Windows 8 Kernel Version 9200 MP (2 procs) Free x64
    Built by: 9200.16461.amd64fre.win8_gdr.121119-1606
    System Uptime:3 days 8:29:56.131
    Probably caused by :ntkrnlmp.exe ( nt! ?? ::FNODOBFM::`string'+13ca8 )
    BugCheck 133, {1, 784, 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: 0000000000000784, The watchdog period.
    Arg3: 0000000000000000
    Arg4: 0000000000000000
    BUGCHECK_STR:  0x133
    DEFAULT_BUCKET_ID:  WIN8_DRIVER_FAULT
    PROCESS_NAME: System
    FAILURE_BUCKET_ID: 0x133_ISR_nt!_??_::FNODOBFM::_string_
      BIOS Version                  V8.7
      BIOS Release Date             09/04/2010
      Manufacturer                  MICRO-STAR INTERNATIONAL CO.,LTD
      Product Name                  MS-7388
    ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии``
    
    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:
    **************************Tue Jan 15 14:17:28.843 2013 (UTC - 5:00)**************************
    SASDIFSV64.SYS              Mon Feb  8 19:11:52 2010 (4B70A848)
    SASKUTIL64.SYS              Tue Feb  9 17:27:34 2010 (4B71E156)
    SAlpham64.sys               Fri Sep 16 15:00:29 2011 (4E739CCD)
    Rt630x64.sys                Wed Oct 19 08:12:55 2011 (4E9EBEC7)
    GEARAspiWDM.sys             Thu May  3 15:56:17 2012 (4FA2E2E1)
    RTKVHD64.sys                Tue May  8 05:42:27 2012 (4FA8EA83)
    atikmpag.sys                Mon Jun 18 16:41:29 2012 (4FDF9279)
    atikmdag.sys                Mon Jun 18 17:21:01 2012 (4FDF9BBD)
    AtihdW86.sys                Tue Aug 21 22:26:37 2012 (5034435D)
    usbaapl64.sys               Fri Sep 28 13:32:37 2012 (5065DF35)
    lvrs64.sys                  Mon Oct 22 22:11:24 2012 (5085FCCC)
    lvuvc64.sys                 Mon Oct 22 22:12:08 2012 (5085FCF8)
    
    http://www.carrona.org/drivers/driver.php?id=SASDIFSV64.SYS
    http://www.carrona.org/drivers/driver.php?id=SASKUTIL64.SYS
    http://www.carrona.org/drivers/driver.php?id=SAlpham64.sys
    http://www.carrona.org/drivers/driver.php?id=Rt630x64.sys
    http://www.carrona.org/drivers/driver.php?id=GEARAspiWDM.sys
    http://www.carrona.org/drivers/driver.php?id=RTKVHD64.sys
    http://www.carrona.org/drivers/driver.php?id=atikmpag.sys
    http://www.carrona.org/drivers/driver.php?id=atikmdag.sys
    http://www.carrona.org/drivers/driver.php?id=AtihdW86.sys
    http://www.carrona.org/drivers/driver.php?id=usbaapl64.sys
    http://www.carrona.org/drivers/driver.php?id=lvrs64.sys
    http://www.carrona.org/drivers/driver.php?id=lvuvc64.sys
      My System SpecsSystem Spec

  3. #3


    Thank you for your response usasma!
    I'll respond to your instructions in turn.

    My MoBo is sort of old, so there hasn't been a BIOS update from MSI since 2010. It's as up-to-date as it can be.

    I've freed up a lot of HDD space.

    I'd be willing to do a fresh install if need be, but, obviously, it would be preferable to end the BSODs without a wipe.

    Concerning graphics drivers, though you say that there are a lot of video drivers installed, according to my programs list, there are no ATI drivers installed. I'm not exactly sure how to follow your instructions on this front, as none of the procedures in the link you provided give directions on how to uninstall video drivers that don't register as installed. It assumes that they show up in the Add/Remove Programs list. Any help?

    I uninstalled SUPERAntiSpyware, so that should be taken care of.

    I also don't have anything by SteelSeries installed, so I'm not certain how to proceed with uninstalling or updating the SAlpham64.sys driver.

    Also, I have no idea how to update or uninstall the Rt630x64.sys driver, as the Realtek website is confusing as hell.

    Thank you for your assistance.
      My System SpecsSystem Spec

  4. #4


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


    Just a general observation here. I'm starting to notice that the fewer 3rd party drivers that appear in the apps output - the more likely it is that this is a low-level problem.

    By low-level I mean:
    - borked (broken) hardware (several different procedures used to isolate the problem device)
    - overclocking - You'll know if you're overclocking or not. If uncertain we can suggest things to check.
    - compatibility issues (3rd party hardware/drivers)
    - low-level driver problems (mostly 3rd party software/drivers)
    - or even malware (scanned for when we ask for hardware diagnostics from Initial Hardware Diagnostics or Hardware Diagnostics ).

    I suggest that you perform the free hardware diagnostics listed here: Hardware Diagnostics

    I reran the memory dumps from 14 and 15 January - and the same results came up. There are ATI video drivers loaded on your system (and this is for your ATI Radeon HD 4800 video card). If the drivers aren't in Control Panel...Programs and Features - then install a fresh copy from the ATI website. If it asks, do not let it install AMD Overdrive (don't worry if it doesn't ask about it).

    Have you used any gaming peripherals in the past? Keyboards, mice, headsets, etc?
    If so, what was the make and model?

    As for the Realtek networking device,
    go to this link: Realtek
    Scroll down to the "Win8 Auto Installation Program (SID:1546352)"
    and click on one of the links to the right of it (the US1 stuff) in order to download it
      My System SpecsSystem Spec

  5. #5


    Regarding your list of potential "low-level problems":
    -It's completely possible that I have broken hardware. Most of my hardware is around 6 years old, so that could have something to do with it, I guess.
    -I'm not overclocking.
    -I haven't installed any new hardware, so there should be no new compatibility issues.
    -I don't know anything about drivers except that I should try to keep them updated.
    -I don't believe I'm infected with any malware. I suppose I could always be wrong.

    As for the hardware diagnostics, I'm a little lost with your link. Could you perhaps be more specific as to what I should do, please?

    I re-installed the ATI drivers with Catalyst Install Manager and all that. Should I now go back to your first response and follow the instructions in the "ATI video cards - DRIVER ONLY installation procedure" link?

    The only gaming peripheral I own is an old Ideazon ZBoard. Nothing by SteelSeries, so I'm still curious as to why that SteelSeries driver would be there.

    And I followed your instructions concerning the Realtek driver, so that should be taken care of.

    Thanks again.
      My System SpecsSystem Spec

  6. #6


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


    H/W Diagnostics:
    Please start by running these bootable hardware diagnostics:
    Memory Diagnostics (read the details at the link)
    Hard Drive Diagnostic Procedure (read the details at the link) - Test ALL of the hard drives.

    Also, please run one of these free, independent online malware scans to ensure that your current protection hasn't been compromised: Free Online AntiMalware Resources (read the details at the link)
    There are also free, bootable antivirus disks at this link: Free Online AntiMalware Resources - Bootable Disks
    If all of those pass, then you'll move on to those tests at Additional Hardware Diagnostics

    If the BSOD's continue, please zip up and upload the memory dumps (they're located in C:\Windows\Minidump)
      My System SpecsSystem Spec

  7. #7


    I've been trying to run the Memtest+ test, and my computer will always power down before the test is complete. No errors show, but the computer just shuts down without notice.
      My System SpecsSystem Spec

  8. #8


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


    Check for overheating...

    Wait for the system to shut down
    Unplug it from the wall and open the case.
    Hold onto the metal of the case with one hand (to prevent static discharge)
    DO NOT TOUCH anything inside the case.
    Rather you should feel around near the different items (motherboard, memory, CPU, etc) and see if anything is very hot. What you're looking for is something that's almost hot enough (or is hot enough) to burn you. Simply being very warm isn't a concern to us.
    Again I say - DO NOT TOUCH ANYTHING!!! I have gotten 2nd degree burns when doing this - and I'm fairly experienced at this.
    BE CAREFUL!!!
      My System SpecsSystem Spec

  9. #9


    I did as you instructed, and no component is that hot. The only thing that really seems warm at all is the heatsink/fan, which I imagine is how it should be.
      My System SpecsSystem Spec

  10. #10


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


    Hmmm, I wonder what's causing it.
    Try running MemTest with only one stick and try it in each slot.
    Then try the other stick(s) individually in each slot.

    Another option - if you get into Windows, run Prime95 to see what happens (you can download it using the instructions here: Additional Hardware Diagnostics )
      My System SpecsSystem Spec

Page 1 of 2 12 LastLast
Dpc_watchdog_violation
Related Threads
Dpc_watchdog_violation in BSOD Crashes and Debugging
Hello, I had a Dpc_watchdog_violation bsod today. It was completely out of nowhere after a month of using my new pc without any problem. I was just downloading something from steam and watching Game of Thrones from my NTB hard drive via lan. If you can help me diagnose what caused it, I would be...
Dpc_watchdog_violation in BSOD Crashes and Debugging
Hi,I am facing many BSOD , mainly DPC_WATCHDOG_VIOLATION and also others like IRQL-NOT LESS OR EQUAL,kernel mode exception not handled etc..sometimes i get them while paying games and even when watching movies or just browsing my hard disk.please help me out....see attachments.Thanks
dpc_watchdog_violation in BSOD Crashes and Debugging
guys i don't why but i started having dpc_watchdog_violation problem, like few days back, i restored my laptop to factory settings but still no help. I have lenovo y400. if you want full specs just check my profile or where ever the specs on this site are. and here is my minidump file. Download...
Another DPC_WATCHDOG_VIOLATION in BSOD Crashes and Debugging
Hey guys, new to the forums. New to Windows 8. Used to be able to fairly easily sort out issues for BSOD on previous windows... not sure why it's so hard with 8, lol. Anyways, i hope someone can help. I've been getting random freezes and BSOD's. Usually at night while i'm sleeping. I have...
Dpc_watchdog_violation in BSOD Crashes and Debugging
For some time now my computer has been having some stability issues. Today I had a DPC_WATCHDOG_VIOLATION 2 minutes after starting the computer. Here is the SF zip. It'll be most appreciated if anyone can help. Thanks.
Dpc_watchdog_violation in BSOD Crashes and Debugging
I have this error every time I use my main desktop. Could I have some help please? This is a retail version of Windows 8. What files do I need to upload so I can help you with solving my problem? Many thanks!
DPC_WATCHDOG_VIOLATION help! in BSOD Crashes and Debugging
Hey guys Recently got a new laptop running Windows 8. Initially I had a problem "Can not find script file c:\windows\temp\vaio care rescue tool.vbs" but this was solved by doing a system refresh. Since doing this refresh the laptop has been BSOD'ing on me with 2 messages. The first was...
Eight Forums Android App Eight Forums IOS App Follow us on Facebook