Windows 10: Windows 10 Crash - Memory Dump Help

Hi there,


I've encountered the BSOD a few times in the last couple of days. It does seem to coincide with the use of particular software, however, I am using these programs quite often so that may not be much to go on SNES game emulator and OBS streaming software. I updated all of my drivers yesterday evening and thought the issue was resolved. Unfortunately, my system crashed again today.


I do not know enough about the contents of this file memory.dmp to understand where to go now. Would you please help me to understand the next steps in the troubleshooting process? Is there another spot on my machine that I could gather better information about the source of the issue? I would greatly appreciate your help.


Thanks, Kyle


Microsoft R Windows Debugger Version 10.0.19041.685 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 19041 MP 16 procs Free x64

Product: WinNt, suite: TerminalServer SingleUserTS

Built by: 19041.1.amd64fre.vb_release.191206-1406

Machine Name:

Kernel base = 0xfffff806`21e00000 PsLoadedModuleList = 0xfffff806`22a2a2f0

Debug session time: Sat Jan 16 18:51:50.512 2021 UTC - 8:00

System Uptime: 1 days 2:00:01.154

Loading Kernel Symbols

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

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

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

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

Loading User Symbols



Loading unloaded module list

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

For analysis of this file, run !analyze -v

0: kd> !analyze -v

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

* *

* Bugcheck Analysis *

* *

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



KMODE_EXCEPTION_NOT_HANDLED 1e

This is a very common bugcheck. Usually the exception address pinpoints

the driver/function that caused the problem. Always note this address

as well as the link date of the driver/image that contains this address.

Arguments:

Arg1: ffffffffc0000005, The exception code that was not handled

Arg2: fffff806221fd6b7, The address that the exception occurred at

Arg3: ffff87067c4b3978, Parameter 0 of the exception

Arg4: fffff80625281920, Parameter 1 of the exception



Debugging Details:

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





KEY_VALUES_STRING: 1



Key : Analysis.CPU.Sec

Value: 2



Key : Analysis.DebugAnalysisProvider.CPP

Value: Create: 8007007e on SHEPHERD



Key : Analysis.DebugData

Value: CreateObject



Key : Analysis.DebugModel

Value: CreateObject



Key : Analysis.Elapsed.Sec

Value: 2



Key : Analysis.Memory.CommitPeak.Mb

Value: 75



Key : Analysis.System

Value: CreateObject





BUGCHECK_CODE: 1e



BUGCHECK_P1: ffffffffc0000005



BUGCHECK_P2: fffff806221fd6b7



BUGCHECK_P3: ffff87067c4b3978



BUGCHECK_P4: fffff80625281920



WRITE_ADDRESS: fffff80625281920



EXCEPTION_PARAMETER1: ffff87067c4b3978



EXCEPTION_PARAMETER2: fffff80625281920



BLACKBOXBSD: 1 !blackboxbsd





BLACKBOXNTFS: 1 !blackboxntfs





BLACKBOXPNP: 1 !blackboxpnp





BLACKBOXWINLOGON: 1



PROCESS_NAME: System



BAD_STACK_POINTER: fffff806252810a8



STACK_TEXT:

fffff806`252810a8 fffff806`2230ebaf : 00000000`0000001e ffffffff`c0000005 fffff806`221fd6b7 ffff8706`7c4b3978 : nt!KeBugCheckEx

fffff806`252810b0 fffff806`22211986 : fffff806`25281920 fffff806`22103845 ffff8706`7c4b3bb0 fffff806`221fd6b7 : nt!KiFatalFilter+0x1f

fffff806`252810f0 fffff806`221cbf32 : fffff806`00000002 fffff806`21ed8e34 ffff8706`7c4b0000 ffff8706`7c4b6000 : nt!KeExpandKernelStackAndCalloutInternal$filt$0+0x16

fffff806`25281130 fffff806`221fe642 : fffff806`21ed8e34 fffff806`25281710 fffff806`221cbe90 00000000`00000000 : nt!_C_specific_handler+0xa2

fffff806`252811a0 fffff806`2212bf97 : fffff806`25281710 00000000`00000000 ffff8706`7c4b51e0 fffff806`22154488 : nt!RtlpExecuteHandlerForException+0x12

