Aller au contenu
  • Pas encore inscrit ?

    Pourquoi ne pas vous inscrire ? C'est simple, rapide et gratuit.
    Pour en savoir plus, lisez Les avantages de l'inscription... et la Charte de Zébulon.
    De plus, les messages que vous postez en tant qu'invité restent invisibles tant qu'un modérateur ne les a pas validés. Inscrivez-vous, ce sera un gain de temps pour tout le monde, vous, les helpeurs et les modérateurs ! :wink:

Écran bleu fréquent


karlomat
 Share

Messages recommandés

Bonjour,

 

J'ai un vieux pc de 8 ans qui fonctionne sous XP.

Le problème est qu'il plante fréquemment (écran bleu avec stop : 0x0000008E / début de vidage de la mémoire physique) et cela depuis de nombreux mois.

J'ai fait un MEMTEST car j'ai autrefois rajouté de la RAM : RAS

J'ai mis à jour le pilote de la carte garphique.

 

Je suis un peu désemparé car mes connaissances en informatique sont minimes.

Je me suis donc décidé (enfin !) à prendre le taureau par les cornes et à consulter un site de spécialistes comme le votre.

 

J'ai fait un rapport blue screen view. Je ne sais pas si cela peut être utile ?

 

Merci pour votre aide.

Bien cordialement,

Lien vers le commentaire
Partager sur d’autres sites

Invité Notpa

Bonjour karlomat,

 

Télécharge WhoCrached, installe-le et exécute-le. Copie le résultat d’analyse dans ta réponse.

 

A+

 

Notpa

Lien vers le commentaire
Partager sur d’autres sites

Bonjour,

 

Je viens d'exécuter WhoCrashed dont je fais suivre le rapport plus bas.

 

Merci d'avance.

karlomat

 

 

 

 

System Information (local)

--------------------------------------------------------------------------------

 

computer name: UNKNOW-9A33YR3L

windows version: Windows XP Service Pack 3, 5.1, build: 2600

windows dir: C:\WINDOWS

CPU: AuthenticAMD AMD Athlon XP 2500+ AMD586, level: 6

1 logical processors, active mask: 1

RAM: 1610072064 total

VM: 2147352576, free: 2065313792

 

 

 

 

--------------------------------------------------------------------------------

Crash Dump Analysis

--------------------------------------------------------------------------------

 

Crash dump directory: C:\WINDOWS\Minidump

 

Crash dumps are enabled on your computer.

 

On Sun 25/11/2012 09:11:55 GMT your computer crashed

crash dump file: C:\WINDOWS\Minidump\Mini112512-01.dmp

This was probably caused by the following module: ntoskrnl.exe (nt+0x20E65)

Bugcheck code: 0x1000008E (0xFFFFFFFFC0000005, 0xFFFFFFFF804F7E65, 0xFFFFFFFFB58CDCE0, 0x0)

Error: KERNEL_MODE_EXCEPTION_NOT_HANDLED_M

file path: C:\WINDOWS\system32\ntoskrnl.exe

product: Système d'exploitation Microsoft® Windows®

company: Microsoft Corporation

description: Noyau et système NT

Bug check description: This indicates that a kernel-mode program 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 the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.

 

 

 

On Sat 24/11/2012 08:33:13 GMT your computer crashed

crash dump file: C:\WINDOWS\Minidump\Mini112412-01.dmp

This was probably caused by the following module: ntoskrnl.exe (nt+0x8DDDA)

Bugcheck code: 0x1000008E (0xFFFFFFFFC000001D, 0xFFFFFFFF80564DDA, 0xFFFFFFFFAC224C10, 0x0)

Error: KERNEL_MODE_EXCEPTION_NOT_HANDLED_M

file path: C:\WINDOWS\system32\ntoskrnl.exe

product: Système d'exploitation Microsoft® Windows®

company: Microsoft Corporation

description: Noyau et système NT

Bug check description: This indicates that a kernel-mode program 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 the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.

 

 

 

On Sat 10/11/2012 15:22:26 GMT your computer crashed

crash dump file: C:\WINDOWS\Minidump\Mini111012-02.dmp

This was probably caused by the following module: ntoskrnl.exe (nt+0x20E65)

