Ecran bleu fréquents sur mon PC

[doudou75]

Mon pc ne cesse de faire des plantages, arrêts soudain, repart, ou parfois ecran bleu...
j ai essayé pas mal de solutions proposées par votre site, mais cela continue

Que faire?

Merci

[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.
→ WhoCrashed : analyser les écrans bleus, BSOD ou code d’arrêt
Fais un copier/coller du contenu ici comme indiqué dans le tuto.


Faire le test central et donner en retour le lien qui figurera dans le navigateur
https://www.malekal.com/userdiag-diagno ... rdinateur/

---

3°) FRST
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.
Tu peux aussi attacher les fichiers de rapports FRST dans une nouvelle réponse avec l'éditeur avancé.



Ensuite en bas pièce-jointe.



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

NOTE : tu peux aussi envoyer les rapports sur https://pjjoint.malekal.com et donner les liens en retour.

[doudou75]

re bonjour
j avais deja utilisé whocrashed sans trop savoir quoi faire des résultats d analyse. J espere que vous y verrez plus clair!!

Par ailleurs, j ajoute aux ennuis que j eprouve, le fait que mon pc freeze!!

merci d avance

[Malekal_morte]

Il manque le résultat de WhoCrashed.

[doudou75]

bonjour
voici le rapport

Code : Tout sélectionner

--------------------------------------------------------------------------------
Welcome to WhoCrashed (Home Edition) v 6.70
--------------------------------------------------------------------------------

This program checks for drivers which have been crashing your computer. If your computer has displayed a blue (or black) screen of death, suddenly rebooted or shut down then this program might help you find the root cause of the problem and a solution. 

Whenever a computer suddenly reboots without displaying any notice or blue (or black) screen of death, the first thing that is often thought about is a hardware failure. In reality, on Windows a lot of system crashes are caused by malfunctioning device drivers and kernel modules. In case of a kernel error, many computers do not show a blue or black screen unless they are configured for this. Instead these systems suddenly reboot without any notice. 

This program will analyze your crash dumps with the single click of a button. It will tell you what drivers are likely to be responsible for crashing your computer. It will report a conclusion which offers suggestions on how to proceed in any situation while the analysis report will display internet links which will help you further troubleshoot any detected problems. 

To obtain technical support visit www.resplendence.com/support

Click here to check if you have the latest version or if an update is available. 

Just click the Analyze button for a comprehensible report ...



--------------------------------------------------------------------------------
Home Edition Notice
--------------------------------------------------------------------------------

This version of WhoCrashed is free for use at home only. If you would like to use this software at work or in a commercial environment you should get the professional edition of WhoCrashed which allows you to perform more thorough and detailed analysis. It also offers a range of additional features such as remote analysis on remote directories and remote computers on the network. 

Please note that this version of WhoCrashed is not licensed for use by professional support engineers.

Click here for more information on the professional edition.
Click here to buy the the professional edition of WhoCrashed.


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

Computer name: LAPTOP-RSG00GCE
Windows version: Windows 10, 10.0, version 2009, build: 22631
Windows dir: C:\WINDOWS
Hardware: TUF Gaming FX505DU, ASUSTeK COMPUTER INC., FX505DU
CPU: AuthenticAMD AMD Ryzen 7 3750H with Radeon Vega Mobile Gfx 8664, level: 23
8 logical processors, active mask: 255
RAM: 16974405632 bytes (15,8GB)




--------------------------------------------------------------------------------
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 Thu 11/01/2024 11:25:45 your computer crashed or a problem was reported
crash dump file: C:\WINDOWS\Minidump\011124-21500-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x416B00) 
Bugcheck code: 0xD1 (0xFFFFF80300969B37, 0xFF, 0x87, 0xFFFFF80300969B37)
Error: DRIVER_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 a kernel-mode driver attempted to access pageable memory at a process IRQL that was too high. 
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 Thu 11/01/2024 08:36:36 your computer crashed or a problem was reported
crash dump file: C:\WINDOWS\Minidump\011124-16187-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x416B00) 
Bugcheck code: 0xD1 (0xFFFFF80000C49B37, 0xFF, 0x0, 0xFFFFF80000C49B37)
Error: DRIVER_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 a kernel-mode driver attempted to access pageable memory at a process IRQL that was too high. 
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
--------------------------------------------------------------------------------

