Windows 10: Getting BSODs at random intervals, ntkrnlmp.exe

Hi. I recently built a new PC, and it's working just fine, except that I randomly am experiencing BSODs. Usually they happen around once or twice per week. The failures all seem to be related to "ntkrnlmp.exe", but I am getting different codes each BSOD. Googling my issue I find that people are pointing to all sorts of issues, whether it's related to GPU drivers, memory, or whatnot. I'm coming here and asking because I'm hoping I can get some more accurate insight before I start troubleshooting myself.

Some things that I suspect could be causing issues:

I'm running an RTX3080 - even if the drivers are up to date, it's still a new card.

The 3080 is paired with an RMX650 PSU rated 100w below Nvidia's own reccomendation. I'm gaming and stress testing just fine, and from what I gather - if my GPU would overdraw I shouldn't BSOD, rather the PC should just reboot.

I've enabled XMP for my memory, but only to run the sticks at advertised clock speeds.


I analyzed a few logs using WinDbg and this is what came out of it:

1


******************************************************************************** ** Bugcheck Analysis ** ********************************************************************************KERNEL_SECURITY_CHECK_FAILURE 139A kernel component has corrupted a critical data structure. The corruptioncould potentially allow a malicious user to gain control of this machine.Arguments:Arg1: 0000000000000003, A LIST_ENTRY has been corrupted i.e. double remove.Arg2: ffffdb0007947160, Address of the trap frame for the exception that caused the bugcheckArg3: ffffdb00079470b8, Address of the exception record for the exception that caused the bugcheckArg4: 0000000000000000, ReservedDebugging Details:------------------KEY_VALUES_STRING: 1 Key : Analysis.CPU.mSec Value: 2655 Key : Analysis.DebugAnalysisProvider.CPP Value: Create: 8007007e on GUSTOSANCHEZ Key : Analysis.DebugData Value: CreateObject Key : Analysis.DebugModel Value: CreateObject Key : Analysis.Elapsed.mSec Value: 2740 Key : Analysis.Memory.CommitPeak.Mb Value: 87 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: 139BUGCHECK_P1: 3BUGCHECK_P2: ffffdb0007947160BUGCHECK_P3: ffffdb00079470b8BUGCHECK_P4: 0TRAP_FRAME: ffffdb0007947160 -- .trap 0xffffdb0007947160NOTE: The trap frame does not contain all registers.Some register values may be zeroed or incorrect.rax=ffffdc0440c685d0 rbx=0000000000000000 rcx=0000000000000003rdx=0000000000000000 rsi=0000000000000000 rdi=0000000000000000rip=fffff8042f60cd4a rsp=ffffdb00079472f0 rbp=0000000000000705 r8=0000000000000000 r9=7fff820343d2c1b8 r10=0000000000000000r11=0000000000000000 r12=0000000000000000 r13=0000000000000000r14=0000000000000000 r15=0000000000000000iopl=0 nv up ei ng nz na po cyFLTMGR!DeleteStreamListCtrlCallback+0x7a:fffff804`2f60cd4a cd29 int 29hResetting default scopeEXCEPTION_RECORD: ffffdb00079470b8 -- .exr 0xffffdb00079470b8ExceptionAddress: fffff8042f60cd4a FLTMGR!DeleteStreamListCtrlCallback+0x000000000000007a ExceptionCode: c0000409 Security check failure or stack buffer overrun ExceptionFlags: 00000001NumberParameters: 1 Parameter[0]: 0000000000000003Subcode: 0x3 FAST_FAIL_CORRUPT_LIST_ENTRY BLACKBOXBSD: 1 !blackboxbsdBLACKBOXNTFS: 1 !blackboxntfsBLACKBOXPNP: 1 !blackboxpnpBLACKBOXWINLOGON: 1PROCESS_NAME: SystemERROR_CODE: NTSTATUS 0xc0000409 - En verskridning av en stackbaserad buffert uppt cktes. Detta kan ge anv ndare som vill v lla skada kontroll ver programmet.EXCEPTION_CODE_STR: c0000409EXCEPTION_PARAMETER1: 0000000000000003EXCEPTION_STR: 0xc0000409STACK_TEXT: ffffdb00`07946e38 fffff804`30007769 : 00000000`00000139 00000000`00000003 ffffdb00`07947160 ffffdb00`079470b8 : nt!KeBugCheckExffffdb00`07946e40 fffff804`30007b90 : 00000000`00000004 ffff8203`2d1b1d50 00000000`00000001 ffffdb00`079472c0 : nt!KiBugCheckDispatch+0x69ffffdb00`07946f80 fffff804`30005f23 : 00000028`00000000 00000018`00000028 ffffffd8`00000000 00000000`00000000 : nt!KiFastFailDispatch+0xd0ffffdb00`07947160 fffff804`2f60cd4a : 00000000`00000705 ffffdc04`40c685a8 ffffdc04`31b6a060 ffffdc04`40c685a0 : nt!KiRaiseSecurityCheckFailure+0x323ffffdb00`079472f0 fffff804`302b9069 : ffff8203`43d2c1a8 ffffdc04`40c685a8 ffff8203`00000000 ffffdb00`079477f0 : FLTMGR!DeleteStreamListCtrlCallback+0x7affffdb00`07947330 fffff804`3591c10b : ffff8203`43d2c170 ffffdb00`07947478 ffffdb00`079477f0 00000000`00000703 : nt!FsRtlTeardownPerStreamContexts+0xc9ffffdb00`07947370 fffff804`3591be96 : ffff8203`43d2c170 ffff8203`29a1d208 ffff8203`00000000 ffffdc04`31ba65a8 : Ntfs!NtfsDeleteScb+0x17bffffdb00`07947410 fffff804`35827b95 : ffff8203`43d2c010 ffff8203`43d2c170 ffff8203`43d2c170 ffff8203`43d2c170 : Ntfs!NtfsRemoveScb+0x66ffffdb00`07947470 fffff804`3591bc2c : ffffdb00`079477f0 fffff804`35967930 ffff8203`43d2c010 ffff8203`43d2c500 : Ntfs!NtfsPrepareFcbForRemoval+0x75ffffdb00`079474b0 fffff804`3582bd40 : ffffdb00`079477f0 ffffdb00`079475b2 ffff8203`43d2c528 ffff8203`43d2c010 : Ntfs!NtfsTeardownStructures+0x9cffffdb00`07947530 fffff804`3594b4d7 : ffffdb00`07947600 ffff8203`00000000 00000000`00000000 fffff804`00000000 : Ntfs!NtfsDecrementCloseCounts+0xb0ffffdb00`07947570 fffff804`35947ff1 : ffffdb00`079477f0 ffff8203`43d2c170 ffff8203`43d2c010 ffffdc04`31ba5180 : Ntfs!NtfsCommonClose+0x467ffffdb00`07947650 fffff804`359679b8 : 00000000`0000001c fffff804`30924440 00000000`00000000 00000000`00000000 : Ntfs!NtfsFspCloseInternal+0x241ffffdb00`079477b0 fffff804`2fe25975 : ffffdc04`4847d040 fffff804`302e4b10 ffffdc04`2aeb5ca0 00000000`00000000 : Ntfs!NtfsFspClose+0x88ffffdb00`07947a70 fffff804`2ff17e25 : ffffdc04`4847d040 00000000`00000080 ffffdc04`2aeb6040 00000000`00000000 : nt!ExpWorkerThread+0x105ffffdb00`07947b10 fffff804`2fffcdd8 : ffffae01`3f980180 ffffdc04`4847d040 fffff804`2ff17dd0 00000000`00000000 : nt!PspSystemThreadStartup+0x55ffffdb00`07947b60 00000000`00000000 : ffffdb00`07948000 ffffdb00`07941000 00000000`00000000 00000000`00000000 : nt!KiStartSystemThread+0x28SYMBOL_NAME: nt!KiFastFailDispatch+d0MODULE_NAME: ntIMAGE_NAME: ntkrnlmp.exeSTACK_COMMAND: .thread ; .cxr ; kbBUCKET_ID_FUNC_OFFSET: d0FAILURE_BUCKET_ID: 0x139_3_CORRUPT_LIST_ENTRY_nt!KiFastFailDispatchOS_VERSION: 10.0.19041.1BUILDLAB_STR: vb_releaseOSPLATFORM_TYPE: x64OSNAME: Windows 10FAILURE_ID_HASH: {3aede96a-54dd-40d6-d4cb-2a161a843851}Followup: MachineOwner---------


2


******************************************************************************** ** Bugcheck Analysis ** ********************************************************************************PAGE_FAULT_IN_NONPAGED_AREA 50Invalid system memory was referenced. This cannot be protected by try-except.Typically the address is just plain bad or it is pointing at freed memory.Arguments:Arg1: ffffb50034d00000, memory referenced.Arg2: 0000000000000002, value 0 = read operation, 1 = write operation.Arg3: fffff80134f21ccf, If non-zero, the instruction address which referenced the bad memory address.Arg4: 0000000000000000, reservedDebugging Details:------------------*** WARNING: Unable to verify timestamp for nvlddmkm.sysCould not read faulting driver name*** WARNING: Unable to verify checksum for win32k.sysKEY_VALUES_STRING: 1 Key : Analysis.CPU.mSec Value: 4343 Key : Analysis.DebugAnalysisProvider.CPP Value: Create: 8007007e on GUSTOSANCHEZ Key : Analysis.DebugData Value: CreateObject Key : Analysis.DebugModel Value: CreateObject Key : Analysis.Elapsed.mSec Value: 49130 Key : Analysis.Memory.CommitPeak.Mb Value: 85 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: 50BUGCHECK_P1: ffffb50034d00000BUGCHECK_P2: 2BUGCHECK_P3: fffff80134f21ccfBUGCHECK_P4: 0READ_ADDRESS: fffff8011bcfa390: Unable to get MiVisibleStateUnable to get NonPagedPoolStartUnable to get NonPagedPoolEndUnable to get PagedPoolStartUnable to get PagedPoolEndfffff8011bc0f330: Unable to get Flags value from nt!KdVersionBlockfffff8011bc0f330: Unable to get Flags value from nt!KdVersionBlockunable to get nt!MmSpecialPagesInUse ffffb50034d00000 MM_INTERNAL_CODE: 0CUSTOMER_CRASH_COUNT: 1PROCESS_NAME: SystemTRAP_FRAME: fffffd07881ea020 -- .trap 0xfffffd07881ea020NOTE: The trap frame does not contain all registers.Some register values may be zeroed or incorrect.rax=ffffb50034cff000 rbx=0000000000000000 rcx=ffff8408f0cd4c38rdx=000000000006f00d rsi=0000000000000000 rdi=0000000000000000rip=fffff80134f21ccf rsp=fffffd07881ea1b0 rbp=000000000000000b r8=0000000000000400 r9=000000000006e05e r10=0000000000000000r11=fffffd07881ea1d0 r12=0000000000000000 r13=0000000000000000r14=0000000000000000 r15=0000000000000000iopl=0 nv up ei ng nz na pe ncnvlddmkm+0x7b1ccf:fffff801`34f21ccf 42891480 mov dword ptr [rax+r8*4],edx ds:ffffb500`34d00000=????????Resetting default scopeSTACK_TEXT: fffffd07`881e9d78 fffff801`1b41eb6b : 00000000`00000050 ffffb500`34d00000 00000000`00000002 fffffd07`881ea020 : nt!KeBugCheckExfffffd07`881e9d80 fffff801`1b20c960 : fffffd07`881e9f90 00000000`00000002 fffffd07`881ea0a0 00000000`00000000 : nt!MiSystemFault+0x1f435bfffffd07`881e9e80 fffff801`1b40395e : fffff801`347839e0 fffff801`3519ec6a fffff801`351a836a fffff801`3543dd57 : nt!MmAccessFault+0x400fffffd07`881ea020 fffff801`34f21ccf : ffff8408`f0cd4c38 00000000`008d9ea4 fffffb09`d207846c 00000000`00000018 : nt!KiPageFault+0x35efffffd07`881ea1b0 ffff8408`f0cd4c38 : 00000000`008d9ea4 fffffb09`d207846c 00000000`00000018 00000000`0000000b : nvlddmkm+0x7b1ccffffffd07`881ea1b8 00000000`008d9ea4 : fffffb09`d207846c 00000000`00000018 00000000`0000000b fffff801`352144ba : 0xffff8408`f0cd4c38fffffd07`881ea1c0 fffffb09`d207846c : 00000000`00000018 00000000`0000000b fffff801`352144ba 00000000`00000003 : 0x8d9ea4fffffd07`881ea1c8 00000000`00000018 : 00000000`0000000b fffff801`352144ba 00000000`00000003 ffff8408`f56a6000 : 0xfffffb09`d207846cfffffd07`881ea1d0 00000000`0000000b : fffff801`352144ba 00000000`00000003 ffff8408`f56a6000 ffff8408`f56a6003 : 0x18fffffd07`881ea1d8 fffff801`352144ba : 00000000`00000003 ffff8408`f56a6000 ffff8408`f56a6003 00000000`0000000f : 0xbfffffd07`881ea1e0 00000000`00000003 : ffff8408`f56a6000 ffff8408`f56a6003 00000000`0000000f 00000000`00000000 : nvlddmkm+0xaa44bafffffd07`881ea1e8 ffff8408`f56a6000 : ffff8408`f56a6003 00000000`0000000f 00000000`00000000 ffffb500`35540000 : 0x3fffffd07`881ea1f0 ffff8408`f56a6003 : 00000000`0000000f 00000000`00000000 ffffb500`35540000 00000002`00000001 : 0xffff8408`f56a6000fffffd07`881ea1f8 00000000`0000000f : 00000000`00000000 ffffb500`35540000 00000002`00000001 00000040`00000000 : 0xffff8408`f56a6003fffffd07`881ea200 00000000`00000000 : ffffb500`35540000 00000002`00000001 00000040`00000000 ffff8408`f0cd4d18 : 0xfSYMBOL_NAME: nvlddmkm+7b1ccfMODULE_NAME: nvlddmkmIMAGE_NAME: nvlddmkm.sysSTACK_COMMAND: .thread ; .cxr ; kbBUCKET_ID_FUNC_OFFSET: 7b1ccfFAILURE_BUCKET_ID: AV_INVALID_nvlddmkm!unknown_functionOS_VERSION: 10.0.19041.1BUILDLAB_STR: vb_releaseOSPLATFORM_TYPE: x64OSNAME: Windows 10FAILURE_ID_HASH: {df018c6e-47ce-6234-d97b-e5d8699ade66}Followup: MachineOwner---------

3



******************************************************************************** ** Bugcheck Analysis ** ********************************************************************************SYSTEM_SERVICE_EXCEPTION 3bAn exception happened while executing a system service routine.Arguments:Arg1: 00000000c0000005, Exception code that caused the bugcheckArg2: fffff80453f5ccf1, Address of the instruction which caused the bugcheckArg3: fffffc0bd4f01d60, Address of the context record for the exception that caused the bugcheckArg4: 0000000000000000, zero.Debugging Details:------------------KEY_VALUES_STRING: 1 Key : Analysis.CPU.mSec Value: 2703 Key : Analysis.DebugAnalysisProvider.CPP Value: Create: 8007007e on GUSTOSANCHEZ Key : Analysis.DebugData Value: CreateObject Key : Analysis.DebugModel Value: CreateObject Key : Analysis.Elapsed.mSec Value: 17035 Key : Analysis.Memory.CommitPeak.Mb Value: 77 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: 3bBUGCHECK_P1: c0000005BUGCHECK_P2: fffff80453f5ccf1BUGCHECK_P3: fffffc0bd4f01d60BUGCHECK_P4: 0CONTEXT: fffffc0bd4f01d60 -- .cxr 0xfffffc0bd4f01d60rax=0000000000000000 rbx=ffffc8000c3af3c0 rcx=ffffc8000c3af3f0rdx=0000000000000000 rsi=0000000000000000 rdi=ffffc8000c3af3f0rip=fffff80453f5ccf1 rsp=fffffc0bd4f02760 rbp=fffffc0bd4f02939 r8=0000000000000000 r9=0000000000000000 r10=fffff80453f5cce0r11=0000000000000000 r12=0000000000000000 r13=ffffde091b1f9b40r14=ffffc8000c3af3c0 r15=0000000000000000iopl=0 nv up ei ng nz na po nccs=0010 ss=0018 ds=002b es=002b fs=0053 gs=002b efl=00050286nt!IopDeleteDriver+0x11:fffff804`53f5ccf1 488b4828 mov rcx,qword ptr [rax+28h] ds:002b:00000000`00000028=????????????????Resetting default scopeBLACKBOXBSD: 1 !blackboxbsdBLACKBOXNTFS: 1 !blackboxntfsBLACKBOXPNP: 1 !blackboxpnpBLACKBOXWINLOGON: 1CUSTOMER_CRASH_COUNT: 1PROCESS_NAME: svchost.exeSTACK_TEXT: fffffc0b`d4f02760 fffff804`53dfaef0 : ffffc800`0c3af3c0 fffffc0b`d4f02939 00000000`00000000 00000000`00000000 : nt!IopDeleteDriver+0x11fffffc0b`d4f027b0 fffff804`53a61277 : 00000000`00000000 00000000`00000000 fffffc0b`d4f02939 ffffc800`0c3af3f0 : nt!ObpRemoveObjectRoutine+0x80fffffc0b`d4f02810 fffff804`53e2887e : ffffc80f`fc95b640 00000000`00000001 ffffffff`ffffffff ffffde09`1196e820 : nt!ObfDereferenceObjectWithTag+0xc7fffffc0b`d4f02850 fffff804`53e2c4fc : 00000000`00000208 00000000`00000000 00000000`00000000 fffff804`53e358fa : nt!ObCloseHandleTableEntry+0x29efffffc0b`d4f02990 fffff804`53c071b5 : 00000000`00000000 fffffc0b`d4f02a80 fffffc0b`d4f02a80 ffffc800`0ecf7340 : nt!NtClose+0xecfffffc0b`d4f02a00 00007ffa`efc4c194 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceCopyEnd+0x25000000e0`b267f878 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x00007ffa`efc4c194SYMBOL_NAME: nt!IopDeleteDriver+11MODULE_NAME: ntIMAGE_NAME: ntkrnlmp.exeIMAGE_VERSION: 10.0.19041.685STACK_COMMAND: .cxr 0xfffffc0bd4f01d60 ; kbBUCKET_ID_FUNC_OFFSET: 11FAILURE_BUCKET_ID: 0x3B_c0000005_nt!IopDeleteDriverOS_VERSION: 10.0.19041.1BUILDLAB_STR: vb_releaseOSPLATFORM_TYPE: x64OSNAME: Windows 10FAILURE_ID_HASH: {90ff16cc-c90a-bdfb-f031-796195b5424e}Followup: MachineOwner---------

4


******************************************************************************** ** Bugcheck Analysis ** ********************************************************************************KERNEL_SECURITY_CHECK_FAILURE 139A kernel component has corrupted a critical data structure. The corruptioncould potentially allow a malicious user to gain control of this machine.Arguments:Arg1: 0000000000000003, A LIST_ENTRY has been corrupted i.e. double remove.Arg2: ffff9d06554ef250, Address of the trap frame for the exception that caused the bugcheckArg3: ffff9d06554ef1a8, Address of the exception record for the exception that caused the bugcheckArg4: 0000000000000000, ReservedDebugging Details:------------------*** WARNING: Unable to verify checksum for win32k.sysKEY_VALUES_STRING: 1 Key : Analysis.CPU.mSec Value: 3312 Key : Analysis.DebugAnalysisProvider.CPP Value: Create: 8007007e on GUSTOSANCHEZ Key : Analysis.DebugData Value: CreateObject Key : Analysis.DebugModel Value: CreateObject Key : Analysis.Elapsed.mSec Value: 11978 Key : Analysis.Memory.CommitPeak.Mb Value: 89 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: 139BUGCHECK_P1: 3BUGCHECK_P2: ffff9d06554ef250BUGCHECK_P3: ffff9d06554ef1a8BUGCHECK_P4: 0TRAP_FRAME: ffff9d06554ef250 -- .trap 0xffff9d06554ef250NOTE: The trap frame does not contain all registers.Some register values may be zeroed or incorrect.rax=ffffdb8351c6a530 rbx=0000000000000000 rcx=0000000000000003rdx=ffffdb8353d743d0 rsi=0000000000000000 rdi=0000000000000000rip=fffff80745d1b378 rsp=ffff9d06554ef3e0 rbp=fffff80745d67930 r8=ffff9d06554ef3f0 r9=7fffdb8353d74160 r10=fffff807402600d0r11=ffffdb8353d74408 r12=0000000000000000 r13=0000000000000000r14=0000000000000000 r15=0000000000000000iopl=0 nv up ei ng nz na po cyNtfs!NtfsFullDeleteLcb+0x1f8:fffff807`45d1b378 cd29 int 29hResetting default scopeEXCEPTION_RECORD: ffff9d06554ef1a8 -- .exr 0xffff9d06554ef1a8ExceptionAddress: fffff80745d1b378 Ntfs!NtfsFullDeleteLcb+0x00000000000001f8 ExceptionCode: c0000409 Security check failure or stack buffer overrun ExceptionFlags: 00000001NumberParameters: 1 Parameter[0]: 0000000000000003Subcode: 0x3 FAST_FAIL_CORRUPT_LIST_ENTRY BLACKBOXBSD: 1 !blackboxbsdBLACKBOXNTFS: 1 !blackboxntfsBLACKBOXPNP: 1 !blackboxpnpBLACKBOXWINLOGON: 1CUSTOMER_CRASH_COUNT: 1PROCESS_NAME: SystemERROR_CODE: NTSTATUS 0xc0000409 - En verskridning av en stackbaserad buffert uppt cktes. Detta kan ge anv ndare som vill v lla skada kontroll ver programmet.EXCEPTION_CODE_STR: c0000409EXCEPTION_PARAMETER1: 0000000000000003EXCEPTION_STR: 0xc0000409STACK_TEXT: ffff9d06`554eef28 fffff807`40407769 : 00000000`00000139 00000000`00000003 ffff9d06`554ef250 ffff9d06`554ef1a8 : nt!KeBugCheckExffff9d06`554eef30 fffff807`40407b90 : 00000000`00000000 ffff8d0b`00000000 ffffdb83`38a00100 fffff807`4024caf2 : nt!KiBugCheckDispatch+0x69ffff9d06`554ef070 fffff807`40405f23 : ffff9d06`554ef7f0 00000000`00000000 ffff8d0b`1c972060 ffff8d0b`247756e8 : nt!KiFastFailDispatch+0xd0ffff9d06`554ef250 fffff807`45d1b378 : fffff807`45d67930 ffffdb83`00000001 ffffdb83`00000000 ffffdb83`00000000 : nt!KiRaiseSecurityCheckFailure+0x323ffff9d06`554ef3e0 fffff807`45c27748 : ffff9d06`554ef7f0 ffffdb83`53d74170 ffffdb83`53d74170 ffff8d0b`1c9a85a0 : Ntfs!NtfsFullDeleteLcb+0x1f8ffff9d06`554ef410 fffff807`45d1bc7a : ffff9d06`554ef7f0 ffff8d0b`1c9a7180 ffffdb83`51c6a010 ffffdb83`51c6a528 : Ntfs!NtfsTeardownFromLcb+0x1a8ffff9d06`554ef4b0 fffff807`45c2bd40 : ffff9d06`554ef7f0 ffff9d06`554ef5b2 00000000`00000000 ffffdb83`51c6a010 : Ntfs!NtfsTeardownStructures+0xeaffff9d06`554ef530 fffff807`45d4b4d7 : ffff9d06`554ef600 ffffdb83`51c6a010 00000000`00000000 ffffdb83`51c6a000 : Ntfs!NtfsDecrementCloseCounts+0xb0ffff9d06`554ef570 fffff807`45d47ff1 : ffff9d06`554ef7f0 ffffdb83`51c6a170 ffffdb83`51c6a010 ffff8d0b`1c9a7180 : Ntfs!NtfsCommonClose+0x467ffff9d06`554ef650 fffff807`45d679b8 : 00000000`0000001c fffff807`40d24440 00000000`00000000 00000000`00000000 : Ntfs!NtfsFspCloseInternal+0x241ffff9d06`554ef7b0 fffff807`40225975 : ffff8d0b`261cb080 fffff807`45d67930 ffff8d0b`15c9b8d0 fffff807`00000000 : Ntfs!NtfsFspClose+0x88ffff9d06`554efa70 fffff807`40317e25 : ffff8d0b`261cb080 00000000`00000080 ffff8d0b`15cca040 3c5f81bb`fce2b1a4 : nt!ExpWorkerThread+0x105ffff9d06`554efb10 fffff807`403fcdd8 : fffff807`3e67d180 ffff8d0b`261cb080 fffff807`40317dd0 addb6bb9`6402dd6a : nt!PspSystemThreadStartup+0x55ffff9d06`554efb60 00000000`00000000 : ffff9d06`554f0000 ffff9d06`554e9000 00000000`00000000 00000000`00000000 : nt!KiStartSystemThread+0x28SYMBOL_NAME: nt!KiFastFailDispatch+d0MODULE_NAME: ntIMAGE_NAME: ntkrnlmp.exeIMAGE_VERSION: 10.0.19041.685STACK_COMMAND: .thread ; .cxr ; kbBUCKET_ID_FUNC_OFFSET: d0FAILURE_BUCKET_ID: 0x139_3_CORRUPT_LIST_ENTRY_nt!KiFastFailDispatchOS_VERSION: 10.0.19041.1BUILDLAB_STR: vb_releaseOSPLATFORM_TYPE: x64OSNAME: Windows 10FAILURE_ID_HASH: {3aede96a-54dd-40d6-d4cb-2a161a843851}Followup: MachineOwner---------



