Suite Mise a jour Wds 10 , nombreux BSOD

[jmd40]

Bonjour ,

sur mon pc (tour montée LDLC) sous Windows 10 , 64 bits , je rencontre pour la dernière mise a jour cumulative
(KB4501375) de nombreux écrans bleus (BSOD)
* KMODE EXCEPTION HANDLED
*MEMORY MANAGEMENT

J'ai 2 codes erreur : 0X80073712 pour la KB4501375

ainsi que 0X80070643 pour la Mise a jour Windows defender (KB2267602)

J'ai vérifié dans le gestionnaire de périphériques , que chaque pilote es a jour
=> tout es a jour

Je pense qu il vous faut plus de précisions , rapports WhoCrashed et Speccy pour la config ?
Hébergement des rapports sur ci joint ?

d'avance merci pour vos aides

[Malekal_morte]

Salut,

On peut aussi utiliser WhoCrashed pour obtenir des informations sur ces plantages.
=> Tutoriel WhoCrashed
Fais un copier/coller du contenu ici comme indiqué dans le tuto.

et :

[*] Vérifie la température de l'ordinateur.
[*] Vérifie la CPU si utilisation mémoire/CPU excessive par un processus en particulier. N'hésite pas à fournir des captures d'écran du gestionnaire de tâches avec les processus triés sur la colonne CPU pour voir celui qui reste le plus proche de 100%.
[*] Vérifie l'état de santé des disques dur notamment avec Par exemple avec CrystalDiskInfo, voir si le statut est correct ou Prudence.


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.

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

[jmd40]

salut , merci de ton aide

j ai aussi "passé" l utilitaire de résolution de Windows Update , sans résultat
idem pour la mise a jour de la pile du BIOS

donc rapport WHOCRASHED

Code : Tout sélectionner

Welcome to WhoCrashed (HOME EDITION) v 6.61
--------------------------------------------------------------------------------

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: DESKTOP-NT59O7F
Windows version: Windows 10 , 10.0, version 1903, build: 18362
Windows dir: C:\WINDOWS
Hardware: ASUSTeK COMPUTER INC., PRIME B360M-K
CPU: GenuineIntel Intel(R) Core(TM) i5-8400 CPU @ 2.80GHz Intel8664, level: 6
6 logical processors, active mask: 63
RAM: 8504995840 bytes (7,9GB)




--------------------------------------------------------------------------------
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 Tue 02/07/2019 02:39:38 your computer crashed or a problem was reported
crash dump file: C:\WINDOWS\Minidump\070219-27250-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x1BC8A0) 
Bugcheck code: 0x1A (0x41792, 0xFFFFAD8F67D3F810, 0x100200100000000, 0x0)
Error: MEMORY_MANAGEMENT
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 severe memory management error occurred. A corrupted PTE has been detected. 
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. This problem might also be caused because of overheating (thermal issue). 
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 01/07/2019 21:45:25 your computer crashed or a problem was reported
crash dump file: C:\WINDOWS\Minidump\070119-23656-01.dmp
This was probably caused by the following module: fltmgr.sys (FLTMGR+0x8539) 
Bugcheck code: 0x1000007E (0xFFFFFFFFC0000005, 0xFFFFF805091111D3, 0xFFFF968655D3EF98, 0xFFFF968655D3E7E0)
Error: SYSTEM_THREAD_EXCEPTION_NOT_HANDLED_M
file path: C:\WINDOWS\system32\drivers\fltmgr.sys
product: Système d’exploitation Microsoft® Windows®
company: Microsoft Corporation
description: Gestionnaire de filtres de système de fichiers Microsoft
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 Mon 01/07/2019 15:38:28 your computer crashed or a problem was reported
crash dump file: C:\WINDOWS\Minidump\070119-22984-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x1BC8A0) 
Bugcheck code: 0xEF (0xFFFF958DC156E440, 0x0, 0x0, 0x0)
Error: CRITICAL_PROCESS_DIED
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 critical system process died. 
There is a possibility this problem was caused by a virus or other malware. 
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time. 





--------------------------------------------------------------------------------


Conclusion
--------------------------------------------------------------------------------

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

Je vais envoyer en plusieures fois , car ça plante

[jmd40]

voila la suite
https://pjjoint.malekal.com/files.php?i ... q10t14p5r7
https://pjjoint.malekal.com/files.php?i ... 0q14u11f12
https://pjjoint.malekal.com/files.php?i ... i12z12i8g9
https://pjjoint.malekal.com/files.php?i ... 14c14b11s7
https://pjjoint.malekal.com/files.php?i ... 13d9n10s11

https://pjjoint.malekal.com/files.php?i ... 12g15d5r10

voila je poste avant plantage

[jmd40]

suite FRST

https://pjjoint.malekal.com/files.php?i ... 5w7m5q13n9
https://pjjoint.malekal.com/files.php?i ... 5f11z15c14
https://pjjoint.malekal.com/files.php?i ... 11d10w8f13

voila , a plus

[jmd40]

un petit "up" pour ce sujet

a plus merci

[Malekal_morte]

Fais une mise à jour driversCloud.


Essaye d'utiliser le gestionnaire de vérificateur de pilotes : Vérifier les pilotes défectueux de Windows.
Soit le tutoriel et vois si tu arrives à obtenir un plantage avec DRIVER_VERIFIED_DETECTED_VIOLATION (xxxxx.sys).
Il faut alors indiquer le xxxxx.sys à l'origine.
Il y a un test où on coche une série de d'éléments et un autre test avec tous les pilotes non MIcrosoft.


Sinon il faudra tester en Réinitialisant Windows 10