Random BSODs after opening up Chrome?

After upgrading to Windows 10, I kept getting many BSODs of random statusi, so I downgraded back to 7 Pro, but the BSODs have not stopped.
I get various BSODs from Memory_Management to Bad Pool Header to IRQL Not Less Or Equal.

I have not found any solutions after searching the web, but I have ran memory diagnostic tool and ran it in safe mode.

Please read BSOD Posting Instructions & How to upload files

Uninstall McAfee while troubleshooting
https://service.mcafee.com/webcenter...3Djiltcdhj6_49

Code:

fffff880`11e517c8  fffff880`01129685Unable to load image \SystemRoot\system32\drivers\mfehidk.sys, Win32 error 0n2
*** WARNING: Unable to verify timestamp for mfehidk.sys
*** ERROR: Module load completed but symbols could not be loaded for mfehidk.sys
 mfehidk+0x72685
fffff880`11e51848  fffff880`071b9678Unable to load image \SystemRoot\system32\drivers\mfeavfk.sys, Win32 error 0n2
*** WARNING: Unable to verify timestamp for mfeavfk.sys
*** ERROR: Module load completed but symbols could not be loaded for mfeavfk.sys
 mfeavfk+0x1b678
fffff880`11e51878  fffff880`079accd9Unable to load image \SystemRoot\system32\DRIVERS\mfencbdc.sys, Win32 error 0n2
*** WARNING: Unable to verify timestamp for mfencbdc.sys
*** ERROR: Module load completed but symbols could not be loaded for mfencbdc.sys
 mfencbdc+0x49cd9

Update Acronis, or uninstall while troubleshooting

Code:

fffff880`11e514e8  fffff880`01fd6695Unable to load image \SystemRoot\system32\DRIVERS\fltsrv.sys, Win32 error 0n2
*** WARNING: Unable to verify timestamp for fltsrv.sys
*** ERROR: Module load completed but symbols could not be loaded for fltsrv.sys
 fltsrv+0xa695
fffff880`11e512f8  fffff880`01e18862Unable to load image \SystemRoot\system32\DRIVERS\snapman.sys, Win32 error 0n2
*** WARNING: Unable to verify timestamp for snapman.sys
*** ERROR: Module load completed but symbols could not be loaded for snapman.sys
 snapman+0x18862

Please uninstall everything of Nvidia using Display Driver Uninstaller and install new drivers from Nvidia. Be sure the clean install box is checked and only install the Graphics driver and the PhysX driver.

Code:

fffff800`00b9aaa8  fffff880`05dfc6a2Unable to load image \SystemRoot\system32\DRIVERS\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+0x1416a2
0: kd> lmvm nvlddmkm
start             end                 module name
fffff880`05cbb000 fffff880`0679e000   nvlddmkm T (no symbols)           
    Loaded symbol image file: nvlddmkm.sys
    Image path: \SystemRoot\system32\DRIVERS\nvlddmkm.sys
    Image name: nvlddmkm.sys
    Timestamp:        Sat Oct 03 03:54:49 2015 (560F3569)
    CheckSum:         00A9E36F
    ImageSize:        00AE3000
    Translations:     0000.04b0 0000.04e4 0409.04b0 0409.04e4

Update the Intel USB driver
Driver Reference Table - iusb3xhc.sys

Code:

*** WARNING: Unable to verify timestamp for iusb3xhc.sys
*** ERROR: Module load completed but symbols could not be loaded for iusb3xhc.sys
0: kd> lmvm iusb3xhc
start             end                 module name
fffff880`04a00000 fffff880`04ac3000   iusb3xhc T (no symbols)           
    Loaded symbol image file: iusb3xhc.sys
    Image path: \SystemRoot\system32\DRIVERS\iusb3xhc.sys
    Image name: iusb3xhc.sys
    Timestamp:        Fri Mar 29 13:36:19 2013 (51558AC3)
    CheckSum:         000C59AC
    ImageSize:        000C3000
    Translations:     0000.04b0 0000.04e4 0409.04b0 0409.04e4

Due to a 0x1A(MEMORY_MANAGEMENT) and a 0x4E(PFN_LIST_CORRUPT)

Diagnostic Test

 RAM TEST

Run MemTest86+ to analyse your RAM. MemTest86+ - Test RAM - Windows 7 Forums

   Note

MemTest86+ needs to be run for at least 8 passes for conclusive results. Set it running before you go to bed and leave it overnight. We're looking for zero errors here. Even a single error will indicate RAM failure.

Diagnostics Test

 HDD TEST

Run SeaTools to check the integrity of your HDD. SeaTools for DOS and Windows - How to Use

   Note

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

Run chkdsk Disk Check

Run HDTune to scan for errors, health and benchmark.
Let me know what the results are, prefered screenshots.

Code:

2: kd> k
Child-SP          RetAddr           Call Site
fffff880`0ed008f8 fffff800`03ce24dd nt!KeBugCheckEx
fffff880`0ed00900 fffff800`03c43382 nt! ?? ::FNODOBFM::`string'+0x2c811
fffff880`0ed009f0 fffff800`03c442b5 nt!CcPurgeCacheSection+0x172
fffff880`0ed00a60 fffff800`03c9c2b2 nt!CcPurgeAndClearCacheSection+0x75
fffff880`0ed00b10 fffff880`016477e0 nt!CcSetFileSizesEx+0x2c6
fffff880`0ed00b90 fffff880`016be364 Ntfs!NtfsSetBothCacheSizes+0x50
fffff880`0ed00bf0 fffff880`016ad183 Ntfs!NtfsDeleteAllocation+0x2f4
fffff880`0ed00cc0 fffff880`016aec98 Ntfs!NtfsDeleteAllocationFromRecord+0x173
fffff880`0ed00d80 fffff880`016ce18d Ntfs!NtfsDeleteFile+0x328
fffff880`0ed00ff0 fffff880`0163e639 Ntfs!NtfsCommonCleanup+0x166d
fffff880`0ed01410 fffff800`03c81e68 Ntfs!NtfsCommonCleanupCallout+0x19
fffff880`0ed01440 fffff880`0163e6b2 nt!KeExpandKernelStackAndCalloutEx+0xd8
fffff880`0ed01520 fffff880`016dbba4 Ntfs!NtfsCommonCleanupOnNewStack+0x42
fffff880`0ed01590 fffff880`01271bcf Ntfs!NtfsFsdCleanup+0x144
fffff880`0ed01800 fffff880`012706df fltmgr!FltpLegacyProcessingAfterPreCallbacksCompleted+0x24f
fffff880`0ed01890 fffff800`03f8116f fltmgr!FltpDispatch+0xcf
fffff880`0ed018f0 00000000`00000000 nt!IopCloseFile+0x11f

Beter update manually, make sure it is done properly :)

Manually via the site of Intel of course

Please let me know how it goes :)