Un Ecran bleu de la mort (BSOD) a cause de ntoskrnl.exe

nanak55 Messages postés 68 Statut Membre -  
nanak55 Messages postés 68 Statut Membre -
Bon jour a tous depuis quelque temps j'ai un problème de BSOD, l'ordi crash d'un seul coup . J'ai fait un analyse avec WhoCrashed et voici le résultat

On Fri 25/10/2013 08:32:34 GMT your computer crashed
crash dump file: C:\Windows\Minidump\102513-42666-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x75BC0)
Bugcheck code: 0x3B (0xC0000005, 0xFFFFF8000316FC12, 0xFFFFF88006542190, 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 Fri 25/10/2013 08:32:34 GMT your computer crashed
crash dump file: C:\Windows\memory.dmp
This was probably caused by the following module: ntkrnlmp.exe (nt!KeBugCheckEx+0x0)
Bugcheck code: 0x3B (0xC0000005, 0xFFFFF8000316FC12, 0xFFFFF88006542190, 0x0)
Error: SYSTEM_SERVICE_EXCEPTION
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 Sat 19/10/2013 06:21:12 GMT your computer crashed
crash dump file: C:\Windows\Minidump\101913-43430-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x75BC0)
Bugcheck code: 0x3B (0xC0000047, 0xFFFFF80002EFE7FC, 0xFFFFF880073F3560, 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 Thu 17/10/2013 10:08:46 GMT your computer crashed
crash dump file: C:\Windows\Minidump\101713-19780-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x75BC0)
Bugcheck code: 0x3B (0xC0000005, 0xFFFFF800031BBE61, 0xFFFFF88003807A70, 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 Thu 17/10/2013 07:24:55 GMT your computer crashed
crash dump file: C:\Windows\Minidump\101713-49842-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x75BC0)
Bugcheck code: 0xA (0xFFF8F000, 0x2, 0x0, 0xFFFFF80002ED5861)
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 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 Mon 14/10/2013 07:12:09 GMT your computer crashed
crash dump file: C:\Windows\Minidump\101413-29312-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x75BC0)
Bugcheck code: 0xA (0x4A8ECB4E, 0x2, 0x0, 0xFFFFF80002E80289)
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 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 Mon 14/10/2013 07:04:40 GMT your computer crashed
crash dump file: C:\Windows\Minidump\101413-30638-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x75BC0)
Bugcheck code: 0xA (0xF8D24CB33, 0x2, 0x0, 0xFFFFF80002E8E289)
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 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.

Alors voila j'ai remarqué que le ntoskrnl.exe se répète pratiquement a chaque fois. Je ne sais pas si la réinstallation de windows va résoudre ce problème c'est pourquoi je ne me décide pas a se lancer. Si vous pourrait m'aider a résoudre ce problème ça sera vraiment très sympa de votre part. Merci d'avance. :(
A voir également:

2 réponses

thrallcss Messages postés 868 Statut Membre 113
 
Selon Whocrashed, ça devrait venir d'un de tes drivers, tu les as mis à jour récemment ?

Tu es passé d'un système d'exploitation 32bit à 64bit ou inversement ?
0
nanak55 Messages postés 68 Statut Membre
 
Non pas de passage et avec MesConfiguration mes drivers sont a jours.
0
nanak55 Messages postés 68 Statut Membre
 
UP
0