Bonjour
 
j'ai des écrans bleu a répétition, donc j'ai décidé d'installé Whocrashed et il a trouvé:
 
System Information (local)
--------------------------------------------------------------------------------
 
Computer name: DESKTOP-S1JGGOG
Windows version: Windows 10 , 10.0, build: 16299
Windows dir: C:\WINDOWS
Hardware: GL753VE, ASUSTeK COMPUTER INC.
CPU: GenuineIntel Intel(R) Core(TM) i7-7700HQ CPU @ 2.80GHz Intel586, level: 6
8 logical processors, active mask: 255
RAM: 17059098624 bytes total
 
 
 
 
--------------------------------------------------------------------------------
Crash Dump Analysis
--------------------------------------------------------------------------------
 
Crash dumps are enabled on your computer.  
 
Crash dump directories:  
C:\WINDOWS
C:\WINDOWS\Minidump
 
On Fri 23/02/2018 19:04:39 your computer crashed or a problem was reported
crash dump file: C:\WINDOWS\Minidump\022318-6453-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x175430)  
Bugcheck code: 0xEF (0xFFFF930BF621C080, 0x0, 0x0, 0x0)
Error: CRITICAL_PROCESS_DIED
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 critical system process died.  
There is a possibility this problem was caused by a virus or other malware.  
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.  
 
 
 
On Fri 23/02/2018 19:04:39 your computer crashed or a problem was reported
crash dump file: C:\WINDOWS\MEMORY.DMP
This was probably caused by the following module: ntdll.sys (ntdll!NtTerminateProcess+0x14)  
Bugcheck code: 0xEF (0xFFFF930BF621C080, 0x0, 0x0, 0x0)
Error: CRITICAL_PROCESS_DIED
Bug check description: This indicates that a critical system process died.  
There is a possibility this problem was caused by a virus or other malware.  
A third party driver was identified as the probable root cause of this system error. It is suggested you look for an update for the following driver: ntdll.sys .  
Google query: ntdll.sys CRITICAL_PROCESS_DIED
 
 
 
On Fri 23/02/2018 18:57:41 your computer crashed or a problem was reported
crash dump file: C:\WINDOWS\Minidump\022318-6750-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x175430)  
Bugcheck code: 0x139 (0x3, 0xFFFF900943AEFE00, 0xFFFF900943AEFD58, 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 Fri 23/02/2018 13:58:32 your computer crashed or a problem was reported
crash dump file: C:\WINDOWS\Minidump\022318-6734-01.dmp
This was probably caused by the following module: ntfs.sys (0xFFFFF800859E17F3)  
Bugcheck code: 0x50 (0xFFFFF80A8599C020, 0x0, 0xFFFFF800859E17F3, 0x2)
Error: PAGE_FAULT_IN_NONPAGED_AREA
file path: C:\WINDOWS\system32\drivers\ntfs.sys
product: Système d’exploitation Microsoft® Windows®
company: Microsoft Corporation
description: Pilote du système de fichiers NT
Bug check description: This indicates that invalid system memory has been referenced.  
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 file system driver. Since there is no other responsible driver detected, this could be pointing to a malfunctioning drive or corrupted disk. It's suggested that you run CHKDSK.
 
 
 
On Fri 23/02/2018 12:21:46 your computer crashed or a problem was reported
crash dump file: C:\WINDOWS\Minidump\022318-7015-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x175430)  
Bugcheck code: 0xA (0xFFFFB58F9E000000, 0xFF, 0x0, 0xFFFFF801A02CCDE4)
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 is a software bug.  
This bug check belongs to the crash dump test that you have performed with WhoCrashed or other software. It means that a crash dump file was properly written out.  
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.  
 
 
 
On Fri 23/02/2018 12:19:24 your computer crashed or a problem was reported
crash dump file: C:\WINDOWS\Minidump\022318-6656-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x175430)  
Bugcheck code: 0x139 (0x3, 0xFFFFAC0D8011F0C0, 0xFFFFAC0D8011F018, 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.  
 
et comme il s'agit de fichier Windows je n'ai pas envie de faire n'importe quoi  
 
aurait-il une âme charitable qui pourrait m'aidé.
 
Merci par avance.

Voici un lien qui pourrait t'être utile : https://www.malekal.com/ntoskrnl-exe/

Vu les erreurs et les heures auxquelles elles sont arrivées, je pencherai pour soit un souci de Windows, soit un souci matériel.
 
Dans l'ordre, vérifie :
- que tu n'as pas un driver foireux (et qu'ils sont à jour)
- que Windows est intègre (avec la commande sfc /scannow)
- que ta ram n'a pas de soucis avec Memtest
- que tes disques sont en bon état avec CrystalDiskInfo

Bonjour, j'ai aussi un ASUS, ce n'est pas le même mais j'ai eu aussi des écrans bleus mais souvent avec "machine check exception". Comme son nom l'indique spécifique de la machine. La seule solution qui a marché et qui marche encore lorsque cela se produit c'est d'enlever une barette RAM et lorsque cela se reproduit tout simplement de la remettre. Les RAM ne sont pas en cause mais plutôt leur management. Alors si cette solution peut servir je la donne. Un autre point est d'avoir les derniers drivers des fabriquants (NVIDIA, Realtek, Atheros,...etc