Qui pourrait me traduire le Crash Dump Analysis de WhoCrashed [Résolu] - Windows 7

A voir également:Qui pourrait me traduire le crash dump analysis de whocrashedCrash dump ✓ - Forum - Matériel informatique Collecting data for crash dump ✓ - Forum - Windows Ecran bleu windows 7 crash dump - Conseils pratiques - Windows Utorrent has crashed a crash dump has been saved ✓ - Forum - Téléchargement Crash dump windows ✓ - Forum - Webmaster

Bonjour,

j'ai un ordinateur sous Win7 qui crash avec la page bleue. Whocrashed m'a fait un rapport d'analyse ci-dessous.
pouvez vous me dire ce que ça signifie

merci d'avance

On Fri 08/02/2019 17:52:45 your computer crashed or a problem was reported
crash dump file: C:\Windows\Minidump\020819-29390-01.dmp
This was probably caused by the following module: ntfs.sys (Ntfs+0x1A9A9)
Bugcheck code: 0x24 (0x1904FB, 0xFFFFFFFFA3CA3A48, 0xFFFFFFFFA3CA3620, 0xFFFFFFFF81591AAC)
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 file system driver. Since there is no other responsible driver detected, this could be pointing to a malfunctioning drive or corrupted disk. It's suggested that you run CHKDSK.



On Fri 08/02/2019 17:52:45 your computer crashed or a problem was reported
crash dump file: C:\Windows\MEMORY.DMP
This was probably caused by the following module: ntfs.sys (Ntfs+0x1A9A9)
Bugcheck code: 0x24 (0x1904FB, 0xFFFFFFFFA3CA3A48, 0xFFFFFFFFA3CA3620, 0xFFFFFFFF81591AAC)
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 file system driver. Since there is no other responsible driver detected, this could be pointing to a malfunctioning drive or corrupted disk. It's suggested that you run CHKDSK.



On Thu 07/02/2019 08:57:59 your computer crashed or a problem was reported
crash dump file: C:\Windows\Minidump\020719-28906-01.dmp
This was probably caused by the following module: fltmgr.sys (fltmgr+0x2324)
Bugcheck code: 0x19 (0x20, 0xFFFFFFFFAD626730, 0xFFFFFFFFAD626800, 0xA1A0803)
Error: BAD_POOL_HEADER
file path: C:\Windows\system32\drivers\fltmgr.sys
product: Système d’exploitation Microsoft® Windows®
company: Microsoft Corporation
description: Gestionnaire de filtres de système de fichiers Microsoft
Bug check description: This indicates that a pool header is corrupt.
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 file system driver. Since there is no other responsible driver detected, this could be pointing to a malfunctioning drive or corrupted disk. It's suggested that you run CHKDSK.



On Wed 06/02/2019 19:58:03 your computer crashed or a problem was reported
crash dump file: C:\Windows\Minidump\020619-32417-01.dmp
This was probably caused by the following module: fltmgr.sys (fltmgr+0x20DF4)
Bugcheck code: 0xC5 (0x4, 0x2, 0x0, 0xFFFFFFFF8272187B)
Error: DRIVER_CORRUPTED_EXPOOL
file path: C:\Windows\system32\drivers\fltmgr.sys
product: Système d’exploitation Microsoft® Windows®
company: Microsoft Corporation
description: Gestionnaire de filtres de système de fichiers Microsoft
Bug check description: This indicates that the system attempted to access invalid 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.
The crash took place in a file system driver. Since there is no other responsible driver detected, this could be pointing to a malfunctioning drive or corrupted disk. It's suggested that you run CHKDSK.



On Mon 04/02/2019 17:34:39 your computer crashed or a problem was reported
crash dump file: C:\Windows\Minidump\020419-29577-01.dmp
This was probably caused by the following module: netbt.sys (netbt+0x1139)
Bugcheck code: 0xD1 (0x0, 0x2, 0x0, 0xFFFFFFFF91294139)
Error: DRIVER_IRQL_NOT_LESS_OR_EQUAL
file path: C:\Windows\system32\drivers\netbt.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: MBT Transport driver
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.
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 21/01/2019 18:34:10 your computer crashed or a problem was reported
crash dump file: C:\Windows\Minidump\012119-29842-01.dmp
This was probably caused by the following module: fvevol.sys (fvevol+0x1854)
Bugcheck code: 0x1000007E (0xFFFFFFFFC0000005, 0xFFFFFFFF8266F58F, 0xFFFFFFFF8DB971E0, 0xFFFFFFFF8DB96DC0)
Error: SYSTEM_THREAD_EXCEPTION_NOT_HANDLED_M
file path: C:\Windows\system32\drivers\fvevol.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: BitLocker Drive Encryption Driver
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 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 Tue 09/10/2018 13:38:59 your computer crashed or a problem was reported
crash dump file: C:\Windows\Minidump\100918-249710-01.dmp
This was probably caused by the following module: npfs.sys (Npfs+0xA0D9)
Bugcheck code: 0x18 (0xFFFFFFFF8594AF78, 0xFFFFFFFF85D8E630, 0x1, 0x3)
Error: REFERENCE_BY_POINTER
file path: C:\Windows\system32\drivers\npfs.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NPFS Driver
Bug check description: This indicates that the reference count of an object is illegal for the current state of the object.
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 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.

