irratic BSOD crashes, various reasons given

Hello rickkiing.

Your crash dumps are not showing any finite probable cause.

Seatool for dos: SeaTools | Seagate download

• Burn it in a blank cd. boot from the CD, click on "Accept", wait for it to finish detecting the drives, then in the upper left corner select "Basic Tests", then select "Long Test" and let it run.

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.

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

Scan the system for possible virus infection with the following programs.

• Anti-rootkit utility TDSSKiller
• Windows Defender Offline

If all the tests comes free from errors, enable Driver Verifier to monitor the drivers.
Driver Verifier - Enable and Disable
Run Driver Verifier for 24 hours or the occurrence of the next crash, whichever is earlier.

   Information

Why Driver Verifier:
It puts a stress on the drivers, ans so it makes the unstable drivers crash. Hopefully the driver that crashes is recorded in the memory dump.

How Can we know that DV is enabled:
It will make the system bit of slow, laggy.

   Warning

Before enabling DV, make it sure that you have earlier System restore points made in your computer. You can check it easily by using CCleaner looking at Tools > System Restore.

If there is no points, make a System Restore Point manually before enabling DV.

   Tip

• If you fail to get on the Desktop because of DV, Boot into Advanced Boot Options > Safe mode. Disable DV there. Now boot normally again, and try following the instruction of enabling DV again.
• If you cannot boot in Safe mode too, do a System Restore to a point you made earlier.

Let us know the results, with the subsequent crash dumps, if any. Post it following the Blue Screen of Death (BSOD) Posting Instructions.
___________________________________________________________________
BSOD ANALYSIS:

Code:

BugCheck 24, {c08a5, 0, 0, 0}

Probably caused by : Ntfs.sys ( Ntfs!NtfsPagingFileIo+155 )

Followup: MachineOwner
------------------------------------------------------------------------
BugCheck 19, {3, fffff8a026f58840, fffff8a026f58840, 12fff8a026f58840}

Probably caused by : Pool_Corruption ( nt!ExDeferredFreePool+c96 )

Followup: Pool_corruption
------------------------------------------------------------------------
BugCheck 3B, {c0000005, fffff80002fc47f1, fffff8800a5d0fb0, 0}

Probably caused by : ntkrnlmp.exe ( nt!ExFreePoolWithTag+711 )

Followup: MachineOwner
------------------------------------------------------------------------
BugCheck 3B, {c0000005, fffff80003002b05, fffff880089cfdc0, 0}

Probably caused by : Pool_Corruption ( nt!ExDeferredFreePool+249 )

Followup: Pool_corruption
------------------------------------------------------------------------
BugCheck 3B, {c0000005, fffff88003a97756, fffff88008fbed00, 0}

Probably caused by : dxgkrnl.sys ( dxgkrnl!DXGADAPTER::ReleaseReference+16 )

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