Kernel data inpage error et écran bleu

[emmanuel57]

Bonjour,

depuis aujourd'hui, mon Pc s'arrête brutalement, puis un écran bleu apparait avec le message suivant : Kernel data inpage error
Puis mon pc redémarre en faisant une réparation.
Mon PC fonctionne sous windows 8.1.

Merci d'avance de votre aide.

Cordialement

Manu

[EinsteinZero]

Bonsoir
comme ce genre de souci est rarement lié à un malware, j'ai déplacé le sujet dans "win 8,7, vista, xp"

ton souci fait penser à un pb hardware ou pilote
pourrais tu utiliser "whocrashed" >>ici<< afin d'accéder aux rapports de plantage (si le PC a eu le temps d'en créer un)
ce rapport est en anglais...mais on a l'habitude
fait un copier coller du rapport (s'il y en a un valide) on aura peut-être une piste

[emmanuel57]

Merci pour votre réponse. Voici le rapport

Crash dumps are enabled on your computer.

Crash dump directories:
C:\WINDOWS
C:\WINDOWS\Minidump

On Mon 12/02/2018 21:39:25 your computer crashed or a problem was reported
crash dump file: C:\WINDOWS\Minidump\021218-43203-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x154EA0)
Bugcheck code: 0x3B (0xC0000005, 0xFFFFF80397E981EF, 0xFFFFD00109A6EBE0, 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 Mon 12/02/2018 21:39:25 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!setjmpex+0x8299)
Bugcheck code: 0x3B (0xC0000005, 0xFFFFF80397E981EF, 0xFFFFD00109A6EBE0, 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 Mon 12/02/2018 21:15:51 your computer crashed or a problem was reported
crash dump file: C:\WINDOWS\Minidump\021218-41515-01.dmp
This was probably caused by the following module: tmcomm.sys (tmcomm+0x20BD)
Bugcheck code: 0x1A (0x3470, 0xFFFFD0018DDDC000, 0x91574000A2AD4, 0xFB8A6B51673F80A)
Error: MEMORY_MANAGEMENT
file path: C:\WINDOWS\system32\drivers\tmcomm.sys
product: Trend Micro Eyes
company: Trend Micro Inc.
description: TrendMicro Common Module
Bug check description: This indicates that a severe memory management error occurred.
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).
A third party driver was identified as the probable root cause of this system error. It is suggested you look for an update for the following driver: tmcomm.sys (TrendMicro Common Module, Trend Micro Inc.).
Google query: tmcomm.sys Trend Micro Inc. MEMORY_MANAGEMENT



On Mon 12/02/2018 20:27:45 your computer crashed or a problem was reported
crash dump file: C:\WINDOWS\Minidump\021218-30171-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x154EA0)
Bugcheck code: 0x1E (0xFFFFFFFFC0000005, 0xFFFFF801AA16DBE0, 0x0, 0xFFFFFFFFFFFFFFFF)
Error: KMODE_EXCEPTION_NOT_HANDLED
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 kernel-mode program generated an exception which the error handler did not catch.
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.
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 12/02/2018 20:13:51 your computer crashed or a problem was reported
crash dump file: C:\WINDOWS\Minidump\021218-27390-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x154EA0)
Bugcheck code: 0x1A (0x5200, 0xFFFFE00005CFE000, 0x6E756F636361227B, 0xC903B54E83B15031)
Error: MEMORY_MANAGEMENT
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 severe memory management error occurred.
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 Mon 12/02/2018 19:45:42 your computer crashed or a problem was reported
crash dump file: C:\WINDOWS\Minidump\021218-33343-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x154EA0)
Bugcheck code: 0x7A (0x4, 0x0, 0xFFFFE000F0291E80, 0xFFFFC000814B74B8)
Error: KERNEL_DATA_INPAGE_ERROR
file path: C:\WINDOWS\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This bug check indicates that the requested page of kernel data from the paging file could not be read into memory.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.





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

6 crash dumps have been found and analyzed. A third party driver has been identified to be causing system crashes on your computer. It is strongly suggested that you check for updates for these drivers on their company websites. Click on the links below to search with Google for updates for these drivers:

tmcomm.sys (TrendMicro Common Module, Trend Micro Inc.)

If no updates for these drivers are available, try searching with Google on the names of these drivers in combination with the errors that have been reported for these drivers. Include the brand and model name of your computer as well in the query. This often yields interesting results from discussions on the web by users who have been experiencing similar problems.


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 an

[EinsteinZero]

Bonsoir
l'analyse renvoie à plusieurs pistes
1> un problème de pilote instable
2> un souci lié à l'antivirus trendmicro (il ne pose pas de souci chez moi sous win 10...mais j'ai une version 64 bits)
3> vu les différentes causes...un problème sur un composant mémoire est aussi possible.

je n'ai hélas pas le temps ce soir de détailler..du travail à finir

[emmanuel57]

Pas de souci

Quand vous aurez un peu de temps.
Merci de prendre en compte mon souci

Cordialement

Manu

[EinsteinZero]

Bonsoir
pour vérifier les pilotes tu peux, par exemple utiliser l'outil de "touslesdrivers.com" >>ici<< ou celui de driverscloud >>ici<<

pour tester la mémoire on préconise généralement l'usage de memtest mais si tu es sous win10 il existe un outils intégré
il suffit de taper dans la barre de recherche diagnostic de mémoire pour y accéder >>explication ici<<

si le souci vient de ton antivirus, comme il s'agit d'une version payante, peut être que trend micro peut te fournir un support d'aide >>voir ici (hélas pas mieux)<<

[emmanuel57]

Bonsoir,

merci beaucoup. Je vais m'y atteler.

Je vous tiens au courant.

Cordialement

Manu

[emmanuel57]

Bonjour,
bon ben tout est revenu en faisant un test mémoire mais sans que je ne fasse quoique ce soit de spécial

En tout cas merci

Manue

[routman54]

Bonjour ,
Quand il y a plusieurs causes possibles dans Whocrashed , c'est souvent un problème de mémoires ram. Et là on ne sait pas ce qui se passe, j'ai vu une panne il y a une dizaine d'années ou la personne à passer un coup de gomme sur les " dents" de la barrette et c'est reparti , on a jamais compris. les mystères de l'informatique .
Content pour toi que ce soit résolu .
Bonne continuation .

[EinsteinZero]

Bonsoir
ceci dit, le pb peut revenir..où jamais..., si une impureté se balade dans un composant mémoire... le test global peut l'avoir mis "sur un parking".. si elle y reste tant mieux (et c'est possible) mais si elle re-bouge vers une jonction le souci reviendra.

bref, si le pb recommence avec divers causes de plantage.... refait la même manip pour qu'elle "reparque l'impureté" et si ça ne marche pas... peut être faudra-t-il changer une élément mémoire.