Windows 10: BSODing, dmp readouts

Discus and support BSODing, dmp readouts in Windows 10 BSOD Crashes and Debugging to solve the problem; My computer has constantly been BSODing, and this morning I decided to do a fresh install of Windows 10 on it to see if it helps. The computer will run... Discussion in 'Windows 10 BSOD Crashes and Debugging' started by MikeC18, Apr 5, 2021.

  1. MIKEC18
    MikeC18 Win User

    BSODing, dmp readouts


    My computer has constantly been BSODing, and this morning I decided to do a fresh install of Windows 10 on it to see if it helps. The computer will run fine for gaming hours on end, but once i start to multitask is when it seems to go down, so the time interval between crashes is not consistent. I have updated the drivers and have now started looking at the minidump files trying to track down the issue.



    One talks about discord.exe which i have now uninstalled, but before then it was still BSODing, and the other file i have references ntkrnlmp.exe. I have been looking around trying solutions i have been finding but am wondering if there is someone more experienced here that may be able to help me present time.

    I have attached the .dmp readouts


    Thanks





    Microsoft R Windows Debugger Version 10.0.21306.1007 AMD64

    Copyright c Microsoft Corporation. All rights reserved.





    Loading Dump File [C:\Windows\Minidump\040521-9265-01.dmp]

    Mini Kernel Dump File: Only registers and stack trace are available



    Symbol search path is: srv*

    Executable search path is:

    Windows 10 Kernel Version 19041 MP 12 procs Free x64

    Product: WinNt, suite: TerminalServer SingleUserTS Personal

    Edition build lab: 19041.1.amd64fre.vb_release.191206-1406

    Machine Name:

    Kernel base = 0xfffff800`0be00000 PsLoadedModuleList = 0xfffff800`0ca2a3b0

    Debug session time: Mon Apr 5 13:34:38.167 2021 UTC - 5:00

    System Uptime: 0 days 3:59:04.793

    Loading Kernel Symbols

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

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

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

    Loading User Symbols

    Loading unloaded module list

    ........

    For analysis of this file, run !analyze -v

    nt!KeBugCheckEx:

    fffff800`0c1f5210 48894c2408 mov qword ptr [rsp+8],rcx ss:0018:fffff68b`54f4e3b0=000000000000001e

    1: 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: fffff8000c1fd147, The address that the exception occurred at

    Arg3: 0000000000000000, Parameter 0 of the exception

    Arg4: ffffffffffffffff, Parameter 1 of the exception



    Debugging Details:

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





    KEY_VALUES_STRING: 1



    Key : Analysis.CPU.mSec

    Value: 2827



    Key : Analysis.DebugAnalysisManager

    Value: Create



    Key : Analysis.Elapsed.mSec

    Value: 14513



    Key : Analysis.Init.CPU.mSec

    Value: 406



    Key : Analysis.Init.Elapsed.mSec

    Value: 20327



    Key : Analysis.Memory.CommitPeak.Mb

    Value: 74



    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: 1e



    BUGCHECK_P1: ffffffffc0000005



    BUGCHECK_P2: fffff8000c1fd147



    BUGCHECK_P3: 0



    BUGCHECK_P4: ffffffffffffffff



    READ_ADDRESS: fffff8000cafb390: Unable to get MiVisibleState

    Unable to get NonPagedPoolStart

    Unable to get NonPagedPoolEnd

    Unable to get PagedPoolStart

    Unable to get PagedPoolEnd

    unable to get nt!MmSpecialPagesInUse

    ffffffffffffffff



    EXCEPTION_PARAMETER2: ffffffffffffffff



    BLACKBOXBSD: 1 !blackboxbsd





    BLACKBOXNTFS: 1 !blackboxntfs





    BLACKBOXPNP: 1 !blackboxpnp





    BLACKBOXWINLOGON: 1



    CUSTOMER_CRASH_COUNT: 1



    PROCESS_NAME: Discord.exe



    TRAP_FRAME: fffff68b54f4ec50 -- .trap 0xfffff68b54f4ec50

    NOTE: The trap frame does not contain all registers.

    Some register values may be zeroed or incorrect.

    rax=00000005f1550000 rbx=0000000000000000 rcx=ffffc20b7e6ac800

    rdx=0076006500440050 rsi=0000000000000000 rdi=0000000000000000

    rip=fffff8000c1fd147 rsp=fffff68b54f4ede0 rbp=fffff68b54f4f009

    r8=0076006500440050 r9=0000000000000001 r10=ffffc20b7e6ac800

    r11=fffff68b54f4ee78 r12=0000000000000000 r13=0000000000000000

    r14=0000000000000000 r15=0000000000000000

    iopl=0 nv up ei pl nz na po nc

    nt!ExpInterlockedPopEntrySListFault:

    fffff800`0c1fd147 498b08 mov rcx,qword ptr [r8] ds:00760065`00440050=????????????????

    Resetting default scope



    STACK_TEXT:

    fffff68b`54f4e3a8 fffff800`0c230d05 : 00000000`0000001e ffffffff`c0000005 fffff800`0c1fd147 00000000`00000000 : nt!KeBugCheckEx

    fffff68b`54f4e3b0 fffff800`0c2072ac : ffffe683`b5d7ccc0 fffff68b`54f4eba0 fffff68b`54f4ec50 fffff68b`54f4eb90 : nt!KiDispatchException+0x1df4e5

    fffff68b`54f4ea70 fffff800`0c202fe0 : ffffe683`b594d830 fffff800`0c4f51ae 00000000`00000000 fffff800`0c4edf27 : nt!KiExceptionDispatch+0x12c

    fffff68b`54f4ec50 fffff800`0c1fd147 : ffffc20b`8e0710b0 fffff800`0c4f5f70 00000000`00000000 00000000`00000000 : nt!KiGeneralProtectionFault+0x320

    fffff68b`54f4ede0 fffff800`0c4f5f70 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!ExpInterlockedPopEntrySListFault

    fffff68b`54f4edf0 fffff800`0c4f5da9 : ffffc20b`8e0710b0 00000000`00000000 ffffe683`b594d830 00000000`00000001 : nt!ObpCaptureObjectName+0x120

    fffff68b`54f4ee80 fffff800`0c4f5537 : ffffc20b`8e071010 ffffc20b`7e6972a0 ffffe683`b5d7ccc0 fffff68b`54f4f050 : nt!ObpCaptureObjectCreateInformation+0x1c9

    fffff68b`54f4ef20 fffff800`0c4f544c : 00000000`00000000 00000000`00000000 00000000`00000000 ffffc20b`7e6f1640 : nt!ObOpenObjectByNameEx+0xc7

    fffff68b`54f4f050 fffff800`0c4f4f71 : fffff68b`54f4f510 fffff68b`54f4f3c0 00000000`00000000 01000000`00100000 : nt!ObOpenObjectByName+0x5c

    fffff68b`54f4f0a0 fffff800`0c46c9b2 : ffffe683`b5863040 fffff800`0c4f138c 00000000`0000193c 00000000`00000000 : nt!CmOpenKey+0x2c1

    fffff68b`54f4f300 fffff800`0c206bb8 : 00000000`00000000 fffff68b`54f4f650 00000000`00000002 00000000`00000000 : nt!NtOpenKey+0x12

    fffff68b`54f4f340 fffff800`0c1f9070 : fffff800`0c43b38c ffffc20b`96b5f6d0 fffff800`0c1f9070 00000000`00000010 : nt!KiSystemServiceCopyEnd+0x28

    fffff68b`54f4f4d8 fffff800`0c43b38c : ffffc20b`96b5f6d0 fffff800`0c1f9070 00000000`00000010 00000000`00040082 : nt!KiServiceLinkage

    fffff68b`54f4f4e0 fffff800`0c43b1f1 : fffff68b`54f4f800 ffffffff`8000193c 00000000`006c006a fffff800`0c5bd7f0 : nt!SepRegOpenKey+0x68

    fffff68b`54f4f550 fffff800`0c486f8b : fffff68b`54f4f800 00000000`00000000 00000000`00000000 00000000`00000000 : nt!SepRegQueryDwordValue+0x29

    fffff68b`54f4f590 fffff800`0c40be3a : fffff68b`54f4f840 00000000`00000000 00000000`00000000 00000000`00000000 : nt!SeGetImageRequiredSigningLevel+0x63

    fffff68b`54f4f5f0 fffff800`0c40bbbf : 00000000`00000000 fffff68b`54f4f840 ffffe683`bd7a3500 ffffc20b`8e221400 : nt!MiValidateExistingImage+0x1e2

    fffff68b`54f4f6a0 fffff800`0c4ff5ed : 00000000`00000000 fffff68b`54f4f840 ffffc20b`96b5f080 ffffc20b`a46042b0 : nt!MiShareExistingControlArea+0xc7

    fffff68b`54f4f6d0 fffff800`0c4fed64 : ffffc20b`8e2214d0 00000000`00000000 ffffc20b`a46042b0 00000000`00000000 : nt!MiCreateImageOrDataSection+0x1ad

    fffff68b`54f4f7c0 fffff800`0c4feb47 : 00000000`01000000 fffff68b`54f4fb80 00000000`00000001 00000000`00000010 : nt!MiCreateSection+0xf4

    fffff68b`54f4f940 fffff800`0c4fe92c : 00000000`00b5e438 00000000`0000000d 00000000`00000000 00000000`00000001 : nt!MiCreateSectionCommon+0x207

    fffff68b`54f4fa20 fffff800`0c206bb8 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!NtCreateSection+0x5c

    fffff68b`54f4fa90 00007ff8`ba46c6e4 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceCopyEnd+0x28

    00000000`00b5e398 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x00007ff8`ba46c6e4





    SYMBOL_NAME: nt!KiDispatchException+1df4e5



    MODULE_NAME: nt



    IMAGE_NAME: ntkrnlmp.exe



    IMAGE_VERSION: 10.0.19041.631



    STACK_COMMAND: .thread ; .cxr ; kb



    BUCKET_ID_FUNC_OFFSET: 1df4e5



    FAILURE_BUCKET_ID: 0x1E_c0000005_R_nt!KiDispatchException



    OS_VERSION: 10.0.19041.1



    BUILDLAB_STR: vb_release



    OSPLATFORM_TYPE: x64



    OSNAME: Windows 10



    FAILURE_ID_HASH: {8cda4994-5937-8d70-909d-3f5236ba02c6}



    Followup: MachineOwner

    ---------



    1: kd> lmvm nt

    Browse full module list

    start end module name

    fffff800`0be00000 fffff800`0ce46000 nt pdb symbols C:\ProgramData\Dbg\sym\ntkrnlmp.pdb\F923DA2D238E7C7CE180B962B19A37811\ntkrnlmp.pdb

    Loaded symbol image file: ntkrnlmp.exe

    Mapped memory image file: C:\ProgramData\Dbg\sym\ntoskrnl.exe\ED9DC31E1046000\ntoskrnl.exe

    Image path: ntkrnlmp.exe

    Image name: ntkrnlmp.exe

    Browse all global symbols functions data

    Image was built with /Brepro flag.

    Timestamp: ED9DC31E This is a reproducible build file hash, not a timestamp

    CheckSum: 00A5F2BD

    ImageSize: 01046000

    File version: 10.0.19041.631

    Product version: 10.0.19041.631

    File flags: 0 Mask 3F

    File OS: 40004 NT Win32

    File type: 1.0 App

    File date: 00000000.00000000

    Translations: 0409.04b0

    Information from resource tables:

    CompanyName: Microsoft Corporation

    ProductName: Microsoft® Windows® Operating System

    InternalName: ntkrnlmp.exe

    OriginalFilename: ntkrnlmp.exe

    ProductVersion: 10.0.19041.631

    FileVersion: 10.0.19041.631 WinBuild.160101.0800

    FileDescription: NT Kernel & System

    LegalCopyright: © Microsoft Corporation. All rights reserved.

    NatVis script unloaded from 'C:\Program Files\WindowsApps\Microsoft.WinDbg_1.2103.1004.0_neutral__8wekyb3d8bbwe\amd64\Visualizers\atlmfc.natvis'

    NatVis script unloaded from 'C:\Program Files\WindowsApps\Microsoft.WinDbg_1.2103.1004.0_neutral__8wekyb3d8bbwe\amd64\Visualizers\ObjectiveC.natvis'

    NatVis script unloaded from 'C:\Program Files\WindowsApps\Microsoft.WinDbg_1.2103.1004.0_neutral__8wekyb3d8bbwe\amd64\Visualizers\concurrency.natvis'

    NatVis script unloaded from 'C:\Program Files\WindowsApps\Microsoft.WinDbg_1.2103.1004.0_neutral__8wekyb3d8bbwe\amd64\Visualizers\cpp_rest.natvis'

    NatVis script unloaded from 'C:\Program Files\WindowsApps\Microsoft.WinDbg_1.2103.1004.0_neutral__8wekyb3d8bbwe\amd64\Visualizers\Kernel.natvis'

    NatVis script unloaded from 'C:\Program Files\WindowsApps\Microsoft.WinDbg_1.2103.1004.0_neutral__8wekyb3d8bbwe\amd64\Visualizers\stl.natvis'

    NatVis script unloaded from 'C:\Program Files\WindowsApps\Microsoft.WinDbg_1.2103.1004.0_neutral__8wekyb3d8bbwe\amd64\Visualizers\Windows.Data.Json.natvis'

    NatVis script unloaded from 'C:\Program Files\WindowsApps\Microsoft.WinDbg_1.2103.1004.0_neutral__8wekyb3d8bbwe\amd64\Visualizers\Windows.Devices.Geolocation.natvis'

    NatVis script unloaded from 'C:\Program Files\WindowsApps\Microsoft.WinDbg_1.2103.1004.0_neutral__8wekyb3d8bbwe\amd64\Visualizers\Windows.Devices.Sensors.natvis'

    NatVis script unloaded from 'C:\Program Files\WindowsApps\Microsoft.WinDbg_1.2103.1004.0_neutral__8wekyb3d8bbwe\amd64\Visualizers\Windows.Media.natvis'

    NatVis script unloaded from 'C:\Program Files\WindowsApps\Microsoft.WinDbg_1.2103.1004.0_neutral__8wekyb3d8bbwe\amd64\Visualizers\windows.natvis'

    NatVis script unloaded from 'C:\Program Files\WindowsApps\Microsoft.WinDbg_1.2103.1004.0_neutral__8wekyb3d8bbwe\amd64\Visualizers\winrt.natvis'



    Microsoft R Windows Debugger Version 10.0.21306.1007 AMD64

    Copyright c Microsoft Corporation. All rights reserved.





    Loading Dump File [C:\Windows\Minidump\040521-5390-01.dmp]

    Mini Kernel Dump File: Only registers and stack trace are available





    ************* Path validation summary **************

    Response Time ms Location

    Deferred srv*

    Symbol search path is: srv*

    Executable search path is:

    Windows 10 Kernel Version 19041 MP 12 procs Free x64

    Product: WinNt, suite: TerminalServer SingleUserTS Personal

    Edition build lab: 19041.1.amd64fre.vb_release.191206-1406

    Machine Name:

    Kernel base = 0xfffff804`5f400000 PsLoadedModuleList = 0xfffff804`6002a3b0

    Debug session time: Mon Apr 5 09:11:27.339 2021 UTC - 5:00

    System Uptime: 0 days 0:05:11.035

    Loading Kernel Symbols

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

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

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

    Loading User Symbols

    Loading unloaded module list

    ......

    For analysis of this file, run !analyze -v

    nt!KeBugCheckEx:

    fffff804`5f7f5210 48894c2408 mov qword ptr [rsp+8],rcx ss:0018:fffff804`6307ae20=0000000000000133

    0: 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: fffff804600fb320, 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 ***

    *** ***

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

    *** WARNING: Unable to verify checksum for win32k.sys



    KEY_VALUES_STRING: 1



    Key : Analysis.CPU.mSec

    Value: 5265



    Key : Analysis.DebugAnalysisManager

    Value: Create



    Key : Analysis.Elapsed.mSec

    Value: 12243



    Key : Analysis.Init.CPU.mSec

    Value: 452



    Key : Analysis.Init.Elapsed.mSec

    Value: 17440



    Key : Analysis.Memory.CommitPeak.Mb

    Value: 102



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



    DPC_TIMEOUT_TYPE: SINGLE_DPC_TIMEOUT_EXCEEDED



    TRAP_FRAME: fffff8046306ac90 -- .trap 0xfffff8046306ac90

    NOTE: The trap frame does not contain all registers.

    Some register values may be zeroed or incorrect.

    rax=00000007566d0003 rbx=0000000000000000 rcx=ffff800fd70febc0

    rdx=ffff800f00000000 rsi=0000000000000000 rdi=0000000000000000

    rip=fffff8045f7fd147 rsp=fffff8046306ae20 rbp=0000000000000001

    r8=ffff800f00000000 r9=ffff800fda3a7ac0 r10=ffff800fd70febc0

    r11=000000000000004f r12=0000000000000000 r13=0000000000000000

    r14=0000000000000000 r15=0000000000000000

    iopl=0 nv up ei ng nz na po nc

    nt!ExpInterlockedPopEntrySListFault:

    fffff804`5f7fd147 498b08 mov rcx,qword ptr [r8] ds:ffff800f`00000000=????????????????

    Resetting default scope



    BLACKBOXBSD: 1 !blackboxbsd





    BLACKBOXNTFS: 1 !blackboxntfs





    BLACKBOXPNP: 1 !blackboxpnp





    BLACKBOXWINLOGON: 1



    CUSTOMER_CRASH_COUNT: 1



    PROCESS_NAME: System



    STACK_TEXT:

    fffff804`6307ae18 fffff804`5f887372 : 00000000`00000133 00000000`00000000 00000000`00000501 00000000`00000500 : nt!KeBugCheckEx

    fffff804`6307ae20 fffff804`5f726853 : 00000113`327640fc fffff804`5b510180 00000000`00000000 fffff804`5b510180 : nt!KeAccumulateTicks+0x15e2c2

    fffff804`6307ae80 fffff804`5f72633a : fffff804`600f38c0 fffff804`6306ab80 fffff804`6ecd2700 00000000`00006300 : nt!KeClockInterruptNotify+0x453

    fffff804`6307af30 fffff804`5f62ecd5 : fffff804`600f38c0 fffff804`6307af40 00000000`0000000c ffffcb53`32eec707 : nt!HalpTimerClockIpiRoutine+0x1a

    fffff804`6307af60 fffff804`5f7f6cba : fffff804`6306ab80 fffff804`600f38c0 00000000`00000001 00000000`00000000 : nt!KiCallInterruptServiceRoutine+0xa5

    fffff804`6307afb0 fffff804`5f7f7227 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiInterruptSubDispatchNoLockNoEtw+0xfa

    fffff804`6306ab00 fffff804`5f803315 : ffff800f`0000000b ffff800f`00000000 fffff804`00000000 fffff804`6306ace8 : nt!KiInterruptDispatchNoLockNoEtw+0x37

    fffff804`6306ac90 fffff804`5f7fd147 : 00000000`00000000 fffff804`625b23af ffff800f`dbefa5e0 ffff800f`d7d0a8e8 : nt!KiPageFault+0x315

    fffff804`6306ae20 fffff804`625b23af : ffff800f`dbefa5e0 ffff800f`d7d0a8e8 fffff804`00000000 00000000`00000000 : nt!ExpInterlockedPopEntrySListFault

    fffff804`6306ae30 fffff804`6298135c : 00000000`00000000 ffff800f`db679070 ffff800f`dae5e100 00000000`00000000 : NETIO!WfpNblInfoAlloc+0x6f

    fffff804`6306ae70 fffff804`629812bb : 00000000`00000000 ffff800f`daf7c720 ffff800f`dae5e100 00000000`00000000 : fwpkclnt!FwppNetBufferListAssociateContext+0x7c

    fffff804`6306af10 fffff804`5c6243bd : fffff804`6306b160 ffff800f`dc9d30a0 fffff804`6306b1f0 fffff804`6306afd8 : fwpkclnt!FwpsNetBufferListAssociateContext1+0x7b

    fffff804`6306af70 fffff804`625c8cee : 00000000`00000000 fffff804`6306b079 00000000`0000004e fffff804`6306b340 : Ndu!NduOutboundTransportClassify+0x24d

    fffff804`6306b010 fffff804`626c3ffb : 00000000`00000000 00000000`00000000 ffff800f`dc4f1a20 ffff800f`dc4f1a20 : NETIO!KfdClassify2+0x19e

    fffff804`6306b0e0 fffff804`626c322b : ffff800f`d7d0a9c8 00000000`00000007 ffff800f`da3b5000 ffff800f`d7d5f000 : tcpip!IppInspectLocalDatagramsOut+0x6cb

    fffff804`6306b3b0 fffff804`626c1d99 : 00000000`00000000 00000000`00000000 fffff804`62883000 ffff800f`dc4f1a20 : tcpip!IppSendDatagramsCommon+0x41b

    fffff804`6306b530 fffff804`626a103d : ffff800f`dbefa520 00000000`00000028 00000000`00000000 ffff800f`dbde5990 : tcpip!IpNlpFastSendDatagram+0x349

    fffff804`6306b5f0 fffff804`626a3206 : ffff800f`dbde5990 00000000`00000000 00000000`33e653db fffff804`62883368 : tcpip!TcpTcbHeaderSend+0x5cd

    fffff804`6306b8a0 fffff804`62708a52 : ffff800f`d2fdf500 00000000`00005000 00000000`00000000 ffff800f`d7d5f001 : tcpip!TcpReceive+0x4d6

    fffff804`6306b990 fffff804`626c9b30 : ffff800f`d8166780 fffff804`626c6f00 00000029`00000000 ffff800f`d2e5ba60 : tcpip!TcpNlClientReceiveDatagrams+0x22

    fffff804`6306b9d0 fffff804`626c647b : 00000000`00000001 fffff804`6306bb00 00000000`00000000 ffff800f`d7d5f000 : tcpip!IppProcessDeliverList+0xc0

    fffff804`6306bab0 fffff804`626c59ff : fffff804`62883000 ffff800f`d7db38e0 ffff800f`d7d5f000 ffff800f`da725c00 : tcpip!IppReceiveHeaderBatch+0x21b

    fffff804`6306bbb0 fffff804`626c2d9c : ffff800f`d8ef2f20 ffff800f`d8166780 00000000`00000001 00000000`00000000 : tcpip!IppFlcReceivePacketsCore+0x32f

    fffff804`6306bcd0 fffff804`6270efcf : ffff800f`d8166780 00000000`00000000 fffff804`6306bda1 00000000`00000000 : tcpip!IpFlcReceivePackets+0xc

    fffff804`6306bd00 fffff804`6270e5cc : fffff804`5f7f1301 ffff800f`d8fa3800 fffff804`62701a50 fffff804`6306c0dc : tcpip!FlpReceiveNonPreValidatedNetBufferListChain+0x26f

    fffff804`6306be00 fffff804`5f60d468 : ffff800f`d7ddbea0 00000000`00000002 fffff804`60127600 fffff804`6306c0f8 : tcpip!FlReceiveNetBufferListChainCalloutRoutine+0x17c

    fffff804`6306bf50 fffff804`5f60d3dd : fffff804`6270e450 fffff804`6306c0f8 ffff800f`d2cfe4d0 fffff804`628518c4 : nt!KeExpandKernelStackAndCalloutInternal+0x78

    fffff804`6306bfc0 fffff804`627015ed : 00000000`00000028 fffff804`62766b2a ffff800f`d8166900 fffff804`6298142f : nt!KeExpandKernelStackAndCalloutEx+0x1d

    fffff804`6306c000 fffff804`62700ccd : 00000000`00000001 fffff804`6306c160 ffff800f`d8fa38a0 fffff804`6306c170 : tcpip!NetioExpandKernelStackAndCallout+0x8d

    fffff804`6306c060 fffff804`62441eb0 : ffff800f`d82d6081 00000000`00000001 ffff800f`d7ea4070 fffff804`6306c470 : tcpip!FlReceiveNetBufferListChain+0x46d

    fffff804`6306c310 fffff804`62441ccb : ffff800f`d8fc4c00 fffff804`0000dd01 fffff804`00000000 00000000`00000001 : ndis!ndisMIndicateNetBufferListsToOpen+0x140

    fffff804`6306c3f0 fffff804`62447ef0 : ffff800f`d80141a0 ffff800f`d8166701 ffff800f`d80141a0 00000000`00000001 : ndis!ndisMTopReceiveNetBufferLists+0x22b

    fffff804`6306c470 fffff804`6247dee3 : ffff800f`d8166780 fffff804`6306c541 00000000`00000000 ffff800f`d83a8320 : ndis!ndisCallReceiveHandler+0x60

    fffff804`6306c4c0 fffff804`62444a94 : 00000000`000048c1 00000000`00000001 ffff800f`d80141a0 00000000`00000001 : ndis!ndisInvokeNextReceiveHandler+0x1df

    fffff804`6306c590 fffff804`6ec361d8 : ffff800f`d80a9000 ffff800f`d80a9000 00000000`00000000 ffff800f`d80a95f0 : ndis!NdisMIndicateReceiveNetBufferLists+0x104

    fffff804`6306c620 fffff804`6ec21dc8 : 00000000`00000000 00000000`ad9a1c01 ffff800f`00000400 fffff804`6306c790 : rt640x64!MpHandleRecvIntPriVLanJumbo+0x2c4

    fffff804`6306c710 fffff804`62483879 : 00000000`00000000 ffff800f`d81ec4f0 ffff800f`00000000 00000000`ffffffff : rt640x64!MPHandleInterrupt+0x398

    fffff804`6306c780 fffff804`5f6e535e : fffff804`5b513240 00000000`00000000 00000000`00000004 fffff804`5b510180 : ndis!ndisInterruptDpc+0x3c189

    fffff804`6306c860 fffff804`5f6e4644 : 00000000`00000000 00000000`00000000 00000000`00140001 00000000`00000000 : nt!KiExecuteAllDpcs+0x30e

    fffff804`6306c9d0 fffff804`5f7f8d7e : 00000000`00000000 fffff804`5b510180 fffff804`60127600 ffff800f`da663080 : nt!KiRetireDpcList+0x1f4

    fffff804`6306cc60 00000000`00000000 : fffff804`6306d000 fffff804`63067000 00000000`00000000 00000000`00000000 : nt!KiIdleLoop+0x9e





    SYMBOL_NAME: NETIO!WfpNblInfoAlloc+6f



    MODULE_NAME: NETIO



    IMAGE_NAME: NETIO.SYS



    IMAGE_VERSION: 10.0.19041.867



    STACK_COMMAND: .thread ; .cxr ; kb



    BUCKET_ID_FUNC_OFFSET: 6f



    FAILURE_BUCKET_ID: 0x133_DPC_NETIO!WfpNblInfoAlloc



    OS_VERSION: 10.0.19041.1



    BUILDLAB_STR: vb_release



    OSPLATFORM_TYPE: x64



    OSNAME: Windows 10



    FAILURE_ID_HASH: {4517527a-bccb-804d-edb3-bfe381d04b2e}



    Followup: MachineOwner

    ---------

    :)
     
    MikeC18, Apr 5, 2021
    #1
  2. ANDE_11228
    Ande_11228 Win User

    BSOD - Ram issue or driver issue?

    I've been consistently BSODing or the computer completely freezes with the audio stuck these past few days.

    There's been a few different error codes like...

    • Memory_Management
    • Faulty Hardware Corrupted Page
    • Kmode_Exception_Not_Handled
    • Driver_Verifier_Detected_Violation
    There were only 2 dmp files created but, they're linked below.

    DMP

    I've tried running memory diagnostics, updating drivers and disk cleanup. Not sure what else the issue might be, could anyone provide some suggestions?
     
    Ande_11228, Apr 5, 2021
    #2
  3. FELIXBACHER
    FelixBacher Win User
    Need somebody analyzing this dmp file after constant crashes

    Hey guys, so my PC is BSODing every 5 minutes after boot, even after a complete clean install of Win10

    Here is a dmp. file, would be grateful if someone helped me here.

    033020-6703-01.dmp
     
    FelixBacher, Apr 5, 2021
    #3
  4. GOLDEN
    Golden Win User

    BSODing, dmp readouts

    BSOD - Gaming PC is getting old

    From the screencapture image, the 0x9F with parameter 1 =3 suggests the problem is a 3rd party driver. You need to upload the .dmp file so someone can analyse it further to see if they can determine which driver is at fault.

    I also suggest following the steps posted in post #6.
     
    Golden, Apr 5, 2021
    #4