Bugcheck code: 0x1000008E (0xFFFFFFFFC0000005, 0xFFFFFFFF804F7E65, 0xFFFFFFFFA8642CE0, 0x0)

Error: KERNEL_MODE_EXCEPTION_NOT_HANDLED_M

file path: C:\WINDOWS\system32\ntoskrnl.exe

product: Système d'exploitation Microsoft® Windows®

company: Microsoft Corporation

description: Noyau et système NT

Bug check description: This indicates that a kernel-mode program 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 the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.

 

 

Edit de Notpa :

 

A fin de faciliter la lecture, j'ai supprimé 12 analyses. Elles sont toutes identiques à celles ci-dessus.

 

 

--------------------------------------------------------------------------------

Conclusion

--------------------------------------------------------------------------------

 

143 crash dumps have been found and analyzed. Only 15 are included in this report. 4 third party drivers have 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:

 

ati2dvag.dll (ATI Radeon WindowsNT Display Driver, ATI Technologies Inc.)

klif.sys (Klif Mini-Filter [fre_wnet_x86], Kaspersky Lab)

klim5.sys (Kaspersky Lab Intermediate Network Driver, Kaspersky Lab ZAO)

kl1.sys (Kaspersky Unified Driver, Kaspersky Lab ZAO)

 

If no updates for these drivers are available, try searching with Google on the names of these drivers in combination the errors that have been reported for these drivers and include the brand and model name of your computer as well in the query. This often yields interesting results from discussions from 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 actually 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.

Lien vers le commentaire
Partager sur d’autres sites

Invité Notpa

Merci du rapport karlomat. Je l'ai allégé un peu car les 15 analyse concernent le même problème.

 

Microsoft parle de ce problème : Bug Check 0x1000008E: KERNEL_MODE_EXCEPTION_NOT_HANDLED_M (Windows Debuggers) mais n'est pas très explicite ! :

 

"If you received a blue screen error, or stop code, the computer has shut down abruptly to protect itself from data loss. A hardware device, its driver, or related software might have caused this error"

ou en français :

"Si vous avez reçu un écran bleu d'erreur ou code d'arrêt, l'ordinateur s'est arrêté brusquement pour se protéger contre la perte de données. Un périphérique matériel, son pilote, ou un logiciel associé pourrait avoir causé cette erreur"

 

Bref, l'erreur peut venir aussi bien d'un périphérique que d'un driver. WhoCrashed suggère à la fin de vérifier les drivers suivants :

 

ati2dvag.dll (ATI Radeon WindowsNT Display Driver, ATI Technologies Inc.)

klif.sys (Klif Mini-Filter [fre_wnet_x86], Kaspersky Lab)

klim5.sys (Kaspersky Lab Intermediate Network Driver, Kaspersky Lab ZAO)

kl1.sys (Kaspersky Unified Driver, Kaspersky Lab ZAO)

 

Pour Kaspersky, je ne connais pas trop et ne saurais te conseiller là-dessus. Pour Ati : driver vidéo.

 

Dernier point :

Dans le dossier

C:\WINDOWS\Minidump, tu as 143 dumps mémoire ! Tu peux en virer 140, tu gagneras de la place !

 

A+

 

Notpa

 

Lien vers le commentaire
Partager sur d’autres sites

ok, j'ai mis à jour le driver ATI de ma carte Radeon 9550.

j'ai viré les dumps en mémoire pour faire de la place...

 

