SOMEONE PLEASE HELP -BLUE SCREEN ERROR

Edwin Tenkorang 21 Reputation points
2021-04-29T15:57:37.11+00:00

I have a recurring DPC Watchdog error which comes with a blue screen, I've reinstalled windows but still doesn't work. Help me.
I run a debugger and this is what i got.

**

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: fffff805284fb320, 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 

Key  : Analysis.CPU.mSec  
Value: 4140  

Key  : Analysis.DebugAnalysisManager  
Value: Create  

Key  : Analysis.Elapsed.mSec  
Value: 9775  

Key  : Analysis.Init.CPU.mSec  
Value: 624  

Key  : Analysis.Init.Elapsed.mSec  
Value: 22066  

Key  : Analysis.Memory.CommitPeak.Mb  
Value: 87  

Key  : WER.OS.Branch  
Value: vb_release  

Key  : WER.OS.Timestamp  
Value: 2019-12-06T14:06:00Z  

Key  : WER.OS.Version  
Value: 10.0.19041.1

BUGCHECK_CODE: 133

BUGCHECK_P1: 0

BUGCHECK_P2: 501

BUGCHECK_P3: 500

BUGCHECK_P4: fffff805284fb320

DPC_TIMEOUT_TYPE: SINGLE_DPC_TIMEOUT_EXCEEDED

