Windows 8 and 8.1 Forums


Intermittent DPC Watchdog Violation BSODs occurring

  1. #1


    Posts : 3
    Windows 8 Pro

    Intermittent DPC Watchdog Violation BSODs occurring


    Hello all,
    First time poster having some Windows 8 Pro difficulties. I keep getting the dreaded DPC_WATCHDOG_VIOLATION errors. It seems to be completely random as to when they occur (system idle, actively working, etc). The frequency is nearly everyday and it's not uncommon for me to see the Windows login screen when I return home from work or after I wake up in the morning. I have updated all the drivers that I can think of to Windows 8 versions, provided they are available, with the exception of my sound card because they have not released the full driver for my model yet (supposedly coming later this month). I upgraded from Windows 7 Professional, which was very stable for me, and so far I have refreshed Windows 8 once but that did not solve the problem. Any help would be much appreciated.

      My System SpecsSystem Spec

  2. #2


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


    Please remove the overclock and test the system without it. If that stops the BSOD's, then you've found your problem. If not, then continue with the rest of the tests without the overclock. Once the BSOD's have stopped, feel free to resume the overclock.

    Just FYI - we've seen issues in Win7 with the BigFoot network cards. There haven't been issues recently, so this could be due to an updated driver (and it may/may not be workable in Win8).

    We've seen a number of BSOD issues with SSD's. Here's the information that I've compiled so far:
    There's not a whole bunch available to test SSD's. The "easiest" test is to remove the SSD, install a platter-based hard drive, install Windows and test for stability that way.

    Here's some suggestions:
    - Update the SSD's firmware to the latest available version (VERY IMPORTANT!!!)
    - Update the motherboard controllers drivers to the latest available version from the controller manufacturer (NOT the mobo manufacturer unless you can't find any on the controller manufacturer's website)
    - Slow the memory (RAM) down to the next slower speed (I've only seen one person who claimed that this worked for them).
    - Use any manufacturer's utilities that you may have. If you don't have any, then try this free one (I haven't used it myself): Crystal Dew World
    - Update chipset and storage controller drivers to the latest available from the manufacturer of the device (not the manufacturer of the motherboard). Be sure to update ALL controllers on the motherboard!
    ....NOTE: Recently (Nov 2011) we had BSOD issues with the Marvell 91xx controller and an SSD. You may have to switch controllers also.
    - Replace the SSD with a platter based hard drive and see if that stops the BSOD's. If it does, then it's likely that there's a problem with the SSD OR an incompatibility with your system.
    It's my opinion that SSD's aren't reliable enough (with current hardware) to be used on a system that needs to work reliably. Until I see reliability I will not recommend, nor will I use, SSD's for critical applications.
    06 Dec 2011 - This post tends to confirm issues with certain SSD chipsets and certain controllers - [SOLVED] cant find the cause of BSOD F4 - Tech Support Forum
    29 May 2012 - The frequency of BSOD's with SSD's seems to have been decreasing over the last several months. It may be approaching time to re-evaluate my stand on their suitability for use in production systems.
    10 Nov 2012 - I'm seeing an upswing in SSD errors - but most appear due to older storage controller drivers. I strongly suggest NOT using storage controller drivers that don't date from 2012 (if none are available, don't connect an SSD to that controller)
    FWIW - the majority of STOP 0x133 errors that I'm seeing are in systems with SSD's (with uncertain firmware revisions) and older storage controller drivers.

    BUT, in this case, the BSOD's that I see in MSINFO32 (and the memory dumps) point at Xeno7x64.sys - a driver for your BigFoot network card. I presume that the "7" in the driver name refers to Win7 - so please be sure that the driver is certified compatible with Win8 (it dates from May of 2011, so I have to wonder if it's compatible with Win8). In case of corruption, remove the drivers (and the rest of the software) currently installed and then install a fresh copy.

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

    WRfiltv.sys Thu Jul 30 23:40:32 2009 (4A7267B0)
    Creative Audio Driver - maybe the WoW headset?
    WRfiltv.sys - this driver hasn't been added to the DRT as of this run. Please search Google/Bing for the driver if additional information is needed.

    Edge7x64.sys Wed May 18 18:55:15 2011 (4DD44E53)
    Bigfoot Networks Killer Xeno NDIS-EDGE Miniport Driver (this card is from VisionTek)
    http://www.carrona.org/drivers/driver.php?id=Edge7x64.sys

    Xeno7x64.sys Wed May 18 18:55:16 2011 (4DD44E54)
    Bigfoot Networks Killer Xeno PCI-E Gaming Adapter (this card is from VisionTek)
    http://www.carrona.org/drivers/driver.php?id=Xeno7x64.sys

    emupia2k.sys Thu Aug 11 06:03:39 2011 (4E43A8FB)
    Creative E-mu Plug-in Architecture Driver
    http://www.carrona.org/drivers/driver.php?id=emupia2k.sys

    ctsfm2k.sys Thu Aug 11 06:03:48 2011 (4E43A904)
    Creative SoundFont Management Device Driver
    http://www.carrona.org/drivers/driver.php?id=ctsfm2k.sys

    ctoss2k.sys Thu Aug 11 06:04:05 2011 (4E43A915)
    Creative OS Services Driver
    http://www.carrona.org/drivers/driver.php?id=ctoss2k.sys

    ha20x22k.sys Thu Aug 11 06:07:26 2011 (4E43A9DE)
    Creative Technology Audigy
    http://www.carrona.org/drivers/driver.php?id=ha20x22k.sys

    ctaud2k.sys Thu Aug 11 06:08:16 2011 (4E43AA10)
    Creative Audio Driver (WDM)
    http://www.carrona.org/drivers/driver.php?id=ctaud2k.sys

    ctprxy2k.sys Thu Aug 11 06:08:19 2011 (4E43AA13)
    Creative Audio Driver (WDM)
    http://www.carrona.org/drivers/driver.php?id=ctprxy2k.sys

    CTEXFIFX.SYS Thu Aug 11 06:09:50 2011 (4E43AA6E)
    Creative sound card driver
    http://www.carrona.org/drivers/driver.php?id=CTEXFIFX.SYS

    CT20XUT.SYS Thu Aug 11 06:09:58 2011 (4E43AA76)
    Creative sound card driver
    http://www.carrona.org/drivers/driver.php?id=CT20XUT.SYS

    CTHWIUT.SYS Thu Aug 11 06:10:02 2011 (4E43AA7A)
    Creative sound card driver
    http://www.carrona.org/drivers/driver.php?id=CTHWIUT.SYS



    Analysis:
    The following is for informational purposes only.
    Code:
    **************************Thu Dec 20 10:06:58.904 2012 (UTC - 5:00)**************************
    Loading Dump File [C:\Users\John\_jcgriff2_\dbug\__Kernel__\122012-17281-01.dmp]
    Windows 8 Kernel Version 9200 MP (12 procs) Free x64
    Built by: 9200.16461.amd64fre.win8_gdr.121119-1606
    System Uptime:0 days 5:29:55.516
    *** WARNING: Unable to verify timestamp for Xeno7x64.sys
    *** ERROR: Module load completed but symbols could not be loaded for Xeno7x64.sys
    Probably caused by :Xeno7x64.sys ( Xeno7x64+12230 )
    BugCheck 133, {0, 281, 280, 0}
    BugCheck Info: DPC_WATCHDOG_VIOLATION (133)
    Arguments: 
    Arg1: 0000000000000000, A single DPC or ISR exceeded its time allotment. The offending
        component can usually be identified with a stack trace.
    Arg2: 0000000000000281, The DPC time count (in ticks).
    Arg3: 0000000000000280, The DPC time allotment (in ticks).
    Arg4: 0000000000000000
    BUGCHECK_STR:  0x133
    DEFAULT_BUCKET_ID:  WIN8_DRIVER_FAULT
    PROCESS_NAME: System
    FAILURE_BUCKET_ID: 0x133_DPC_Xeno7x64+12230
    CPUID:        "Intel(R) Core(TM) i7 CPU       X 980  @ 3.33GHz"
    MaxSpeed:     3330
    CurrentSpeed: 3575
     
    Processor may be overclocked!
    Expected Frequency:   3330
    Actual Frequency:     3575
    Overclock Ratio:      1.07357
     
      BIOS Version                  F4d
      BIOS Release Date             12/12/2011
      Manufacturer                  Gigabyte Technology Co., Ltd.
      Product Name                  G1.Guerrilla
    ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии``
    **************************Thu Dec 20 04:36:24.076 2012 (UTC - 5:00)**************************
    Loading Dump File [C:\Users\John\_jcgriff2_\dbug\__Kernel__\122012-18968-01.dmp]
    Windows 8 Kernel Version 9200 MP (12 procs) Free x64
    Built by: 9200.16461.amd64fre.win8_gdr.121119-1606
    System Uptime:0 days 9:53:15.527
    *** WARNING: Unable to verify timestamp for Xeno7x64.sys
    *** ERROR: Module load completed but symbols could not be loaded for Xeno7x64.sys
    Probably caused by :Xeno7x64.sys ( Xeno7x64+12230 )
    BugCheck 133, {0, 281, 280, 0}
    BugCheck Info: DPC_WATCHDOG_VIOLATION (133)
    Arguments: 
    Arg1: 0000000000000000, A single DPC or ISR exceeded its time allotment. The offending
        component can usually be identified with a stack trace.
    Arg2: 0000000000000281, The DPC time count (in ticks).
    Arg3: 0000000000000280, The DPC time allotment (in ticks).
    Arg4: 0000000000000000
    BUGCHECK_STR:  0x133
    DEFAULT_BUCKET_ID:  WIN8_DRIVER_FAULT
    PROCESS_NAME: System
    FAILURE_BUCKET_ID: 0x133_DPC_Xeno7x64+12230
    CPUID:        "Intel(R) Core(TM) i7 CPU       X 980  @ 3.33GHz"
    MaxSpeed:     3330
    CurrentSpeed: 3575
     
    Processor may be overclocked!
    Expected Frequency:   3330
    Actual Frequency:     3575
    Overclock Ratio:      1.07357
     
      BIOS Version                  F4d
      BIOS Release Date             12/12/2011
      Manufacturer                  Gigabyte Technology Co., Ltd.
      Product Name                  G1.Guerrilla
    ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии``
    **************************Wed Dec 19 18:16:31.913 2012 (UTC - 5:00)**************************
    Loading Dump File [C:\Users\John\_jcgriff2_\dbug\__Kernel__\121912-17031-01.dmp]
    Windows 8 Kernel Version 9200 MP (12 procs) Free x64
    Built by: 9200.16461.amd64fre.win8_gdr.121119-1606
    System Uptime:0 days 3:25:18.525
    *** WARNING: Unable to verify timestamp for Xeno7x64.sys
    *** ERROR: Module load completed but symbols could not be loaded for Xeno7x64.sys
    Probably caused by :Xeno7x64.sys ( Xeno7x64+12230 )
    BugCheck 133, {0, 281, 280, 0}
    BugCheck Info: DPC_WATCHDOG_VIOLATION (133)
    Arguments: 
    Arg1: 0000000000000000, A single DPC or ISR exceeded its time allotment. The offending
        component can usually be identified with a stack trace.
    Arg2: 0000000000000281, The DPC time count (in ticks).
    Arg3: 0000000000000280, The DPC time allotment (in ticks).
    Arg4: 0000000000000000
    BUGCHECK_STR:  0x133
    DEFAULT_BUCKET_ID:  WIN8_DRIVER_FAULT
    PROCESS_NAME: System
    FAILURE_BUCKET_ID: 0x133_DPC_Xeno7x64+12230
    CPUID:        "Intel(R) Core(TM) i7 CPU       X 980  @ 3.33GHz"
    MaxSpeed:     3330
    CurrentSpeed: 3575
     
    Processor may be overclocked!
    Expected Frequency:   3330
    Actual Frequency:     3575
    Overclock Ratio:      1.07357
     
      BIOS Version                  F4d
      BIOS Release Date             12/12/2011
      Manufacturer                  Gigabyte Technology Co., Ltd.
      Product Name                  G1.Guerrilla
    ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии``
    **************************Wed Dec 19 14:50:35.443 2012 (UTC - 5:00)**************************
    Loading Dump File [C:\Users\John\_jcgriff2_\dbug\__Kernel__\121912-16968-01.dmp]
    Windows 8 Kernel Version 9200 MP (12 procs) Free x64
    Built by: 9200.16461.amd64fre.win8_gdr.121119-1606
    System Uptime:0 days 23:53:29.518
    *** WARNING: Unable to verify timestamp for Xeno7x64.sys
    *** ERROR: Module load completed but symbols could not be loaded for Xeno7x64.sys
    Probably caused by :Xeno7x64.sys ( Xeno7x64+12230 )
    BugCheck 133, {0, 281, 280, 0}
    BugCheck Info: DPC_WATCHDOG_VIOLATION (133)
    Arguments: 
    Arg1: 0000000000000000, A single DPC or ISR exceeded its time allotment. The offending
        component can usually be identified with a stack trace.
    Arg2: 0000000000000281, The DPC time count (in ticks).
    Arg3: 0000000000000280, The DPC time allotment (in ticks).
    Arg4: 0000000000000000
    BUGCHECK_STR:  0x133
    DEFAULT_BUCKET_ID:  WIN8_DRIVER_FAULT
    PROCESS_NAME: System
    FAILURE_BUCKET_ID: 0x133_DPC_Xeno7x64+12230
    CPUID:        "Intel(R) Core(TM) i7 CPU       X 980  @ 3.33GHz"
    MaxSpeed:     3330
    CurrentSpeed: 3575
     
    Processor may be overclocked!
    Expected Frequency:   3330
    Actual Frequency:     3575
    Overclock Ratio:      1.07357
     
      BIOS Version                  F4d
      BIOS Release Date             12/12/2011
      Manufacturer                  Gigabyte Technology Co., Ltd.
      Product Name                  G1.Guerrilla
    ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии``
    **************************Tue Dec 18 14:56:09.920 2012 (UTC - 5:00)**************************
    Loading Dump File [C:\Users\John\_jcgriff2_\dbug\__Kernel__\121812-17093-01.dmp]
    Windows 8 Kernel Version 9200 MP (12 procs) Free x64
    Built by: 9200.16461.amd64fre.win8_gdr.121119-1606
    System Uptime:0 days 15:09:10.531
    *** WARNING: Unable to verify timestamp for Xeno7x64.sys
    *** ERROR: Module load completed but symbols could not be loaded for Xeno7x64.sys
    Probably caused by :Xeno7x64.sys ( Xeno7x64+12230 )
    BugCheck 133, {0, 281, 280, 0}
    BugCheck Info: DPC_WATCHDOG_VIOLATION (133)
    Arguments: 
    Arg1: 0000000000000000, A single DPC or ISR exceeded its time allotment. The offending
        component can usually be identified with a stack trace.
    Arg2: 0000000000000281, The DPC time count (in ticks).
    Arg3: 0000000000000280, The DPC time allotment (in ticks).
    Arg4: 0000000000000000
    BUGCHECK_STR:  0x133
    DEFAULT_BUCKET_ID:  WIN8_DRIVER_FAULT
    PROCESS_NAME: System
    FAILURE_BUCKET_ID: 0x133_DPC_Xeno7x64+12230
    CPUID:        "Intel(R) Core(TM) i7 CPU       X 980  @ 3.33GHz"
    MaxSpeed:     3330
    CurrentSpeed: 3575
     
    Processor may be overclocked!
    Expected Frequency:   3330
    Actual Frequency:     3575
    Overclock Ratio:      1.07357
     
      BIOS Version                  F4d
      BIOS Release Date             12/12/2011
      Manufacturer                  Gigabyte Technology Co., Ltd.
      Product Name                  G1.Guerrilla
    ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии``
    **************************Mon Dec 17 23:46:19.410 2012 (UTC - 5:00)**************************
    Loading Dump File [C:\Users\John\_jcgriff2_\dbug\__Kernel__\121712-18187-01.dmp]
    Windows 8 Kernel Version 9200 MP (12 procs) Free x64
    Built by: 9200.16461.amd64fre.win8_gdr.121119-1606
    System Uptime:0 days 1:30:07.021
    *** WARNING: Unable to verify timestamp for Xeno7x64.sys
    *** ERROR: Module load completed but symbols could not be loaded for Xeno7x64.sys
    Probably caused by :Xeno7x64.sys ( Xeno7x64+12230 )
    BugCheck 133, {0, 281, 280, 0}
    BugCheck Info: DPC_WATCHDOG_VIOLATION (133)
    Arguments: 
    Arg1: 0000000000000000, A single DPC or ISR exceeded its time allotment. The offending
        component can usually be identified with a stack trace.
    Arg2: 0000000000000281, The DPC time count (in ticks).
    Arg3: 0000000000000280, The DPC time allotment (in ticks).
    Arg4: 0000000000000000
    BUGCHECK_STR:  0x133
    DEFAULT_BUCKET_ID:  WIN8_DRIVER_FAULT
    PROCESS_NAME: System
    FAILURE_BUCKET_ID: 0x133_DPC_Xeno7x64+12230
    CPUID:        "Intel(R) Core(TM) i7 CPU       X 980  @ 3.33GHz"
    MaxSpeed:     3330
    CurrentSpeed: 3575
     
    Processor may be overclocked!
    Expected Frequency:   3330
    Actual Frequency:     3575
    Overclock Ratio:      1.07357
     
      BIOS Version                  F4d
      BIOS Release Date             12/12/2011
      Manufacturer                  Gigabyte Technology Co., Ltd.
      Product Name                  G1.Guerrilla
    ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии``
    **************************Mon Dec 17 01:29:59.909 2012 (UTC - 5:00)**************************
    Loading Dump File [C:\Users\John\_jcgriff2_\dbug\__Kernel__\121712-17218-01.dmp]
    Windows 8 Kernel Version 9200 MP (12 procs) Free x64
    Built by: 9200.16442.amd64fre.win8_gdr.121023-1503
    System Uptime:0 days 10:38:23.520
    *** WARNING: Unable to verify timestamp for Xeno7x64.sys
    *** ERROR: Module load completed but symbols could not be loaded for Xeno7x64.sys
    Probably caused by :Xeno7x64.sys ( Xeno7x64+12230 )
    BugCheck 133, {0, 281, 280, 0}
    BugCheck Info: DPC_WATCHDOG_VIOLATION (133)
    Arguments: 
    Arg1: 0000000000000000, A single DPC or ISR exceeded its time allotment. The offending
        component can usually be identified with a stack trace.
    Arg2: 0000000000000281, The DPC time count (in ticks).
    Arg3: 0000000000000280, The DPC time allotment (in ticks).
    Arg4: 0000000000000000
    BUGCHECK_STR:  0x133
    DEFAULT_BUCKET_ID:  WIN8_DRIVER_FAULT
    PROCESS_NAME: System
    FAILURE_BUCKET_ID: 0x133_DPC_Xeno7x64+12230
    CPUID:        "Intel(R) Core(TM) i7 CPU       X 980  @ 3.33GHz"
    MaxSpeed:     3330
    CurrentSpeed: 3575
     
    Processor may be overclocked!
    Expected Frequency:   3330
    Actual Frequency:     3575
    Overclock Ratio:      1.07357
     
      BIOS Version                  F4d
      BIOS Release Date             12/12/2011
      Manufacturer                  Gigabyte Technology Co., Ltd.
      Product Name                  G1.Guerrilla
    ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии``
    **************************Sun Dec 16 14:50:58.918 2012 (UTC - 5:00)**************************
    Loading Dump File [C:\Users\John\_jcgriff2_\dbug\__Kernel__\121612-18859-01.dmp]
    Windows 8 Kernel Version 9200 MP (12 procs) Free x64
    Built by: 9200.16442.amd64fre.win8_gdr.121023-1503
    System Uptime:0 days 22:55:24.530
    *** WARNING: Unable to verify timestamp for Xeno7x64.sys
    *** ERROR: Module load completed but symbols could not be loaded for Xeno7x64.sys
    Probably caused by :Xeno7x64.sys ( Xeno7x64+12230 )
    BugCheck 133, {0, 281, 280, 0}
    BugCheck Info: DPC_WATCHDOG_VIOLATION (133)
    Arguments: 
    Arg1: 0000000000000000, A single DPC or ISR exceeded its time allotment. The offending
        component can usually be identified with a stack trace.
    Arg2: 0000000000000281, The DPC time count (in ticks).
    Arg3: 0000000000000280, The DPC time allotment (in ticks).
    Arg4: 0000000000000000
    BUGCHECK_STR:  0x133
    DEFAULT_BUCKET_ID:  WIN8_DRIVER_FAULT
    PROCESS_NAME: System
    FAILURE_BUCKET_ID: 0x133_DPC_Xeno7x64+12230
    CPUID:        "Intel(R) Core(TM) i7 CPU       X 980  @ 3.33GHz"
    MaxSpeed:     3330
    CurrentSpeed: 3575
     
    Processor may be overclocked!
    Expected Frequency:   3330
    Actual Frequency:     3575
    Overclock Ratio:      1.07357
     
      BIOS Version                  F4d
      BIOS Release Date             12/12/2011
      Manufacturer                  Gigabyte Technology Co., Ltd.
      Product Name                  G1.Guerrilla
    ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии``
    **************************Sat Dec 15 15:54:56.915 2012 (UTC - 5:00)**************************
    Loading Dump File [C:\Users\John\_jcgriff2_\dbug\__Kernel__\121512-27531-01.dmp]
    Windows 8 Kernel Version 9200 MP (12 procs) Free x64
    Built by: 9200.16442.amd64fre.win8_gdr.121023-1503
    System Uptime:0 days 21:19:20.527
    *** WARNING: Unable to verify timestamp for Xeno7x64.sys
    *** ERROR: Module load completed but symbols could not be loaded for Xeno7x64.sys
    Probably caused by :Xeno7x64.sys ( Xeno7x64+12230 )
    BugCheck 133, {0, 281, 280, 0}
    BugCheck Info: DPC_WATCHDOG_VIOLATION (133)
    Arguments: 
    Arg1: 0000000000000000, A single DPC or ISR exceeded its time allotment. The offending
        component can usually be identified with a stack trace.
    Arg2: 0000000000000281, The DPC time count (in ticks).
    Arg3: 0000000000000280, The DPC time allotment (in ticks).
    Arg4: 0000000000000000
    BUGCHECK_STR:  0x133
    DEFAULT_BUCKET_ID:  WIN8_DRIVER_FAULT
    PROCESS_NAME: System
    FAILURE_BUCKET_ID: 0x133_DPC_Xeno7x64+12230
    CPUID:        "Intel(R) Core(TM) i7 CPU       X 980  @ 3.33GHz"
    MaxSpeed:     3330
    CurrentSpeed: 3575
     
    Processor may be overclocked!
    Expected Frequency:   3330
    Actual Frequency:     3575
    Overclock Ratio:      1.07357
     
      BIOS Version                  F4d
      BIOS Release Date             12/12/2011
      Manufacturer                  Gigabyte Technology Co., Ltd.
      Product Name                  G1.Guerrilla
    ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии``
    **************************Sun Dec  9 16:12:37.405 2012 (UTC - 5:00)**************************
    Loading Dump File [C:\Users\John\_jcgriff2_\dbug\__Kernel__\120912-19140-01.dmp]
    Windows 8 Kernel Version 9200 MP (12 procs) Free x64
    Built by: 9200.16442.amd64fre.win8_gdr.121023-1503
    System Uptime:0 days 3:08:40.017
    *** WARNING: Unable to verify timestamp for Xeno7x64.sys
    *** ERROR: Module load completed but symbols could not be loaded for Xeno7x64.sys
    Probably caused by :Xeno7x64.sys ( Xeno7x64+12230 )
    BugCheck 133, {0, 281, 280, 0}
    BugCheck Info: DPC_WATCHDOG_VIOLATION (133)
    Arguments: 
    Arg1: 0000000000000000, A single DPC or ISR exceeded its time allotment. The offending
        component can usually be identified with a stack trace.
    Arg2: 0000000000000281, The DPC time count (in ticks).
    Arg3: 0000000000000280, The DPC time allotment (in ticks).
    Arg4: 0000000000000000
    BUGCHECK_STR:  0x133
    DEFAULT_BUCKET_ID:  WIN8_DRIVER_FAULT
    PROCESS_NAME: System
    FAILURE_BUCKET_ID: 0x133_DPC_Xeno7x64+12230
    CPUID:        "Intel(R) Core(TM) i7 CPU       X 980  @ 3.33GHz"
    MaxSpeed:     3330
    CurrentSpeed: 3575
     
    Processor may be overclocked!
    Expected Frequency:   3330
    Actual Frequency:     3575
    Overclock Ratio:      1.07357
     
      BIOS Version                  F4d
      BIOS Release Date             12/12/2011
      Manufacturer                  Gigabyte Technology Co., Ltd.
      Product Name                  G1.Guerrilla
    ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии``
    **************************Sun Dec  9 12:56:10.603 2012 (UTC - 5:00)**************************
    Loading Dump File [C:\Users\John\_jcgriff2_\dbug\__Kernel__\120912-19640-01.dmp]
    Windows 8 Kernel Version 9200 MP (12 procs) Free x64
    Built by: 9200.16442.amd64fre.win8_gdr.121023-1503
    System Uptime:0 days 5:45:20.027
    *** WARNING: Unable to verify timestamp for Xeno7x64.sys
    *** ERROR: Module load completed but symbols could not be loaded for Xeno7x64.sys
    Probably caused by :Xeno7x64.sys ( Xeno7x64+12230 )
    BugCheck 133, {0, 281, 280, 0}
    BugCheck Info: DPC_WATCHDOG_VIOLATION (133)
    Arguments: 
    Arg1: 0000000000000000, A single DPC or ISR exceeded its time allotment. The offending
        component can usually be identified with a stack trace.
    Arg2: 0000000000000281, The DPC time count (in ticks).
    Arg3: 0000000000000280, The DPC time allotment (in ticks).
    Arg4: 0000000000000000
    BUGCHECK_STR:  0x133
    DEFAULT_BUCKET_ID:  WIN8_DRIVER_FAULT
    PROCESS_NAME: System
    FAILURE_BUCKET_ID: 0x133_DPC_Xeno7x64+12230
    CPUID:        "Intel(R) Core(TM) i7 CPU       X 980  @ 3.33GHz"
    MaxSpeed:     3330
    CurrentSpeed: 3575
     
    Processor may be overclocked!
    Expected Frequency:   3330
    Actual Frequency:     3575
    Overclock Ratio:      1.07357
     
      BIOS Version                  F4d
      BIOS Release Date             12/12/2011
      Manufacturer                  Gigabyte Technology Co., Ltd.
      Product Name                  G1.Guerrilla
    ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии``
    **************************Sun Dec  9 07:09:25.444 2012 (UTC - 5:00)**************************
    Loading Dump File [C:\Users\John\_jcgriff2_\dbug\__Kernel__\120912-19218-01.dmp]
    Windows 8 Kernel Version 9200 MP (12 procs) Free x64
    Built by: 9200.16442.amd64fre.win8_gdr.121023-1503
    System Uptime:0 days 10:50:48.021
    *** WARNING: Unable to verify timestamp for Xeno7x64.sys
    *** ERROR: Module load completed but symbols could not be loaded for Xeno7x64.sys
    Probably caused by :Xeno7x64.sys ( Xeno7x64+12230 )
    BugCheck 133, {0, 281, 280, 0}
    BugCheck Info: DPC_WATCHDOG_VIOLATION (133)
    Arguments: 
    Arg1: 0000000000000000, A single DPC or ISR exceeded its time allotment. The offending
        component can usually be identified with a stack trace.
    Arg2: 0000000000000281, The DPC time count (in ticks).
    Arg3: 0000000000000280, The DPC time allotment (in ticks).
    Arg4: 0000000000000000
    BUGCHECK_STR:  0x133
    DEFAULT_BUCKET_ID:  WIN8_DRIVER_FAULT
    PROCESS_NAME: System
    FAILURE_BUCKET_ID: 0x133_DPC_Xeno7x64+12230
    CPUID:        "Intel(R) Core(TM) i7 CPU       X 980  @ 3.33GHz"
    MaxSpeed:     3330
    CurrentSpeed: 3575
     
    Processor may be overclocked!
    Expected Frequency:   3330
    Actual Frequency:     3575
    Overclock Ratio:      1.07357
     
      BIOS Version                  F4d
      BIOS Release Date             12/12/2011
      Manufacturer                  Gigabyte Technology Co., Ltd.
      Product Name                  G1.Guerrilla
    ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии``
    **************************Sat Dec  8 14:51:03.917 2012 (UTC - 5:00)**************************
    Loading Dump File [C:\Users\John\_jcgriff2_\dbug\__Kernel__\120812-18953-01.dmp]
    Windows 8 Kernel Version 9200 MP (12 procs) Free x64
    Built by: 9200.16442.amd64fre.win8_gdr.121023-1503
    System Uptime:0 days 1:23:26.529
    *** WARNING: Unable to verify timestamp for Xeno7x64.sys
    *** ERROR: Module load completed but symbols could not be loaded for Xeno7x64.sys
    Probably caused by :Xeno7x64.sys ( Xeno7x64+12230 )
    BugCheck 133, {0, 281, 280, 0}
    BugCheck Info: DPC_WATCHDOG_VIOLATION (133)
    Arguments: 
    Arg1: 0000000000000000, A single DPC or ISR exceeded its time allotment. The offending
        component can usually be identified with a stack trace.
    Arg2: 0000000000000281, The DPC time count (in ticks).
    Arg3: 0000000000000280, The DPC time allotment (in ticks).
    Arg4: 0000000000000000
    BUGCHECK_STR:  0x133
    DEFAULT_BUCKET_ID:  WIN8_DRIVER_FAULT
    PROCESS_NAME: System
    FAILURE_BUCKET_ID: 0x133_DPC_Xeno7x64+12230
    CPUID:        "Intel(R) Core(TM) i7 CPU       X 980  @ 3.33GHz"
    MaxSpeed:     3330
    CurrentSpeed: 3575
     
    Processor may be overclocked!
    Expected Frequency:   3330
    Actual Frequency:     3575
    Overclock Ratio:      1.07357
     
      BIOS Version                  F4d
      BIOS Release Date             12/12/2011
      Manufacturer                  Gigabyte Technology Co., Ltd.
      Product Name                  G1.Guerrilla
    ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии``
    **************************Fri Dec  7 19:44:55.911 2012 (UTC - 5:00)**************************
    Loading Dump File [C:\Users\John\_jcgriff2_\dbug\__Kernel__\120712-19546-01.dmp]
    Windows 8 Kernel Version 9200 MP (12 procs) Free x64
    Built by: 9200.16442.amd64fre.win8_gdr.121023-1503
    System Uptime:0 days 16:53:19.523
    *** WARNING: Unable to verify timestamp for Xeno7x64.sys
    *** ERROR: Module load completed but symbols could not be loaded for Xeno7x64.sys
    Probably caused by :Xeno7x64.sys ( Xeno7x64+12230 )
    BugCheck 133, {0, 281, 280, 0}
    BugCheck Info: DPC_WATCHDOG_VIOLATION (133)
    Arguments: 
    Arg1: 0000000000000000, A single DPC or ISR exceeded its time allotment. The offending
        component can usually be identified with a stack trace.
    Arg2: 0000000000000281, The DPC time count (in ticks).
    Arg3: 0000000000000280, The DPC time allotment (in ticks).
    Arg4: 0000000000000000
    BUGCHECK_STR:  0x133
    DEFAULT_BUCKET_ID:  WIN8_DRIVER_FAULT
    PROCESS_NAME: System
    FAILURE_BUCKET_ID: 0x133_DPC_Xeno7x64+12230
    CPUID:        "Intel(R) Core(TM) i7 CPU       X 980  @ 3.33GHz"
    MaxSpeed:     3330
    CurrentSpeed: 3575
     
    Processor may be overclocked!
    Expected Frequency:   3330
    Actual Frequency:     3575
    Overclock Ratio:      1.07357
     
      BIOS Version                  F4d
      BIOS Release Date             12/12/2011
      Manufacturer                  Gigabyte Technology Co., Ltd.
      Product Name                  G1.Guerrilla
    ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии``
    **************************Fri Dec  7 02:50:12.914 2012 (UTC - 5:00)**************************
    Loading Dump File [C:\Users\John\_jcgriff2_\dbug\__Kernel__\120712-18984-01.dmp]
    Windows 8 Kernel Version 9200 MP (12 procs) Free x64
    Built by: 9200.16442.amd64fre.win8_gdr.121023-1503
    System Uptime:0 days 7:03:44.526
    *** WARNING: Unable to verify timestamp for Xeno7x64.sys
    *** ERROR: Module load completed but symbols could not be loaded for Xeno7x64.sys
    Probably caused by :Xeno7x64.sys ( Xeno7x64+12230 )
    BugCheck 133, {0, 281, 280, 0}
    BugCheck Info: DPC_WATCHDOG_VIOLATION (133)
    Arguments: 
    Arg1: 0000000000000000, A single DPC or ISR exceeded its time allotment. The offending
        component can usually be identified with a stack trace.
    Arg2: 0000000000000281, The DPC time count (in ticks).
    Arg3: 0000000000000280, The DPC time allotment (in ticks).
    Arg4: 0000000000000000
    BUGCHECK_STR:  0x133
    DEFAULT_BUCKET_ID:  WIN8_DRIVER_FAULT
    PROCESS_NAME: System
    FAILURE_BUCKET_ID: 0x133_DPC_Xeno7x64+12230
    CPUID:        "Intel(R) Core(TM) i7 CPU       X 980  @ 3.33GHz"
    MaxSpeed:     3330
    CurrentSpeed: 3575
     
    Processor may be overclocked!
    Expected Frequency:   3330
    Actual Frequency:     3575
    Overclock Ratio:      1.07357
     
      BIOS Version                  F4d
      BIOS Release Date             12/12/2011
      Manufacturer                  Gigabyte Technology Co., Ltd.
      Product Name                  G1.Guerrilla
    ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии``
    **************************Thu Dec  6 13:08:24.913 2012 (UTC - 5:00)**************************
    Loading Dump File [C:\Users\John\_jcgriff2_\dbug\__Kernel__\120612-12093-01.dmp]
    Windows 8 Kernel Version 9200 MP (12 procs) Free x64
    Built by: 9200.16442.amd64fre.win8_gdr.121023-1503
    System Uptime:0 days 14:14:57.526
    *** WARNING: Unable to verify timestamp for Xeno7x64.sys
    *** ERROR: Module load completed but symbols could not be loaded for Xeno7x64.sys
    Probably caused by :Xeno7x64.sys ( Xeno7x64+12230 )
    BugCheck 133, {0, 281, 280, 0}
    BugCheck Info: DPC_WATCHDOG_VIOLATION (133)
    Arguments: 
    Arg1: 0000000000000000, A single DPC or ISR exceeded its time allotment. The offending
        component can usually be identified with a stack trace.
    Arg2: 0000000000000281, The DPC time count (in ticks).
    Arg3: 0000000000000280, The DPC time allotment (in ticks).
    Arg4: 0000000000000000
    BUGCHECK_STR:  0x133
    DEFAULT_BUCKET_ID:  WIN8_DRIVER_FAULT
    PROCESS_NAME: System
    FAILURE_BUCKET_ID: 0x133_DPC_Xeno7x64+12230
    CPUID:        "Intel(R) Core(TM) i7 CPU       X 980  @ 3.33GHz"
    MaxSpeed:     3330
    CurrentSpeed: 3575
     
    Processor may be overclocked!
    Expected Frequency:   3330
    Actual Frequency:     3575
    Overclock Ratio:      1.07357
     
      BIOS Version                  F4d
      BIOS Release Date             12/12/2011
      Manufacturer                  Gigabyte Technology Co., Ltd.
      Product Name                  G1.Guerrilla
    ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии``
    **************************Wed Dec  5 21:32:52.915 2012 (UTC - 5:00)**************************
    Loading Dump File [C:\Users\John\_jcgriff2_\dbug\__Kernel__\120512-11796-01.dmp]
    Windows 8 Kernel Version 9200 MP (12 procs) Free x64
    Built by: 9200.16442.amd64fre.win8_gdr.121023-1503
    System Uptime:0 days 0:33:31.527
    *** WARNING: Unable to verify timestamp for Xeno7x64.sys
    *** ERROR: Module load completed but symbols could not be loaded for Xeno7x64.sys
    Probably caused by :Xeno7x64.sys ( Xeno7x64+12230 )
    BugCheck 133, {0, 281, 280, 0}
    BugCheck Info: DPC_WATCHDOG_VIOLATION (133)
    Arguments: 
    Arg1: 0000000000000000, A single DPC or ISR exceeded its time allotment. The offending
        component can usually be identified with a stack trace.
    Arg2: 0000000000000281, The DPC time count (in ticks).
    Arg3: 0000000000000280, The DPC time allotment (in ticks).
    Arg4: 0000000000000000
    BUGCHECK_STR:  0x133
    DEFAULT_BUCKET_ID:  WIN8_DRIVER_FAULT
    PROCESS_NAME: System
    FAILURE_BUCKET_ID: 0x133_DPC_Xeno7x64+12230
    CPUID:        "Intel(R) Core(TM) i7 CPU       X 980  @ 3.33GHz"
    MaxSpeed:     3330
    CurrentSpeed: 3575
     
    Processor may be overclocked!
    Expected Frequency:   3330
    Actual Frequency:     3575
    Overclock Ratio:      1.07357
     
      BIOS Version                  F4d
      BIOS Release Date             12/12/2011
      Manufacturer                  Gigabyte Technology Co., Ltd.
      Product Name                  G1.Guerrilla
    ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии``
    **************************Wed Dec  5 20:57:57.912 2012 (UTC - 5:00)**************************
    Loading Dump File [C:\Users\John\_jcgriff2_\dbug\__Kernel__\120512-17765-01.dmp]
    Windows 8 Kernel Version 9200 MP (12 procs) Free x64
    Built by: 9200.16442.amd64fre.win8_gdr.121023-1503
    System Uptime:0 days 7:45:32.524
    *** WARNING: Unable to verify timestamp for Xeno7x64.sys
    *** ERROR: Module load completed but symbols could not be loaded for Xeno7x64.sys
    Probably caused by :Xeno7x64.sys ( Xeno7x64+12230 )
    BugCheck 133, {0, 281, 280, 0}
    BugCheck Info: DPC_WATCHDOG_VIOLATION (133)
    Arguments: 
    Arg1: 0000000000000000, A single DPC or ISR exceeded its time allotment. The offending
        component can usually be identified with a stack trace.
    Arg2: 0000000000000281, The DPC time count (in ticks).
    Arg3: 0000000000000280, The DPC time allotment (in ticks).
    Arg4: 0000000000000000
    BUGCHECK_STR:  0x133
    DEFAULT_BUCKET_ID:  WIN8_DRIVER_FAULT
    PROCESS_NAME: System
    FAILURE_BUCKET_ID: 0x133_DPC_Xeno7x64+12230
    CPUID:        "Intel(R) Core(TM) i7 CPU       X 980  @ 3.33GHz"
    MaxSpeed:     3330
    CurrentSpeed: 3575
     
    Processor may be overclocked!
    Expected Frequency:   3330
    Actual Frequency:     3575
    Overclock Ratio:      1.07357
     
      BIOS Version                  F4d
      BIOS Release Date             12/12/2011
      Manufacturer                  Gigabyte Technology Co., Ltd.
      Product Name                  G1.Guerrilla
    ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии``
    **************************Wed Dec  5 13:11:08.903 2012 (UTC - 5:00)**************************
    Loading Dump File [C:\Users\John\_jcgriff2_\dbug\__Kernel__\120512-21421-01.dmp]
    Windows 8 Kernel Version 9200 MP (12 procs) Free x64
    Built by: 9200.16442.amd64fre.win8_gdr.121023-1503
    System Uptime:2 days 20:43:43.515
    *** WARNING: Unable to verify timestamp for Xeno7x64.sys
    *** ERROR: Module load completed but symbols could not be loaded for Xeno7x64.sys
    Probably caused by :Xeno7x64.sys ( Xeno7x64+12230 )
    BugCheck 133, {0, 281, 280, 0}
    BugCheck Info: DPC_WATCHDOG_VIOLATION (133)
    Arguments: 
    Arg1: 0000000000000000, A single DPC or ISR exceeded its time allotment. The offending
        component can usually be identified with a stack trace.
    Arg2: 0000000000000281, The DPC time count (in ticks).
    Arg3: 0000000000000280, The DPC time allotment (in ticks).
    Arg4: 0000000000000000
    BUGCHECK_STR:  0x133
    DEFAULT_BUCKET_ID:  WIN8_DRIVER_FAULT
    PROCESS_NAME: System
    FAILURE_BUCKET_ID: 0x133_DPC_Xeno7x64+12230
    CPUID:        "Intel(R) Core(TM) i7 CPU       X 980  @ 3.33GHz"
    MaxSpeed:     3330
    CurrentSpeed: 3575
     
    Processor may be overclocked!
    Expected Frequency:   3330
    Actual Frequency:     3575
    Overclock Ratio:      1.07357
     
      BIOS Version                  F4d
      BIOS Release Date             12/12/2011
      Manufacturer                  Gigabyte Technology Co., Ltd.
      Product Name                  G1.Guerrilla
    ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии``
    
    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:
    **************************Thu Dec 20 10:06:58.904 2012 (UTC - 5:00)**************************
    WRfiltv.sys                 Thu Jul 30 23:40:32 2009 (4A7267B0)
    Edge7x64.sys                Wed May 18 18:55:15 2011 (4DD44E53)
    Xeno7x64.sys                Wed May 18 18:55:16 2011 (4DD44E54)
    nusb3hub.sys                Mon Oct 24 20:57:37 2011 (4EA60981)
    nusb3xhc.sys                Mon Oct 24 20:57:38 2011 (4EA60982)
    NEOFLTR_710_20169.SYS       Fri Jan 13 06:46:40 2012 (4F1019A0)
    ctxusbm.sys                 Fri Feb  3 09:36:13 2012 (4F2BF0DD)
    GEARAspiWDM.sys             Thu May  3 15:56:17 2012 (4FA2E2E1)
    nvhda64v.sys                Tue Jul  3 11:25:04 2012 (4FF30ED0)
    dump_storahci.sys           Wed Jul 25 22:30:35 2012 (5010ABCB)
    aswrdr2.sys                 Mon Oct  8 04:23:43 2012 (50728D8F)
    aswFsBlk.SYS                Tue Oct 30 18:43:04 2012 (509057F8)
    aswMonFlt.sys               Tue Oct 30 18:43:09 2012 (509057FD)
    aswSP.SYS                   Tue Oct 30 18:44:06 2012 (50905836)
    aswSnx.SYS                  Tue Oct 30 18:44:08 2012 (50905838)
    aswnet.sys                  Sun Nov  4 05:12:57 2012 (50963FA9)
    intelppm.sys                Mon Nov  5 22:55:02 2012 (50988A16)
    nvlddmkm.sys                Fri Nov 30 22:24:02 2012 (50B97852)
    nvstusb.sys                 Fri Nov 30 23:19:35 2012 (50B98557)
    ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии``
    **************************Mon Dec 17 01:29:59.909 2012 (UTC - 5:00)**************************
    intelppm.sys                Wed Jul 25 22:26:48 2012 (5010AAE8)
    ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии``
    **************************Sun Dec  9 12:56:10.603 2012 (UTC - 5:00)**************************
    emupia2k.sys                Thu Aug 11 06:03:39 2011 (4E43A8FB)
    ctsfm2k.sys                 Thu Aug 11 06:03:48 2011 (4E43A904)
    ctoss2k.sys                 Thu Aug 11 06:04:05 2011 (4E43A915)
    ha20x22k.sys                Thu Aug 11 06:07:26 2011 (4E43A9DE)
    ctaud2k.sys                 Thu Aug 11 06:08:16 2011 (4E43AA10)
    ctprxy2k.sys                Thu Aug 11 06:08:19 2011 (4E43AA13)
    CTEXFIFX.SYS                Thu Aug 11 06:09:50 2011 (4E43AA6E)
    CT20XUT.SYS                 Thu Aug 11 06:09:58 2011 (4E43AA76)
    CTHWIUT.SYS                 Thu Aug 11 06:10:02 2011 (4E43AA7A)
    ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии``
    **************************Wed Dec  5 13:11:08.903 2012 (UTC - 5:00)**************************
    nvlddmkm.sys                Sun Nov 18 06:10:12 2012 (50A8C214)
    nvstusb.sys                 Sun Nov 18 06:37:26 2012 (50A8C876)
    
    WRfiltv.sys - this driver hasn't been added to the DRT as of this run. Please search Google/Bing for the driver if additional information is needed.
    http://www.carrona.org/drivers/driver.php?id=Edge7x64.sys
    http://www.carrona.org/drivers/driver.php?id=Xeno7x64.sys
    http://www.carrona.org/drivers/driver.php?id=nusb3hub.sys
    http://www.carrona.org/drivers/driver.php?id=nusb3xhc.sys
    NEOFLTR_710_20169.SYS - this driver hasn't been added to the DRT as of this run. Please search Google/Bing for the driver if additional information is needed.
    http://www.carrona.org/drivers/driver.php?id=ctxusbm.sys
    http://www.carrona.org/drivers/driver.php?id=GEARAspiWDM.sys
    http://www.carrona.org/drivers/driver.php?id=nvhda64v.sys
    http://www.carrona.org/drivers/driver.php?id=dump_storahci.sys
    http://www.carrona.org/drivers/driver.php?id=aswrdr2.sys
    http://www.carrona.org/drivers/driver.php?id=aswFsBlk.SYS
    http://www.carrona.org/drivers/driver.php?id=aswMonFlt.sys
    http://www.carrona.org/drivers/driver.php?id=aswSP.SYS
    http://www.carrona.org/drivers/driver.php?id=aswSnx.SYS
    aswnet.sys - this driver hasn't been added to the DRT as of this run. Please search Google/Bing for the driver if additional information is needed.
    http://www.carrona.org/drivers/driver.php?id=intelppm.sys
    http://www.carrona.org/drivers/driver.php?id=nvlddmkm.sys
    http://www.carrona.org/drivers/driver.php?id=nvstusb.sys
    http://www.carrona.org/drivers/driver.php?id=intelppm.sys
    http://www.carrona.org/drivers/driver.php?id=emupia2k.sys
    http://www.carrona.org/drivers/driver.php?id=ctsfm2k.sys
    http://www.carrona.org/drivers/driver.php?id=ctoss2k.sys
    http://www.carrona.org/drivers/driver.php?id=ha20x22k.sys
    http://www.carrona.org/drivers/driver.php?id=ctaud2k.sys
    http://www.carrona.org/drivers/driver.php?id=ctprxy2k.sys
    http://www.carrona.org/drivers/driver.php?id=CTEXFIFX.SYS
    http://www.carrona.org/drivers/driver.php?id=CT20XUT.SYS
    http://www.carrona.org/drivers/driver.php?id=CTHWIUT.SYS
    http://www.carrona.org/drivers/driver.php?id=nvlddmkm.sys
    http://www.carrona.org/drivers/driver.php?id=nvstusb.sys
      My System SpecsSystem Spec

  3. #3


    Posts : 3
    Windows 8 Pro


    Thanks for the help so far, usasma. I did remove the overclock temporarily and BSOD occurred again. I researched the Xeno7x64.sys file a bit and it looks like Bigfoot only tweaked their Windows 7 driver to work on Windows 8, but it doesn't appear to have been written for it. I have filed a support ticket with them to see if they have a new driver in development. I was able to find and install updated USB3 drivers without problem. I'm hopeful that Creative will provide a full Windows 8 driver for my SoundBlaster devices this week or the next. Finally, I actually did purchase a new SSD (Samsung 840 PRO), which is Windows 8 certified, so I'll be installing that over the next few days. I'll report back if I get any updates from Bigfoot or if the BSOD stops with the installation of the new SSD.
      My System SpecsSystem Spec

  4. #4


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


    Be sure that your storage controller drivers are dated from 2012. Earlier drivers and SSD's dont' get along very well.

    When the last problems surfaced with Bigfoot cards (a year or two ago), the problems stopped appearing rather rapidly. So I suspect that the driver writers at Bigfoot will be on it very soon.

    Good luck!
      My System SpecsSystem Spec

  5. #5


    Posts : 3
    Windows 8 Pro


    Just to give an update on this, I did replace my old SSD with a Samsung 840 Pro SSD. In the process I did a clean install of Windows 8 Pro. The Watchdog violations still occur (though maybe just a hair less frequently) to the point where I'm just about 100% positive that it is the embedded Killer NIC causing the issue. I did put a support ticket in with them that was never responded to, so I have pretty much lost all faith in their company. Supposedly someone did a live chat with them and confirmed they are working on a new Win8 native driver, but who knows when/if that will, in fact, surface.
      My System SpecsSystem Spec

  6. #6


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


    I'd suggest a new, run of the mill NIC card that has Win8 drivers available.
    It's always nice to have one on hand "just in case"
    Good luck!
      My System SpecsSystem Spec

  7. #7


    Redmond
    Posts : 651
    Windows 8.1 x64


    I've posted about these sorts of crashes before, and after looking at your data I would agree with usasma's findings - it does look like this is caused by the Xeno7x64 driver:
    Code:
    9: kd> .bugcheck
    Bugcheck code 00000133
    Arguments 00000000`00000000 00000000`00000281 00000000`00000280 00000000`00000000
    
    9: kd> k
    Child-SP          RetAddr           Call Site
    fffff880`02bb1808 fffff800`df3df143 nt!KeBugCheckEx
    fffff880`02bb1810 fffff800`df2b1011 nt! ?? ::FNODOBFM::`string'+0x13c4c
    fffff880`02bb1890 fffff800`df976e94 nt!KeUpdateRunTime+0x51
    fffff880`02bb18c0 fffff800`df27f7ee hal!HalpTimerClockInterrupt+0x50
    fffff880`02bb18f0 fffff800`df2755c3 nt!KiInterruptDispatchLBControl+0x1ce
    fffff880`02bb1a80 fffff880`03a12230 nt!KxWaitForSpinLockAndAcquire+0x23
    fffff880`02bb1ab0 fffff880`02b8af00 Xeno7x64+0x12230
    fffff880`02bb1ab8 0000001c`ed9e9167 0xfffff880`02b8af00
    fffff880`02bb1ac0 fffff880`02b88180 0x0000001c`ed9e9167
    fffff880`02bb1ac8 fffff800`df49cb80 0xfffff880`02b88180
    fffff880`02bb1ad0 00000000`00000000 nt!EtwpGroupMasks
    
    9: kd> lmvm Xeno7x64
    start             end                 module name
    fffff880`03a00000 fffff880`03a29000   Xeno7x64 T (no symbols)           
        Loaded symbol image file: Xeno7x64.sys
        Image path: \SystemRoot\System32\drivers\Xeno7x64.sys
        Image name: Xeno7x64.sys
        Timestamp:        Wed May 18 18:55:16 2011 (4DD44E54)
        CheckSum:         0002E73E
        ImageSize:        00029000
        Translations:     0000.04b0 0000.04e4 0409.04b0 0409.04e4
    Usually when I see this stack with a network driver on it, there's another thread somewhere that's waiting on this thread and they're deadlocked - eventually this will "time out" and trigger the DPC watchdog. Because these are minidumps, I can't confirm this is happening (you can't see any data but what was on the crashing thread at the time of the dump, and this machine has multiple CPUs (thus multiple threads could be running at the time of the crash). However, I have seen this exact stack before, and it was a driver deadlock issue waiting on itself (basically), so it would definitely behoove you to try a different NIC (and uninstall the driver for this one, and disable it in BIOS (if it's onboard) or remove it (if it's an adapter card) as well.
      My System SpecsSystem Spec

Intermittent DPC Watchdog Violation BSODs occurring
Related Threads
Dpc Watchdog Violation (133) in BSOD Crashes and Debugging
Hi, I have a problem. But I do not know english. I uploaded the dump file. Thanks for help.
Hi guys, recently my computer has been crashing multiple times with BSOD errors, quite a few of them are different to each other. Here is a couple of BSODs I've noted down, although I guess they'll be in the dump files: - BAD_POOL_HEADER - IRQL_NOT_LESS_OR_EQUAL - nvlddmkm.sys (pretty sure it...
DPC WatchDog Violation in BSOD Crashes and Debugging
I have Samsung NP-RV515 A01-US. I upgraded to 128gb ssd. I got dpc watchdog violation for the first time today after runing updates. Uninstalling doesn't help. Upon boot every time after 60 seconds. No luck. I know there are threads here about this but not my exact issue. After running...
Please help me out, DPC watchdog violation. in BSOD Crashes and Debugging
I am getting DPC watchdog violation issue when i turned on my laptop today...I dont know what to do now, please help me out.:cry:
So, I recently installed Sid Meier's Pirates on my new laptop. Unfortunately, the game has frozen three times so far during action sequences, causing DPC Watchdog Violations and a restart of the computer. I was wondering if anyone could glean something from the error files that would help my...
DPC Watchdog Violation in BSOD Crashes and Debugging
Hello, I recently refreshed Windows 8 have been running into "Watchdog" reboots. My guess is that it is something network related. I am using a Linksys wmp54g adapter, which hasn't been supported by Linksys for a couple of years. The funny thing is that I never had this issue with my...
DPC Watchdog Violation BSOD need help :( in BSOD Crashes and Debugging
Hello ! , I've just changed few components in my PC , re installed Windows and I'm getting this BSOD , can't figure out what it is , sometimes my PC will restart 4-5 times in the row before i can get few hours of use from it. I changed only my CPU and Motherboard all the rest is the same and I've...
Eight Forums Android App Eight Forums IOS App Follow us on Facebook