System keeps crashing.

Question

System keeps crashing.

Anonymous

Recently I have done an upgrade on my computer and upgraded the power supply/graphics card. Ever since then, I've been having crashes. I have done clean installations of my drivers and even clean installed the OS to try and mitigate the crashing but it keeps happening.

Below is the DMP file that is being generated, is there anything I should be worried about?

Microsoft (R) Windows Debugger Version 10.0.25200.1003 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.

************* 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 = 0xfffff802`1a800000 PsLoadedModuleList = 0xfffff802`1b42a290
Debug session time: Fri Mar 31 13:25:41.053 2023 (UTC - 4:00)
System Uptime: 0 days 8:01:18.731
Loading Kernel Symbols
...............................................................
...Page 48a026 not present in the dump file. Type ".hh dbgerr004" for details
.......Page 4827e2 not present in the dump file. Type ".hh dbgerr004" for details
......................................................
...........................................................
Loading User Symbols

Loading unloaded module list
..................
For analysis of this file, run !analyze -v
nt!KeBugCheckEx:
fffff802`1abfbbf0 48894c2408      mov     qword ptr [rsp+8],rcx ss:0018:fffffa82`a282d8c0=000000000000001e

Loading Dump File [C:\Windows\MEMORY.DMP]
Kernel Bitmap Dump File: Kernel address space is available, User address space may not be available.

Can't set dump file contexts
MachineInfo::SetContext failed - Thread: 00000224AF1A39F0  Handle: b  Id: b - Error == 0x8000FFFF

************* 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 = 0xfffff802`1a800000 PsLoadedModuleList = 0xfffff802`1b42a290
Debug session time: Fri Mar 31 13:25:41.053 2023 (UTC - 4:00)
System Uptime: 0 days 8:01:18.731
Loading Kernel Symbols
...............................................................
...Page 48a026 not present in the dump file. Type ".hh dbgerr004" for details
.......Page 4827e2 not present in the dump file. Type ".hh dbgerr004" for details
......................................................
...........................................................
Loading User Symbols

Loading unloaded module list
..................
nt!KeBugCheckEx:
fffff802`1abfbbf0 48894c2408      mov     qword ptr [rsp+8],rcx ss:0018:fffffa82`a282d8c0=000000000000001e
||1:10: 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: ffffffffc000001d, The exception code that was not handled
Arg2: fffff8021f4914c8, The address that the exception occurred at
Arg3: fffffa82a282e8f8, Parameter 0 of the exception
Arg4: fffffa82a282e130, Parameter 1 of the exception

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: ExceptionRecord                               ***
***                                                                   ***
*************************************************************************
*************************************************************************
***                                                                   ***
***                                                                   ***
***    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: ContextRecord                                 ***
***                                                                   ***
*************************************************************************
*************************************************************************
***                                                                   ***
***                                                                   ***
***    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: ExceptionRecord                               ***
***                                                                   ***
*************************************************************************
*************************************************************************
***                                                                   ***
***                                                                   ***
***    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: ContextRecord                                 ***
***                                                                   ***
*************************************************************************
Page 481773 not present in the dump file. Type ".hh dbgerr004" for details
Page 481773 not present in the dump file. Type ".hh dbgerr004" for details
Page 481773 not present in the dump file. Type ".hh dbgerr004" for details
Page 481773 not present in the dump file. Type ".hh dbgerr004" for details
Page 481773 not present in the dump file. Type ".hh dbgerr004" for details
Page 481773 not present in the dump file. Type ".hh dbgerr004" for details
Page 481773 not present in the dump file. Type ".hh dbgerr004" for details
Page 481773 not present in the dump file. Type ".hh dbgerr004" for details
Page 481773 not present in the dump file. Type ".hh dbgerr004" for details
Page 481773 not present in the dump file. Type ".hh dbgerr004" for details
Page 481773 not present in the dump file. Type ".hh dbgerr004" for details
Page 481773 not present in the dump file. Type ".hh dbgerr004" for details
Page 481773 not present in the dump file. Type ".hh dbgerr004" for details
Page 481773 not present in the dump file. Type ".hh dbgerr004" for details

KEY_VALUES_STRING: 1

    Key  : Analysis.CPU.mSec
    Value: 3656

    Key  : Analysis.DebugAnalysisManager
    Value: Create

    Key  : Analysis.Elapsed.mSec
    Value: 5583

    Key  : Analysis.IO.Other.Mb
    Value: 2

    Key  : Analysis.IO.Read.Mb
    Value: 0

    Key  : Analysis.IO.Write.Mb
    Value: 13

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

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

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

    Key  : Bugcheck.Code.DumpHeader
    Value: 0x1e

    Key  : Bugcheck.Code.KiBugCheckData
    Value: 0x1e

    Key  : Bugcheck.Code.Register
    Value: 0x1e

    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