Forum

A voir également:Qui pourrait me traduire le crash dump analysis de whocrashedCrash dump ✓ - Forum - Matériel informatique Collecting data for crash dump ✓ - Forum - Windows Ecran bleu windows 7 crash dump - Conseils pratiques - Windows Utorrent has crashed a crash dump has been saved ✓ - Forum - Téléchargement Crash dump windows ✓ - Forum - Webmaster

Web: www.shapebootstrap.net

6 réponses

Marsh

NOVEMBER 9, 2013 AT 9:15 PM

Salut,

Vu que ça plante sur différents pilotes, il faut envisager un problème matériel comme la mémoire.

Vérifie l'état de santé de tes barrettes de mémoire :
- memtest : vérifier barette de mémoire (malekal.com)
- memtest : vérifier barette de mémoire (CCM)

~~

Vérifie déjà le disque dur : Comment vérifier la santé du disque dur
Avec CrystalDiskInfo
- Télécharger CrystalDiskInfo
Il faut que le statut soit en bleu, sinon c'est pas bon signe.
Plus d'explications : CrystalDiskInfo.


et enfin :

Pour vérifier ton ordinateur, pour d'éventuels infections et avoir un état général du système :

Suis le tutoriel FRST en cliquant sur ce lien bleu. ( prends le temps de lire attentivement - tout y est bien expliqué ).

Télécharge et lance le scan FRST,
Attendre la fin du scan, un message indique que l'analyse est terminée.

Trois rapports FRST seront générés :
  • FRST.txt
  • Shortcut.
  • Additionnal.txt


Envoie ces 3 rapports sur le site https://pjjoint.malekal.com/ et en retour donne les 3 liens pjjoint qui mènent aux rapports ici dans une nouvelle réponse afin que l'on puisse les consulter.

(Les liens bleus mènent à des tutoriels explicatifs pas à pas, clic dessus pour avoir les instructions plus précises à suivre).



Dire « Merci » 1

Heureux de vous avoir aidé ! Vous nous appréciez ? Donnez votre avis sur nous ! Evaluez CommentCaMarche

CCM 40347 internautes nous ont dit merci ce mois-ci

Reply

Marsh

NOVEMBER 9, 2013 AT 9:15 PM

Bonjour,

Commence par tester ton dd avec ceci :
https://www.commentcamarche.net/download/telecharger-34068243-crystaldiskinfo

Reply

Marsh

NOVEMBER 9, 2013 AT 9:15 PM

Bonjour

Suivant le traducteur Google =

Description de la vérification de bogue: Cela indique qu'un problème est survenu dans le système de fichiers NTFS.
L'accident s'est produit dans un pilote de système de fichiers. Comme aucun autre pilote responsable n'a été détecté, il est possible que cela indique un lecteur défectueux ou un disque corrompu. Il est suggéré que vous exécutiez CHKDSK.

Reply

Marsh

NOVEMBER 9, 2013 AT 9:15 PM

Bonsoir,

merci pour toutes ces infos. j'ai utilisé Crystaldiskinfo et mes disques durs sont ok. j'ai pas réussi à lancer memtest. je l'installe sur une clé USB et je reboot dessus mais rien ne se passe.

j'ai lancé FRST. voici les liens vers les fichiers résultat
FRST : https://pjjoint.malekal.com/files.php?id=FRST_20190212_k13l9l7j5h6
addition : https://pjjoint.malekal.com/files.php?id=20190212_w10k15o15r12w15
shortcut : https://pjjoint.malekal.com/files.php?id=20190212_k1010o6i10f8

Reply

Marsh

NOVEMBER 9, 2013 AT 9:15 PM

Désinstalle
AVG
CCleaner
Java
Nero (sauf si tu utilises)


et vois si ça continue de planter sans AVG.
Windows Defender va prendre le relai pour protéger ton ordinateur.

Reply

Marsh

NOVEMBER 9, 2013 AT 9:15 PM

Bonjour,

j'ai trouvé la cause de mon problème. une barette de RAM (j'ai 2 x 2 GO) qui ne marchait pas correctement. je l'ai changé et j'en ai profité pour passer de win 10 32 bits à 64 bits car j'ai appris que 32 bits n'utilisait que 3 GO maxi !

merci pour votre aide.

Reply
réponses:
  • auteur

    ca roule :)

Leave a Replay

Make sure you enter the(*)required information where indicate.HTML code is not allowed