Windows 10: Can anyone tell me what this WinDbg error means for BSOD "DPC_Watchdog Violation" I get daily?

Discus and support Can anyone tell me what this WinDbg error means for BSOD "DPC_Watchdog Violation" I get daily? in Windows 10 BSOD Crashes and Debugging to solve the problem; I get this error about once a day. I've done the following while troubleshooting: 1 - Updated Nvidia P2000 Graphics card driver Geforce Experience... Discussion in 'Windows 10 BSOD Crashes and Debugging' started by BrianTowll, Jan 11, 2020.

  1. BRIANTOWLL
    BrianTowll Win User

    Can anyone tell me what this WinDbg error means for BSOD "DPC_Watchdog Violation" I get daily?


    I get this error about once a day. I've done the following while troubleshooting:

    1 - Updated Nvidia P2000 Graphics card driver Geforce Experience says up to date

    2 - Updated NIC driver via Motherboard website

    3 - Disabled all audio drivers don't need audio on this system


    Error from WinDbg:




    Microsoft R Windows Debugger Version 10.0.18362.1 AMD64

    Copyright c Microsoft Corporation. All rights reserved.





    Loading Dump File [C:\Windows\MEMORY.DMP]

    Kernel Bitmap Dump File: Kernel address space is available, User address space may not be available.



    Symbol search path is: srv*

    Executable search path is:

    Windows 10 Kernel Version 18362 MP 24 procs Free x64

    Product: WinNt, suite: TerminalServer SingleUserTS

    Built by: 18362.1.amd64fre.19h1_release.190318-1202

    Machine Name:

    Kernel base = 0xfffff806`42400000 PsLoadedModuleList = 0xfffff806`42848130

    Debug session time: Fri Jan 10 23:08:38.379 2020 UTC - 6:00

    System Uptime: 0 days 6:14:42.031

    Loading Kernel Symbols

    ...............................................................

    ................................................................

    ...............................................................

    Loading User Symbols

    PEB is paged out Peb.Ldr = 00000000`020d1018. Type ".hh dbgerr001" for details

    Loading unloaded module list

    ..........

    For analysis of this file, run !analyze -v

    6: kd> !analyze -v

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

    * *

    * Bugcheck Analysis *

    * *

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



    DPC_WATCHDOG_VIOLATION 133

    The DPC watchdog detected a prolonged run time at an IRQL of DISPATCH_LEVEL

    or above.

    Arguments:

    Arg1: 0000000000000000, A single DPC or ISR exceeded its time allotment. The offending

    component can usually be identified with a stack trace.

    Arg2: 0000000000000501, The DPC time count in ticks.

    Arg3: 0000000000000500, The DPC time allotment in ticks.

    Arg4: fffff80642973358, cast to nt!DPC_WATCHDOG_GLOBAL_TRIAGE_BLOCK, which contains

    additional information regarding this single DPC timeout



    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: 401



    BUILD_VERSION_STRING: 18362.1.amd64fre.19h1_release.190318-1202



    SYSTEM_MANUFACTURER: Gigabyte Technology Co., Ltd.



    SYSTEM_PRODUCT_NAME: X570 UD



    SYSTEM_SKU: Default string



    SYSTEM_VERSION: Default string



    BIOS_VENDOR: American Megatrends Inc.



    BIOS_VERSION: F3



    BIOS_DATE: 09/04/2019



    BASEBOARD_MANUFACTURER: Gigabyte Technology Co., Ltd.



    BASEBOARD_PRODUCT: X570 UD



    BASEBOARD_VERSION: x.x



    DUMP_TYPE: 1



    BUGCHECK_P1: 0



    BUGCHECK_P2: 501



    BUGCHECK_P3: 500



    BUGCHECK_P4: fffff80642973358



    DPC_TIMEOUT_TYPE: SINGLE_DPC_TIMEOUT_EXCEEDED



    CPU_COUNT: 18



    CPU_MHZ: ed1



    CPU_VENDOR: AuthenticAMD



    CPU_FAMILY: 17



    CPU_MODEL: 71



    CPU_STEPPING: 0



    DEFAULT_BUCKET_ID: WIN8_DRIVER_FAULT



    BUGCHECK_STR: 0x133



    PROCESS_NAME: Plex Media Server.exe



    CURRENT_IRQL: d



    ANALYSIS_SESSION_HOST: DESKTOP-0LCPO7P



    ANALYSIS_SESSION_TIME: 01-10-2020 23:13:46.0581



    ANALYSIS_VERSION: 10.0.18362.1 amd64fre



    LAST_CONTROL_TRANSFER: from fffff806425eea3d to fffff806425c14e0



    STACK_TEXT:

    ffffce01`0517cb08 fffff806`425eea3d : 00000000`00000133 00000000`00000000 00000000`00000501 00000000`00000500 : nt!KeBugCheckEx

    ffffce01`0517cb10 fffff806`4241f897 : 00004dc2`83b62c31 ffffce01`0515c180 00000000`00000286 ffffe685`fac76840 : nt!KeAccumulateTicks+0x1cbfdd

    ffffce01`0517cb70 fffff806`423601e1 : ffffa887`87b861a0 ffffa887`7dec9b00 ffffe685`fac768c0 ffffa887`7dec9bb0 : nt!KeClockInterruptNotify+0xc07

    ffffce01`0517cf30 fffff806`42402a25 : ffffa887`7dec9b00 00000000`00000000 00000000`00000000 ffff4fd7`01980de4 : hal!HalpTimerClockIpiRoutine+0x21

    ffffce01`0517cf60 fffff806`425c2f7a : ffffe685`fac768c0 ffffa887`7dec9b00 00000000`00000002 00000000`00000000 : nt!KiCallInterruptServiceRoutine+0xa5

    ffffce01`0517cfb0 fffff806`425c34e7 : 3fe30000`0000000a 0020b400`00000000 00000000`0000000a 00000002`0000000a : nt!KiInterruptSubDispatchNoLockNoEtw+0xfa

    ffffe685`fac76840 fffff806`424a2320 : 00000000`00000003 ffffe685`0000000a 00000000`00000000 ffffe685`fac76ad8 : nt!KiInterruptDispatchNoLockNoEtw+0x37

    ffffe685`fac769d0 fffff806`426a808c : ffffce01`0515c180 00000000`00000000 00000000`00001fff ffffe685`fac76b39 : nt!KxWaitForSpinLockAndAcquire+0x30

    ffffe685`fac76a00 fffff806`4261fc7e : ffffa887`87b872f0 00000000`00000002 ffffe685`fac76b39 ffffa887`8973e000 : nt!KiAcquireSpinLockInstrumented+0xb4

    ffffe685`fac76a50 fffff806`4689ecf5 : ffffa887`87b861a0 ffffa887`87b861a0 ffffa887`907d6000 00001fff`03ffbfff : nt!KeAcquireSpinLockRaiseToDpc+0x17ddfe

    ffffe685`fac76a80 fffff806`4689faea : ffffce01`0515c180 ffffa887`8973ef08 ffffa887`81b74350 00000000`00020000 : ndis!ndisQueuedMiniportDpcWorkItem+0x205

    ffffe685`fac76ba0 fffff806`4246ae95 : ffffce01`0515ef80 ffffa887`81b74350 ffffce01`0515c180 00000000`00000000 : ndis!ndisPeriodicReceivesTimer+0xea

    ffffe685`fac76c40 fffff806`4246a4ef : ffffce01`0515c180 798bd233`00000000 00000000`00000002 00000000`00000006 : nt!KiExecuteAllDpcs+0x305

    ffffe685`fac76d80 fffff806`425c8525 : 83484024`5c8b48c3 ffffce01`0515c180 00000000`00000000 00000000`0000007c : nt!KiRetireDpcList+0x1ef

    ffffe685`fac76fb0 fffff806`425c8310 : 00000000`180b8d01 00000000`00000000 00000000`00000000 00000000`00001dd8 : nt!KxRetireDpcList+0x5

    ffffe686`02a76ad0 fffff806`425c79e0 : 00000000`00000000 ffffe686`02a76b80 ffffa887`7dec9b00 00000000`00000001 : nt!KiDispatchInterruptContinue

    ffffe686`02a76b00 00000000`008bb1f1 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiDpcInterrupt+0x2f0

    00000000`180b87d8 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x8bb1f1





    THREAD_SHA1_HASH_MOD_FUNC: 3007274cee77e68fcb723cc089dc33aaa5222513



    THREAD_SHA1_HASH_MOD_FUNC_OFFSET: 1f7ddceeaee54f5d7ac407f4f1c8689a410fc901



    THREAD_SHA1_HASH_MOD: 26a778f0fd03891ad31c905da5c178ca4739a259



    FOLLOWUP_IP:

    ndis!ndisQueuedMiniportDpcWorkItem+205

    fffff806`4689ecf5 488b8b18130000 mov rcx,qword ptr [rbx+1318h]



    FAULT_INSTR_CODE: 188b8b48



    SYMBOL_STACK_INDEX: a



    SYMBOL_NAME: ndis!ndisQueuedMiniportDpcWorkItem+205



    FOLLOWUP_NAME: MachineOwner



    MODULE_NAME: ndis



    IMAGE_NAME: ndis.sys



    DEBUG_FLR_IMAGE_TIMESTAMP: 20136331



    STACK_COMMAND: .thread ; .cxr ; kb



    BUCKET_ID_FUNC_OFFSET: 205



    FAILURE_BUCKET_ID: 0x133_DPC_ndis!ndisQueuedMiniportDpcWorkItem



    BUCKET_ID: 0x133_DPC_ndis!ndisQueuedMiniportDpcWorkItem



    PRIMARY_PROBLEM_CLASS: 0x133_DPC_ndis!ndisQueuedMiniportDpcWorkItem



    TARGET_TIME: 2020-01-11T05:08:38.000Z



    OSBUILD: 18362



    OSSERVICEPACK: 0



    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: 1980-01-11 09:53:20



    BUILDDATESTAMP_STR: 190318-1202



    BUILDLAB_STR: 19h1_release



    BUILDOSVER_STR: 10.0.18362.1.amd64fre.19h1_release.190318-1202



    ANALYSIS_SESSION_ELAPSED_TIME: 3a60



    ANALYSIS_SOURCE: KM



    FAILURE_ID_HASH_STRING: km:0x133_dpc_ndis!ndisqueuedminiportdpcworkitem



    FAILURE_ID_HASH: {94235cf9-4baa-c0d7-f20b-c1d66e3d3670}



    Followup: MachineOwner

    ---------



    6: kd> !analyze -v

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

    * *

    * Bugcheck Analysis *

    * *

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



    DPC_WATCHDOG_VIOLATION 133

    The DPC watchdog detected a prolonged run time at an IRQL of DISPATCH_LEVEL

    or above.

    Arguments:

    Arg1: 0000000000000000, A single DPC or ISR exceeded its time allotment. The offending

    component can usually be identified with a stack trace.

    Arg2: 0000000000000501, The DPC time count in ticks.

    Arg3: 0000000000000500, The DPC time allotment in ticks.

    Arg4: fffff80642973358, cast to nt!DPC_WATCHDOG_GLOBAL_TRIAGE_BLOCK, which contains

    additional information regarding this single DPC timeout



    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: 401



    BUILD_VERSION_STRING: 18362.1.amd64fre.19h1_release.190318-1202



    SYSTEM_MANUFACTURER: Gigabyte Technology Co., Ltd.



    SYSTEM_PRODUCT_NAME: X570 UD



    SYSTEM_SKU: Default string



    SYSTEM_VERSION: Default string



    BIOS_VENDOR: American Megatrends Inc.



    BIOS_VERSION: F3



    BIOS_DATE: 09/04/2019



    BASEBOARD_MANUFACTURER: Gigabyte Technology Co., Ltd.



    BASEBOARD_PRODUCT: X570 UD



    BASEBOARD_VERSION: x.x



    DUMP_TYPE: 1



    BUGCHECK_P1: 0



    BUGCHECK_P2: 501



    BUGCHECK_P3: 500



    BUGCHECK_P4: fffff80642973358



    DPC_TIMEOUT_TYPE: SINGLE_DPC_TIMEOUT_EXCEEDED



    CPU_COUNT: 18



    CPU_MHZ: ed1



    CPU_VENDOR: AuthenticAMD



    CPU_FAMILY: 17



    CPU_MODEL: 71



    CPU_STEPPING: 0



    DEFAULT_BUCKET_ID: WIN8_DRIVER_FAULT



    BUGCHECK_STR: 0x133



    PROCESS_NAME: Plex Media Server.exe



    CURRENT_IRQL: d



    ANALYSIS_SESSION_HOST: DESKTOP-0LCPO7P



    ANALYSIS_SESSION_TIME: 01-10-2020 23:30:21.0765



    ANALYSIS_VERSION: 10.0.18362.1 amd64fre



    LAST_CONTROL_TRANSFER: from fffff806425eea3d to fffff806425c14e0



    STACK_TEXT:

    ffffce01`0517cb08 fffff806`425eea3d : 00000000`00000133 00000000`00000000 00000000`00000501 00000000`00000500 : nt!KeBugCheckEx

    ffffce01`0517cb10 fffff806`4241f897 : 00004dc2`83b62c31 ffffce01`0515c180 00000000`00000286 ffffe685`fac76840 : nt!KeAccumulateTicks+0x1cbfdd

    ffffce01`0517cb70 fffff806`423601e1 : ffffa887`87b861a0 ffffa887`7dec9b00 ffffe685`fac768c0 ffffa887`7dec9bb0 : nt!KeClockInterruptNotify+0xc07

    ffffce01`0517cf30 fffff806`42402a25 : ffffa887`7dec9b00 00000000`00000000 00000000`00000000 ffff4fd7`01980de4 : hal!HalpTimerClockIpiRoutine+0x21

    ffffce01`0517cf60 fffff806`425c2f7a : ffffe685`fac768c0 ffffa887`7dec9b00 00000000`00000002 00000000`00000000 : nt!KiCallInterruptServiceRoutine+0xa5

    ffffce01`0517cfb0 fffff806`425c34e7 : 3fe30000`0000000a 0020b400`00000000 00000000`0000000a 00000002`0000000a : nt!KiInterruptSubDispatchNoLockNoEtw+0xfa

    ffffe685`fac76840 fffff806`424a2320 : 00000000`00000003 ffffe685`0000000a 00000000`00000000 ffffe685`fac76ad8 : nt!KiInterruptDispatchNoLockNoEtw+0x37

    ffffe685`fac769d0 fffff806`426a808c : ffffce01`0515c180 00000000`00000000 00000000`00001fff ffffe685`fac76b39 : nt!KxWaitForSpinLockAndAcquire+0x30

    ffffe685`fac76a00 fffff806`4261fc7e : ffffa887`87b872f0 00000000`00000002 ffffe685`fac76b39 ffffa887`8973e000 : nt!KiAcquireSpinLockInstrumented+0xb4

    ffffe685`fac76a50 fffff806`4689ecf5 : ffffa887`87b861a0 ffffa887`87b861a0 ffffa887`907d6000 00001fff`03ffbfff : nt!KeAcquireSpinLockRaiseToDpc+0x17ddfe

    ffffe685`fac76a80 fffff806`4689faea : ffffce01`0515c180 ffffa887`8973ef08 ffffa887`81b74350 00000000`00020000 : ndis!ndisQueuedMiniportDpcWorkItem+0x205

    ffffe685`fac76ba0 fffff806`4246ae95 : ffffce01`0515ef80 ffffa887`81b74350 ffffce01`0515c180 00000000`00000000 : ndis!ndisPeriodicReceivesTimer+0xea

    ffffe685`fac76c40 fffff806`4246a4ef : ffffce01`0515c180 798bd233`00000000 00000000`00000002 00000000`00000006 : nt!KiExecuteAllDpcs+0x305

    ffffe685`fac76d80 fffff806`425c8525 : 83484024`5c8b48c3 ffffce01`0515c180 00000000`00000000 00000000`0000007c : nt!KiRetireDpcList+0x1ef

    ffffe685`fac76fb0 fffff806`425c8310 : 00000000`180b8d01 00000000`00000000 00000000`00000000 00000000`00001dd8 : nt!KxRetireDpcList+0x5

    ffffe686`02a76ad0 fffff806`425c79e0 : 00000000`00000000 ffffe686`02a76b80 ffffa887`7dec9b00 00000000`00000001 : nt!KiDispatchInterruptContinue

    ffffe686`02a76b00 00000000`008bb1f1 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiDpcInterrupt+0x2f0

    00000000`180b87d8 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x8bb1f1





    THREAD_SHA1_HASH_MOD_FUNC: 3007274cee77e68fcb723cc089dc33aaa5222513



    THREAD_SHA1_HASH_MOD_FUNC_OFFSET: 1f7ddceeaee54f5d7ac407f4f1c8689a410fc901



    THREAD_SHA1_HASH_MOD: 26a778f0fd03891ad31c905da5c178ca4739a259



    FOLLOWUP_IP:

    ndis!ndisQueuedMiniportDpcWorkItem+205

    fffff806`4689ecf5 488b8b18130000 mov rcx,qword ptr [rbx+1318h]



    FAULT_INSTR_CODE: 188b8b48



    SYMBOL_STACK_INDEX: a



    SYMBOL_NAME: ndis!ndisQueuedMiniportDpcWorkItem+205



    FOLLOWUP_NAME: MachineOwner



    MODULE_NAME: ndis



    IMAGE_NAME: ndis.sys



    DEBUG_FLR_IMAGE_TIMESTAMP: 20136331



    STACK_COMMAND: .thread ; .cxr ; kb



    BUCKET_ID_FUNC_OFFSET: 205



    FAILURE_BUCKET_ID: 0x133_DPC_ndis!ndisQueuedMiniportDpcWorkItem



    BUCKET_ID: 0x133_DPC_ndis!ndisQueuedMiniportDpcWorkItem



    PRIMARY_PROBLEM_CLASS: 0x133_DPC_ndis!ndisQueuedMiniportDpcWorkItem



    TARGET_TIME: 2020-01-11T05:08:38.000Z



    OSBUILD: 18362



    OSSERVICEPACK: 0



    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: 1980-01-11 09:53:20



    BUILDDATESTAMP_STR: 190318-1202



    BUILDLAB_STR: 19h1_release



    BUILDOSVER_STR: 10.0.18362.1.amd64fre.19h1_release.190318-1202



    ANALYSIS_SESSION_ELAPSED_TIME: 29e2



    ANALYSIS_SOURCE: KM



    FAILURE_ID_HASH_STRING: km:0x133_dpc_ndis!ndisqueuedminiportdpcworkitem



    FAILURE_ID_HASH: {94235cf9-4baa-c0d7-f20b-c1d66e3d3670}



    Followup: MachineOwner

    ---------

    :)
     
    BrianTowll, Jan 11, 2020
    #1
  2. JWILLIAMS17349
    jwilliams17349 Win User

    DPC_WATCHDOG Violation

    Recently, I have been receiving a DPC_WATCHDOG Violation error resulting in a BSOD and eventual restart of my machine. This seems to only happen when I'm watching Netflix, or Hulu, or some other video streaming. At the following location is the two minidump
    files that I have on my machine Minidump Files. Typically, when streaming a video
    the video becomes glitchy and freezes, sound is distorted, or the video just stops playing. Sometimes the video then recontinues, or occasionally it errors out with the DPC_WATCHDOG Violation. Also, I have updated all of my drivers. Any help would be appreciated.
    Thank you
     
    jwilliams17349, Jan 11, 2020
    #2
  3. CHRISFRY1977
    ChrisFry1977 Win User
    DPC_WATCHDOG violation BSOD Windows 8.1/10

    I am experiencing multiple BSOD's with the message DPC_WATCHDOG Violation. This has been happening since I upgraded to Windows 8.1 and has continued since upgrading to Windows 10.

    My dump files are on OneDrive

    082315-20828-01.zip

    Please can you have a look and give me some indication of where to start looking?

    Regards

    Chris Fry
     
    ChrisFry1977, Jan 11, 2020
    #3
  4. WILLXXX
    Willxxx Win User

    Can anyone tell me what this WinDbg error means for BSOD "DPC_Watchdog Violation" I get daily?

    BSOD DPC_Watchdog violation on new custom built computer

    Hi,

    since few days I keep having a BSOD type DPC_Watchdog_violation.
    the minidump log file is pointing me to hal.dll and ntoskrnl.exe which i know aren't directly relevant to investigate.

    please find the dump log file, driverreviewreport and systeminfofile in a zip here: bsod.zip

    Hope someone can help me, as
    - I already checked my drivers and everything seems uptodate
    - I ran a chkdsk, nothing
    - I ran a scannow, nothing
    I have one new SSD WD black 512gb (firmware uptodate) + 2x old 4tb hdd and no GPU yet (using integrated one in my cpu).

    Thanks!

    BSOD DPC_Watchdog violation on new custom built computer
     
    Willxxx, Jan 11, 2020
    #4
Thema:

Can anyone tell me what this WinDbg error means for BSOD "DPC_Watchdog Violation" I get daily?

Loading...

  1. Can anyone tell me what this WinDbg error means for BSOD "DPC_Watchdog Violation" I get daily? - Similar Threads - anyone tell WinDbg

  2. Can anyone tell me what this means?

    in Windows 10 Gaming
    Can anyone tell me what this means?: I just installed and also updated windows on this PC, and after the PC finishes booting this notification pops up a few minutes later, can anyone tell me what this means?...

  3. Can anyone tell me what this means?

    in Windows 10 BSOD Crashes and Debugging
    Can anyone tell me what this means?: I just installed and also updated windows on this PC, and after the PC finishes booting this notification pops up a few minutes later, can anyone tell me what this means?...

  4. Can anyone tell me what this means?

    in Windows 10 Software and Apps
    Can anyone tell me what this means?: I just installed and also updated windows on this PC, and after the PC finishes booting this notification pops up a few minutes later, can anyone tell me what this means?...

  5. Can anyone tell me what this is?...

    in Windows 10 Software and Apps
    Can anyone tell me what this is?...: I believe its making my games crash at random times. I've done everything i can think of to stop the black screens mid game. So I started going through the event viewer to look at what is showing up around the time it black screens out and me having to reboot the system....

  6. Can anyone tell me what this is?

    in Windows 10 BSOD Crashes and Debugging
    Can anyone tell me what this is?: I saw this on the top left of my screen on the regular desktop part with no windows opened and I can move it around with my cursor but that’s it, don’t know what it is please help me...

  7. DPC_watchdog violation BSOD

    in Windows 10 BSOD Crashes and Debugging
    DPC_watchdog violation BSOD: Hi, I'm frequently blue screening - Ran memtest and sfc/dism and they came up with nothing found or fixed. My last 5 dumps are here. https://1drv.ms/u/s!ArgYnYnOFWvDgqk5xjAVUKtANSyHfA?e=nl6WJp Running the latest Windows update. Whocrashed suggests it's ntoskrnl.exe or...

  8. Can anyone tell me what this means pls?

    in Windows 10 Ask Insider
    Can anyone tell me what this means pls?: [ATTACH] submitted by /u/Fin808 [link] [comments] https://www.reddit.com/r/Windows10/comments/k4z1wj/can_anyone_tell_me_what_this_means_pls/

  9. Can anyone tell me what this icon means?

    in Windows 10 Ask Insider
    Can anyone tell me what this icon means?: [ATTACH] submitted by /u/medic713 [link] [comments] https://www.reddit.com/r/Windows10/comments/j6y6s9/can_anyone_tell_me_what_this_icon_means/

  10. Bsod dpc_watchdog violation

    in Windows 10 BSOD Crashes and Debugging
    Bsod dpc_watchdog violation: It's been less than 2 days since I upgraded from Windows 7 to Windows 10 and I already got hit by this BSOD twice. I searched on the web for solution and everything that I found is related to drivers outdated but I'm certain that all my drivers are updated. Can anyone help...