Help with random shutoff

[tangstang]

Motherboard- asus p8p67 le
Cpu- i7-2600 running 4.6 ghz, tried running less and it didn't seem to matter.
Ram- HyperX 16GB (4 x 4GB) 240-Pin DDR3 SDRAM DDR3 1600 (PC3 12800)
Vid card- asus gtx 1070

Problems seemed to be power related and I had a 700w PSU which worked great but I figured after swapping out the vid card(had to swap everything over to a larger case for this) maybe I was running out of power and it was crashing seemingly at random. Now has a evga 1000w PSU so that shouldn't be an issue.
I've got a thermaltake frio which keeps the Cpu around 50*C. It will crash randomly regardless of temperature so pretty sure that's not an issue.
Ran windows memory diagnostic tool and it shows all the ram is good.
Crashes are becoming much more frequent now.

Had thought about getting a new mobo/cpu/ram setup but am still on the fence and would rather not if I don't have to.
What do you guys think the issue could be and what can I do to check?
If I do have to upgrade what's your opinion on the new i7s?

[Tx Redneck]

Run Bluescreenview and see what's in the dump and post back.

[tangstang]

There are more crashes in the last week than are shown here by the way.

doesn't look like it wants to post that.
here's the url

http://imgur.com/a/SoM2c

[Tx Redneck]

Run sfc /scannow from an elevated cmd prompt and see if it comes back clear, but I suspect based on the age of the mobo, you have TIM drying out on one of the chipset components that's dried out and the component is overheating. I had to rebuild 4yrs ago for that very reason.

[tangstang]

I got this back in the logs
7-04-19 21:40:32, Info CSI 00000306 [SR] Beginning Verify and Repair transaction
2017-04-19 21:40:32, Info CSI 00000308 [SR] Cannot repair member file [l:28{14}]"iassdo.dll.mui" of Microsoft-Windows-Networking-Internet_Authentication_Service_Iassdo.Resources, Version = 6.1.7600.16385, pA = PROCESSOR_ARCHITECTURE_INTEL (0), Culture = [l:10{5}]"en-US", VersionScope = 1 nonSxS, PublicKeyToken = {l:8 b:31bf3856ad364e35}, Type neutral, TypeName neutral, PublicKey neutral in the store, hash mismatch
2017-04-19 21:40:32, Info CSI 0000030a [SR] Cannot repair member file [l:28{14}]"iassdo.dll.mui" of Microsoft-Windows-Networking-Internet_Authentication_Service_Iassdo.Resources, Version = 6.1.7600.16385, pA = PROCESSOR_ARCHITECTURE_INTEL (0), Culture = [l:10{5}]"en-US", VersionScope = 1 nonSxS, PublicKeyToken = {l:8 b:31bf3856ad364e35}, Type neutral, TypeName neutral, PublicKey neutral in the store, hash mismatch
2017-04-19 21:40:32, Info CSI 0000030b [SR] This component was referenced by [l:266{133}]"Microsoft-Windows-WindowsFoundation-LanguagePack-Package~31bf3856ad364e35~amd64~en-US~6.1.7600.16385.Windows Foundation Language Pack"
2017-04-19 21:40:32, Info CSI 0000030e [SR] Could not reproject corrupted file [ml:60{30},l:58{29}]"\??\C:\Windows\SysWOW64\en-US"\[l:28{14}]"iassdo.dll.mui"; source file in store is also corrupted
2017-04-19 21:40:32, Info CSI 00000310 [SR] Repair complete

Sooo where do I go from here?

[Tx Redneck]

Are you using a hacktivated copy of 7? Nbd if you are, but that file is used to validate the authenticity of Win and the hacktivators patch it and sfc can't repair. You can try an in place upgrade to repair those files, but I don't think that's the issue causing the problem.

I'd locate the Northbridge heatsink, pop it off and replace the thermal paste.

[tangstang]

Yeah, I'll have to order some paste and try that. Will report back after it comes in/ reapplication.