[Résolu] Écran bleu suite à la migration de Windows 7 vers Windows 10

[Tonton]

Probablement un problème de driver.

Ouvre le Gestionnaire de périphériques et vérifie s'il y a présence de ? ou de !.

[DelphineS]

et bien non aucun ? ou ! dans les pilotes 🤨

[Tonton]

Pour bien faire, il faudrait télécharger les drivers nécessaires à partir du site ASUS, mais ton PC datant quelque peu, les drivers proposés ne le sont que pour Vista ou Windows 7.

Nous allons donc chercher la liste des drivers à mettre à jour sur DriversCloud :

• Crée un point de restauration système
• Rends-toi sur le site de DriversCloud.com
• Clique sur Installation de l'Agent (à désinstaller en fin de manip)
• Ensuite tu peux Démarrer la détection
• Tu peux t'aider de ce tuto-ci et de ce tuto-là

             Poste la liste des drivers qui te sont proposés pour chacun des composants

• Voici un exemple de liste demandée :

• 

• Après vérification, nous installerons les pilotes nécessaires, en ne choisissant que ceux dont le niveau de pertinence est le plus élevé

[DelphineS]

il y a 31 minutes, DelphineS a dit :

et bien non aucun ? ou ! dans les pilotes 🤨

Non non aucun §

J'ai cliqué meme sur chaque driver mais j'ai un message disant que c'est à jour.

Je vais devoir me deconnecter car je dois m'occuper aussi du reste de la famille lol. je reviens faire ta procedure demain matin.

Je te souhaite une très bonne soirée et merci encore

[DelphineS]

Bonjour Tonton,

Après plusieurs tentatives hier, voilà ce que j'obtiens :

[DelphineS]

J'ai voulu faire la mise à jour de ce pilote mais voilà :

[DelphineS]

J'ai utilisé la recherche de plantage et voici quelques rapporets si cela peut aider...

[DelphineS]

C'est encore moi

Pour le coup j'ai fait des mises à jour sur le 2ième ordi (petit portable asus utilisé très occasionnellement par ma fille) et il y a également des soucis de mises à jour de pilotes.

Notamment le Intel Corporation Atom Processor Z36xxx/Z37xxx Series Trusted Execution Engine qui est siganlé par driverscloud comme étant mal installé + d'autres.

Penses tu que je peux ouvrir un autre sujet de demande d'aide ?

[Tonton]

Bonjour DelphineS,

Il y a 3 heures, DelphineS a dit :

J'ai voulu faire la mise à jour de ce pilote

Comme indiqué, j'aurais préféré que tu me communiques la liste exhaustive des drivers proposés et que je t'indique ceux qu'il convient d'installer (niveau de pertinence le plus élevé). Ce n'est pas bien grave : nous allons vérifier la cause de ces crashes plus en profondeur (voir ci-dessous)

Il y a 2 heures, DelphineS a dit :

J'ai utilisé la recherche de plantage et voici quelques rapports si cela peut aider

Nous allons utiliser l'outil WhoCrashed, qui va nous permettre d’identifier avec précision la raison de ces plantages; voici les manips à effectuer :

• Rends-toi dans Panneau de configuration > Système > Paramètres système avancés > Démarrage et Récupération > Paramètres :
  1. 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
• 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
   

il y a 45 minutes, DelphineS a dit :

Penses tu que je peux ouvrir un autre sujet de demande d'aide ?

Oui, il est préférable d'ouvrir un nouveau sujet, dédié à cet autre PC

@+

[DelphineS]

Bonjour Tonton,

 

Tu as raison je n'aurais pas du tenter de faire moi même la mise à jour mais vu qu'il n y avait qu'un seul pilote de notifié, j'ai voulu t’épargner l’écriture d'un message... toutes mes excuses. 😚

 

Pour info , Image memoire du noyau était déjà selectionné.

Voici le rapport de whocrash :

System Information (local)

---

Computer name: MAMINOUCHE
Windows version: Windows 10, 10.0, version 2009, build: 19043
Windows dir: C:\WINDOWS
Hardware: K70IJ , ASUSTeK Computer Inc. , K70IJ
CPU: GenuineIntel Pentium(R) Dual-Core CPU T4400 @ 2.20GHz 8664, level: 6
2 logical processors, active mask: 3
RAM: 4258353152 bytes (4,0GB)


 

---

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 Sat 14/08/2021 08:27:51 your computer crashed or a problem was reported
crash dump file: C:\WINDOWS\Minidump\081421-382250-01.dmp
This was probably caused by the following module: ntfs.sys (0xFFFFF80081343D28)
Bugcheck code: 0x1000007E (0xFFFFFFFFC0000005, 0xFFFFF80081343D28, 0xFFFFF9034D5414B8, 0xFFFFF9034D540CF0)
Error: SYSTEM_THREAD_EXCEPTION_NOT_HANDLED_M
file path: C:\WINDOWS\system32\drivers\ntfs.sys
product: Système d’exploitation Microsoft® Windows®
company: Microsoft Corporation
description: Pilote du système de fichiers NT
Bug check description: This indicates that a system thread generated an exception which the error handler did not catch.
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 file system driver. Since there is no other responsible driver detected, this could be pointing to a malfunctioning drive or corrupted disk. It's suggested that you run CHKDSK.



