Blue screen of death qui survient régulièrement !
Duke15
Messages postés
3
Date d'inscription
Statut
Membre
Dernière intervention
-
jeanbern Messages postés 13848 Date d'inscription Statut Contributeur Dernière intervention -
jeanbern Messages postés 13848 Date d'inscription Statut Contributeur Dernière intervention -
Bonjour,
J'explique la situation. J'ai fait l'acquisition d'un PC il y a tout juste 3 semaines.
Le PC était vendu sans Windows, chose qui été résolu lorsque j'ai installé Windows 10 par moi même.
Ainsi, j'installe majoritairement des jeux étant un joueur et je me mets donc à jouer et là, le problème survient: aléatoirement, le PC a un blue screen. Dans la majorité des cas, lorsque le PC redémarre, un autre blue screen différent intervient au redémarrage.
Je laisse donc ma config ainsi que le rapport WhoCrashed si quelqu'un est bien motivé à m'aider.
CONFIGURATION:
Windows version: Windows 10 , 10.0, build: 17134
Windows dir: C:\Windows
Hardware: ASUSTeK COMPUTER INC., ROG STRIX Z370-F GAMING
CPU: GenuineIntel Intel(R) Core(TM) i7-8700K CPU @ 3.70GHz Intel586, level: 6
12 logical processors, active mask: 4095
RAM: 17112158208 bytes total
RAPPORTS WHOCRASHED:
On Sun 09/09/2018 00:40:19 your computer crashed or a problem was reported
crash dump file: C:\Windows\Minidump\090918-4281-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x1A8CA0)
Bugcheck code: 0xA (0x27, 0x2, 0x1, 0xFFFFF802686753FB)
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 Sun 09/09/2018 00:40:19 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+0x7489)
Bugcheck code: 0xA (0x27, 0x2, 0x1, 0xFFFFF802686753FB)
Error: IRQL_NOT_LESS_OR_EQUAL
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 Sun 09/09/2018 00:39:02 your computer crashed or a problem was reported
crash dump file: C:\Windows\Minidump\090918-4000-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x1A8CA0)
Bugcheck code: 0x7F (0x8, 0xFFFFBD816D871150, 0x400E79ED, 0xFFFFF8005A506F1F)
Error: UNEXPECTED_KERNEL_MODE_TRAP
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 the Intel CPU generated a trap and the kernel failed to catch this trap.Double Fault, indicates that an exception occurs during a call to the handler for a prior exception. Most often this is caused by a software problem (kernel stack overflow) but this can also 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 09/09/2018 00:35:49 your computer crashed or a problem was reported
crash dump file: C:\Windows\Minidump\090918-4375-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x1A8CA0)
Bugcheck code: 0xA (0x1, 0x2, 0x0, 0xFFFFF800CB868988)
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 Sun 09/09/2018 00:31:08 your computer crashed or a problem was reported
crash dump file: C:\Windows\Minidump\090918-4359-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x1A8CA0)
Bugcheck code: 0x3B (0xC0000005, 0xFFFFF80164AAB96A, 0xFFFF83061AB698B0, 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 Sun 09/09/2018 00:30:13 your computer crashed or a problem was reported
crash dump file: C:\Windows\Minidump\090918-4234-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x1A8CA0)
Bugcheck code: 0x7F (0x8, 0xFFFF9D007F9A0150, 0xBBA4F658, 0xFFFFF800FB7C70CA)
Error: UNEXPECTED_KERNEL_MODE_TRAP
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 the Intel CPU generated a trap and the kernel failed to catch this trap.Double Fault, indicates that an exception occurs during a call to the handler for a prior exception. Most often this is caused by a software problem (kernel stack overflow) but this can also 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.
J'explique la situation. J'ai fait l'acquisition d'un PC il y a tout juste 3 semaines.
Le PC était vendu sans Windows, chose qui été résolu lorsque j'ai installé Windows 10 par moi même.
Ainsi, j'installe majoritairement des jeux étant un joueur et je me mets donc à jouer et là, le problème survient: aléatoirement, le PC a un blue screen. Dans la majorité des cas, lorsque le PC redémarre, un autre blue screen différent intervient au redémarrage.
Je laisse donc ma config ainsi que le rapport WhoCrashed si quelqu'un est bien motivé à m'aider.
CONFIGURATION:
Windows version: Windows 10 , 10.0, build: 17134
Windows dir: C:\Windows
Hardware: ASUSTeK COMPUTER INC., ROG STRIX Z370-F GAMING
CPU: GenuineIntel Intel(R) Core(TM) i7-8700K CPU @ 3.70GHz Intel586, level: 6
12 logical processors, active mask: 4095
RAM: 17112158208 bytes total
RAPPORTS WHOCRASHED:
On Sun 09/09/2018 00:40:19 your computer crashed or a problem was reported
crash dump file: C:\Windows\Minidump\090918-4281-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x1A8CA0)
Bugcheck code: 0xA (0x27, 0x2, 0x1, 0xFFFFF802686753FB)
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 Sun 09/09/2018 00:40:19 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+0x7489)
Bugcheck code: 0xA (0x27, 0x2, 0x1, 0xFFFFF802686753FB)
Error: IRQL_NOT_LESS_OR_EQUAL
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 Sun 09/09/2018 00:39:02 your computer crashed or a problem was reported
crash dump file: C:\Windows\Minidump\090918-4000-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x1A8CA0)
Bugcheck code: 0x7F (0x8, 0xFFFFBD816D871150, 0x400E79ED, 0xFFFFF8005A506F1F)
Error: UNEXPECTED_KERNEL_MODE_TRAP
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 the Intel CPU generated a trap and the kernel failed to catch this trap.Double Fault, indicates that an exception occurs during a call to the handler for a prior exception. Most often this is caused by a software problem (kernel stack overflow) but this can also 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 09/09/2018 00:35:49 your computer crashed or a problem was reported
crash dump file: C:\Windows\Minidump\090918-4375-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x1A8CA0)
Bugcheck code: 0xA (0x1, 0x2, 0x0, 0xFFFFF800CB868988)
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 Sun 09/09/2018 00:31:08 your computer crashed or a problem was reported
crash dump file: C:\Windows\Minidump\090918-4359-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x1A8CA0)
Bugcheck code: 0x3B (0xC0000005, 0xFFFFF80164AAB96A, 0xFFFF83061AB698B0, 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 Sun 09/09/2018 00:30:13 your computer crashed or a problem was reported
crash dump file: C:\Windows\Minidump\090918-4234-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x1A8CA0)
Bugcheck code: 0x7F (0x8, 0xFFFF9D007F9A0150, 0xBBA4F658, 0xFFFFF800FB7C70CA)
Error: UNEXPECTED_KERNEL_MODE_TRAP
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 the Intel CPU generated a trap and the kernel failed to catch this trap.Double Fault, indicates that an exception occurs during a call to the handler for a prior exception. Most often this is caused by a software problem (kernel stack overflow) but this can also 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.
A voir également:
- Blue screen of death qui survient régulièrement !
- Blue screen windows 10 - Guide
- Screen whatsapp - Accueil - Messagerie instantanée
- Apowersoft screen recorder - Télécharger - Capture d'écran
- Blue iris - Télécharger - Divers Utilitaires
- Double screen pc - Guide
2 réponses
Salut
Description du bogue: cette vérification des bogues indique que le processeur Intel a généré un "piège" et que le noyau n'a pas réussi à intercepter ce piège. Double faute, indique qu'une exception se produit lors d'un appel au gestionnaire pour une exception antérieure. Le plus souvent, cela est causé par un problème logiciel (débordement de pile du noyau), mais cela peut également être causée par un problème matériel.
Le crash a eu lieu dans le noyau Windows. Peut-être que ce problème est causé par un autre pilote qui ne peut pas être identifié à ce moment.
Commence par changer ta pile 2032 (normalement)
Description du bogue: cette vérification des bogues indique que le processeur Intel a généré un "piège" et que le noyau n'a pas réussi à intercepter ce piège. Double faute, indique qu'une exception se produit lors d'un appel au gestionnaire pour une exception antérieure. Le plus souvent, cela est causé par un problème logiciel (débordement de pile du noyau), mais cela peut également être causée par un problème matériel.
Le crash a eu lieu dans le noyau Windows. Peut-être que ce problème est causé par un autre pilote qui ne peut pas être identifié à ce moment.
Commence par changer ta pile 2032 (normalement)
Ensuite fais un clic droit "propriétés" et avancées : que dit-il ?
Combien de port USB as tu en tout ?
Et j'ai 8 ports USB sur ma tour.