Problème de Bluescreen aléatoires

[alexandre.vachon]

Bonjour!

J'ai un problèmes de bluescreen qui semblent tout à fait aléatoires. Parfois ils arrivent en naviguant sur internet, parfois dans Office, parfois en regardant mes courriels. J'ai passer WhoCrashed, mais je n'y vois rien de concluant, rien ne semble indiquer une cause en particulier.

Le PC est un HP DC7800 sous Windows 10

Pouvez vous m'aider?

Merci beaucoup!

[Malekal_morte]

Salut,

Les écrans bleus ou BSOD sont des plantages de Windows qui ne peut plus continuer à fonctionner.
Ces plantages ont plusieurs sources possibles :
- sources logiciels : plantage d'un pilote d'un périphérique comme ceux de la carte graphique, l'antivirus qui plante ou tout autre logiciel qui peut se charger "dans un bas niveau" sur Windows.
- sources matériels : problème matériels sur le disque dur, barrettes de mémoire défectueuses ou incomparabilités, etc

Il faut impérativement que tu regardes si ces plantages ont lieu à des moments particuliers, par exemple, si c'est lorsque tu lances une vidéo sur ton navigateur internet ou un jeu, il y a des chances que ce soit le pilote de la carte graphique. Il faudra alors réinstaller les pilotes de la carte graphique.
Débranche aussi tout autre périphérique que le clavier/souris (manette de jeu, webcam en USB, imprimante USB, etc), si tu as un de ces périphériques, indique le, ça peut être une source.

plus d'informations sur ces écrans bleus, sur la page suivante : Les écrans bleus de plantages (BSOD)

On peut aussi utiliser WhoCrashed pour obtenir des informations sur ces plantages.
=> Tutoriel WhoCrashed
Fais un copier/coller du contenu ici comme indiqué dans le tuto.


puis :

Suis le tutoriel FRST. ( prends le temps de lire attentivement - tout y est bien expliqué ).

Attendre la fin du scan, un message indique que l'analyse est terminée.
Télécharge et lance le scan FRST,

Trois rapports FRST seront générés :
* FRST.txt
* Shortcut.
* Additionnal.txt

Envoie ces 3 rapports sur le site https://pjjoint.malekal.com/ et en retour donne les 3 liens pjjoint qui mènent aux rapports ici dans une nouvelle réponse afin que l'on puisse les consulter.

(Les liens bleus mènent à des tutoriels explicatifs pas à pas, clic dessus pour avoir les instructions plus précises à suivre).

[alexandre.vachon]

Merci pour la réponse

Voici ce que donne WhoCrashed

Crash dumps are enabled on your computer.

Crash dump directories:
C:\Windows
C:\Windows\Minidump

On Wed 2019-10-23 15:29:46 your computer crashed or a problem was reported
crash dump file: C:\Windows\Minidump\102319-9468-01.dmp
This was probably caused by the following module: hardware.sys (hardware)
Bugcheck code: 0x3B (0xC000001D, 0xFFFFB022314BB937, 0xFFFF860AA5743F20, 0x0)
Error: SYSTEM_SERVICE_EXCEPTION
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.
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 SYSTEM_SERVICE_EXCEPTION



On Wed 2019-10-23 15:29:46 your computer crashed or a problem was reported
crash dump file: C:\Windows\MEMORY.DMP
This was probably caused by the following module: hardware.sys (hardware)
Bugcheck code: 0x3B (0xC000001D, 0xFFFFB022314BB937, 0xFFFF860AA5743F20, 0x0)
Error: SYSTEM_SERVICE_EXCEPTION
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.
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 SYSTEM_SERVICE_EXCEPTION



On Thu 2019-10-17 09:36:39 your computer crashed or a problem was reported
crash dump file: C:\Windows\Minidump\101719-5843-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x1C1220)
Bugcheck code: 0xBE (0xFFFFA50004871200, 0x8A00000003D00021, 0xFFFFFC8205733280, 0xA)
Error: ATTEMPTED_WRITE_TO_READONLY_MEMORY
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This is issued if a driver attempts to write to a read-only memory segment.
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 2019-10-16 17:34:36 your computer crashed or a problem was reported
crash dump file: C:\Windows\Minidump\101619-6484-01.dmp
This was probably caused by the following module: win32kfull.sys (0xFFFFBB6380E5C2AD)
Bugcheck code: 0x3B (0xC000001D, 0xFFFFBB6380E5C2AD, 0xFFFF928FF48BBEA0, 0x0)
Error: SYSTEM_SERVICE_EXCEPTION
file path: C:\Windows\system32\win32kfull.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: Full/Desktop Win32k Kernel Driver
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 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 Wed 2019-10-16 17:33:38 your computer crashed or a problem was reported
crash dump file: C:\Windows\Minidump\101619-6093-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x1C1220)
Bugcheck code: 0x1E (0xFFFFFFFFC0000005, 0x0, 0x8, 0x0)
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.



The following dump files were found but could not be read. These files may be corrupted:
C:\Windows\Minidump\102119-6203-01.dmp




--------------------------------------------------------------------------------
Conclusion
--------------------------------------------------------------------------------

6 crash dumps have been found and analyzed. Only 5 are included in this report. If dump files are found and they could not be analuzed, it means they are corrupted. Because crash dumps are an emergency measure it is not uncommon for this to happen, however often it points to a problem in the storage stack. It is suggested that you run CHKDSK on your system drive to check your drive for errors.
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.


* FRST.txt https://pjjoint.malekal.com/files.php?r ... 10c13d10y9

* Shortcut https://pjjoint.malekal.com/files.php?r ... h5b12f14l5

* Additionnal.txt https://pjjoint.malekal.com/files.php?r ... u11m9b14u5


Merci

[Malekal_morte]

Regarde si tu as un utilitaire HP Update
Lance pour effectuer des mises à jour de pilotes.

Sinon faire une mise à jour de pilotes avec driversCloud


Enfin :

• Vérifie la température de l'ordinateur.
• Vérifie l'état de santé des disques dur notamment avec Par exemple avec CrystalDiskInfo, voir si le statut est correct ou Prudence.

vérifie tes barrettes mémoire avec un memtest
Et si possible tester quelques heures avec une barrette à la fois.
Utilise bien memtest86+ et pas celui de Windows.

[alexandre.vachon]

Bonjour,

J'ai vérifier le SSD avec Crystal Disk, il est à 100% et en bon état. J'ai testé les 4 barrettes ensembles toute la nuit, et aussi une par une dans Memtest et aucune erreur. J'ai aussi essayer le logiciel Driver Cloud et tout mes drivers sont à jours selon le site. La température est aussi correct même en stress test (OCCT). Il n'a pas non plus de mises à jours HP, car le PC est vieux. Avez vous d'autres suggestions?

Merci!

[Malekal_morte]

bizarre.
répare Windows 10 Sans perte de données.
En espérant que cela aide