BSOD KERNEL_MODE_HEAP_CORRUPTION sur Windows 10

[John News]

Bonsoir,

Depuis quelque jours que j'ai effectué la MAJ Windows 1809, je viens de constaté une erreur matérielle "LiveKernelEvent code 117", qui semble être lié a ma carte graphique qui est pourtant à jour.

LiveKernelEvent-Code-117.png

peripherique-Intel-HD.png

De ce fait, ma consommation de mémoire est un peut plus élevé que la normal.
Je voudrai savoir, est-ce qu'il y a une gravité au bon fonctionnement de mon PC?
D'autre part pourquoi je me retrouve avec une erreur matérielle?
Est-ce qu'il y a une solution pour y remédier et la quelle? Ou bien je n'ai aucun soucis a me faire.

[Malekal_morte]

Salut,

Ne tiens pas compte de cette erreur.
Elle est courante.

[John News]

Merci.

[John News]

Bonsoir,

Je reviens vers vous car je viens juste d'avoir un Plantage BSOD.

[Malekal_morte]

Les écrans bleus ou BSOD sont des plantages de Windows qui ne peut plus continuer à fonctionner.
Ces plantages ont plusieurs sources possibles :
- sources logiciels : plantage d'un pilote d'un périphérique comme ceux de la carte graphique, l'antivirus qui plante ou tout autre logiciel qui peut se charger "dans un bas niveau" sur Windows.
- sources matériels : problème matériels sur le disque dur, barrettes de mémoire défectueuses ou incomparabilités, etc

Il faut impérativement que tu regardes si ces plantages ont lieu à des moments particuliers, par exemple, si c'est lorsque tu lances une vidéo sur ton navigateur internet ou un jeu, il y a des chances que ce soit le pilote de la carte graphique. Il faudra alors réinstaller les pilotes de la carte graphique.
Débranche aussi tout autre périphérique que le clavier/souris (manette de jeu, webcam en USB, imprimante USB, etc), si tu as un de ces périphériques, indique le, ça peut être une source.

plus d'informations sur ces écrans bleus, sur la page suivante : Les écrans bleus de plantages (BSOD)

On peut aussi utiliser WhoCrashed pour obtenir des informations sur ces plantages.
=> Tutoriel WhoCrashed
Fais un copier/coller du contenu ici comme indiqué dans le tuto.

[John News]

Bonsoir,

Je vous transmets les résultats de WhoCrashed.

Code : Tout sélectionner

Crash dump file:        C:\Windows\MEMORY.DMP
Date/time:              20/01/2019 22:45:00
Uptime:                 20:44:31
Machine:                -PC
Bug check name:         KERNEL_MODE_HEAP_CORRUPTION
Bug check code:         0x13A
Bug check parm 1:       0x12
Bug check parm 2:       0xFFFFD40F3D002100
Bug check parm 3:       0xFFFFD40F43E43000
Bug check parm 4:       0x0
Probably caused by:     ntkrnlmp.exe
Driver description:     
Driver product:         
Driver company:         
OS build:               Built by: 17763.1.amd64fre.rs5_release.180914-1434
Architecture:           x64 (64 bit)
CPU count:              4
Page size:              4096

Bug check description: 
This indicates that the kernel mode heap manager has detected corruption in a heap.

Comments:
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. 


Crash dump file:        C:\Windows\Minidump\012019-31859-01.dmp
Date/time:              20/01/2019 22:45:00
Uptime:                 20:44:31
Machine:                JEANPIERRE-PC
Bug check name:         KERNEL_MODE_HEAP_CORRUPTION
Bug check code:         0x13A
Bug check parm 1:       0x12
Bug check parm 2:       0xFFFFD40F3D002100
Bug check parm 3:       0xFFFFD40F43E43000
Bug check parm 4:       0x0
Probably caused by:     ntkrnlmp.exe
Driver description:     
Driver product:         
Driver company:         
OS build:               Built by: 17763.1.amd64fre.rs5_release.180914-1434
Architecture:           x64 (64 bit)
CPU count:              4
Page size:              4096

Bug check description: 
This indicates that the kernel mode heap manager has detected corruption in a heap.

Comments:
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. 


nt!KeBugCheckEx+0x0
nt!RtlpHeapHandleError+0x29
nt!RtlpHpHeapHandleError+0x58
nt!RtlpLogHeapFailure+0x45
nt!ExFreePoolWithTag+0x980
nt!IopCompleteRequest+0xA73
nt!KiDeliverApc+0x19D
nt!KiApcInterrupt+0x2D5
nt!IopCancelIrpsInCurrentThreadList+0xB6
nt!IopCancelIrpsInThreadList+0x37
nt!IopCancelIrpsInThreadListForCurrentProcess+0xC3
nt!NtCancelIoFileEx+0xC2
nt!KiSystemServiceCopyEnd+0x25
0x7FFD6DE60854

[John News]

Code : Tout sélectionner

