BSOD playing MGSV/DotA 2/Compiling Code, (almost) always from ntoskrnl

You can downgrade to 7 via multiple ways. However, the ways of Microsoft will give you more/other problems

Tomorrow I'll check for drivers that need updating.

There are just 2 drivers dating a little old.
Please check Realtek for the audio driver and Qualcomm for the network driver updates

Code:

2: kd> lmvm RTKVHD64
start             end                 module name
fffff800`238d0000 fffff800`23c84380   RTKVHD64   (deferred)             
    Image path: RTKVHD64.sys
    Image name: RTKVHD64.sys
    Timestamp:        Tue Mar 11 13:56:41 2014 (531F0809)
    CheckSum:         003B9623
    ImageSize:        003B4380
    Translations:     0000.04b0 0000.04e4 0409.04b0 0409.04e4

2: kd> lmvm athuw8x
start             end                 module name
fffff800`23cf0000 fffff800`24089000   athuw8x    (deferred)             
    Image path: athuw8x.sys
    Image name: athuw8x.sys
    Timestamp:        Mon Oct 15 13:08:55 2012 (507BEEC7)
    CheckSum:         003956BB
    ImageSize:        00399000
    Translations:     0000.04b0 0000.04e4 0409.04b0 0409.04e4

Let me know how it goes :)

Both 0x1A(MEMORY_MANAGEMENT) and 0x4E(PFN_LIST_CORRUPT) indicate memory problems.
However, both the hard drives and memory modules have been ruled out.
This indicates a driver is causing problems.
(If you have fast startup enabled, please disable it just to make sure fast startup is not causing any problem.)
There are lots of drivers that are dated around July, August, and September so we need driver verifier again to find violations with the drivers.

Diagnostic Test

 DRIVER VERIFIER

   Warning

Please make a backup of your important files and get your rescue media or create one.
Please create a restore point.

Please follow this tutorial to run driver verifier.

Some windows drivers are blamed in a few crashes, but that usually means that a 3rd party driver is actually the cause.
Driver verifier stresses your drivers and will crash your pc if any driver fails due to a violation.

Driver verifier should be performed for a max of 48 hours, or when you have a bluescreen, whatever comes first.

If driver verifier has found a violation and you can't get back into windows normally, try to boot into safe mode and reset in safe mode driver verifier, or in the troubleshooting options open command prompt and type verifier /reset.

   Note

Your system will act very sluggishly while driver verifier is enabled, this is normal as your drivers will be being subjected to heavy testing in order to make them crash.