Problème écran bleu au premier démarrage puis après redémarrage OK (PC monté)
Fermé
HolyDeamon
Messages postés
3
Date d'inscription
jeudi 26 novembre 2020
Statut
Membre
Dernière intervention
26 novembre 2020
-
26 nov. 2020 à 10:51
HolyDeamon - 10 déc. 2020 à 16:59
HolyDeamon - 10 déc. 2020 à 16:59
A voir également:
- Problème écran bleu au premier démarrage puis après redémarrage OK (PC monté)
- Pc lent au démarrage - Guide
- Double ecran pc - Guide
- Ecran noir demarrage pc - Guide
- Forcer demarrage pc - Guide
- Reinitialiser pc au demarrage - Guide
6 réponses
epango
Messages postés
37084
Date d'inscription
vendredi 24 août 2007
Statut
Membre
Dernière intervention
25 avril 2024
4 202
26 nov. 2020 à 12:01
26 nov. 2020 à 12:01
As-tu essayé de prendre les températures pour voir s'il n'y a pas de surchauffe?
billmaxime
Messages postés
49931
Date d'inscription
dimanche 20 novembre 2011
Statut
Contributeur
Dernière intervention
25 avril 2024
5 946
26 nov. 2020 à 22:56
26 nov. 2020 à 22:56
salut
télécharge WhoCrashed sur ton bureau --> clique ici
clique droit sur WhoCrashed, et choisi "exécuter en tant qu'administrateur"
poste le rapport via 1 copier/coller dans ta réponse
@+
télécharge WhoCrashed sur ton bureau --> clique ici
clique droit sur WhoCrashed, et choisi "exécuter en tant qu'administrateur"
poste le rapport via 1 copier/coller dans ta réponse
@+
HolyDeamon
Messages postés
3
Date d'inscription
jeudi 26 novembre 2020
Statut
Membre
Dernière intervention
26 novembre 2020
26 nov. 2020 à 23:03
26 nov. 2020 à 23:03
Crash dumps are enabled on your computer.
Crash dump directories:
C:\WINDOWS
C:\WINDOWS\Minidump
On Thu 26/11/2020 19:30:29 your computer crashed or a problem was reported
crash dump file: C:\WINDOWS\Minidump\112620-6343-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x3F5210)
Bugcheck code: 0x3B (0xC0000005, 0xFFFFF805580C711E, 0xFFFFB283C18C6CA0, 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 Thu 26/11/2020 19:30:29 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+0x8209)
Bugcheck code: 0x3B (0xC0000005, 0xFFFFF805580C711E, 0xFFFFB283C18C6CA0, 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 Wed 25/11/2020 08:39:52 your computer crashed or a problem was reported
crash dump file: C:\WINDOWS\Minidump\112520-6390-01.dmp
This was probably caused by the following module: win32kbase.sys (0xFFFFF88D86E902BA)
Bugcheck code: 0x3B (0xC0000005, 0xFFFFF88D86E902BA, 0xFFFFF98C49416E60, 0x0)
Error: SYSTEM_SERVICE_EXCEPTION
file path: C:\WINDOWS\system32\win32kbase.sys
product: Système d’exploitation Microsoft® Windows®
company: Microsoft Corporation
description: Pilote du noyau Base Win32k
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 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 Tue 24/11/2020 09:21:24 your computer crashed or a problem was reported
crash dump file: C:\WINDOWS\Minidump\112420-6828-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x3F5210)
Bugcheck code: 0x50 (0xFFFFDF8B84648A48, 0x0, 0xFFFFF805190D8DA6, 0x2)
Error: PAGE_FAULT_IN_NONPAGED_AREA
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 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 the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.
On Mon 23/11/2020 08:34:50 your computer crashed or a problem was reported
crash dump file: C:\WINDOWS\Minidump\112320-7687-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x3F5210)
Bugcheck code: 0x50 (0xFFFFBA8182851138, 0x0, 0xFFFFF8016C2D8DA6, 0x2)
Error: PAGE_FAULT_IN_NONPAGED_AREA
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 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 the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.
On Sun 22/11/2020 10:03:43 your computer crashed or a problem was reported
crash dump file: C:\WINDOWS\Minidump\112220-6390-01.dmp
This was probably caused by the following module: win32kfull.sys (0xFFFF923A4643543D)
Bugcheck code: 0x1E (0xFFFFFFFFC0000005, 0xFFFF923A4643543D, 0x0, 0xFFFFFFFFFFFFFFFF)
Error: KMODE_EXCEPTION_NOT_HANDLED
file path: C:\WINDOWS\system32\win32kfull.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: Full/Desktop Win32k Kernel Driver
Bug check description: This indicates that a kernel-mode program generated an exception which the error handler did not catch.
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.
The crash took place in a 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
--------------------------------------------------------------------------------
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 dump directories:
C:\WINDOWS
C:\WINDOWS\Minidump
On Thu 26/11/2020 19:30:29 your computer crashed or a problem was reported
crash dump file: C:\WINDOWS\Minidump\112620-6343-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x3F5210)
Bugcheck code: 0x3B (0xC0000005, 0xFFFFF805580C711E, 0xFFFFB283C18C6CA0, 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 Thu 26/11/2020 19:30:29 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+0x8209)
Bugcheck code: 0x3B (0xC0000005, 0xFFFFF805580C711E, 0xFFFFB283C18C6CA0, 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 Wed 25/11/2020 08:39:52 your computer crashed or a problem was reported
crash dump file: C:\WINDOWS\Minidump\112520-6390-01.dmp
This was probably caused by the following module: win32kbase.sys (0xFFFFF88D86E902BA)
Bugcheck code: 0x3B (0xC0000005, 0xFFFFF88D86E902BA, 0xFFFFF98C49416E60, 0x0)
Error: SYSTEM_SERVICE_EXCEPTION
file path: C:\WINDOWS\system32\win32kbase.sys
product: Système d’exploitation Microsoft® Windows®
company: Microsoft Corporation
description: Pilote du noyau Base Win32k
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 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 Tue 24/11/2020 09:21:24 your computer crashed or a problem was reported
crash dump file: C:\WINDOWS\Minidump\112420-6828-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x3F5210)
Bugcheck code: 0x50 (0xFFFFDF8B84648A48, 0x0, 0xFFFFF805190D8DA6, 0x2)
Error: PAGE_FAULT_IN_NONPAGED_AREA
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 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 the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.
On Mon 23/11/2020 08:34:50 your computer crashed or a problem was reported
crash dump file: C:\WINDOWS\Minidump\112320-7687-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x3F5210)
Bugcheck code: 0x50 (0xFFFFBA8182851138, 0x0, 0xFFFFF8016C2D8DA6, 0x2)
Error: PAGE_FAULT_IN_NONPAGED_AREA
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 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 the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.
On Sun 22/11/2020 10:03:43 your computer crashed or a problem was reported
crash dump file: C:\WINDOWS\Minidump\112220-6390-01.dmp
This was probably caused by the following module: win32kfull.sys (0xFFFF923A4643543D)
Bugcheck code: 0x1E (0xFFFFFFFFC0000005, 0xFFFF923A4643543D, 0x0, 0xFFFFFFFFFFFFFFFF)
Error: KMODE_EXCEPTION_NOT_HANDLED
file path: C:\WINDOWS\system32\win32kfull.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: Full/Desktop Win32k Kernel Driver
Bug check description: This indicates that a kernel-mode program generated an exception which the error handler did not catch.
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.
The crash took place in a 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
--------------------------------------------------------------------------------
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.
billmaxime
Messages postés
49931
Date d'inscription
dimanche 20 novembre 2011
Statut
Contributeur
Dernière intervention
25 avril 2024
5 946
26 nov. 2020 à 23:37
26 nov. 2020 à 23:37
re
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem
les causes de plantages/écran bleu peuvent être de diverses origines (matériel ou logiciel)
1 pilote/driver non reconnu, 1 problème matériel, 1 ventilo qui ne fait pas son boulot
tu peux faire des recherche sur le NET avec les codes d'erreurs --> nt+0x3F5210 et nt!setjmpex+0x8209
@+
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem
les causes de plantages/écran bleu peuvent être de diverses origines (matériel ou logiciel)
1 pilote/driver non reconnu, 1 problème matériel, 1 ventilo qui ne fait pas son boulot
tu peux faire des recherche sur le NET avec les codes d'erreurs --> nt+0x3F5210 et nt!setjmpex+0x8209
@+
Pour le problème matériel je pense que cela doit venir de ma ram. En effet j'ai un diagnostique et apparemment des problèmes ont été détectés, pour le pilote je ne vois pas trop et le ventilo à priori ils fonctionnement tous très bien, il y en a juste 2 dont le rgb n'est pas allumé (manque de place sur le commande pro de chez corsair), je vais faire quelques recherches
Vous n’avez pas trouvé la réponse que vous recherchez ?
Posez votre question
billmaxime
Messages postés
49931
Date d'inscription
dimanche 20 novembre 2011
Statut
Contributeur
Dernière intervention
25 avril 2024
5 946
26 nov. 2020 à 23:59
26 nov. 2020 à 23:59
re
je pense que cela doit venir de ma ram. En effet j'ai un diagnostique et apparemment des problèmes ont été détectés
tu as fait 1 test des barrettes de RAM avec MemTest?
regarde sur cette page --> clique ici
@+
je pense que cela doit venir de ma ram. En effet j'ai un diagnostique et apparemment des problèmes ont été détectés
tu as fait 1 test des barrettes de RAM avec MemTest?
regarde sur cette page --> clique ici
@+
Après changement des barrettes de ram par des nouvelles, le PC n'a plus de problème, plus d'écrans mort Windows au premier démarrage.
Les anciennes barrettes de RAM étaient donc défectueuses, j'ai effectué un retour auprès de amazon afin de me faire rembourser.
Les anciennes barrettes de RAM étaient donc défectueuses, j'ai effectué un retour auprès de amazon afin de me faire rembourser.
26 nov. 2020 à 14:29
Au repos (bureautique) ma carte graphique est environs à 28°
Mon processeur à environ 35°