BSOD en boucle
Melway
Messages postés
8
Date d'inscription
Statut
Membre
Dernière intervention
-
Melway Messages postés 8 Date d'inscription Statut Membre Dernière intervention -
Melway Messages postés 8 Date d'inscription Statut Membre Dernière intervention -
Bonjour, depuis samedi soir mon pc crash en boucle , à chaque fois qu'il redémarre j'ai le temps de voir le bureau quelques seconde puis j'ai un blue screen. J'ai tenté de réinstaller Windows plusieurs fois (avec une clé bootable et formatage complet des ssd) et j'ai aussi reset le bios en enlevant la pile mais le problème persiste.
J'ai aussi testé la ram avec Memtest86 mais il n'a trouvé aucune erreur.
Quand je lance Windows en mode sans échec, je n'ai pas de crash.
Ma config:
- ryzen 5 5600x
- 2x 8Go corsair vengence
- 2x corsair mp600 core 1to
- carte maire Asus Prime-p x570
- Nvidia Gforce 750ti (pas d'info sur la marque je l' ai récupérée d'un pc premontè)
Merci d'avance.
J'ai aussi testé la ram avec Memtest86 mais il n'a trouvé aucune erreur.
Quand je lance Windows en mode sans échec, je n'ai pas de crash.
Ma config:
- ryzen 5 5600x
- 2x 8Go corsair vengence
- 2x corsair mp600 core 1to
- carte maire Asus Prime-p x570
- Nvidia Gforce 750ti (pas d'info sur la marque je l' ai récupérée d'un pc premontè)
Merci d'avance.
6 réponses
epango
Messages postés
37504
Date d'inscription
Statut
Membre
Dernière intervention
Ambassadeur
4 246
Quelle alimentation as-tu (marque et modèle)?
Melway
Messages postés
8
Date d'inscription
Statut
Membre
Dernière intervention
C'est une corsair RM850
Tu n'as pas installé la version 1507, tu as bien utilisé la dernière version avec ce lien ?
https://www.microsoft.com/fr-fr/software-download/windows10/
Tu peux tester ton disque avec CrystalDiskInfo
https://www.microsoft.com/fr-fr/software-download/windows10/
Tu peux tester ton disque avec CrystalDiskInfo
Utilises l'outil pour créer une Clé USB pour mettre à jour, réparer, ou réinstaller Windows
Windows 11 si compatible, tu peux voir avec WhyNotWin11
https://github.com/rcmaehl/WhyNotWin11/releases
Windows 10 https://www.microsoft.com/fr-fr/software-download/windows10/
Windows 11 https://www.microsoft.com/fr-fr/software-download/windows11
Si tu a déjà le fichier ISO de Windows que tu peux télécharger à partir de l'outil, tu peux créer ta clé USB avec Rufus
Si le PC est ancien, il faut créer la clé en mode MBR
Si il est récent (Windows 8 ou supérieur) en mode GPT > Pour Windows 11 GPT
Démarres dessus par le Boot Menu du PC
https://www.malekal.com/liste-touches-acces-bios-boot-menu-constructeur/
Si tu ne vois pas, tu peux chercher sur Google "[Marque Modèle] Boot Menu Key"
Choisis "Installation personnalisée" (Pas mise à niveau)
Pas obligé de formater si il y a de l'espace, si il y a des données, elles se retrouveront dans un dossier Windows.old
Installes sur la même partition, ou au choix, supprimes toutes les partitions système et crées en une nouvelle (Supprime les données).
Windows 11 si compatible, tu peux voir avec WhyNotWin11
https://github.com/rcmaehl/WhyNotWin11/releases
Windows 10 https://www.microsoft.com/fr-fr/software-download/windows10/
Windows 11 https://www.microsoft.com/fr-fr/software-download/windows11
Si tu a déjà le fichier ISO de Windows que tu peux télécharger à partir de l'outil, tu peux créer ta clé USB avec Rufus
Si le PC est ancien, il faut créer la clé en mode MBR
Si il est récent (Windows 8 ou supérieur) en mode GPT > Pour Windows 11 GPT
Démarres dessus par le Boot Menu du PC
https://www.malekal.com/liste-touches-acces-bios-boot-menu-constructeur/
Si tu ne vois pas, tu peux chercher sur Google "[Marque Modèle] Boot Menu Key"
Choisis "Installation personnalisée" (Pas mise à niveau)
Pas obligé de formater si il y a de l'espace, si il y a des données, elles se retrouveront dans un dossier Windows.old
Installes sur la même partition, ou au choix, supprimes toutes les partitions système et crées en une nouvelle (Supprime les données).
Vous n’avez pas trouvé la réponse que vous recherchez ?
Posez votre question
Note:
Tu peux télécharger l'ISO de Windows et le vérifier avec 7-Zip > Tester
Tu peux formater ta clé et ensuite la tester avec h2testw
Tu peux télécharger l'ISO de Windows et le vérifier avec 7-Zip > Tester
Tu peux formater ta clé et ensuite la tester avec h2testw
J'ai réinstallé windows 10 et réessayé d'utiliser WhoCrashed.
Voici ce qu'il me dit:
On Tue 30-11-21 17:50:09 your computer crashed or a problem was reported
crash dump file: C:\Windows\Minidump\113021-3687-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x3F72A0)
Bugcheck code: 0x3B (0xC0000005, 0xFFFFF80033407FDF, 0xFFFF848C54EF69E0, 0x0)
Error: SYSTEM_SERVICE_EXCEPTION
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 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 the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.
On Tue 30-11-21 17:50:09 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!setjmpex+0x8279)
Bugcheck code: 0x3B (0xC0000005, 0xFFFFF80033407FDF, 0xFFFF848C54EF69E0, 0x0)
Error: SYSTEM_SERVICE_EXCEPTION
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 the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.
On Tue 30-11-21 17:49:27 your computer crashed or a problem was reported
crash dump file: C:\Windows\Minidump\113021-3734-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x3F72A0)
Bugcheck code: 0xA (0x4FC8FAE8, 0xFF, 0x0, 0xFFFFF8017741715E)
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 Tue 30-11-21 17:18:47 your computer crashed or a problem was reported
crash dump file: C:\Windows\Minidump\113021-3546-01.dmp
This was probably caused by the following module: fltmgr.sys (0xFFFFF8053F8E6723)
Bugcheck code: 0x3B (0xC0000005, 0xFFFFF8053F8E6723, 0xFFFFF306E74F6510, 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 Tue 30-11-21 17:16:51 your computer crashed or a problem was reported
crash dump file: C:\Windows\Minidump\113021-2890-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x3F72A0)
Bugcheck code: 0x162 (0xFFFFB08C2F3C3080, 0xFFFFC2A1C06063A8, 0x1, 0x0)
Error: KERNEL_AUTO_BOOST_INVALID_LOCK_RELEASE
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 lock tracked by AutoBoost was released by a thread that did not own the lock.
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 Tue 30-11-21 17:14:04 your computer crashed or a problem was reported
crash dump file: C:\Windows\Minidump\113021-3125-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x3F72A0)
Bugcheck code: 0x3B (0xC0000005, 0xFFFFF8013326F7B7, 0xFFFFBC8DBDB2F030, 0x0)
Error: SYSTEM_SERVICE_EXCEPTION
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 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 the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.
Voici ce qu'il me dit:
On Tue 30-11-21 17:50:09 your computer crashed or a problem was reported
crash dump file: C:\Windows\Minidump\113021-3687-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x3F72A0)
Bugcheck code: 0x3B (0xC0000005, 0xFFFFF80033407FDF, 0xFFFF848C54EF69E0, 0x0)
Error: SYSTEM_SERVICE_EXCEPTION
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 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 the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.
On Tue 30-11-21 17:50:09 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!setjmpex+0x8279)
Bugcheck code: 0x3B (0xC0000005, 0xFFFFF80033407FDF, 0xFFFF848C54EF69E0, 0x0)
Error: SYSTEM_SERVICE_EXCEPTION
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 the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.
On Tue 30-11-21 17:49:27 your computer crashed or a problem was reported
crash dump file: C:\Windows\Minidump\113021-3734-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x3F72A0)
Bugcheck code: 0xA (0x4FC8FAE8, 0xFF, 0x0, 0xFFFFF8017741715E)
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 Tue 30-11-21 17:18:47 your computer crashed or a problem was reported
crash dump file: C:\Windows\Minidump\113021-3546-01.dmp
This was probably caused by the following module: fltmgr.sys (0xFFFFF8053F8E6723)
Bugcheck code: 0x3B (0xC0000005, 0xFFFFF8053F8E6723, 0xFFFFF306E74F6510, 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 Tue 30-11-21 17:16:51 your computer crashed or a problem was reported
crash dump file: C:\Windows\Minidump\113021-2890-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x3F72A0)
Bugcheck code: 0x162 (0xFFFFB08C2F3C3080, 0xFFFFC2A1C06063A8, 0x1, 0x0)
Error: KERNEL_AUTO_BOOST_INVALID_LOCK_RELEASE
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 lock tracked by AutoBoost was released by a thread that did not own the lock.
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 Tue 30-11-21 17:14:04 your computer crashed or a problem was reported
crash dump file: C:\Windows\Minidump\113021-3125-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x3F72A0)
Bugcheck code: 0x3B (0xC0000005, 0xFFFFF8013326F7B7, 0xFFFFBC8DBDB2F030, 0x0)
Error: SYSTEM_SERVICE_EXCEPTION
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 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 the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.
fltmgr.sys == Filesystem Filter Manager
Comment as tu testée ta RAM avec Memtest, en USB ou dans Windows ?
Tu peux le refaire avec Memtest86 Free USB sur clé USB à droite >
https://www.memtest86.com/download.htm
Démarres dessus par le Boot Menu du PC
https://www.malekal.com/liste-touches-acces-bios-boot-menu-constructeur/
Si tu ne vois pas, tu peux chercher sur Google "[Marque Modèle] Boot Menu Key"
Quoi que WhoCrashed dit que c'est plutôt comme un genre de un bug Software...
This indicates that an exception happened while executing a routine that transitions from non-privileged code to privileged code.
Comment as tu testée ta RAM avec Memtest, en USB ou dans Windows ?
Tu peux le refaire avec Memtest86 Free USB sur clé USB à droite >
https://www.memtest86.com/download.htm
Démarres dessus par le Boot Menu du PC
https://www.malekal.com/liste-touches-acces-bios-boot-menu-constructeur/
Si tu ne vois pas, tu peux chercher sur Google "[Marque Modèle] Boot Menu Key"
Quoi que WhoCrashed dit que c'est plutôt comme un genre de un bug Software...
This indicates that an exception happened while executing a routine that transitions from non-privileged code to privileged code.
