Windows 10: Debug of memory.dmp help please.

Discus and support Debug of memory.dmp help please. in Windows 10 BSOD Crashes and Debugging to solve the problem; Had 4 BSODs is 2 weeks on a new PC, I looked into the dmp files and thought as it was tcpip.sys being called out as the Module I would upgrade my NIC... Discussion in 'Windows 10 BSOD Crashes and Debugging' started by LyallNorth, Feb 19, 2021.

  1. Debug of memory.dmp help please.


    Had 4 BSODs is 2 weeks on a new PC, I looked into the dmp files and thought as it was tcpip.sys being called out as the Module I would upgrade my NIC driver.

    I did that lasr Wednesday and it crashed again tonight. Can anyone analyze the dmp please and see if anything jumps out.



    Microsoft R Windows Debugger Version 10.0.20153.1000 AMD64Copyright c Microsoft Corporation. All rights reserved.Loading Dump File [E:\MEMORY.DMP]Kernel Bitmap Dump File: Kernel address space is available, User address space may not be available.************* Path validation summary **************Response Time ms LocationDeferred srv*Symbol search path is: srv*Executable search path is: Windows 10 Kernel Version 19041 MP 12 procs Free x64Product: WinNt, suite: TerminalServer SingleUserTSEdition build lab: 19041.1.amd64fre.vb_release.191206-1406Machine Name:Kernel base = 0xfffff803`36600000 PsLoadedModuleList = 0xfffff803`3722a390Debug session time: Fri Feb 19 23:20:52.565 2021 UTC + 13:00System Uptime: 0 days 5:32:19.266Loading Kernel Symbols.............................................................................................................................................................................................................................Loading User SymbolsLoading unloaded module list.........For analysis of this file, run !analyze -vnt!KeBugCheckEx:fffff803`369f5a80 48894c2408 mov qword ptr [rsp+8],rcx ss:0018:fffff803`351dac90=00000000000001330: kd> !analyze -v******************************************************************************** ** Bugcheck Analysis ** ********************************************************************************DPC_WATCHDOG_VIOLATION 133The DPC watchdog detected a prolonged run time at an IRQL of DISPATCH_LEVELor 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: fffff803372fb320, cast to nt!DPC_WATCHDOG_GLOBAL_TRIAGE_BLOCK, which contains additional information regarding this single DPC timeoutDebugging 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: 4483 Key : Analysis.DebugAnalysisProvider.CPP Value: Create: 8007007e on LYALL-PC Key : Analysis.DebugData Value: CreateObject Key : Analysis.DebugModel Value: CreateObject Key : Analysis.Elapsed.mSec Value: 7285 Key : Analysis.Memory.CommitPeak.Mb Value: 100 Key : Analysis.System Value: CreateObject 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.1ADDITIONAL_XML: 1OS_BUILD_LAYERS: 1BUGCHECK_CODE: 133BUGCHECK_P1: 0BUGCHECK_P2: 501BUGCHECK_P3: 500BUGCHECK_P4: fffff803372fb320DPC_TIMEOUT_TYPE: SINGLE_DPC_TIMEOUT_EXCEEDEDTRAP_FRAME: fffff803351d1820 -- .trap 0xfffff803351d1820NOTE: The trap frame does not contain all registers.Some register values may be zeroed or incorrect.rax=000000001e65aab4 rbx=0000000000000000 rcx=fffff803351d1a10rdx=ffffa80ced00f9d0 rsi=0000000000000000 rdi=0000000000000000rip=fffff80336844567 rsp=fffff803351d19b0 rbp=fffff803351d1ac0 r8=fffff803351d1b20 r9=fffff803351d1b28 r10=fffff8033682c0a0r11=0000000000000002 r12=0000000000000000 r13=0000000000000000r14=0000000000000000 r15=0000000000000000iopl=0 nv up ei pl nz na po ncnt!KeYieldProcessorEx+0x17:fffff803`36844567 4883c420 add rsp,20hResetting default scopeBLACKBOXBSD: 1 !blackboxbsdBLACKBOXNTFS: 1 !blackboxntfsBLACKBOXPNP: 1 !blackboxpnpBLACKBOXWINLOGON: 1PROCESS_NAME: SystemDPC_STACK_BASE: FFFFF803351D3FB0STACK_TEXT: fffff803`351dac88 fffff803`36a3ac88 : 00000000`00000133 00000000`00000000 00000000`00000501 00000000`00000500 : nt!KeBugCheckExfffff803`351dac90 fffff803`3687541d : 000034b6`dd743592 fffff803`337cb180 00000000`00000246 00000000`001378d1 : nt!KeAccumulateTicks+0x1c8a88fffff803`351dacf0 fffff803`368759c1 : 00000000`001378d0 00000000`000b9b2e fffff803`337cb180 00000000`00000001 : nt!KiUpdateRunTime+0x5dfffff803`351dad40 fffff803`3686f833 : fffff803`337cb180 00000000`00000000 fffff803`37231640 00000000`00000000 : nt!KiUpdateTime+0x4a1fffff803`351dae80 fffff803`368781f2 : fffff803`351d1820 fffff803`351d18a0 fffff803`351d1800 00000000`00000002 : nt!KeClockInterruptNotify+0x2e3fffff803`351daf30 fffff803`36927ef5 : 0000002e`6cbda945 fffff803`372f39e0 fffff803`372f3a90 ffffc73c`14080a29 : nt!HalpTimerClockInterrupt+0xe2fffff803`351daf60 fffff803`369f752a : fffff803`351d18a0 fffff803`372f39e0 00000000`00000002 00000000`00000000 : nt!KiCallInterruptServiceRoutine+0xa5fffff803`351dafb0 fffff803`369f7a97 : 00000000`00000000 0000ff02`0000ff02 fffff803`351d1a90 fffff803`369f7aa4 : nt!KiInterruptSubDispatchNoLockNoEtw+0xfafffff803`351d1820 fffff803`36844567 : ffffffff`ffffffd1 fffff803`3682e09e 00000000`00000010 00000000`00000282 : nt!KiInterruptDispatchNoLockNoEtw+0x37fffff803`351d19b0 fffff803`3682e09a : ffffd002`43aad030 00000000`00000001 ffffd002`2ff558b0 fffff803`3ca03e40 : nt!KeYieldProcessorEx+0x17fffff803`351d19e0 fffff803`3682c113 : ffffd002`1e65aab4 fffff803`3ca03e63 ffffd002`43aad001 00000000`00000c01 : nt!KxWaitForLockOwnerShip+0x2afffff803`351d1a10 fffff803`3c6d61a7 : fffff803`3c81d6a8 fffff803`3c3d4f90 ffffd002`370921a0 fffff803`3c3d50af : nt!KeAcquireInStackQueuedSpinLockAtDpcLevel+0x73fffff803`351d1a40 fffff803`3c657088 : 00000000`00004800 ffffa80c`eb701000 00000000`00000000 ffffd002`370921a0 : tcpip!IppLbIndicatePackets+0x7f007fffff803`351d1af0 fffff803`36954488 : ffffd002`2ff9f2c0 ffffd002`2fe3b080 fffff803`351d1cc0 ffffd002`2ff9f201 : tcpip!IppLbTransmitStackCallout+0x2a8fffff803`351d1b60 fffff803`369543fd : fffff803`3c656de0 fffff803`351d1cc0 ffffd002`2fee8a20 ffffd002`00000000 : nt!KeExpandKernelStackAndCalloutInternal+0x78fffff803`351d1bd0 fffff803`3c657f09 : fffff803`3c819230 ffffd002`2fee8a20 fffff803`351d1c99 ffffd002`4d732010 : nt!KeExpandKernelStackAndCalloutEx+0x1dfffff803`351d1c10 fffff803`3c655dcf : 00000000`00000000 fffff803`3c819230 00000000`00000000 00000000`00000000 : tcpip!IppLoopbackEnqueue+0x729fffff803`351d1e70 fffff803`3c6550e3 : 00006c07`e6f20004 00000000`00000000 fffff803`3c819230 ffffd002`00000000 : tcpip!IppFragmentPackets+0x4affffff803`351d1f50 fffff803`3c654d68 : ffffd002`2ffa78e8 00000000`00000001 00000000`00000000 00000000`0000cd08 : tcpip!IppDispatchSendPacketHelper+0xbffffff803`351d2020 fffff803`3c6539b8 : ffffd002`2ffa79c8 00000000`00000007 00000000`00000000 ffffd002`2ffa78e8 : tcpip!IppPacketizeDatagrams+0x2e8fffff803`351d2150 fffff803`3c6524a9 : 00000000`00000000 00000000`00000000 fffff803`3c819230 ffffd002`4a8e07a0 : tcpip!IppSendDatagramsCommon+0x498fffff803`351d22d0 fffff803`3c63174e : ffffd002`39945040 00000000`00000014 00000000`00000000 ffffd002`497a0010 : tcpip!IpNlpFastSendDatagram+0x349fffff803`351d2390 fffff803`3c633916 : ffffd002`497a0010 00000000`00000000 00000000`8fd545fc fffff803`3c819598 : tcpip!TcpTcbHeaderSend+0x5cefffff803`351d2640 fffff803`3c699142 : ffffd002`2fcb9900 fffff803`3c556c07 00000000`00000000 ffffd002`4ca4cd01 : tcpip!TcpReceive+0x4d6fffff803`351d2730 fffff803`3c65a241 : ffffd002`2ffaf000 fffff803`3c64f433 ffffd002`4ca4cd60 fffff803`3c819230 : tcpip!TcpNlClientReceiveDatagrams+0x22fffff803`351d2770 fffff803`3c656b8b : ffffd002`2ffaf000 fffff803`351d28e9 00000000`00000000 ffffd002`2ffaf000 : tcpip!IppProcessDeliverList+0xc1fffff803`351d2850 fffff803`3c65610f : fffff803`3c819230 ffffd002`2ffda8e0 ffffd002`2ffaf000 00000000`00000000 : tcpip!IppReceiveHeaderBatch+0x21bfffff803`351d2950 fffff803`3c6534ac : ffffd002`3768e020 ffffd002`4ca4cd60 00000000`00000001 00000000`00000000 : tcpip!IppFlcReceivePacketsCore+0x32ffffff803`351d2a70 fffff803`3c69f770 : ffffd002`4ca4cd60 00000000`00000000 fffff803`351d2b41 00000000`00000000 : tcpip!IpFlcReceivePackets+0xcfffff803`351d2aa0 fffff803`3c69ed6c : 00000000`00000001 ffffd002`37626300 fffff803`3c692140 fffff803`351d2e7c : tcpip!FlpReceiveNonPreValidatedNetBufferListChain+0x270fffff803`351d2ba0 fffff803`36954488 : ffffd002`35e398a0 00000000`00000002 ffffd002`2fe3b080 fffff803`351d2e98 : tcpip!FlReceiveNetBufferListChainCalloutRoutine+0x17cfffff803`351d2cf0 fffff803`369543fd : fffff803`3c69ebf0 fffff803`351d2e98 ffffd002`2fcbccb0 fffff803`4f8dcf10 : nt!KeExpandKernelStackAndCalloutInternal+0x78fffff803`351d2d60 fffff803`3c691cdd : ffffd002`4ca4cee0 ffffd002`4ca4cd60 00000000`00000000 fffff803`3c3d392e : nt!KeExpandKernelStackAndCalloutEx+0x1dfffff803`351d2da0 fffff803`3c6913bd : 00000000`00000001 fffff803`351d2f00 ffffd002`37626370 fffff803`4fa567e0 : tcpip!NetioExpandKernelStackAndCallout+0x8dfffff803`351d2e00 fffff803`3c3d1eb1 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : tcpip!FlReceiveNetBufferListChain+0x46dfffff803`351d30b0 fffff803`3c3d1ccb : ffffd002`3757da30 00000000`00000001 00000000`00000000 00000000`00000001 : ndis!ndisMIndicateNetBufferListsToOpen+0x141fffff803`351d3190 fffff803`3c40dd4f : ffffd002`370921a0 ffffd002`00000001 ffffd002`4ca4cd60 ffffd002`4ca4cd60 : ndis!ndisMTopReceiveNetBufferLists+0x22bfffff803`351d3210 fffff803`3c413681 : 00000000`00000000 ffffd002`37619750 00000000`00000000 ffffd002`4f4bdba6 : ndis!ndisInvokeNextReceiveHandler+0x4bfffff803`351d32e0 fffff803`3c3d804e : ffffd002`37619750 00000000`00000000 00000000`00000000 fffff803`00000001 : ndis!ndisFilterIndicateReceiveNetBufferLists+0x3c211fffff803`351d3390 fffff803`3c993427 : 00000000`00000001 ffffd002`4ca4cd60 00000000`00000001 ffffd002`37619ad0 : ndis!NdisFIndicateReceiveNetBufferLists+0x6efffff803`351d33d0 fffff803`3c9944de : 00000000`00000003 ffffd002`37619750 fffff803`351d3490 00000000`00000000 : wfplwfs!L2NdisFIndicateReceiveNetBufferLists+0xa3fffff803`351d3430 fffff803`3c3d7ef1 : ffffd002`00000001 ffffd002`4cfad030 fffff803`3c3e8380 fffff803`00000001 : wfplwfs!LwfUpperRecvNetBufferLists+0xcefffff803`351d34c0 fffff803`3c3e83be : ffffd002`2fe3b080 fffff803`351d3691 fffff803`351d3670 fffff803`351d4000 : ndis!ndisCallReceiveHandler+0x61fffff803`351d3510 fffff803`36954488 : fffff803`351d3691 ffffd002`37619750 ffffd002`00000001 ffffd002`37558970 : ndis!ndisDataPathExpandStackCallback+0x3efffff803`351d3560 fffff803`369543fd : fffff803`3c3e8380 fffff803`351d3670 ffffd002`4cfad030 fffff803`351d3610 : nt!KeExpandKernelStackAndCalloutInternal+0x78fffff803`351d35d0 fffff803`3c40df40 : ffffd002`4cfad030 fffff803`36b3ef82 ffffd002`4cfad100 fffff803`3c697ac3 : nt!KeExpandKernelStackAndCalloutEx+0x1dfffff803`351d3610 fffff803`3c413681 : 00000000`00000002 ffffd002`375f1410 00000000`00000000 ffffd002`37685390 : ndis!ndisInvokeNextReceiveHandler+0x23cfffff803`351d36e0 fffff803`3c3d804e : ffffd002`375f1410 ffffd002`375ce020 ffffd002`00000000 00000000`00000001 : ndis!ndisFilterIndicateReceiveNetBufferLists+0x3c211fffff803`351d3790 fffff803`4ff3ab00 : ffffd002`4cfad1c0 00000000`00000003 00000000`00000000 ffffd002`375ce020 : ndis!NdisFIndicateReceiveNetBufferLists+0x6efffff803`351d37d0 fffff803`4ff3a5eb : ffffd002`4cfad1c0 ffffd002`4cfad1c0 00000000`00000000 ffffd002`00000034 : dnelwf64+0xab00fffff803`351d3870 fffff803`4ff37981 : ffffd002`00000000 ffffd002`3b2c7c90 fffff803`00000000 ffffd002`00000002 : dnelwf64+0xa5ebfffff803`351d3910 fffff803`3c3d7ef1 : 00000000`00000002 ffffd002`3b2c7c90 ffffd002`375f1010 fffff803`351d3a01 : dnelwf64+0x7981fffff803`351d3950 fffff803`3c40de4c : ffffd002`37558940 fffff803`351d3a21 ffffd002`375d7970 fffff803`36836264 : ndis!ndisCallReceiveHandler+0x61fffff803`351d39a0 fffff803`3c3d4a94 : 00000000`001373d0 00000000`00000001 ffffd002`370921a0 00000000`00000001 : ndis!ndisInvokeNextReceiveHandler+0x148fffff803`351d3a70 fffff803`4f8dd9c2 : 00000000`00000001 00000000`00000001 00000000`00000001 ffffd002`3b2c7c90 : ndis!NdisMIndicateReceiveNetBufferLists+0x104fffff803`351d3b00 fffff803`4f8be08a : ffffd002`36e8dfc0 00000000`00000000 ffffd002`36dea000 fffff803`368452d6 : vmswitch!VmsMpNicPvtReceiveRssProcessNblGroup+0x82fffff803`351d3b60 fffff803`3680781e : ffffd002`36e8dec0 00000000`00000000 fffff803`337ce240 ffffd002`425e6080 : vmswitch!VmsVrssDpc+0x7afffff803`351d3bb0 fffff803`36806b04 : fffff803`337cb180 00000000`00000000 00000000`00000008 00000000`000b984b : nt!KiExecuteAllDpcs+0x30efffff803`351d3d20 fffff803`369fcac5 : 00000000`00000000 fffff803`337cb180 00000000`00000000 ffffd002`37510738 : nt!KiRetireDpcList+0x1f4fffff803`351d3fb0 fffff803`369fc8b0 : ffffffff`ffffffb1 fffff803`369fbf65 00000000`01000010 00000000`00000246 : nt!KxRetireDpcList+0x5ffffa80c`eb707850 fffff803`369fbf7e : 00000000`00000000 ffffd002`370d7000 00000000`058c05b4 ffffa80c`eb707930 : nt!KiDispatchInterruptContinueffffa80c`eb707880 fffff803`3689328b : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000196 : nt!KiDpcInterrupt+0x2eeffffa80c`eb707a10 fffff803`3c427a9b : ffffd002`2fdfd690 ffffd002`2fdfd690 ffffa80c`eb707aa9 fffff803`3c406e00 : nt!KzLowerIrql+0x1bffffa80c`eb707a40 fffff803`36917e25 : ffffd002`2fe3b080 ffffd002`2fe3b080 fffff803`3c406ed0 00000000`00000000 : ndis!ndisReceiveWorkerThread+0x20bcbffffa80c`eb707b10 fffff803`369fd0d8 : ffff8380`a53c0180 ffffd002`2fe3b080 fffff803`36917dd0 24648b48`e0894850 : nt!PspSystemThreadStartup+0x55ffffa80c`eb707b60 00000000`00000000 : ffffa80c`eb708000 ffffa80c`eb701000 00000000`00000000 00000000`00000000 : nt!KiStartSystemThread+0x28SYMBOL_NAME: tcpip!IppLbIndicatePackets+7f007MODULE_NAME: tcpipIMAGE_NAME: tcpip.sysSTACK_COMMAND: .thread ; .cxr ; kbBUCKET_ID_FUNC_OFFSET: 7f007FAILURE_BUCKET_ID: 0x133_DPC_tcpip!IppLbIndicatePacketsOS_VERSION: 10.0.19041.1BUILDLAB_STR: vb_releaseOSPLATFORM_TYPE: x64OSNAME: Windows 10FAILURE_ID_HASH: {a0deef31-f3fd-261b-d75f-27a35a6e8170}Followup: MachineOwner---------

    :)
     
    LyallNorth, Feb 19, 2021
    #1
  2. Nikhar_K Win User

    Ethernet is showing as Kernel Debug Network Adapater

    Hi,



    Thank you for writing to Microsoft Community Forums.



    I understand that you see Kernel Debug Network Adapter in Device Manager. This can happen if debugging is turner on. I would suggest you to turn off debugging by following the steps mentioned below:



    1. Type command prompt in the search bar on the
      Taskbar.
    2. Right click on the command prompt icon and select
      Run as administrator.
    3. Paste the following commands and hit Enter:

      bcdedit /debug off


    If you still see the Network Adapter, you can disable it from Device Manager without problems. Refer the steps mentioned below:



    1. Press Windows Logo key + X, to open
      Device Manager.
    2. Expand Network adapters.
    3. Now, right click on the Kernel Debug adapter and select
      Disable device.


    Let us know how it goes.



    Regards,

    Nikhar Khare

    Microsoft Community - Moderator
     
    Nikhar_K, Feb 19, 2021
    #2
  3. Barman58 Win User
    Barman58, Feb 19, 2021
    #3
  4. Debug of memory.dmp help please.

    help to remote connect

    not sure how to use both programs u 2 suggested, i need more helpful steps thanks
     
    Corduroy_Jr, Feb 19, 2021
    #4
Thema:

Debug of memory.dmp help please.

Loading...
  1. Debug of memory.dmp help please. - Similar Threads - Debug memory dmp

  2. BSOD / please help reading debug info

    in Windows 10 Gaming
    BSOD / please help reading debug info: I have 2 brand new Dell Precision 3680 desktops. We got them to replace 2 older desktops that run in our procedure rooms. These computers require the use of Osprey capture cardsOsprey 825e. When the new desktops came in, We made sure all windows and dell command updates were...
  3. BSOD / please help reading debug info

    in Windows 10 Software and Apps
    BSOD / please help reading debug info: I have 2 brand new Dell Precision 3680 desktops. We got them to replace 2 older desktops that run in our procedure rooms. These computers require the use of Osprey capture cardsOsprey 825e. When the new desktops came in, We made sure all windows and dell command updates were...
  4. DMP File Debug help

    in Windows 10 Gaming
    DMP File Debug help: I have been experiencing issues with almost daily BSOD as well as my games crashing unexpectedly. I'm not very familiar with reading dmp files. Any suggestion on what my next step could be based off of the information provided below?Troubleshooting performed:- Memtest86 - No...
  5. DMP File Debug help

    in Windows 10 Software and Apps
    DMP File Debug help: I have been experiencing issues with almost daily BSOD as well as my games crashing unexpectedly. I'm not very familiar with reading dmp files. Any suggestion on what my next step could be based off of the information provided below?Troubleshooting performed:- Memtest86 - No...
  6. DMP File Debug help

    in Windows 10 BSOD Crashes and Debugging
    DMP File Debug help: I have been experiencing issues with almost daily BSOD as well as my games crashing unexpectedly. I'm not very familiar with reading dmp files. Any suggestion on what my next step could be based off of the information provided below?Troubleshooting performed:- Memtest86 - No...
  7. Memory DMP file

    in Windows 10 Gaming
    Memory DMP file: Can someone please run this minidump file and tell me specifically what's causing my blue Screen error to pop-up, I don't understand the errors and the cause.My system specs: Win 1016 GB ddr4 ramRTX 2070512 x2 NVMeintel i10 10th genminidump File:...
  8. Memory DMP file

    in Windows 10 BSOD Crashes and Debugging
    Memory DMP file: Can someone please run this minidump file and tell me specifically what's causing my blue Screen error to pop-up, I don't understand the errors and the cause.My system specs: Win 1016 GB ddr4 ramRTX 2070512 x2 NVMeintel i10 10th genminidump File:...
  9. BSOD - help with DMP files please

    in Windows 10 BSOD Crashes and Debugging
    BSOD - help with DMP files please: Hi, Having problems - can you help with my re-occurring BSOD? https://drive.google.com/drive/folders/1__oEZfyo9JTM5xsUFTz5vt8SQnlwDHV5?usp=sharing https://answers.microsoft.com/en-us/windows/forum/all/bsod-help-with-dmp-files-please/ab36c648-cd54-489a-994c-7f3c6d7ecc31
  10. JIT DEBUGGING - Please help.

    in Windows 10 BSOD Crashes and Debugging
    JIT DEBUGGING - Please help.: Please help me find out what to do with the notification below: See the end of this message for details on invoking just-in-time JIT debugging instead of this dialog box. ************** Exception Text ************** System.Management.ManagementException: Invalid...