fffff806`252811d0 fffff806`2212ab86 : ffff8706`7c4b3978 fffff806`25281e20 ffff8706`7c4b3978 00000000`00000000 : nt!RtlDispatchException+0x297

fffff806`252818f0 fffff806`221f6612 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiDispatchException+0x186

fffff806`25281fb0 fffff806`221f65e0 : fffff806`222078a5 ffffcd05`eb7173cf ffffcd05`eb3e0410 ffffcd05`f3e0cc30 : nt!KxExceptionDispatchOnExceptionStack+0x12

ffff8706`7c4b3838 fffff806`222078a5 : ffffcd05`eb7173cf ffffcd05`eb3e0410 ffffcd05`f3e0cc30 ffffcd05`f3e0cc30 : nt!KiExceptionDispatchOnExceptionStackContinue

ffff8706`7c4b3840 fffff806`222035e0 : ffffcd05`eb494d60 ffff8706`7c4b3a89 00000000`00000000 00000000`00000003 : nt!KiExceptionDispatch+0x125

ffff8706`7c4b3a20 fffff806`221fd6b7 : ffffcd05`eda36480 fffff806`33b44b31 fffff806`300bc6b0 00000000`00000000 : nt!KiGeneralProtectionFault+0x320

ffff8706`7c4b3bb0 fffff806`33b44b31 : fffff806`300bc6b0 00000000`00000000 00000000`00000000 00000000`00000000 : nt!ExpInterlockedPopEntrySListFault

ffff8706`7c4b3bc0 fffff806`33b433c9 : 00000000`00000000 00060080`01000000 ffffcd05`f1037030 00000000`ef99cb01 : Ndu!NduCreateNblContext+0x59

ffff8706`7c4b3c00 fffff806`33b43251 : 00000000`00000000 00060080`01000000 00000000`00000000 fffff806`300ba580 : Ndu!NduOutboundMacClassifyProcessSingleNbl+0x149

ffff8706`7c4b3c80 fffff806`24338cee : ffff8706`7c4b3e68 00000000`00000002 ffffcd05`00000004 00000000`0000b74e : Ndu!NduOutboundMacClassify+0x151

ffff8706`7c4b3d00 fffff806`24a814d5 : 00000000`00000000 ffffcd05`eadfa730 ffffcd05`f1b6c600 00000000`00000051 : NETIO!KfdClassify2+0x19e

ffff8706`7c4b3dd0 fffff806`24a810ce : 00000000`00000000 ffffcd05`eba2c8b0 00000000`00000000 00000000`00000000 : wfplwfs!L2InspectNetBufferListsFast+0x165

ffff8706`7c4b3ee0 fffff806`241b58e8 : 00000000`00000001 ffffcd05`f1b6c600 ffffcd05`ed6d8810 fffff806`2ffcb2c0 : wfplwfs!LwfLowerSendNetBufferLists+0xbe

ffff8706`7c4b3f90 fffff806`241ee102 : 00000000`00000000 ffff8706`7c4b4059 ffffcd05`f030d4b0 00000000`00000001 : ndis!ndisCallSendHandler+0x58

ffff8706`7c4b3fe0 fffff806`241b25dd : 00000000`00000000 ffffcd05`e60ab1a0 ffffcd05`f3d59eb0 fffff806`00000000 : ndis!ndisInvokeNextSendHandler+0x10e

ffff8706`7c4b40b0 fffff806`2478fcbd : ffffcd05`ebee3520 ffffcd05`eba2c8b0 00000000`00000000 fffff806`00000000 : ndis!NdisSendNetBufferLists+0x17d

ffff8706`7c4b41b0 fffff806`2478f9e7 : ffffcd05`f23d8e10 00000000`00000000 00000000`00000800 ffffcd05`f3e1fb00 : tcpip!FlpSendPacketsHelper+0x2bd

ffff8706`7c4b4260 fffff806`24745bc5 : 00000000`00000000 fffff806`24909230 ffffcd05`e57028e8 00000000`00000000 : tcpip!FlSendPackets+0x57

ffff8706`7c4b4290 fffff806`247450e3 : 00008f07`d0cc0004 00000000`00000000 fffff806`24909230 ffffcd05`00000000 : tcpip!IppFragmentPackets+0x2a5

ffff8706`7c4b4370 fffff806`24744d68 : ffffcd05`e57028e8 00000000`00000001 00000000`00000000 00000000`0000d4a1 : tcpip!IppDispatchSendPacketHelper+0xbf

