Bonjour tout le monde !  
 
Config :  
Carte mère : asus 99x strix gaming  
Processeur : 6800k  
Mémoire : ripjaws 5 / 4x8G  
Carte graphique : zotac 1080ti extrème  
Refroidissement : Noctua u12s  
Alimentation : seasonic m12D 850w  
 
Voilà depuis hier soir j'ai un problème avec ma nouvelle config...  
En effet, hier j'ai lancé un test occt avant d'aller me coucher, l'histoire de voir la stabilité de mon overcloking. En me réveillant le lendemain matin je me suis rendu compte que mon pc avait planté après 50 minutes de test avec des piques de température à 85°c mais un moyenne globale de température de 79°C, suite à ça je redémarre mais dès que j'arrive sur le bureau le pc plante dans les 10 secondes soit il freeze soit il me fait des blue screen avec des message différents à chaque fois KERNEL_SECURITY_CHECK_FAILURE / IRQL_NOT_LESS_OR_EQUAL / BAD_POOL_HEADER / MACHINE CHECK EXCEPTION  
 
j'ai donc remis les paramètres du processeur par defaut et là tout fonctionne de nouveau mais dès que je touche à la fréquence du processeur celui ci se remet à planter. Je tiens à préciser qu'avant se fucking test occt je pouvais ajuster la fréquence sans problème et mon overcloking était plus ou moins stable à 4.1 ghz avec un vcore de 1.34 mais depuis le test occt c'est impossible.  
 
J'ai essayer plusieurs solutions dont un Clear cmos et une Réinstallation de windows mais le tout sans succès le problème est toujours le même... j'ai également fait un test who crashed afin de comprendre les blue screen voici le rapport ci-dessous.  
En espérant que vous allez pouvoir m'aider parceque je désespère quelque peu...  
Merci d'avance  
 
 
 
System Information (local)  
--------------------------------------------------------------------------------  
 
Computer name: DESKTOP-A8H8POB  
Windows version: Windows 10 , 10.0, build: 15063  
Windows dir: C:\Windows  
Hardware: All Series, ASUS, ASUSTeK COMPUTER INC., STRIX X99 GAMING  
CPU: GenuineIntel Intel(R) Core(TM) i7-6800K CPU @ 3.40GHz Intel586, level: 6  
12 logical processors, active mask: 4095  
RAM: 34266263552 bytes total  
 
 
 
 
--------------------------------------------------------------------------------  
Crash Dump Analysis  
--------------------------------------------------------------------------------  
 
Crash dump directory: C:\Windows\Minidump  
 
Crash dumps are enabled on your computer.  
 
On Mon 05/06/2017 19:50:29 your computer crashed  
crash dump file: C:\Windows\Minidump\060517-12125-01.dmp  
This was probably caused by the following module: ntoskrnl.exe (nt+0x16C310)  
Bugcheck code: 0x139 (0x3, 0xFFFFA58191C088F0, 0xFFFFA58191C08848, 0x0)  
Error: KERNEL_SECURITY_CHECK_FAILURE  
file path: C:\Windows\system32\ntoskrnl.exe  
product: Microsoft® Windows® Operating System  
company: Microsoft Corporation  
description: NT Kernel & System  
Bug check description: The kernel has detected the corruption of a critical data structure.  
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.  
 
 
 
On Mon 05/06/2017 19:50:29 your computer crashed  
crash dump file: C:\Windows\memory.dmp  
This was probably caused by the following module: ntkrnlmp.exe (nt!KeBugCheckEx+0x0)
Bugcheck code: 0x139 (0x3, 0xFFFFA58191C088F0, 0xFFFFA58191C08848, 0x0)  
Error: KERNEL_SECURITY_CHECK_FAILURE  
Bug check description: The kernel has detected the corruption of a critical data structure.  
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.  
 
 
 
On Mon 05/06/2017 19:42:32 your computer crashed  
crash dump file: C:\Windows\Minidump\060517-12703-01.dmp  
This was probably caused by the following module: ntoskrnl.exe (nt+0x16C310)  
Bugcheck code: 0x139 (0x3, 0xFFFFE2019B836F30, 0xFFFFE2019B836E88, 0x0)  
Error: KERNEL_SECURITY_CHECK_FAILURE  
file path: C:\Windows\system32\ntoskrnl.exe  
product: Microsoft® Windows® Operating System  
company: Microsoft Corporation  
description: NT Kernel & System  
Bug check description: The kernel has detected the corruption of a critical data structure.  
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.  
 
 
 
On Mon 05/06/2017 19:40:14 your computer crashed  
crash dump file: C:\Windows\Minidump\060517-12296-01.dmp  
This was probably caused by the following module: ntoskrnl.exe (nt+0x16C310)  
Bugcheck code: 0xA (0x8, 0x2, 0x0, 0xFFFFF80068CA23BF)  
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 Mon 05/06/2017 19:33:19 your computer crashed  
crash dump file: C:\Windows\Minidump\060517-21703-01.dmp  
This was probably caused by the following module: ntoskrnl.exe (nt+0x16C310)  
Bugcheck code: 0x19 (0xD, 0xFFFFDC025FC3CDA0, 0x0, 0xC5221EC1FA25578C)  
Error: BAD_POOL_HEADER  
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 pool header is corrupt.  
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem. 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. This problem might also be caused because of overheating (thermal issue).
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time