Problème avec ntoskrnl.exe (crash pc)
Fermé
anonymeN1
Messages postés
253
Date d'inscription
lundi 5 décembre 2011
Statut
Membre
Dernière intervention
21 février 2015
-
21 juin 2014 à 13:25
anonymeN1 Messages postés 253 Date d'inscription lundi 5 décembre 2011 Statut Membre Dernière intervention 21 février 2015 - 21 juin 2014 à 14:29
anonymeN1 Messages postés 253 Date d'inscription lundi 5 décembre 2011 Statut Membre Dernière intervention 21 février 2015 - 21 juin 2014 à 14:29
A voir également:
- Problème avec ntoskrnl.exe (crash pc)
- Benchmark pc - Guide
- Reinitialiser pc - Guide
- Pc lent - Guide
- Whatsapp pc - Télécharger - Messagerie
- Double ecran pc - Guide
1 réponse
anonymeN1
Messages postés
253
Date d'inscription
lundi 5 décembre 2011
Statut
Membre
Dernière intervention
21 février 2015
92
21 juin 2014 à 14:29
21 juin 2014 à 14:29
Lorsque j'allume mon pc il s'éteint au bout de 15min sous forme de bsod win8 ( smilley ;) + message d'erreur "UNEXPECTED_KERNEL_MODE_TRAP") alors le pc se rallume (il est récent) et j'analyse le pb avec who crashed qui me donne ce message :
Crash dump directory: C:\WINDOWS\Minidump
Crash dumps are enabled on your computer.
On Sat 21/06/2014 11:16:42 GMT your computer crashed
crash dump file: C:\WINDOWS\Minidump\062114-18546-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x153FA0)
Bugcheck code: 0x7F (0x8, 0xFFFFD0005EF68130, 0xFFFFD00062C2C000, 0xFFFFF800432A732B)
Error: UNEXPECTED_KERNEL_MODE_TRAP
file path: C:\WINDOWS\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This bug check indicates that the Intel CPU generated a trap and the kernel failed to catch this trap.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.
On Sat 21/06/2014 11:16:42 GMT your computer crashed
crash dump file: C:\WINDOWS\memory.dmp
This was probably caused by the following module: netio.sys (NETIO!NetioFreeCloneNetBufferList+0x10A)
Bugcheck code: 0x7F (0x8, 0xFFFFD0005EF68130, 0xFFFFD00062C2C000, 0xFFFFF800432A732B)
Error: UNEXPECTED_KERNEL_MODE_TRAP
file path: C:\WINDOWS\system32\drivers\netio.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: Network I/O Subsystem
Bug check description: This bug check indicates that the Intel CPU generated a trap and the kernel failed to catch this trap.
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.
Crash dump directory: C:\WINDOWS\Minidump
Crash dumps are enabled on your computer.
On Sat 21/06/2014 11:16:42 GMT your computer crashed
crash dump file: C:\WINDOWS\Minidump\062114-18546-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x153FA0)
Bugcheck code: 0x7F (0x8, 0xFFFFD0005EF68130, 0xFFFFD00062C2C000, 0xFFFFF800432A732B)
Error: UNEXPECTED_KERNEL_MODE_TRAP
file path: C:\WINDOWS\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This bug check indicates that the Intel CPU generated a trap and the kernel failed to catch this trap.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.
On Sat 21/06/2014 11:16:42 GMT your computer crashed
crash dump file: C:\WINDOWS\memory.dmp
This was probably caused by the following module: netio.sys (NETIO!NetioFreeCloneNetBufferList+0x10A)
Bugcheck code: 0x7F (0x8, 0xFFFFD0005EF68130, 0xFFFFD00062C2C000, 0xFFFFF800432A732B)
Error: UNEXPECTED_KERNEL_MODE_TRAP
file path: C:\WINDOWS\system32\drivers\netio.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: Network I/O Subsystem
Bug check description: This bug check indicates that the Intel CPU generated a trap and the kernel failed to catch this trap.
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.
