BSOD Since Win10 1809 update, 0x133(1) DPC Watchdog Violation

Page 11 of 12 FirstFirst ... 9101112 LastLast

  1. Posts : 61
    Windows 10 Home v1809 (17763.475)
    Thread Starter
       #101

    If you mean fast startup (in power options), yes I disabled that a long time ago, I did that the first time I tried 1809 back in October and had issues. I checked to see if the setting has stuck now I'm on 1903, and it has.
      My ComputerSystem Spec

  2.    #102

    Disabling Fast startup would prevent the computer from hibernating when told to shutdown through the physical power button and menus but it could still go through a sleep/wake cycle from closing the lid or if the Power Options are set to sleep after a period of inactivity. It might be worth a try if you hadn't also changed those settings.
      My ComputerSystem Spec


  3. Posts : 61
    Windows 10 Home v1809 (17763.475)
    Thread Starter
       #103

    I've had a few bugchecks from an idle screen on a fresh boot, with no sleep/wake cycles.
    Here's another dump for good measure, ckcl running and paging exec still disabled.
    MEMORY15.zip - Google Drive
    BSOD Since Win10 1809 update, 0x133(1) DPC Watchdog Violation Attached Files
      My ComputerSystem Spec


  4. Posts : 26,088
    windows 10 professional version 1607 build 14393.969 64 bit
       #104

    1) Check the motherboard manual and view the motherboard.


    2) Different driver versions have caused recurrent BSOD.

    3) Are you able or unable to remove Intel wireless hardware?

    4) Are you able or unable to use only Eternet or cat5e internet connection?

    5) Are you able or unable to use only a USB wireless?





    Code:
    Netwbw02.sys Mon Sep  3 05:14:07 2018 (5B8D096F)
    Code:
    NETwNb64     Intel(R) Wireless Adap Intel(R) Wireless Adap Kernel        Manual     Running    OK         TRUE        FALSE        749,568           2,179,072   0          03/09/2018 11:14:07    C:\WINDOWS\system32\drivers\Netwbw02.sys         4,096
    Code:
    Name	[00000002] Intel(R) Dual Band Wireless-AC 3160
    Adapter Type	Ethernet 802.3
    Product Type	Intel(R) Dual Band Wireless-AC 3160
    Installed	Yes
    PNP Device ID	PCI\VEN_8086&DEV_08B3&SUBSYS_81708086&REV_CB\E4F89CFFFF508B7E00
    Last Reset	19/06/2019 20:31
    Index	2
    Service Name	NETwNb64
    IP Address	169.254.55.221, fe80::3417:1c50:fa1:37dd, fdaa:bbcc:ddee:0:89:6687:6aa2:e7ea, 2a00:23c6:a10f:3a00:89:6687:6aa2:e7ea, fdaa:bbcc:ddee:0:3417:1c50:fa1:37dd, 2a00:23c6:a10f:3a00:3417:1c50:fa1:37dd
    IP Subnet	255.255.0.0, 64, 128, 128, 64, 64
    Default IP Gateway	fe80::a608:f5ff:fe67:b249
    DHCP Enabled	Yes
    DHCP Server	255.255.255.255
    DHCP Lease Expires	31/10/1932 09:35
    DHCP Lease Obtained	30/10/1932 09:35
    MAC Address	‪E4:F8:9C:50:8B:7E‬
    Memory Address	0xB1100000-0xB1101FFF
    IRQ Channel	IRQ 4294967289
    Driver	C:\WINDOWS\SYSTEM32\DRIVERS\NETWBW02.SYS (18.33.14.3, 3.43 MB (3,595,472 bytes), 12/10/2018 14:25)
      My ComputerSystem Spec


  5. Posts : 61
    Windows 10 Home v1809 (17763.475)
    Thread Starter
       #105

    That's odd, I didn't update that wireless driver, it was on 17.5.0.5 (auto installed after I removed device in dev mgr and rebooted). I have checked and I still have WU driver updates disabled, and I haven't run the Intel DSA. How has it updated itself?
    For information, 18.33.14.3 isn't the latest driver available from Intel. So don't know where that's come from.
      My ComputerSystem Spec


  6. Posts : 26,088
    windows 10 professional version 1607 build 14393.969 64 bit
       #106

    The prior post was updated while you were posting and this may not have been seen:

    1) Check the motherboard manual and view the motherboard.


    2) Different driver versions have caused recurrent BSOD.

    3) Are you able or unable to remove Intel wireless hardware?

    4) Are you able or unable to use only Eternet or cat5e internet connection?

    5) Are you able or unable to use only a USB wireless?
      My ComputerSystem Spec



  7. Posts : 61
    Windows 10 Home v1809 (17763.475)
    Thread Starter
       #107

    It's a laptop with built-in wireless so I'm not able to remove the hardware. Unfortunately I don't have an ethernet port either. I'm not sure I have a USB wifi dongle, but I may be able to get hold of one.
    I have a funny feeling the wifi driver isn't the issue, but rather is falling victim to another driver misbehaving.
    If you add to that the fact that all wifi driver versions I've had run without incident in v1803, plus a growing number of other Toshiba users are reporting similar problems, some with different wireless hardware, I think by process of elimination it's looking like a Toshiba driver problem, apparent in v1809 and above. That's just what it's starting to seem like to me.
      My ComputerSystem Spec


  8. Posts : 26,088
    windows 10 professional version 1607 build 14393.969 64 bit
       #108

    On other computers I'm using windows 1607 and 1709 so you may need to do that while waiting for a Tohiba solution.

    At this time you can:
    a) make a backup image
    b) save the image to another drive or to the cloud
    c) clean install windows 1803
    d) stress test drivers with windows 1803
    e) if stress testing confirms that there are no problems then block windows uprades

    f) alternatively use a USB dongle and uninstall / disable Intel wireless
      My ComputerSystem Spec


  9. Posts : 61
    Windows 10 Home v1809 (17763.475)
    Thread Starter
       #109

    I've just rebooted from a bugcheck, and something is different now, the mouse pointer is jerking really badly, like continuously doing it. What could be causing that? I'm pretty sure if I reboot again it will fix it. It did last time.

    Interestingly, it's only the mouse pointer, the touchscreen is behaving fine.

    Just thought I may be able to look somewhere to see what's interfering with it?
    Last edited by spark001uk; 4 Weeks Ago at 12:36.
      My ComputerSystem Spec

  10.    #110

    I learned from this blog post that since we can get the addresses from the etl trace and the symbols exist in the dump we can actually use the address to find the name of the function being called using the "ln" command in WinDbg. Looking at memory15.dmp shows this:
    Code:
    0: kd> ln 0xFFFFF807814E2AC0
    Browse module
    Set bu breakpoint
    
    (fffff807`814e2ac0)   ACPI!AmliWatchdog   |  (fffff807`814e2b1c)   ACPI!AmliWatchdogInitiateBugcheck
    Exact matches:
    0: kd> ln 0xFFFFF80781488F70
    Browse module
    Set bu breakpoint
    
    (fffff807`81488f70)   ACPI!ACPIInterruptDispatchEventDpc   |  (fffff807`814892ac)   ACPI!ACPIWakeRemoveDevicesAndUpdate
    Exact matches:
        ACPI!ACPIInterruptDispatchEventDpc (void)
    0: kd> ln 0xFFFFF8077C12BCD0
    Browse module
    Set bu breakpoint
    
    (fffff807`7c12bcd0)   nt!KiEntropyDpcRoutine   |  (fffff807`7c12bd30)   nt!KeRestoreExtendedProcessorState
    Exact matches:
    0: kd> ln 0xFFFFF80781488DA0
    Browse module
    Set bu breakpoint
    
    (fffff807`81488da0)   ACPI!ACPIInterruptServiceRoutine   |  (fffff807`81488ef8)   ACPI!CLEAR_PM1_STATUS_BITS
    Exact matches:
        ACPI!ACPIInterruptServiceRoutine (void)
    I believe AmliWatchdogInitiateBugcheck is just a function which gets called to trigger a watchdog bugcheck so not very interesting.

    ACPIWakeRemoveDevicesAndUpdate is interesting because it suggests the system is trying to wake and/or remove devices and update something.

    Perhaps ACPIInterruptServiceRoutine is expecting CLEAR_PM1_STATUS_BITS to be updated but it's not happening. I'm just speculating but it seems plausible. The callstacks all seem to show something waiting on and trying to acquire a spinlock so perhaps it involves those bits.

    I suspect it's a Toshiba ACPI implementation bug (either UEFI/BIOS or driver) which has been exposed by newer versions of Windows 10.
      My ComputerSystem Spec


 
Page 11 of 12 FirstFirst ... 9101112 LastLast

Related Threads
BSOD dpc watchdog violation in BSOD Crashes and Debugging
Hi I am getting this error mentioned in the title... I try a few ways and have not been able to fix it! Can anyone help me?
Solved BSOD DPC Watchdog Violation in BSOD Crashes and Debugging
Hi, I keep getting the bsod and Idk how to fix this. I believe it might be audio related because when I watch youtube the video freezes and plays a buzzing sound but it unfreezes itself. Sometimes it just freezes up completely and gives me a bsod....
BSOD (watchdog violation) in BSOD Crashes and Debugging
I tried most of googles suggestions like turning off fast startup or using driver thats not iaStorA.sys Dont really know what to do at this point. This happens usually while watching youtube at least once/day.. Doesnt happen with others sites...
BSOD DPC Watchdog Violation in BSOD Crashes and Debugging
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...
BSOD DPC Watchdog Violation in BSOD Crashes and Debugging
Hi guys, I hope you can help me. So i had a GTX 1070 that went out on me and while I getting the new one from EVGA I used my old GTX 760. I got the new one today and installed my 1070. I used DDU to make sure I didn't have any conflicting driver...
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 16:44.
Find Us