Computer name: 
Windows version: Windows 10 , 10.0, build: 17763
Windows dir: C:\WINDOWS
Hardware: SATELLITE C670-1DT, TOSHIBA, TKBSC
CPU: GenuineIntel Intel(R) Core(TM) i3 CPU M 380 @ 2.53GHz Intel586, level: 6
4 logical processors, active mask: 15
RAM: 8377122816 bytes total




--------------------------------------------------------------------------------
Crash Dump Analysis
--------------------------------------------------------------------------------

Crash dumps are enabled on your computer. This system is not configured for complete or automatic crash dumps. For best results, configure your system to write out complete or automatic crash dumps. Select Tools->Crash Dump Configuration from the main menu to configure your system to write out complete memory dumps. 

Crash dump directories: 
C:\Windows
C:\Windows\Minidump



On Mon 21/01/2019 07:25:28 your computer crashed or a problem was reported
crash dump file: C:\Windows\Minidump\012119-35328-01.dmp
uptime: 07:16:25
This was probably caused by the following module: rspcrash64.sys (rspCrash64+0x108B) 
Bugcheck code: 0xDEADDEAD (0x1, 0x2, 0x19EB7BF5, 0x3C2A58ED)
Error: MANUALLY_INITIATED_CRASH1
file path: C:\WINDOWS\system32\drivers\rspcrash64.sys
product: WhoCrashed
company: Resplendence Software Projects Sp.
description: Resplendence WhoCrashed Crash Dump Test
Bug check description: This indicates that the user deliberately initiated a crash dump from either the kernel debugger or the keyboard. 
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. 



On Mon 21/01/2019 07:25:28 your computer crashed or a problem was reported
crash dump file: C:\Windows\MEMORY.DMP
uptime: 07:16:25
This was probably caused by the following module: rspcrash64.sys (rspCrash64+0x108B) 
Bugcheck code: 0xDEADDEAD (0x1, 0x2, 0x19EB7BF5, 0x3C2A58ED)
Error: MANUALLY_INITIATED_CRASH1
file path: C:\WINDOWS\system32\drivers\rspcrash64.sys
product: WhoCrashed
company: Resplendence Software Projects Sp.
description: Resplendence WhoCrashed Crash Dump Test
Bug check description: This indicates that the user deliberately initiated a crash dump from either the kernel debugger or the keyboard. 
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. 



On Sun 20/01/2019 22:45:00 your computer crashed or a problem was reported
crash dump file: C:\Windows\Minidump\012019-31859-01.dmp
uptime: 20:44:31
This was probably caused by the following module: ntkrnlmp.exe (nt!RtlpHeapHandleError+0x29) 
Bugcheck code: 0x13A (0x12, 0xFFFFD40F3D002100, 0xFFFFD40F43E43000, 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. 
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time. 





--------------------------------------------------------------------------------
Conclusion
--------------------------------------------------------------------------------

3 crash dumps have been found and analyzed. No offending third party drivers have been found. 


Read the topic general suggestions for troubleshooting system crashes for more information. 

Note that it's not always possible to state with certainty whether a reported driver is responsible for crashing your system or that the root cause is in another module. Nonetheless it's suggested you look for updates for the products that these drivers belong to and regularly visit Windows update or enable automatic updates for Windows. In case a piece of malfunctioning hardware is causing trouble, a search with Google on the bug check errors together with the model name and brand of your computer may help you investigate this further.

[Malekal_morte]

C'est le pilote esplendence Software Projects Sp qui plante.
Désinstalle l'application.

[electro]

J'ai lu des conseils de spécialistes qui informaient qu'il valait mieux, pour le public, attendre que les développeurs professionnels de Microsoft aient sorti une version stable de Windows10, il semble bien que les annonces régulières de màj disponibles soient en fait des tests (sans que cela soit précisé).
Moi, j'ai trouvé une seule solution pour être ''tranquille'' avec Windows10, c'est de ne faire que les Updates de support de la marque de mon Pc et ça fonctionne, je laisse juste en plus faire les ups pour Windows Defender. Ce n'est peut-être pas la meilleure solution technique pour des ''puristes'' mais, comme d'autres utilisateurs, ça a vraiment ''calmé'' le système en mieux. Bon courage.

[John News]

Bonjour,

Je reviens vers vous car je me retrouve une seconde fois blue screen, cela après avoir désinstaller "resplendence".

Kernel-mode-heap-corruption.jpg

Que j'ai du réinstaller pour pouvoir identifier la cause de l'écran bleu, dans le rapport suivant.

Code : Tout sélectionner

On Wed 23/01/2019 09:17:47 your computer crashed or a problem was reported
crash dump file: C:\WINDOWS\Minidump\012319-36468-01.dmp
uptime: 1 day, 15:06:01
This was probably caused by the following module: fltmgr.sys (FLTMGR!FltpDispatch+0xE3) 
Bugcheck code: 0x13A (0x12, 0xFFFF880F75E02100, 0xFFFF880F7CC6B000, 0x0)
Error: KERNEL_MODE_HEAP_CORRUPTION
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 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. 
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 23/01/2019 09:17:47 your computer crashed or a problem was reported
crash dump file: C:\WINDOWS\MEMORY.DMP
uptime: 1 day, 15:06:01
This was probably caused by the following module: fltmgr.sys (FLTMGR!FltpDispatch+0xE3) 
Bugcheck code: 0x13A (0x12, 0xFFFF880F75E02100, 0xFFFF880F7CC6B000, 0x0)
Error: KERNEL_MODE_HEAP_CORRUPTION
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 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. 
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.

--------------------------------------------------------------------------------
Conclusion
--------------------------------------------------------------------------------

2 crash dumps have been found and analyzed. No offending third party drivers have been found. 


Read the topic general suggestions for troubleshooting system crashes for more information. 

Note that it's not always possible to state with certainty whether a reported driver is responsible for crashing your system or that the root cause is in another module. Nonetheless it's suggested you look for updates for the products that these drivers belong to and regularly visit Windows update or enable automatic updates for Windows. In case a piece of malfunctioning hardware is causing trouble, a search with Google on the bug check errors together with the model name and brand of your computer may help you investigate this further. 

Merci pour votre aide.

[Malekal_morte]

ok toujours ce KERNEL_MODE_HEAP_CORRUPTION.
Cette fois-ci BSOD et plantage sur fltmgr.sys.

Suis ces trois étapes.

1)
Vérifie l'état de santé des disques dur notamment avec Par exemple avec CrystalDiskInfo, voir si le statut est correct ou Prudence.

