ZONE ANTIMALWARE

Le forum de Nicolas Coolman a pour objectif de détecter et d'informer sur les nouvelles menaces malwares présentes sur le web. 

Cette section concerne le système d'exploitation Windows. Quand votre système met beaucoup de temps à démarrer. Lorsque vous avez un message d'erreur Windows qui s'affiche sur votre ordinateur. Si vous constatez des dysfonctionnements dans l'affichage des fenêtres. Si votre disque dur se bloque souvent à 100% d'utilisation. Quand Windows vous signale une absence ou une erreur de pilote. Lorsque votre mémoire est saturée à 100% d'occupation. Ce sont autant de cas sur lesquels vous pouvez trouver une solution.
 #78528  par aristotelous
 
Bonjour,
mon PC "plante" régulièrement depuis peu et affiche l' écran bleu 'kernel data...".
Je suis déjà passée par le forum "analyse de rapports et désinfection" grâce auquel du ménage a été fait, mais qui n'a pas résolu le problème.
J'ai exécuté SFC, le scan va jusque 47% puis s'arrête.
J'ai essayé de réparer avec DISM mais cela ne fonctionne pas, voici le rapport:
https://www.cjoint.com/c/HDAozsYp4AK

Merci de l'aide que vous voudrez bien m'apporter!
 #78529  par Enfermedehors
 
Bonjour,
J'ai vu cette erreur dans le log Addition de FRST :
Description: Le périphérique \Device\Harddisk0\DR0 comporte un bloc défectueux.
Il faut commencer par contrôler le disque dur. Télécharge CrystalDiskInfo.
https://www.pcastuces.com/logitheque/cr ... skinfo.htm
Prend la version portable.
Lance CrystalDiskInfo d'un clic droit - Exécuter en tant qu'administrateur.

Fais une capture d'écran et joins-la à ton prochain message ou héberge-la sur cjoint.com
 #78532  par Enfermedehors
 
Le disque dur est en bon état.
Fais un chkdsk.
Dans l'explorateur, fais un clic droit sur la partition (c:), clique sur Propriétés.
Onglet Outils, clique sur Vérifier.
 #78537  par aristotelous
 
Windows affichait qu'il était inutile de vérifier le lecteur. Je l'ai fait quand même bien sûr: il vient de détecter des erreurs et va tenter de les réparer...je le laisse faire et je reviens.
 #78540  par aristotelous
 
Le pc a redémarré mais j'ai eu un écran bleu d'erreur stipulant qu'il n'avait pas redémarré normalement, j'ai continué, redémarrage correct ensuite. J'ai vérifié à nouveau le disque dur, plus d'erreur détectée.
 #78550  par aristotelous
 
C'est fait: ccleaner a dû effacer plein d'anciens rapports de crash, il y en a quand même deux


--------------------------------------------------------------------------------
Welcome to WhoCrashed (HOME EDITION) v 6.01
--------------------------------------------------------------------------------

This program checks for drivers which have been crashing your computer. If your computer has displayed a blue (or black) screen of death, suddenly rebooted or shut down then this program might help you find the root cause of the problem and a solution.

Whenever a computer suddenly reboots without displaying any notice or blue (or black) screen of death, the first thing that is often thought about is a hardware failure. In reality, on Windows a lot of system crashes are caused by malfunctioning device drivers and kernel modules. In case of a kernel error, many computers do not show a blue or black screen unless they are configured for this. Instead these systems suddenly reboot without any notice.

This program will analyze your crash dumps with the single click of a button. It will tell you what drivers are likely to be responsible for crashing your computer. It will report a conclusion which offers suggestions on how to proceed in any situation while the analysis report will display internet links which will help you further troubleshoot any detected problems.

To obtain technical support visit www.resplendence.com/support

Click here to check if you have the latest version or if an update is available.

Just click the Analyze button for a comprehensible report ...



--------------------------------------------------------------------------------
Home Edition Notice
--------------------------------------------------------------------------------

This version of WhoCrashed is free for use at home only. If you would like to use this software at work or in a commercial environment you should get the professional edition of WhoCrashed which allows you to perform more thorough and detailed analysis. It also offers a range of additional features such as remote analysis on remote directories and remote computers on the network.

Please note that this version of WhoCrashed is not licensed for use by professional support engineers.

Click here for more information on the professional edition.
Click here to buy the the professional edition of WhoCrashed.


--------------------------------------------------------------------------------
System Information (local)
--------------------------------------------------------------------------------

Computer name: SALON
Windows version: Windows 8.1 , 6.3, build: 9600
Windows dir: C:\Windows
Hardware: Aspire E5-471, Acer, EA40_HB
CPU: GenuineIntel Intel(R) Core(TM) i3-4030U CPU @ 1.90GHz Intel586, level: 6
4 logical processors, active mask: 15
RAM: 4218793984 bytes total




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

Crash dumps are enabled on your computer.

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

On Wed 25/04/2018 14:19:35 your computer crashed or a problem was reported
crash dump file: C:\Windows\Minidump\042518-18578-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x1552A0)
Bugcheck code: 0x7A (0xFFFFF6E0002265E0, 0xFFFFFFFFC00000C0, 0x149F13880, 0xFFFFC00044CBC000)
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.



On Wed 25/04/2018 14:19:35 your computer crashed or a problem was reported
crash dump file: C:\Windows\MEMORY.DMP
This was probably caused by the following module: avgsnx.sys (avgSnx+0x2CE34)
Bugcheck code: 0x7A (0xFFFFF6E0002265E0, 0xFFFFFFFFC00000C0, 0x149F13880, 0xFFFFC00044CBC000)
Error: KERNEL_DATA_INPAGE_ERROR
file path: C:\Windows\system32\drivers\avgsnx.sys
product: AVG Internet Security System
company: AVG Technologies CZ, s.r.o.
description: AVG Virtualization Driver
Bug check description: This bug check indicates that the requested page of kernel data from the paging file could not be read into memory.
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: avgsnx.sys (AVG Virtualization Driver, AVG Technologies CZ, s.r.o.).
Google query: avgsnx.sys AVG Technologies CZ, s.r.o. KERNEL_DATA_INPAGE_ERROR





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

2 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:

avgsnx.sys (AVG Virtualization Driver, AVG Technologies CZ, s.r.o.)

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 and brand of your computer may help you investigate this further.
Sujets similaires Statistiques Dernier message
BSOD ntoskrnl.exe incessant depuis plusieurs mois.
par thomas-l30  dans : Support Windows
48 Réponses
15648 Vues
par ab_web