Windows 10: Código de Error DPC_WATCHDOG_VIOLATION 133 - 0x133_DPC_nvlddmkm!unknown_function

Discus and support Código de Error DPC_WATCHDOG_VIOLATION 133 - 0x133_DPC_nvlddmkm!unknown_function in Windows 10 BSOD Crashes and Debugging to solve the problem; He tenido este bsod desde que recuerdo haber tenido esta computadora. He tratado de formatearla completamente e incluso re-instalar Windows pero el... Discussion in 'Windows 10 BSOD Crashes and Debugging' started by Jason Vilchez, Feb 2, 2020.

  1. Código de Error DPC_WATCHDOG_VIOLATION 133 - 0x133_DPC_nvlddmkm!unknown_function


    He tenido este bsod desde que recuerdo haber tenido esta computadora. He tratado de formatearla completamente e incluso re-instalar Windows pero el error persistía así que la llevé al servicio técnico de Acer donde le cambiaron el disco duro pero con solo horas de usarla el problema seguía presente y la garantía acaba de expirar. Todos mis drivers están actualizados en este momento.


    Aquí dejo información de mi sistema:


    Fabricante: Acer

    Modelo: Nitro AN515-52

    Procesador: IntelR CoreTM i5-8300H CPU @ 2.30GHz 2.30 GHz

    Memoria instalada RAM: 12.0 GB 11.8 GB utilizable

    Tipo de sistema: Sistema operativo de 64 bits, procesador x64

    :)
     
    Jason Vilchez, Feb 2, 2020
    #1
  2. auggy Win User

    DPC_WATCHDOG_VIOLATION

    The minidump files showed two different errors, a DPC_WATCHDOG_VIOLATION (133) error and a SYSTEM_SERVICE_EXCEPTION (3b) error.

    The DPC_WATCHDOG_VIOLATION may be caused by a wireless driver, the athwnx.sys.

    Which wireless adapter do you have and which driver is installed?

    Also, what ASUS software is installed?
     
    auggy, Feb 2, 2020
    #2
  3. BSoD : DPC_WATCHDOG_VIOLATION (133)

    I am using Win 10 and keep getting a DPC_WATCHDOG_VIOLATION (133) BSoD at random intervals.

    Below is my latest mini dump results, can anyone assist.

    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: fffff80121bf2380, cast to nt!DPC_WATCHDOG_GLOBAL_TRIAGE_BLOCK, which contains

    additional information regarding the cumulative timeout

    Arg4: 0000000000000000

    Debugging Details:

    ------------------

    *************************************************************************

    *** ***

    *** ***

    *** Either you specified an unqualified symbol, or your debugger ***

    *** doesn't have full symbol information. Unqualified symbol ***

    *** resolution is turned off by default. Please either specify a ***

    *** fully qualified symbol module!symbolname, or enable resolution ***

    *** of unqualified symbols by typing ".symopt- 100". Note that ***

    *** enabling unqualified symbol resolution with network symbol ***

    *** server shares in the symbol path may cause the debugger to ***

    *** appear to hang for long periods of time when an incorrect ***

    *** symbol name is typed or the network symbol server is down. ***

    *** ***

    *** For some commands to work properly, your symbol path ***

    *** must point to .pdb files that have full type information. ***

    *** ***

    *** Certain .pdb files (such as the public OS symbols) do not ***

    *** contain the required information. Contact the group that ***

    *** provided you with these symbols if you need this command to ***

    *** work. ***

    *** ***

    *** Type referenced: TickPeriods ***

    *** ***

    *************************************************************************

    KEY_VALUES_STRING: 1

    PROCESSES_ANALYSIS: 1

    SERVICE_ANALYSIS: 1

    STACKHASH_ANALYSIS: 1

    TIMELINE_ANALYSIS: 1

    DUMP_CLASS: 1

    DUMP_QUALIFIER: 400

    BUILD_VERSION_STRING: 17763.1.amd64fre.rs5_release.180914-1434

    SYSTEM_MANUFACTURER: Hewlett-Packard

    SYSTEM_PRODUCT_NAME: HP EliteDesk 800 G1 TWR

    SYSTEM_SKU: C8N27AV

    BIOS_VENDOR: Hewlett-Packard

    BIOS_VERSION: L01 v02.74

    BIOS_DATE: 01/25/2018

    BASEBOARD_MANUFACTURER: Hewlett-Packard

    BASEBOARD_PRODUCT: 18E4

    DUMP_TYPE: 2

    BUGCHECK_P1: 1

    BUGCHECK_P2: 1e00

    BUGCHECK_P3: fffff80121bf2380

    BUGCHECK_P4: 0

    DPC_TIMEOUT_TYPE: DPC_QUEUE_EXECUTION_TIMEOUT_EXCEEDED

    CPU_COUNT: 8

    CPU_MHZ: d40

    CPU_VENDOR: GenuineIntel

    CPU_FAMILY: 6

    CPU_MODEL: 3c

    CPU_STEPPING: 3

    CPU_MICROCODE: 6,3c,3,0 (F,M,S,R) SIG: 24'00000000 (cache) 24'00000000 (init)

    BLACKBOXBSD: 1 (!blackboxbsd)

    BLACKBOXPNP: 1 (!blackboxpnp)

    CUSTOMER_CRASH_COUNT: 1

    DEFAULT_BUCKET_ID: WIN8_DRIVER_FAULT

    BUGCHECK_STR: 0x133

    PROCESS_NAME: OUTLOOK.EXE

    CURRENT_IRQL: d

    ANALYSIS_SESSION_HOST: LAPIN0140

    ANALYSIS_SESSION_TIME: 06-03-2019 15:09:51.0953

    ANALYSIS_VERSION: 10.0.18362.1 amd64fre

    LAST_CONTROL_TRANSFER: from fffff801218dcbc3 to fffff80121863730

    STACK_TEXT:

    fffff801`214ceba8 fffff801`218dcbc3 : 00000000`00000133 00000000`00000001 00000000`00001e00 fffff801`21bf2380 : nt!KeBugCheckEx

    fffff801`214cebb0 fffff801`217948bf : 0006e3d4`051cf7e3 fffff801`1fdae180 00000000`00000286 00000000`022e4dde : nt!KeAccumulateTicks+0x144c93

    fffff801`214cec10 fffff801`2161b47c : 00000000`00000000 fffff801`21680750 fffff503`048b1f50 fffff801`21680800 : nt!KeClockInterruptNotify+0xcf

    fffff801`214cef30 fffff801`217e3195 : fffff801`21680750 fffff801`21864d40 ffffad00`1e2348c8 fffff503`048b1f50 : hal!HalpTimerClockIpiRoutine+0x1c

    fffff801`214cef60 fffff801`2186512a : fffff503`048b1f50 fffff801`21680750 00000000`c1d00000 fffff801`21680750 : nt!KiCallInterruptServiceRoutine+0xa5

    fffff801`214cefb0 fffff801`21865677 : 00000000`00000000 fffff503`048b1f50 ffffad00`1e2348c0 00000000`00000000 : nt!KiInterruptSubDispatchNoLockNoEtw+0xfa

    fffff503`048b1ed0 fffff801`21869c31 : 00000000`00000003 fffff801`218649e1 00000000`00000000 fffff503`048b20f0 : nt!KiInterruptDispatchNoLockNoEtw+0x37

    fffff503`048b2060 fffff801`218649e1 : 00000000`00000000 fffff503`048b20f0 ffffad00`1e2348c0 ffffe08c`3051fda0 : nt!KiDpcInterruptBypass+0x11

    fffff503`048b2070 fffff801`2c00f5f5 : 00000000`00000002 00000000`00000001 00000000`00000003 ffffae07`b64942a8 : nt!KiChainedDispatch+0xb1

    fffff503`048b2200 00000000`00000002 : 00000000`00000001 00000000`00000003 ffffae07`b64942a8 00000000`00000000 : nvlddmkm+0x1bf5f5

    fffff503`048b2208 00000000`00000001 : 00000000`00000003 ffffae07`b64942a8 00000000`00000000 fffff801`2c00f918 : 0x2

    fffff503`048b2210 00000000`00000003 : ffffae07`b64942a8 00000000`00000000 fffff801`2c00f918 fffff503`048b23f0 : 0x1

    fffff503`048b2218 ffffae07`b64942a8 : 00000000`00000000 fffff801`2c00f918 fffff503`048b23f0 ffffe08c`428ca080 : 0x3

    fffff503`048b2220 00000000`00000000 : fffff801`2c00f918 fffff503`048b23f0 ffffe08c`428ca080 00000000`00000000 : 0xffffae07`b64942a8

    THREAD_SHA1_HASH_MOD_FUNC: 936ab3482a43b455fc540bcc4956a7e7f0603158

    THREAD_SHA1_HASH_MOD_FUNC_OFFSET: ce2f9a73874763c8485aecdab5d96458e84039fd

    THREAD_SHA1_HASH_MOD: d0c4326baaecf4e9adb1c8c55d4daee64aa76950

    FOLLOWUP_IP:

    nvlddmkm+1bf5f5

    fffff801`2c00f5f5 488b542438 mov rdx,qword ptr [rsp+38h]

    FAULT_INSTR_CODE: 24548b48

    SYMBOL_STACK_INDEX: 9

    SYMBOL_NAME: nvlddmkm+1bf5f5

    FOLLOWUP_NAME: MachineOwner

    MODULE_NAME: nvlddmkm

    IMAGE_NAME: nvlddmkm.sys

    DEBUG_FLR_IMAGE_TIMESTAMP: 59953bcb

    STACK_COMMAND: .thread ; .cxr ; kb

    BUCKET_ID_FUNC_OFFSET: 1bf5f5

    FAILURE_BUCKET_ID: 0x133_ISR_nvlddmkm!unknown_function

    BUCKET_ID: 0x133_ISR_nvlddmkm!unknown_function

    PRIMARY_PROBLEM_CLASS: 0x133_ISR_nvlddmkm!unknown_function

    TARGET_TIME: 2019-05-24T13:49:15.000Z

    OSBUILD: 17763

    OSSERVICEPACK: 437

    SERVICEPACK_NUMBER: 0

    OS_REVISION: 0

    SUITE_MASK: 272

    PRODUCT_TYPE: 1

    OSPLATFORM_TYPE: x64

    OSNAME: Windows 10

    OSEDITION: Windows 10 WinNt TerminalServer SingleUserTS

    OS_LOCALE:

    USER_LCID: 0

    OSBUILD_TIMESTAMP: 2005-12-02 08:58:59

    BUILDDATESTAMP_STR: 180914-1434

    BUILDLAB_STR: rs5_release

    BUILDOSVER_STR: 10.0.17763.1.amd64fre.rs5_release.180914-1434

    ANALYSIS_SESSION_ELAPSED_TIME: 27a85

    ANALYSIS_SOURCE: KM

    FAILURE_ID_HASH_STRING: km:0x133_isr_nvlddmkm!unknown_function

    FAILURE_ID_HASH: {f97493a5-ea2b-23ca-a808-8602773c2a86}

    Followup: MachineOwner

    ---------
     
    Sachin Kumar Dubey (SACD), Feb 2, 2020
    #3
  4. Rose Cal Win User

    Código de Error DPC_WATCHDOG_VIOLATION 133 - 0x133_DPC_nvlddmkm!unknown_function

    DPC_WATCHDOG_VIOLATION

    Hi,

    It is possible that the error DPC_WATCHDOG_VIOLATION may occur if the iastor.sys driver is incompatible with Windows 10. To isolate your issue, we'd like to gather more information:

    • Have you made any recent changes before this issue occurred?
    • What troubleshooting steps have you done so far?

    Any response will be highly appreciated.
     
    Rose Cal, Feb 2, 2020
    #4
