[BSOD][WhoCrashed]Windows 10 Ecran Bleu
TheGarious
Messages postés
8
Date d'inscription
Statut
Membre
Dernière intervention
-
didmed Messages postés 2668 Date d'inscription Statut Membre Dernière intervention -
didmed Messages postés 2668 Date d'inscription Statut Membre Dernière intervention -
Bonjour,
J'ai un soucis avec mon pc monté, cela fait quelques jours que j'enchaine les bsod et les reformatage de mon pc.
Maintenant je partage les erreurs pour voir si quelqu'un à la science infuse pour m'aider :).
--------------------------------------------------------------------------------
System Information (local)
--------------------------------------------------------------------------------
Computer name: DESKTOP-KQ8RDE1
Windows version: Windows 10 , 10.0, build: 14393
Windows dir: C:\Windows
Hardware: ASUSTeK COMPUTER INC., Z170 PRO GAMING
CPU: GenuineIntel Intel(R) Core(TM) i7-6700K CPU @ 4.00GHz Intel586, level: 6
8 logical processors, active mask: 255
RAM: 17115832320 bytes total
--------------------------------------------------------------------------------
Crash Dump Analysis
--------------------------------------------------------------------------------
Crash dump directory: C:\Windows\Minidump
Crash dumps are enabled on your computer.
On Tue 22/11/2016 19:42:19 your computer crashed
crash dump file: C:\Windows\Minidump\112216-37203-01.dmp
This was probably caused by the following module: ntfs.sys (NTFS+0x20913)
Bugcheck code: 0x19 (0xE, 0xFFFF968F355CC520, 0xA1C4BF534EE934BF, 0xA1C4BF534FE934BF)
Error: BAD_POOL_HEADER
file path: C:\Windows\system32\drivers\ntfs.sys
product: Système d’exploitation Microsoft® Windows®
company: Microsoft Corporation
description: Pilote du système de fichiers NT
Bug check description: This indicates that a pool header is corrupt.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem. This might be a case of memory corruption. More often memory corruption happens because of software errors in buggy drivers, not because of faulty RAM modules. This problem might also be caused because of overheating (thermal issue).
The crash took place in a standard 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 22/11/2016 19:42:19 your computer crashed
crash dump file: C:\Windows\memory.dmp
This was probably caused by the following module: ntfs.sys (NTFS+0x20913)
Bugcheck code: 0x19 (0xE, 0xFFFF968F355CC520, 0xA1C4BF534EE934BF, 0xA1C4BF534FE934BF)
Error: BAD_POOL_HEADER
file path: C:\Windows\system32\drivers\ntfs.sys
product: Système d’exploitation Microsoft® Windows®
company: Microsoft Corporation
description: Pilote du système de fichiers NT
Bug check description: This indicates that a pool header is corrupt.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem. This might be a case of memory corruption. More often memory corruption happens because of software errors in buggy drivers, not because of faulty RAM modules. This problem might also be caused because of overheating (thermal issue).
The crash took place in a standard 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 22/11/2016 00:47:27 your computer crashed
crash dump file: C:\Windows\Minidump\112216-19625-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x14A510)
Bugcheck code: 0xA (0xFFFFD30000028FE8, 0x2, 0x0, 0xFFFFF80003339092)
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 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.
J'ai un soucis avec mon pc monté, cela fait quelques jours que j'enchaine les bsod et les reformatage de mon pc.
Maintenant je partage les erreurs pour voir si quelqu'un à la science infuse pour m'aider :).
--------------------------------------------------------------------------------
System Information (local)
--------------------------------------------------------------------------------
Computer name: DESKTOP-KQ8RDE1
Windows version: Windows 10 , 10.0, build: 14393
Windows dir: C:\Windows
Hardware: ASUSTeK COMPUTER INC., Z170 PRO GAMING
CPU: GenuineIntel Intel(R) Core(TM) i7-6700K CPU @ 4.00GHz Intel586, level: 6
8 logical processors, active mask: 255
RAM: 17115832320 bytes total
--------------------------------------------------------------------------------
Crash Dump Analysis
--------------------------------------------------------------------------------
Crash dump directory: C:\Windows\Minidump
Crash dumps are enabled on your computer.
On Tue 22/11/2016 19:42:19 your computer crashed
crash dump file: C:\Windows\Minidump\112216-37203-01.dmp
This was probably caused by the following module: ntfs.sys (NTFS+0x20913)
Bugcheck code: 0x19 (0xE, 0xFFFF968F355CC520, 0xA1C4BF534EE934BF, 0xA1C4BF534FE934BF)
Error: BAD_POOL_HEADER
file path: C:\Windows\system32\drivers\ntfs.sys
product: Système d’exploitation Microsoft® Windows®
company: Microsoft Corporation
description: Pilote du système de fichiers NT
Bug check description: This indicates that a pool header is corrupt.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem. This might be a case of memory corruption. More often memory corruption happens because of software errors in buggy drivers, not because of faulty RAM modules. This problem might also be caused because of overheating (thermal issue).
The crash took place in a standard 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 22/11/2016 19:42:19 your computer crashed
crash dump file: C:\Windows\memory.dmp
This was probably caused by the following module: ntfs.sys (NTFS+0x20913)
Bugcheck code: 0x19 (0xE, 0xFFFF968F355CC520, 0xA1C4BF534EE934BF, 0xA1C4BF534FE934BF)
Error: BAD_POOL_HEADER
file path: C:\Windows\system32\drivers\ntfs.sys
product: Système d’exploitation Microsoft® Windows®
company: Microsoft Corporation
description: Pilote du système de fichiers NT
Bug check description: This indicates that a pool header is corrupt.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem. This might be a case of memory corruption. More often memory corruption happens because of software errors in buggy drivers, not because of faulty RAM modules. This problem might also be caused because of overheating (thermal issue).
The crash took place in a standard 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 22/11/2016 00:47:27 your computer crashed
crash dump file: C:\Windows\Minidump\112216-19625-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x14A510)
Bugcheck code: 0xA (0xFFFFD30000028FE8, 0x2, 0x0, 0xFFFFF80003339092)
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 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.
A voir également:
- [BSOD][WhoCrashed]Windows 10 Ecran Bleu
- Supprimer rond bleu whatsapp - Guide
- Clé d'activation windows 10 - Guide
- Restauration systeme windows 10 - Guide
- Ecran bleu windows 10 - Guide
- Windows 10 ne démarre plus - Guide
9 réponses
Salut
Utilises Memtest (en gravant l'ISO sur un CD ou une clé USB bootable par exemple) et testes la RAM (barrette par barrette):
https://www.commentcamarche.net/informatique/composants/1437-tester-la-memoire-vive-ram-d-un-ordinateur-avec-memtest86/
il faut modifier l'ordre de boot dans le BIOS/UEFI bien sûr.
@+
Utilises Memtest (en gravant l'ISO sur un CD ou une clé USB bootable par exemple) et testes la RAM (barrette par barrette):
https://www.commentcamarche.net/informatique/composants/1437-tester-la-memoire-vive-ram-d-un-ordinateur-avec-memtest86/
il faut modifier l'ordre de boot dans le BIOS/UEFI bien sûr.
@+
Si tu as reformaté et que cela continue, c'est un problème matériel
Pour être sûr, démarres en Mode sans échec avec prise en charge réseau >>>
Si le PC est stable, le problème est logiciel (drivers, Windows, programmes...)
Si le PC est instable avec BSOD, le problème est matériel (mémoire, carte-mère, alim)
@+
Pour être sûr, démarres en Mode sans échec avec prise en charge réseau >>>
Si le PC est stable, le problème est logiciel (drivers, Windows, programmes...)
Si le PC est instable avec BSOD, le problème est matériel (mémoire, carte-mère, alim)
@+
Possibly this problem is caused by another driver on your system that cannot be identified at this time.
Non
Non
les BSOD aléatoires et sans message convaincants sont les + ch.....
Et le Mode sans échec est tlimité...
Donc c'est la joie !
@+
Et le Mode sans échec est tlimité...
Donc c'est la joie !
@+
Vous n’avez pas trouvé la réponse que vous recherchez ?
Posez votre question
Merci de ta réponse, j'ai déjà tester la RAM sans soucis apparent.