BSOD while booting

Question

Hi, my Windows 11 laptop runs into BSOD almost all the time while booting for the past week. The error codes vary, but I've seen IRQL_NOT_LESS_OR_EQUAL, CLOCK_WATCHDOG_TIMEOUT, and some other codes.

Can someone please tell me know what was the problem? I suspect it is a driver's issue, but I am not able to point out which one.

Thank you very much.

Here is the link to the memory dump: MEMORY.DMP

Here is the analysis from WinDbg: Microsoft (R) Windows Debugger Version 10.0.22621.2428 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. Dump completed successfully, progress percentage: 100 ************* Path validation summary ************** Response Time (ms) Location Deferred SRV*C:\Windows\symbol_cache*http://msdl.microsoft.com/download/symbols Symbol search path is: SRV*C:\Windows\symbol_cache*http://msdl.microsoft.com/download/symbols Executable search path is: Windows 10 Kernel Version 22621 MP (16 procs) Free x64 Product: WinNt, suite: TerminalServer SingleUserTS Personal Edition build lab: 22621.1.amd64fre.ni_release.220506-1250 Machine Name: Kernel base = 0xfffff8053b600000 PsLoadedModuleList = 0xfffff8053c213130 Debug session time: Sat May 18 12:03:03.155 2024 (UTC - 7:00) System Uptime: 0 days 0:00:04.850 Loading Kernel Symbols ............................................................... ........................................ Loading User Symbols Loading unloaded module list .. For analysis of this file, run !analyze -v 12: 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: 0000000000000170, memory referenced Arg2: 0000000000000002, 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: fffff8053b83a740, address which referenced memory Debugging Details: ------------------ KEY_VALUES_STRING: 1 Key : Analysis.CPU.mSec Value: 1406 Key : Analysis.DebugAnalysisManager Value: Create Key : Analysis.Elapsed.mSec Value: 2770 Key : Analysis.Init.CPU.mSec Value: 1718 Key : Analysis.Init.Elapsed.mSec Value: 93937 Key : Analysis.Memory.CommitPeak.Mb Value: 101 Key : WER.OS.Branch Value: ni_release Key : WER.OS.Timestamp Value: 2022-05-06T12:50:00Z Key : WER.OS.Version Value: 10.0.22621.1 FILE_IN_CAB: MEMORY.DMP TAG_NOT_DEFINED_202b: *** Unknown TAG in analysis list 202b DUMP_FILE_ATTRIBUTES: 0x1800 BUGCHECK_CODE: a BUGCHECK_P1: 170 BUGCHECK_P2: 2 BUGCHECK_P3: 0 BUGCHECK_P4: fffff8053b83a740 READ_ADDRESS: 0000000000000170 BLACKBOXNTFS: 1 (!blackboxntfs) PROCESS_NAME: System TRAP_FRAME: fffff304997b5330 -- (.trap 0xfffff304997b5330) NOTE: The trap frame does not contain all registers. Some register values may be zeroed or incorrect. rax=0000000000000000 rbx=0000000000000000 rcx=000000000001536d rdx=0000000000000001 rsi=0000000000000000 rdi=0000000000000000 rip=fffff8053b83a740 rsp=fffff304997b54c0 rbp=fffff304997b55c0 r8=0000000000000000 r9=ffffa88df9afca50 r10=fffff805370f9d80 r11=fffff304997b5438 r12=0000000000000000 r13=0000000000000000 r14=0000000000000000 r15=0000000000000000 iopl=0 nv up ei pl nz na po nc nt!KiSwapThread+0x7f0: fffff8053b83a740 f6437004 test byte ptr [rbx+70h],4 ds:0000000000000070=?? Resetting default scope STACK_TEXT: fffff304997b51e8 fffff8053ba2de29 : 000000000000000a 0000000000000170 0000000000000002 0000000000000000 : nt!KeBugCheckEx fffff304997b51f0 fffff8053ba29289 : fffff805370f6180 fffff8053c34b040 fffff8053c34c700 fffff8053c34c700 : nt!KiBugCheckDispatch+0x69 fffff304997b5330 fffff8053b83a740 : 0000000000000020 0000000000000000 ffff48f200000006 0000000000000064 : nt!KiPageFault+0x489 fffff304997b54c0 fffff8053b83cbe7 : ffffa88df9ae9040 ffffa88d00000000 0000000000000000 0000000000000000 : nt!KiSwapThread+0x7f0 fffff304997b5610 fffff8053b8bfed6 : 0000000000000000 0000000000000001 ffff48f2000000b9 0000000002e4e41d : nt!KiCommitThreadWait+0x137 fffff304997b56c0 fffff8053b8bfb1a : ffffa88d00000000 fffff8053c23e900 fffff8053c23e900 0000000000000000 : nt!KeWaitForMultipleObjects+0x306 fffff304997b5920 fffff8053bd6004a : ffffffffffff3cb0 ffffa88df9ae9040 fffff304997b5ac0 ffffa88df9b102a0 : nt!PopFxProcessWorkPool+0xf6 fffff304997b5990 fffff8053b8d6d85 : ffffa88df9b102a0 ffffa88df9ae9000 ffffa88d00000000 ffffa88d00000000 : nt!PopFxPluginWork+0x2a fffff304997b59c0 fffff8053b96d8e7 : ffffa88df9ae9040 0000000000000ba0 ffffa88df9ae9040 fffff8053b8d6c30 : nt!ExpWorkerThread+0x155 fffff304997b5bb0 fffff8053ba1d0f4 : ffff97002bd97180 ffffa88df9ae9040 fffff8053b96d890 65ddcc07699dcc03 : nt!PspSystemThreadStartup+0x57 fffff304997b5c00 0000000000000000 : fffff304997b6000 fffff304997af000 0000000000000000 0000000000000000 : nt!KiStartSystemThread+0x34 SYMBOL_NAME: nt!KiSwapThread+7f0 MODULE_NAME: nt IMAGE_NAME: ntkrnlmp.exe IMAGE_VERSION: 10.0.22621.3593 STACK_COMMAND: .cxr; .ecxr ; kb BUCKET_ID_FUNC_OFFSET: 7f0 FAILURE_BUCKET_ID: AV_nt!KiSwapThread OS_VERSION: 10.0.22621.1 BUILDLAB_STR: ni_release OSPLATFORM_TYPE: x64 OSNAME: Windows 10 FAILURE_ID_HASH: {3a5eca23-a992-0c0e-a0ce-d48add0d8eda} Followup: MachineOwner ---------

Answer 1

Hi, thanks for reaching out. My name is Bernard a Windows fan like you. I'll be happy to help you out today.

I understand the issue you have, there is nothing to worry I am here to help, can you further check if you have more dump files on the PC? As per checking the Minidump files, it is only displaying general errors, in addition, can you please check the System logs on the PC so that we can further examine what is the root cause of the issue?

To do this kindly follow the steps from this link:

https://www.yourwindowsguide.com/2017/12/how-to...

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.

Then please upload it by following the steps from the link.

Let me know how it goes and I hope that helps.

Bernard