Ecran bleu ksecdd.sys et ntoskrnl.exe [Résolu]

Signaler
Messages postés
149
Date d'inscription
vendredi 8 juillet 2011
Statut
Membre
Dernière intervention
15 août 2020
-
Messages postés
1029
Date d'inscription
dimanche 15 mars 2020
Statut
Membre
Dernière intervention
27 octobre 2020
-
Bonjour
Depuis que j'ai monté mon PC, j'ai des écrans bleus, j'ai essayé toutes solutions auxquelles j'ai pu penser. Les deux seules qui ont semblé avoir un effet quelconque, c'est à dire qu'il n'y a pas eu d'écran bleu pendant 1 mois sont :
Réinitialiser Windows
Mettre à jour le BiOS

Voici le rapport de WhoCrashed:

On Fri 10/04/2020 14:47:14 your computer crashed or a problem was reported
crash dump file: C:\WINDOWS\Minidump\041020-12328-01.dmp
This was probably caused by the following module: ksecdd.sys (0xFFFFF8041C45B4B4)
Bugcheck code: 0x109 (0xA3A0145B597044F4, 0xB3B720E1ABF0879D, 0xFFFFF8041C45B4B4, 0x1)
Error: CRITICAL_STRUCTURE_CORRUPTION
file path: C:\WINDOWS\system32\drivers\ksecdd.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: Kernel Security Support Provider Interface
Bug check description: This indicates that the kernel has detected critical kernel code or data corruption.
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. This may be because of a hardware issue such as faulty RAM, overheating (thermal issue) or because of a buggy driver. This problem might also be caused because of overheating (thermal issue).
The crash took place in a 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 10/04/2020 14:47:14 your computer crashed or a problem was reported
crash dump file: C:\WINDOWS\MEMORY.DMP
This was probably caused by the following module: ksecdd.sys (0xFFFFF8041C45B4B4)
Bugcheck code: 0x109 (0xA3A0145B597044F4, 0xB3B720E1ABF0879D, 0xFFFFF8041C45B4B4, 0x1)
Error: CRITICAL_STRUCTURE_CORRUPTION
file path: C:\WINDOWS\system32\drivers\ksecdd.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: Kernel Security Support Provider Interface
Bug check description: This indicates that the kernel has detected critical kernel code or data corruption.
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. This may be because of a hardware issue such as faulty RAM, overheating (thermal issue) or because of a buggy driver. This problem might also be caused because of overheating (thermal issue).
The crash took place in a 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 Mon 06/04/2020 13:19:41 your computer crashed or a problem was reported
crash dump file: C:\WINDOWS\Minidump\040620-10015-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x13E811)
Bugcheck code: 0x1000007E (0xFFFFFFFFC0000005, 0xFFFFF8032E53E811, 0xFFFFFB88684D99C8, 0xFFFFBC8169CD8930)
Error: SYSTEM_THREAD_EXCEPTION_NOT_HANDLED_M
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 system thread 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 the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.



On Thu 05/03/2020 19:08:47 your computer crashed or a problem was reported
crash dump file: C:\WINDOWS\Minidump\030520-13281-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x1C1510)
Bugcheck code: 0x139 (0x3, 0xFFFFAF80C788F460, 0xFFFFAF80C788F3B8, 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 28/02/2020 17:07:51 your computer crashed or a problem was reported
crash dump file: C:\WINDOWS\Minidump\022820-10265-01.dmp
This was probably caused by the following module: Unknown (0xFFFFF80774EE8BDA)
Bugcheck code: 0xD1 (0x0, 0x2, 0x1, 0xFFFFF80774EE8BDA)
Error: DRIVER_IRQL_NOT_LESS_OR_EQUAL
Bug check description: This indicates that a kernel-mode driver attempted to access pageable memory at a process IRQL that was too high.
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.
A third party driver was identified as the probable root cause of this system error.
Google query: DRIVER_IRQL_NOT_LESS_OR_EQUAL



On Sun 23/02/2020 13:38:30 your computer crashed or a problem was reported
crash dump file: C:\WINDOWS\Minidump\022320-11593-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x1C1510)
Bugcheck code: 0x4A (0x7FFA3E79C784, 0x2, 0x0, 0xFFFFCF07E6B1FA80)
Error: IRQL_GT_ZERO_AT_SYSTEM_SERVICE
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 thread is returning to user mode from a system call when its IRQL is still above PASSIVE_LEVEL.
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.

S'il vous plait j'ai vraiment besoin d'aide.

1 réponse

Messages postés
1029
Date d'inscription
dimanche 15 mars 2020
Statut
Membre
Dernière intervention
27 octobre 2020
112
Cela semble du à un drivers. Met tous tes drivers à jour sur le site du fabricant du PC ou de la carte-mère, pas ailleurs.