BSOD when doing random things. Mostly games though 0x000000F4

Bumping is a not allowed thing, it is recommended to read the Forum Rules

Both bugchecks 0x7A and 0xF4 are present, indicative of a problem with the hard drive as we can see in the code below.
I suggest that you test your hard drive according to below instructions.

Diagnostics Test

 HDD TEST

Run SeaTools to check the integrity of your HDD. SeaTools for DOS and Windows - How to Use - Windows 7 Help Forums
Run following tests

1. Short Drive Self Test
2. Short generic
3. Long generic

If the short generic fails, no need for the long generic.

   Note

Do not run SeaTools on an SSD as the results will be invalid.

Run HDTune to

• scan for errors, no quick scan but full scan
• check the health,
• benchmark.

It may take some time, but please take the time you need to perform it properly.
Let me know what the results are

• of the error scan,
• make a screenshot of the health of every hard drive and post the screenshots,
• post screenshots with the benchmark of the
  
  • transfer rate,
  • access time,
  • burst rate,
  • cpu usage.

Code:

*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

KERNEL_DATA_INPAGE_ERROR (7a)
The requested page of kernel data could not be read in.  Typically caused by
a bad block in the paging file or disk controller error. Also see
KERNEL_STACK_INPAGE_ERROR.
If the error status is 0xC000000E, 0xC000009C, 0xC000009D or 0xC0000185,
it means the disk subsystem has experienced a failure.
If the error status is 0xC000009A, then it means the request failed because
a filesystem failed to make forward progress.
Arguments:
Arg1: fffff6fc400099d8, lock type that was held (value 1,2,3, or PTE address)
Arg2: ffffffffc000000e, error status (normally i/o status code)
Arg3: 00000000c3220860, current process (virtual address for lock type 3, or PTE)
Arg4: fffff8800133b148, virtual address that could not be in-paged (or PTE contents if arg1 is a PTE address)

I've taken a look at a lot of dumps, all are 0xF4 or 0x7A, most of us will say that this combination of BSODs is an indication to the hard drive.

Yes there is, but the best guess I can give is this:
Basically there are I/O actions to the hard drive from what I see now is the Nvidia display drivers, my guess is that the allocation of the I/O actions to the page file was improper given that allocating a tag to the pool where the I/O actions were saved gave a pagefault which resulted in a few other faults what eventually resulted in a bugcheck.

Please note that this may not be correct, this is a wild guess as there undocumented function calls + I'm not very good with understanding the functions based on their names without documentation.

Code:

fffff880`033a1778  fffff880`0f42bf98Unable to load image nvlddmkm.sys, Win32 error 0n2
*** WARNING: Unable to verify timestamp for nvlddmkm.sys
*** ERROR: Module load completed but symbols could not be loaded for nvlddmkm.sys
 nvlddmkm+0x1eaf98

I'm glad to hear your issue is solved :)