Windows 10: 0x00000133 - DPC_WATCHDOG_VIOLATION 133 - WARNING: Unable to verify timestamp for nvlddmkm.sys

Discus and support 0x00000133 - DPC_WATCHDOG_VIOLATION 133 - WARNING: Unable to verify timestamp for nvlddmkm.sys in Windows 10 Software and Apps to solve the problem; Hi, Dear Moderators!Me need your help.My PC has a BSOD every day, error 0x00000133 - DPC_WATCHDOG_VIOLATION 133 - WARNING: Unable to verify timestamp... Discussion in 'Windows 10 Software and Apps' started by Артур Вартанян, Mar 28, 2022.

  1. 0x00000133 - DPC_WATCHDOG_VIOLATION 133 - WARNING: Unable to verify timestamp for nvlddmkm.sys


    Hi, Dear Moderators!Me need your help.My PC has a BSOD every day, error 0x00000133 - DPC_WATCHDOG_VIOLATION 133 - WARNING: Unable to verify timestamp for nvlddmkm.sys.I changed the CPU, RAM, GPU, Motherboard, power supply.And I just don't know what else to check. Can it be in the software?I am attaching a link to the memory dumps.https://1drv.ms/u/s!AtLHUKWxYGEoiCzXcZjDJppc138s?e=PTLt0cI ran stress tests, no errors. It appears during normal PC usage Discord,Notepad++,DataGrip 2020.1 x64,Microsoft OfficeI would really appreciate any help, thanks!

    :)
     
    Артур Вартанян, Mar 28, 2022
    #1

  2. Blue screen when ever i connect to wifi

    Only 3 files are useful remaining were of 0 bytes.

    A. Analysis Results

    File Name: 052519-28921-01.dmp

    DRIVER_IRQL_NOT_LESS_OR_EQUAL (d1)

    DEFAULT_BUCKET_ID: WIN8_DRIVER_FAULT

    IMAGE_NAME: storahci.sys

    File Name: 052519-34484-01.dmp

    DPC_WATCHDOG_VIOLATION (133)

    *** WARNING: Unable to verify timestamp for avgStm.sys

    DEFAULT_BUCKET_ID: WIN8_DRIVER_FAULT

    IMAGE_NAME: avgStm.sys

    *** WARNING: Unable to verify timestamp for klwfp.sys

    *** WARNING: Unable to verify timestamp for kneps.sys

    *** WARNING: Unable to verify timestamp for klim6.sys

    *** WARNING: Unable to verify timestamp for bcmwl63a.sys

    File Name: 052519-36390-01.dmp

    DPC_WATCHDOG_VIOLATION (133)

    DEFAULT_BUCKET_ID: WIN8_DRIVER_FAULT

    IMAGE_NAME: tcpip.sys

    *** WARNING: Unable to verify timestamp for klflt.sys

    *** WARNING: Unable to verify timestamp for avgStm.sys

    *** WARNING: Unable to verify timestamp for klwfp.sys

    *** WARNING: Unable to verify timestamp for kneps.sys

    B. Recommendations

    1. Create a system restore point so that if something wrong happens you can revert.

    Type restore point in Cortana Search > Create a Restore point > Check whether against your drive, Protection is ON or not. If not ON, click Configure button below to Make it ON > Now press Create to create a restore point

    2. Uninstall AVG and Kaspersky.
     
    Vijay_Verma, Mar 28, 2022
    #2
  3. dpc_watchdog_violation

    Hi JesseAK

    Greetings! I am Vijay, an Independent Advisor. I am here to work with you on this problem.

    A. Analysis Results

    File Name: 042319-6953-01.dmp

    DPC_WATCHDOG_VIOLATION (133)

    DEFAULT_BUCKET_ID: WIN8_DRIVER_FAULT

    IMAGE_NAME: ntkrnlmp.exe

    *** WARNING: Unable to verify timestamp for netfilter21573.sys

    File Name: 042319-5359-01.dmp

    DPC_WATCHDOG_VIOLATION (133)

    DEFAULT_BUCKET_ID: WIN8_DRIVER_FAULT

    IMAGE_NAME: ntkrnlmp.exe

    B. Third Party Drivers

    netfilter21573.sys - ???

    Driver date - Wed Aug 29 23:50:30 2018

    C. Recommendations

    1. Create a system restore point so that if something wrong happens you can revert.

    Type restore point in Cortana Search > Create a Restore point > Check whether against your drive, Protection is ON or not. If not ON, click Configure button below to Make it ON > Now press Create to create a restore point

    2. Udpate netfilter21573.sys

    Do let me know if you require any further help on this. Will be glad to help you.
     
    Vijay_Verma, Mar 28, 2022
    #3
  4. axe0 Win User

    0x00000133 - DPC_WATCHDOG_VIOLATION 133 - WARNING: Unable to verify timestamp for nvlddmkm.sys

    Dpc_watchdog_violation


    Hi darthtony,

    Welcome to the 10forums 0x00000133 - DPC_WATCHDOG_VIOLATION 133 - WARNING: Unable to verify timestamp for nvlddmkm.sys :)

    Your Logitech Webcam 300 is causing the crashes, please make sure to update the drivers.
    Driver Reference Table - lvuvc64.sys
    Code:
    Code:
    *******************************************************************************  *                                                                             *  *                        Bugcheck Analysis                                    *  *                                                                             *  *******************************************************************************    Use !analyze -v to get detailed debugging information.    BugCheck 133, {1, 1e00, 0, 0}    *** WARNING: Unable to verify timestamp for lvuvc64.sys  *** ERROR: Module load completed but symbols could not be loaded for lvuvc64.sys  *** WARNING: Unable to verify checksum for win32k.sys  Probably caused by : lvuvc64.sys ( lvuvc64+5aca8 )    Followup:     MachineOwner    2: kd> lmvm lvuvc64  Browse full module list  start             end                 module name  fffff801`1d5f0000 fffff801`1da77d80   lvuvc64  T (no symbols)                 Loaded symbol image file: lvuvc64.sys      Image path: \SystemRoot\system32\DRIVERS\lvuvc64.sys      Image name: lvuvc64.sys      Browse all global symbols  functions  data      Timestamp:        Tue Oct 23 04:12:08 2012 (5085FCF8)      CheckSum:         004912C7      ImageSize:        00487D80      Translations:     0000.04b0 0000.04e4 0409.04b0 0409.04e4
    EDIT: it seems the AVG activity monitor driver is being flagged too in 2/3 dumps, worth mentioning thus.
    I would suggest that you temporary remove AVG and use Windows Defender as alternative.
    In the link below, go to part C and download the uninstaller to ensure AVG is proper removed.
    Uninstall AVG software | AVG
    Code:
    Code:
    ffffd000`22a62980  fffff801`90ed2050Unable to load image \SystemRoot\system32\DRIVERS\avgidsdrivera.sys, Win32 error 0n2  *** WARNING: Unable to verify timestamp for avgidsdrivera.sys  *** ERROR: Module load completed but symbols could not be loaded for avgidsdrivera.sys   avgidsdrivera+0x42050
     
