Problème écran bleu erreur windows répétitif
Fermé
Micho__
Messages postés
43
Date d'inscription
lundi 10 août 2020
Statut
Membre
Dernière intervention
18 mai 2021
-
27 avril 2021 à 16:06
SATS_fr Messages postés 4735 Date d'inscription dimanche 15 mars 2020 Statut Membre Dernière intervention 12 janvier 2025 - 18 mai 2021 à 21:23
SATS_fr Messages postés 4735 Date d'inscription dimanche 15 mars 2020 Statut Membre Dernière intervention 12 janvier 2025 - 18 mai 2021 à 21:23
A voir également:
- Problème écran bleu erreur windows répétitif
- Erreur 0x80070643 - Accueil - Windows
- Double ecran - Guide
- Retourner ecran windows - Guide
- Écran bleu - Guide
- Clé windows 10 gratuit - Guide
27 réponses
SATS_fr
Messages postés
4735
Date d'inscription
dimanche 15 mars 2020
Statut
Membre
Dernière intervention
12 janvier 2025
760
8 mai 2021 à 15:15
8 mai 2021 à 15:15
Même le BIOS ? J'ai vu que les dernières version date de mars 2021.
Sinon, pour le matériel, il faut analyser les rapports de dump.
Installe le logiciel WhoCrashed et publie les derniers rapport de BSOD.
Sinon, pour le matériel, il faut analyser les rapports de dump.
Installe le logiciel WhoCrashed et publie les derniers rapport de BSOD.
SATS_fr
Messages postés
4735
Date d'inscription
dimanche 15 mars 2020
Statut
Membre
Dernière intervention
12 janvier 2025
760
8 mai 2021 à 15:19
8 mai 2021 à 15:19
De chrome, oui, c'est possible. D'une extension, bien qu'assez peu probable, cela reste imaginable. De ton compte, là, non.
Micho__
Messages postés
43
Date d'inscription
lundi 10 août 2020
Statut
Membre
Dernière intervention
18 mai 2021
8 mai 2021 à 17:38
8 mai 2021 à 17:38
encore un ecran bleu ca ne doit pas provenir de chrome
Micho__
Messages postés
43
Date d'inscription
lundi 10 août 2020
Statut
Membre
Dernière intervention
18 mai 2021
10 mai 2021 à 15:30
10 mai 2021 à 15:30
J'ai bien mis a jour mon BIOS rien n'y fais, j'ai encore des ecran bleu, ca peut venir d'ou encore ?
je ne devrais mieux l'envoyer en garantie non?
je ne devrais mieux l'envoyer en garantie non?
SATS_fr
Messages postés
4735
Date d'inscription
dimanche 15 mars 2020
Statut
Membre
Dernière intervention
12 janvier 2025
760
10 mai 2021 à 15:47
10 mai 2021 à 15:47
Bonjour. Essaye d'installer le programme WhoCrashed ( https://www.resplendence.com/downloads )
Le problème du SAV c'est que le PC étant vendu sans OS, ils vont te dire que l'anomalie vient de W10, et donc pas d'eux.
Le problème du SAV c'est que le PC étant vendu sans OS, ils vont te dire que l'anomalie vient de W10, et donc pas d'eux.
Micho__
Messages postés
43
Date d'inscription
lundi 10 août 2020
Statut
Membre
Dernière intervention
18 mai 2021
10 mai 2021 à 16:33
10 mai 2021 à 16:33
a oui c'est fort possible
Crash dumps are enabled on your computer.
Crash dump directories:
C:\Windows
C:\Windows\Minidump
On Mon 10/05/2021 16:29:48 your computer crashed or a problem was reported
crash dump file: C:\Windows\Minidump\051021-8750-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x3F5210)
Bugcheck code: 0x1A (0x41792, 0xFFFFA3BFFEAE4120, 0x3C00000000, 0x0)
Error: MEMORY_MANAGEMENT
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This indicates that a severe memory management error occurred. A corrupted PTE has been detected.
This might be a case of memory corruption. This may be because of a hardware issue such as faulty RAM, overheating (thermal issue) or because of a buggy driver. This problem might also be caused because of overheating (thermal issue).
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.
On Mon 10/05/2021 16:29:48 your computer crashed or a problem was reported
crash dump file: C:\Windows\MEMORY.DMP
This was probably caused by the following module: ntkrnlmp.exe (nt!RtlAvlRemoveNode+0x643A)
Bugcheck code: 0x1A (0x41792, 0xFFFFA3BFFEAE4120, 0x3C00000000, 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).
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 10/05/2021 15:25:45 your computer crashed or a problem was reported
crash dump file: C:\Windows\Minidump\051021-9921-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x3F5210)
Bugcheck code: 0xA (0xFFFF8EF2051557A0, 0x2, 0x0, 0xFFFFF8074C2F2964)
Error: IRQL_NOT_LESS_OR_EQUAL
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This indicates that Microsoft Windows or a kernel-mode driver accessed paged memory at DISPATCH_LEVEL or above. This is a software bug.
This bug check belongs to the crash dump test that you have performed with WhoCrashed or other software. It means that a crash dump file was properly written out.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.
On Mon 10/05/2021 15:23:18 your computer crashed or a problem was reported
crash dump file: C:\Windows\Minidump\051021-8734-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x3F5210)
Bugcheck code: 0x1A (0x41792, 0xFFFFFB00DA054020, 0x2A00000000, 0x0)
Error: MEMORY_MANAGEMENT
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This indicates that a severe memory management error occurred. A corrupted PTE has been detected.
This might be a case of memory corruption. This may be because of a hardware issue such as faulty RAM, overheating (thermal issue) or because of a buggy driver. This problem might also be caused because of overheating (thermal issue).
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.
On Mon 10/05/2021 15:20:30 your computer crashed or a problem was reported
crash dump file: C:\Windows\Minidump\051021-9625-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x3F5210)
Bugcheck code: 0x1A (0x41792, 0xFFFF843EFA2753E0, 0x4100000000, 0x0)
Error: MEMORY_MANAGEMENT
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This indicates that a severe memory management error occurred. A corrupted PTE has been detected.
This might be a case of memory corruption. This may be because of a hardware issue such as faulty RAM, overheating (thermal issue) or because of a buggy driver. This problem might also be caused because of overheating (thermal issue).
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.
On Mon 10/05/2021 15:13:19 your computer crashed or a problem was reported
crash dump file: C:\Windows\Minidump\051021-8656-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x3F5210)
Bugcheck code: 0x1A (0x41792, 0xFFFFFC80DC262020, 0x2E00000000, 0x0)
Error: MEMORY_MANAGEMENT
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This indicates that a severe memory management error occurred. A corrupted PTE has been detected.
This might be a case of memory corruption. This may be because of a hardware issue such as faulty RAM, overheating (thermal issue) or because of a buggy driver. This problem might also be caused because of overheating (thermal issue).
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.
--------------------------------------------------------------------------------
Conclusion
--------------------------------------------------------------------------------
6 crash dumps have been found and analyzed. No offending third party drivers have been found. Connsider using WhoCrashed Professional which offers more detailed analysis using symbol resolution. Also configuring your system to produce a full memory dump may help you.
Read the topic general suggestions for troubleshooting system crashes for more information.
Note that it's not always possible to state with certainty whether a reported driver is responsible for crashing your system or that the root cause is in another module. Nonetheless it's suggested you look for updates for the products that these drivers belong to and regularly visit Windows update or enable automatic updates for Windows. In case a piece of malfunctioning hardware is causing trouble, a search with Google on the bug check errors together with the model name and brand of your computer may help you investigate this further.
Crash dumps are enabled on your computer.
Crash dump directories:
C:\Windows
C:\Windows\Minidump
On Mon 10/05/2021 16:29:48 your computer crashed or a problem was reported
crash dump file: C:\Windows\Minidump\051021-8750-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x3F5210)
Bugcheck code: 0x1A (0x41792, 0xFFFFA3BFFEAE4120, 0x3C00000000, 0x0)
Error: MEMORY_MANAGEMENT
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This indicates that a severe memory management error occurred. A corrupted PTE has been detected.
This might be a case of memory corruption. This may be because of a hardware issue such as faulty RAM, overheating (thermal issue) or because of a buggy driver. This problem might also be caused because of overheating (thermal issue).
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.
On Mon 10/05/2021 16:29:48 your computer crashed or a problem was reported
crash dump file: C:\Windows\MEMORY.DMP
This was probably caused by the following module: ntkrnlmp.exe (nt!RtlAvlRemoveNode+0x643A)
Bugcheck code: 0x1A (0x41792, 0xFFFFA3BFFEAE4120, 0x3C00000000, 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).
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 10/05/2021 15:25:45 your computer crashed or a problem was reported
crash dump file: C:\Windows\Minidump\051021-9921-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x3F5210)
Bugcheck code: 0xA (0xFFFF8EF2051557A0, 0x2, 0x0, 0xFFFFF8074C2F2964)
Error: IRQL_NOT_LESS_OR_EQUAL
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This indicates that Microsoft Windows or a kernel-mode driver accessed paged memory at DISPATCH_LEVEL or above. This is a software bug.
This bug check belongs to the crash dump test that you have performed with WhoCrashed or other software. It means that a crash dump file was properly written out.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.
On Mon 10/05/2021 15:23:18 your computer crashed or a problem was reported
crash dump file: C:\Windows\Minidump\051021-8734-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x3F5210)
Bugcheck code: 0x1A (0x41792, 0xFFFFFB00DA054020, 0x2A00000000, 0x0)
Error: MEMORY_MANAGEMENT
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This indicates that a severe memory management error occurred. A corrupted PTE has been detected.
This might be a case of memory corruption. This may be because of a hardware issue such as faulty RAM, overheating (thermal issue) or because of a buggy driver. This problem might also be caused because of overheating (thermal issue).
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.
On Mon 10/05/2021 15:20:30 your computer crashed or a problem was reported
crash dump file: C:\Windows\Minidump\051021-9625-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x3F5210)
Bugcheck code: 0x1A (0x41792, 0xFFFF843EFA2753E0, 0x4100000000, 0x0)
Error: MEMORY_MANAGEMENT
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This indicates that a severe memory management error occurred. A corrupted PTE has been detected.
This might be a case of memory corruption. This may be because of a hardware issue such as faulty RAM, overheating (thermal issue) or because of a buggy driver. This problem might also be caused because of overheating (thermal issue).
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.
On Mon 10/05/2021 15:13:19 your computer crashed or a problem was reported
crash dump file: C:\Windows\Minidump\051021-8656-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x3F5210)
Bugcheck code: 0x1A (0x41792, 0xFFFFFC80DC262020, 0x2E00000000, 0x0)
Error: MEMORY_MANAGEMENT
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This indicates that a severe memory management error occurred. A corrupted PTE has been detected.
This might be a case of memory corruption. This may be because of a hardware issue such as faulty RAM, overheating (thermal issue) or because of a buggy driver. This problem might also be caused because of overheating (thermal issue).
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.
--------------------------------------------------------------------------------
Conclusion
--------------------------------------------------------------------------------
6 crash dumps have been found and analyzed. No offending third party drivers have been found. Connsider using WhoCrashed Professional which offers more detailed analysis using symbol resolution. Also configuring your system to produce a full memory dump may help you.
Read the topic general suggestions for troubleshooting system crashes for more information.
Note that it's not always possible to state with certainty whether a reported driver is responsible for crashing your system or that the root cause is in another module. Nonetheless it's suggested you look for updates for the products that these drivers belong to and regularly visit Windows update or enable automatic updates for Windows. In case a piece of malfunctioning hardware is causing trouble, a search with Google on the bug check errors together with the model name and brand of your computer may help you investigate this further.
SATS_fr
Messages postés
4735
Date d'inscription
dimanche 15 mars 2020
Statut
Membre
Dernière intervention
12 janvier 2025
760
10 mai 2021 à 16:37
10 mai 2021 à 16:37
Il semblerait que ce soit un problème de mémoire.
exécute un test mémoire :
Attention à bien télécharger la version qui correspond à ton BIOS (V4) ou UEFI (v8)
https://www.memtest86.com/download.htm
exécute un test mémoire :
Attention à bien télécharger la version qui correspond à ton BIOS (V4) ou UEFI (v8)
https://www.memtest86.com/download.htm
Micho__
Messages postés
43
Date d'inscription
lundi 10 août 2020
Statut
Membre
Dernière intervention
18 mai 2021
10 mai 2021 à 17:37
10 mai 2021 à 17:37
j'ai fais la clé usb avec le memtest comment te l'as transférer ?
Vous n’avez pas trouvé la réponse que vous recherchez ?
Posez votre question
SATS_fr
Messages postés
4735
Date d'inscription
dimanche 15 mars 2020
Statut
Membre
Dernière intervention
12 janvier 2025
760
10 mai 2021 à 18:14
10 mai 2021 à 18:14
Il ne faut pas la transférer mais démarrer dessus : Au démarrage, il faut appuyer sur une des touches de fonction (F1 à F12). Cela dépend de ton PC. Une fois dans le BIOS, tu cherches l'ordre de boot et tu mets la clé USB en premier.
Edit. Sur un MSI, cela pourrait être la touche SUPPR.
Edit. Sur un MSI, cela pourrait être la touche SUPPR.
Micho__
Messages postés
43
Date d'inscription
lundi 10 août 2020
Statut
Membre
Dernière intervention
18 mai 2021
10 mai 2021 à 22:09
10 mai 2021 à 22:09
Je vais dans boot ?
SATS_fr
Messages postés
4735
Date d'inscription
dimanche 15 mars 2020
Statut
Membre
Dernière intervention
12 janvier 2025
760
10 mai 2021 à 22:15
10 mai 2021 à 22:15
Oui, c'est cela. Éventuellement, tu fais des copies d'écrans, ce sera plus rapide.
Micho__
Messages postés
43
Date d'inscription
lundi 10 août 2020
Statut
Membre
Dernière intervention
18 mai 2021
18 mai 2021 à 10:35
18 mai 2021 à 10:35
SATS_fr
Messages postés
4735
Date d'inscription
dimanche 15 mars 2020
Statut
Membre
Dernière intervention
12 janvier 2025
760
>
Micho__
Messages postés
43
Date d'inscription
lundi 10 août 2020
Statut
Membre
Dernière intervention
18 mai 2021
18 mai 2021 à 10:53
18 mai 2021 à 10:53
Bonjour. Là, tu fais remonter la ligne USB CD/DVD en première position (boot option #1) en suivant le mode d'emploi situé dans le carré en bas à droite.
Micho__
Messages postés
43
Date d'inscription
lundi 10 août 2020
Statut
Membre
Dernière intervention
18 mai 2021
>
SATS_fr
Messages postés
4735
Date d'inscription
dimanche 15 mars 2020
Statut
Membre
Dernière intervention
12 janvier 2025
18 mai 2021 à 11:52
18 mai 2021 à 11:52
Je l'ai fais seulement ça n'as pas l'air d'avoir fait grand chose au démarrage
SATS_fr
Messages postés
4735
Date d'inscription
dimanche 15 mars 2020
Statut
Membre
Dernière intervention
12 janvier 2025
760
>
Micho__
Messages postés
43
Date d'inscription
lundi 10 août 2020
Statut
Membre
Dernière intervention
18 mai 2021
18 mai 2021 à 13:07
18 mai 2021 à 13:07
Une fois fait, tu as pensé à sauvegarder ?
Micho__
Messages postés
43
Date d'inscription
lundi 10 août 2020
Statut
Membre
Dernière intervention
18 mai 2021
>
SATS_fr
Messages postés
4735
Date d'inscription
dimanche 15 mars 2020
Statut
Membre
Dernière intervention
12 janvier 2025
18 mai 2021 à 13:29
18 mai 2021 à 13:29
Oui oui c'est bien discard changes and exit ?
SATS_fr
Messages postés
4735
Date d'inscription
dimanche 15 mars 2020
Statut
Membre
Dernière intervention
12 janvier 2025
760
18 mai 2021 à 21:23
18 mai 2021 à 21:23
Bonjour. C'est un peu ce que je craignais, c'est un problème matériel concernant la RAM.
Maintenant, soit c'est les barrettes et c'est récupérable, soit c'est un ou des slots et là c'est changement de carte-mère.
Si ton PC n'est plus sous garantie, ouvre-le, ce ne doit pas être très difficile. Repère les caractéristiques de tes barrettes et change-les. Si le problème n'est pas résolu, c'est la carte-mère qu'il faut changer, et là, c'est beaucoup plus compliqué.
Si le PC est sous garantie, retour SAV.
Maintenant, soit c'est les barrettes et c'est récupérable, soit c'est un ou des slots et là c'est changement de carte-mère.
Si ton PC n'est plus sous garantie, ouvre-le, ce ne doit pas être très difficile. Repère les caractéristiques de tes barrettes et change-les. Si le problème n'est pas résolu, c'est la carte-mère qu'il faut changer, et là, c'est beaucoup plus compliqué.
Si le PC est sous garantie, retour SAV.
8 mai 2021 à 15:22
8 mai 2021 à 15:43
Décompresse-le (avec 7Zip ou un autre utilitaire). Dans le répertoire décompressé, il y a un pdf avec le mode d'emploi.
8 mai 2021 à 17:38