BlueScreen et explorer.exe echec
Oupy
-
Oupy -
Oupy -
Bonjour,
Donc voilà, depuis quelques jours, j'ai eu 4 fois ce fameux écran bleu, me disant quelque chose du genre «window has been shut down to prevent damage». Au redémarrage, voilà ce que window m'a affiché :
Signature du problème :
Nom d'événement de problème: BlueScreen
Version du système: 6.1.7600.2.0.0.768.3
Identificateur de paramètres régionaux: 3084
Informations supplémentaires sur le problème :
BCCode: 1e
BCP1: FFFFFFFFC0000005
BCP2: FFFFF88004064238
BCP3: 0000000000000000
BCP4: FFFFFFFFFFFFFFFF
OS Version: 6_1_7600
Service Pack: 0_0
Product: 768_1
Fichiers aidant à décrire le problème :
C:\Windows\Minidump\112610-14882-01.dmp
C:\Users\Anthéa\AppData\Local\Temp\WER-67376-0.sysdata.xml
Lire notre déclaration de confidentialité en ligne :
http://go.microsoft.com/fwlink/?linkid=104288&clcid=0x040c
Si la déclaration de confidentialité en ligne n'est pas disponible, lisez la version hors connexion :
C:\Windows\system32\fr-FR\erofflps.txt
Je fais quelques recherches et je finis par faire une analyse avec WhoCrashed.
Crash dump directory: C:\Windows\Minidump
Crash dumps are enabled on your computer.
On Fri 2010-11-26 15:42:33 GMT your computer crashed
crash dump file: C:\Windows\Minidump\112610-14882-01.dmp
This was probably caused by the following module: kl1.sys (kl1+0x4E238)
Bugcheck code: 0x1E (0xFFFFFFFFC0000005, 0xFFFFF88004064238, 0x0, 0xFFFFFFFFFFFFFFFF)
Error: KMODE_EXCEPTION_NOT_HANDLED
file path: C:\Windows\system32\drivers\kl1.sys
product: Kaspersky Anti-Virus
company: Kaspersky Lab
description: Kaspersky Unified Driver
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: kl1.sys (Kaspersky Unified Driver, Kaspersky Lab).
Google query: kl1.sys Kaspersky Lab KMODE_EXCEPTION_NOT_HANDLED
On Fri 2010-11-26 15:42:33 GMT your computer crashed
crash dump file: C:\Windows\memory.dmp
This was probably caused by the following module: kl1.sys (kl1+0x4E238)
Bugcheck code: 0x1E (0xFFFFFFFFC0000005, 0xFFFFF88004064238, 0x0, 0xFFFFFFFFFFFFFFFF)
Error: KMODE_EXCEPTION_NOT_HANDLED
file path: C:\Windows\system32\drivers\kl1.sys
product: Kaspersky Anti-Virus
company: Kaspersky Lab
description: Kaspersky Unified Driver
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: kl1.sys (Kaspersky Unified Driver, Kaspersky Lab).
Google query: kl1.sys Kaspersky Lab KMODE_EXCEPTION_NOT_HANDLED
On Thu 2010-11-25 12:49:34 GMT your computer crashed
crash dump file: C:\Windows\Minidump\112510-15428-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x70740)
Bugcheck code: 0xD1 (0x0, 0x2, 0x8, 0x0)
Error: DRIVER_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 a kernel-mode driver attempted to access pageable memory at a process IRQL that was too high.
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 which cannot be identified at this time.
On Thu 2010-11-25 00:13:08 GMT your computer crashed
crash dump file: C:\Windows\Minidump\112410-15756-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x70740)
Bugcheck code: 0x1A (0x41287, 0xFFFFFFFF, 0x0, 0x0)
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. More often memory corruption happens because of software errors in buggy drivers, not because of faulty RAM modules.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver which cannot be identified at this time.
On Mon 2010-10-25 00:39:03 GMT your computer crashed
crash dump file: C:\Windows\Minidump\102410-21340-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x70740)
Bugcheck code: 0xC5 (0x0, 0x2, 0x0, 0xFFFFF80002DB50CD)
Error: DRIVER_CORRUPTED_EXPOOL
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 system attempted to access invalid memory at a process IRQL that was too high.
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. More often memory corruption happens because of software errors in buggy drivers, not because of faulty RAM modules.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver which cannot be identified at this time.
Et maintenant, mon explorer.exe ne veut plus s'ouvrir. Dès que je tente d'aller sur un dossier, panneau de configuration, etc. ça me marque échec d'un appel système. Mon bureau est gelé et mon curseur indique que ça charge toujours.
Merci de bien vouloir m'aider !!
Bonne journée
to
Donc voilà, depuis quelques jours, j'ai eu 4 fois ce fameux écran bleu, me disant quelque chose du genre «window has been shut down to prevent damage». Au redémarrage, voilà ce que window m'a affiché :
Signature du problème :
Nom d'événement de problème: BlueScreen
Version du système: 6.1.7600.2.0.0.768.3
Identificateur de paramètres régionaux: 3084
Informations supplémentaires sur le problème :
BCCode: 1e
BCP1: FFFFFFFFC0000005
BCP2: FFFFF88004064238
BCP3: 0000000000000000
BCP4: FFFFFFFFFFFFFFFF
OS Version: 6_1_7600
Service Pack: 0_0
Product: 768_1
Fichiers aidant à décrire le problème :
C:\Windows\Minidump\112610-14882-01.dmp
C:\Users\Anthéa\AppData\Local\Temp\WER-67376-0.sysdata.xml
Lire notre déclaration de confidentialité en ligne :
http://go.microsoft.com/fwlink/?linkid=104288&clcid=0x040c
Si la déclaration de confidentialité en ligne n'est pas disponible, lisez la version hors connexion :
C:\Windows\system32\fr-FR\erofflps.txt
Je fais quelques recherches et je finis par faire une analyse avec WhoCrashed.
Crash dump directory: C:\Windows\Minidump
Crash dumps are enabled on your computer.
On Fri 2010-11-26 15:42:33 GMT your computer crashed
crash dump file: C:\Windows\Minidump\112610-14882-01.dmp
This was probably caused by the following module: kl1.sys (kl1+0x4E238)
Bugcheck code: 0x1E (0xFFFFFFFFC0000005, 0xFFFFF88004064238, 0x0, 0xFFFFFFFFFFFFFFFF)
Error: KMODE_EXCEPTION_NOT_HANDLED
file path: C:\Windows\system32\drivers\kl1.sys
product: Kaspersky Anti-Virus
company: Kaspersky Lab
description: Kaspersky Unified Driver
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: kl1.sys (Kaspersky Unified Driver, Kaspersky Lab).
Google query: kl1.sys Kaspersky Lab KMODE_EXCEPTION_NOT_HANDLED
On Fri 2010-11-26 15:42:33 GMT your computer crashed
crash dump file: C:\Windows\memory.dmp
This was probably caused by the following module: kl1.sys (kl1+0x4E238)
Bugcheck code: 0x1E (0xFFFFFFFFC0000005, 0xFFFFF88004064238, 0x0, 0xFFFFFFFFFFFFFFFF)
Error: KMODE_EXCEPTION_NOT_HANDLED
file path: C:\Windows\system32\drivers\kl1.sys
product: Kaspersky Anti-Virus
company: Kaspersky Lab
description: Kaspersky Unified Driver
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: kl1.sys (Kaspersky Unified Driver, Kaspersky Lab).
Google query: kl1.sys Kaspersky Lab KMODE_EXCEPTION_NOT_HANDLED
On Thu 2010-11-25 12:49:34 GMT your computer crashed
crash dump file: C:\Windows\Minidump\112510-15428-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x70740)
Bugcheck code: 0xD1 (0x0, 0x2, 0x8, 0x0)
Error: DRIVER_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 a kernel-mode driver attempted to access pageable memory at a process IRQL that was too high.
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 which cannot be identified at this time.
On Thu 2010-11-25 00:13:08 GMT your computer crashed
crash dump file: C:\Windows\Minidump\112410-15756-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x70740)
Bugcheck code: 0x1A (0x41287, 0xFFFFFFFF, 0x0, 0x0)
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. More often memory corruption happens because of software errors in buggy drivers, not because of faulty RAM modules.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver which cannot be identified at this time.
On Mon 2010-10-25 00:39:03 GMT your computer crashed
crash dump file: C:\Windows\Minidump\102410-21340-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x70740)
Bugcheck code: 0xC5 (0x0, 0x2, 0x0, 0xFFFFF80002DB50CD)
Error: DRIVER_CORRUPTED_EXPOOL
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 system attempted to access invalid memory at a process IRQL that was too high.
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. More often memory corruption happens because of software errors in buggy drivers, not because of faulty RAM modules.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver which cannot be identified at this time.
Et maintenant, mon explorer.exe ne veut plus s'ouvrir. Dès que je tente d'aller sur un dossier, panneau de configuration, etc. ça me marque échec d'un appel système. Mon bureau est gelé et mon curseur indique que ça charge toujours.
Merci de bien vouloir m'aider !!
Bonne journée
to
A voir également:
- BlueScreen et explorer.exe echec
- Explorer.exe - Télécharger - Divers Utilitaires
- Mode sans echec ps4 - Guide
- Démarrage sans échec - Guide
- Échec du chargement du module twitch - Forum jeux en ligne
- Mode sans échec asus - Forum BIOS
2 réponses
Salut,
Vu le code, on dirait un problème de mémoire dû directement ou indirectement à Kaspersky (un peu lourd..), fais un scan à tout hasard, si possible, puis réinstalle ton antivirus en utilisant leur logiciel de nettoyage du registre.
Vu le code, on dirait un problème de mémoire dû directement ou indirectement à Kaspersky (un peu lourd..), fais un scan à tout hasard, si possible, puis réinstalle ton antivirus en utilisant leur logiciel de nettoyage du registre.
Tout d'abord, bonjour et merci d'avoir répondu :D
Ensuite ... j'ai mis le disque d'installation de mon antivirus mais aucune fenêtre ne s'ouvre pour me demander si je veux le lire. Du coup, il n'y a aucune réaction. J'ai voulu aller sur mon ordinateur mais bien sûr, échec de l'appel système. Je fais clic droit. Bug.. Ma barre démarrer est carrément geler.
Et j'avais télécharger, en faisant quelques recherches, deux programmes qui scannaient l'ordi pour déceler les failles, les erreurs etc. Au-dessus de 160 de trouvés et niveau élevé. Mais bien entendu ... pour réparer, il faut payer le logiciel ...
Et je crois que j'avais oublié de préciser : mon bureau est complétement gelé. Les icônes ne s'affichent qu'à moitié, mon curseur indique que ça charge en permanence.
Ahlala -_-
Bonne journée :)
Ensuite ... j'ai mis le disque d'installation de mon antivirus mais aucune fenêtre ne s'ouvre pour me demander si je veux le lire. Du coup, il n'y a aucune réaction. J'ai voulu aller sur mon ordinateur mais bien sûr, échec de l'appel système. Je fais clic droit. Bug.. Ma barre démarrer est carrément geler.
Et j'avais télécharger, en faisant quelques recherches, deux programmes qui scannaient l'ordi pour déceler les failles, les erreurs etc. Au-dessus de 160 de trouvés et niveau élevé. Mais bien entendu ... pour réparer, il faut payer le logiciel ...
Et je crois que j'avais oublié de préciser : mon bureau est complétement gelé. Les icônes ne s'affichent qu'à moitié, mon curseur indique que ça charge en permanence.
Ahlala -_-
Bonne journée :)
