Bonjour, voici le bilan:
le 9 avril:
Crash dump directories:
C:\Windows
C:\Windows\Minidump
On Tue 09-04-19 18:40:48 your computer crashed or a problem was reported
crash dump file: C:\Windows\Minidump\040919-4453-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x1B35E0)
Bugcheck code: 0xA (0xFFFFF089EBB8CC03, 0x2, 0x0, 0xFFFFF8005B7724F0)
Error: IRQL_NOT_LESS_OR_EQUAL
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This indicates that Microsoft Windows or a kernel-mode driver accessed paged memory at DISPATCH_LEVEL or above. This is a software bug.
This bug check belongs to the crash dump test that you have performed with WhoCrashed or other software. It means that a crash dump file was properly written out.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.
On Tue 09-04-19 18:40:48 your computer crashed or a problem was reported
crash dump file: C:\Windows\MEMORY.DMP
This was probably caused by the following module: storport.sys (storport!StorPortGetScatterGatherList+0x579D)
Bugcheck code: 0xA (0xFFFFF089EBB8CC03, 0x2, 0x0, 0xFFFFF8005B7724F0)
Error: IRQL_NOT_LESS_OR_EQUAL
file path: C:\Windows\system32\drivers\storport.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: Microsoft Storage Port Driver
Bug check description: This indicates that Microsoft Windows or a kernel-mode driver accessed paged memory at DISPATCH_LEVEL or above. This is a software bug.
This bug check belongs to the crash dump test that you have performed with WhoCrashed or other software. It means that a crash dump file was properly written out.
The crash took place in a storage driver or controller driver. Since there is no other responsible driver detected, this could be pointing to a malfunctioning drive or corrupted disk. It's suggested that you run CHKDSK.
Hier:
On Fri 12-04-19 21:38:00 your computer crashed or a problem was reported
crash dump file: C:\Windows\Minidump\041219-4578-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x1B35E0)
Bugcheck code: 0xA (0x20000000000, 0x2, 0x1, 0xFFFFF8045EB83654)
Error: IRQL_NOT_LESS_OR_EQUAL
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This indicates that Microsoft Windows or a kernel-mode driver accessed paged memory at DISPATCH_LEVEL or above. This is a software bug.
This bug check belongs to the crash dump test that you have performed with WhoCrashed or other software. It means that a crash dump file was properly written out.
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 12-04-19 21:38:00 your computer crashed or a problem was reported
crash dump file: C:\Windows\MEMORY.DMP
This was probably caused by the following module: farflt.sys (farflt+0x1E69)
Bugcheck code: 0xA (0x20000000000, 0x2, 0x1, 0xFFFFF8045EB83654)
Error: IRQL_NOT_LESS_OR_EQUAL
file path: C:\Windows\system32\drivers\farflt.sys
product: Malwarebytes Anti-Ransomware Protection
company: Malwarebytes
description: Malwarebytes Anti-Ransomware Protection
Bug check description: This indicates that Microsoft Windows or a kernel-mode driver accessed paged memory at DISPATCH_LEVEL or above. This is a software bug.
This bug check belongs to the crash dump test that you have performed with WhoCrashed or other software. It means that a crash dump file was properly written out.
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: farflt.sys (Malwarebytes Anti-Ransomware Protection, Malwarebytes).
Google query: farflt.sys Malwarebytes IRQL_NOT_LESS_OR_EQUAL
Je ne faisais rien de particulier. Test de ram effectué (4 passes sur chaque barrette individuellement). 0 erreur.
Vérification disque dur avec Crucial Storage Executive.
Je ne sais pas ce qui cause ces écrans bleus à répétition.
Merci.