Thema:

BSODing, dmp readouts

Loading...

  1. BSODing, dmp readouts - Similar Threads - BSODing dmp readouts

  2. Continuous BSODing

    in Windows 10 Software and Apps
    Continuous BSODing: Hello! I've been using my 2022 ROG Flow X16 GV601RW for a few months I bought it in october 2022 and now it's constantly having BSODs which seemingly come from nowhere. The stop code is always DPC_WATCHDOG_VIOLATION, and I searched it up online and checked solutions. I...

  3. Continuous BSODing

    in Windows 10 Gaming
    Continuous BSODing: Hello! I've been using my 2022 ROG Flow X16 GV601RW for a few months I bought it in october 2022 and now it's constantly having BSODs which seemingly come from nowhere. The stop code is always DPC_WATCHDOG_VIOLATION, and I searched it up online and checked solutions. I...

  4. Problem with Joystick HID descriptor readout

    in Windows 10 Drivers and Hardware
    Problem with Joystick HID descriptor readout: I bought a used Joystick Speedlink Phantom Hawk, which I can't return. The Z-Rotation Axis twist axis has a weird offset and doesn't read out the full Motion, it is centred at readout 180, and only uses about 20-30% of the IRL range. I tried everything conventional, and...

  5. Bsoding Laptop

    in Windows 10 BSOD Crashes and Debugging
    Bsoding Laptop: My PC keeps bsdoing ive run driver ive tried everythingi can think of to fix it. These are some mini dumps i zipped. https://drive.google.com/file/d/1C0Sut3n_dmSfF29IqtjpmaxUrI6_pQAK/view?usp=sharing...

  6. PC BSODING

    in Windows 10 BSOD Crashes and Debugging
    PC BSODING: My pc blue screens often, i built myself and have tried many solutions, no ram errors have shown up yet on memtests These are the recent dmp files https://1drv.ms/u/s!AuS1QHFoglP5qDei9aUcINqL87cl?e=3edFLH and here are all of them...

  7. PC BSODING

    in Windows 10 Drivers and Hardware
    PC BSODING: https://1drv.ms/u/s!AuS1QHFoglP5pmd6IlqKsEqj-XOO?e=iIFXkq These are the dmp files My pc has been crashing at least once a day but often crashes more than once, once it starts....

  8. PC BSODING

    in Windows 10 BSOD Crashes and Debugging
    PC BSODING: Hi so I put in some new RAM and i plugged in and unplugged ram while the psu was still on but previous to that i had been turning it off. Now my PC blue screens often at least once a day. Here are the dumps and the event, the event ID is 41 and here are the dmp files...

  9. Windows BSODing

    in Windows 10 Ask Insider
    Windows BSODing: I don’t know if this is the right subreddit for this, but there isn’t an r/windows support so oh well. Over the past 3 days my computer has BSODed 3 times. Here is what I know: 1st: The error code all 3 times was “ERROR: PAGE_FAULT_IN_NONPAGED_AREA” or something along those...

  10. Task Manager GPU readout not correct.

    in Windows 10 BSOD Crashes and Debugging
    Task Manager GPU readout not correct.: Hello! I've got a 2-GPU system that I'm using to run Folding@Home. This, naturally, fully loads both graphics cards. However, Windows Task Manager only shows a 0-2% load on the cards. This also occurred when running a video game for a more normal GPU task. Radeon Settings,...