Bonjour
Depuis 19h j'ai eu de nombreux BSOD dont voici le rendu par WhoCrashed :
System Information (local)
"Computer name: PHILIPPE-PC
Windows version: Windows 10 , 10.0, build: 10586
Windows dir: C:\WINDOWS
Hardware: GA-880GM-UD2H, Gigabyte Technology Co., Ltd.
CPU: AuthenticAMD AMD Phenom(tm) II X4 955 Processor AMD586, level: 16
4 logical processors, active mask: 15
RAM: 4291321856 bytes total
Crash Dump Analysis
Crash dump directory: C:\WINDOWS\Minidump
Crash dumps are enabled on your computer.
On Sun 12/06/2016 21:50:25 GMT your computer crashed
crash dump file: C:\WINDOWS\Minidump\061216-16015-01.dmp
This was probably caused by the following module: fileinfo.sys (fileinfo! ?? ::NNGAKEGL::`string'+0xCDF)
Bugcheck code: 0x139 (0x3, 0xFFFFD001309E9550, 0xFFFFD001309E94A8, 0x0)
Error: KERNEL_SECURITY_CHECK_FAILURE
file path: C:\WINDOWS\system32\drivers\fileinfo.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: FileInfo Filter Driver
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 Sun 12/06/2016 21:50:25 GMT your computer crashed
crash dump file: C:\WINDOWS\memory.dmp
This was probably caused by the following module: fileinfo.sys (fileinfo! ?? ::NNGAKEGL::`string'+0xCDF)
Bugcheck code: 0x139 (0x3, 0xFFFFD001309E9550, 0xFFFFD001309E94A8, 0x0)
Error: KERNEL_SECURITY_CHECK_FAILURE
file path: C:\WINDOWS\system32\drivers\fileinfo.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: FileInfo Filter Driver
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 Sun 12/06/2016 17:26:14 GMT your computer crashed
crash dump file: C:\WINDOWS\Minidump\061216-8890-01.dmp
This was probably caused by the following module: rapportcerberus64_1609041.sys (RapportCerberus64_1609041+0x89EB6)
Bugcheck code: 0xC2 (0x7, 0x126C, 0x5030100, 0xFFFFC00092660010)
Error: BAD_POOL_CALLER
file path: C:\ProgramData\Trusteer\Rapport\store\exts\RapportCerberus\baseline\RapportCerberus64_1609041.sys
product: Rapport
company: IBM Corp.
description: RapportCerberus
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.
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: rapportcerberus64_1609041.sys (RapportCerberus, IBM Corp.).
Google query: IBM Corp. BAD_POOL_CALLER
On Sun 12/06/2016 17:19:31 GMT your computer crashed
crash dump file: C:\WINDOWS\Minidump\061216-24093-01.dmp
This was probably caused by the following module: wof.sys (Wof!FileProvReadCompressedCompletionWorker+0x9D)
Bugcheck code: 0x1E (0xFFFFFFFFC0000005, 0xFFFFF80188F4699D, 0x0, 0xFFFFFFFFFFFFFFFF)
Error: KMODE_EXCEPTION_NOT_HANDLED
file path: C:\WINDOWS\system32\drivers\wof.sys
product: Système d’exploitation Microsoft® Windows®
company: Microsoft Corporation
description: Filtre de superposition Windows
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 Sun 12/06/2016 17:10:49 GMT your computer crashed
crash dump file: C:\WINDOWS\Minidump\061216-25250-01.dmp
This was probably caused by the following module: Unknown ()
Bugcheck code: 0x0 (0x0, 0x0, 0x0, 0x0)
Error: CUSTOM_ERROR
A third party driver was identified as the probable root cause of this system error.
Google query: CUSTOM_ERROR
On Sun 12/06/2016 17:08:12 GMT your computer crashed
crash dump file: C:\WINDOWS\Minidump\061216-19125-01.dmp
This was probably caused by the following module: Unknown ()
Bugcheck code: 0x0 (0x0, 0x0, 0x0, 0x0)
Error: CUSTOM_ERROR
A third party driver was identified as the probable root cause of this system error.
Google query: CUSTOM_ERROR
On Sun 12/06/2016 17:03:42 GMT your computer crashed
crash dump file: C:\WINDOWS\Minidump\061216-24109-01.dmp
This was probably caused by the following module: fltmgr.sys (FLTMGR!TargetedIOCtrlAttachAsFoCtx+0x95)
Bugcheck code: 0x19 (0x3, 0xFFFFE001470715D0, 0xFFFF6001470715D0, 0xFFFFE001470715D0)
Error: BAD_POOL_HEADER
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: This indicates that a pool header is corrupt.
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 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.
Conclusion
8 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:
rapportcerberus64_1609041.sys (RapportCerberus, IBM Corp.) "
Et encore les crash ont été plus nombreux que ceux la car des fois à peine arrivé au log ca crashait. J'ai essayé de lancer des scanhealth ou des restorehealth ou meme des reinitialisation mais ça crashait aussi même si je les lançais depuis un mode sans echecs.
J'ai voulu aussi booté sur mes CD windows ( et même sur une clef linux) mais pas moyen de booter dessus. J'avais beau changer l ordre de boot dans le bios mais aps moyen. c'etait comme si mon ordi ne tenait pas compte de mon changement d'ordre de boot. Jusqu'a minuit seul ma partition avec win 7 acceptait de fonctionner. Depuis minuit les BSod se sont calmé car depuis (touchons du bois) je n'en ai pas eu.
C'est la premiere fois que je vois un truc comme ça.
Si vous avez des idées je suis preneur...
