Bonjour à tous,
 
J'ai depuis quelques temps (mois) des soucis avec mon PC ==> BSOD a répétition, le dernier suite à un crash en game
 
- Antivirus lancé, rien vu : Toujours BSOD de manière aléatoire  
- BIOS maj : Toujours BSOD de manière aléatoire  
- Pilote MAJ : Toujours BSOD de manière aléatoire  
- Dépoussiéré totalement le PC : Toujours BSOD de manière aléatoire  
 
- J'ai re instal window au moins 2 fois (réinitialisation complète)
- Testé ma RAM avec MEMTEST en boot (une des barrettes était défectueuse = changement de RAM)
- La ram n'est pas OC (sans XMP sur CM)
 
Je pensais être au top mais retour de 3 BSOD (habituels) enchainés proprement hier soir suite crash en jeu,  
1. Kernel Security,  
2. puis System  
3. puis Thread
 
ensuite le PC a bloqué au démarrage (ce qui m'arrivait régulièrement après les BSOD)  
Après 3 ou 4 lancement qui ne donne rien ca tourne mais rien ne se passe j'arrive sur écran qui propose de dépanner ou restaurer ...
Ce coup ci rien a marché sauf le point de restauration
 
Je suis un peu perdu, si vous avez des orientations à me donner ce serait top,  
 
ma conf date de 3 ans :  
 
AMD RYZEN 5 3600
AMD RADEON 5600XT
MSI MAG B550M BAZZOKA
un petit SSD M2 INTEL SSDPEKNW010T8 pour le Système
2*16 DDR4 3200 CL13 (sans XMP donc 2100 ou 2400)
j'ai un AIO CORSAIR pour le CPU (comment savoir si ca fonctionne bien ?)
 
Un gros merci par avance
 
Bon dimanche

Il faudrait le rapport complet du logiciel Whocrashed, à poser avec www.cjoint.com ou un service équivalent.

Hello,
 
J'imagine que la restauration a du supprimer les dumps car je n'ai rien quand je lance Whocrashed

Vérifies l'état de santé du ssd (Crystaldisk)
L'alimentation est de qualité?

Hello  
l'AIO c'est : ENERMAX WATERCOOLING LIQMAX III 120MM
l'alimentation : CORSAIR ALIM BUILDER SERIES CX550
 
L'analyse me donne ca :  
         Model : INTEL SSDPEKNW010T8
        Firmware : 002C
   Serial Number : BTNH942411FD1P0B
       Disk Size : 1024,2 GB
       Interface : NVM Express
        Standard : NVM Express 1.3
   Transfer Mode : PCIe 3.0 x4 | PCIe 3.0 x4
  Power On Hours : 4403 heures
  Power On Count : 1297 fois
      Host Reads : 22305 GB
     Host Writes : 14597 GB
     Temperature : 35 C (95 F)
   Health Status : Bon (98 %)
        Features : S.M.A.R.T., TRIM, VolatileWriteCache

Perdu mon PC pendant 2h ...  
 
J'ai du faire une restauration (et reperdre mes dumps), mais déjà 2 à la reprise.
 
que je post ci dessous.  
Pour ne rien vous cacher ... je suis triste
 

--------------------------------------------------------------------------------
System Information (local)
--------------------------------------------------------------------------------

Computer name: DESKTOP-K2LF710
Windows version: Windows 10, 10.0, version 2009, build: 22631
Windows dir: C:\WINDOWS
Hardware: MS-7C95, Micro-Star International Co., Ltd., MAG B550M BAZOOKA (MS-7C95)
CPU: AuthenticAMD AMD Ryzen 5 3600 6-Core Processor 8664, level: 23
12 logical processors, active mask: 4095
RAM: 34280943616 bytes (31,9GB)

--------------------------------------------------------------------------------
Crash Dump Analysis
--------------------------------------------------------------------------------

Crash dumps are enabled on your computer. This system is not configured for complete or automatic crash dumps. For best results, configure your system to write out complete or automatic crash dumps. Select Tools->Crash Dump Configuration from the main menu to configure your system to write out complete memory dumps.

Crash dump directories:
C:\WINDOWS
C:\WINDOWS\Minidump

On Sun 12/11/2023 19:57:59 your computer crashed or a problem was reported
crash dump file: C:\WINDOWS\Minidump\111223-6453-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x412740)
Bugcheck code: 0x1E (0xFFFFFFFFC0000005, 0xFFFFF802102B1546, 0x0, 0x11)
Error: KMODE_EXCEPTION_NOT_HANDLED
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 kernel-mode program generated an exception which the error handler did not catch.
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.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.

On Sun 12/11/2023 16:46:47 your computer crashed or a problem was reported
crash dump file: C:\WINDOWS\Minidump\111223-6468-01.dmp
This was probably caused by the following module: hardware.sys (hardware)
Bugcheck code: 0x1A (0x41792, 0xFFFFFB3FFEC86BE8, 0x10000, 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 12/11/2023 16:40:46 your computer crashed or a problem was reported
crash dump file: C:\WINDOWS\Minidump\111223-46125-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x89661B)
Bugcheck code: 0x1000007E (0xFFFFFFFFC0000005, 0xFFFFF8051D49661B, 0xFFFFF88A47230668, 0xFFFFF88A4722FE80)
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.

On Sun 12/11/2023 16:15:59 your computer crashed or a problem was reported
crash dump file: C:\WINDOWS\Minidump\111223-6218-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x412740)
Bugcheck code: 0x1A (0x403, 0xFFFFFDC0C0000010, 0x8A00000000200121, 0xFFFFFD8000000000)
Error: MEMORY_MANAGEMENT
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 severe memory management error occurred. The page table and PFNs are out of sync . This is probably a hardware error, especially if parameters 3 & 4 differ by only a single bit.
This is likely to be caused by a hardware 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) and make sure your system is not getting overheated. This problem might also be caused because of overheating (thermal issue).
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. 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.

== je viens de faire ca :
C:\Windows\System32>sfc /scannow

Début de l’analyse du système. Cette opération peut nécessiter un certain temps.

Démarrage de la phase de vérification de l’analyse du système.
La vérification est à 100% terminée.

Le programme de protection des ressources Windows n’a trouvé aucune violation d’intégrité.

ca sent pas bon pour la RAM

 
 
oui il devrait faire un memtest (la version à partir d'une clef usb memtest86) et lancer le test pendant une nuit.