J'ai lancé le logiciel WhoCrashed et j'ai obtenu ceci :
Edit : ces crash ont eu lieu lors de l'installation des drivers Logitech
Crash Dump Analysis
--------------------------------------------------------------------------------
Crash dump directory: C:\WINDOWS\Minidump
Crash dumps are enabled on your computer.
On Sun 24/01/2016 22:35:13 GMT your computer crashed
crash dump file: C:\WINDOWS\Minidump\012416-5921-01.dmp
This was probably caused by the following module: androidafdx64.sys (AndroidAFDx64+0x2AEE)
Bugcheck code: 0xD1 (0xFFFFE001C7631000, 0x2, 0x1, 0xFFFFF80128272AEE)
Error: DRIVER_IRQL_NOT_LESS_OR_EQUAL
file path: C:\WINDOWS\SysWow64\drivers\AndroidAFDx64.sys
product: ASUS Ai Charger
company: ASUSTek Computer Inc.
description: ASUS Charger driver
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.
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: androidafdx64.sys (ASUS Charger driver, ASUSTek Computer Inc.).
Google query: ASUSTek Computer Inc. DRIVER_IRQL_NOT_LESS_OR_EQUAL
On Sun 24/01/2016 22:35:13 GMT your computer crashed
crash dump file: C:\WINDOWS\memory.dmp
This was probably caused by the following module: androidafdx64.sys (AndroidAFDx64+0x2AEE)
Bugcheck code: 0xD1 (0xFFFFE001C7631000, 0x2, 0x1, 0xFFFFF80128272AEE)
Error: DRIVER_IRQL_NOT_LESS_OR_EQUAL
file path: C:\WINDOWS\SysWow64\drivers\AndroidAFDx64.sys
product: ASUS Ai Charger
company: ASUSTek Computer Inc.
description: ASUS Charger driver
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.
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: androidafdx64.sys (ASUS Charger driver, ASUSTek Computer Inc.).
Google query: ASUSTek Computer Inc. DRIVER_IRQL_NOT_LESS_OR_EQUAL
On Sun 24/01/2016 22:20:19 GMT your computer crashed
crash dump file: C:\WINDOWS\Minidump\012416-7218-01.dmp
This was probably caused by the following module: androidafdx64.sys (AndroidAFDx64+0x2A91)
Bugcheck code: 0xC5 (0x8, 0x2, 0x0, 0xFFFFF8004C0BB119)
Error: DRIVER_CORRUPTED_EXPOOL
file path: C:\WINDOWS\SysWow64\drivers\AndroidAFDx64.sys
product: ASUS Ai Charger
company: ASUSTek Computer Inc.
description: ASUS Charger driver
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.
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: androidafdx64.sys (ASUS Charger driver, ASUSTek Computer Inc.).
Google query: ASUSTek Computer Inc. DRIVER_CORRUPTED_EXPOOL
On Sun 24/01/2016 12:32:58 GMT your computer crashed
crash dump file: C:\WINDOWS\Minidump\012416-7593-01.dmp
This was probably caused by the following module: androidafdx64.sys (AndroidAFDx64+0x2A91)
Bugcheck code: 0x1E (0xFFFFFFFFC0000005, 0xFFFFF80068C3D119, 0x0, 0xFFFFFFFFFFFFFFFF)
Error: KMODE_EXCEPTION_NOT_HANDLED
file path: C:\WINDOWS\SysWow64\drivers\AndroidAFDx64.sys
product: ASUS Ai Charger
company: ASUSTek Computer Inc.
description: ASUS Charger 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: androidafdx64.sys (ASUS Charger driver, ASUSTek Computer Inc.).
Google query: ASUSTek Computer Inc. KMODE_EXCEPTION_NOT_HANDLED
On Fri 22/01/2016 09:50:46 GMT your computer crashed
crash dump file: C:\WINDOWS\Minidump\012216-5718-01.dmp
This was probably caused by the following module: androidafdx64.sys (AndroidAFDx64+0x2A91)
Bugcheck code: 0x1E (0xFFFFFFFFC0000005, 0xFFFFF8023684B119, 0x0, 0xFFFFFFFFFFFFFFFF)
Error: KMODE_EXCEPTION_NOT_HANDLED
file path: C:\WINDOWS\SysWow64\drivers\AndroidAFDx64.sys
product: ASUS Ai Charger
company: ASUSTek Computer Inc.
description: ASUS Charger 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: androidafdx64.sys (ASUS Charger driver, ASUSTek Computer Inc.).
Google query: ASUSTek Computer Inc. KMODE_EXCEPTION_NOT_HANDLED
--------------------------------------------------------------------------------
Conclusion
--------------------------------------------------------------------------------
5 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:
androidafdx64.sys (ASUS Charger driver, ASUSTek Computer Inc.)
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.
Késako ce driver androidAfdx64 ?
Message édité par bigboub le 25-01-2016 à 13:02:17