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