:)

 

Random BSOD while browsing internet


BitDefender is nothing special. mwac.sys causes BSODs anywhere.
A tiny documentation can be found here: Solved Random BSODs - Windows 10 Forums
In that very thread, the suggested action apparently worked.

The storage and network filters of any third party antivirus can cause BSODs. Neither MBAM nor BitDefender is any special. For a regular antivirus, it may be shifted to an alternative; but MBAM has no alternative. So a clean install of the said program is the most feasible first step.
As far as the first step is not failing, it is better to not think for the second step. Because the BSODs are not universal, failure at the first step is not universal; and success at the second step is also not universal.
That is why I posted that my suggestion may work, or may not. Let us see where it goes.

 

BSOD UNEXPECTED_KERNEL_MODE_TRAP

Hi, OttOiToto

The problem is caused by (ntkrnlmp.exe)

Check this link, I hope it helps

https://www.thewindowsclub.com/fix-ntkrnlmp-exe...

Note: This is a non-Microsoft website. The page appears to be providing accurate, safe information. Watch out for ads on the site that may advertise products frequently classified as a PUP (Potentially Unwanted Products). Thoroughly research any product advertised
on the site before you decide to download and install it.

Let us know if these steps help you to resolve the issue.

 

Random BSOD at random intervals

Hello, I have been having troubles as of recent with random BSOD errors that happen at random times.

I initially thought that it may have something to do with my ram as I have had troubles with it in the past, although I have used the Windows Memory Diagnostic tool and no errors came up. Some of the BSOD include "WORKER_THRED_RETURNED_AT_BAD_IRQL", "SYSTEM_SERVICE_EXCEPTION",
"KMODE_EXCEPTION_NOT_HANDLED", "SYSTEM_THREAD_EXCEPTION_NOT_HANDLED" etc.

It doesnt generally impact my use as it doesn't happen all the time, only about once if I use my computer for more than four hours, sometimes less. Sometimes it will happen twice in a row. I just hope that I can somehow stop this as it would be nice to not
have them every so often.

Below is a link to my minidump files in a OneDrive:

Minidump