bonjours à tous je suis nouveau sur ce forum depuis quelques temps mon ordi était très lent et maintenant ecran bleu au démarage je peux accéder en mode sans échec j'ai fais tous les antimalware j'ai mis a jour les pilotes je ne sais pas du tout d'où cela peut venir j'ai verifier ma ram avec memtest aucune erreur je pense que mon ordi commence a être vieux
merci pour votre aide
voici ma config
windows 10 pro
carte mère MSI 760GM-P34 fx
AMD phenom II X4 965
carte graphique nvidia gforce 560 ti
ram 16 Go
voici mon rapport de who crashed
Crash Dump Analysis
Crash dumps are enabled on your computer.
Crash dump directories:
C:\Windows
C:\Windows\Minidump
On Mon 12/11/2018 11:28:32 your computer crashed or a problem was reported
crash dump file: C:\Windows\Minidump\111218-19281-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x15C980)
Bugcheck code: 0x3B (0x80000003, 0xFFFFF803BEB80488, 0xFFFFA78139F2EFD0, 0x0)
Error: SYSTEM_SERVICE_EXCEPTION
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 an exception happened while executing a routine that transitions from non-privileged code to privileged code.
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 the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.
On Mon 12/11/2018 11:28:32 your computer crashed or a problem was reported
crash dump file: C:\Windows\MEMORY.DMP
This was probably caused by the following module: fltmgr.sys (FLTMGR!FltNotifyFilterChangeDirectory+0x3F16)
Bugcheck code: 0x3B (0x80000003, 0xFFFFF803BEB80488, 0xFFFFA78139F2EFD0, 0x0)
Error: SYSTEM_SERVICE_EXCEPTION
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 an exception happened while executing a routine that transitions from non-privileged code to privileged code.
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 file system 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.
On Mon 12/11/2018 11:19:01 your computer crashed or a problem was reported
crash dump file: C:\Windows\Minidump\111218-28656-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x15C980)
Bugcheck code: 0x3B (0x80000003, 0xFFFFF803A0570488, 0xFFFFA480701C4FD0, 0x0)
Error: SYSTEM_SERVICE_EXCEPTION
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 an exception happened while executing a routine that transitions from non-privileged code to privileged code.
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 the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.
On Mon 12/11/2018 00:44:00 your computer crashed or a problem was reported
crash dump file: C:\Windows\Minidump\111218-15843-01.dmp
This was probably caused by the following module: hal.dll (0xFFFFF80119E1B6C7)
Bugcheck code: 0xA (0x974FF08, 0xF, 0x1, 0xFFFFF80119E1B6C7)
Error: IRQL_NOT_LESS_OR_EQUAL
file path: C:\Windows\system32\hal.dll
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: Hardware Abstraction Layer DLL
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.
Conclusion
4 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.