Random BSOD, 0x000000BE, removed Ram but still issues

Mate's PC, using an old Asus Striker Extreme with 7 Pro 64bit on it, randomly bluescreening. Hiren's memchecks found no issue, but removed a couple of sticks leaving 4Gb down from the original 6Gb. Seems more stable now but not perfect. Oddly the memchecks. For instance, had Comodo installed on it, worked ok, updated, ran fine, post a reboot randomly will stop working, can't repair itself, stripping it out and re-installing, nada. This machine may stay up for days, may just randomly bluescreen, sometimes x000000BE, once I noticed 1E. Bios beeps not helpful. link now removed as zip attached below Hoping that you can spot something from the logs. Thank you for your time

Post it following the Blue Screen of Death (BSOD) Posting Instructions.

It appears to be an old computer.

Is the computer hot? Report us the heat of the computer after a couple of hours of your normal usage. Upload a screenshot of the summery tab of Speccy. Alternatively, you can publish a Speccy snapshot too: Speccy - Publish Snapshot of your System Specs .

Check if the Power Supply Unit (PSU) supplying adequate power to the computer or not.
eXtreme Power Supply Calculator
Also let us know the wattage of the PSU.

Test your RAM modules for possible errors.
How to Test and Diagnose RAM Issues with Memtest86+
Run memtest for at least 8 passes, preferably overnight.
If it start showing errors/red lines, stop testing. A single error is enough to determine that something is going bad there.

Stress test the Graphics Card using Furmark.
Video Card - Stress Test with Furmark

Stress test the CPU.
Hardware - Stress Test With Prime95

Also, if possible, plan to update the BIOS to the latest available, Version 2002 from ASUSTeK Computer Inc. -Support- Drivers and Download Striker Extreme

Let us know the results.
______________________________________

Code:

BugCheck 24, {1904fb, fffff88002fdff58, fffff88002fdf7b0, fffff880012bfcba}

Probably caused by : hardware ( Ntfs!LfsWriteLogRecordIntoLogPage+38a )

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

Code:

BugCheck A, {fffffa7fffffff80, 2, 1, fffff80002a44ac1}

Probably caused by : memory_corruption ( nt!MmZeroPageThread+3c4 )

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