Forum |  HardWare.fr | News | Articles | PC | S'identifier | S'inscrire | Shop Recherche
929 connectés 

  FORUM HardWare.fr
  Windows & Software
  Win 10

  éran bleu et redémarrage pc erreur : KMODE_EXCEPTION_NOT_HANDLED

 


 Mot :   Pseudo :  
 
Bas de page
Auteur Sujet :

éran bleu et redémarrage pc erreur : KMODE_EXCEPTION_NOT_HANDLED

n°3292447
spider gal​axy
Posté le 02-12-2017 à 11:52:32  profilanswer
 

Bonjour,
 
Cela fait déjà deux fois depuis hier que j'ai mon pc qui redémarre avec un jolie écran bleu et le message d'erreur suivant : KMODE_EXCEPTION_NOT_HANDLED
 
J'ai windows 10 avec la dernière mise à jour. Si je pouvais avoir un peu d'aide, car le le net je trouve pas de solution. Merci
 
edit :
 
J'ai fait une analyse avec whocrashed et j'obtiens ça :
 
System Information (local)
--------------------------------------------------------------------------------
 
Computer name: sg
Windows version: Windows 10 , 10.0, build: 16299
Windows dir: C:\WINDOWS
Hardware: ASUSTeK COMPUTER INC., H170M-PLUS
CPU: GenuineIntel Intel(R) Core(TM) i5-6600 CPU @ 3.30GHz Intel586, level: 6
4 logical processors, active mask: 15
RAM: 34283339776 bytes total
 
 
 
 
--------------------------------------------------------------------------------
Crash Dump Analysis
--------------------------------------------------------------------------------
 
Crash dump directory: C:\WINDOWS\Minidump
 
Crash dumps are enabled on your computer.
 
On Sat 02/12/2017 11:35:26 your computer crashed
crash dump file: C:\WINDOWS\Minidump\120217-7484-01.dmp
This was probably caused by the following module: classpnp.sys (CLASSPNP+0x3FB7)  
Bugcheck code: 0x1E (0xFFFFFFFFC0000005, 0xFFFFF80F9B8E3FB7, 0xFFFFCA0393ADE858, 0xFFFFCA0393ADE0A0)
Error: KMODE_EXCEPTION_NOT_HANDLED
file path: C:\WINDOWS\system32\drivers\classpnp.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: SCSI Class System Dll
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 a standard Microsoft module. Your system configuration may be incorrect. Possibly this problem is caused by another driver on your system that cannot be identified at this time.  
 
 
 
On Sat 02/12/2017 11:35:26 your computer crashed
crash dump file: C:\WINDOWS\memory.dmp
This was probably caused by the following module: fltsrv.sys (fltsrv+0x40B7)  
Bugcheck code: 0x1E (0xFFFFFFFFC0000005, 0xFFFFF80F9B8E3FB7, 0xFFFFCA0393ADE858, 0xFFFFCA0393ADE0A0)
Error: KMODE_EXCEPTION_NOT_HANDLED
file path: C:\WINDOWS\system32\drivers\fltsrv.sys
product: Acronis Storage Filter Management
company: Acronis International GmbH
description: Acronis Storage Filter Management 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: fltsrv.sys (Acronis Storage Filter Management Driver, Acronis International GmbH).  
Google query: Acronis International GmbH KMODE_EXCEPTION_NOT_HANDLED
 
 
 
 
 
--------------------------------------------------------------------------------
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:  
 
fltsrv.sys (Acronis Storage Filter Management Driver, Acronis International GmbH)
 
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.


Message édité par spider galaxy le 02-12-2017 à 12:51:15
mood
Publicité
Posté le 02-12-2017 à 11:52:32  profilanswer
 

n°3292501
HPIR40
Posté le 02-12-2017 à 16:13:01  profilanswer
 

C'est pas compliqué il suffit de lire: il y a un soucis avec Acronis Storage Filter Management donc je commencerai par désinstaller tout ce qui est en relation avec Acronis et je rebooterai


Message édité par HPIR40 le 02-12-2017 à 16:13:59
n°3292685
spider gal​axy
Posté le 04-12-2017 à 11:29:42  profilanswer
 

