BSOD ntoskrnl.exe
Hors ligneAntho123 Le 11/07/2016 à 11:59 Profil de Antho123 Configuration de Antho123

Bonjour,

Je reviens sur ce forum avec un problème lié à un programme système prénommé ntoskrnl.exe *Ceci est un ordinateur portable.

Voila le rapport d'analyse du logiciel WhoCrashed :
System Information (local)
Computer name: ANTHONY
Windows version: Windows 10 , 10.0, build: 10586
Windows dir: C:\WINDOWS
Hardware: X555LB, ASUSTeK COMPUTER INC.
CPU: GenuineIntel Intel(R) Core(TM) i7-5500U CPU @ 2.40GHz Intel586, level: 6
4 logical processors, active mask: 15
RAM: 6340567040 bytes total
Crash Dump Analysis
Crash dump directory: C:\WINDOWS\Minidump
Crash dumps are enabled on your computer


On Mon 11/07/2016 09:34:26 GMT your computer crashed
crash dump file: C:\WINDOWS\Minidump\071116-32062-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x142780)
Bugcheck code: 0x133 (0x1, 0x1E00, 0x0, 0x0)
Error: DPC_WATCHDOG_VIOLATION
file path: C:\WINDOWS\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: The DPC watchdog detected a prolonged run time at an IRQL of DISPATCH_LEVEL or above.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem. 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 Mon 11/07/2016 09:34:26 GMT your computer crashed
crash dump file: C:\WINDOWS\memory.dmp
This was probably caused by the following module: hal.dll (hal!HalRequestSoftwareInterrupt+0x1E6)
Bugcheck code: 0x133 (0x1, 0x1E00, 0x0, 0x0)
Error: DPC_WATCHDOG_VIOLATION
file path: C:\WINDOWS\system32\hal.dll
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: Hardware Abstraction Layer DLL
Bug check description: The DPC watchdog detected a prolonged run time at an IRQL of DISPATCH_LEVEL or above.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem. This problem might also be caused because of overheating (thermal issue).
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 Sun 10/07/2016 16:19:10 GMT your computer crashed
crash dump file: C:\WINDOWS\Minidump\071016-31781-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x142780)
Bugcheck code: 0x133 (0x1, 0x1E00, 0x0, 0x0)
Error: DPC_WATCHDOG_VIOLATION
file path: C:\WINDOWS\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: The DPC watchdog detected a prolonged run time at an IRQL of DISPATCH_LEVEL or above.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem. 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 10/07/2016 16:15:07 GMT your computer crashed
crash dump file: C:\WINDOWS\Minidump\071016-30750-01.dmp
This was probably caused by the following module: Unknown ()
Bugcheck code: 0x0 (0x0, 0x0, 0x0, 0x0)
Error: CUSTOM_ERROR
A third party driver was identified as the probable root cause of this system error.
Google query: CUSTOM_ERROR

On Sun 10/07/2016 15:55:01 GMT your computer crashed
crash dump file: C:\WINDOWS\Minidump\071016-31515-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x142780)
Bugcheck code: 0x133 (0x1, 0x1E00, 0x0, 0x0)
Error: DPC_WATCHDOG_VIOLATION
file path: C:\WINDOWS\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: The DPC watchdog detected a prolonged run time at an IRQL of DISPATCH_LEVEL or above.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem. 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 10/07/2016 15:27:37 GMT your computer crashed
crash dump file: C:\WINDOWS\Minidump\071016-32765-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x142780)
Bugcheck code: 0x133 (0x0, 0x501, 0x500, 0x0)
Error: DPC_WATCHDOG_VIOLATION
file path: C:\WINDOWS\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: The DPC watchdog detected a prolonged run time at an IRQL of DISPATCH_LEVEL or above.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem. 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 10/07/2016 14:28:15 GMT your computer crashed
crash dump file: C:\WINDOWS\Minidump\071016-28359-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x142780)
Bugcheck code: 0x133 (0x1, 0x1E00, 0x0, 0x0)
Error: DPC_WATCHDOG_VIOLATION
file path: C:\WINDOWS\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: The DPC watchdog detected a prolonged run time at an IRQL of DISPATCH_LEVEL or above.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem. 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 10/07/2016 14:05:13 GMT your computer crashed
crash dump file: C:\WINDOWS\Minidump\071016-28781-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x142780)
Bugcheck code: 0x133 (0x1, 0x1E00, 0x0, 0x0)
Error: DPC_WATCHDOG_VIOLATION
file path: C:\WINDOWS\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: The DPC watchdog detected a prolonged run time at an IRQL of DISPATCH_LEVEL or above.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem. 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 10/07/2016 13:49:06 GMT your computer crashed
crash dump file: C:\WINDOWS\Minidump\071016-34890-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x142780)
Bugcheck code: 0x133 (0x1, 0x1E00, 0x0, 0x0)
Error: DPC_WATCHDOG_VIOLATION
file path: C:\WINDOWS\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: The DPC watchdog detected a prolonged run time at an IRQL of DISPATCH_LEVEL or above.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem. 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 Tue 26/04/2016 15:18:35 GMT your computer crashed
crash dump file: C:\WINDOWS\Minidump\042616-37140-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x142760)
Bugcheck code: 0x50 (0xFFFFE0020809B000, 0x0, 0xFFFFD00027FA3911, 0x0)
Error: PAGE_FAULT_IN_NONPAGED_AREA
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 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 the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.