ffff8706`7c4b4440 fffff806`247439b8 : ffffcd05`e57029c8 00000000`00000007 00000000`00000000 ffffcd05`e57028e8 : tcpip!IppPacketizeDatagrams+0x2e8

ffff8706`7c4b4570 fffff806`247424a9 : eb707c79`51d04600 00000000`00000000 fffff806`24909230 ffffcd05`f230e560 : tcpip!IppSendDatagramsCommon+0x498

ffff8706`7c4b46f0 fffff806`24764c46 : ffffcd05`ebeb8ba0 fffff806`00000014 00000000`00000000 ffffcd05`f230e560 : tcpip!IpNlpFastSendDatagram+0x349

ffff8706`7c4b47b0 fffff806`24723ab4 : ffffcd05`f104e010 fffff806`2490ec00 00000000`d5b4aeca fffff806`24909598 : tcpip!TcpTcbSend+0x1736

ffff8706`7c4b4b30 fffff806`24789142 : ffffcd05`e0d33400 00000000`00008f07 00000000`00000000 ffffcd05`e5718001 : tcpip!TcpReceive+0x674

ffff8706`7c4b4c20 fffff806`2474a240 : ffffcd05`f0ee4030 00000000`000001e4 00000000`01ff0000 ffffcd05`e03fe6a0 : tcpip!TcpNlClientReceiveDatagrams+0x22

ffff8706`7c4b4c60 fffff806`24746b8b : 00000000`00000000 00000000`0000111c 00000000`00000000 ffffcd05`e5718000 : tcpip!IppProcessDeliverList+0xc0

ffff8706`7c4b4d40 fffff806`2474610f : fffff806`24909230 ffffcd05`e56a98a0 ffffcd05`e5718000 00000000`00000000 : tcpip!IppReceiveHeaderBatch+0x21b

ffff8706`7c4b4e40 fffff806`247434ac : ffffcd05`f3e1fb10 ffffcd05`f0ee4030 00000000`00000001 00000000`00000000 : tcpip!IppFlcReceivePacketsCore+0x32f

ffff8706`7c4b4f60 fffff806`2478f76f : ffffcd05`f0ee4030 00000000`00000000 ffff8706`7c4b5031 00000000`00000000 : tcpip!IpFlcReceivePackets+0xc

ffff8706`7c4b4f90 fffff806`2478ed6c : ffffcd05`f2110001 ffffcd05`f244f400 fffff806`24782140 ffff8706`7c4b536c : tcpip!FlpReceiveNonPreValidatedNetBufferListChain+0x26f

ffff8706`7c4b5090 fffff806`22154488 : ffffcd05`e57cb0c0 00000000`00000002 ffffcd05`e554f200 ffff8706`7c4b5388 : tcpip!FlReceiveNetBufferListChainCalloutRoutine+0x17c

ffff8706`7c4b51e0 fffff806`221543fd : fffff806`2478ebf0 ffff8706`7c4b5388 ffffcd05`e00fbbd0 ffffcd05`f3e0e730 : nt!KeExpandKernelStackAndCalloutInternal+0x78

ffff8706`7c4b5250 fffff806`24781cdd : 00000000`00000000 00000000`00000000 ffff8706`7c4b5300 fffff806`2ffddf1b : nt!KeExpandKernelStackAndCalloutEx+0x1d

ffff8706`7c4b5290 fffff806`247813bd : 00000000`00000001 ffff8706`7c4b53f0 ffffcd05`f244f4a0 ffffcd05`ef3acf70 : tcpip!NetioExpandKernelStackAndCallout+0x8d

ffff8706`7c4b52f0 fffff806`241b1eb0 : 00000000`00000000 ffffcd05`ed735b20 00000000`00000000 00000000`00000000 : tcpip!FlReceiveNetBufferListChain+0x46d

ffff8706`7c4b55a0 fffff806`241b1ccb : ffffcd05`ebee3520 ffffcd05`ed6d0001 ffffcd05`00000000 00000001`00000001 : ndis!ndisMIndicateNetBufferListsToOpen+0x140

ffff8706`7c4b5680 fffff806`241b7ef0 : ffffcd05`e60ab1a0 ffffcd05`f2117a01 ffffcd05`e60ab1a0 ffffcd05`ed6d8810 : ndis!ndisMTopReceiveNetBufferLists+0x22b