2 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.

[Malekal_morte]

ok maintenant, il manque userdiag.
Vu qu'il y avait trois choses à faire.

[doudou75]

re bonjour
Voici le lien du rapport
j espere que c 'est ce qui est demandé
cordialement

https://userdiag.com/id/vnhMSO8kEi

[Malekal_morte]

Donc Windows 11.

Désinstalle, cela :

CCleaner
MEGAsync

Mets à jour tes pilotes avec driversCloud

[doudou75]

bonsoir
Merci bien
j ai effectué vos recommandations

Je reviens vers vous si besoin

En vous remerciant beaucoup
cordialement

[Malekal_morte]

Oui vois si les BSOD persistent.

[doudou75]

bonjour

Code : Tout sélectionner

--------------------------------------------------------------------------------
Welcome to WhoCrashed (Home Edition) v 6.70
--------------------------------------------------------------------------------

This program checks for drivers which have been crashing your computer. If your computer has displayed a blue (or black) screen of death, suddenly rebooted or shut down then this program might help you find the root cause of the problem and a solution. 

Whenever a computer suddenly reboots without displaying any notice or blue (or black) screen of death, the first thing that is often thought about is a hardware failure. In reality, on Windows a lot of system crashes are caused by malfunctioning device drivers and kernel modules. In case of a kernel error, many computers do not show a blue or black screen unless they are configured for this. Instead these systems suddenly reboot without any notice. 

This program will analyze your crash dumps with the single click of a button. It will tell you what drivers are likely to be responsible for crashing your computer. It will report a conclusion which offers suggestions on how to proceed in any situation while the analysis report will display internet links which will help you further troubleshoot any detected problems. 

To obtain technical support visit www.resplendence.com/support

Click here to check if you have the latest version or if an update is available. 

Just click the Analyze button for a comprehensible report ...



--------------------------------------------------------------------------------
Home Edition Notice
--------------------------------------------------------------------------------

This version of WhoCrashed is free for use at home only. If you would like to use this software at work or in a commercial environment you should get the professional edition of WhoCrashed which allows you to perform more thorough and detailed analysis. It also offers a range of additional features such as remote analysis on remote directories and remote computers on the network. 

Please note that this version of WhoCrashed is not licensed for use by professional support engineers.

Click here for more information on the professional edition.
Click here to buy the the professional edition of WhoCrashed.


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

Computer name: LAPTOP-RSG00GCE
Windows version: Windows 10, 10.0, version 2009, build: 22631
Windows dir: C:\WINDOWS
Hardware: TUF Gaming FX505DU, ASUSTeK COMPUTER INC., FX505DU
CPU: AuthenticAMD AMD Ryzen 7 3750H with Radeon Vega Mobile Gfx 8664, level: 23
8 logical processors, active mask: 255
RAM: 16974405632 bytes (15,8GB)




