Keep Getting BSOD. Ran Device Verifier and detected error BSOD.

CraigTC

New member
May 12, 2021
1
0
0
Visit site
I really don't know if this is the right place to ask this question but I am on Windows 10 and keep getting BSODs. Ran Device Verifier and said it detected error. Ran restore point and used WinDbg to analyze minidump. Can anyone help me understand this result. Thanks.

Microsoft (R) Windows Debugger Version 10.0.21349.1004 AMD64
Copyright (c) Microsoft Corporation. All rights reserved.

Loading Dump File [C:\Windows\Minidump\051121-16015-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 (8 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS Personal
Edition build lab: 19041.1.amd64fre.vb_release.191206-1406
Machine Name:
Kernel base = 0xfffff804`36600000 PsLoadedModuleList = 0xfffff804`3722a490
Debug session time: Tue May 11 23:21:51.187 2021 (UTC - 4:00)
System Uptime: 0 days 10:36:19.030
Loading Kernel Symbols
...............................................................
................................................................
................................................................
..........
Loading User Symbols
Loading unloaded module list
.................
For analysis of this file, run !analyze -v
nt!KeBugCheckEx:
fffff804`369f5c50 48894c2408 mov qword ptr [rsp+8],rcx ss:0018:ffffa780`d1eee020=000000000000003b
7: kd>
7: kd> !analyze -v
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************

SYSTEM_SERVICE_EXCEPTION (3b)
An exception happened while executing a system service routine.
Arguments:
Arg1: 00000000c0000005, Exception code that caused the BugCheck
Arg2: fffff80436865892, Address of the instruction which caused the BugCheck
Arg3: ffffa780d1eee920, Address of the context record for the exception that caused the BugCheck
Arg4: 0000000000000000, zero.

Debugging Details:
------------------

KEY_VALUES_STRING: 1

Key : Analysis.CPU.mSec
Value: 4358

Key : Analysis.DebugAnalysisManager
Value: Create

Key : Analysis.Elapsed.mSec
Value: 16049

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

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

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

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: 3b

BUGCHECK_P1: c0000005

BUGCHECK_P2: fffff80436865892

BUGCHECK_P3: ffffa780d1eee920

BUGCHECK_P4: 0

CONTEXT: ffffa780d1eee920 -- (.cxr 0xffffa780d1eee920)
rax=0000000000000000 rbx=0000000000000102 rcx=0020000000000000
rdx=0000000000000001 rsi=ffffb90dba19a080 rdi=ffffb90dba19a180
rip=fffff80436865892 rsp=fffffa0aacd33920 rbp=0000000000000000
r8=ffffa780d1ece180 r9=0000000000000000 r10=0000000000000000
r11=fffff80436600000 r12=0000000000000001 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0 nv up ei pl nz na po nc
cs=0010 ss=0018 ds=002b es=002b fs=0053 gs=002b efl=00010206
nt!KiSwapThread+0x542:
fffff804`36865892 488901 mov qword ptr [rcx],rax ds:002b:00200000`00000000=????????????????
Resetting default scope

BLACKBOXBSD: 1 (!blackboxbsd)

BLACKBOXNTFS: 1 (!blackboxntfs)

BLACKBOXPNP: 1 (!blackboxpnp)

BLACKBOXWINLOGON: 1

CUSTOMER_CRASH_COUNT: 1

PROCESS_NAME: nvcontainer.exe

STACK_TEXT:
fffffa0a`acd33920 fffff804`36864d7f : 00000001`00000007 00000000`00000000 00200000`00000000 00000000`00000000 : nt!KiSwapThread+0x542
fffffa0a`acd339d0 fffff804`368fc4dc : ffffb90d`0000001e ffffb90d`00000000 fffffa0a`00000001 0000017b`ff1c61b8 : nt!KiCommitThreadWait+0x14f
fffffa0a`acd33a70 fffff804`36cbf360 : ffffb90d`ba19a080 fffffa0a`acd33b80 00000074`341ff980 0000017b`00000002 : nt!KeWaitForAlertByThreadId+0xc4
fffffa0a`acd33ad0 fffff804`36a075b8 : ffffb90d`00000000 fffffa0a`acd33b10 fffffff7`9e3b9800 fffffa0a`acd33b80 : nt!NtWaitForAlertByThreadId+0x30
fffffa0a`acd33b00 00007ffd`c5cf0604 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceCopyEnd+0x28
00000074`341ff8d8 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x00007ffd`c5cf0604

SYMBOL_NAME: nt!KiSwapThread+542

MODULE_NAME: nt

IMAGE_NAME: ntkrnlmp.exe

IMAGE_VERSION: 10.0.19041.870

STACK_COMMAND: .cxr 0xffffa780d1eee920 ; kb

BUCKET_ID_FUNC_OFFSET: 542

FAILURE_BUCKET_ID: 0x3B_c0000005_nt!KiSwapThread

OS_VERSION: 10.0.19041.1

BUILDLAB_STR: vb_release

OSPLATFORM_TYPE: x64

OSNAME: Windows 10

FAILURE_ID_HASH: {84555688-391b-94c0-6e71-1aa9cc17aed7}

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

Members online

Forum statistics

Threads
323,688
Messages
2,244,211
Members
428,098
Latest member
Linux86