Solved BSOD caused by the following module: ntoskrnl.exe (nt+0x4B87C0)

Hi all,

For the last couple of days I'm experiencing a BSOD regarding to a module ntoskrnl.exe
I checked if my drives are outdated, but I didn't find any optional drivers which should be updated.

BSOD Mini Dump: 101224-8843-01.rar



SYMBOL_NAME: nt!MiGetPageChain+1e6

MODULE_NAME: nt

IMAGE_VERSION: 10.0.26100.1912

STACK_COMMAND: .process /r /p 0xffffe603372f5080; .thread 0xffffe60332de9080 ; kb

IMAGE_NAME: ntkrnlmp.exe

BUCKET_ID_FUNC_OFFSET: 1e6

FAILURE_BUCKET_ID: AV_R_nt!MiGetPageChain

OSPLATFORM_TYPE: x64

OSNAME: Windows 10

FAILURE_ID_HASH: {e47728b7-9f3a-0155-b2aa-ef5f5ed6cf18}

Followup: MachineOwner

Attention:

MaitieS​

Before posting a BSOD thread, please read the instructions here: Blue/Black Screen of Death (BSOD) Posting Instructions
If you need to add new information, please make a new post in your initial BSOD thread. Please do not make an extra new thread.

Please do not post anything other than Windows 11 Blue/Black Screen Of Death problems in this section.

zbook said:

Attention:

MaitieS​

Before posting a BSOD thread, please read the instructions here: Blue/Black Screen of Death (BSOD) Posting Instructions
If you need to add new information, please make a new post in your initial BSOD thread. Please do not make an extra new thread.

Please do not post anything other than Windows 11 Blue/Black Screen Of Death problems in this section.

Click to expand...

I followed it? If mini-dump and driver version-table won't be enough for this particular BSOD, I will post more.

When available post a V2 share link into the newest post

zbook said:

When available post a V2 share link into the newest post

Click to expand...

Hi zbook,

Sorry for late replay. I thought that mini-dump & driver logs from v2 would be enough cuz I didn't want to share Network stuff as it contains my IP especially on pub forum, and without any sign of someone being interested in the first place. I did a few checks myself like: memory, disk, stress tests for memory as well, and all finished successfully. I also performed a clean reinstall of the latest update using Reinstall Update in Recovery settings. I might be wrong but before that reinstall my version was different 26100.1912 instead of the one that I was supposed to have (current: 26100.2152), so maybe that was the issue? Would be a weird one but from that process that was crashing it was Window's one.

If the BSOD will reoccure, I will make sure to provide v2 log in the next post.