Quant à Kaspersky (j'ai KAV 2013), je ne sais que faire ?

 

 

J'ai refait un WhoCrashed en ne conservant que les 3 derniers dumps, voici le résultat :

j'ai toujours le même message "kernel mode ..."

 

Merci pour vos avis et conseils.

karlomat

 

 

 

 

--------------------------------------------------------------------------------

Welcome to WhoCrashed (HOME EDITION) v 4.01

--------------------------------------------------------------------------------

 

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

 

Whenever a computer suddenly reboots without displaying any notice or blue screen of death, the first thing that is often thought about is a hardware failure. In reality, on Windows most crashes are caused by malfunctioning device drivers and kernel modules. In case of a kernel error, many computers do not show a blue 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 also allows analysis of crashdumps on remote drives and computers on the network and offers a range of additional features.

 

Click here for more information on the professional edition.

Click here to buy the the professional edition of WhoCrashed.

 

 

--------------------------------------------------------------------------------

System Information (local)

--------------------------------------------------------------------------------

 

computer name: UNKNOW-9A33YR3L

windows version: Windows XP Service Pack 3, 5.1, build: 2600

windows dir: C:\WINDOWS

CPU: AuthenticAMD AMD Athlon XP 2500+ AMD586, level: 6

1 logical processors, active mask: 1

RAM: 1610072064 total

VM: 2147352576, free: 2065838080

 

 

 

 

--------------------------------------------------------------------------------

Crash Dump Analysis

--------------------------------------------------------------------------------

 

Crash dump directory: C:\WINDOWS\Minidump

 

Crash dumps are enabled on your computer.

 

On Sun 25/11/2012 16:34:29 GMT your computer crashed

crash dump file: C:\WINDOWS\Minidump\Mini112512-02.dmp

This was probably caused by the following module: ntoskrnl.exe (nt+0x8DDDA)

Bugcheck code: 0x1000008E (0xFFFFFFFFC000001D, 0xFFFFFFFF80564DDA, 0xFFFFFFFFF7555C78, 0x0)

Error: KERNEL_MODE_EXCEPTION_NOT_HANDLED_M

file path: C:\WINDOWS\system32\ntoskrnl.exe

product: Système d'exploitation Microsoft® Windows®

company: Microsoft Corporation

description: Noyau et système NT

Bug check description: This indicates that a kernel-mode program 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 the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.

 

 

 

On Sun 25/11/2012 09:11:55 GMT your computer crashed

crash dump file: C:\WINDOWS\Minidump\Mini112512-01.dmp

This was probably caused by the following module: ntoskrnl.exe (nt+0x20E65)

Bugcheck code: 0x1000008E (0xFFFFFFFFC0000005, 0xFFFFFFFF804F7E65, 0xFFFFFFFFB58CDCE0, 0x0)

Error: KERNEL_MODE_EXCEPTION_NOT_HANDLED_M

file path: C:\WINDOWS\system32\ntoskrnl.exe

product: Système d'exploitation Microsoft® Windows®

company: Microsoft Corporation

description: Noyau et système NT

Bug check description: This indicates that a kernel-mode program 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 the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.

 

 

 

On Sat 24/11/2012 08:33:13 GMT your computer crashed

crash dump file: C:\WINDOWS\Minidump\Mini112412-01.dmp

This was probably caused by the following module: ntoskrnl.exe (nt+0x8DDDA)

Bugcheck code: 0x1000008E (0xFFFFFFFFC000001D, 0xFFFFFFFF80564DDA, 0xFFFFFFFFAC224C10, 0x0)

Error: KERNEL_MODE_EXCEPTION_NOT_HANDLED_M

file path: C:\WINDOWS\system32\ntoskrnl.exe

product: Système d'exploitation Microsoft® Windows®

company: Microsoft Corporation

description: Noyau et système NT

Bug check description: This indicates that a kernel-mode program 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 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. Consider configuring your system to produce a full memory dump for better analysis.

 

 

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 actually 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.

Lien vers le commentaire
Partager sur d’autres sites

Bonjour karlomat, salut ma puce ;)

 

Envisagez de configurer votre système afin de produire une image mémoire complète pour une meilleure analyse.

Propriétés système (touches WIN+Pause) > onglet avancé > Démarrage et récupération (en bas) cliquer sur Paramètres > décocher "Redémarrer automatiquement" > sélectionner "Image mémoire du noyau.

Lien vers le commentaire
Partager sur d’autres sites

Bonjour,

 

je viens de modifier les propriétés système comme recommandé dans le message plus haut.

Que dois-je faire maintenant ?

 

Cdt,

Lien vers le commentaire
Partager sur d’autres sites

Bonjour karlomat (salut Notpa, leminou, ;) ),

 

Après avoir mis en pratique le conseil de leminou, tu peux poster les derniers logs de WhoCrashed.

 

Bon dimanche,

Tonton

Lien vers le commentaire
Partager sur d’autres sites

Bonjour,

 

Mon PC fait tjrs des siennes et les BSoD se succèdent.

Apparemment, il y a 2 types de causes :

 

- l'AV kaspersky (j'ai KAV 2013 et je le trouve bien lourd pour mon vieux PC)

