Blue screen
ValakGames
Messages postés
2
Date d'inscription
Statut
Membre
Dernière intervention
-
Malekal_morte- Messages postés 180304 Date d'inscription Statut Modérateur, Contributeur sécurité Dernière intervention -
Malekal_morte- Messages postés 180304 Date d'inscription Statut Modérateur, Contributeur sécurité Dernière intervention -
Bonjour,
depuis plusieurs mois j'ai des blue screen sur mon pc(monté par moi-même) peut importe le moment ou la tache effectué.Voici mon rapport Whocrashed:
Crash Dump Analysis
Crash dumps are enabled on your computer.
Crash dump directories:
C:\WINDOWS
C:\WINDOWS\Minidump
On Thu 19/12/2019 22:09:03 your computer crashed or a problem was reported
crash dump file: C:\WINDOWS\Minidump\121919-11062-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x1C14E0)
Bugcheck code: 0x109 (0xA39FD268901EB9C1, 0x0, 0x18F332BDCC0A284E, 0x102)
Error: CRITICAL_STRUCTURE_CORRUPTION
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 the kernel has detected critical kernel code or data corruption.
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. 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 the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.
On Thu 19/12/2019 22:09:03 your computer crashed or a problem was reported
crash dump file: C:\WINDOWS\MEMORY.DMP
This was probably caused by the following module: ntkrnlmp.exe (nt!KeBugCheckEx+0x0)
Bugcheck code: 0x109 (0xA39FD268901EB9C1, 0x0, 0x18F332BDCC0A284E, 0x102)
Error: CRITICAL_STRUCTURE_CORRUPTION
Bug check description: This indicates that the kernel has detected critical kernel code or data corruption.
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. 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 the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.
On Thu 19/12/2019 22:05:40 your computer crashed or a problem was reported
crash dump file: C:\WINDOWS\Minidump\121919-10984-01.dmp
This was probably caused by the following module: Unknown (0x0000000000000000)
Bugcheck code: 0x13A (0x9, 0xFFFFB18AE0C02000, 0xFFFFB18AEF7C7E30, 0x0)
Error: KERNEL_MODE_HEAP_CORRUPTION
Bug check description: This indicates that the kernel mode heap manager has detected corruption in a heap.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
A third party driver was identified as the probable root cause of this system error.
Google query: KERNEL_MODE_HEAP_CORRUPTION
On Sun 15/12/2019 19:19:26 your computer crashed or a problem was reported
crash dump file: C:\WINDOWS\Minidump\121519-12328-01.dmp
This was probably caused by the following module: ntfs.sys (0xFFFFF80108B60729)
Bugcheck code: 0x1000007E (0xFFFFFFFFC0000005, 0xFFFFF80108B60729, 0xFFFF9A82CF2A41C8, 0xFFFF9A82CF2A3A10)
Error: SYSTEM_THREAD_EXCEPTION_NOT_HANDLED_M
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 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 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 06/12/2019 20:42:47 your computer crashed or a problem was reported
crash dump file: C:\WINDOWS\Minidump\120619-10531-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x1C14E0)
Bugcheck code: 0xA (0x106DC2F0, 0x2, 0x0, 0xFFFFF8061583EEEE)
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 is a software bug.
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 the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.
On Thu 14/11/2019 22:13:46 your computer crashed or a problem was reported
crash dump file: C:\WINDOWS\Minidump\111419-10250-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x1C1220)
Bugcheck code: 0xFC (0xFFFFA787BBCC4330, 0x8A000003EC2009E3, 0xFFFFF801402673D0, 0x3)
Error: ATTEMPTED_EXECUTE_OF_NOEXECUTE_MEMORY
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 attempt was made to execute non-executable memory.
This may be a case of memory corruption. More often memory corruption happens because of software errors in buggy drivers, not because of faulty RAM modules. Memory corruption can also occur because of overheating (thermal issue). There is a possibility this problem was caused by a virus or other malware.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time
depuis plusieurs mois j'ai des blue screen sur mon pc(monté par moi-même) peut importe le moment ou la tache effectué.Voici mon rapport Whocrashed:
Crash Dump Analysis
Crash dumps are enabled on your computer.
Crash dump directories:
C:\WINDOWS
C:\WINDOWS\Minidump
On Thu 19/12/2019 22:09:03 your computer crashed or a problem was reported
crash dump file: C:\WINDOWS\Minidump\121919-11062-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x1C14E0)
Bugcheck code: 0x109 (0xA39FD268901EB9C1, 0x0, 0x18F332BDCC0A284E, 0x102)
Error: CRITICAL_STRUCTURE_CORRUPTION
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 the kernel has detected critical kernel code or data corruption.
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. 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 the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.
On Thu 19/12/2019 22:09:03 your computer crashed or a problem was reported
crash dump file: C:\WINDOWS\MEMORY.DMP
This was probably caused by the following module: ntkrnlmp.exe (nt!KeBugCheckEx+0x0)
Bugcheck code: 0x109 (0xA39FD268901EB9C1, 0x0, 0x18F332BDCC0A284E, 0x102)
Error: CRITICAL_STRUCTURE_CORRUPTION
Bug check description: This indicates that the kernel has detected critical kernel code or data corruption.
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. 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 the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.
On Thu 19/12/2019 22:05:40 your computer crashed or a problem was reported
crash dump file: C:\WINDOWS\Minidump\121919-10984-01.dmp
This was probably caused by the following module: Unknown (0x0000000000000000)
Bugcheck code: 0x13A (0x9, 0xFFFFB18AE0C02000, 0xFFFFB18AEF7C7E30, 0x0)
Error: KERNEL_MODE_HEAP_CORRUPTION
Bug check description: This indicates that the kernel mode heap manager has detected corruption in a heap.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
A third party driver was identified as the probable root cause of this system error.
Google query: KERNEL_MODE_HEAP_CORRUPTION
On Sun 15/12/2019 19:19:26 your computer crashed or a problem was reported
crash dump file: C:\WINDOWS\Minidump\121519-12328-01.dmp
This was probably caused by the following module: ntfs.sys (0xFFFFF80108B60729)
Bugcheck code: 0x1000007E (0xFFFFFFFFC0000005, 0xFFFFF80108B60729, 0xFFFF9A82CF2A41C8, 0xFFFF9A82CF2A3A10)
Error: SYSTEM_THREAD_EXCEPTION_NOT_HANDLED_M
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 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 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 06/12/2019 20:42:47 your computer crashed or a problem was reported
crash dump file: C:\WINDOWS\Minidump\120619-10531-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x1C14E0)
Bugcheck code: 0xA (0x106DC2F0, 0x2, 0x0, 0xFFFFF8061583EEEE)
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 is a software bug.
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 the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.
On Thu 14/11/2019 22:13:46 your computer crashed or a problem was reported
crash dump file: C:\WINDOWS\Minidump\111419-10250-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x1C1220)
Bugcheck code: 0xFC (0xFFFFA787BBCC4330, 0x8A000003EC2009E3, 0xFFFFF801402673D0, 0x3)
Error: ATTEMPTED_EXECUTE_OF_NOEXECUTE_MEMORY
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 attempt was made to execute non-executable memory.
This may be a case of memory corruption. More often memory corruption happens because of software errors in buggy drivers, not because of faulty RAM modules. Memory corruption can also occur because of overheating (thermal issue). There is a possibility this problem was caused by a virus or other malware.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time
A voir également:
- Blue screen
- Blue screen windows 10 - Guide
- Screen whatsapp - Accueil - Messagerie instantanée
- Blue griffon - Télécharger - HTML
- Apowersoft screen recorder - Télécharger - Capture d'écran
- Blue iris - Télécharger - Divers Utilitaires
4 réponses
Bonsoir,
Essaye de faire tout cela.
1) 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)
Utilise bien memtest86+ et pas celui de Windows.
2) Cela n'est pas normal qu'une partition passe en RAW, outre les coupures de courants ou autre, il faut s'assurer que le disque dur n'a pas un problème matériel.
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: Vérifier l’état de santé du disque dur.
3) 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 :
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).
Essaye de faire tout cela.
1) 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)
Utilise bien memtest86+ et pas celui de Windows.
2) Cela n'est pas normal qu'une partition passe en RAW, outre les coupures de courants ou autre, il faut s'assurer que le disque dur n'a pas un problème matériel.
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: Vérifier l’état de santé du disque dur.
3) 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).
Bonjour j'ai effectuer tous les test et le test memtest86+ a découvert plein d’erreur de ram en rouge.Mon ssd a 100% de santé et pareil pour mon sshd.
Voici les rapport de FRST:
https://pjjoint.malekal.com/files.php?id=FRST_20191220_e10k10d8l13z12
https://pjjoint.malekal.com/files.php?id=20191220_8y5j6f13s10
Je n'ai pas de rapport shortcut.
Voici les rapport de FRST:
https://pjjoint.malekal.com/files.php?id=FRST_20191220_e10k10d8l13z12
https://pjjoint.malekal.com/files.php?id=20191220_8y5j6f13s10
Je n'ai pas de rapport shortcut.
Faut donc trouver la barrette défectueuse et la remplacer.
Tu as des programmes qui ont été installés à l'achat de l'ordinateur ou installés par la suite et qui sont pas forcément utiles.
Ils encombrent Windows et peuvent le ralentir.
Tu peux donc les désinstaller.
Vas dans le Panneau de configuration
puis programmes et fonctionnalités.
Désinstalle :
Avast - laisse Windows Defender - plus léger.
CCleaner
MEGAsync
PS : CCleaner n'est pas vraiment utile, même si on le recommande de partout.
Si tu veux le garder, désactive la surveillance de CCleaner, inutile, ça se met au démarrage de Windows et le ralentit avec ces nettoyages incessants, voir : https://www.malekal.com/supprimer-ccleaner-demarrage-windows/
Tu as des programmes qui ont été installés à l'achat de l'ordinateur ou installés par la suite et qui sont pas forcément utiles.
Ils encombrent Windows et peuvent le ralentir.
Tu peux donc les désinstaller.
Vas dans le Panneau de configuration
puis programmes et fonctionnalités.
Désinstalle :
Avast - laisse Windows Defender - plus léger.
CCleaner
MEGAsync
PS : CCleaner n'est pas vraiment utile, même si on le recommande de partout.
Si tu veux le garder, désactive la surveillance de CCleaner, inutile, ça se met au démarrage de Windows et le ralentit avec ces nettoyages incessants, voir : https://www.malekal.com/supprimer-ccleaner-demarrage-windows/