Problème de bluescreen windows 10

Horseman -  
 Mathieu -
Bonjour,

Voila, je viens de faire une remise à zéro de mon ordinateur, j'ai installer un SSD et formater mon ancien disque dur, tout en installant windows 10 sur le SSD.

Problème, j'ai des bluescreen assez fréquent, du coup j'ai lancer une analyse avec le logiciel "WhoCrashed" et résultat :

On Sun 25/12/2016 03:54:45 your computer crashed
crash dump file: C:\Windows\Minidump\122516-4671-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x149F90)
Bugcheck code: 0xEF (0xFFFF960214B10800, 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 Sun 25/12/2016 03:54:45 your computer crashed
crash dump file: C:\Windows\memory.dmp
This was probably caused by the following module: ntdll.sys (ntdll!NtTerminateProcess+0x14)
Bugcheck code: 0xEF (0xFFFF960214B10800, 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 Sun 25/12/2016 03:52:30 your computer crashed
crash dump file: C:\Windows\Minidump\122516-4593-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x149F90)
Bugcheck code: 0x1A (0x5100, 0xFFFFB2D140936008, 0x100, 0x20)
Error: MEMORY_MANAGEMENT
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 severe memory management error occurred.
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.

On Sun 25/12/2016 03:00:00 your computer crashed
crash dump file: C:\Windows\Minidump\122516-3875-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x149F90)
Bugcheck code: 0x3B (0xC0000005, 0xFFFFF80204A561D3, 0xFFFFE3010D162480, 0x0)
Error: SYSTEM_SERVICE_EXCEPTION
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 an exception happened while executing a routine that transitions from non-privileged code to privileged code.
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 Sun 25/12/2016 02:54:02 your computer crashed
crash dump file: C:\Windows\Minidump\122516-3468-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x149F90)
Bugcheck code: 0x1A (0x41793, 0xFFFFB5BFFD342608, 0x2, 0x1)
Error: MEMORY_MANAGEMENT
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation

Voila, j'aimerai avoir votre aide afin de résoudre ce problème car je n'y comprend rien, merci d'avance.
A voir également:

2 réponses

jeanbern Messages postés 16970 Date d'inscription   Statut Contributeur Dernière intervention   4 990
 
Salut,
Il te faut faire une réparation avec l'invité de commande :
en tapant chksdk /r
0
Mathieu
 
Bonsoir, merci pour ton aide précieuse, problème résolu, toutefois si tu sais d'où vient ce problème je t'en serai reconnaissant de me le faire parvenir, je suis curieux de savoir ^^
0