Écran bleu (BSOD) - Critical Process Died

[stigma]

Bonjour,

Hier j'ai eu 3 ou  4 ecrans bleus qui se produisaient après plusieurs minutes (c'est la 1ere fois que ça arrive)

J'ai lancé un Who Crashed et voilà ce que ça a donné. Le lien pour les pilots donne une erreur 400

Merci

Citation

3 crash dumps have been found and analyzed. Only 2 are included in this report. If one or more dump files were found that could not be analyzed, it means they are corrupted. It's an emergency measure for the system to write out a crash dump file and because of this, it's not uncommon for this process to fail. Often, but not always, it points to a problem in the storage stack. For instance, if the disk that should write out the crash dump file has failed, there will be no crash dump file written out. 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:

fffff803`5b3b5776 : 00000000`00000000 00000000`0000000e 00000000`005c5eae fffff803`5dc74b10 : nt.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.
 

 

[Tonton]

Bonjour @stigma,

Il faudrait un rapport WhoCrashed complet.

  Voici comment procéder (les paramétrages à effectuer avant de lancer WhoCrashed sont importants) :

• Saisis Panneau de configuration dans la Barre de recherche (située à côté du bouton Démarrer) > clique sur Panneau de configuration > Système > Paramètres avancés du système > sous Démarrage et Récupération, clique sur Paramètres :
  1. Vérifie que Vidage mémoire automatique soit sélectionné, sinon il n'y aura pas de minidump (sous Windows 10 et Windows 11, cette sélection s'effectue via le menu déroulant situé sous Écriture des informations de débogage)
  2. Redémarrer automatiquement doit être décoché, ce qui te permettra de lire les informations relatives aux BSOD
• Télécharge WhoCrashed Free de Resplendence et enregistre-le sur le Bureau
• Pour l'installer, clique droit sur l'icône whocrashedSetup et choisis Exécuter en tant qu'administrateur
• Coche la case Create a desktop icon
• Pour le lancer, clique droit sur l'icône WhoCrashed et choisis Exécuter en tant qu'administrateur
• Clique sur Analyze :

• Lorsque le scan est terminé, le message suivant apparaît : Please scroll down the information window to read the report
• Valide par OK
• Clique sur l'onglet Report afin d'ouvrir le rapport généré suite au scan

  Copie-colle l'intégralité de ce rapport dans ta prochaine réponse ; il est constitué des rubriques suivantes :

• System Information (local)
• Crash Dump Analysis
• Conclusion

• Règle à nouveau les paramètres "1" et "2" sur leur valeur initiale

[stigma]

Citation

Crash Dump Analysis

---

Crash dumps are enabled on your computer.

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

On Thu 29/02/2024 11:30:18 your computer crashed or a problem was reported

 

 

Crash dump file:	C:\WINDOWS\Minidump\022924-15906-01.dmp (Minidump)
Bugcheck code:	0x1000009F(0x4, 0x12C, 0xFFFF800186FA9600, 0xFFFFF8035DC74880)
Bugcheck name:	CUSTOM_ERROR
Analysis:

On Thu 29/02/2024 11:30:18 your computer crashed or a problem was reported

 

 

Crash dump file:	C:\WINDOWS\MEMORY.DMP (Kernel memory dump)
Bugcheck code:	0x9F(0x4, 0x12C, 0xFFFF800186FA9600, 0xFFFFF8035DC74880)
Bugcheck name:	DRIVER_POWER_STATE_FAILURE
Driver or module in which error occurred:	fffff803`5b3b5776 : 00000000`00000000 00000000`0000000e 00000000`005c5eae fffff803`5dc74b10 : nt.sys (fffff803`5b3b5776 : 00000000`00000000 00000000`0000000e 00000000`005c5eae fffff803`5dc74b10 : nt!IoTranslateBusAddress+0xb16)
Bug check description:	This bug check indicates that the driver is in an inconsistent or invalid power state.
Analysis:	The power state transition timed out waiting to synchronize with the PnP subsystem. This is likely caused by a hardware problem, but there is a possibility that this is caused by a misbehaving driver. This bugcheck indicates that a timeout has occurred. This may be caused by a hardware failure such as a thermal issue or a bug in a driver for a hardware device. Read this article on thermal issues A full memory dump will likely provide more useful information on the cause of this particular bugcheck.
Google query:	fffff803`5b3b5776 : 00000000`00000000 00000000`0000000e 00000000`005c5eae fffff803`5dc74b10 : nt DRIVER_POWER_STATE_FAILURE

The following dump file was found but appeared to be corrupt: C:\WINDOWS\LiveKernelReports\WATCHDOG-20240926-1333.dmp

 

 

 

---

Conclusion

---

3 crash dumps have been found and analyzed. Only 2 are included in this report. If one or more dump files were found that could not be analyzed, it means they are corrupted. It's an emergency measure for the system to write out a crash dump file and because of this, it's not uncommon for this process to fail. Often, but not always, it points to a problem in the storage stack. For instance, if the disk that should write out the crash dump file has failed, there will be no crash dump file written out. 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:

fffff803`5b3b5776 : 00000000`00000000 00000000`0000000e 00000000`005c5eae fffff803`5dc74b10 : nt.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 suggestions displayed in the bugcheck analysis above.

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.
The analysis process took 0:00:07 (h:mm:ss).
 

 

[Tonton]

OK, merci.
S'il s'agit d'un PC de marque, peux-tu me communiquer la marque et le modèle (référence complète), stp ?
S'il s'agit d'un PC monté, merci de me communiquer les marques et références des principaux composants : carte-mère, carte graphique, carte son et CPU.