bonjour!
 
voila maintenant quelque temps que j'ai un BSOD au démarrage.
 
config :  
 
I7 9700 k
MSI MPG z390 EDGE AC  
2*8go corsair vengeance pro 2666  
Noctua NH U12A
KFA2 rtx 2070 super
MP510 960 M.2
SSD PNY CS900 480 go
boitier fractal design define C tempered
Alim corsair RM 750
 
 
voici un rapport who crashed, si quelqu'un peut m'aider à l'interprétation, en plus de mes recherches personnelles, ...
 
D'avance merci pour vos réponses,  
 
bonne journée  
 
 
Crash dumps are enabled on your computer.  
 
Crash dump directories:  
C:\Windows
C:\Windows\Minidump
 
On Wed 11/11/2020 08:48:53 your computer crashed or a problem was reported
crash dump file: C:\Windows\minidump\111120-19750-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x1C2CE0)  
Bugcheck code: 0x154 (0xFFFF97856753D000, 0xFFFFFA06B88E6630, 0x1, 0x0)
Error: UNEXPECTED_STORE_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 the store component caught an unexpected exception.  
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 Wed 11/11/2020 08:48:53 your computer crashed or a problem was reported
crash dump file: C:\Windows\MEMORY.DMP
This was probably caused by the following module: ntkrnlmp.exe (nt!SeConvertSidToStringSid+0x203A)  
Bugcheck code: 0x154 (0xFFFF97856753D000, 0xFFFFFA06B88E6630, 0x1, 0x0)
Error: UNEXPECTED_STORE_EXCEPTION
Bug check description: This indicates that the store component caught an unexpected exception.  
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 09/11/2020 18:23:22 your computer crashed or a problem was reported
crash dump file: C:\Windows\minidump\110920-18312-01.dmp
This was probably caused by the following module: hardware.sys (hardware)  
Bugcheck code: 0x1A (0x41792, 0xFFFFB68074943890, 0x8000000, 0x0)
Error: MEMORY_MANAGEMENT
Bug check description: This indicates that a severe memory management error occurred. A corrupted PTE has been detected.  
This might be a case of memory corruption. This may be because of a hardware issue such as faulty RAM, overheating (thermal issue) or because of a buggy driver. This problem might also be caused because of overheating (thermal issue).  
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: hardware.sys .  
Google query: hardware.sys MEMORY_MANAGEMENT
 
 
 
On Sun 08/11/2020 09:17:07 your computer crashed or a problem was reported
crash dump file: C:\Windows\minidump\110820-17765-01.dmp
This was probably caused by the following module: fltmgr.sys (0xFFFFF80145F3859F)  
Bugcheck code: 0x1000007E (0xFFFFFFFFC0000005, 0xFFFFF80145F3859F, 0xFFFFA90FFB187148, 0xFFFFA90FFB186990)
Error: SYSTEM_THREAD_EXCEPTION_NOT_HANDLED_M
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 system thread 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 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 Tue 03/11/2020 16:34:55 your computer crashed or a problem was reported
crash dump file: C:\Windows\minidump\110320-18125-01.dmp
This was probably caused by the following module: hardware.sys (hardware)  
Bugcheck code: 0x1A (0x41792, 0xFFFFF000D74B1240, 0x1000000, 0x0)
Error: MEMORY_MANAGEMENT
Bug check description: This indicates that a severe memory management error occurred. A corrupted PTE has been detected.  
This might be a case of memory corruption. This may be because of a hardware issue such as faulty RAM, overheating (thermal issue) or because of a buggy driver. This problem might also be caused because of overheating (thermal issue).  
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: hardware.sys .  
Google query: hardware.sys MEMORY_MANAGEMENT
 
 
 
On Tue 03/11/2020 16:21:38 your computer crashed or a problem was reported
crash dump file: C:\Windows\minidump\110320-19671-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x1C2CE0)  
Bugcheck code: 0x1000007E (0xFFFFFFFFC0000005, 0xFFFFF8025B540751, 0xFFFFF485C4109C38, 0xFFFFA6807E7EE930)
Error: SYSTEM_THREAD_EXCEPTION_NOT_HANDLED_M
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 a system thread 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 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. 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:  
 
hardware.sys  
 
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.
 
 
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.
 
 

Qu'as-tu testé ? changé limité les lecteurs, les barrettes de RAM, changé de CG,... ?