BSOD multiple times when running intensive software

Attached is the log-collector v2 output. I thumbed through it and noticed the issues were from ntkrnlmp.exe every time for the past 2 times (sometimes logs were not generated), and all issues had bugcheck values relating to page files. I did put in two different sets of RAM (in different channels), so I was wondering if that was the issue. Because this is a minidump I can't seem to access a stack trace for the issues. Was wondering if someone else could take a look at this too.

Windows version 24H2.

this maybe of help.

please check the results of the advice at the bottom of that post.
best of luck, Steve ..

Please perform the following steps: (in sequence)



Make sure that images or share links are posted for all steps / tests.



1) Run Tuneup plus > post a share link

https://www.tenforums.com/attachmen...-files-use-bsod-debugging-tuneup_plus_log.zip

Batch files for use in BSOD debugging - Windows 10 Help Forums

Batch files for use in BSOD debugging - Windows 10 Help Forums




2) Create a new restore point:





3) Read the owners manual to see if there are optimal DIMMs when using only one or only two RAM modules > report findings




4) The BIOS Version/Date American Megatrends Inc. 3.70, 6/9/2020

Upgrade the BIOS: 3.7 > 3J (the most up to date non-beta BIOS)





5) Remove all RAM modules > label them > test one RAM module at a time in the same DIMM for 8 or more passes


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.

Memtest86+ | The Open-Source Memory Testing Tool

MemTest86+ - Test RAM




6) Once you've confirmed a non-malfunctioning RAM module with 8 or more passes > perform Windows and defender updates > post a new V2 share link into the newest post

I'm away for four days on vacation, I'll do this when I get back.