Écran noir / Crash potentiel de carte graphique

Merci pour ta réponse!

Est-ce que ça ressemble à quelque chose comme ça?

Ou ça plutôt : Welcome to WhoCrashed (HOME EDITION) v 7.06

WhoCrashed is a comprehensible crash dump analyzer. It analyzes the system crashes of your computer or a remote computer on the network.

If your computer has displayed a blue (or black) screen of death or rebooted suddenly then your system may have crashed because of a malfunctioning device driver or because of a hardware failure. WhoCrashed will go to great lengths to help you find the root cause of the problem and a solution if available. It will analyze the crash dump files on your system or a system on the network with the single click of a button. In case the problem is caused by a malfunctioning driver, it will tell you what drivers are likely to be responsible for crashing your computer. In case of a hardware failure, it will tell you the most likely root cause and how to fix the problem.

When the analysis process is complete, WhoCrashed will write a report that offers suggestions on how to proceed in any situation, including internet links which will help you further troubleshoot any detected problems.

WhoCrashed will do great efforts to find out why your system crashed and what can be done to remedy the problem.

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: MARVYNWindows version: Windows 11, 10.0, version 2009, build: 22631 (x64)Windows dir: C:\WINDOWSHardware: ASUSTeK COMPUTER INC., TUF Z390-PRO GAMINGCPU: GenuineIntel Intel(R) Core(TM) i5-9600K CPU @ 3.70GHz 8664, level: 6Processor count:6 logical processors, active mask: 63RAM: 32679,6MB

 

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 Wed 13/12/2023 21:38:23 your computer crashed or a problem was reported

Crash dump file: C:\WINDOWS\Minidump\121323-8906-01.dmp (Minidump) Bugcheck code: 0x116(0xFFFFCB86ABE43050, 0xFFFFF802A99D6730, 0xFFFFFFFFC000009A, 0x4)Bugcheck name:VIDEO_TDR_ERRORDriver or module in which error occurred: nvlddmkm.sys (nvlddmkm+0x10F6730)File path:nvlddmkm.sysDescription: NVIDIA Windows Kernel Mode Driver, Version 546.33 Product: NVIDIA Windows Kernel Mode Driver, Version 546.33 Company: NVIDIA CorporationBug check description:This indicates that an attempt to reset the display driver and recover from a timeout failed. Analysis:This is a video related crash. 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:
nvlddmkm.sys (NVIDIA Windows Kernel Mode Driver, Version 546.33 , NVIDIA Corporation). Google query:nvlddmkm NVIDIA Corporation VIDEO_TDR_ERROR



On Tue 12/12/2023 23:27:40 your computer crashed or a problem was reported

Crash dump file: C:\WINDOWS\Minidump\121223-10187-01.dmp (Minidump) Bugcheck code: 0x116(0xFFFFD606D1E7F010, 0xFFFFF80365CA6730, 0xFFFFFFFFC000009A, 0x4)Bugcheck name:VIDEO_TDR_ERRORDriver or module in which error occurred: nvlddmkm.sys (nvlddmkm+0x10F6730)File path:nvlddmkm.sysDescription: NVIDIA Windows Kernel Mode Driver, Version 546.33 Product: NVIDIA Windows Kernel Mode Driver, Version 546.33 Company: NVIDIA CorporationBug check description:This indicates that an attempt to reset the display driver and recover from a timeout failed. Analysis:This is a video related crash. 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:
nvlddmkm.sys (NVIDIA Windows Kernel Mode Driver, Version 546.33 , NVIDIA Corporation). Google query:nvlddmkm NVIDIA Corporation VIDEO_TDR_ERROR



On Sat 04/11/2023 22:50:15 your computer crashed or a problem was reported

