Windows 8 and 8.1 Forums


DPC_WATCHDOG_VIOLATION in Windows 8, network card related

  1. #1


    Posts : 4
    Windows 8 64-bit

    DPC_WATCHDOG_VIOLATION in Windows 8, network card related


    Hello.

    I am running Windows 8, 64 bit, fully updated. I have been experiencing DPC_WATCHDOG_VIOLATION BSODs at random intervals. My own analysis points to Xeno7x64.sys, which is related to the driver for my built-in Bigfoot Killer NIC 2100. I have reinstalled the most up to date drivers on this card twice now. I also did not get the BSOD before a somewhat recent Windows 8 update.

    I am overclocking currently, but I have put things at factory default and still gotten the error.

    I am unsure if there is anything I can do besides buy a new NIC or downgrade to Windows 7, as I never got the error there (overclocking or not). I am 99% sure the problem lies in the fact the drivers are not well written.

    I'd like any help that I can get at this point. Thank you.

      My System SpecsSystem Spec

  2. #2


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


    Did you install the drivers from here: Killer Gaming :: Support :: Driver Downloads

    I'm unable to get any info from the uploaded .zip file (but I can get info from other zip files on this forum).
    Please re-run the data collection app and let it run for 15 minutes.

    This is the second issue I've seen with the Killer cards recently - and I'd suggest that you disable the onboard Killer card and try another card in order to rule it out. It's always good to have a spare card on hand (in case something happens to the onboard one) - and they're relatively cheap to purchase (about $15 US the last time I checked) at most major retailers.

    Good luck!
      My System SpecsSystem Spec

  3. #3


    Posts : 4
    Windows 8 64-bit


    That is the source of my drivers, and I have followed those directions to install them.

    I had just reinstalled the drivers after making this post, and I initialized Driver Verifier. I got a BSOD very fast and it pointed at the aforementioned file, Xeno7x64.sys.

    I'm not sure why the zip is unreadable, but I'll upload a newly updated one in this post.

    Thank you.
      My System SpecsSystem Spec

  4. #4


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


    This zip file worked for me - I got 7 memory dumps from it along with the other reports that I use.
    Frankly, I suspect that your diagnosis of the Killer card is correct - so my suggestions are meant to increase the stability of the system (and, hopefully, stop the BSOD's). But it's just a guess as we're not able to see any direct relationship between the different problem programs that I've pointed out.

    You have 5 hard drives - what is the make/model/wattage and age of your Power Supply?

    Lot's of missing info in the WER section of MSINFO32. I suspect that this was due to an upgrade install of Win8 on/about 10 Dec 2012. Is that the case?

    The WER section of MSINFO32 does show 7 memory dumps blaming Xeno7x64.sys (as do the memory dumps)

    MSI Afterburner (along with Riva Tuner and EVGA Precision) is known to cause BSOD's on some Win7 systems - I suspect that the same will be true w/Win8. Please uninstall it.
    Please leave the overclock off until we've fixed the BSOD's.

    Death Adder mouse drivers date from 2007 - and they were a known cause of BSOD's in Win7 systems. I've seen other Win8 topics that have BSOD issues with these drivers also.

    Please update your NEC Electronics USB 3.0 drivers. The 2010 version (which you have) was also known to cause BSOD's on Win7 systems - so we suspect the same for Win8.

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

    THIS ONE MUST GO:
    Afc.sys Wed Jul 12 01:48:20 2006 (44B48D24)
    Arcsoft(R) ASPI Shell (CD/DVD program)
    Driver Reference Table - Afc.sys

    THIS ONE MUST GO:
    ElbyCDFL.sys Thu Dec 14 16:22:27 2006 (4581C093)
    ElbyCDIO Filter Driver
    Driver Reference Table - ElbyCDFL.sys

    dadder.sys Thu Aug 2 05:33:03 2007 (46B1A4CF)
    DeathAdder Mouse driver
    Driver Reference Table - dadder.sys

    THIS ONE MUST GO:
    ElbyCDIO.sys Tue Feb 17 12:11:23 2009 (499AEFBB)
    CDRTools/ElbyCDIO/DVD Region Killer/VirtualCloneDrive (elby CloneDVD™ 2)/AnyDVD
    Driver Reference Table - ElbyCDIO.sys

    cpuz132_x64.sys Thu Mar 26 19:17:23 2009 (49CC0D03)
    CPU-Z
    Driver Reference Table - cpuz132_x64.sys

    nusb3hub.sys Thu Nov 18 20:34:24 2010 (4CE5D420)
    NEC Electronics USB 3.0 Host Controller Driver (previous BSOD issues with 2010 version)
    Driver Reference Table - nusb3hub.sys

    nusb3xhc.sys Thu Nov 18 20:34:25 2010 (4CE5D421)
    NEC Electronics USB 3.0 Host Controller Driver (previous BSOD issues with 2010 version)
    Driver Reference Table - nusb3xhc.sys

    nvhda64v.sys Tue May 10 05:41:18 2011 (4DC9083E)
    nVidia HDMI Audio Device (nForce chipset driver)
    Driver Reference Table - nvhda64v.sys

    Edge7x64.sys Wed May 18 18:55:15 2011 (4DD44E53)
    Bigfoot Networks Killer Xeno NDIS-EDGE Miniport Driver (this card is from VisionTek)
    Driver Reference Table - 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)
    Driver Reference Table - Xeno7x64.sys

    ALSysIO64.sys Sat Jul 9 20:27:45 2011 (4E18F201)
    Core Temp - CPU temperature monitor
    Driver Reference Table - ALSysIO64.sys

    RTCore64.sys Tue Sep 6 08:24:50 2011 (4E661112)
    RivaTuner/EVGA Precision/MSI Afterburner (known BSOD issues w/Win7)
    Driver Reference Table - RTCore64.sys

    hcwD1cap.sys Wed Dec 28 10:58:30 2011 (4EFB3CA6)
    Hauppauge Colossus Capture Driver
    Driver Reference Table - hcwD1cap.sys

    hcwD1xcm.sys Wed Dec 28 10:59:43 2011 (4EFB3CEF)
    Hauppauge Colossus XCode Driver
    Driver Reference Table - hcwD1xcm.sys

    hcwD1xcd.sys Wed Dec 28 10:59:47 2011 (4EFB3CF3)
    Hauppauge Colossus XCode Driver
    Driver Reference Table - hcwD1xcd.sys



    BSOD BUGCHECK SUMMARY
    **************************Sat Dec 22 04:58:26.384 2012 (UTC - 5:00)**************************
    Loading Dump File [C:\Users\John\_jcgriff2_\dbug\__Kernel__\122212-27393-01.dmp]
    Windows 8 Kernel Version 9200 MP (8 procs) Free x64
    Built by: 9200.16461.amd64fre.win8_gdr.121119-1606
    System Uptime: 0 days 1:48:02.029
    *** 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, 283, 282, 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: 0000000000000283, The DPC time count (in ticks).
    Arg3: 0000000000000282, 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 920 @ 2.67GHz"
    MaxSpeed: 2670
    CurrentSpeed: 3200

    Processor may be overclocked!
    Expected Frequency: 2670
    Actual Frequency: 3200
    Overclock Ratio: 1.1985

    BIOS Version F3
    BIOS Release Date 04/29/2011
    Manufacturer Gigabyte Technology Co., Ltd.
    Product Name G1.Guerrilla
    จจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจ``
    **************************Fri Dec 21 20:25:34.386 2012 (UTC - 5:00)**************************
    Loading Dump File [C:\Users\John\_jcgriff2_\dbug\__Kernel__\122212-24039-01.dmp]
    Windows 8 Kernel Version 9200 MP (8 procs) Free x64
    Built by: 9200.16461.amd64fre.win8_gdr.121119-1606
    System Uptime: 0 days 8:00:10.031
    *** 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, 283, 282, 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: 0000000000000283, The DPC time count (in ticks).
    Arg3: 0000000000000282, 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 920 @ 2.67GHz"
    MaxSpeed: 2670
    CurrentSpeed: 3200

    Processor may be overclocked!
    Expected Frequency: 2670
    Actual Frequency: 3200
    Overclock Ratio: 1.1985

    BIOS Version F3
    BIOS Release Date 04/29/2011
    Manufacturer Gigabyte Technology Co., Ltd.
    Product Name G1.Guerrilla
    จจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจ``
    **************************Fri Dec 21 12:07:37.877 2012 (UTC - 5:00)**************************
    Loading Dump File [C:\Users\John\_jcgriff2_\dbug\__Kernel__\122112-20233-01.dmp]
    Windows 8 Kernel Version 9200 MP (8 procs) Free x64
    Built by: 9200.16424.amd64fre.win8_gdr.120926-1855
    System Uptime: 0 days 3:16:41.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, 283, 282, 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: 0000000000000283, The DPC time count (in ticks).
    Arg3: 0000000000000282, 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 920 @ 2.67GHz"
    MaxSpeed: 2670
    CurrentSpeed: 3200

    Processor may be overclocked!
    Expected Frequency: 2670
    Actual Frequency: 3200
    Overclock Ratio: 1.1985

    BIOS Version F3
    BIOS Release Date 04/29/2011
    Manufacturer Gigabyte Technology Co., Ltd.
    Product Name G1.Guerrilla
    จจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจ``
    **************************Thu Dec 20 13:01:48.883 2012 (UTC - 5:00)**************************
    Loading Dump File [C:\Users\John\_jcgriff2_\dbug\__Kernel__\122012-18907-01.dmp]
    Windows 8 Kernel Version 9200 MP (8 procs) Free x64
    Built by: 9200.16424.amd64fre.win8_gdr.120926-1855
    System Uptime: 1 days 7:02:25.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, 283, 282, 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: 0000000000000283, The DPC time count (in ticks).
    Arg3: 0000000000000282, 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 920 @ 2.67GHz"
    MaxSpeed: 2670
    CurrentSpeed: 3200

    Processor may be overclocked!
    Expected Frequency: 2670
    Actual Frequency: 3200
    Overclock Ratio: 1.1985

    BIOS Version F3
    BIOS Release Date 04/29/2011
    Manufacturer Gigabyte Technology Co., Ltd.
    Product Name G1.Guerrilla
    จจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจ``
    **************************Mon Dec 17 16:54:41.873 2012 (UTC - 5:00)**************************
    Loading Dump File [C:\Users\John\_jcgriff2_\dbug\__Kernel__\121712-22292-01.dmp]
    Windows 8 Kernel Version 9200 MP (8 procs) Free x64
    Built by: 9200.16424.amd64fre.win8_gdr.120926-1855
    System Uptime: 0 days 8:25:42.522
    *** 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, 283, 282, 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: 0000000000000283, The DPC time count (in ticks).
    Arg3: 0000000000000282, 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 920 @ 2.67GHz"
    MaxSpeed: 2670
    CurrentSpeed: 3200

    Processor may be overclocked!
    Expected Frequency: 2670
    Actual Frequency: 3200
    Overclock Ratio: 1.1985

    BIOS Version F3
    BIOS Release Date 04/29/2011
    Manufacturer Gigabyte Technology Co., Ltd.
    Product Name G1.Guerrilla
    จจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจ``
    **************************Wed Dec 12 00:38:35.506 2012 (UTC - 5:00)**************************
    Loading Dump File [C:\Users\John\_jcgriff2_\dbug\__Kernel__\121212-24913-01.dmp]
    Windows 8 Kernel Version 9200 MP (8 procs) Free x64
    Built by: 9200.16384.amd64fre.win8_rtm.120725-1247
    System Uptime: 0 days 0:02:14.149
    Probably caused by : ntkrnlmp.exe ( nt!KxMcheckAbort+7b )
    BugCheck 9C, {0, fffff88000fbcad0, 0, 0}
    BugCheck Info: MACHINE_CHECK_EXCEPTION (9c)
    Arguments:
    Arg1: 0000000000000000
    Arg2: fffff88000fbcad0
    Arg3: 0000000000000000
    Arg4: 0000000000000000
    BUGCHECK_STR: 0x9C_GenuineIntel
    PROCESS_NAME: System
    FAILURE_BUCKET_ID: 0x9C_GenuineIntel_nt!KxMcheckAbort
    จจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจ``
      My System SpecsSystem Spec

  5. #5


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


    Not the same as your issue but similar enough to ask - can you try an ATI video card to see if that helps?
    N40L - DPC_WATCHDOG_VIOLATION
      My System SpecsSystem Spec

  6. #6


    Posts : 4
    Windows 8 64-bit


    My power supply is 850W, less than a year old. KINGWIN and 80+ rated, which I believe is more than enough to power my rig. You are correct with the Windows 8 upgrade assessment.

    I've followed the advice you've given me on uninstalling and removing the various programs, though they haven't caused me any BSODs on 7 or 8. Still, it can't hurt to get rid of old programs and update drivers.

    I do have an ATI card. I will wait and see if my system crashes again after having followed what you suggested, then try that. I have already ordered a NIC that was rated to be compatible with Windows 8, so I will also see if that changes the issue once I get it.

    Thank you for your thorough and quick help, as well. I do hope this solves the issue.
      My System SpecsSystem Spec

  7. #7


    Posts : 4
    Windows 8 64-bit


    Update on this --

    I've replaced my NIC with one that was rated to be compatible with Windows 8, and disabled and uninstalled by Bigfoot one. The problem has entirely ceased.
      My System SpecsSystem Spec

  8. #8


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


    I'm glad to hear it. Thanks for letting us know!
      My System SpecsSystem Spec