On Fri 13/08/2021 12:09:05 your computer crashed or a problem was reported
crash dump file: C:\WINDOWS\Minidump\081321-353468-01.dmp
This was probably caused by the following module: ntfs.sys (0xFFFFF8015E343D28)
Bugcheck code: 0x3B (0xC0000005, 0xFFFFF8015E343D28, 0xFFFF8187F8659000, 0x0)
Error: SYSTEM_SERVICE_EXCEPTION
file path: C:\WINDOWS\system32\drivers\ntfs.sys
product: Système d’exploitation Microsoft® Windows®
company: Microsoft Corporation
description: Pilote du système de fichiers NT
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 file system driver. Since there is no other responsible driver detected, this could be pointing to a malfunctioning drive or corrupted disk. It's suggested that you run CHKDSK.



On Fri 13/08/2021 10:22:53 your computer crashed or a problem was reported
crash dump file: C:\WINDOWS\Minidump\081321-318671-01.dmp
This was probably caused by the following module: ntfs.sys (0xFFFFF8070B343D28)
Bugcheck code: 0x3B (0xC0000005, 0xFFFFF8070B343D28, 0xFFFF8181EA91CF90, 0x0)
Error: SYSTEM_SERVICE_EXCEPTION
file path: C:\WINDOWS\system32\drivers\ntfs.sys
product: Système d’exploitation Microsoft® Windows®
company: Microsoft Corporation
description: Pilote du système de fichiers NT
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 file system driver. Since there is no other responsible driver detected, this could be pointing to a malfunctioning drive or corrupted disk. It's suggested that you run CHKDSK.



On Fri 13/08/2021 10:07:14 your computer crashed or a problem was reported
crash dump file: C:\WINDOWS\Minidump\081321-309562-01.dmp
This was probably caused by the following module: ntfs.sys (0xFFFFF80070758AC2)
Bugcheck code: 0x3B (0xC0000005, 0xFFFFF80070758AC2, 0xFFFFBB87F5FD38A0, 0x0)
Error: SYSTEM_SERVICE_EXCEPTION
file path: C:\WINDOWS\system32\drivers\ntfs.sys
product: Système d’exploitation Microsoft® Windows®
company: Microsoft Corporation
description: Pilote du système de fichiers NT
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 file system driver. Since there is no other responsible driver detected, this could be pointing to a malfunctioning drive or corrupted disk. It's suggested that you run CHKDSK.



On Fri 13/08/2021 09:55:08 your computer crashed or a problem was reported
crash dump file: C:\WINDOWS\Minidump\081321-312953-01.dmp
This was probably caused by the following module: ntfs.sys (0xFFFFF8006AF43D28)
Bugcheck code: 0x3B (0xC0000005, 0xFFFFF8006AF43D28, 0xFFFFF48E57E27E80, 0x0)
Error: SYSTEM_SERVICE_EXCEPTION
file path: C:\WINDOWS\system32\drivers\ntfs.sys
product: Système d’exploitation Microsoft® Windows®
company: Microsoft Corporation
description: Pilote du système de fichiers NT
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 file system driver. Since there is no other responsible driver detected, this could be pointing to a malfunctioning drive or corrupted disk. It's suggested that you run CHKDSK.



On Fri 13/08/2021 09:37:20 your computer crashed or a problem was reported
crash dump file: C:\WINDOWS\Minidump\081321-338968-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x3F71D0)
Bugcheck code: 0x139 (0x1D, 0xFFFFED83A4DC5E00, 0xFFFFED83A4DC5D58, 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 Fri 13/08/2021 09:00:55 your computer crashed or a problem was reported
crash dump file: C:\WINDOWS\Minidump\081321-451359-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x3F71D0)
Bugcheck code: 0x1000007E (0xFFFFFFFFC0000005, 0xFFFFF80264D307C9, 0xFFFF870F4AD46188, 0xFFFF870F4AD459C0)
Error: SYSTEM_THREAD_EXCEPTION_NOT_HANDLED_M
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 system thread generated an exception which the error handler did not catch.
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 Fri 13/08/2021 08:27:41 your computer crashed or a problem was reported
crash dump file: C:\WINDOWS\Minidump\081321-350546-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x3F71D0)
Bugcheck code: 0x1000007E (0xFFFFFFFFC0000005, 0xFFFFF80184D307C9, 0xFFFFEB87E01A8188, 0xFFFFEB87E01A79C0)
Error: SYSTEM_THREAD_EXCEPTION_NOT_HANDLED_M
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 system thread generated an exception which the error handler did not catch.
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 Fri 13/08/2021 06:45:01 your computer crashed or a problem was reported
crash dump file: C:\WINDOWS\Minidump\081321-509109-01.dmp
This was probably caused by the following module: ntfs.sys (0xFFFFF80625B43D28)
Bugcheck code: 0x1000007E (0xFFFFFFFFC0000005, 0xFFFFF80625B43D28, 0xFFFF9D02AE1C5068, 0xFFFF9D02AE1C48A0)
Error: SYSTEM_THREAD_EXCEPTION_NOT_HANDLED_M
file path: C:\WINDOWS\system32\drivers\ntfs.sys
product: Système d’exploitation Microsoft® Windows®
company: Microsoft Corporation
description: Pilote du système de fichiers NT
Bug check description: This indicates that a system thread generated an exception which the error handler did not catch.
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 file system driver. Since there is no other responsible driver detected, this could be pointing to a malfunctioning drive or corrupted disk. It's suggested that you run CHKDSK.



The following dump files were found but could not be read. These files may be corrupted:
C:\WINDOWS\Minidump\081221-522250-01.dmp


 

---

Conclusion

---

On your computer a total of 29 crash dumps have been found. Only 10 have been analyzed. Only 9 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.
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.

 

Modifié le 14 août 2021 par DelphineS