These dumps look like they could be a RAM issue to me.
The two 0x1AA dumps are caused by a user stack pointer crossing over into a kernel stack. You can see this in the call stack text...
Rich (BB code):
0: kd> knL
# Child-SP RetAddr Call Site
00 fffff800`290f3108 fffff800`2ae75bfc nt!KeBugCheckEx
01 fffff800`290f3110 fffff800`2ae757b1 nt!RtlpGetStackLimitsEx+0x266abc
02 fffff800`290f3160 fffff800`2ac10027 nt!RtlDispatchException+0x2698f1
03 fffff800`290f38d0 fffff800`2ae29582 nt!KiDispatchException+0x317
04 fffff800`290f3fb0 fffff800`2ae29550 nt!KxExceptionDispatchOnExceptionStack+0x12
05 ffffae07`972c2f48 fffff800`2ae3dbf5 nt!KiExceptionDispatchOnExceptionStackContinue
06 ffffae07`972c2f50 fffff800`2ae38c83 nt!KiExceptionDispatch+0x135
07 ffffae07`972c3130 fffff800`2ae32437 nt!KiGeneralProtectionFault+0x343
08 ffffae07`972c32c0 fffff800`2ac5e287 nt!ExpInterlockedPopEntrySListFault
09 ffffae07`972c32d0 fffff800`2ac5d6e1 nt!MiGetPage+0x257
0a ffffae07`972c33f0 fffff800`2ad53bd7 nt!MiGetPageChain+0x541
0b ffffae07`972c3630 fffff800`2ac590b3 nt!MiCreateSharedZeroPages+0x87
0c ffffae07`972c36c0 fffff800`2ac57464 nt!MiResolveDemandZeroFault+0x543
0d ffffae07`972c37b0 fffff800`2ac55814 nt!MiResolveProtoPteFault+0x9d4
0e ffffae07`972c3880 fffff800`2ac53b02 nt!MiDispatchFault+0x1a4
0f ffffae07`972c39c0 fffff800`2ae39029 nt!MmAccessFault+0x152
10 ffffae07`972c3ae0 00007ffc`d9d405d3 nt!KiPageFault+0x369
11 000000ac`4e5ff390 0000643c`020ea870 0x00007ffc`d9d405d3
12 000000ac`4e5ff398 00007ffc`d9d5e21c 0x0000643c`020ea870
13 000000ac`4e5ff3a0 0000c722`1371ee68 0x00007ffc`d9d5e21c
14 000000ac`4e5ff3a8 00000000`00000bbb 0x0000c722`1371ee68
15 000000ac`4e5ff3b0 0000643c`020e9490 0xbbb
16 000000ac`4e5ff3b8 0000643c`0020ec00 0x0000643c`020e9490
17 000000ac`4e5ff3c0 ff58e2d7`69440250 0x0000643c`0020ec00
18 000000ac`4e5ff3c8 0000c722`1371eeb8 0xff58e2d7`69440250
19 000000ac`4e5ff3d0 3fe51831`17eb57b7 0x0000c722`1371eeb8
1a 000000ac`4e5ff3d8 aaaaaaaa`aaaaaaaa 0x3fe51831`17eb57b7
1b 000000ac`4e5ff3e0 3f847ae1`40000000 0xaaaaaaaa`aaaaaaaa
1c 000000ac`4e5ff3e8 00000000`00000000 0x3f847ae1`40000000
The blue text above is the user mode stack and the red text is the kernel stack. Note the nt!KiPageFault immediately the kernel stack is referenced.
Both the 0x7E and 0xBE dumps are manipulating memory pages when the bugcheck occurs. This is the 0x7E...
Rich (BB code):
2: kd> knL
# Child-SP RetAddr Call Site
00 fffff906`36947068 fffff804`22847a36 nt!KeBugCheckEx
01 fffff906`36947070 fffff804`227ea854 nt!PspSystemThreadStartup$filt$0+0x44
02 fffff906`369470b0 fffff804`22833632 nt!_C_specific_handler+0xa4
03 fffff906`36947120 fffff804`2260c1b3 nt!RtlpExecuteHandlerForException+0x12
04 fffff906`36947150 fffff804`22610027 nt!RtlDispatchException+0x2f3
05 fffff906`369478c0 fffff804`2283dbfc nt!KiDispatchException+0x317
06 fffff906`36947fa0 fffff804`22838c83 nt!KiExceptionDispatch+0x13c
07 fffff906`36948180 fffff804`22832437 nt!KiGeneralProtectionFault+0x343
08 fffff906`36948310 fffff804`2265e4f4 nt!ExpInterlockedPopEntrySListFault
09 fffff906`36948320 fffff804`22741262 nt!MiGetPage+0x4c4
0a fffff906`36948440 fffff804`2273ecd1 nt!MiTradeTransitionPage+0x12a
0b fffff906`369484a0 fffff804`2273e7b4 nt!MiTradePage+0x459
0c fffff906`36948550 fffff804`2273f2e0 nt!MiClaimPhysicalRun+0xcc
0d fffff906`369485f0 fffff804`2286f840 nt!MiFindContiguousPagesEx+0x408
0e fffff906`36948840 fffff804`22a4a58b nt!MiRebuildLargePage+0x176
0f fffff906`36948970 fffff804`22614f95 nt!MiRebuildLargePages+0x2db
10 fffff906`36948a00 fffff804`227088b7 nt!ExpWorkerThread+0x155
11 fffff906`36948bf0 fffff804`2282d324 nt!PspSystemThreadStartup+0x57
12 fffff906`36948c40 00000000`00000000 nt!KiStartSystemThread+0x34
And this is the 0xBE...
Rich (BB code):
2: kd> knL
# Child-SP RetAddr Call Site
00 fffff90636947068 fffff804
22847a36 nt!KeBugCheckEx
01 fffff90636947070 fffff804
227ea854 nt!PspSystemThreadStartup$filt$0+0x44
02 fffff906369470b0 fffff804
22833632 nt!_C_specific_handler+0xa4
03 fffff90636947120 fffff804
2260c1b3 nt!RtlpExecuteHandlerForException+0x12
04 fffff90636947150 fffff804
22610027 nt!RtlDispatchException+0x2f3
05 fffff906369478c0 fffff804
2283dbfc nt!KiDispatchException+0x317
06 fffff90636947fa0 fffff804
22838c83 nt!KiExceptionDispatch+0x13c
07 fffff90636948180 fffff804
22832437 nt!KiGeneralProtectionFault+0x343
08 fffff90636948310 fffff804
2265e4f4 nt!ExpInterlockedPopEntrySListFault
09 fffff90636948320 fffff804
22741262 nt!MiGetPage+0x4c4
0a fffff90636948440 fffff804
2273ecd1 nt!MiTradeTransitionPage+0x12a
0b fffff906369484a0 fffff804
2273e7b4 nt!MiTradePage+0x459
0c fffff90636948550 fffff804
2273f2e0 nt!MiClaimPhysicalRun+0xcc
0d fffff906369485f0 fffff804
2286f840 nt!MiFindContiguousPagesEx+0x408
0e fffff90636948840 fffff804
22a4a58b nt!MiRebuildLargePage+0x176
0f fffff90636948970 fffff804
22614f95 nt!MiRebuildLargePages+0x2db
10 fffff90636948a00 fffff804
227088b7 nt!ExpWorkerThread+0x155
11 fffff90636948bf0 fffff804
2282d324 nt!PspSystemThreadStartup+0x57
12 fffff90636948c40 00000000
00000000 nt!KiStartSystemThread+0x34
I would download
Memtest86, burn it to a USB drive, boot that drive and run the 4 iterations the free version does, twice - so you do 8 iterations of the 13 different tests. This will take a few hours.
I did not think it would be a general memory error since it looked like a bad link being removed from a linked list. I figured maybe a malware attack by a browser extension or some device driver making a bad link. I figured dumping the pagefile.sys and clearing the standby list could help it was a random error staved to the pagefile then reloaded.
nt!ExpInterlockedPopEntrySListFault
ExInterlockedPopEntrySList function (wdm.h) - Windows drivers | Microsoft Learn
2: kd> !poolused /t 10 2
....
Sorting by NonPaged Pool Consumed
NonPaged Paged
Tag Allocs Used Allocs Used
KLOG 63 21347264 1298 3396160 UNKNOWN pooltag 'KLOG', please update pooltag.txt
MINI 4919 10636608 4649 25478256 UNKNOWN pooltag 'MINI', please update pooltag.txt
these are the largest consumers of non paged pool.
pooltags KLOG and MINI
bunch of programs using lots of ram, admow.exe
amdow.exe Windows process - What is it? (file.net)
AMDRSServ.exe 103572 Kb 1155328 Kb
AMDRSSrcExt.exe 62608 Kb 107136 Kb
system process is using .9 GB ram for some reason.
boot into bios and leave the system powered on but not running for a hour or two then reboot and see if the system process uses less resources.
this shows how to use findstr.exe to find a pooltag in on your machine:
An Introduction to Pool Tags - Microsoft Community Hub
You can use the
findstr command in all versions of Windows. Change to the %systemroot%\system32\drivers folder at a command prompt and then run the
findstr /m /l <tag> *.sys command.
findstr.exe /m /l KLOG *.sys
findstr.exe /m /l MINI *.sys
these command should tell you the name of the driver