Thema:

Código de Error DPC_WATCHDOG_VIOLATION 133 - 0x133_DPC_nvlddmkm!unknown_function

Loading...
  1. Código de Error DPC_WATCHDOG_VIOLATION 133 - 0x133_DPC_nvlddmkm!unknown_function - Similar Threads - Código Error DPC_WATCHDOG_VIOLATION

  2. Código de parada 0xc000021a no Windows 10

    in Windows 10 BSOD Crashes and Debugging
    Código de parada 0xc000021a no Windows 10: Estava acessando justamente o site da microsoft quando apareceu uma tela azul. Depois de coletada as informações, reiniciei a máquina e estou há dois dias sem conseguir fazer boot com o código 0xc000021a. Já tentei diversos comandos e nenhum funcionou. Não posso formatar pois...
  3. pc frezez sometimes on startup DPC_WATCHDOG_VIOLATION 133

    in Windows 10 BSOD Crashes and Debugging
    pc frezez sometimes on startup DPC_WATCHDOG_VIOLATION 133: here is the link to the drive where all the information is for the stuff https://drive.google.com/open?id=1p_QY7HzqfEyU2T4mrof9MjNxjh1joG9b https://answers.microsoft.com/en-us/windows/forum/all/pc-frezez-sometimes-on-startup/372f9cf4-1aca-4826-9d0e-cdc479721513
  4. DPC_WATCHDOG_VIOLATION (133)

    in Windows 10 BSOD Crashes and Debugging
    DPC_WATCHDOG_VIOLATION (133): Hello, some days ago my computer started crashing with this bluescreen. I tried several things already but didn't find out the issue: - Sometimes it crashes after many hours of usage, today it crashed after a little more than one hour. - Every crash happened when playing...
  5. BSoD : DPC_WATCHDOG_VIOLATION (133)

    in Windows 10 BSOD Crashes and Debugging
    BSoD : DPC_WATCHDOG_VIOLATION (133): I am using Win 10 and keep getting a DPC_WATCHDOG_VIOLATION (133) BSoD at random intervals. Below is my latest mini dump results, can anyone assist. DPC_WATCHDOG_VIOLATION (133) The DPC watchdog detected a prolonged run time at an IRQL of DISPATCH_LEVEL or above....
  6. Error código: 0x80072F8F

    in Microsoft Windows 10 Store
    Error código: 0x80072F8F: Cuando intento descargar cualquier app de la tienda, esta me dice: ocurrió algo inesperado, y me da el código 0x80072F8F ya probé a borrar el cache y restablecer la tienda, también comprobé que la fecha y hora son correctos, así como si de verdad estaba registrada mi cuenta...
  7. How to fix AV_NETwew01!unknown_function. error/crash?

    in Windows 10 BSOD Crashes and Debugging
    How to fix AV_NETwew01!unknown_function. error/crash?: Ever since I built my computer, I get a Bsod out of nowhere. It happens to me all the time and it keeps getting worse. When I check the reliability report, it gives the Bucket id which is AV_NETwew01!unknown_function. Also when I get a Bsod, the screen looks normal or looks...
  8. DPC_WATCHDOG_VIOLATION (133) when closing monitor of laptop

    in Windows 10 BSOD Crashes and Debugging
    DPC_WATCHDOG_VIOLATION (133) when closing monitor of laptop: Dear all, Since yesterday I have trouble with my computer when I close the monitor of my laptop. It is a Lenovo ThinkPad X1 Yoga 2nd. I installed WinDBG and extracted the following information from the memory.dmp file. Any Idea what is the reason for this problem?...
  9. BSOD after 15 min idling (following boot). DPC_WATCHDOG_VIOLATION 133

    in Windows 10 BSOD Crashes and Debugging
    BSOD after 15 min idling (following boot). DPC_WATCHDOG_VIOLATION 133: Hello, So I just bought a brand new HP spectre, installed few softwares like CCleaner, Speccy... And randomly get BSOD 10 or 15 min after booting (btw booting takes some time , about 1min ((for an SSD that's quite long isn't it ?))). I noticed that it can take up to 30 min...
  10. BSOD DPC_WATCHDOG_VIOLATION, error (133) driving me crazy

    in Windows 10 BSOD Crashes and Debugging
    BSOD DPC_WATCHDOG_VIOLATION, error (133) driving me crazy: System Config: GA-970A-UD3 1.1 AMD FX-6100, 16G RAM NVIDIA GeForce GT 610 Patriot Pyro SE 120GB SSD WD 1TB SATA III ST 1TB SATA III I continue to get DPC_WATCHDOG_VIOLATION. I have updated BIOS, MB Drivers (Realtek LAN and Audio) , NVIDIA Drivers. I have disabled...