DPC_WATCHDOG_VIOLATION in Windows 8, network card related
Related Threads
I did a clean install of Windows 8.1 recently. Now when my computer wakes up from sleep I receive a DRIVER_IRQ_NOT LESS_OR_EQUAL BSOD related to cmudaxp.sys, which I've discovered is related to my Asus Xonar Essence STX sound card. I am running the Windows 8.1 beta drivers directly from Asus's...
BSOD related with my graphic card in BSOD Crashes and Debugging
Good night :) I'm having a trouble with my computer. As you can see with my system specs, I have a graphic card nVidia GeForce GTX 750, which has worked properly in some cases but in others something strange is happening. Recently I was playing FIFA 14 and suddenly a BSOD pop up, with a...
HI all i got this twice today BSOD Nvidia Geforce GTX 660Ti Driver (C:windows\system32\drivers\nvlddmkm.sys) Appears to have caused a system crash. Bug check code 0x00000116 Driver c:\windows\system32\drivers\nvlddmkm.sys Not sure what i can do i uninstalled reinstalled nothing helped i then...
Random BSOD - possible video card related? in BSOD Crashes and Debugging
**Please ignore or remove this thread, I uploaded the wrong file and am at work, so cannot upload again** Sorry for the inconveniance..will update later. Hello all, first time, long time. I keep getting errors of the BSOD variety lately, and i have not changed anything of interest. The...
Hi I hope im in the correct forum. Lets just say someone was looking at something they shouldnt of been looking at online and now my game lags. The lag isn't network related its because my cpu is peaking out and it didnt before the above mentioned event. The game will lag, I will hit w key and my...
I have a Kingston USB3 multi card reader that was working fine with Windows 7. After upgrading to Windows 8 on Sunday i now find that the SD card slot works fine, but the CF slot wont ready my CF Card, it just sits there flashing away. Now the strange bit. I took the card reader and connected it...
Strange boot problems (related to video card?) in BSOD Crashes and Debugging
Hello everybody, Yesterday I installed windows 8 on my 4 year old Acer Aspire 5920G laptop (still runs many recent games decently), dual booted with Vista (OEM) and W7. W8 was installed succesfully and it worked as it should, but when I let the system do a performance rating the screen went...
Eight Forums Android App Eight Forums IOS App Follow us on Facebook