FILE_IN_CAB:  MEMORY.DMP

BUGCHECK_CODE:  1e

BUGCHECK_P1: ffffffffc000001d

BUGCHECK_P2: fffff8021f4914c8

BUGCHECK_P3: fffffa82a282e8f8

BUGCHECK_P4: fffffa82a282e130

EXCEPTION_PARAMETER1:  fffffa82a282e8f8

EXCEPTION_PARAMETER2:  fffffa82a282e130

BLACKBOXBSD: 1 (!blackboxbsd)

BLACKBOXNTFS: 1 (!blackboxntfs)

BLACKBOXPNP: 1 (!blackboxpnp)

BLACKBOXWINLOGON: 1

PROCESS_NAME:  System

FAILED_INSTRUCTION_ADDRESS: 
wfplwfs!L2InspectNetBufferListsFast+158
fffff802`1f4914c8 304c8b15        xor     byte ptr [rbx+rcx*4+15h],cl

STACK_TEXT:  
fffffa82`a282d8b8 fffff802`1ad12eff     : 00000000`0000001e ffffffff`c000001d fffff802`1f4914c8 fffffa82`a282e8f8 : nt!KeBugCheckEx
fffffa82`a282d8c0 fffff802`1ac174b6     : fffffa82`a282e130 fffff802`1ab116a5 fffffa82`a282eb30 fffff802`1f4914c8 : nt!KiFatalFilter+0x1f
fffffa82`a282d900 fffff802`1abcfaff     : fffff802`00000002 fffff802`1a8d0944 fffffa82`a2829000 fffffa82`a2830000 : nt!KeExpandKernelStackAndCalloutInternal$filt$0+0x16
fffffa82`a282d940 fffff802`1ac062df     : fffff802`1a8d0944 fffffa82`a282df20 fffff802`1abcfa60 00000000`00000000 : nt!_C_specific_handler+0x9f
fffffa82`a282d9b0 fffff802`1aae58c7     : fffffa82`a282df20 00000000`00000000 fffffa82`a282eda0 fffff802`1aaad478 : nt!RtlpExecuteHandlerForException+0xf
fffffa82`a282d9e0 fffff802`1aae7896     : fffffa82`a282e8f8 fffffa82`a282e630 fffffa82`a282e8f8 00000000`00000000 : nt!RtlDispatchException+0x297
fffffa82`a282e100 fffff802`1ac0fd6c     : ffff860f`822bc9d0 ffff860f`7eee7cd0 00000000`00000000 fffff802`1ef13a81 : nt!KiDispatchException+0x186
fffffa82`a282e7c0 fffff802`1ac09aa3     : 00000000`00000000 fffff802`00000001 00000000`00000000 fffffa82`a282eae0 : nt!KiExceptionDispatch+0x12c
fffffa82`a282e9a0 fffff802`1f4914c8     : ffff860f`779b0a20 ffff860f`7c98aad0 00000000`00000000 fffff802`1ef13a81 : nt!KiInvalidOpcodeFault+0x323
fffffa82`a282eb30 fffff802`1f491270     : ffff860f`779aea20 00000000`00000001 00000000`00000000 00000000`00000001 : wfplwfs!L2InspectNetBufferListsFast+0x158
fffffa82`a282ec40 fffff802`1eed7ef1     : ffff860f`00000001 ffff860f`835f0d90 00000000`00000000 ffff860f`88bcd701 : wfplwfs!LwfLowerRecvNetBufferLists+0xd0
fffffa82`a282ed00 fffff802`1eee837e     : ffff860f`863d5040 fffffa82`a282eed1 fffffa82`a282eeb0 00000000`00000000 : ndis!ndisCallReceiveHandler+0x61
fffffa82`a282ed50 fffff802`1aaad478     : fffffa82`a282eed1 ffff860f`779b0a20 00000000`00000000 00000000`00000002 : ndis!ndisDataPathExpandStackCallback+0x3e
fffffa82`a282eda0 fffff802`1aaad3ed     : fffff802`1eee8340 fffffa82`a282eeb0 ffff860f`835f0d90 00000000`00000000 : nt!KeExpandKernelStackAndCalloutInternal+0x78
fffffa82`a282ee10 fffff802`1ef0e04c     : ffff860f`779aea20 00000000`00000000 ffff860f`7795b010 fffff802`31df6400 : nt!KeExpandKernelStackAndCalloutEx+0x1d
fffffa82`a282ee50 fffff802`1eed4a94     : 00000000`001c33ae 00000000`00000000 ffff860f`7cf521a0 00000000`00000000 : ndis!ndisInvokeNextReceiveHandler+0x23c
fffffa82`a282ef20 fffff802`438632d0     : 00000000`00000000 ffff860f`7d065010 fffffa82`a282f010 ffff860f`835f0d90 : ndis!NdisMIndicateReceiveNetBufferLists+0x104
fffffa82`a282efb0 fffff802`43828251     : ffffa001`00000001 00000000`00000000 ffff860f`88bcd9b0 00000000`00000000 : wdiwifi!CPort::IndicateFrames+0x2d8
fffffa82`a282f050 fffff802`4380bbb7     : ffff860f`835f0d90 fffffa82`a282f179 ffff860f`7d9ffbb0 fffff802`1ac042b2 : wdiwifi!CAdapter::IndicateFrames+0x141
fffffa82`a282f0c0 fffff802`4380c2f6     : ffff860f`7d9ffbb0 00000000`00000000 ffff860f`7d9ffbb0 fffff802`4436ec27 : wdiwifi!CRxMgr::RxProcessAndIndicateNblChain+0x7f7
fffffa82`a282f1e0 fffff802`43808192     : ffff860f`835f0d90 fffffa82`a282f320 00000000`00000000 00000000`00000023 : wdiwifi!CRxMgr::RxInOrderDataInd+0x35a
fffffa82`a282f280 fffff802`441366eb     : 00000000`00000000 00000000`00000003 ffff860f`7c028d40 ffff860f`7c842040 : wdiwifi!AdapterRxInorderDataInd+0x92
fffffa82`a282f2d0 fffff802`44136b04     : 00000000`00000000 ffff860e`ffffffff ffff860f`7daf81b0 00000000`00000000 : Netwtw04+0x566eb
fffffa82`a282f320 fffff802`1ef09dc2     : ffff860f`7cd31c40 ffff860f`7c842040 fffff802`1ef09db0 ffff860f`778df530 : Netwtw04+0x56b04
fffffa82`a282f390 fffff802`1aa43f85     : 00000000`00000000 ffff860f`7d08fb50 ffff860f`7cd31c40 fffff802`31d45440 : ndis!ndisDispatchIoWorkItem+0x12
fffffa82`a282f3c0 fffff802`1aa8e5c5     : ffff860f`863d5040 ffff860f`863d5040 fffff802`1aa43e50 00000000`00000000 : nt!IopProcessWorkItem+0x135
fffffa82`a282f430 fffff802`1ab265f5     : ffff860f`863d5040 00000000`00000080 ffff860f`778cd080 00000000`00000000 : nt!ExpWorkerThread+0x105
fffffa82`a282f4d0 fffff802`1ac04828     : ffffa001`0e0f6180 ffff860f`863d5040 fffff802`1ab265a0 00000000`00000246 : nt!PspSystemThreadStartup+0x55
fffffa82`a282f520 00000000`00000000     : fffffa82`a2830000 fffffa82`a2829000 00000000`00000000 00000000`00000000 : nt!KiStartSystemThread+0x28

SYMBOL_NAME:  wfplwfs!L2InspectNetBufferListsFast+158

MODULE_NAME: wfplwfs

IMAGE_NAME:  wfplwfs.sys

STACK_COMMAND:  .cxr; .ecxr ; kb

BUCKET_ID_FUNC_OFFSET:  158

FAILURE_BUCKET_ID:  0x1E_C000001D_BAD_IP_wfplwfs!L2InspectNetBufferListsFast

OS_VERSION:  10.0.19041.1

BUILDLAB_STR:  vb_release

OSPLATFORM_TYPE:  x64

OSNAME:  Windows 10

FAILURE_ID_HASH:  {c4aa7d24-d129-9216-af5e-707f6df40b0c}

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

Locked Question. This question was migrated from the Microsoft Support Community. You can vote on whether it's helpful, but you can't add comments or replies or follow the question.

0 comments

1 answer

Answer 1

Anonymous

Please run the V2 log collector and post a share link into this thread using one drive, drop box, or google drive.

BSOD - Posting Instructions - Windows 10 Forums (tenforums.com)

BSOD - Posting Instructions | Windows 11 Forum (elevenforum.com)

0 comments

Share via

System keeps crashing.

1 answer