PC Crash Blue screen
Fermé
kdb
-
19 mars 2020 à 12:35
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 - 19 mars 2020 à 18:05
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 - 19 mars 2020 à 18:05
A voir également:
- Bitdefender crashing windows 10
- Blue screen - Guide
- Benchmark pc - Guide
- Reinitialiser pc - Guide
- Pc lent - Guide
- Whatsapp pc - Télécharger - Messagerie
5 réponses
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 627
19 mars 2020 à 13:28
19 mars 2020 à 13:28
Salut,
Les écrans bleus ou BSOD sont des plantages de Windows qui ne peut plus continuer à fonctionner.
Ces plantages ont plusieurs sources possibles :
- sources logiciels : plantage d'un pilote d'un périphérique comme ceux de la carte graphique, l'antivirus qui plante ou tout autre logiciel qui peut se charger "dans un bas niveau" sur Windows.
- sources matériels : problème matériels sur le disque dur, barrettes de mémoire défectueuses ou incomparabilités, etc
Il faut impérativement que tu regardes si ces plantages ont lieu à des moments particuliers, par exemple, si c'est lorsque tu lances une vidéo sur ton navigateur internet ou un jeu, il y a des chances que ce soit le pilote de la carte graphique. Il faudra alors réinstaller les pilotes de la carte graphique.
Débranche aussi tout autre périphérique que le clavier/souris (manette de jeu, webcam en USB, imprimante USB, etc), si tu as un de ces périphériques, indique le, ça peut être une source.
plus d'informations sur ces écrans bleus, sur la page suivante : https://www.malekal.com/bsod-ecran-bleu-windows/
On peut aussi utiliser WhoCrashed pour obtenir des informations sur ces plantages.
Télécharger et exécute Whocrashed : Telecharger WhoCrashed
=> Tutoriel WhoCrashed
Fais un copier/coller du contenu ici comme indiqué dans le tuto.
Les écrans bleus ou BSOD sont des plantages de Windows qui ne peut plus continuer à fonctionner.
Ces plantages ont plusieurs sources possibles :
- sources logiciels : plantage d'un pilote d'un périphérique comme ceux de la carte graphique, l'antivirus qui plante ou tout autre logiciel qui peut se charger "dans un bas niveau" sur Windows.
- sources matériels : problème matériels sur le disque dur, barrettes de mémoire défectueuses ou incomparabilités, etc
Il faut impérativement que tu regardes si ces plantages ont lieu à des moments particuliers, par exemple, si c'est lorsque tu lances une vidéo sur ton navigateur internet ou un jeu, il y a des chances que ce soit le pilote de la carte graphique. Il faudra alors réinstaller les pilotes de la carte graphique.
Débranche aussi tout autre périphérique que le clavier/souris (manette de jeu, webcam en USB, imprimante USB, etc), si tu as un de ces périphériques, indique le, ça peut être une source.
plus d'informations sur ces écrans bleus, sur la page suivante : https://www.malekal.com/bsod-ecran-bleu-windows/
On peut aussi utiliser WhoCrashed pour obtenir des informations sur ces plantages.
Télécharger et exécute Whocrashed : Telecharger WhoCrashed
=> Tutoriel WhoCrashed
Fais un copier/coller du contenu ici comme indiqué dans le tuto.
--------------------------------------------------------------------------------
Welcome to WhoCrashed (HOME EDITION) v 6.65
--------------------------------------------------------------------------------
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-BIUUNU5
Windows version: Windows 10 , 10.0, version 1809, build: 17763
Windows dir: C:\Windows
Hardware: ASUSTeK COMPUTER INC., MAXIMUS VIII RANGER
CPU: GenuineIntel Intel(R) Core(TM) i5-7500 CPU @ 3.40GHz Intel8664, level: 6
4 logical processors, active mask: 15
RAM: 8525979648 bytes (7,9GB)
--------------------------------------------------------------------------------
Crash Dump Analysis
--------------------------------------------------------------------------------
Crash dumps are enabled on your computer.
Crash dump directories:
C:\Windows
C:\Windows\Minidump
On Thu 19/03/2020 13:44:38 your computer crashed or a problem was reported
crash dump file: C:\Windows\Minidump\031920-5390-01.dmp
This was probably caused by the following module: fltmgr.sys (0xFFFFF8057F5D88A2)
Bugcheck code: 0x1000007E (0xFFFFFFFFC0000005, 0xFFFFF8057F5D88A2, 0xFFFFF507E3566DF8, 0xFFFFF507E3566640)
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 Thu 19/03/2020 13:44:38 your computer crashed or a problem was reported
crash dump file: C:\Windows\MEMORY.DMP
This was probably caused by the following module: gzflt.sys (gzflt+0x24314)
Bugcheck code: 0x7E (0xFFFFFFFFC0000005, 0xFFFFF8057F5D88A2, 0xFFFFF507E3566DF8, 0xFFFFF507E3566640)
Error: SYSTEM_THREAD_EXCEPTION_NOT_HANDLED
file path: C:\Windows\system32\drivers\gzflt.sys
product: BitDefender Gonzales
company: BitDefender LLC
description: BitDefender Gonzales FileSystem Driver
Bug check description: This bug check indicates that a system thread generated an exception that the error handler did not catch.
A third party driver was identified as the probable root cause of this system error. It is suggested you look for an update for the following driver: gzflt.sys (BitDefender Gonzales FileSystem Driver, BitDefender LLC).
Google query: gzflt.sys BitDefender LLC SYSTEM_THREAD_EXCEPTION_NOT_HANDLED
On Thu 19/03/2020 13:43:50 your computer crashed or a problem was reported
crash dump file: C:\Windows\Minidump\031920-5437-01.dmp
This was probably caused by the following module: fltmgr.sys (0xFFFFF80064B02C00)
Bugcheck code: 0x3B (0xC0000005, 0xFFFFF80064B02C00, 0xFFFFF681FEB3D7D0, 0x0)
Error: SYSTEM_SERVICE_EXCEPTION
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 an exception happened while executing a routine that transitions from non-privileged code to privileged code.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
The crash took place in a file system driver. Since there is no other responsible driver detected, this could be pointing to a malfunctioning drive or corrupted disk. It's suggested that you run CHKDSK.
On Thu 19/03/2020 13:17:56 your computer crashed or a problem was reported
crash dump file: C:\Windows\Minidump\031920-5515-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x1B3EF0)
Bugcheck code: 0x12B (0xFFFFFFFFC00002C4, 0xAC5, 0x1A902D377E0, 0xFFFFAF0116640000)
Error: FAULTY_HARDWARE_CORRUPTED_PAGE
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This bug check indicates that a single-bit error was found in this page. This is a hardware memory error.
This is likely to be caused by a hardware problem. This error suggests a case of memory corruption because of a hardware problem. It is suggested you do a test on your RAM modules (memory test) and make sure your system is not getting overheated. 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 Thu 19/03/2020 12:26:33 your computer crashed or a problem was reported
crash dump file: C:\Windows\Minidump\031920-5328-01.dmp
This was probably caused by the following module: hardware.sys (hardware)
Bugcheck code: 0x1A (0x41792, 0xFFFFFB3FFF623340, 0x100000000000, 0x0)
Error: MEMORY_MANAGEMENT
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).
A third party driver was identified as the probable root cause of this system error. It is suggested you look for an update for the following driver: hardware.sys .
Google query: hardware.sys MEMORY_MANAGEMENT
On Thu 19/03/2020 01:11:44 your computer crashed or a problem was reported
crash dump file: C:\Windows\Minidump\031920-5312-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x1B3EF0)
Bugcheck code: 0x12B (0xFFFFFFFFC00002C4, 0xEDC, 0x12FA9EA0000, 0xFFFF9E00F74E6000)
Error: FAULTY_HARDWARE_CORRUPTED_PAGE
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This bug check indicates that a single-bit error was found in this page. This is a hardware memory error.
This is likely to be caused by a hardware problem. This error suggests a case of memory corruption because of a hardware problem. It is suggested you do a test on your RAM modules (memory test) and make sure your system is not getting overheated. 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.
--------------------------------------------------------------------------------
Conclusion
--------------------------------------------------------------------------------
6 crash dumps have been found and analyzed. 2 third party drivers have been identified to be causing system crashes on your computer. It is strongly suggested that you check for updates for these drivers on their company websites. Click on the links below to search with Google for updates for these drivers:
gzflt.sys (BitDefender Gonzales FileSystem Driver, BitDefender LLC)
hardware.sys
If no updates for these drivers are available, try searching with Google on the names of these drivers in combination with the errors that have been reported for these drivers. Include the brand and model name of your computer as well in the query. This often yields interesting results from discussions on the web by users who have been experiencing similar problems.
Read the 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 6.65
--------------------------------------------------------------------------------
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-BIUUNU5
Windows version: Windows 10 , 10.0, version 1809, build: 17763
Windows dir: C:\Windows
Hardware: ASUSTeK COMPUTER INC., MAXIMUS VIII RANGER
CPU: GenuineIntel Intel(R) Core(TM) i5-7500 CPU @ 3.40GHz Intel8664, level: 6
4 logical processors, active mask: 15
RAM: 8525979648 bytes (7,9GB)
--------------------------------------------------------------------------------
Crash Dump Analysis
--------------------------------------------------------------------------------
Crash dumps are enabled on your computer.
Crash dump directories:
C:\Windows
C:\Windows\Minidump
On Thu 19/03/2020 13:44:38 your computer crashed or a problem was reported
crash dump file: C:\Windows\Minidump\031920-5390-01.dmp
This was probably caused by the following module: fltmgr.sys (0xFFFFF8057F5D88A2)
Bugcheck code: 0x1000007E (0xFFFFFFFFC0000005, 0xFFFFF8057F5D88A2, 0xFFFFF507E3566DF8, 0xFFFFF507E3566640)
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 Thu 19/03/2020 13:44:38 your computer crashed or a problem was reported
crash dump file: C:\Windows\MEMORY.DMP
This was probably caused by the following module: gzflt.sys (gzflt+0x24314)
Bugcheck code: 0x7E (0xFFFFFFFFC0000005, 0xFFFFF8057F5D88A2, 0xFFFFF507E3566DF8, 0xFFFFF507E3566640)
Error: SYSTEM_THREAD_EXCEPTION_NOT_HANDLED
file path: C:\Windows\system32\drivers\gzflt.sys
product: BitDefender Gonzales
company: BitDefender LLC
description: BitDefender Gonzales FileSystem Driver
Bug check description: This bug check indicates that a system thread generated an exception that the error handler did not catch.
A third party driver was identified as the probable root cause of this system error. It is suggested you look for an update for the following driver: gzflt.sys (BitDefender Gonzales FileSystem Driver, BitDefender LLC).
Google query: gzflt.sys BitDefender LLC SYSTEM_THREAD_EXCEPTION_NOT_HANDLED
On Thu 19/03/2020 13:43:50 your computer crashed or a problem was reported
crash dump file: C:\Windows\Minidump\031920-5437-01.dmp
This was probably caused by the following module: fltmgr.sys (0xFFFFF80064B02C00)
Bugcheck code: 0x3B (0xC0000005, 0xFFFFF80064B02C00, 0xFFFFF681FEB3D7D0, 0x0)
Error: SYSTEM_SERVICE_EXCEPTION
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 an exception happened while executing a routine that transitions from non-privileged code to privileged code.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
The crash took place in a file system driver. Since there is no other responsible driver detected, this could be pointing to a malfunctioning drive or corrupted disk. It's suggested that you run CHKDSK.
On Thu 19/03/2020 13:17:56 your computer crashed or a problem was reported
crash dump file: C:\Windows\Minidump\031920-5515-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x1B3EF0)
Bugcheck code: 0x12B (0xFFFFFFFFC00002C4, 0xAC5, 0x1A902D377E0, 0xFFFFAF0116640000)
Error: FAULTY_HARDWARE_CORRUPTED_PAGE
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This bug check indicates that a single-bit error was found in this page. This is a hardware memory error.
This is likely to be caused by a hardware problem. This error suggests a case of memory corruption because of a hardware problem. It is suggested you do a test on your RAM modules (memory test) and make sure your system is not getting overheated. 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 Thu 19/03/2020 12:26:33 your computer crashed or a problem was reported
crash dump file: C:\Windows\Minidump\031920-5328-01.dmp
This was probably caused by the following module: hardware.sys (hardware)
Bugcheck code: 0x1A (0x41792, 0xFFFFFB3FFF623340, 0x100000000000, 0x0)
Error: MEMORY_MANAGEMENT
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).
A third party driver was identified as the probable root cause of this system error. It is suggested you look for an update for the following driver: hardware.sys .
Google query: hardware.sys MEMORY_MANAGEMENT
On Thu 19/03/2020 01:11:44 your computer crashed or a problem was reported
crash dump file: C:\Windows\Minidump\031920-5312-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x1B3EF0)
Bugcheck code: 0x12B (0xFFFFFFFFC00002C4, 0xEDC, 0x12FA9EA0000, 0xFFFF9E00F74E6000)
Error: FAULTY_HARDWARE_CORRUPTED_PAGE
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This bug check indicates that a single-bit error was found in this page. This is a hardware memory error.
This is likely to be caused by a hardware problem. This error suggests a case of memory corruption because of a hardware problem. It is suggested you do a test on your RAM modules (memory test) and make sure your system is not getting overheated. 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.
--------------------------------------------------------------------------------
Conclusion
--------------------------------------------------------------------------------
6 crash dumps have been found and analyzed. 2 third party drivers have been identified to be causing system crashes on your computer. It is strongly suggested that you check for updates for these drivers on their company websites. Click on the links below to search with Google for updates for these drivers:
gzflt.sys (BitDefender Gonzales FileSystem Driver, BitDefender LLC)
hardware.sys
If no updates for these drivers are available, try searching with Google on the names of these drivers in combination with the errors that have been reported for these drivers. Include the brand and model name of your computer as well in the query. This often yields interesting results from discussions on the web by users who have been experiencing similar problems.
Read the 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.
Alors merci de ta réponse , voici le rapport de who crashed , l'écran bleu peut survenir dès le premier démarrage plusieurs fois, comme plus longtemps après . Il a plus de chance de survenir lorsque je joue mais j'ai toujours une page google et youtube ouvert derrière donc voilà .
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 627
Modifié le 19 mars 2020 à 14:51
Modifié le 19 mars 2020 à 14:51
C'est BitDefender qui plante.
Désinstalle le pour tester sans.
et :
Vérifie déjà le disque dur : Comment vérifier la santé du disque dur
Avec CrystalDiskInfo
- Télécharger CrystalDiskInfo
Il faut que le statut soit en bleu, sinon c'est pas bon signe.
Plus d'explications : CrystalDiskInfo: Vérifier l’état de santé du disque dur.
et enfin :
Pour vérifier ton ordinateur, pour d'éventuels infections et avoir un état général du système :
Suis le tutoriel FRST en cliquant sur ce lien bleu. ( 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/ 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).
Désinstalle le pour tester sans.
et :
Vérifie déjà le disque dur : Comment vérifier la santé du disque dur
Avec CrystalDiskInfo
- Télécharger CrystalDiskInfo
Il faut que le statut soit en bleu, sinon c'est pas bon signe.
Plus d'explications : CrystalDiskInfo: Vérifier l’état de santé du disque dur.
et enfin :
Pour vérifier ton ordinateur, pour d'éventuels infections et avoir un état général du système :
Suis le tutoriel FRST en cliquant sur ce lien bleu. ( 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.
- 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).
https://pjjoint.malekal.com/files.php?id=FRST_20200319_n9k14z10q12z8
https://pjjoint.malekal.com/files.php?id=20200319_w15j6n10k15n15
Voici les liens je n'ai eu que le dossier additions, et frst.
Le pc a crash à de multiples reprises lors du démarre toute à l'heure avec pour code d'erreur memory management ce qui parle de la ram non ? En sachant que j'ai désactivé Bitdefender
Mon disque dur est en bleu à 92 %
https://pjjoint.malekal.com/files.php?id=20200319_w15j6n10k15n15
Voici les liens je n'ai eu que le dossier additions, et frst.
Le pc a crash à de multiples reprises lors du démarre toute à l'heure avec pour code d'erreur memory management ce qui parle de la ram non ? En sachant que j'ai désactivé Bitdefender
Mon disque dur est en bleu à 92 %
Vous n’avez pas trouvé la réponse que vous recherchez ?
Posez votre question
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 627
19 mars 2020 à 18:05
19 mars 2020 à 18:05
Désinstalle Driver Booster, ça met le bazar.
Quel est le statut du disque ?
Vérifie l'état de santé de tes barrettes de mémoire :
- memtest : vérifier barette de mémoire (malekal.com)
- memtest : vérifier barette de mémoire (CCM)
Utilise bien Memtest86 de PassMark et pas celui de Windows
Quel est le statut du disque ?
Vérifie l'état de santé de tes barrettes de mémoire :
- memtest : vérifier barette de mémoire (malekal.com)
- memtest : vérifier barette de mémoire (CCM)
Utilise bien Memtest86 de PassMark et pas celui de Windows
