[Résolu] Écran bleu de la mort (BSOD)

[prj107]

bonjour

aujourd hui j ai eu deux fois des ecran bleu de la mort 

je ne sais pas a quoi cela est du pouvez vous m aider svp

cordialement 

[Tonton]

Bonsoir prj107,

La cause probable est un driver de la carte graphique qui n'est pas à jour.

  On va vérifier :

1. Rends-toi dans Panneau de configuration > Système > Paramètres système avancés > Démarrage et Récupération > Paramètres > vérifie que Image mémoire du noyau soit sélectionnée, sinon il n'y aura pas de minidump (sous Windows 10, 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

3. Télécharge WhoCrashed Free de Resplendence et enregistre-le sur le Bureau :

4. Pour l'installer, clique droit sur l'icône whocrashedSetup et choisis Exécuter en tant qu'administrateur

5. Coche la case Create a desktop icon

6. Pour le lancer, clique droit sur l'icône WhoCrashed et choisis Exécuter en tant qu'administrateur

7. Clique sur Analyze :

8. Lorsque le scan est terminé, le message suivant apparaît : Please scroll down the information window to read the report

9. Valide par OK

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

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

@+

[prj107]

ok merci je vais essayer je te dirai si  ca fonctionne

[prj107]

voici le rapport demandé

dsl je n'ai pas trouve l,onglet reprt

 

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-JDUTS5E6
Windows version: Windows 10, 10.0, version 2009, build: 19042
Windows dir: C:\WINDOWS
Hardware: ASUS TUF Gaming A17 FA706IU_TUF766IU, ASUSTeK COMPUTER INC., FA706IU
CPU: AuthenticAMD AMD Ryzen 7 4800H with Radeon Graphics 8664, level: 23
16 logical processors, active mask: 65535
RAM: 16556597248 bytes (15,4GB)
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 07/04/2021 19:32:04 your computer crashed or a problem was reported
crash dump file: C:\WINDOWS\Minidump\040721-9687-01.dmp
This was probably caused by the following module: dxgkrnl.sys (0xFFFFF8063F42430B)
Bugcheck code: 0xD1 (0x0, 0xFF, 0x0, 0xFFFFF8063F42430B)
Error: DRIVER_IRQL_NOT_LESS_OR_EQUAL
file path: C:\WINDOWS\system32\drivers\dxgkrnl.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: DirectX Graphics Kernel
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 Wed 07/04/2021 19:32:04 your computer crashed or a problem was reported
crash dump file: C:\WINDOWS\MEMORY.DMP
This was probably caused by the following module: dxgkrnl.sys (0xFFFFF8063F42430B)
Bugcheck code: 0xD1 (0x0, 0xFF, 0x0, 0xFFFFF8063F42430B)
Error: DRIVER_IRQL_NOT_LESS_OR_EQUAL
file path: C:\WINDOWS\system32\drivers\dxgkrnl.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: DirectX Graphics Kernel
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 Wed 07/04/2021 19:17:55 your computer crashed or a problem was reported
crash dump file: C:\WINDOWS\Minidump\040721-9562-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x3F5DB0)
Bugcheck code: 0x1E (0xFFFFFFFFC0000005, 0xFFFFF80729F2B349, 0x0, 0x100)
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 Tue 06/04/2021 18:30:38 your computer crashed or a problem was reported
crash dump file: C:\WINDOWS\Minidump\040621-9093-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x3F5DB0)
Bugcheck code: 0x139 (0x21, 0xFFFFCE04DC4DF510, 0xFFFFCE04DC4DF468, 0x0)
Error: KERNEL_SECURITY_CHECK_FAILURE
file path: C:\WINDOWS\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: The kernel has detected the corruption of a critical data structure.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be
identified at this time.
On Sat 03/04/2021 15:44:02 your computer crashed or a problem was reported
crash dump file: C:\WINDOWS\Minidump\040321-9718-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x3F5DB0)
Bugcheck code: 0x1E (0xFFFFFFFFC000001D, 0xFFFFF8067407363B, 0xFFFFAD00105A4440, 0xFFFFAD0010599180)
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 Mon 22/03/2021 18:33:17 your computer crashed or a problem was reported
crash dump file: C:\WINDOWS\Minidump\032221-9625-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x3F5C50)
Bugcheck code: 0xA (0xFFFF9086B4F46440, 0x2, 0x0, 0xFFFFF8021CE4AE2F)
Error: 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 Microsoft Windows or a kernel-mode driver accessed paged memory at
DISPATCH_LEVEL or above. This is a software bug.
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
6 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.
 

 

[Tonton]

Bonjour prj107,

Les codes erreur remontés par WhoCrashed concernent 2 points :
- les pilotes graphiques
- d'éventuels problèmes de matériel

  Commençons par les drivers graphiques :

1. Rends-toi sur le site officiel ASUS (modéle de ton PC : ASUS TUF Gaming A17 (TUF706/TUF766 => cf. ton autre sujet en cours)
2. Télécharge le driver graphique proposé sur ton Bureau :

3. Désinstalle le driver graphique actuellement en place via le Gestionnaire de périphériques 
4. Redémarre ton PC
5. Installe le driver proposé par ASUS
6. Redémarre ton PC + retour d'info sur le comportement de ton PC

[prj107]

j ai installé le pilote graphique demandé  et Windows update m'a proposé une mise a jour 

NVIDIA - Display - 27.21.1.14.5763

je fais quoi ? 

 

[Tonton]

Installe-le.

[prj107]

ok je l ai installer 

ci desous vous trouverez le rapport d aujourd hui 

cordialement 

[prj107]

*et j ai eu un ecran bleu 

cordialement 

[Tonton]

Bonjour @prj107

La piste des drivers ayant été écartée, on va traiter la partie "matériel".

Mais avant, je souhaiterais que tu effectues les manips ci-dessous, stp :

1. Dism

• Clique droit sur Démarrer, puis sur  Windows PowerShell (admin)
• Copie-colle la commande suivante : Dism /Online /Cleanup-Image /RestoreHealth et valide avec la touche Entrée
• Le message suivant devrait apparaître : « La restauration a été effectuée. L’opération a réussi »
• Ferme l'invite de commande en tapant Exit et valide avec Entrée
• Redémarre ton PC

2. sfc /scannow

• À nouveau, clique droit sur Démarrer, puis sur  Windows PowerShell (admin)
• Copie-colle la commande suivante : sfc /scannow, valide avec la touche Entrée et patiente jusqu'à l'étape suivante
• 2 possibilités vont se présenter :
  • si le message suivant apparaît : « Le programme de protection des ressources Windows n'a trouvé aucune violation d'intégrité », cela signifie qu'aucun problème n'a été trouvé,
  • si ce message n'apparaît pas, cela signifie que des problèmes ont été détectés et/ou réparés ; nous procèderons alors aux vérifications correspondantes
• Ferme l'invite de commande en tapant Exit et valide avec Entrée
• Redémarre ton PC

Dans les 2 cas, merci de m'indiquer le message qui est apparu à la suite de la manip indiquée.

@+