BSOD issues - F4 error

You should still have the minidump of the 0xF4 in %systemroot%\minidump, zip it up and upload it directly please.

The 0x9F is caused by the Logitech drivers, updating/reinstalling is suggested.
Driver Reference Table - LHidEqd.Sys

Code:

0: kd> lmvm LHidEqd
Browse full module list
start             end                 module name
fffff880`05d87000 fffff880`05d8f000   LHidEqd    (no symbols)           
    Loaded symbol image file: LHidEqd.Sys
    Image path: \SystemRoot\system32\DRIVERS\LHidEqd.Sys
    Image name: LHidEqd.Sys
    Browse all global symbols  functions  data
    Timestamp:        Tue Jun 09 21:25:30 2015 (55773DAA)
    CheckSum:         00009BAC
    ImageSize:        00008000
    Translations:     0000.04b0 0000.04e4 0409.04b0 0409.04e4

If you have software from MSI, please remove them.

I hoped to find something like memory leakage or anything, but everything looks normal. Unfortunately I am unable to debug the kernel dump more, I'm not sure how to continue to dig deeper in all the threads that the winit.exe holds to find possible reasons for certain pagefaults.

Besides of this I dumped the raw stack, something I always do, which revealed the Intel display driver

Code:

fffff880`0bcf7c18  fffff880`048c51e8*** ERROR: Module load completed but symbols could not be loaded for igdkmd64.sys
 igdkmd64+0xc31e8

6: kd> lmvm igdkmd64
Browse full module list
start             end                 module name
fffff880`04802000 fffff880`04bba000   igdkmd64   (no symbols)           
    Loaded symbol image file: igdkmd64.sys
    Image path: \SystemRoot\system32\DRIVERS\igdkmd64.sys
    Image name: igdkmd64.sys
    Browse all global symbols  functions  data
    Timestamp:        Mon Apr 04 19:48:36 2016 (5702A8F4)
    CheckSum:         003A55B0
    ImageSize:        003B8000
    Translations:     0000.04b0 0000.04e4 0409.04b0 0409.04e4

Please uninstall everything of Intel graphics using Display Driver Uninstaller and install new drivers from MSI. Be sure to ONLY install the drivers using custom/advanced options.
Attachment 388157

There are some usual causes that we haven't done anything for yet.

Try to reseat the GPU or seat it into a different slot.

These are the usual causes for the 0x7A, we haven't done much, only checking the file system and hard drive. I have however not ruled out the hard drive with the reason that hard drives can fail even when software cannot detect any problem. To fully rule out certain causes they need to be replaced.
I would like to go through all the usual causes one at a time, but before we can do so I would recommend to make a system backup on an external hard drive. My next suggestion would be to do a vanille installation, a clean installation with only Windows 7 fully updated + Microsoft Security Essentials installed, this would immediately rule out most of the kinds of malware. Malware like rootkits that hide in the firmware (BIOS) require hardware replacement to get rid off.

• Memory,
• Paging file corruption,
• File system,
• Hard drive,
• Cabling,
• Virus infection,
• Improperly seated cards,
• BIOS,
• Bad motherboard,
• Missing Service Pack

I cannot say for sure if it is safe, I wouldn't do it personally, but at least make sure that it is disconnected when you install Windows on the m.2 SSD to prevent installation conflicts.