BSOD DPC_WATCHDOG_VIOLATION hal.ddl ntoskrnl.exe

Page 3 of 3 FirstFirst 123

  1. philc43
    Posts : 5,169
    64bit Win 10 Pro ver 21H2
       New #21

    These latest dumps show that the same DPC bugcheck is occurring (0x133 with first parameter =1). Using the kernel memory dump we can look at the DPCs on the processor as follows:

    Code:
    0: kd> !dpcs 0
CPU Type      KDPC       Function
 0: Normal  : 0xffffed0245a4f000 0xfffff80335139220 nt!PopExecuteProcessorCallback
 0: Normal  : 0xffffed0245ca7000 0xfffff80335139220 nt!PopExecuteProcessorCallback
 0: Normal  : 0xffff9b8b1b9ddc38 0xfffff80df9b82ea0 HDAudBus!HdaController::CodecDpc
 0: Normal  : 0xffff9b8b1a3cdc40 0xfffff80df4c179a0 ndis!ndisPeriodicReceivesTimer
 0: Normal  : 0xfffff803342bdf90 0xfffff803350f5210 nt!PpmPerfAction
 0: Normal  : 0xffff9b8b1a5e30c8 0xfffff80df4e32450 tcpip!TcpPeriodicTimeoutHandler
 0: Threaded: 0xfffff803342be0d8 0xfffff8033519a160 nt!KiDpcWatchdog
    The audio driver shows up again but also a network driver, these ones are MS and are usually not the problem.

    The 3rd party network driver is rt640x64.sys - it is already the newest on your MB website so all I can suggest is trying an older one.

    I have tried extracting a trace of the DPC durations using the Kernel logger data in the dump but unfortunately it reports that time inversion has occurred and the Windows Performance Analyser will not load it. This is not something I've experienced before but @cwsink may have some ideas on how to proceed.
      My Computers
    Quote Quote

  3. romanbomba
    Posts : 14
    Windows 10 update 1809
    Thread Starter
       New #22

    but still you can not rule out hardware damage (graphics card)?

    I have 3 new dmp files. According to these recent bugs, the nvidia driver also causes bluescreen?

    *******************************************************************************
    * *
    * Bugcheck Analysis *
    * *
    *******************************************************************************

    DPC_WATCHDOG_VIOLATION (133)
    The DPC watchdog detected a prolonged run time at an IRQL of DISPATCH_LEVEL
    or above.
    Arguments:
    Arg1: 0000000000000001, The system cumulatively spent an extended period of time at
    DISPATCH_LEVEL or above. The offending component can usually be
    identified with a stack trace.
    Arg2: 0000000000001e00, The watchdog period.
    Arg3: fffff8024ba6e378
    Arg4: 0000000000000000

    Debugging Details:
    ------------------

    TRIAGER: Could not open triage file : e:\dump_analysis\program\triage\modclass.ini, error 2

    DEFAULT_BUCKET_ID: WIN8_DRIVER_FAULT

    BUGCHECK_STR: 0x133

    PROCESS_NAME: System

    CURRENT_IRQL: d

    LAST_CONTROL_TRANSFER: from fffff8024b7e9063 to fffff8024b7a8650

    STACK_TEXT:
    fffff802`4da6cbc8 fffff802`4b7e9063 : 00000000`00000133 00000000`00000001 00000000`00001e00 fffff802`4ba6e378 : nt!KeBugCheckEx
    fffff802`4da6cbd0 fffff802`4b672d5a : 0000072f`80bc0e66 fffff802`4a7f9180 00000000`00000282 00000000`00000000 : nt!KeAccumulateTicks+0x1743a3
    fffff802`4da6cc30 fffff802`4bf7951b : 0000072f`80bbedca 00000000`0000b101 00000000`00000000 fffff802`4bfd8bb0 : nt!KeClockInterruptNotify+0x9da
    fffff802`4da6cf40 fffff802`4b6c9195 : fffff802`4bfd8bb0 00000000`00000001 00000000`00000001 fffff802`4b7a9eab : hal!HalpTimerClockIpiRoutine+0x1b
    fffff802`4da6cf70 fffff802`4b7aa0ea : fffff802`4da5c4e0 fffff802`4bfd8bb0 00000000`00000020 ffffba01`e8cb0140 : nt!KiCallInterruptServiceRoutine+0xa5
    fffff802`4da6cfb0 fffff802`4b7aa6d7 : 00000000`00000018 fffff802`4da5c600 ffffba01`e9d33000 fffff80b`9aea1730 : nt!KiInterruptSubDispatchNoLockNoEtw+0xea
    fffff802`4da5c460 fffff80b`9a7f0962 : 00000000`00000000 ffffba01`e9c52000 00000000`00000000 ffffba01`e8cb0140 : nt!KiInterruptDispatchNoLockNoEtw+0x37
    fffff802`4da5c5f0 00000000`00000000 : ffffba01`e9c52000 00000000`00000000 ffffba01`e8cb0140 ffffba01`e9c52000 : nvlddmkm+0x2f0962


    STACK_COMMAND: kb

    FOLLOWUP_IP:
    nvlddmkm+2f0962
    fffff80b`9a7f0962 488b4f08 mov rcx,qword ptr [rdi+8]

    SYMBOL_STACK_INDEX: 7

    SYMBOL_NAME: nvlddmkm+2f0962

    FOLLOWUP_NAME: MachineOwner

    MODULE_NAME: nvlddmkm

    IMAGE_NAME: nvlddmkm.sys

    DEBUG_FLR_IMAGE_TIMESTAMP: 5c25d39f

    FAILURE_BUCKET_ID: X64_0x133_nvlddmkm+2f0962

    BUCKET_ID: X64_0x133_nvlddmkm+2f0962

    Followup: MachineOwner
    ---------
      My Computer
    Quote Quote

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

    1) For any BSOD please post:

    a) BETA log collector zip
    BSOD - Posting Instructions - Windows 10 Forums
    https://www.tenforums.com/dl/dm_log_collector.exe
    (extract all > open)

    b) memory.dmp if file size is < 1.5 GB


    2) Run Memtest86 version 8.0 for 8 or more passes.
    MemTest86 - Official Site of the x86 Memory Testing Tool
    MemTest86 - Official Site of the x86 Memory Testing Tool
    Testing is not done by time but by passes.
    The more the passes the better the testing conditions.
    Testing must be continuous.
    A substantial portion of the testing can be performed overnight.
    The computer has 16 GB RAM with two 8 GB modules.
    Testing time is approximately 1 - 2 hours /GB RAM.
    Just one error is a test fail and testing can be aborted.
    Then test one RAM module at a time in the same DIMM for 8 or more passes to differentiate good from malfunctioning RAM

    Memory problems. - Microsoft Community
    MemTest86+ - Test RAM | Tutorials

    3) For each RAM test please use a camera or smartphone camera to take pictures of the results and post images into the thread.

    4) In addition to posting images, Memtest86 version 8 has text files. Please zip the text file and post a share link into the thread using one drive, drop box, or google drive.



    5) The latest memory dump debugging displayed two recurrent drivers in the crash.

    nvlddmkm.sys
    rt640x64.sys


    Code:
    Nazwa	[00000001] Realtek PCIe GBE Family Controller
Typ karty	Ethernet 802.3
Typ produktu	Realtek PCIe GBE Family Controller
Zainstalowane	Tak
Identyfikator urządzenia PNP	PCI\VEN_10EC&DEV_8168&SUBSYS_86771043&REV_15\4&188A02D0&0&00E7
Ostatnie resetowanie	09.01.2019 13:43
Indeks	1
Nazwa usługi	rt640x64
Adres IP	192.168.0.128, fe80::21f3:151f:ac6:df02
Podsieć IP	255.255.255.0, 64
Domyślna brama IP	192.168.0.1
Włączony protokół DHCP	Tak
Serwer DHCP	192.168.0.1
Dzierżawa DHCP wygasa	02.01.1970 02:40
Dzierżawa DHCP uzyskana	01.01.1970 02:40
Adres MAC	‪10:7B:44:4A:5C:FD‬
Port We/Wy	0x0000D000-0x0000D0FF
Adres pamięci	0xF7104000-0xF7104FFF
Adres pamięci	0xF7100000-0xF7103FFF
Kanał IRQ	IRQ 4294967293
Sterownik	c:\windows\system32\drivers\rt640x64.sys (10.23.1003.2017, 986,96 KB (1 010 648 bajtów), 08.01.2019 02:59)
    Code:
    rt640x64	Realtek RT640 NT Driver	c:\windows\system32\drivers\rt640x64.sys	Kernel Driver	Tak	Manual	Running	OK	Normal	Nie	Tak
    Code:
    Nazwa	NVIDIA GeForce RTX 2080
Identyfikator urządzenia PNP	PCI\VEN_10DE&DEV_1E87&SUBSYS_37261462&REV_A1\4&38AB2860&0&0008
Typ karty	GeForce RTX 2080, NVIDIA zgodne
Opis karty	NVIDIA GeForce RTX 2080
Pamięć RAM karty	(1*048*576) bajtów
Zainstalowane sterowniki	C:\Windows\System32\DriverStore\FileRepository\nv_dispi.inf_amd64_2dab3aec607621ff\nvldumdx.dll,C:\Windows\System32\DriverStore\FileRepository\nv_dispi.inf_amd64_2dab3aec607621ff\nvldumdx.dll,C:\Windows\System32\DriverStore\FileRepository\nv_dispi.inf_amd64_2dab3aec607621ff\nvldumdx.dll,C:\Windows\System32\DriverStore\FileRepository\nv_dispi.inf_amd64_2dab3aec607621ff\nvldumdx.dll
Wersja sterownika	25.21.14.1758
Plik INF	oem2.inf (sekcja Section002)
Płaszczyzny kolorów	Niedostępne
Pozycje tabeli kolorów	4294967296
Rozdzielczość	3440 x 1440 x 100 Hz
Bitów/piksel	32
Adres pamięci	0xF6000000-0xF70FFFFF
Adres pamięci	0xE0000000-0xF20FFFFF
Adres pamięci	0xF0000000-0xF1FFFFFF
Port We/Wy	0x0000E000-0x0000EFFF
Kanał IRQ	IRQ 16
Port We/Wy	0x000003B0-0x000003BB
Port We/Wy	0x000003C0-0x000003DF
Adres pamięci	0xA0000-0xBFFFF
Sterownik	c:\windows\system32\driverstore\filerepository\nv_dispi.inf_amd64_2dab3aec607621ff\nvlddmkm.sys (25.21.14.1758, 19,48 MB (20*425*424 bajtów), 08.01.2019 19:28)
    Code:
    nvlddmkm	nvlddmkm	c:\windows\system32\driverstore\filerepository\nv_dispi.inf_amd64_2dab3aec607621ff\nvlddmkm.sys	Kernel Driver	Tak	Manual	Running	OK	Ignore	Nie	Tak
    Code:
    nvlddmkm.sys Thu Dec 27 23:41:19 2018 (5C25D39F)
    Code:
    rt640x64.sys Tue Oct  3 01:31:47 2017 (59D34AF3)
    Last edited by zbook; 09 Jan 2019 at 10:49.
      My Computer
    Quote Quote

  6. romanbomba
    Posts : 14
    Windows 10 update 1809
    Thread Starter
       New #24

    New MEMORY.dmp
    link:
    MEMORY.DMP - Google Drive

    log in the attachment
      My Computer
    Quote Quote

  7. zbook
    Posts : 41,472
    windows 10 professional version 1607 build 14393.969 64 bit
       New #25

    There are two log collectors: DM and BETA.
    The BETA log collector at some time will replace the DM log collector.
    The BETA log collector collects more useful files and folders.
    In post #15 the BETA log collector was posted.
    In post #23 and #24 the DM log collector was posted.
    Please use the link for BETA log collector and post it for any BSOD.
      My Computer
    Quote Quote

  8. romanbomba
    Posts : 14
    Windows 10 update 1809
    Thread Starter
       New #26

    ok, done
      My Computer
    Quote Quote

  9. zbook
    Posts : 41,472
    windows 10 professional version 1607 build 14393.969 64 bit
       New #27

    The event logs are in a foreign language and cannot be scanned or read.
    Whenever possible please use English as the default language during the troubleshooting.
    Add, Remove, and Change Display Language in Windows 10 | Tutorials
      My Computer
    Quote Quote

  10. cwsink
    Posts : 261
    Windows 10 Home 21H2
       New #28

    Hi romanbomba,

    I think a newer driver exists for your Ethernet adapter which can be found here. I think the RTL111 drivers are the same - the last letters of the filename designating a language though I'm not sure. You'll need to provide an email address and a link to the file will be sent to that email address.

    I'm not sure the network driver is the problem but it's worth a try.
      My Computer
    Quote Quote

  12. romanbomba
    Posts : 14
    Windows 10 update 1809
    Thread Starter
       New #29

    I found the cause of problems - my motherboard is damaged (problem with dualchannel)
    Thanks to everyone for help
      My Computer
    Quote Quote

  13. zbook
    Posts : 41,472
    windows 10 professional version 1607 build 14393.969 64 bit
       New #30

    When available please post the results of the RAM and motherboard testing.

    Nice to see it sorted.

    You are welcome.
      My Computer
    Quote Quote

 

  Related Discussions
Bsod - dpc_watchdog_violation (133)
in BSOD Crashes and Debugging

Hi guys, This is Lenovo ideapad 320 laptop Winver 2004 that keep crashing with the DPC Watchdog Violation 133. I ran the Windbg with Anlyze-v and came up with the following error codes which by googling rtwlane seems to be the Realtek 8821AE...
I got this brand new gaming computer. Acer Nitro 5 right after summer. It worked for a good while but now it's getting BSODs with the error code DPC_WATCHDOG_VIOLATION. recently I got Bluescreen Viewer, and it told me the two files hal.dll +...
Bsod dpc_watchdog_violation
in BSOD Crashes and Debugging

Hello I get a Blue screen of death error maybe once or twice a day, it is labeled as DPC_WATCHDOG_VIOLATION. I've ran some minidump file analyzers and one said it was my razer mouse software, so I updated it, restarted the computer, and got the BSOD...
Hi. I've researched and attempted as much as I could possibly try, and now have to ask for community assistance. I never had these BSODs until updating to Windows 10. My crash dump files show two regular culprits (majority are the first one): ...
BSOD DPC_Watchdog_Violation
in BSOD Crashes and Debugging

Dear Sir/Madame, I have received a few messages since upgrading to Windows 10 saying my computer needed to restart and that I could find the answer at DPC Watchdog Violation. I have not had this happen while I am using the computer but the message...
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 17:55.
Find Us




Windows 10 Forums