2)
Faire un checkdisk, si possible en ligne de commandes.
Ouvre une invite de commandes en administrateur
Lance l'invite de commandes en administrateur puis saisir la commande :
chkdsk c: /F /R
ça doit te proposer de faire une vérification au redémarrage, accepte, le scan peut durer 1h30.
[*] Fais un nettoyage System File Check (SFC) et DISM
[/list]

3)
Pour voir un peu ce qui tourne :

Suis le tutoriel FRST. ( 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).

[John News]

Bonjour et merci,

1)
Vérification de l'état de santé des disques dur avec CrystalDiskInfo et Speccy.


2)
chkdsk c: /F /R
System File Check (SFC) et DISM


3)
FRST.txt https://pjjoint.malekal.com/files.php?i ... 11u14m14m8
* Shortcut.https://pjjoint.malekal.com/files.php?i ... 7i13e15i11
* Additionnal.txthttps://pjjoint.malekal.com/files.php?i ... 13z5d14z14

[Malekal_morte]

Pour le 1), c'est CrystalDiskInfo et pas CrystalDiskMark
Mais bon sur Speccy, le disque a l'air d''être en correct.

Tu as bien fait un chkdsk ?

Désinstalle tout ça :

CleanMem
MEGAsync
Unchecky
WildTangent Games

Voi si des mises à jour Intel sont disponible : https://www.malekal.com/mettre-a-jour-pilotes-intel/

Vois si ça change quelque chose.

[John News]

Bonsoir et merci,

Je vous répond tardivement car je voulais être sure que mon problème soit résolu, malheureuse se n'est pas le cas, je me retrouve pour la troisième fois avec un blue screen.




Information complémentaire.



Rapport WhoCrashed.

Code : Tout sélectionner

On Fri 25/01/2019 22:02:09 your computer crashed or a problem was reported
crash dump file: C:\WINDOWS\Minidump\012519-38453-01.dmp
uptime: 1 day, 16:30:17
This was probably caused by the following module: ntkrnlmp.exe (nt!RtlpHeapHandleError+0x29) 
Bugcheck code: 0x13A (0x12, 0xFFFFB48E70602100, 0xFFFFB48E77274000, 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. 
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/01/2019 22:02:09 your computer crashed or a problem was reported
crash dump file: C:\WINDOWS\MEMORY.DMP
uptime: 1 day, 16:30:17
This was probably caused by the following module: ntkrnlmp.exe (nt!RtlpHeapHandleError+0x29) 
Bugcheck code: 0x13A (0x12, 0xFFFFB48E70602100, 0xFFFFB48E77274000, 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. 
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time. 





--------------------------------------------------------------------------------
Conclusion
--------------------------------------------------------------------------------

2 crash dumps have been found and analyzed. No offending third party drivers have been found. 


Read the topic general suggestions for troubleshooting system crashes for more information. 

Note that it's not always possible to state with certainty whether a reported driver is responsible for crashing your system or that the root cause is in another module. Nonetheless it's suggested you look for updates for the products that these drivers belong to and regularly visit Windows update or enable automatic updates for Windows. In case a piece of malfunctioning hardware is causing trouble, a search with Google on the bug check errors together with the model name and brand of your computer may help you investigate this further. 

Ma machine est bien à jour.

Merci pour votre aide.

[Malekal_morte]

Donc que donne CrystalDiskInfo sur l'état des disques ?