BSOD at completely random times

I have been getting a BSOD occasionally when playing Star Wars Outlaws. I had not noticed it before on any other game so I assumed the game was the cause. This morning I got one just browsing the internet, a couple of minutes after booting up my PC.

This is the minidump analysis:

************* Preparing the environment for Debugger Extensions Gallery repositories **************
ExtensionRepository : Implicit
UseExperimentalFeatureForNugetShare : true
AllowNugetExeUpdate : true
NonInteractiveNuget : true
AllowNugetMSCredentialProviderInstall : true
AllowParallelInitializationOfLocalRepositories : true
EnableRedirectToChakraJsProvider : false

-- Configuring repositories
----> Repository : LocalInstalled, Enabled: true
----> Repository : UserExtensions, Enabled: true

>>>>>>>>>>>>> Preparing the environment for Debugger Extensions Gallery repositories completed, duration 0.000 seconds

************* Waiting for Debugger Extensions Gallery to Initialize **************

>>>>>>>>>>>>> Waiting for Debugger Extensions Gallery to Initialize completed, duration 0.250 seconds
----> Repository : UserExtensions, Enabled: true, Packages count: 0
----> Repository : LocalInstalled, Enabled: true, Packages count: 46

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


Loading Dump File [C:\Windows\Minidump\012626-12078-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 26100 MP (16 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Kernel base = 0xfffff802`c6e00000 PsLoadedModuleList = 0xfffff802`c7cf4fc0
Debug session time: Mon Jan 26 08:34:45.955 2026 (UTC - 5:00)
System Uptime: 0 days 16:15:01.580
Loading Kernel Symbols
...............................................................
................................................................
................................................................
.................
Loading User Symbols
PEB is paged out (Peb.Ldr = 0000001a`b5a8b018). Type ".hh dbgerr001" for details
Loading unloaded module list
................................
For analysis of this file, run !analyze -v
nt!KeBugCheckEx:
fffff802`c72fb240 48894c2408 mov qword ptr [rsp+8],rcx ss:ffffae8e`3bf87450=000000000000000a
14: kd> !analyze -v
Loading Kernel Symbols
...............................................................
................................................................
................................................................
.................
Loading User Symbols
PEB is paged out (Peb.Ldr = 0000001a`b5a8b018). Type ".hh dbgerr001" for details
Loading unloaded module list
................................
*******************************************************************************
* *
* 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: fffffb4a425dc4b0, 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: fffff802c712b230, address which referenced memory

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


KEY_VALUES_STRING: 1

Key : Analysis.CPU.mSec
Value: 1421

Key : Analysis.Elapsed.mSec
Value: 2569

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

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

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

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

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

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

Key : Analysis.Version.DbgEng
Value: 10.0.29507.1001

Key : Analysis.Version.Description
Value: 10.2511.5.1 amd64fre

Key : Analysis.Version.Ext
Value: 1.2511.5.1

Key : Bugcheck.Code.LegacyAPI
Value: 0xa

Key : Bugcheck.Code.TargetModel
Value: 0xa

Key : Dump.Attributes.AsUlong
Value: 0x21008

Key : Dump.Attributes.DiagDataWrittenToHeader
Value: 1

Key : Dump.Attributes.ErrorCode
Value: 0x0

Key : Dump.Attributes.KernelGeneratedTriageDump
Value: 1

Key : Dump.Attributes.LastLine
Value: Dump completed successfully.

Key : Dump.Attributes.ProgressPercentage
Value: 0

Key : Failure.Bucket
Value: AV_nt!MiResolveProtoPteFault

Key : Failure.Exception.IP.Address
Value: 0xfffff802c712b230

Key : Failure.Exception.IP.Module
Value: nt

Key : Failure.Exception.IP.Offset
Value: 0x32b230

Key : Failure.Hash
Value: {2f2238e9-4751-e3c3-543c-b0cdf930b219}

Key : Faulting.IP.Type
Value: Paged

Key : WER.System.BIOSRevision
Value: 5.17.0.0


BUGCHECK_CODE: a

BUGCHECK_P1: fffffb4a425dc4b0

BUGCHECK_P2: 2

BUGCHECK_P3: 0

BUGCHECK_P4: fffff802c712b230

FILE_IN_CAB: 012626-12078-01.dmp

DUMP_FILE_ATTRIBUTES: 0x21008
Kernel Generated Triage Dump

FAULTING_THREAD: ffffb086ec4aa080

READ_ADDRESS: fffff802c7dc44c0: Unable to get MiVisibleState
Unable to get NonPagedPoolStart
Unable to get NonPagedPoolEnd
Unable to get PagedPoolStart
Unable to get PagedPoolEnd
unable to get nt!MmSpecialPagesInUse
fffffb4a425dc4b0

BLACKBOXBSD: 1 (!blackboxbsd)


BLACKBOXNTFS: 1 (!blackboxntfs)


BLACKBOXPNP: 1 (!blackboxpnp)


BLACKBOXWINLOGON: 1 (!blackboxwinlogon)


CUSTOMER_CRASH_COUNT: 1

PROCESS_NAME: MsMpEng.exe

IP_IN_PAGED_CODE:
nt!MiResolveProtoPteFault+c0
fffff802`c712b230 488b1e mov rbx,qword ptr [rsi]

STACK_TEXT:
ffffae8e`3bf87448 fffff802`c74b60e9 : 00000000`0000000a fffffb4a`425dc4b0 00000000`00000002 00000000`00000000 : nt!KeBugCheckEx
ffffae8e`3bf87450 fffff802`c74b13a8 : 07000004`00726025 ffffd400`00000000 ffffb086`d8290480 ffffd400`0c015720 : nt!KiBugCheckDispatch+0x69
ffffae8e`3bf87590 fffff802`c712b230 : fffff802`00000000 ffff9c84`bb896968 0a000004`00726121 00000000`00000000 : nt!KiPageFault+0x468
ffffae8e`3bf87720 fffff802`c712aa6c : ffffae8e`3bf87840 00000000`00000000 ffffae8e`3bf877f8 fffffb7f`ffffffff : nt!MiResolveProtoPteFault+0xc0
ffffae8e`3bf877c0 fffff802`c712cf36 : 00007ff8`944dd48c ffff8000`00000100 00007ff8`944c216c ffff9484`bb896890 : nt!MiDispatchFault+0x1fc
ffffae8e`3bf87930 fffff802`c74b12cb : ffffb086`ec4aa000 0000001a`b5c7d500 000001b7`41b237cc 00007ff8`94ba4828 : nt!MmAccessFault+0x226
ffffae8e`3bf87aa0 00007ff8`944c216c : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiPageFault+0x38b
0000001a`b5c7d468 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x00007ff8`944c216c


SYMBOL_NAME: nt!MiResolveProtoPteFault+c0

MODULE_NAME: nt

IMAGE_VERSION: 10.0.26100.7627

STACK_COMMAND: .process /r /p 0xffffb086d8290080; .thread 0xffffb086ec4aa080 ; kb

IMAGE_NAME: ntkrnlmp.exe

BUCKET_ID_FUNC_OFFSET: c0

FAILURE_BUCKET_ID: AV_nt!MiResolveProtoPteFault

OSPLATFORM_TYPE: x64

OSNAME: Windows 10

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

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

Please see the instructions on the top of the webpage:


Attention: LincSausage
Before posting a BSOD thread, please read the instructions here: Blue/Black Screen of Death (BSOD) Posting Instructions