Bonsoir
j'aurais besoin d'un petit coup de main car sur mon pc qui est assez récent j'ai réguliérement des message d'erreur au démarage
mais je ne sais comment les réparer .
Avec le logiciel who chashed j 'ai fait une analyse et voici le résultat
Crash Dump Analysis
--------------------------------------------------------------------------------
Crash dump directory: C:\Windows\Minidump
Crash dumps are enabled on your computer.
On Wed 02/03/2016 06:42:33 GMT your computer crashed
crash dump file: C:\Windows\Minidump\030216-7468-01.dmp
This was probably caused by the following module: fltmgr.sys (FLTMGR!DeleteStreamListCtrlCallback+0xA9)
Bugcheck code: 0x139 (0x3, 0xFFFFD00023BE1420, 0xFFFFD00023BE1378, 0x0)
Error: KERNEL_SECURITY_CHECK_FAILURE
file path: C:\Windows\system32\drivers\fltmgr.sys
product: Système d’exploitation Microsoft® Windows®
company: Microsoft Corporation
description: Gestionnaire de filtres de système de fichiers Microsoft
Bug check description: The kernel has detected the corruption of a critical data structure.
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 Wed 02/03/2016 06:42:33 GMT your computer crashed
crash dump file: C:\Windows\memory.dmp
This was probably caused by the following module: fltmgr.sys (FLTMGR!DeleteStreamListCtrlCallback+0xA9)
Bugcheck code: 0x139 (0x3, 0xFFFFD00023BE1420, 0xFFFFD00023BE1378, 0x0)
Error: KERNEL_SECURITY_CHECK_FAILURE
file path: C:\Windows\system32\drivers\fltmgr.sys
product: Système d’exploitation Microsoft® Windows®
company: Microsoft Corporation
description: Gestionnaire de filtres de système de fichiers Microsoft
Bug check description: The kernel has detected the corruption of a critical data structure.
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 Tue 01/03/2016 20:56:43 GMT your computer crashed
crash dump file: C:\Windows\Minidump\030116-6406-01.dmp
This was probably caused by the following module: ntfs.sys (NTFS!NtfsFullDeleteLcb+0x47)
Bugcheck code: 0x50 (0xFFFFC0004E082B08, 0x0, 0xFFFFF8011DB69CB1, 0x0)
Error: PAGE_FAULT_IN_NONPAGED_AREA
file path: C:\Windows\system32\drivers\ntfs.sys
product: Système d’exploitation Microsoft® Windows®
company: Microsoft Corporation
description: Pilote du système de fichiers NT
Bug check description: This indicates that invalid system memory has been referenced.
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 27/02/2016 08:46:41 GMT your computer crashed
crash dump file: C:\Windows\Minidump\022716-5687-01.dmp
This was probably caused by the following module: ntkrnlmp.exe (nt!KeBugCheckEx+0x0)
Bugcheck code: 0x12B (0xFFFFFFFFC00002C4, 0xA65, 0x1B5B93E9F30, 0xFFFFD00029444000)
Error: FAULTY_HARDWARE_CORRUPTED_PAGE
Bug check description: This bug check indicates that a single-bit error was found in this page. This is a hardware memory error.
This is likely to be caused by a hardware problem problem. This error suggests a case of memory corruption because of a hardware problem. It is suggested you do a test on your RAM modules (memory test).
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.
On Fri 26/02/2016 20:33:41 GMT your computer crashed
crash dump file: C:\Windows\Minidump\022616-7296-01.dmp
This was probably caused by the following module: ci.dll (CI!CiReleaseContext+0x28)
Bugcheck code: 0xC2 (0x7, 0x126C, 0x2C3004C0, 0xFFFFC001E4973F20)
Error: BAD_POOL_CALLER
file path: C:\Windows\system32\ci.dll
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: Code Integrity Module
Bug check description: This indicates that the current thread is making a bad pool request.
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 Tue 23/02/2016 19:54:52 GMT your computer crashed
crash dump file: C:\Windows\Minidump\022316-5000-01.dmp
This was probably caused by the following module: ntkrnlmp.exe (nt!KeBugCheckEx+0x0)
Bugcheck code: 0xEF (0xFFFFE0001C2D2840, 0x0, 0x0, 0x0)
Error: CRITICAL_PROCESS_DIED
Bug check description: This indicates that a critical system process died.
There is a possibility this problem was caused by a virus or other malware.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.
--------------------------------------------------------------------------------
Conclusion
--------------------------------------------------------------------------------
6 crash dumps have been found and analyzed. No offending third party drivers have been found. Connsider using WhoCrashed Professional which offers more detailed analysis using symbol resolution. Also configuring your system to produce a full memory dump may help you.
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.
Pour moi tout ceci est du " chinois " pouvez vous m'aider a résoudre tout cela
Pour information j'ai réinitialisé mon pc il y a 15 jours et sa recommence de plus belle .
Merci d'avance pour vos futur réponse