Several blue screens per day on ASUS Vivobook 15 - 11 25H2

I've been investigating a blue screen issue on my friend's laptop for a couple of months and I've gone through every avenue of troubleshooting I can think of and I've gotten nowhere. Despite the following the bullet points below, the issue still persists.

Model no: ASUS Vivobook X513UA running a Ryzen 7 5700U, 12GB DDR4 3200MHz sticks. Running Windows 11 25H2.

- Reinstalled Windows 11 clean from two refus imaged flashdrives. Use this ISO image for many computers and isn't the issue.
- Replaced the SSD twice. Happens on a new 990 pro, SN770 etc.
- Unplugged the docking station out of fear this was causing it
- Ram MEMTEST for several hours. All good.
- Updated BIOS to the latest version
- Ensured windows update and drivers are up to date.

The blue screen is almost always page fault in non paged area with an 0x50 code at the bottom. The machine gets to 100% complete but never restarts so must be manually powered down.

I have 5 different dump files for these crashed and all of them point at ntfs.sys being the culprit. I've fed one of them into windbg and used analyze -v to view the log. It mentions the following information in the dump log:



DUMP_FILE_ATTRIBUTES: 0x21808
Kernel Generated Triage Dump

READ_ADDRESS: Unable to get NonPagedPoolStart
Unable to get NonPagedPoolEnd
Unable to get PagedPoolStart
Unable to get PagedPoolEnd
ffff928c81538b90

MM_INTERNAL_CODE: 2

BLACKBOXBSD: 1 (!blackboxbsd)


BLACKBOXNTFS: 1 (!blackboxntfs)


BLACKBOXWINLOGON: 1

CUSTOMER_CRASH_COUNT: 1

PROCESS_NAME: MsMpEng.exe

TRAP_FRAME: fffffa021e5f6e50 -- (.trap 0xfffffa021e5f6e50)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=ffff988a62f41b68 rbx=0000000000000000 rcx=ffff988a62f41b68
rdx=ffffcb882b2b7d60 rsi=0000000000000000 rdi=0000000000000000
rip=fffff807bac5ba0c rsp=fffffa021e5f6fe0 rbp=4080000040000003
r8=ffff988a66cdd820 r9=ffff988a66cdd858 r10=ffff988a62f41b68
r11=0000000000013000 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0 nv up ei pl nz na pe nc
nt!IoGetOplockFullFoExt+0x10:
fffff807`bac5ba0c d2740448 sal byte ptr [rsp+rax+48h],cl ss:0018:ffff928c`81538b90=??
Resetting default scope

MISALIGNED_IP:
nt!IoGetOplockFullFoExt+10
fffff807`bac5ba0c d2740448 sal byte ptr [rsp+rax+48h],cl

STACK_TEXT:
fffffa02`1e5f6be8 fffff807`bab37750 : 00000000`00000050 ffff928c`81538b90 00000000`00000002 fffffa02`1e5f6e50 : nt!KeBugCheckEx
fffffa02`1e5f6bf0 fffff807`bab246b6 : 00000000`00000000 ffff8000`00000000 ffff928c`81538b90 0000007f`fffffff8 : nt!MiSystemFault+0x850
fffffa02`1e5f6ce0 fffff807`baeb97cb : ffff988a`66cc6000 fffff807`ba000000 ffff988a`62f41af0 fffff807`00000000 : nt!MmAccessFault+0x646
fffffa02`1e5f6e50 fffff807`bac5ba0c : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiPageFault+0x38b
fffffa02`1e5f6fe0 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!IoGetOplockFullFoExt+0x10


SYMBOL_NAME: nt!IoGetOplockFullFoExt+10

IMAGE_VERSION: 10.0.26100.7824

STACK_COMMAND: .cxr; .ecxr ; kb

MODULE_NAME: AuthenticAMD

IMAGE_NAME: AuthenticAMD.sys

FAILURE_BUCKET_ID: IP_MISALIGNED_AuthenticAMD.sys

OSPLATFORM_TYPE: x64

OSNAME: Windows 10

FAILURE_ID_HASH: {716d112a-8330-4bbb-160c-ec98297019d2}

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


I've also provided the dump file below. Here's the link to the log collector zip folder here as well: DESKTOP-MCLPMNO-(2026-02-14_18-00-02).zip Any insight would be amazing.

Please see the posting instructions:

1) Please add WMIC:





2) Run tuneup_plus_log.bat > post a share link






3) Run Memtest86+ for 8 or more passes > take pictures > post images or share links

Memtest86+ | The Open-Source Memory Testing Tool

Just 1 error is a test fail and testing can be aborted.

The more the passes the better the testing conditions.

It sometimes takes passes into the 20's to detect malfunctioning RAM.

The RAM can be tested all at one time or one at a time in the same DIMM.

Memtest86+ | The Open-Source Memory Testing Tool

MemTest86+ - Test RAM

Reevesii said:

- Reinstalled Windows 11 clean from two refus imaged flashdrives. Use this ISO image for many computers and isn't the issue.

Click to expand...

It's a hardware issue then. Unless you go on and reinstall all third-party software before testing? In that case it's possible that you reinstalled the problem. When you clean install because of a problem you need to install all drivers (from the Asus website, not from Windows Update), install all Windows updates, and then test it thoroughly before installing anything else (or plugging any external devices in).

Looking at the dump, the page fault happens because of an invalid memory reference (or bad RAM)...
That SAL (shift/multiply by 2) instruction does a left shift on the contents of memory pointed to by the sum of the RSP and RAX registers and 0x48. The resulting location (0xffff928c81538b90) is invalid, indicated by the ?? characters. The instruction is in a Windows function call that directly follows a call to ntfs.sys (a Windows driver). You read this stack trace excerpt from the bottom up (it's a push-down stack)...
It's thus possible that you either have a RAM issue or (possibly) a drive issue.

Also from the dump, you're running with mismatched RAM. You have one 8GB stick of Samsung M471A1K43EB1-CWE RAM and one stick of 4GB Micron 4ATF51264HZ-3G2J1 RAM (which may well be soldered in). Whilst these may look similar on paper they may well have different internal timings that cause issues, especially since they are overclocked to 3200MHz from the native DDR4 speed of 2666MHz. On a laptop you're unlikely to be able to remove that overclock because the BIOS is locked down. I doubt you'll get Windows 11 to run in any reasonable way in the 4GB soldered-in RAM so your testing options here are pretty limited. Testing your RAM with Metst86 (or Memtest86+ as already advised) is a wise move.

You don't say what your drive(s) is/are, but I'd suggest downloading and installing CrystalDiskInfo and use that to display the SMART data from each drive. Post a screenshot of those displays.

Again, since the issue persists across reinstalls, you're almost certainly looking at a hardware cause.

Have you set the BIOS to fail safe defaults?
Assuming that was one of the first things you did but just thought I would mention it it.