Thema:

0x00000133 - DPC_WATCHDOG_VIOLATION 133 - WARNING: Unable to verify timestamp for nvlddmkm.sys

Loading...
  1. 0x00000133 - DPC_WATCHDOG_VIOLATION 133 - WARNING: Unable to verify timestamp for nvlddmkm.sys - Similar Threads - 0x00000133 DPC_WATCHDOG_VIOLATION 133

  2. 0x00000133 - DPC_WATCHDOG_VIOLATION 133 - WARNING: Unable to verify timestamp for nvlddmkm.sys

    in Windows 10 Gaming
    0x00000133 - DPC_WATCHDOG_VIOLATION 133 - WARNING: Unable to verify timestamp for nvlddmkm.sys: Hi, Dear Moderators!Me need your help.My PC has a BSOD every day, error 0x00000133 - DPC_WATCHDOG_VIOLATION 133 - WARNING: Unable to verify timestamp for nvlddmkm.sys.I changed the CPU, RAM, GPU, Motherboard, power unit, Windows reinstalled.And I just don't know what else to...
  3. 0x00000133 - DPC_WATCHDOG_VIOLATION 133 - WARNING: Unable to verify timestamp for nvlddmkm.sys

    in Windows 10 BSOD Crashes and Debugging
    0x00000133 - DPC_WATCHDOG_VIOLATION 133 - WARNING: Unable to verify timestamp for nvlddmkm.sys: Hi, Dear Moderators!Me need your help.My PC has a BSOD every day, error 0x00000133 - DPC_WATCHDOG_VIOLATION 133 - WARNING: Unable to verify timestamp for nvlddmkm.sys.I changed the CPU, RAM, GPU, Motherboard, power supply.And I just don't know what else to check. Can it be in...
  4. WARNING: Unable to verify timestamp for win32k.sys

    in Windows 10 Gaming
    WARNING: Unable to verify timestamp for win32k.sys: Microsoft R Windows Debugger Version 10.0.21306.1007 AMD64Copyright c Microsoft Corporation. All rights reserved.Loading Dump File [D:\Desktop\\031022-19218-01.dmp]Mini Kernel Dump File: Only registers and stack trace are availableSymbol search path is: srv*Executable search...
  5. WARNING: Unable to verify timestamp for win32k.sys

    in Windows 10 Software and Apps
    WARNING: Unable to verify timestamp for win32k.sys: Microsoft R Windows Debugger Version 10.0.21306.1007 AMD64Copyright c Microsoft Corporation. All rights reserved.Loading Dump File [D:\Desktop\\031022-19218-01.dmp]Mini Kernel Dump File: Only registers and stack trace are availableSymbol search path is: srv*Executable search...
  6. WARNING: Unable to verify timestamp for win32k.sys

    in Windows 10 Drivers and Hardware
    WARNING: Unable to verify timestamp for win32k.sys: Microsoft R Windows Debugger Version 10.0.21306.1007 AMD64Copyright c Microsoft Corporation. All rights reserved.Loading Dump File [D:\Desktop\\031022-19218-01.dmp]Mini Kernel Dump File: Only registers and stack trace are availableSymbol search path is: srv*Executable search...
  7. Blue Screen error - WARNING: Unable to verify timestamp for Ntfs.sy

    in Windows 10 Gaming
    Blue Screen error - WARNING: Unable to verify timestamp for Ntfs.sy: Microsoft R Windows Debugger Version 10.0.22000.194 AMD64 Copyright c Microsoft Corporation. All rights reserved. Loading Dump File [G:\APA\Minidump\Mini082721-01.dmp] Mini Kernel Dump File: Only registers and stack trace are available Symbol search path is: srv* Executable...
  8. Blue Screen error - WARNING: Unable to verify timestamp for Ntfs.sy

    in Windows 10 Software and Apps
    Blue Screen error - WARNING: Unable to verify timestamp for Ntfs.sy: Microsoft R Windows Debugger Version 10.0.22000.194 AMD64 Copyright c Microsoft Corporation. All rights reserved. Loading Dump File [G:\APA\Minidump\Mini082721-01.dmp] Mini Kernel Dump File: Only registers and stack trace are available Symbol search path is: srv* Executable...
  9. WARNING: Unable to verify timestamp for win32k.sys

    in Windows 10 Drivers and Hardware
    WARNING: Unable to verify timestamp for win32k.sys: I have been getting BSODs recently after I replaced mobo, GPU, NVME, cooling system and PSU.I have done MEMtest all good no error. Ran DriverVerifier to stress test third party driver with no issues.Below are bugcheck analysis:DRIVER_OVERRAN_STACK_BUFFER f7 A driver has...
  10. BSOD - Unknown Cause - WARNING: Unable to verify timestamp for win32k.sys

    in Windows 10 BSOD Crashes and Debugging
    BSOD - Unknown Cause - WARNING: Unable to verify timestamp for win32k.sys: Hi all, I need your help, I have been plagued the past few days with intermittent bluescreens. I have tried to diagnose the issue myself, putting the .dmp files through WinDbg, following countless forum suggestions to no avail. I have a few dump files, one of which pointed...