Crash dump file: C:\WINDOWS\Minidump\110423-7359-01.dmp (Minidump) Bugcheck code: 0x124(0x0, 0xFFFFBB09051CE028, 0xB2000000, 0x30005)Bugcheck name:WHEA_UNCORRECTABLE_ERRORDriver or module in which error occurred: genuineintel.sys (genuineintel)Bug check description:A fatal hardware error has occurred. This bug check uses the error data that is provided by the Windows Hardware Error Architecture (WHEA). This bug check is typically related to physical hardware failures. It can be heat related, defective hardware, memory or even a processor that is beginning to fail or has failed. Analysis:
Google query:genuineintel WHEA_UNCORRECTABLE_ERROR



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

 

Conclusion

4 crash dumps have been found and analyzed. Only 3 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.
2 third party drivers have 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:

nvlddmkm.sys (NVIDIA Windows Kernel Mode Driver, Version 546.33 , NVIDIA Corporation)
genuineintel.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:06 (h:mm:ss).
 

Re

c'est ce  que > l'on a fait < mais cette fois tu le feras en manuel

_ tu vas lancer une recherche sur > touslesdrivers < _ tu auras un petit fichier à télécharger et à exécuter https://fichiers2.touslesdrivers.com/Mes_Drivers_3.0.4.exe

_ tu prendras l'option des drivers releasés , pour ne pas avoir les versions béta ( en cours de test ) , et télécharger le fichier proposé

_ démarrer en > mode sans échec < normalement touche F8 au démarrge

_ dans le gestionnaire des périphériques , tu désinstalles la carte graphique , et tu exécuteras le fichier que tu as téléchargé ( en manuel )

_et tu redémarres le PC deux fois

> je regarde d' autres solutions

@+

Voilà ce que HWmonitor me donne.

Par contre, je n'ai pas "Diagnostiquer les problèmes de mémoire". Peut-être que sur Windows 11 c'est autre chose?

Ok non, sûr mon ordinateur ça s'appelle "Diagnostic de mémoire Windows", et je l'ai déjà effectué hier.

J'ai complètement désintallé Microsoft Game Input de mon pc. Mais les crashs sont toujours là, même sans jeux.

Maintenant, les erreurs qui sortent dans l'observateur avant le crash sont, dans l'ordre : 

- Le serveur {8CFC164F-4BE5-4FDD-94E9-E2AF73ED4A19} ne s’est pas enregistré sur DCOM avant la fin du temps imparti.

- Les paramètres d’autorisation propres à l’application n’accordent pas l’autorisation Local Exécution pour l’application serveur COM avec le CLSID 
Windows.SecurityCenter.WscDataProtection
 et l’APPID 
Non disponible
 au SID AUTORITE NT\Système de l’utilisateur (S-1-5-18) depuis l’adresse LocalHost (avec LRPC) s’exécutant dans le SID Non disponible du conteneur d’applications (Non disponible). Cette autorisation de sécurité peut être modifiée à l’aide de l’outil d’administration Services de composants.

- Les paramètres d’autorisation propres à l’application n’accordent pas l’autorisation Local Activation pour l’application serveur COM avec le CLSID 
{2593F8B9-4EAF-457C-B68A-50F6B8EA6B54}
 et l’APPID 
{15C20B67-12E7-4BB6-92BB-7AFF07997402}
 au SID MARVYN\marvy de l’utilisateur (S-1-5-21-1653857834-4075970821-4077178306-1001) depuis l’adresse LocalHost (avec LRPC) s’exécutant dans le SID Non disponible du conteneur d’applications (Non disponible). Cette autorisation de sécurité peut être modifiée à l’aide de l’outil d’administration Services de composants.

- Le disque 2 a été enlevé de manière inattendue.

Et puis ça crash.

j'ai un Windows 10 , je ne me rappelle plus si j'avais installé > Memtest <

tu fais tes captures d'écran trop grande li faut réduire la fenêtre ; ce qui est utile c'est 20% de la capture

en plus tu as un 24/25" ; et moi j'ai un 22" (1920x1080)

il faut rogner la capture

fenêtre pour le diagnostique Windows de la RAM => pour le poste <23>

prendre la 1ère option