- le rapport WhoCrashed indique un autre type de pb avec le module ntoskrnl.exe. Qu'est-ce que cela signifie ?

 

J'ai posté le rapport WhoCrashed.

Merci de votre aide.

 

karlomat

 

 

 

System Information (local)

--------------------------------------------------------------------------------

 

computer name: UNKNOW-9A33YR3L

windows version: Windows XP Service Pack 3, 5.1, build: 2600

windows dir: C:\WINDOWS

CPU: AuthenticAMD AMD Athlon XP 2500+ AMD586, level: 6

1 logical processors, active mask: 1

RAM: 1610072064 total

VM: 2147352576, free: 2065833984

 

 

 

 

--------------------------------------------------------------------------------

Crash Dump Analysis

--------------------------------------------------------------------------------

 

Crash dump directory: C:\WINDOWS\Minidump

 

Crash dumps are enabled on your computer.

 

On Sat 08/12/2012 18:18:55 GMT your computer crashed

crash dump file: C:\WINDOWS\Minidump\Mini120912-01.dmp

This was probably caused by the following module: klif.sys (klif+0x79AE4)

Bugcheck code: 0x1000008E (0xFFFFFFFFC000001D, 0xFFFFFFFF80564DDA, 0xFFFFFFFF9D62DC90, 0x0)

Error: KERNEL_MODE_EXCEPTION_NOT_HANDLED_M

file path: C:\WINDOWS\system32\drivers\klif.sys

product: Kaspersky Anti-Virus ®

company: Kaspersky Lab

description: Klif Mini-Filter [fre_wnet_x86]

Bug check description: This indicates that a kernel-mode program 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.

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: klif.sys (Klif Mini-Filter [fre_wnet_x86], Kaspersky Lab).

Google query: Kaspersky Lab KERNEL_MODE_EXCEPTION_NOT_HANDLED_M

 

 

 

On Sat 08/12/2012 18:18:55 GMT your computer crashed

crash dump file: C:\WINDOWS\memory.dmp

This was probably caused by the following module: klif.sys (klif+0x79AE4)

Bugcheck code: 0x8E (0xFFFFFFFFC000001D, 0xFFFFFFFF80564DDA, 0xFFFFFFFF9D62DC90, 0x0)

Error: KERNEL_MODE_EXCEPTION_NOT_HANDLED

file path: C:\WINDOWS\system32\drivers\klif.sys

product: Kaspersky Anti-Virus ®

company: Kaspersky Lab

description: Klif Mini-Filter [fre_wnet_x86]

Bug check description: This bug check indicates that a kernel-mode application generated an exception that the error handler did not catch.

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: klif.sys (Klif Mini-Filter [fre_wnet_x86], Kaspersky Lab).

Google query: Kaspersky Lab KERNEL_MODE_EXCEPTION_NOT_HANDLED

 

 

 

On Wed 05/12/2012 16:04:15 GMT your computer crashed

crash dump file: C:\WINDOWS\Minidump\Mini120512-01.dmp

This was probably caused by the following module: klif.sys (klif+0x12ED2)

Bugcheck code: 0x1000008E (0xFFFFFFFFC000001D, 0xFFFFFFFF80564DDA, 0xFFFFFFFF9D9D2B68, 0x0)

Error: KERNEL_MODE_EXCEPTION_NOT_HANDLED_M

file path: C:\WINDOWS\system32\drivers\klif.sys

product: Kaspersky Anti-Virus ®

company: Kaspersky Lab

description: Klif Mini-Filter [fre_wnet_x86]

Bug check description: This indicates that a kernel-mode program 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.

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: klif.sys (Klif Mini-Filter [fre_wnet_x86], Kaspersky Lab).

Google query: Kaspersky Lab KERNEL_MODE_EXCEPTION_NOT_HANDLED_M

 

 

 

On Tue 04/12/2012 19:22:09 GMT your computer crashed

crash dump file: C:\WINDOWS\Minidump\Mini120412-01.dmp

This was probably caused by the following module: ntoskrnl.exe (nt+0x20E65)

Bugcheck code: 0x1000008E (0xFFFFFFFFC0000005, 0xFFFFFFFF804F7E65, 0xFFFFFFFFB83B4CE0, 0x0)

Error: KERNEL_MODE_EXCEPTION_NOT_HANDLED_M

