DPC_WATCHDOG_VIOLATION (133) by athw10x.sys

Page 2 of 2 FirstFirst 12

  1. Posts : 8
    windows 10
    Thread Starter
       #11

    philc43 said:
    Hello bigbrian123

    The latest crash still indicates the network driver:

    DPC Watchdog Captures Analysis for CPU #0.
    DPC Watchdog capture size: 108 stacks.
    Number of unique stacks: 1.
    No common functions detected!

    The captured stacks seem to indicate that only a single DPC or generic function is the culprit.
    Try to analyse what other processors were doing at the time of the following reference capture:
    CPU #0 DPC Watchdog Reference Stack (#0 of 108) - Profiling started at time since boot: 500 Min 52 Sec 843.75 mSec
    # RetAddr Call Site
    00 fffff8018421643a nt!KeClockInterruptNotify+0x453
    01 fffff801842de055 nt!HalpTimerClockIpiRoutine+0x1A
    02 fffff801843f8d4a nt!KiCallInterruptServiceRoutine+0xA5
    03 fffff801843f92b7 nt!KiInterruptSubDispatchNoLockNoEtw+0xFA
    04 fffff80182048ab2 nt!KiInterruptDispatchNoLockNoEtw+0x37
    05 fffff8018205ad8b storport!RaidUnitCompleteRequest+0xD2
    06 fffff8018429a24e storport!RaidpAdapterRedirectDpcRoutine+0x8B
    07 fffff80184299534 nt!KiExecuteAllDpcs+0x30E
    08 fffff801843fe2e5 nt!KiRetireDpcList+0x1F4
    09 fffff801843fe0d0 nt!KxRetireDpcList+0x5
    0a fffff801843fd985 nt!KiDispatchInterruptContinue
    0b fffff801843f8e11 nt!KiDpcInterruptBypass+0x25
    0c fffff801839e9ad9 nt!KiInterruptDispatch+0xB1
    Unable to load image \SystemRoot\System32\drivers\athw10x.sys, Win32 error 0n2
    *** WARNING: Unable to verify timestamp for athw10x.sys
    0d fffff801839e99c2 athw10x+0xC9AD9
    0e fffff801839bf1c0 athw10x+0xC99C2
    0f fffff801839be120 athw10x+0x9F1C0
    10 fffff801839bfd10 athw10x+0x9E120
    11 fffff80183a1967b athw10x+0x9FD10
    12 fffff80183aab1d9 athw10x+0xF967B
    13 fffff80183a816a0 athw10x+0x18B1D9
    14 fffff80183b869ca athw10x+0x1616A0
    15 fffff80183b8cd4e athw10x+0x2669CA
    16 fffff80183bbbb93 athw10x+0x26CD4E
    17 fffff80182529ec1 athw10x+0x29BB93
    18 fffff80184274825 ndis!ndisDispatchIoWorkItem+0x11
    19 fffff801842b8515 nt!IopProcessWorkItem+0x135
    1a fffff80184355855 nt!ExpWorkerThread+0x105
    1b fffff801843fe8f8 nt!PspSystemThreadStartup+0x55
    1c ---------------- nt!KiStartSystemThread+0x28


    You could try rolling back the driver to an earlier state, or contacting the manufacturer for advice.
    Alright, I just rolled back my driver into earliest version. I hope this BSOD won't come again.
      My Computer


  2. Posts : 41,472
    windows 10 professional version 1607 build 14393.969 64 bit
       #12

    In addition to the BSOD troubleshooting consider addressing other problems seen in the logs:

    a) test the drive (there were reports of bad blocks)

    b) run the ESET uninstall tool:
    Download ESET AV Remover | ESET


    If you cannot find a stable Qualcom driver then plan to use a USB device for wifi.
      My Computer


  3. Posts : 8
    windows 10
    Thread Starter
       #13

    zbook said:
    In addition to the BSOD troubleshooting consider addressing other problems seen in the logs:

    a) test the drive (there were reports of bad blocks)

    b) run the ESET uninstall tool:
    Download ESET AV Remover | ESET


    If you cannot find a stable Qualcom driver then plan to use a USB device for wifi.
    Thank you, but how do I test the driver?
    Is there any software / commands to run the test?
      My Computer


  4. Posts : 41,472
    windows 10 professional version 1607 build 14393.969 64 bit
       #14

    Drivers can be tested by using Windows driver verifier.

    It's important that you test the disk drives.

    Please post results into this thread.
      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 01:29.
Find Us




Windows 10 Forums