BSOD DPC Watchdog Violation


  1. Posts : 3
    Windows 10 Pro x64
       #1

    BSOD DPC Watchdog Violation


    Attachment 132590
    I've been getting this DPC Watchdog violation off and on since upgrading to Win 10 Pro. I was previously on Win10 Home, and found out via MS Support for a different issue that my previous Pro license entitled me to Win10 Pro. Since this issue started, I've done a clean install, verified and updated all the drivers I can update, and removed all non-essential hardware. This issue is getting rather annoying, and I've not gotten anything useful from MS. Any ideas and help would be most appreciated, though.
      My Computer

  2. Ztruker's Avatar
    Posts : 13,697
    Windows 10 Pro X64 21H1 19043.1110
       #2

    All thress dumps indicates a problem with athwnx.sys.
    Code:
    BugCheck 133, {0, 501, 500, 0}
    *** WARNING: Unable to verify timestamp for athwnx.sys
    *** ERROR: Module load completed but symbols could not be loaded for athwnx.sys
    Probably caused by : athwnx.sys ( athwnx+c9752 )
    This belongs to your Qualcomm Atheros AR5005G Wireless Network Adapter. Are you using it? You have a Desktop system so I would think you would be using Realtek PCIe GBE Family Controller NIC as it's considerably faster than wireless.

    If you are not using the WiFi, disable the adapter in Device Manager, see if that makes a difference.

    Please fill out your System Specs:

    See here: System Specs - Fill in at Ten Forums

    Of major interest is the Manufacture and full model number of the computer if purchased or the system board if custom built. The more info you provide the better.
      My Computers


  3. Posts : 3
    Windows 10 Pro x64
    Thread Starter
       #3

    Updated my hardware profile. Due to space and restraints on my home network setup, ethernet just isn't an option. I just grabbed an old wireless NIC I had laying in a pile and tossed it in for the time being.
    Oddly enough, this issue wasn't present in Win10 Home, just the Pro edition. Still, I'll see what I can do about that driver. I'll probably just have to pony up for a better NIC, I suppose.
      My Computer

  4. Ztruker's Avatar
    Posts : 13,697
    Windows 10 Pro X64 21H1 19043.1110
       #4

    Definitely try a different wireless nic.

    The driver you are currently using is Timestamped: Tue Mar 01 03:39:03 2016

    There is no difference in the wireless support between home and pro. You are at 14393 which is the Anniversary update from July of last year. You might try updating th the latest 15063 Creators Update. See here: How to get the Windows 10 Creators Update - - Windows 10 Forums
      My Computers


  5. Posts : 3
    Windows 10 Pro x64
    Thread Starter
       #5

    Ztruker said:
    Definitely try a different wireless nic.

    The driver you are currently using is Timestamped: Tue Mar 01 03:39:03 2016

    There is no difference in the wireless support between home and pro. You are at 14393 which is the Anniversary update from July of last year. You might try updating th the latest 15063 Creators Update. See here: How to get the Windows 10 Creators Update - - Windows 10 Forums
    I'm pretty sure I have a USB powered NIC around here somewhere I can try. I'll give the Creator's Update a shot first, and then switch NICs. If one or both fixes the issue, I'll mark as solved by tomorrow morning. Thanks for the rapid, awesomely helpful responses. I got more from you in an hour than 3 with MS Support lol
      My Computer


 

  Related Discussions
Our Sites
Site Links
About Us
Windows 10 Forums is an independent web site and has not been authorized, sponsored, or otherwise approved by Microsoft Corporation. "Windows 10" and related materials are trademarks of Microsoft Corp.

Designer Media Ltd
All times are GMT -5. The time now is 08:18.
Find Us




Windows 10 Forums