file path: C:\WINDOWS\system32\ntoskrnl.exe

product: Système d'exploitation Microsoft® Windows®

company: Microsoft Corporation

description: Noyau et système NT

Bug check description: This indicates that a kernel-mode program 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 the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.

 

 

 

On Sun 25/11/2012 16:34:29 GMT your computer crashed

crash dump file: C:\WINDOWS\Minidump\Mini112512-02.dmp

This was probably caused by the following module: ntoskrnl.exe (nt+0x8DDDA)

Bugcheck code: 0x1000008E (0xFFFFFFFFC000001D, 0xFFFFFFFF80564DDA, 0xFFFFFFFFF7555C78, 0x0)

Error: KERNEL_MODE_EXCEPTION_NOT_HANDLED_M

file path: C:\WINDOWS\system32\ntoskrnl.exe

product: Système d'exploitation Microsoft® Windows®

company: Microsoft Corporation

description: Noyau et système NT

Bug check description: This indicates that a kernel-mode program 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 the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.

 

 

 

On Sun 25/11/2012 09:11:55 GMT your computer crashed

crash dump file: C:\WINDOWS\Minidump\Mini112512-01.dmp

This was probably caused by the following module: ntoskrnl.exe (nt+0x20E65)

Bugcheck code: 0x1000008E (0xFFFFFFFFC0000005, 0xFFFFFFFF804F7E65, 0xFFFFFFFFB58CDCE0, 0x0)

Error: KERNEL_MODE_EXCEPTION_NOT_HANDLED_M

file path: C:\WINDOWS\system32\ntoskrnl.exe

product: Système d'exploitation Microsoft® Windows®

company: Microsoft Corporation

description: Noyau et système NT

Bug check description: This indicates that a kernel-mode program 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 the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.

 

 

 

On Sat 24/11/2012 08:33:13 GMT your computer crashed

crash dump file: C:\WINDOWS\Minidump\Mini112412-01.dmp

This was probably caused by the following module: ntoskrnl.exe (nt+0x8DDDA)

Bugcheck code: 0x1000008E (0xFFFFFFFFC000001D, 0xFFFFFFFF80564DDA, 0xFFFFFFFFAC224C10, 0x0)

Error: KERNEL_MODE_EXCEPTION_NOT_HANDLED_M

file path: C:\WINDOWS\system32\ntoskrnl.exe

product: Système d'exploitation Microsoft® Windows®

company: Microsoft Corporation

description: Noyau et système NT

Bug check description: This indicates that a kernel-mode program 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 the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.

 

 

 

 

--------------------------------------------------------------------------------

Conclusion

--------------------------------------------------------------------------------

 

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

 

klif.sys (Klif Mini-Filter [fre_wnet_x86], Kaspersky Lab)

 

If no updates for these drivers are available, try searching with Google on the names of these drivers in combination the errors that have been reported for these drivers and include the brand and model name of your computer as well in the query. This often yields interesting results from discussions from 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 actually 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.

Lien vers le commentaire
Partager sur d’autres sites

Invité Notpa

Bonsoir karlomat,

 

D'après le net, il s'agit d'un problème avec Kaspersky. Les solutions proposées sont de désinstaller complètement Kaspersky, rebooter, installer la dernière version connue à ce jour, puis rebooter. La plus part des utilisateurs ayant eu ce problème l’ont résolu de cette manière.

 

Voir le lien Utilitaire de désinstallation des produits Kaspersky Lab pour une désinstallation propre et complète de Kasperky.

 

A+

 

Notpa

Lien vers le commentaire
Partager sur d’autres sites

Join the conversation

You are posting as a guest. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.

Invité
Répondre à ce sujet…

×   Collé en tant que texte enrichi.   Coller en tant que texte brut à la place

  Seulement 75 émoticônes maximum sont autorisées.

×   Votre lien a été automatiquement intégré.   Afficher plutôt comme un lien

×   Votre contenu précédent a été rétabli.   Vider l’éditeur

×   Vous ne pouvez pas directement coller des images. Envoyez-les depuis votre ordinateur ou insérez-les depuis une URL.

 Share

  • En ligne récemment   0 membre est en ligne

    Aucun utilisateur enregistré regarde cette page.

×
×
  • Créer...