Keep getting BSOD even though it's a clean install

Kris Romero 1 Reputation point
2022-08-18T00:50:12.237+00:00

I keep getting IRQL_NOT_LESS_OR_EQUAL BSOD on boot. I've tried to find where the problem is. I have fresh mobo, ssd, ram, gpu. Clean install, up to date drivers. did sfc, memtest. uninstalled kaspersky. removed some potentially faulty drivers/devices.

Microsoft (R) Windows Debugger Version 10.0.25136.1001 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*
Symbol search path is: srv*
Executable search path is:
Windows 10 Kernel Version 22000 MP (16 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Edition build lab: 22000.1.amd64fre.co_release.210604-1628
Machine Name:
Kernel base = 0xfffff8005d200000 PsLoadedModuleList = 0xfffff8005de296b0
Debug session time: Thu Aug 18 10:32:44.696 2022 (UTC + 10:00)
System Uptime: 0 days 0:00:10.346
Loading Kernel Symbols
...............................................................
................................................................
................................................................
...............
Loading User Symbols
PEB is paged out (Peb.Ldr = 00000000011d3018). Type ".hh dbgerr001" for details Loading unloaded module list ......... For analysis of this file, run !analyze -v nt!KeBugCheckEx: fffff8005d617d40 48894c2408 mov qword ptr [rsp+8],rcx ss:ffffc105`7c941440=000000000000000a
2: 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: 0000000000000004, 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: fffff8005d478055, address which referenced memory

Debugging Details:

------------------

KEY_VALUES_STRING: 1 

Key  : Analysis.CPU.mSec  
Value: 2265  

Key  : Analysis.DebugAnalysisManager  
Value: Create  

Key  : Analysis.Elapsed.mSec  
Value: 2330  

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

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

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

Key  : Bugcheck.Code.DumpHeader  
Value: 0xa  

Key  : Bugcheck.Code.KiBugCheckData  
Value: 0xa  

Key  : Bugcheck.Code.Register  
Value: 0xa  

Key  : Dump.Attributes.AsUlong  
Value: 1800  

Key  : WER.OS.Branch  
Value: co_release  

Key  : WER.OS.Timestamp  
Value: 2021-06-04T16:28:00Z  

Key  : WER.OS.Version  
Value: 10.0.22000.1

FILE_IN_CAB: MEMORY.DMP

DUMP_FILE_ATTRIBUTES: 0x1800

BUGCHECK_CODE: a

BUGCHECK_P1: 4

BUGCHECK_P2: 2

BUGCHECK_P3: 0

BUGCHECK_P4: fffff8005d478055

READ_ADDRESS: 0000000000000004

PROCESS_NAME: OriginWebHelperService.exe

TRAP_FRAME: ffffc1057c941580 -- (.trap 0xffffc1057c941580)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=fffff8005de51e00 rbx=0000000000000000 rcx=0000000000000000
rdx=0000000000000000 rsi=0000000000000000 rdi=0000000000000000
rip=fffff8005d478055 rsp=ffffc1057c941710 rbp=ffffc1057c941900
r8=00000000ffffffff r9=7fffffffffffffff r10=ffffe7004ed44eb0
r11=ffffb40000000000 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0 nv up ei pl nz na po nc
nt!MiResolveProtoPteFault+0x3c5:
fffff8005d478055 f7420400010000 test dword ptr [rdx+4],100h ds:0000000000000004=????????
Resetting default scope

STACK_TEXT:
ffffc1057c941438 fffff8005d62a9a9 : 000000000000000a 0000000000000004 0000000000000002 0000000000000000 : nt!KeBugCheckEx
ffffc1057c941440 fffff8005d626b00 : 0000000000000000 0000000000000000 ffffb400003b0688 0000000000000000 : nt!KiBugCheckDispatch+0x69
ffffc1057c941580 fffff8005d478055 : ffffc1057c941860 1a00000ff0267867 0000000000000000 0000000000000000 : nt!KiPageFault+0x440
ffffc1057c941710 fffff8005d4775a3 : ffffc1057c941860 0000000000000000 ffffc1057c941840 ffffb45a00000000 : nt!MiResolveProtoPteFault+0x3c5
ffffc1057c941800 fffff8005d475ba2 : 0000000000000100 0000000000000100 00000000c0000016 00000000760d0000 : nt!MiDispatchFault+0x1b3
ffffc1057c941940 fffff8005d6269f5 : ffff808b0a389080 ffff808b0a40caf0 000000000125fda0 0000000000000000 : nt!MmAccessFault+0x152
ffffc1057c941ae0 0000000076f240f2 : 0000000000000000 0000000000000000 0000000000000000 0000000000000000 : nt!KiPageFault+0x335
000000000135e780 0000000000000000 : 0000000000000000 0000000000000000 0000000000000000 0000000000000000 : 0x76f240f2

SYMBOL_NAME: nt!MiResolveProtoPteFault+3c5

MODULE_NAME: nt

STACK_COMMAND: .cxr; .ecxr ; kb

IMAGE_NAME: ntkrnlmp.exe

BUCKET_ID_FUNC_OFFSET: 3c5

FAILURE_BUCKET_ID: AV_nt!MiResolveProtoPteFault

OS_VERSION: 10.0.22000.1

BUILDLAB_STR: co_release

OSPLATFORM_TYPE: x64

OSNAME: Windows 10

FAILURE_ID_HASH: {2f2238e9-4751-e3c3-543c-b0cdf930b219}

Followup: MachineOwner

Windows 11
Windows 11
A Microsoft operating system designed for productivity, creativity, and ease of use.
8,143 questions
0 comments

2 answers

Sort by: Most helpful
Most helpful Newest Oldest
  1. Limitless Technology 39,351 Reputation points
    2022-08-18T15:36:17.7+00:00

    Hi there,

    These crashes are related to memory corruption and are probably caused by a driver.

    You can follow

    these below articles to find the driver and memory leak which is causing you this BSOD.

    Driver verifier is a utility built into the OS that will often find the driver/drivers that are the underlying

    cause of BSOD/Crashes.

    Driver Verifier-- tracking down a mis-behaving driver.

    https://answers.microsoft.com/en-us/windows/forum/all/driver-verifier-tracking-down-a-mis-behavin

    g/f5cb4faf-556b-4b6d-95b3-c48669e4c983

    Memtest is easy to use and is an accurate test of your computer memory. It can tell you if your

    memory is bad, a motherboard slot is bad, etc.

    Memory problems.

    https://answers.microsoft.com/en-us/windows/forum/all/memory-problems/21c3f63f-f570-4522-b2

    ef-ecc7b7ff6461

    ---------------------------------------------------------------------------------------------------------------------------------------------

    --If the reply is helpful, please Upvote and Accept it as an answer–

    0 comments
  2. Reza-Ameri 16,831 Reputation points
    2022-08-18T16:48:51.747+00:00

    Since this is fresh install try run Windows Update and download and install all update.
    In addition, try update drivers .

    0 comments