<Help> i can't get rid of a bsod

Howdy !
So, i know i'm not an active member of the community, but i just give up to try to solve my problem alone.
I have a desktop computer in a very bad shape. I build it at a time where money felt endless, and now i can't get it up to date, or solve some overheating issue.

And before i get a "Switch to Linux", i have a couple of server and desktop on linux, but this is the big one, and i need it to play/VR/Adobe video editor.

So here is my probleme, pretty randomly, i will get a BSOD with a "random" error (it's not always the same) and the computer will reboot. This have start a couple month ago. i was looking for the cause of most of this, and usually fall on driver issue. I start to uninstall driver after driver, removing devices after devices while never getting result. I try the driver check utility in windows, but it was crashing the computer at initialization. Finally, Yesterday i give up and start a full, and clean installation. I've only install the basic driver and still haven't finish to get it as i like, but i got a BOSD, same kind of error.

If any of you is really good with windows ( and i'm sure they are in this community ) and have time to help someone who wish to throw is computer by the windows, please do !

I leave you with the last BSOD log and the config. Thank you a lot !


System Information (local)


Computer name: TESLA
Windows version: Windows 8.1 , 6.3, build: 9600
Windows dir: C:\Windows
Hardware: ASUSTeK COMPUTER INC., RAMPAGE IV EXTREME
CPU: GenuineIntel Intel(R) Core(TM) i7-3970X CPU @ 3.50GHz Intel586, level: 6
12 logical processors, active mask: 4095
RAM: 17114972160 bytes total


Crash Dump Analysis


Crash dump directory: C:\Windows\Minidump

Crash dumps are enabled on your computer.

On Fri 26/08/2016 12:03:51 GMT your computer crashed
crash dump file: C:\Windows\Minidump\082616-8218-01.dmp
This was probably caused by the following module: tcpip.sys (tcpip+0x6C935)
Bugcheck code: 0x1E (0xFFFFFFFFC000001D, 0xFFFFF801D6089935, 0xFFFFD000204F1C68, 0xFFFFD000204F1470)
Error: KMODE_EXCEPTION_NOT_HANDLED
file path: C:\Windows\system32\drivers\tcpip.sys
product: Système d’exploitation Microsoft® Windows®
company: Microsoft Corporation
description: Pilote TCP/IP
Bug check description: This indicates that a kernel-mode program generated an exception which the error handler did not catch.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
The crash took place in a standard Microsoft module. Your system configuration may be incorrect. Possibly this problem is caused by another driver on your system that cannot be identified at this time.

On Fri 26/08/2016 12:03:51 GMT your computer crashed
crash dump file: C:\Windows\memory.dmp
This was probably caused by the following module: tcpip.sys (tcpip+0x6C935)
Bugcheck code: 0x1E (0xFFFFFFFFC000001D, 0xFFFFF801D6089935, 0xFFFFD000204F1C68, 0xFFFFD000204F1470)
Error: KMODE_EXCEPTION_NOT_HANDLED
file path: C:\Windows\system32\drivers\tcpip.sys
product: Système d’exploitation Microsoft® Windows®
company: Microsoft Corporation
description: Pilote TCP/IP
Bug check description: This indicates that a kernel-mode program generated an exception which the error handler did not catch.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
The crash took place in a standard Microsoft module. Your system configuration may be incorrect. Possibly this problem is caused by another driver on your system that cannot be identified at this time.

On Fri 26/08/2016 09:44:31 GMT your computer crashed
crash dump file: C:\Windows\Minidump\082616-9421-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x14E2A0)
Bugcheck code: 0xA (0xFFFFE018588668B0, 0x2, 0x1, 0xFFFFF8037D8F83C3)
Error: IRQL_NOT_LESS_OR_EQUAL
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This indicates that Microsoft Windows or a kernel-mode driver accessed paged memory at DISPATCH_LEVEL or above.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.

On Thu 25/08/2016 19:22:38 GMT your computer crashed
crash dump file: C:\Windows\Minidump\082516-8375-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x14E2A0)
Bugcheck code: 0x109 (0xA3A01F591737960C, 0xB3B72BDF69B4D85F, 0xFFFFF801B320C952, 0x1)
Error: CRITICAL_STRUCTURE_CORRUPTION
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This indicates that the kernel has detected critical kernel code or data corruption.
This might be a case of memory corruption. More often memory corruption happens because of software errors in buggy drivers, not because of faulty RAM modules.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.

On Thu 25/08/2016 18:15:50 GMT your computer crashed
crash dump file: C:\Windows\Minidump\082516-11343-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x14E2A0)
Bugcheck code: 0xD1 (0xFFFFF80214E0C982, 0x2, 0x8, 0xFFFFF80214E0C982)
Error: DRIVER_IRQL_NOT_LESS_OR_EQUAL
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This indicates that a kernel-mode driver attempted to access pageable memory at a process IRQL that was too high.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.

Computer setup
16Gb of corsair DDR3 4X4G
i7-3970X a 4.3 ghz
GTX 780 EVGA hydroCopper
GTX 590 with a waterblock but unplug and pci-e disable with a dip-switch (to much heat)
RaidR SSD 240g (OS) UEFI (Marvell raid 0 of the 2 internal 120g ssd)
WD Velociraptor 1TB (Data) Plugged on the direct sata port (no controller)
Xonar DSX
Rampage 4 EXTREME
Corsair AX860 power supply
3 1080p screen (2 DVI+ 1 DP)

USB Device
Corsair K70 Black
logitech G502
HTC vive
Tritton Pro+ Headset (i know but i can't leave without the separated vocal chat thing)
Hercules Camera
Aquastream Pump Ultra
Nvidia stereo controller.

EDIT :
26/08 I've run Smart and memtest86 without any error. i'v run chkdsk /F and sfc without any error

So did you already reinstall windows?

and is a 780 really enough for a vive?

Yup, as i said 2 day ago, and yes as long a you don't wish magic XD

You could always take everything out of the motherboard and see what it beeps at you

but run a Live Linux USB and see how it works, I'd suggest mint

-
-
side note, should totally grab a 470/480 at some point

That the main probleme. my watercooling stop me to try to remove something like a GC ...

Then go for the linux USB thing and see how long it functions

i was thinking of it, and just forgot to do it ^^. i have some live Cd of debian, arch, ubuntu ... i will do with that to test. but first i will run memtest86 to get the ram out of it

and then do some stress testing and see if it fails, if not it might just be your storage drives

for the storage i have run some smart, nothing wrong. and i don't know anything else

So... I've try a Ubuntu live but he was bugging everywhere. I guess I should install one ... I try to rollback again to a new windows without adding any drivers and I let run YouTube for 3h before getting a BSOD again about driver. I really don't know what to do

This is your problem.

open CMD as Admin
chkdsk /F
sfc /scannow

Thank I try this Right now. If it's only a HDD error and I was just to leasy to switch it ... Anyway let wait for the results

Looks like a dicked-up windoze install.

Get another hard drive, detach any existing drives. Do a fresh install of Windows on the system. Test it out.
$5 says it's fine and you installed a pr0n virus or something because you were careless or disabled UAC.

Nothing, i restart the computer to allow chkdsk to run before startup, and then run sfc. nothing was found ....

I've done it, twice already .... a brand new and clean install don't fix the trouble.

i would go back on you overclock and see if that helps

Did you check your install files:
Run an MD5 of the install ISO and verify that it is correct.

I've check md5 and the ISO is provided by the windows dreamspark program, not junky or infect.

What is your PSU?

Corsair AX860. i will add it in the main one sorry