Conclusion

10 crash dumps have been found and analyzed.
Read the topic general suggestions for troubleshooting system crashes for more information.

Note that it's not always possible to state with certainty whether a reported driver is responsible for crashing your system or that the root cause is in another module. Nonetheless it's suggested you look for updates for the products that these drivers belong to and regularly visit Windows update or enable automatic updates for Windows. In case a piece of malfunctioning hardware is causing trouble, a search with Google on the bug check errors together with the model name and brand of your computer may help you investigate this further.

J'espère que ces informations vous suffisent pour pouvoir régler mon problème et je reste évidemment à votre disposition pour connaître des informations complémentaires.

Cordialement,

Antho123

--


SourireAntho123Sourire

Hors ligneTribun Le 12/07/2016 à 05:01 Profil de Tribun Configuration de Tribun

Bonjour.

Informations toutes en Anglais, ce qui est difficile a la compréhension.

Mais le ntoskrnl.exe, est le noyau de Windows. Soit tu l'as trafiqué, soit un programme y a touché. Et pour information, le fait de personnaliser l'interface de Windows, c'est à dire le bootscreen et même le style de Windows, modifie ce fichier. Donc si tu as tenté de modifié le style, c'est la source de l'erreur (style incompatible).

--
Qui aime l'instruction, trouve la connaissance qui vient de la réflexion. PS Créez un point de restauration le plus souvent possible ! cela vous évitera de nombreux ennuis.
Hors ligneAntho123 Le 12/07/2016 à 10:30 Profil de Antho123 Configuration de Antho123

Bonjour,

Je n'ai pas trafiqué le bootscreen. Depuis que Avast ma fait cette analyse et ma mis à jour quelques programmes, ce problème est apparu. Vous pensez que le problème vient de cela ?

--


SourireAntho123Sourire

Hors ligneTribun Le 13/07/2016 à 05:57 Profil de Tribun Configuration de Tribun

Il est fort probable qu'Avast est le coupable de ce problème.

Vu que c'est suite a une mise a jour de certains programmes que tu as ce problème.

--
Qui aime l'instruction, trouve la connaissance qui vient de la réflexion. PS Créez un point de restauration le plus souvent possible ! cela vous évitera de nombreux ennuis.
Hors ligneAntho123 Le 14/07/2016 à 14:08 Profil de Antho123 Configuration de Antho123

Bonjour,

Pour l'instant le problème n'apparaît plus en désinstallant Avast. Je vous tiens au courant.

--


SourireAntho123Sourire

Hors ligneAntho123 Le 19/07/2016 à 10:23 Profil de Antho123 Configuration de Antho123

Bonjour,

Le BSOD a disparu lors de la désinstallation d'Avast.

Merci Tribun pour ton aide.

Cordialement,

--


SourireAntho123Sourire

Vous avez résolu votre problème avec VIC ? Faites-le savoir sur les réseaux sociaux !
Vulgarisation-informatique.com
Cours en informatique & tutoriels