Keep getting different BSOD error codes, PLEASE HELP

Question

Copy of my WinDgb debugger report

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 (16 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Edition build lab: 19041.1.amd64fre.vb_release.191206-1406
Machine Name:
Kernel base = 0xfffff803`34c00000 PsLoadedModuleList = 0xfffff803`3582a310
Debug session time: Thu Mar 16 18:14:52.836 2023 (UTC - 4:00)
System Uptime: 0 days 0:18:04.460
Loading Kernel Symbols
...............................................................
................................................................
....................................................
Loading User Symbols
PEB is paged out (Peb.Ldr = 00000000`00277018).  Type ".hh dbgerr001" for details
Loading unloaded module list
......
For analysis of this file, run !analyze -v
nt!KeBugCheckEx:
fffff803`34ffa110 48894c2408      mov     qword ptr [rsp+8],rcx ss:0018:ffffeb0a`0644c620=000000000000000a
13: kd> !analyze -v
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

IRQL_NOT_LESS_OR_EQUAL (a)
An attempt was made to access a pageable (or completely invalid) address at an
interrupt request level (IRQL) that is too high.  This is usually
caused by drivers using improper addresses.
If a kernel debugger is available get the stack backtrace.
Arguments:
Arg1: 00000000000045f8, memory referenced
Arg2: 00000000000000ff, IRQL
Arg3: 0000000000000000, bitfield :
bit 0 : value 0 = read operation, 1 = write operation
bit 3 : value 0 = not an execute operation, 1 = execute operation (only on chips which support this level of status)
Arg4: fffff80334e7e803, address which referenced memory

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

KEY_VALUES_STRING: 1

    Key  : Analysis.CPU.mSec
    Value: 3077

    Key  : Analysis.DebugAnalysisManager
    Value: Create

    Key  : Analysis.Elapsed.mSec
    Value: 3169

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

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

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

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

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

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

    Key  : Bugcheck.Code.DumpHeader
    Value: 0xa

    Key  : Bugcheck.Code.KiBugCheckData
    Value: 0xa

    Key  : Bugcheck.Code.Register
    Value: 0xa

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

BUGCHECK_P1: 45f8

BUGCHECK_P2: ff

BUGCHECK_P3: 0

BUGCHECK_P4: fffff80334e7e803

READ_ADDRESS:  00000000000045f8 

BLACKBOXBSD: 1 (!blackboxbsd)

BLACKBOXNTFS: 1 (!blackboxntfs)

BLACKBOXPNP: 1 (!blackboxpnp)

BLACKBOXWINLOGON: 1

PROCESS_NAME:  Spotify.exe

TRAP_FRAME:  ffffeb0a0644c760 -- (.trap 0xffffeb0a0644c760)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=0000000000004000 rbx=0000000000000000 rcx=000000000000000e
rdx=ffffa7045e04e9c8 rsi=0000000000000000 rdi=0000000000000000
rip=fffff80334e7e803 rsp=ffffeb0a0644c8f0 rbp=0000000000000001
 r8=0000000000000020  r9=ffffa7045e04e918 r10=0000000000017cb2
r11=0000000000000003 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0         nv up di pl nz na po nc
nt!KiSwapThread+0x993:
fffff803`34e7e803 488b80f8050000  mov     rax,qword ptr [rax+5F8h] ds:00000000`000045f8=????????????????
Resetting default scope

STACK_TEXT:  
ffffeb0a`0644c618 fffff803`3500e129     : 00000000`0000000a 00000000`000045f8 00000000`000000ff 00000000`00000000 : nt!KeBugCheckEx
ffffeb0a`0644c620 fffff803`35009ce3     : ffffc901`a44e3180 fffff803`350027d2 000f8067`b4bbbdff 00000000`00000000 : nt!KiBugCheckDispatch+0x69
ffffeb0a`0644c760 fffff803`34e7e803     : ffffc901`a4146180 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiPageFault+0x463
ffffeb0a`0644c8f0 fffff803`34e7d89f     : ffffa704`5e04e080 fffff803`34f30cd7 00000000`00000000 00000000`00989600 : nt!KiSwapThread+0x993
ffffeb0a`0644c9a0 fffff803`34ec1c62     : 00000000`00000099 00000000`00000000 ffffa704`00000001 00000000`77b24660 : nt!KiCommitThreadWait+0x14f
ffffeb0a`0644ca40 fffff803`352bcfbf     : 00000000`0035a000 fffff803`3500d752 ffffeb0a`0644cb00 00000000`00000002 : nt!KeDelayExecutionThread+0x122
ffffeb0a`0644cad0 fffff803`3500d8f8     : 00000000`116ffeac 00000000`00000000 ffffffff`fffe7960 00000000`00000000 : nt!NtDelayExecution+0x5f
ffffeb0a`0644cb00 00000000`77b21cfc     : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceCopyEnd+0x28
00000000`113ff308 00000000`00000000     : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x77b21cfc

SYMBOL_NAME:  nt!KiSwapThread+993

MODULE_NAME: nt

IMAGE_NAME:  ntkrnlmp.exe

STACK_COMMAND:  .cxr; .ecxr ; kb

BUCKET_ID_FUNC_OFFSET:  993

FAILURE_BUCKET_ID:  AV_nt!KiSwapThread

OS_VERSION:  10.0.19041.1

BUILDLAB_STR:  vb_release

OSPLATFORM_TYPE:  x64

OSNAME:  Windows 10

FAILURE_ID_HASH:  {3a5eca23-a992-0c0e-a0ce-d48add0d8eda}

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

Answer 1

Hi Colin,

Welcome to Microsoft Community.

I'm Hahn and I'm here to help you with your concern.

The error message you provided suggests that the Spotify.exe process is causing a system crash or a blue screen of death (BSOD) with the nt!KiSwapThread+993 error code.

If you have more blue screen errors, please let me know.

This error code indicates that there was a problem with the thread scheduling mechanism in the Windows kernel. Specifically, the error occurred when the kernel attempted to swap one thread out of the processor and another thread in, but encountered a problem during the process.

There are several possible causes of this error, including:

Spotify.exe has multiple processes running, taking up a lot of memory and CPU resources, which prevents the system from switching between threads properly.

Spotify.exe or other programs have memory leaks or corrupt drivers that affect the stability of the system.

Spotify.exe or other programs have compatibility problems with the system or hardware, causing abnormal errors.

To troubleshoot this issue, you can try the following steps:

Update or reinstall Spotify.exe

Update your device drivers: Check if there are any available updates for your device drivers, and install them if there are.

Scan your system for malware and viruses: Use an antivirus software to scan your system for any malware or viruses, and remove them if found.

Check your hardware: Run a hardware diagnostic test to check if any hardware components are failing, and replace them if necessary.

If there is anything not clear, please do not hesitate to let me know.

Your Sincerely

Hahn - MSFT | Microsoft Community Support Specialist