--------------------------------------------------------------------------------
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 Thu 11/01/2024 20:21:35 your computer crashed or a problem was reported
crash dump file: C:\WINDOWS\Minidump\011124-18390-01.dmp
This was probably caused by the following module: amdppm.sys (0xFFFFF80397153DCA) 
Bugcheck code: 0x1E (0xFFFFFFFF80000003, 0xFFFFF80397153DCA, 0x0, 0xFFFFD5013D35EAA8)
Error: KMODE_EXCEPTION_NOT_HANDLED
file path: C:\WINDOWS\system32\drivers\amdppm.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: Processor Device Driver
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 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 Thu 11/01/2024 16:20:14 your computer crashed or a problem was reported
crash dump file: C:\WINDOWS\Minidump\011124-22140-01.dmp
This was probably caused by the following module: amdppm.sys (0xFFFFF8019C343DCA) 
Bugcheck code: 0xD1 (0x0, 0xFF, 0x0, 0xFFFFF8019C343DCA)
Error: DRIVER_IRQL_NOT_LESS_OR_EQUAL
file path: C:\WINDOWS\system32\drivers\amdppm.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: Processor Device Driver
Bug check description: This indicates that a kernel-mode driver attempted to access pageable memory at a process IRQL that was too high. 
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 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 Thu 11/01/2024 16:10:48 your computer crashed or a problem was reported
crash dump file: C:\WINDOWS\Minidump\011124-22515-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x416B00) 
Bugcheck code: 0xD1 (0x0, 0x2, 0x8, 0x0)
Error: DRIVER_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 a kernel-mode driver attempted to access pageable memory at a process IRQL that was too high. 
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 Thu 11/01/2024 14:54:30 your computer crashed or a problem was reported
crash dump file: C:\WINDOWS\Minidump\011124-22265-01.dmp
This was probably caused by the following module: amdppm.sys (0xFFFFF806778C3E63) 
Bugcheck code: 0xD1 (0x58, 0xFF, 0x0, 0xFFFFF806778C3E63)
Error: DRIVER_IRQL_NOT_LESS_OR_EQUAL
file path: C:\WINDOWS\system32\drivers\amdppm.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: Processor Device Driver
Bug check description: This indicates that a kernel-mode driver attempted to access pageable memory at a process IRQL that was too high. 
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 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 Thu 11/01/2024 11:25:45 your computer crashed or a problem was reported
crash dump file: C:\WINDOWS\Minidump\011124-21500-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x416B00) 
Bugcheck code: 0xD1 (0xFFFFF80300969B37, 0xFF, 0x87, 0xFFFFF80300969B37)
Error: DRIVER_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 a kernel-mode driver attempted to access pageable memory at a process IRQL that was too high. 
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
--------------------------------------------------------------------------------

5 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. 

j ai encore ce souci ce matin, mon pc freeze soudainement...

[doudou75]

voici les rapport frst

[Malekal_morte]

file path: C:\WINDOWS\system32\drivers\amdppm.sys

C'est le pilote de la carte graphique AMD, dans ton cas AMD Radeon RX Vega 10 Graphics qui plante.

~~

Télécharge et installe HWInfo.
Vas dans les sensors et surveille les températures CPU, GPU et HDD durant l'utilisation de l'ordinateur.
Surveille les températures GPU et notamment de la carte graphique AMD.
Pour tout cela, voir : Le tutoriel HwInfo

~~

Fais un nettoyage des pilotes graphiques avec DDU, voir : DDU : Réinstaller proprement les pilotes de cartes graphiques avec Display Driver Uninstaller

Réinstalle :
NVIDIA Graphic Driver
AMD Graphics, Chipset and HDMI Driver
depuis ce lien : https://www.asus.com/us/laptops/for-gam ... 05DD-DT-DU
Sélectionne bien FX505DU depuis la liste.

[maletbien]

Bonsoir

Ayant moi même un BSOD j ai fait une recherche avec WhoCrahed avec le message suivant

C:\WINDOWS\MEMORY.DMP (Kernel memory dump)
Bugcheck code: 0x139(0x3, 0xFFFFD50D3740C340, 0xFFFFD50D3740C298, 0x0)
Bugcheck name: KERNEL_SECURITY_CHECK_FAILURE et SYSTEM_SERVICE_EXCEPTION avec les infos suivantes WUDFRd.sys (WUDFRd+0x4978)

j ai rechercher une solution sur la toile et j ai trouve un site qui me suggère de traficoter dans ma base de registres est ce bien raisonnable ??
le chemin étant
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\WMI\Autologger\EventLog-System\{b675ec37-bdb6-4648-bc92-f3fdc74d3ca2}

panneau droite changer la valeur dword de 1 a 0 close it and restart j hésite a le faire ?

Je pense que l erreur vient des barrettes mémoire qui pourtant semble bonne !
Mais ce qui m intrigue c est de chipoter dans la base de registre, ou j étais prêt a le faire mais est ce bien la bonne piste ?
Merci d avance de vos éventuelles réponses
JM

[Malekal_morte]

Salut,

Ce serait mieux de donner un rapport WhoCrashed : https://www.malekal.com/whocrashed-anal ... ode-arret/
Ainsi que les rapports FRST et userdiag. Voir première réponse de ce sujet : viewtopic.php?p=549678#p549678