Partager via

BlueScreen Nt Kernel & System

Anonyme
2013-08-24T13:58:40+00:00

Bonjour à tous, je viens à vous car j'ai un très gros problème actuellement avec mon ordinateur, & je ne sais pas comment le régler.

En effet, mon pc fait aléatoirement des BlueScreen, & cela deviens très inquietant.

Voici le rapport des crashs :

Crash dump directory: C:\Windows\Minidump

Crash dumps are enabled on your computer.

On Sat 24/08/2013 13:49:20 GMT your computer crashed

crash dump file: C:\Windows\Minidump\082413-16036-01.dmp

This was probably caused by the following module: [ntoskrnl.exe] (nt+0x75B80)

Bugcheck code: 0x3B (0xC0000005, 0xFFFFF80002CD5A85, 0xFFFFF88003E55E40, 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 Sat 24/08/2013 13:49:20 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, 0xFFFFF80002CD5A85, 0xFFFFF88003E55E40, 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 24/08/2013 12:30:13 GMT your computer crashed

crash dump file: C:\Windows\Minidump\082413-81572-01.dmp

This was probably caused by the following module: [ntfs.sys] (Ntfs+0x4688)

Bugcheck code: 0x24 (0x1904FB, 0xFFFFF8800C7BFB38, 0xFFFFF8800C7BF390, 0xFFFFF80002CD4A85)

Error: [NTFS_FILE_SYSTEM]

file path: C:\Windows\system32\drivers\ntfs.sys

product: [Système d’exploitation Microsoft® Windows®]

company: [Microsoft Corporation]

description: Pilote du système de fichiers NT

Bug check description: This indicates a problem occurred in the NTFS file system.

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 Sat 24/08/2013 03:02:34 GMT your computer crashed

crash dump file: C:\Windows\Minidump\082413-16629-01.dmp

This was probably caused by the following module: [ntoskrnl.exe] (nt+0x75B80)

Bugcheck code: 0x19 (0x22, 0xFFFFF8A00A3F3000, 0x1, 0x0)

Error: [BAD_POOL_HEADER]

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 pool header is corrupt.

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. More often memory corruption happens because of software errors in buggy drivers, not because of faulty RAM modules.

The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.

Merci de votre futur aide.

Windows pour les particuliers | Versions antérieures de Windows | Niveau de performance et défaillances système

Question verrouillée. Cette question a été migrée à partir de la Communauté Support Microsoft. Vous pouvez voter pour indiquer si elle est utile, mais vous ne pouvez pas ajouter de commentaires ou de réponses ni suivre la question.

0 commentaires Aucun commentaire

7 réponses

  1. Anonyme
    2013-08-25T14:01:37+00:00

    Je suis actuellement en train de faire une vérification du disque, quand à sfc, il n'a pas voulu s'effectuer complètement, il s'est bloqué a 16%, je vais essayer après la vérification du disque de recommencer.

    Cette réponse a-t-elle été utile ?

    0 commentaires Aucun commentaire
  2. Anonyme
    2013-08-25T05:52:31+00:00

    as-tu effectué sfc ?

    as-tu faut une vérification du disque?

    Cette réponse a-t-elle été utile ?

    0 commentaires Aucun commentaire