ffff8706`7c4b5700 fffff806`241edee3 : ffffcd05`f0ee4030 ffff8706`7c4b57d1 00000000`00000000 00000000`00000000 : ndis!ndisCallReceiveHandler+0x60

ffff8706`7c4b5750 fffff806`241b4a94 : 00000000`005b6849 00000000`00000001 ffffcd05`e60ab1a0 00000000`00000001 : ndis!ndisInvokeNextReceiveHandler+0x1df

ffff8706`7c4b5820 fffff806`30f961d8 : ffffcd05`e6947000 ffffcd05`e6947000 00000000`00000000 ffffcd05`e69475f0 : ndis!NdisMIndicateReceiveNetBufferLists+0x104

ffff8706`7c4b58b0 fffff806`30f81dc8 : 00000000`00000000 00000000`00000001 00000000`0000000a ffff8706`7c4b5a20 : rt640x64!MpHandleRecvIntPriVLanJumbo+0x2c4

ffff8706`7c4b59a0 fffff806`24216d01 : 00000000`00000000 ffffcd05`f367f520 00000000`00000000 ffffcd05`e554f340 : rt640x64!MPHandleInterrupt+0x398

ffff8706`7c4b5a10 fffff806`242171dc : ffffcd05`f367f540 00000000`0000000a 00000000`00000001 00000000`00000000 : ndis!ndisMiniportDpc+0x109

ffff8706`7c4b5aa0 fffff806`24207b0d : ffffcd05`e553ba20 ffffcd05`e553ba20 ffff8706`7c4b5ba9 fffff806`241e6e00 : ndis!ndisQueuedMiniportDpcWorkItem+0x11c

ffff8706`7c4b5b40 fffff806`22117e25 : ffffcd05`e554f200 ffffcd05`e554f200 fffff806`241e6ed0 00000000`00000000 : ndis!ndisReceiveWorkerThread+0x20c3d

ffff8706`7c4b5c10 fffff806`221fcdd8 : ffff8c00`c3980180 ffffcd05`e554f200 fffff806`22117dd0 00000000`00000000 : nt!PspSystemThreadStartup+0x55

ffff8706`7c4b5c60 00000000`00000000 : ffff8706`7c4b6000 ffff8706`7c4b0000 00000000`00000000 00000000`00000000 : nt!KiStartSystemThread+0x28





SYMBOL_NAME: Ndu!NduCreateNblContext+59



MODULE_NAME: Ndu



IMAGE_NAME: Ndu.sys



STACK_COMMAND: .thread ; .cxr ; kb



BUCKET_ID_FUNC_OFFSET: 59



FAILURE_BUCKET_ID: 0x1E_c0000005_STACKPTR_ERROR_Ndu!NduCreateNblContext



OS_VERSION: 10.0.19041.1



BUILDLAB_STR: vb_release



OSPLATFORM_TYPE: x64



OSNAME: Windows 10



FAILURE_ID_HASH: {2b44c6ba-8dbe-d515-a0f4-1d53055ec81c}



Followup: MachineOwner

---------

:)

 

Windows 10 isnt creating memory dumps

Ok guys, for the past week windows 10 has been randomly rebooting it self on my pc.

Its been doing about once a day or once every couple of days. I'm not getting any bsods or memory dumps when it crashes or at least i dont see or cant find the memory dumps.

I have followed the instructions on this site Install and Configure WinDBG for BSOD Analysis and other one I have bookmarked on my pc but im at work right now so i cant bring it up here, but im still having issues.

So any help in configuring win 10 properly to create memory dumps or bsods so i can diagnose the issue would be greatly appreciated and thanks in advanced.

 

Windows 10 isnt creating memory dumps

It should still be doing a dump whether it's just from kernel space or kernel plus user space. It's possible the crashes your PC is experiencing are not allowing for a memory dump to be created. It's happened to me before when I've been pushing my overclock to far. Instead of the sad face BSOD I've gotten a hard lockup that prevented a memory dump.

This might be worth looking over.
Configure Windows 10 to Create Minidump on BSOD

 

Windows 10 isnt creating memory dumps

Ok if my pc starts crashing again il follow your advice. i used 5 hours last night and game for about 3 hours with no issue.

I also updated my gpu drivers as well.