TRAP_FRAME: ffffcb88d9e4dab0 -- (.trap 0xffffcb88d9e4dab0)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=00000000182d9978 rbx=0000000000000000 rcx=ffffcb88d9e4dca0
rdx=ffffcb88d9e8dc70 rsi=0000000000000000 rdi=0000000000000000
rip=fffff80527a44567 rsp=ffffcb88d9e4dc40 rbp=ffffcc80b593e750
r8=ffffcb88d9e4de10 r9=0000000000000000 r10=0000000000000002
r11=0000000000001001 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0 nv up ei pl nz na po nc
nt!KeYieldProcessorEx+0x17:
fffff805`27a44567 4883c420 add rsp,20h
Resetting default scope

BLACKBOXBSD: 1 (!blackboxbsd)

BLACKBOXNTFS: 1 (!blackboxntfs)

BLACKBOXPNP: 1 (!blackboxpnp)

BLACKBOXWINLOGON: 1

PROCESS_NAME: System

STACK_TEXT:
ffffcc80b329ee18 fffff80527c3adbe : 0000000000000133 0000000000000000 0000000000000501 0000000000000500 : nt!KeBugCheckEx
ffffcc80b329ee20 fffff80527a6f9a3 : 000006f28b110482 ffffcc80b3285180 0000000000000000 ffffcc80b3285180 : nt!KeAccumulateTicks+0x1c8bbe
ffffcc80b329ee80 fffff80527a6f48a : ffffdc8e740ebd40 ffffcb88d9e4db30 ffffcb88d9e4f400 0000000000000000 : nt!KeClockInterruptNotify+0x453
ffffcc80b329ef30 fffff80527b27f55 : ffffdc8e740ebd40 ffffdc8e740ebe60 ffffdc8e740ebf10 ffff58c11610e007 : nt!HalpTimerClockIpiRoutine+0x1a
ffffcc80b329ef60 fffff80527bf78ea : ffffcb88d9e4db30 ffffdc8e740ebd40 0000000000000000 0000000000000000 : nt!KiCallInterruptServiceRoutine+0xa5
ffffcc80b329efb0 fffff80527bf7e57 : ffffdc8e9b0c5000 fffff80527a50cb9 ffffcb88d9e4dd00 fffff80527bf7e64 : nt!KiInterruptSubDispatchNoLockNoEtw+0xfa
ffffcb88d9e4dab0 fffff80527a44567 : 0000000000000010 0000000000000286 ffffcb88d9e4dc68 0000000000000018 : nt!KiInterruptDispatchNoLockNoEtw+0x37
ffffcb88d9e4dc40 fffff80527a2e09a : 0000000000000000 0000000000000000 ffff60057bb754f0 0000000000000000 : nt!KeYieldProcessorEx+0x17
ffffcb88d9e4dc70 fffff80527a2e05f : 00000000182d9978 0000000000000000 0000000000000000 0000000000000000 : nt!KxWaitForLockOwnerShip+0x2a
ffffcb88d9e4dca0 fffff8053343b3eb : 000000000007c0e2 ffffdc8e740a7780 ffffdc8e94e5a010 0000000000000000 : nt!KeAcquireInStackQueuedSpinLock+0x7f
ffffcb88d9e4dcd0 fffff8053343a0e2 : 00000000ffffffff ffffcc80b593e750 0000000000000000 0000000000000003 : SmbCo10X64+0x1b3eb
ffffcb88d9e4dd80 fffff80533426d34 : ffffdc8e9b0c7320 ffffcb88d9e4df00 0000000000000000 0000000000000002 : SmbCo10X64+0x1a0e2
ffffcb88d9e4de00 fffff8052b4dca51 : ffffcb88d9e4e610 ffffdc8e773aecd0 0000000000004500 ffffdc8e773aecd0 : SmbCo10X64+0x6d34
ffffcb88d9e4e000 fffff8052b4d86cb : 0000000000000010 ffffcb88d9e4e610 ffffdc8e773aecd0 ffffdc8e949c6280 : NETIO!ProcessCallout+0x5d1
ffffcb88d9e4e180 fffff8052b6d881c : ffffdc8e773b5a20 0000000000004561 ffffcb88d9e4e670 ffffdc8e9e8ed300 : NETIO!KfdClassify+0x8bb
ffffcb88d9e4e570 fffff8052b664d19 : ffffdc8e98294d10 0000000000000004 ffffdc8e9341fa20 fffff8052b7a9230 : tcpip!WfpTlShimInspectSendTcpDatagram+0x360
ffffcb88d9e4e6e0 fffff8052b5e3d7b : ffffdc8e77419988 0000000000001086 ffffcb88d9e4eab0 0000000000000000 : tcpip!IppInspectLocalDatagramsOut+0x80899
ffffcb88d9e4e9b0 fffff8052b5e28e9 : ffffdc8e9ece0700 0000000000000000 fffff8052b7a9230 ffffdc8e95077460 : tcpip!IppSendDatagramsCommon+0x41b
ffffcb88d9e4eb30 fffff8052b605615 : ffffdc8e9b6f6520 0000000000000014 0000000000000000 ffffdc8e95077460 : tcpip!IpNlpFastSendDatagram+0x349
ffffcb88d9e4ebf0 fffff8052b5c0533 : 0000000000000000 0000000000000003 ffffcb8800000008 00000000004d3186 : tcpip!TcpTcbSend+0x1755
ffffcb88d9e4ef80 fffff80527a0781e : ffffcc80b3288240 0000000000000000 ffffcb88d9e4f460 ffffcc80b3285180 : tcpip!TcpPeriodicTimeoutHandler+0x1683
ffffcb88d9e4f1a0 fffff80527a06b04 : 0000000000000000 0000000000000000 0000000000140001 0000000000000000 : nt!KiExecuteAllDpcs+0x30e
ffffcb88d9e4f310 fffff80527bf99ae : ffffffff00000000 ffffcc80b3285180 ffffcc80b3290240 ffffdc8e9e4ee080 : nt!KiRetireDpcList+0x1f4
ffffcb88d9e4f5a0 0000000000000000 : ffffcb88d9e50000 ffffcb88d9e49000 0000000000000000 0000000000000000 : nt!KiIdleLoop+0x9e

SYMBOL_NAME: SmbCo10X64+1b3eb

MODULE_NAME: SmbCo10X64

IMAGE_NAME: SmbCo10X64.sys

STACK_COMMAND: .thread ; .cxr ; kb

BUCKET_ID_FUNC_OFFSET: 1b3eb

FAILURE_BUCKET_ID: 0x133_DPC_SmbCo10X64!unknown_function

OS_VERSION: 10.0.19041.1

BUILDLAB_STR: vb_release

OSPLATFORM_TYPE: x64

OSNAME: Windows 10

FAILURE_ID_HASH: {b7ae26a3-5838-8ff0-cad2-fb40469d2555}

Followup: MachineOwner
---------

Can anyone decipher anything from this?

Windows 10
Windows 10
A Microsoft operating system that runs on personal computers and tablets.
10,660 questions
0 comments
Accepted answer
  1. Jenny Feng 14,081 Reputation points
    2021-04-30T02:26:50.047+00:00

    @Edwin Tenkorang
    Hi,
    One reason for DPC Watchdog Violation is outdated drivers for your hardware devices. You should verify that all your devices have the right and latest drivers, and update those that don’t.

    You can update your drivers manually by going to the manufacturer’s website and searching for the most recent correct driver.
    For your reference:
    Update drivers in Windows 10
    https://support.microsoft.com/en-us/windows/update-drivers-in-windows-10-ec62f46c-ff14-c91d-eead-d7126dc1f7b6

    Hope above information can help you.

    ============================================

    If the Answer is helpful, please click "Accept Answer" and upvote it.
    Note: Please follow the steps in our documentation to enable e-mail notifications if you want to receive the related email notification for this thread.

    0 comments

2 additional answers

Sort by: Most helpful
Most helpful Newest Oldest
  1. EckiS 821 Reputation points
    2021-04-29T22:07:19.503+00:00

    Crash is in SmbCo10X64.sys.
    Seems to be the "Killer" Network driver, which is known to be buggy.

    0 comments
  2. Docs 15,146 Reputation points
    2021-04-30T05:09:44.953+00:00

    SmbCo10X64.sys was seen in the call stack and is the likely cause of the crash.

    Please post share links for:

    msinfo32 > save as nfo
    C:\windows\memory.dmp > save to downloads folder > post a separate share link if size is less than 2 GB
    If the memory dump is too large then post a share link for the mini dump: C:\windows\minidump

    0 comments