Ecran bleu à répétition
Fermé
Rayz16
Messages postés
15
Date d'inscription
dimanche 8 octobre 2017
Statut
Membre
Dernière intervention
1 novembre 2017
-
8 oct. 2017 à 21:28
Malekal_morte- Messages postés 180304 Date d'inscription mercredi 17 mai 2006 Statut Modérateur, Contributeur sécurité Dernière intervention 15 décembre 2020 - 1 nov. 2017 à 21:32
Malekal_morte- Messages postés 180304 Date d'inscription mercredi 17 mai 2006 Statut Modérateur, Contributeur sécurité Dernière intervention 15 décembre 2020 - 1 nov. 2017 à 21:32
A voir également:
- Ecran bleu à répétition
- Double ecran - Guide
- Écran bleu - Guide
- Capture d'écran samsung - Guide
- Ecran noir pc - Guide
- Ecran d'accueil iphone - Guide
14 réponses
Lenox-Lewis
Messages postés
283
Date d'inscription
mercredi 27 septembre 2017
Statut
Membre
Dernière intervention
6 décembre 2017
78
8 oct. 2017 à 21:59
8 oct. 2017 à 21:59
Bonjour.
Installer Whocrashed afin d'analyser les écrans bleus: https://www.malekal.com/tutoriel-whocrashed/
Installer Whocrashed afin d'analyser les écrans bleus: https://www.malekal.com/tutoriel-whocrashed/
Rayz16
Messages postés
15
Date d'inscription
dimanche 8 octobre 2017
Statut
Membre
Dernière intervention
1 novembre 2017
8 oct. 2017 à 22:32
8 oct. 2017 à 22:32
Bonsoir, merci Lenox,
--------------------------------------------------------------------------------
Welcome to WhoCrashed (HOME EDITION) v 5.54
--------------------------------------------------------------------------------
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 most 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: RAYZPC
Windows version: Windows 10 , 10.0, build: 15063
Windows dir: C:\WINDOWS
Hardware: GE60 2PC, Micro-Star International Co., Ltd., MS-16GF
CPU: GenuineIntel Intel(R) Core(TM) i7-4700HQ CPU @ 2.40GHz Intel586, level: 6
8 logical processors, active mask: 255
RAM: 17096232960 bytes total
--------------------------------------------------------------------------------
Crash Dump Analysis
--------------------------------------------------------------------------------
Crash dump directory: C:\WINDOWS\Minidump
Crash dumps are enabled on your computer.
On Sun 08/10/2017 17:40:54 your computer crashed
crash dump file: C:\WINDOWS\Minidump\100817-20375-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x1855C)
Bugcheck code: 0x1000007E (0xFFFFFFFFC0000005, 0xFFFFF8027102255C, 0xFFFFDE010BD76588, 0xFFFFDE010BD75DD0)
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 Sun 08/10/2017 17:40:54 your computer crashed
crash dump file: C:\WINDOWS\memory.dmp
This was probably caused by the following module: ntfs.sys (NTFS+0x865A)
Bugcheck code: 0x7E (0xFFFFFFFFC0000005, 0xFFFFF8027102255C, 0xFFFFDE010BD76588, 0xFFFFDE010BD75DD0)
Error: SYSTEM_THREAD_EXCEPTION_NOT_HANDLED
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 bug check indicates that a system thread generated an exception that the error handler did not catch.
The crash took place in a standard 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 Sat 07/10/2017 18:30:39 your computer crashed
crash dump file: C:\WINDOWS\Minidump\100717-25781-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x16C580)
Bugcheck code: 0xEF (0xFFFFA709CCC84640, 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.
On Sat 07/10/2017 11:23:59 your computer crashed
crash dump file: C:\WINDOWS\Minidump\100717-16531-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x16C580)
Bugcheck code: 0xC1 (0xFFFF9401510C0DB0, 0xFFFF9401510C086E, 0xBBC24C, 0x32)
Error: SPECIAL_POOL_DETECTED_MEMORY_CORRUPTION
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 the driver wrote to an invalid section of the special pool.
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 Sat 07/10/2017 05:14:03 your computer crashed
crash dump file: C:\WINDOWS\Minidump\100717-18656-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x16C580)
Bugcheck code: 0xC1 (0xFFFFF88C7F594F50, 0xFFFFF88C7F59486E, 0xBD40A8, 0x32)
Error: SPECIAL_POOL_DETECTED_MEMORY_CORRUPTION
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 the driver wrote to an invalid section of the special pool.
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.
--------------------------------------------------------------------------------
Conclusion
--------------------------------------------------------------------------------
34 crash dumps have been found and analyzed. Only 5 are included in this report. 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.
--------------------------------------------------------------------------------
Welcome to WhoCrashed (HOME EDITION) v 5.54
--------------------------------------------------------------------------------
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 most 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: RAYZPC
Windows version: Windows 10 , 10.0, build: 15063
Windows dir: C:\WINDOWS
Hardware: GE60 2PC, Micro-Star International Co., Ltd., MS-16GF
CPU: GenuineIntel Intel(R) Core(TM) i7-4700HQ CPU @ 2.40GHz Intel586, level: 6
8 logical processors, active mask: 255
RAM: 17096232960 bytes total
--------------------------------------------------------------------------------
Crash Dump Analysis
--------------------------------------------------------------------------------
Crash dump directory: C:\WINDOWS\Minidump
Crash dumps are enabled on your computer.
On Sun 08/10/2017 17:40:54 your computer crashed
crash dump file: C:\WINDOWS\Minidump\100817-20375-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x1855C)
Bugcheck code: 0x1000007E (0xFFFFFFFFC0000005, 0xFFFFF8027102255C, 0xFFFFDE010BD76588, 0xFFFFDE010BD75DD0)
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 Sun 08/10/2017 17:40:54 your computer crashed
crash dump file: C:\WINDOWS\memory.dmp
This was probably caused by the following module: ntfs.sys (NTFS+0x865A)
Bugcheck code: 0x7E (0xFFFFFFFFC0000005, 0xFFFFF8027102255C, 0xFFFFDE010BD76588, 0xFFFFDE010BD75DD0)
Error: SYSTEM_THREAD_EXCEPTION_NOT_HANDLED
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 bug check indicates that a system thread generated an exception that the error handler did not catch.
The crash took place in a standard 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 Sat 07/10/2017 18:30:39 your computer crashed
crash dump file: C:\WINDOWS\Minidump\100717-25781-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x16C580)
Bugcheck code: 0xEF (0xFFFFA709CCC84640, 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.
On Sat 07/10/2017 11:23:59 your computer crashed
crash dump file: C:\WINDOWS\Minidump\100717-16531-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x16C580)
Bugcheck code: 0xC1 (0xFFFF9401510C0DB0, 0xFFFF9401510C086E, 0xBBC24C, 0x32)
Error: SPECIAL_POOL_DETECTED_MEMORY_CORRUPTION
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 the driver wrote to an invalid section of the special pool.
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 Sat 07/10/2017 05:14:03 your computer crashed
crash dump file: C:\WINDOWS\Minidump\100717-18656-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x16C580)
Bugcheck code: 0xC1 (0xFFFFF88C7F594F50, 0xFFFFF88C7F59486E, 0xBD40A8, 0x32)
Error: SPECIAL_POOL_DETECTED_MEMORY_CORRUPTION
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 the driver wrote to an invalid section of the special pool.
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.
--------------------------------------------------------------------------------
Conclusion
--------------------------------------------------------------------------------
34 crash dumps have been found and analyzed. Only 5 are included in this report. 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.
Lenox-Lewis
Messages postés
283
Date d'inscription
mercredi 27 septembre 2017
Statut
Membre
Dernière intervention
6 décembre 2017
78
9 oct. 2017 à 10:09
9 oct. 2017 à 10:09
Je vois, il faut la version payante pour afficher le reste, mettre à jour les drivers avec Driverscloud: https://www.malekal.com/driverscloud-mettre-a-jour-ses-pilotes/
Rayz16
Messages postés
15
Date d'inscription
dimanche 8 octobre 2017
Statut
Membre
Dernière intervention
1 novembre 2017
9 oct. 2017 à 19:13
9 oct. 2017 à 19:13
Bonsoir Lenox,
J'ai tous mis à jours, il n'existe aucun autre moyen ou outil qui peux remplacer le who crached payant?
merci encore;
Rayz
J'ai tous mis à jours, il n'existe aucun autre moyen ou outil qui peux remplacer le who crached payant?
merci encore;
Rayz
Lenox-Lewis
Messages postés
283
Date d'inscription
mercredi 27 septembre 2017
Statut
Membre
Dernière intervention
6 décembre 2017
78
9 oct. 2017 à 19:46
9 oct. 2017 à 19:46
Il y a BlueScreenview, voici un tuto: https://forum.malekal.com/viewtopic.php?t=33290&start=
Rayz16
Messages postés
15
Date d'inscription
dimanche 8 octobre 2017
Statut
Membre
Dernière intervention
1 novembre 2017
9 oct. 2017 à 20:41
9 oct. 2017 à 20:41
Bonsoir lenox,
Je l'avais deja, voici un premier rapport, le dernier que j'ai eu aujourd'hui :
==================================================
Dump File : 100817-20375-01.dmp
Crash Time : 08/10/2017 17:40:54
Bug Check String : SYSTEM_THREAD_EXCEPTION_NOT_HANDLED
Bug Check Code : 0x1000007e
Parameter 1 : ffffffff`c0000005
Parameter 2 : fffff802`7102255c
Parameter 3 : ffffde01`0bd76588
Parameter 4 : ffffde01`0bd75dd0
Caused By Driver : NTFS.sys
Caused By Address : NTFS.sys+865a
File Description :
Product Name :
Company :
File Version :
Processor : x64
Crash Address : ntoskrnl.exe+1855c
Stack Address 1 :
Stack Address 2 :
Stack Address 3 :
Computer Name :
Full Path : C:\WINDOWS\Minidump\100817-20375-01.dmp
Processors Count : 8
Major Version : 15
Minor Version : 15063
Dump File Size : 922 260
Dump File Time : 08/10/2017 17:44:20
==================================================
celui d'hier :
==================================================
Dump File : 100717-25781-01.dmp
Crash Time : 07/10/2017 18:30:39
Bug Check String : CRITICAL_PROCESS_DIED
Bug Check Code : 0x000000ef
Parameter 1 : ffffa709`ccc84640
Parameter 2 : 00000000`00000000
Parameter 3 : 00000000`00000000
Parameter 4 : 00000000`00000000
Caused By Driver : ntoskrnl.exe
Caused By Address : ntoskrnl.exe+16c580
File Description :
Product Name :
Company :
File Version :
Processor : x64
Crash Address : ntoskrnl.exe+16c580
Stack Address 1 :
Stack Address 2 :
Stack Address 3 :
Computer Name :
Full Path : C:\WINDOWS\Minidump\100717-25781-01.dmp
Processors Count : 8
Major Version : 15
Minor Version : 15063
Dump File Size : 616 676
Dump File Time : 07/10/2017 18:33:08
==================================================
Je l'avais deja, voici un premier rapport, le dernier que j'ai eu aujourd'hui :
==================================================
Dump File : 100817-20375-01.dmp
Crash Time : 08/10/2017 17:40:54
Bug Check String : SYSTEM_THREAD_EXCEPTION_NOT_HANDLED
Bug Check Code : 0x1000007e
Parameter 1 : ffffffff`c0000005
Parameter 2 : fffff802`7102255c
Parameter 3 : ffffde01`0bd76588
Parameter 4 : ffffde01`0bd75dd0
Caused By Driver : NTFS.sys
Caused By Address : NTFS.sys+865a
File Description :
Product Name :
Company :
File Version :
Processor : x64
Crash Address : ntoskrnl.exe+1855c
Stack Address 1 :
Stack Address 2 :
Stack Address 3 :
Computer Name :
Full Path : C:\WINDOWS\Minidump\100817-20375-01.dmp
Processors Count : 8
Major Version : 15
Minor Version : 15063
Dump File Size : 922 260
Dump File Time : 08/10/2017 17:44:20
==================================================
celui d'hier :
==================================================
Dump File : 100717-25781-01.dmp
Crash Time : 07/10/2017 18:30:39
Bug Check String : CRITICAL_PROCESS_DIED
Bug Check Code : 0x000000ef
Parameter 1 : ffffa709`ccc84640
Parameter 2 : 00000000`00000000
Parameter 3 : 00000000`00000000
Parameter 4 : 00000000`00000000
Caused By Driver : ntoskrnl.exe
Caused By Address : ntoskrnl.exe+16c580
File Description :
Product Name :
Company :
File Version :
Processor : x64
Crash Address : ntoskrnl.exe+16c580
Stack Address 1 :
Stack Address 2 :
Stack Address 3 :
Computer Name :
Full Path : C:\WINDOWS\Minidump\100717-25781-01.dmp
Processors Count : 8
Major Version : 15
Minor Version : 15063
Dump File Size : 616 676
Dump File Time : 07/10/2017 18:33:08
==================================================
Vous n’avez pas trouvé la réponse que vous recherchez ?
Posez votre question
Lenox-Lewis
Messages postés
283
Date d'inscription
mercredi 27 septembre 2017
Statut
Membre
Dernière intervention
6 décembre 2017
78
9 oct. 2017 à 21:54
9 oct. 2017 à 21:54
Appuyer sur les touches WINDOWS et X
Sur la gauche Invite de commandes (admin) ou Powershell (admin)
Dans la fenêtre d'invite, taper chkdsk /f /r
Répondre O(ui), l'analyse se fera au redémarrage du PC.
Sur la gauche Invite de commandes (admin) ou Powershell (admin)
Dans la fenêtre d'invite, taper chkdsk /f /r
Répondre O(ui), l'analyse se fera au redémarrage du PC.
Rayz16
Messages postés
15
Date d'inscription
dimanche 8 octobre 2017
Statut
Membre
Dernière intervention
1 novembre 2017
10 oct. 2017 à 13:32
10 oct. 2017 à 13:32
Bonjour Lenox,
C'est fait, y a aucun problème de disque... même si lors du démarrage, l'utilisation du disque est tout le temps à 100% puis ca redescend au bout d'une mn voir un peu plus.
C'est fait, y a aucun problème de disque... même si lors du démarrage, l'utilisation du disque est tout le temps à 100% puis ca redescend au bout d'une mn voir un peu plus.
Rayz16
Messages postés
15
Date d'inscription
dimanche 8 octobre 2017
Statut
Membre
Dernière intervention
1 novembre 2017
20 oct. 2017 à 18:00
20 oct. 2017 à 18:00
Quelqu'un pourrait m'aider svp ! j'ai toujours le même problème et apparemment lenox n'est plus de la discussion
Merci d'avance
Merci d'avance
Malekal_morte-
Messages postés
180304
Date d'inscription
mercredi 17 mai 2006
Statut
Modérateur, Contributeur sécurité
Dernière intervention
15 décembre 2020
24 629
20 oct. 2017 à 23:00
20 oct. 2017 à 23:00
Salut,
pour voir ce qui tourne :
Suis le tutoriel FRST. ( prends le temps de lire attentivement - tout y est bien expliqué ).
Télécharge et lance le scan FRST,
Attendre la fin du scan, un message indique que l'analyse est terminée.
Trois rapports FRST seront générés :
Envoie ces 3 rapports sur le site https://pjjoint.malekal.com/ afin de les partager.
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.
pour voir ce qui tourne :
Suis le tutoriel FRST. ( prends le temps de lire attentivement - tout y est bien expliqué ).
Télécharge et lance le scan FRST,
Attendre la fin du scan, un message indique que l'analyse est terminée.
Trois rapports FRST seront générés :
- FRST.txt
- Shortcut.txt
- Additionnal.txt
Envoie ces 3 rapports sur le site https://pjjoint.malekal.com/ afin de les partager.
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.
Rayz16
Messages postés
15
Date d'inscription
dimanche 8 octobre 2017
Statut
Membre
Dernière intervention
1 novembre 2017
21 oct. 2017 à 16:27
21 oct. 2017 à 16:27
Bonjour,
tout d'abord merci d'avoir pris le soin de répondre.
Voici les liens demandés :
https://pjjoint.malekal.com/files.php?id=20171021_j9b15s107k12
https://pjjoint.malekal.com/files.php?id=FRST_20171021_l5z5s14n15z8
https://pjjoint.malekal.com/files.php?id=20171021_x10y11b9o10p8
j'espère que ça aidera.
Rayz
tout d'abord merci d'avoir pris le soin de répondre.
Voici les liens demandés :
https://pjjoint.malekal.com/files.php?id=20171021_j9b15s107k12
https://pjjoint.malekal.com/files.php?id=FRST_20171021_l5z5s14n15z8
https://pjjoint.malekal.com/files.php?id=20171021_x10y11b9o10p8
j'espère que ça aidera.
Rayz
Malekal_morte-
Messages postés
180304
Date d'inscription
mercredi 17 mai 2006
Statut
Modérateur, Contributeur sécurité
Dernière intervention
15 décembre 2020
24 629
21 oct. 2017 à 17:45
21 oct. 2017 à 17:45
Error: (10/21/2017 03:07:53 PM) (Source: Ntfs) (EventID: 55) (User: AUTORITE NT)
Description: Une défaillance a été détectée dans la structure du système de fichiers sur le volume C:.
La nature exacte de la défaillance est inconnue. Les structures de système de fichiers doivent être analysées en ligne.
Fais un checkdisk en ligne de commandes.
Il faut saisir la commande suivante dans une invite de commande en administrateur :
Cela va te propose de faire l'analyse au redémarrage de Windows, accepte.
et :
Error: (10/21/2017 11:43:15 AM) (Source: DCOM) (EventID: 10016) (User: AUTORITE NT)
Description: Les paramètres d’autorisation propres à l’application n’accordent pas l’autorisation Local Activation pour l’application serveur COM avec le CLSID
{D63B10C5-BB46-4990-A94F-E40B9D520160}
et l’APPID
{9CA88EE3-ACB7-47C8-AFC4-AB702511C276}
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.
Suis les instructions de cette page : https://www.malekal.com/corriger-erreur-dcom-windows-10/
Description: Une défaillance a été détectée dans la structure du système de fichiers sur le volume C:.
La nature exacte de la défaillance est inconnue. Les structures de système de fichiers doivent être analysées en ligne.
Fais un checkdisk en ligne de commandes.
Il faut saisir la commande suivante dans une invite de commande en administrateur :
chkdsk c: /R /F
Cela va te propose de faire l'analyse au redémarrage de Windows, accepte.
et :
Error: (10/21/2017 11:43:15 AM) (Source: DCOM) (EventID: 10016) (User: AUTORITE NT)
Description: Les paramètres d’autorisation propres à l’application n’accordent pas l’autorisation Local Activation pour l’application serveur COM avec le CLSID
{D63B10C5-BB46-4990-A94F-E40B9D520160}
et l’APPID
{9CA88EE3-ACB7-47C8-AFC4-AB702511C276}
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.
Suis les instructions de cette page : https://www.malekal.com/corriger-erreur-dcom-windows-10/
Rayz16
Messages postés
15
Date d'inscription
dimanche 8 octobre 2017
Statut
Membre
Dernière intervention
1 novembre 2017
21 oct. 2017 à 21:02
21 oct. 2017 à 21:02
Bonsoir,
J'ai fais les deux Manips !
Maintenant faudra que je vérifie la stabilité en utilisant le pc?
Je reste à l'écoute de tes instructions je te remercie bro !
Rayz
J'ai fais les deux Manips !
Maintenant faudra que je vérifie la stabilité en utilisant le pc?
Je reste à l'écoute de tes instructions je te remercie bro !
Rayz
Malekal_morte-
Messages postés
180304
Date d'inscription
mercredi 17 mai 2006
Statut
Modérateur, Contributeur sécurité
Dernière intervention
15 décembre 2020
24 629
Modifié le 21 oct. 2017 à 21:06
Modifié le 21 oct. 2017 à 21:06
Vérifie déjà le disque dur : Comment vérifier la santé du disque dur
Par exemple avec CrystalDiskInfo.
Il faudrait voir si les erreurs de disk persistent car la dernière est du 21, or tu es déjà censé avoir fait un chkdsk avant.
Si le disque est en correct sur CrytalDiskInfo, je pense qu'il faudra réinstaller Windows en créant la partition.
S'il est en prudence, possible que le disque dur soit en train de mourrir.
Par exemple avec CrystalDiskInfo.
Il faudrait voir si les erreurs de disk persistent car la dernière est du 21, or tu es déjà censé avoir fait un chkdsk avant.
Si le disque est en correct sur CrytalDiskInfo, je pense qu'il faudra réinstaller Windows en créant la partition.
S'il est en prudence, possible que le disque dur soit en train de mourrir.
Rayz16
Messages postés
15
Date d'inscription
dimanche 8 octobre 2017
Statut
Membre
Dernière intervention
1 novembre 2017
21 oct. 2017 à 22:04
21 oct. 2017 à 22:04
Bonsoir,
voici le rapport :
----------------------------------------------------------------------------
CrystalDiskInfo 7.1.1 (C) 2008-2016 hiyohiyo
Crystal Dew World : https://crystalmark.info/en/
----------------------------------------------------------------------------
OS : Windows 10 Professional [10.0 Build 15063] (x64)
Date : 2017/10/21 21:03:21
-- Controller Map ----------------------------------------------------------
+ Intel(R) 8 Series Chipset Family SATA AHCI Controller [ATA]
- HL-DT-ST DVDRAM GTA0N
- HGST HTS721010A9E630
- Contrôleur des espaces de stockage Microsoft [SCSI]
-- Disk List ---------------------------------------------------------------
(1) HGST HTS721010A9E630 : 1000,2 GB [0/0/0, pd1]
----------------------------------------------------------------------------
(1) HGST HTS721010A9E630
----------------------------------------------------------------------------
Model : HGST HTS721010A9E630
Firmware : JB0OA3J0
Serial Number : JR10006PH6WD6E
Disk Size : 1000,2 GB (8,4/137,4/1000,2/1000,2)
Buffer Size : 32767 KB
Queue Depth : 32
# of Sectors : 1953525168
Rotation Rate : 7200 RPM
Interface : Serial ATA
Major Version : ATA8-ACS
Minor Version : ATA8-ACS version 6
Transfer Mode : SATA/600 | SATA/600
Power On Hours : 6717 heures
Power On Count : 1613 x
Temperature : 40 C (104 F)
Health Status : Correct
Features : S.M.A.R.T., APM, 48bit LBA, NCQ
APM Level : 4080h [ON]
AAM Level : ----
Drive Letter : C:
-- S.M.A.R.T. --------------------------------------------------------------
ID Cur Wor Thr RawValues(6) Attribute Name
01 100 100 _62 000000000000 Taux Erreur en Lecture
02 100 100 _40 000000000000 Performance général sortie disque
03 138 138 _33 000600000000 Temps moyen mise en rotation
04 _99 _99 __0 0000000006CE Décompte des cycles de mise en rotation
05 _94 _94 __5 000000000000 Nombre de secteurs réalloués
07 100 100 _67 000000000000 Taux d'erreurs d'accès des têtes
08 100 100 _40 000000000000 Performance moyenne des opérations d'accès des têtes
09 _85 _85 __0 000000001A3D Heures de Fonctionnement
0A 100 100 _60 000000000000 Nombre d'essais de relancement de la rotation
0C _99 _99 __0 00000000064D Nombre total de cycles marche/arrêt du disque dur
BF 100 100 __0 000000000000 Nombre d'erreurs résultant de chocs ou de vibrations externes
C0 100 100 __0 000000000027 Nombre de fois que l'armature magnétique a été rétractée automatiquement suite à une coupure secteur
C1 _94 _94 __0 00000000FCC9 Nombre de fois que la tête a changé de position
C2 150 150 __0 0037000C0028 Température interne actuelle.
C4 _92 _92 __0 000000000192 Nombre d'opérations de réallocation (remap)
C5 100 100 __0 000000000000 Nombre de secteurs "instables"
C6 100 100 __0 000000000000 Nombre total d'erreurs incorrigibles d'un secteur
C7 200 200 __0 000000000000 Nombre d'erreurs dans le transfert de données via le câble d'interface
DF 100 100 __0 000000000000 Nombre de fois que la tête a changé de position
-- IDENTIFY_DEVICE ---------------------------------------------------------
0 1 2 3 4 5 6 7 8 9
000: 045A 3FFF C837 0010 0000 0000 003F 0000 0000 0000
010: 2020 2020 2020 4A52 3130 3030 3650 4836 5744 3645
020: 0003 FFFF 0004 4A42 304F 4133 4A30 4847 5354 2048
030: 5453 3732 3130 3130 4139 4536 3330 2020 2020 2020
040: 2020 2020 2020 2020 2020 2020 2020 8010 4000 2F00
050: 4000 0200 0200 0007 3FFF 0010 003F FC10 00FB 0110
060: FFFF 0FFF 0000 0007 0003 0078 0078 0078 0078 0000
070: 0000 0000 0000 0000 0000 001F 970E 0006 005E 004C
080: 01FC 0028 746B 7D69 6163 7469 BC49 6163 407F 0055
090: 0056 4080 FFFE 0000 0000 0000 0000 0000 0000 0000
100: 6DB0 7470 0000 0000 0000 0000 6003 74DC 5000 CCA6
110: ACD1 3890 0000 0000 0000 0000 0000 0000 0000 401C
120: 401C 0000 0000 0000 0000 0000 0000 0000 0029 000B
130: 0C90 0000 2182 1CF1 FA00 0000 4000 2000 0004 0000
140: 0000 0702 0605 0703 0503 0000 0000 0000 0000 0000
150: 0000 0005 304F 4233 0000 6804 0000 5DBD 97B0 8000
160: 0000 0000 0000 0000 0000 0000 0000 0000 0003 0000
170: 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000
180: 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000
190: 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000
200: 0000 0000 0000 0000 0000 0000 003D 0000 0000 4000
210: 0000 0000 0000 0000 0000 0000 0000 1C20 0000 0000
220: 0000 0000 103F 0021 0000 0000 0000 0000 0000 0000
230: 0000 0000 0000 0000 0001 03E0 0000 0000 0000 0000
240: 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000
250: 0000 0000 0000 0000 0000 53A5
-- SMART_READ_DATA ---------------------------------------------------------
+0 +1 +2 +3 +4 +5 +6 +7 +8 +9 +A +B +C +D +E +F
000: 10 00 01 0B 00 64 64 00 00 00 00 00 00 00 02 05
010: 00 64 64 00 00 00 00 00 00 00 03 07 00 8A 8A 00
020: 00 00 00 06 00 00 04 12 00 63 63 CE 06 00 00 00
030: 00 00 05 33 00 5E 5E 00 00 00 00 00 00 00 07 0B
040: 00 64 64 00 00 00 00 00 00 00 08 05 00 64 64 00
050: 00 00 00 00 00 00 09 12 00 55 55 3D 1A 00 00 00
060: 00 00 0A 13 00 64 64 00 00 00 00 00 00 00 0C 32
070: 00 63 63 4D 06 00 00 00 00 00 BF 0A 00 64 64 00
080: 00 00 00 00 00 00 C0 32 00 64 64 27 00 00 00 00
090: 00 00 C1 12 00 5E 5E C9 FC 00 00 00 00 00 C2 02
0A0: 00 96 96 28 00 0C 00 37 00 00 C4 32 00 5C 5C 92
0B0: 01 00 00 00 00 00 C5 22 00 64 64 00 00 00 00 00
0C0: 00 00 C6 08 00 64 64 00 00 00 00 00 00 00 C7 0A
0D0: 00 C8 C8 00 00 00 00 00 00 00 DF 0A 00 64 64 00
0E0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
0F0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
100: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
110: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
120: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
130: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
140: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
150: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
160: 00 00 00 00 00 00 00 00 00 00 00 00 2D 00 01 5B
170: 03 00 01 00 02 AB 00 00 00 00 00 00 00 00 00 00
180: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
190: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
1A0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
1B0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
1C0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
1D0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
1E0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
1F0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 8B
-- SMART_READ_THRESHOLD ----------------------------------------------------
+0 +1 +2 +3 +4 +5 +6 +7 +8 +9 +A +B +C +D +E +F
000: 10 00 01 3E 00 00 00 00 00 00 00 00 00 00 02 28
010: 00 00 00 00 00 00 00 00 00 00 03 21 00 00 00 00
020: 00 00 00 00 00 00 04 00 00 00 00 00 00 00 00 00
030: 00 00 05 05 00 00 00 00 00 00 00 00 00 00 07 43
040: 00 00 00 00 00 00 00 00 00 00 08 28 00 00 00 00
050: 00 00 00 00 00 00 09 00 00 00 00 00 00 00 00 00
060: 00 00 0A 3C 00 00 00 00 00 00 00 00 00 00 0C 00
070: 00 00 00 00 00 00 00 00 00 00 BF 00 00 00 00 00
080: 00 00 00 00 00 00 C0 00 00 00 00 00 00 00 00 00
090: 00 00 C1 00 00 00 00 00 00 00 00 00 00 00 C2 00
0A0: 00 00 00 00 00 00 00 00 00 00 C4 00 00 00 00 00
0B0: 00 00 00 00 00 00 C5 00 00 00 00 00 00 00 00 00
0C0: 00 00 C6 00 00 00 00 00 00 00 00 00 00 00 C7 00
0D0: 00 00 00 00 00 00 00 00 00 00 DF 00 00 00 00 00
0E0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
0F0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
100: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
110: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
120: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
130: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
140: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
150: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
160: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
170: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
180: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
190: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
1A0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
1B0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
1C0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
1D0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
1E0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
1F0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 89
voici le rapport :
----------------------------------------------------------------------------
CrystalDiskInfo 7.1.1 (C) 2008-2016 hiyohiyo
Crystal Dew World : https://crystalmark.info/en/
----------------------------------------------------------------------------
OS : Windows 10 Professional [10.0 Build 15063] (x64)
Date : 2017/10/21 21:03:21
-- Controller Map ----------------------------------------------------------
+ Intel(R) 8 Series Chipset Family SATA AHCI Controller [ATA]
- HL-DT-ST DVDRAM GTA0N
- HGST HTS721010A9E630
- Contrôleur des espaces de stockage Microsoft [SCSI]
-- Disk List ---------------------------------------------------------------
(1) HGST HTS721010A9E630 : 1000,2 GB [0/0/0, pd1]
----------------------------------------------------------------------------
(1) HGST HTS721010A9E630
----------------------------------------------------------------------------
Model : HGST HTS721010A9E630
Firmware : JB0OA3J0
Serial Number : JR10006PH6WD6E
Disk Size : 1000,2 GB (8,4/137,4/1000,2/1000,2)
Buffer Size : 32767 KB
Queue Depth : 32
# of Sectors : 1953525168
Rotation Rate : 7200 RPM
Interface : Serial ATA
Major Version : ATA8-ACS
Minor Version : ATA8-ACS version 6
Transfer Mode : SATA/600 | SATA/600
Power On Hours : 6717 heures
Power On Count : 1613 x
Temperature : 40 C (104 F)
Health Status : Correct
Features : S.M.A.R.T., APM, 48bit LBA, NCQ
APM Level : 4080h [ON]
AAM Level : ----
Drive Letter : C:
-- S.M.A.R.T. --------------------------------------------------------------
ID Cur Wor Thr RawValues(6) Attribute Name
01 100 100 _62 000000000000 Taux Erreur en Lecture
02 100 100 _40 000000000000 Performance général sortie disque
03 138 138 _33 000600000000 Temps moyen mise en rotation
04 _99 _99 __0 0000000006CE Décompte des cycles de mise en rotation
05 _94 _94 __5 000000000000 Nombre de secteurs réalloués
07 100 100 _67 000000000000 Taux d'erreurs d'accès des têtes
08 100 100 _40 000000000000 Performance moyenne des opérations d'accès des têtes
09 _85 _85 __0 000000001A3D Heures de Fonctionnement
0A 100 100 _60 000000000000 Nombre d'essais de relancement de la rotation
0C _99 _99 __0 00000000064D Nombre total de cycles marche/arrêt du disque dur
BF 100 100 __0 000000000000 Nombre d'erreurs résultant de chocs ou de vibrations externes
C0 100 100 __0 000000000027 Nombre de fois que l'armature magnétique a été rétractée automatiquement suite à une coupure secteur
C1 _94 _94 __0 00000000FCC9 Nombre de fois que la tête a changé de position
C2 150 150 __0 0037000C0028 Température interne actuelle.
C4 _92 _92 __0 000000000192 Nombre d'opérations de réallocation (remap)
C5 100 100 __0 000000000000 Nombre de secteurs "instables"
C6 100 100 __0 000000000000 Nombre total d'erreurs incorrigibles d'un secteur
C7 200 200 __0 000000000000 Nombre d'erreurs dans le transfert de données via le câble d'interface
DF 100 100 __0 000000000000 Nombre de fois que la tête a changé de position
-- IDENTIFY_DEVICE ---------------------------------------------------------
0 1 2 3 4 5 6 7 8 9
000: 045A 3FFF C837 0010 0000 0000 003F 0000 0000 0000
010: 2020 2020 2020 4A52 3130 3030 3650 4836 5744 3645
020: 0003 FFFF 0004 4A42 304F 4133 4A30 4847 5354 2048
030: 5453 3732 3130 3130 4139 4536 3330 2020 2020 2020
040: 2020 2020 2020 2020 2020 2020 2020 8010 4000 2F00
050: 4000 0200 0200 0007 3FFF 0010 003F FC10 00FB 0110
060: FFFF 0FFF 0000 0007 0003 0078 0078 0078 0078 0000
070: 0000 0000 0000 0000 0000 001F 970E 0006 005E 004C
080: 01FC 0028 746B 7D69 6163 7469 BC49 6163 407F 0055
090: 0056 4080 FFFE 0000 0000 0000 0000 0000 0000 0000
100: 6DB0 7470 0000 0000 0000 0000 6003 74DC 5000 CCA6
110: ACD1 3890 0000 0000 0000 0000 0000 0000 0000 401C
120: 401C 0000 0000 0000 0000 0000 0000 0000 0029 000B
130: 0C90 0000 2182 1CF1 FA00 0000 4000 2000 0004 0000
140: 0000 0702 0605 0703 0503 0000 0000 0000 0000 0000
150: 0000 0005 304F 4233 0000 6804 0000 5DBD 97B0 8000
160: 0000 0000 0000 0000 0000 0000 0000 0000 0003 0000
170: 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000
180: 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000
190: 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000
200: 0000 0000 0000 0000 0000 0000 003D 0000 0000 4000
210: 0000 0000 0000 0000 0000 0000 0000 1C20 0000 0000
220: 0000 0000 103F 0021 0000 0000 0000 0000 0000 0000
230: 0000 0000 0000 0000 0001 03E0 0000 0000 0000 0000
240: 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000
250: 0000 0000 0000 0000 0000 53A5
-- SMART_READ_DATA ---------------------------------------------------------
+0 +1 +2 +3 +4 +5 +6 +7 +8 +9 +A +B +C +D +E +F
000: 10 00 01 0B 00 64 64 00 00 00 00 00 00 00 02 05
010: 00 64 64 00 00 00 00 00 00 00 03 07 00 8A 8A 00
020: 00 00 00 06 00 00 04 12 00 63 63 CE 06 00 00 00
030: 00 00 05 33 00 5E 5E 00 00 00 00 00 00 00 07 0B
040: 00 64 64 00 00 00 00 00 00 00 08 05 00 64 64 00
050: 00 00 00 00 00 00 09 12 00 55 55 3D 1A 00 00 00
060: 00 00 0A 13 00 64 64 00 00 00 00 00 00 00 0C 32
070: 00 63 63 4D 06 00 00 00 00 00 BF 0A 00 64 64 00
080: 00 00 00 00 00 00 C0 32 00 64 64 27 00 00 00 00
090: 00 00 C1 12 00 5E 5E C9 FC 00 00 00 00 00 C2 02
0A0: 00 96 96 28 00 0C 00 37 00 00 C4 32 00 5C 5C 92
0B0: 01 00 00 00 00 00 C5 22 00 64 64 00 00 00 00 00
0C0: 00 00 C6 08 00 64 64 00 00 00 00 00 00 00 C7 0A
0D0: 00 C8 C8 00 00 00 00 00 00 00 DF 0A 00 64 64 00
0E0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
0F0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
100: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
110: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
120: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
130: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
140: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
150: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
160: 00 00 00 00 00 00 00 00 00 00 00 00 2D 00 01 5B
170: 03 00 01 00 02 AB 00 00 00 00 00 00 00 00 00 00
180: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
190: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
1A0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
1B0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
1C0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
1D0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
1E0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
1F0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 8B
-- SMART_READ_THRESHOLD ----------------------------------------------------
+0 +1 +2 +3 +4 +5 +6 +7 +8 +9 +A +B +C +D +E +F
000: 10 00 01 3E 00 00 00 00 00 00 00 00 00 00 02 28
010: 00 00 00 00 00 00 00 00 00 00 03 21 00 00 00 00
020: 00 00 00 00 00 00 04 00 00 00 00 00 00 00 00 00
030: 00 00 05 05 00 00 00 00 00 00 00 00 00 00 07 43
040: 00 00 00 00 00 00 00 00 00 00 08 28 00 00 00 00
050: 00 00 00 00 00 00 09 00 00 00 00 00 00 00 00 00
060: 00 00 0A 3C 00 00 00 00 00 00 00 00 00 00 0C 00
070: 00 00 00 00 00 00 00 00 00 00 BF 00 00 00 00 00
080: 00 00 00 00 00 00 C0 00 00 00 00 00 00 00 00 00
090: 00 00 C1 00 00 00 00 00 00 00 00 00 00 00 C2 00
0A0: 00 00 00 00 00 00 00 00 00 00 C4 00 00 00 00 00
0B0: 00 00 00 00 00 00 C5 00 00 00 00 00 00 00 00 00
0C0: 00 00 C6 00 00 00 00 00 00 00 00 00 00 00 C7 00
0D0: 00 00 00 00 00 00 00 00 00 00 DF 00 00 00 00 00
0E0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
0F0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
100: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
110: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
120: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
130: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
140: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
150: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
160: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
170: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
180: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
190: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
1A0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
1B0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
1C0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
1D0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
1E0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
1F0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 89
Malekal_morte-
Messages postés
180304
Date d'inscription
mercredi 17 mai 2006
Statut
Modérateur, Contributeur sécurité
Dernière intervention
15 décembre 2020
24 629
>
Rayz16
Messages postés
15
Date d'inscription
dimanche 8 octobre 2017
Statut
Membre
Dernière intervention
1 novembre 2017
22 oct. 2017 à 10:46
22 oct. 2017 à 10:46
ok il est en correct.
Encore des BSOD ?
Vas dans l'observateur d'évènements et regarde si tu as des erreurs relatives à l'ouverture de session :
Touche Windows + R
tape eventvwr.msc
Regarde si tu as d'autres évènements Ntfs récent.
Encore des BSOD ?
Vas dans l'observateur d'évènements et regarde si tu as des erreurs relatives à l'ouverture de session :
Touche Windows + R
tape eventvwr.msc
Regarde si tu as d'autres évènements Ntfs récent.
Rayz16
Messages postés
15
Date d'inscription
dimanche 8 octobre 2017
Statut
Membre
Dernière intervention
1 novembre 2017
Modifié le 22 oct. 2017 à 19:56
Modifié le 22 oct. 2017 à 19:56
Bonsoir Malekal_morte-
Oui d'autres BSOD, ironie, j'ai tapé who crached, j'ai fais entrée et ça a craché !
Voici le rapport who crached, car sur l'observateur d’éventements je ne sais pas quel rapport t'envoyer !
Avant Whocrached, j'ai copié une erreur qui date du 08/10/2017, peut être que ça pourraist te donner des indices !
..........................................................
Nom du journal :System
Source : Ntfs
Date : 08/10/2017 18:46:10
ID de l’événement :55
Catégorie de la tâche :Aucun
Niveau : Erreur
Mots clés :
Utilisateur : Système
Ordinateur : RayzPC
Description :
Une défaillance a été détectée dans la structure du système de fichiers sur le volume C:.
La table MFT (Master File Table) contient un enregistrement de fichier endommagé. Le numéro de référence du fichier est 0x30000000367c2. Le nom du fichier est « \Windows\WinSxS\amd64_microsoft-windows-systemrestore-main_31bf3856ad364e35_10.0.15063.0_none_57f3a920ec0db791\srcore.dll ».
XML de l’événement :
<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
<System>
<Provider Name="Ntfs" Guid="{DD70BC80-EF44-421B-8AC3-CD31DA613A4E}" />
<EventID>55</EventID>
<Version>0</Version>
<Level>2</Level>
<Task>0</Task>
<Opcode>0</Opcode>
<Keywords>0x8000000000000000</Keywords>
<TimeCreated SystemTime="2017-10-08T17:46:10.042354900Z" />
<EventRecordID>41877</EventRecordID>
<Correlation />
<Execution ProcessID="4" ThreadID="8648" />
<Channel>System</Channel>
<Computer>RayzPC</Computer>
<Security UserID="S-1-5-18" />
</System>
<EventData>
<Data Name="DriveName">C:</Data>
<Data Name="DeviceName">\Device\HarddiskVolume2</Data>
<Data Name="CorruptionState">0x1c</Data>
<Data Name="HeaderFlags">0x22</Data>
<Data Name="Severity">Normal</Data>
<Data Name="Origin">Pilote du système de fichiers</Data>
<Data Name="Verb">FRS incorrect</Data>
<Data Name="Description">La table MFT (Master File Table) contient un enregistrement de fichier endommagé. Le numéro de référence du fichier est 0x30000000367c2. Le nom du fichier est « \Windows\WinSxS\amd64_microsoft-windows-systemrestore-main_31bf3856ad364e35_10.0.15063.0_none_57f3a920ec0db791\srcore.dll ».
</Data>
<Data Name="Signature">0x12400117</Data>
<Data Name="Outcome">Vérifié</Data>
<Data Name="SampleLength">0</Data>
<Data Name="SampleData">
</Data>
<Data Name="SourceFile">0x6</Data>
<Data Name="SourceLine">372</Data>
<Data Name="SourceTag">340</Data>
<Data Name="AdditionalInfo">0x10000000</Data>
<Data Name="CallStack">NTFS+0x177693, NTFS+0xbc12e, NTFS+0xbbd9b, NTFS+0xbb8e8, NTFS+0xbe112, NTFS+0xc0050, NTFS+0x1a70c, NTFS+0xdeba, NTFS+0xb93e, FLTMGR+0x563d, FLTMGR+0x34d6, ntoskrnl+0x49568f, ntoskrnl+0x4943f9, ntoskrnl+0x177413</Data>
</EventData>
</Event>
......................................
Le rapport who crached :
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 most 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: RAYZPC
Windows version: Windows 10 , 10.0, build: 15063
Windows dir: C:\WINDOWS
Hardware: GE60 2PC, Micro-Star International Co., Ltd., MS-16GF
CPU: GenuineIntel Intel(R) Core(TM) i7-4700HQ CPU @ 2.40GHz Intel586, level: 6
8 logical processors, active mask: 255
RAM: 17096232960 bytes total
--------------------------------------------------------------------------------
Crash Dump Analysis
--------------------------------------------------------------------------------
Crash dump directory: C:\WINDOWS\Minidump
Crash dumps are enabled on your computer.
On Sun 22/10/2017 18:42:37 your computer crashed
crash dump file: C:\WINDOWS\Minidump\102217-19968-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x16C580)
Bugcheck code: 0x1C6 (0x14, 0xFFFFBE874FEFA080, 0xFFDFBE874FEFA868, 0x0)
Error: CUSTOM_ERROR
file path: C:\WINDOWS\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.
On Sun 22/10/2017 18:42:37 your computer crashed
crash dump file: C:\WINDOWS\memory.dmp
This was probably caused by the following module: ntkrnlmp.exe (nt!KeBugCheckEx+0x0)
Bugcheck code: 0x1C6 (0x14, 0xFFFFBE874FEFA080, 0xFFDFBE874FEFA868, 0x0)
Error: CUSTOM_ERROR
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 21/10/2017 16:20:00 your computer crashed
crash dump file: C:\WINDOWS\Minidump\102117-22453-01.dmp
This was probably caused by the following module: ntfs.sys (NTFS+0xC6451)
Bugcheck code: 0x1E (0xFFFFFFFFC0000005, 0xFFFFF80311496451, 0x0, 0xFFFFFFFFFFFFFFFF)
Error: KMODE_EXCEPTION_NOT_HANDLED
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 kernel-mode program 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 standard 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 Fri 20/10/2017 05:01:53 your computer crashed
crash dump file: C:\WINDOWS\Minidump\102017-17375-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x16C580)
Bugcheck code: 0x1A (0x61948, 0x1EDEA0, 0x1, 0x1EDEA0)
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.
This might be a case of memory corruption. More often memory corruption happens because of software errors in buggy drivers, not because of faulty RAM modules. 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 Tue 17/10/2017 17:42:46 your computer crashed
crash dump file: C:\WINDOWS\Minidump\101717-18750-01.dmp
This was probably caused by the following module: ntfs.sys (0xFFFFF80FB5AC031B)
Bugcheck code: 0x50 (0xFFFF84062E37F87C, 0x2, 0xFFFFF80FB5AC031B, 0x0)
Error: PAGE_FAULT_IN_NONPAGED_AREA
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 invalid system memory has been referenced.
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 standard 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.
--------------------------------------------------------------------------------
Conclusion
--------------------------------------------------------------------------------
44 crash dumps have been found and analyzed. Only 5 are included in this report. 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:
nvlddmkm.sys (NVIDIA Windows Kernel Mode Driver, Version 387.92 , NVIDIA Corporation)
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 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.
Oui d'autres BSOD, ironie, j'ai tapé who crached, j'ai fais entrée et ça a craché !
Voici le rapport who crached, car sur l'observateur d’éventements je ne sais pas quel rapport t'envoyer !
Avant Whocrached, j'ai copié une erreur qui date du 08/10/2017, peut être que ça pourraist te donner des indices !
..........................................................
Nom du journal :System
Source : Ntfs
Date : 08/10/2017 18:46:10
ID de l’événement :55
Catégorie de la tâche :Aucun
Niveau : Erreur
Mots clés :
Utilisateur : Système
Ordinateur : RayzPC
Description :
Une défaillance a été détectée dans la structure du système de fichiers sur le volume C:.
La table MFT (Master File Table) contient un enregistrement de fichier endommagé. Le numéro de référence du fichier est 0x30000000367c2. Le nom du fichier est « \Windows\WinSxS\amd64_microsoft-windows-systemrestore-main_31bf3856ad364e35_10.0.15063.0_none_57f3a920ec0db791\srcore.dll ».
XML de l’événement :
<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
<System>
<Provider Name="Ntfs" Guid="{DD70BC80-EF44-421B-8AC3-CD31DA613A4E}" />
<EventID>55</EventID>
<Version>0</Version>
<Level>2</Level>
<Task>0</Task>
<Opcode>0</Opcode>
<Keywords>0x8000000000000000</Keywords>
<TimeCreated SystemTime="2017-10-08T17:46:10.042354900Z" />
<EventRecordID>41877</EventRecordID>
<Correlation />
<Execution ProcessID="4" ThreadID="8648" />
<Channel>System</Channel>
<Computer>RayzPC</Computer>
<Security UserID="S-1-5-18" />
</System>
<EventData>
<Data Name="DriveName">C:</Data>
<Data Name="DeviceName">\Device\HarddiskVolume2</Data>
<Data Name="CorruptionState">0x1c</Data>
<Data Name="HeaderFlags">0x22</Data>
<Data Name="Severity">Normal</Data>
<Data Name="Origin">Pilote du système de fichiers</Data>
<Data Name="Verb">FRS incorrect</Data>
<Data Name="Description">La table MFT (Master File Table) contient un enregistrement de fichier endommagé. Le numéro de référence du fichier est 0x30000000367c2. Le nom du fichier est « \Windows\WinSxS\amd64_microsoft-windows-systemrestore-main_31bf3856ad364e35_10.0.15063.0_none_57f3a920ec0db791\srcore.dll ».
</Data>
<Data Name="Signature">0x12400117</Data>
<Data Name="Outcome">Vérifié</Data>
<Data Name="SampleLength">0</Data>
<Data Name="SampleData">
</Data>
<Data Name="SourceFile">0x6</Data>
<Data Name="SourceLine">372</Data>
<Data Name="SourceTag">340</Data>
<Data Name="AdditionalInfo">0x10000000</Data>
<Data Name="CallStack">NTFS+0x177693, NTFS+0xbc12e, NTFS+0xbbd9b, NTFS+0xbb8e8, NTFS+0xbe112, NTFS+0xc0050, NTFS+0x1a70c, NTFS+0xdeba, NTFS+0xb93e, FLTMGR+0x563d, FLTMGR+0x34d6, ntoskrnl+0x49568f, ntoskrnl+0x4943f9, ntoskrnl+0x177413</Data>
</EventData>
</Event>
......................................
Le rapport who crached :
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 most 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: RAYZPC
Windows version: Windows 10 , 10.0, build: 15063
Windows dir: C:\WINDOWS
Hardware: GE60 2PC, Micro-Star International Co., Ltd., MS-16GF
CPU: GenuineIntel Intel(R) Core(TM) i7-4700HQ CPU @ 2.40GHz Intel586, level: 6
8 logical processors, active mask: 255
RAM: 17096232960 bytes total
--------------------------------------------------------------------------------
Crash Dump Analysis
--------------------------------------------------------------------------------
Crash dump directory: C:\WINDOWS\Minidump
Crash dumps are enabled on your computer.
On Sun 22/10/2017 18:42:37 your computer crashed
crash dump file: C:\WINDOWS\Minidump\102217-19968-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x16C580)
Bugcheck code: 0x1C6 (0x14, 0xFFFFBE874FEFA080, 0xFFDFBE874FEFA868, 0x0)
Error: CUSTOM_ERROR
file path: C:\WINDOWS\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.
On Sun 22/10/2017 18:42:37 your computer crashed
crash dump file: C:\WINDOWS\memory.dmp
This was probably caused by the following module: ntkrnlmp.exe (nt!KeBugCheckEx+0x0)
Bugcheck code: 0x1C6 (0x14, 0xFFFFBE874FEFA080, 0xFFDFBE874FEFA868, 0x0)
Error: CUSTOM_ERROR
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 21/10/2017 16:20:00 your computer crashed
crash dump file: C:\WINDOWS\Minidump\102117-22453-01.dmp
This was probably caused by the following module: ntfs.sys (NTFS+0xC6451)
Bugcheck code: 0x1E (0xFFFFFFFFC0000005, 0xFFFFF80311496451, 0x0, 0xFFFFFFFFFFFFFFFF)
Error: KMODE_EXCEPTION_NOT_HANDLED
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 kernel-mode program 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 standard 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 Fri 20/10/2017 05:01:53 your computer crashed
crash dump file: C:\WINDOWS\Minidump\102017-17375-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x16C580)
Bugcheck code: 0x1A (0x61948, 0x1EDEA0, 0x1, 0x1EDEA0)
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.
This might be a case of memory corruption. More often memory corruption happens because of software errors in buggy drivers, not because of faulty RAM modules. 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 Tue 17/10/2017 17:42:46 your computer crashed
crash dump file: C:\WINDOWS\Minidump\101717-18750-01.dmp
This was probably caused by the following module: ntfs.sys (0xFFFFF80FB5AC031B)
Bugcheck code: 0x50 (0xFFFF84062E37F87C, 0x2, 0xFFFFF80FB5AC031B, 0x0)
Error: PAGE_FAULT_IN_NONPAGED_AREA
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 invalid system memory has been referenced.
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 standard 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.
--------------------------------------------------------------------------------
Conclusion
--------------------------------------------------------------------------------
44 crash dumps have been found and analyzed. Only 5 are included in this report. 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:
nvlddmkm.sys (NVIDIA Windows Kernel Mode Driver, Version 387.92 , NVIDIA Corporation)
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 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.
Malekal_morte-
Messages postés
180304
Date d'inscription
mercredi 17 mai 2006
Statut
Modérateur, Contributeur sécurité
Dernière intervention
15 décembre 2020
24 629
Modifié le 22 oct. 2017 à 20:43
Modifié le 22 oct. 2017 à 20:43
Whocrashed indique le MFT est endommagé.
Donc comme dit précédemment, faut formater, la partition a l'air morte.
et en plus, tu as aussi des plantages NVIDIA.
Sauvegarde les données importantes.
Réinstaller Windows 10 :
Suis ce tuto qui explique comment installer Windows 10 : comment installer Windows 10.
Toutes les étapes sont données de A à Z avec des conseils à la fin pour sécuriser Windows 10.
Les étapes sont en gros :
- Tu télécharges l'ISO d'installation de Windows 10 : https://www.microsoft.com/fr-fr/software-download/windows10 (d'autres méthodes de téléchargement : https://www.malekal.com/telecharger-iso-windows/ ).
- Créer le support d'installation avec Media Creation Tool
- Démarre dessus en modifiant la séquence de démarrage et indiquer la clé USB ou le DVD : Comment démarrer l'ordinateur sur clé USB
Si la clé ne fonctionne pas, tente d'en refaire une avec Rufus : comment télécharger Rufus - voir ce tuto pour les détails : comment créer une clé USB d'installation de Windows
- Laisse toi guider pour installer Windows 10.
- Choisis personnaliser (pas mise à niveau)
- Supprime toutes les partitions principale et système, recréé la partition pour installer Windows.
- Clic sur suivant, cela va te dire qu'un Windows est déjà installé et qu'il va être déplacé.
- Suis la procédure d'installation de Windows à l'aide du tutoriel plus haut.
Une fois Windows installé, je te conseille de suivre ces conseils pour bien configurer et utiliser Windows : Conseils après réinstallation de Windows.
Veuillez appuyer sur une touche pour continuer la désinfection...
Donc comme dit précédemment, faut formater, la partition a l'air morte.
et en plus, tu as aussi des plantages NVIDIA.
Sauvegarde les données importantes.
Réinstaller Windows 10 :
Suis ce tuto qui explique comment installer Windows 10 : comment installer Windows 10.
Toutes les étapes sont données de A à Z avec des conseils à la fin pour sécuriser Windows 10.
Les étapes sont en gros :
- Tu télécharges l'ISO d'installation de Windows 10 : https://www.microsoft.com/fr-fr/software-download/windows10 (d'autres méthodes de téléchargement : https://www.malekal.com/telecharger-iso-windows/ ).
- Créer le support d'installation avec Media Creation Tool
- Démarre dessus en modifiant la séquence de démarrage et indiquer la clé USB ou le DVD : Comment démarrer l'ordinateur sur clé USB
Si la clé ne fonctionne pas, tente d'en refaire une avec Rufus : comment télécharger Rufus - voir ce tuto pour les détails : comment créer une clé USB d'installation de Windows
- Laisse toi guider pour installer Windows 10.
- Choisis personnaliser (pas mise à niveau)
- Supprime toutes les partitions principale et système, recréé la partition pour installer Windows.
- Clic sur suivant, cela va te dire qu'un Windows est déjà installé et qu'il va être déplacé.
- Suis la procédure d'installation de Windows à l'aide du tutoriel plus haut.
Une fois Windows installé, je te conseille de suivre ces conseils pour bien configurer et utiliser Windows : Conseils après réinstallation de Windows.
Veuillez appuyer sur une touche pour continuer la désinfection...
Rayz16
Messages postés
15
Date d'inscription
dimanche 8 octobre 2017
Statut
Membre
Dernière intervention
1 novembre 2017
22 oct. 2017 à 20:52
22 oct. 2017 à 20:52
La méthode ultime, je savais que j'allais partir sur une réinstallation, j'ai pas de disque dure externe c'est pour cela que je temporisé !
Je penses que je le ferais demain; je reviendrais probablement t'informer si celà est récurrent ou pas.
je te remercie Bro pour ton support.
Cordiales salutations,
Rayz
Je penses que je le ferais demain; je reviendrais probablement t'informer si celà est récurrent ou pas.
je te remercie Bro pour ton support.
Cordiales salutations,
Rayz
Malekal_morte-
Messages postés
180304
Date d'inscription
mercredi 17 mai 2006
Statut
Modérateur, Contributeur sécurité
Dernière intervention
15 décembre 2020
24 629
22 oct. 2017 à 20:54
22 oct. 2017 à 20:54
Pas de soucis :)
Rayz16
Messages postés
15
Date d'inscription
dimanche 8 octobre 2017
Statut
Membre
Dernière intervention
1 novembre 2017
29 oct. 2017 à 23:13
29 oct. 2017 à 23:13
Bonsoir Makelal;
Bon voilà j'ai réinstaller ma version windows et j'ai envie de dire que ça va de mal en pire.
Primo, je n'arrive plus à activer ma version windows, j'ai suivi ton tuto mais toute les solutions ne marchent pas; donc je dois me déplacer vers mon revendeur qui est un peu loin.
Secondo, j'ai encore les bsod, toujours des memory management !
Pourrait on stp faire un petit diagnostic histoire de voir ce qui marche pas ? j'ai des doutes sur mon pilote invidia ou la façon dont il interagit avec mes jeux surtout.
Merci d'avance
Bon voilà j'ai réinstaller ma version windows et j'ai envie de dire que ça va de mal en pire.
Primo, je n'arrive plus à activer ma version windows, j'ai suivi ton tuto mais toute les solutions ne marchent pas; donc je dois me déplacer vers mon revendeur qui est un peu loin.
Secondo, j'ai encore les bsod, toujours des memory management !
Pourrait on stp faire un petit diagnostic histoire de voir ce qui marche pas ? j'ai des doutes sur mon pilote invidia ou la façon dont il interagit avec mes jeux surtout.
Merci d'avance
Malekal_morte-
Messages postés
180304
Date d'inscription
mercredi 17 mai 2006
Statut
Modérateur, Contributeur sécurité
Dernière intervention
15 décembre 2020
24 629
>
Rayz16
Messages postés
15
Date d'inscription
dimanche 8 octobre 2017
Statut
Membre
Dernière intervention
1 novembre 2017
29 oct. 2017 à 23:44
29 oct. 2017 à 23:44
Tu as bien remis exactement le même Windows 10 ?
Tu peux relancer un whocrashed pour voir si Nvidia est encore mentionné ?
Après tu peux toujours faire un memtest :
memtest : vérifier barette de mémoire (malekal.com)
Tu peux relancer un whocrashed pour voir si Nvidia est encore mentionné ?
Après tu peux toujours faire un memtest :
memtest : vérifier barette de mémoire (malekal.com)
Rayz16
Messages postés
15
Date d'inscription
dimanche 8 octobre 2017
Statut
Membre
Dernière intervention
1 novembre 2017
Modifié le 30 oct. 2017 à 00:39
Modifié le 30 oct. 2017 à 00:39
Bonsoir Malekal,
Merci pour ta rapide réponse.
Apparemment, je n'ai pas exécute la fonction ''vérifier'' de windows, du coup who crached ne trouve pas mes 2 bsod.
Concernant le test mémoire, je l'est fait et il montre aucun problème.
Je l'utilise si j'ai d'autres bsod je te fais signe !
merci encore
Merci pour ta rapide réponse.
Apparemment, je n'ai pas exécute la fonction ''vérifier'' de windows, du coup who crached ne trouve pas mes 2 bsod.
Concernant le test mémoire, je l'est fait et il montre aucun problème.
Je l'utilise si j'ai d'autres bsod je te fais signe !
merci encore
Rayz16
Messages postés
15
Date d'inscription
dimanche 8 octobre 2017
Statut
Membre
Dernière intervention
1 novembre 2017
30 oct. 2017 à 02:46
30 oct. 2017 à 02:46
Voici le rapport Who crached :
--------------------------------------------------------------------------------
Welcome to WhoCrashed (HOME EDITION) v 5.54
--------------------------------------------------------------------------------
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 most 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: RAYZ-PC
Windows version: Windows 10 , 10.0, build: 16299
Windows dir: C:\Windows
Hardware: GE60 2PC, Micro-Star International Co., Ltd., MS-16GF
CPU: GenuineIntel Intel(R) Core(TM) i7-4700HQ CPU @ 2.40GHz Intel586, level: 6
8 logical processors, active mask: 255
RAM: 17096232960 bytes total
--------------------------------------------------------------------------------
Crash Dump Analysis
--------------------------------------------------------------------------------
Crash dump directory: C:\Windows\Minidump
Crash dumps are enabled on your computer.
On Mon 30/10/2017 2:43:05 AM your computer crashed
crash dump file: C:\Windows\Minidump\103017-23750-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x163960)
Bugcheck code: 0x1A (0x41792, 0xFFFFFD0000013928, 0x20000000000000, 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.
This might be a case of memory corruption. More often memory corruption happens because of software errors in buggy drivers, not because of faulty RAM modules. 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 30/10/2017 2:43:05 AM your computer crashed
crash dump file: C:\Windows\memory.dmp
This was probably caused by the following module: ntkrnlmp.exe (nt!KeBugCheckEx+0x0)
Bugcheck code: 0x1A (0x41792, 0xFFFFFD0000013928, 0x20000000000000, 0x0)
Error: MEMORY_MANAGEMENT
Bug check description: This indicates that a severe memory management error occurred.
This might be a case of memory corruption. More often memory corruption happens because of software errors in buggy drivers, not because of faulty RAM modules. 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.
--------------------------------------------------------------------------------
Welcome to WhoCrashed (HOME EDITION) v 5.54
--------------------------------------------------------------------------------
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 most 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: RAYZ-PC
Windows version: Windows 10 , 10.0, build: 16299
Windows dir: C:\Windows
Hardware: GE60 2PC, Micro-Star International Co., Ltd., MS-16GF
CPU: GenuineIntel Intel(R) Core(TM) i7-4700HQ CPU @ 2.40GHz Intel586, level: 6
8 logical processors, active mask: 255
RAM: 17096232960 bytes total
--------------------------------------------------------------------------------
Crash Dump Analysis
--------------------------------------------------------------------------------
Crash dump directory: C:\Windows\Minidump
Crash dumps are enabled on your computer.
On Mon 30/10/2017 2:43:05 AM your computer crashed
crash dump file: C:\Windows\Minidump\103017-23750-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x163960)
Bugcheck code: 0x1A (0x41792, 0xFFFFFD0000013928, 0x20000000000000, 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.
This might be a case of memory corruption. More often memory corruption happens because of software errors in buggy drivers, not because of faulty RAM modules. 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 30/10/2017 2:43:05 AM your computer crashed
crash dump file: C:\Windows\memory.dmp
This was probably caused by the following module: ntkrnlmp.exe (nt!KeBugCheckEx+0x0)
Bugcheck code: 0x1A (0x41792, 0xFFFFFD0000013928, 0x20000000000000, 0x0)
Error: MEMORY_MANAGEMENT
Bug check description: This indicates that a severe memory management error occurred.
This might be a case of memory corruption. More often memory corruption happens because of software errors in buggy drivers, not because of faulty RAM modules. 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.
Malekal_morte-
Messages postés
180304
Date d'inscription
mercredi 17 mai 2006
Statut
Modérateur, Contributeur sécurité
Dernière intervention
15 décembre 2020
24 629
30 oct. 2017 à 13:33
30 oct. 2017 à 13:33
Tu as quoi comme périphériques branchés or clavier ou souris ?
Faudrait sinon tester une barrette de mémoire à la fois... voir si les BSOD perdurent.
Faudrait sinon tester une barrette de mémoire à la fois... voir si les BSOD perdurent.
Rayz16
Messages postés
15
Date d'inscription
dimanche 8 octobre 2017
Statut
Membre
Dernière intervention
1 novembre 2017
1 nov. 2017 à 15:59
1 nov. 2017 à 15:59
Bonjour Malekal,
Mes périphérique sont : souris et casque asus !
Sinon, quel est le moyen de tester une barrette de mémoire à la fois?
J'ai eu un souci aujourd'hui, mon proc était super élevé, du coup le pc s'est figé jusqu'a ce que je redémarre manuellement.
La j'ai désinstalle Nvidia complétement, je test sans pour voir.
Si on me demande quel est ton plus grand rêve, je dirais d'avoir un pc qui fonctionne bien...
Merci encore
Mes périphérique sont : souris et casque asus !
Sinon, quel est le moyen de tester une barrette de mémoire à la fois?
J'ai eu un souci aujourd'hui, mon proc était super élevé, du coup le pc s'est figé jusqu'a ce que je redémarre manuellement.
La j'ai désinstalle Nvidia complétement, je test sans pour voir.
Si on me demande quel est ton plus grand rêve, je dirais d'avoir un pc qui fonctionne bien...
Merci encore
Malekal_morte-
Messages postés
180304
Date d'inscription
mercredi 17 mai 2006
Statut
Modérateur, Contributeur sécurité
Dernière intervention
15 décembre 2020
24 629
>
Rayz16
Messages postés
15
Date d'inscription
dimanche 8 octobre 2017
Statut
Membre
Dernière intervention
1 novembre 2017
1 nov. 2017 à 21:32
1 nov. 2017 à 21:32
Tu laisse une barrette dans l'ordinateur à la fois et tu fais le memtest
éventuellement, vois si ça plante sur Windows.
éventuellement, vois si ça plante sur Windows.