Merci, j'y avais pensé, mais même en le désinstallant cela ne change rien même pire je ne pouvais plus ouvrir FF57 pourtant il figurait bien ouvert dans le gestionnaire des tâches.
 
J'ai dû restaurer à partir d'une ancienne sauvegarde pour avoir de nouveau accès à FF57.  
 
C'est bien la 1ere fois que je me retrouve avec une merde pareil.
 
Je me demande si cela n'a rien à voir avec mon concentrateur usb d-link ou mes cpl tp-link car hier en plus de ne plus avoir accès à FF57, je n'arrivais plus à me connecter au à internet (passerelle ip introuvable ou un truc dans le genre).
 
Bref, il y a un moins de vérifier si mes ports usb son correctement  configurer (driver, pas de conflit entre les ports, etc.) ?
 
edit: j'y comprends plus rien, j'ai désinstallé acronis + suppression de tous les fichiers acronis avec leur outil cleanup et maintenant c'est kaspersky qui me le fait. Chose étonnante, dès que j'ouvre FF57 et karspersky, j'ai l'écran bleu qui arrive. Avant c'était FF57 et acronis.
 
Crash dump directory: C:\WINDOWS\Minidump
 
Crash dumps are enabled on your computer.
 
On Mon 04/12/2017 15:42:47 your computer crashed
crash dump file: C:\WINDOWS\Minidump\120417-8015-01.dmp
This was probably caused by the following module: classpnp.sys (CLASSPNP+0x3FB7)  
Bugcheck code: 0x1E (0xFFFFFFFFC0000005, 0xFFFFF80959403FB7, 0x0, 0x2C)
Error: KMODE_EXCEPTION_NOT_HANDLED
file path: C:\WINDOWS\system32\drivers\classpnp.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: SCSI Class System Dll
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 a standard Microsoft module. Your system configuration may be incorrect. Possibly this problem is caused by another driver on your system that cannot be identified at this time.  
 
 
 
On Mon 04/12/2017 15:42:47 your computer crashed
crash dump file: C:\WINDOWS\memory.dmp
This was probably caused by the following module: klbackupdisk.sys (klbackupdisk+0x61DD)  
Bugcheck code: 0x1E (0xFFFFFFFFC0000005, 0xFFFFF80959403FB7, 0x0, 0x2C)
Error: KMODE_EXCEPTION_NOT_HANDLED
file path: C:\WINDOWS\system32\drivers\klbackupdisk.sys
product: System Interceptors PDK
company: AO Kaspersky Lab
description: Backup Disk Filter [fre_wnet_x64]
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: klbackupdisk.sys (Backup Disk Filter [fre_wnet_x64], AO Kaspersky Lab).  
Google query: AO Kaspersky Lab KMODE_EXCEPTION_NOT_HANDLED


Message édité par spider galaxy le 04-12-2017 à 15:57:28
n°3292745
HPIR40
Posté le 04-12-2017 à 16:41:04  profilanswer
 

Mouarf
 
Encore une partie backup mais de kaspersky cette fois ci qui part en vrille.
 
La va falloir aller voir du coté scan virus et malware.

n°3292790
spider gal​axy
Posté le 04-12-2017 à 22:52:04  profilanswer
 

Effectivement, le problème peut provenir de karspersky. J'ai vu sur leur forum que je ne suis pas le seul.


Aller à :
Ajouter une réponse
  FORUM HardWare.fr
  Windows & Software
  Win 10

  éran bleu et redémarrage pc erreur : KMODE_EXCEPTION_NOT_HANDLED

 

Sujets relatifs
Autoroute Express 2011 erreurRedémarrage en boucle win10
Freeze puis redémarrage : j'ai besoin d'aide :oMigration NPS RADIUS 2K8 ver 2012 erreur
Windows 10 - écran bleu incessantErreur démarrage
Erreur 0x800704cfWindows 10, version 1703 - Erreur 0xc00000fd
empecher message d'erreur au redémarrage après arrêt imprévu 
Plus de sujets relatifs à : éran bleu et redémarrage pc erreur : KMODE_EXCEPTION_NOT_HANDLED


Copyright © 1997-2022 Hardware.fr SARL (Signaler un contenu illicite / Données personnelles) / Groupe LDLC / Shop HFR