BSOD
Krusty
-
Malekal_morte- Messages postés 178136 Date d'inscription Statut Modérateur, Contributeur sécurité Dernière intervention -
Malekal_morte- Messages postés 178136 Date d'inscription Statut Modérateur, Contributeur sécurité Dernière intervention -
Bonjour,
j'ai eu 4 BSOD depuis 1 semaine. Ci-dessous les dmp. Pensez vous probleme pilote, logiciel ou hardware ?
Merci d'avance
Crash Dump Analysis
--------------------------------------------------------------------------------
Crash dump directory: C:\WINDOWS\Minidump
Crash dumps are enabled on your computer.
On Mon 30/01/2017 20:45:10 your computer crashed
crash dump file: C:\WINDOWS\Minidump\013017-8078-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x14A6F0)
Bugcheck code: 0xA (0x80000000, 0xFF, 0x9A, 0xFFFFF801AA229BE2)
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.
On Sat 28/01/2017 15:15:53 your computer crashed
crash dump file: C:\WINDOWS\Minidump\012817-9234-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x14A6F0)
Bugcheck code: 0x12B (0xFFFFFFFFC00002C4, 0x7CB, 0x17BFEA30, 0xFFFFDC00ACFFE000)
Error: FAULTY_HARDWARE_CORRUPTED_PAGE
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 a single-bit error was found in this page. This is a hardware memory error.
This is likely to be caused by a hardware problem problem. This error suggests a case of memory corruption because of a hardware problem. It is suggested you do a test on your RAM modules (memory test).
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 24/01/2017 19:16:17 your computer crashed
crash dump file: C:\WINDOWS\Minidump\012417-7265-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x14A6F0)
Bugcheck code: 0x12B (0xFFFFFFFFC00002C4, 0x5E1, 0x23540F50, 0xFFFF8000F7523000)
Error: FAULTY_HARDWARE_CORRUPTED_PAGE
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 a single-bit error was found in this page. This is a hardware memory error.
This is likely to be caused by a hardware problem problem. This error suggests a case of memory corruption because of a hardware problem. It is suggested you do a test on your RAM modules (memory test).
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/01/2017 04:17:59 your computer crashed
crash dump file: C:\WINDOWS\Minidump\012217-12890-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x14A510)
Bugcheck code: 0x12B (0xFFFFFFFFC00002C4, 0xE67, 0x7507C960, 0xFFFF9580E5546000)
Error: FAULTY_HARDWARE_CORRUPTED_PAGE
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 a single-bit error was found in this page. This is a hardware memory error.
This is likely to be caused by a hardware problem problem. This error suggests a case of memory corruption because of a hardware problem. It is suggested you do a test on your RAM modules (memory test).
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 eu 4 BSOD depuis 1 semaine. Ci-dessous les dmp. Pensez vous probleme pilote, logiciel ou hardware ?
Merci d'avance
Crash Dump Analysis
--------------------------------------------------------------------------------
Crash dump directory: C:\WINDOWS\Minidump
Crash dumps are enabled on your computer.
On Mon 30/01/2017 20:45:10 your computer crashed
crash dump file: C:\WINDOWS\Minidump\013017-8078-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x14A6F0)
Bugcheck code: 0xA (0x80000000, 0xFF, 0x9A, 0xFFFFF801AA229BE2)
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.
On Sat 28/01/2017 15:15:53 your computer crashed
crash dump file: C:\WINDOWS\Minidump\012817-9234-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x14A6F0)
Bugcheck code: 0x12B (0xFFFFFFFFC00002C4, 0x7CB, 0x17BFEA30, 0xFFFFDC00ACFFE000)
Error: FAULTY_HARDWARE_CORRUPTED_PAGE
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 a single-bit error was found in this page. This is a hardware memory error.
This is likely to be caused by a hardware problem problem. This error suggests a case of memory corruption because of a hardware problem. It is suggested you do a test on your RAM modules (memory test).
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 24/01/2017 19:16:17 your computer crashed
crash dump file: C:\WINDOWS\Minidump\012417-7265-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x14A6F0)
Bugcheck code: 0x12B (0xFFFFFFFFC00002C4, 0x5E1, 0x23540F50, 0xFFFF8000F7523000)
Error: FAULTY_HARDWARE_CORRUPTED_PAGE
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 a single-bit error was found in this page. This is a hardware memory error.
This is likely to be caused by a hardware problem problem. This error suggests a case of memory corruption because of a hardware problem. It is suggested you do a test on your RAM modules (memory test).
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/01/2017 04:17:59 your computer crashed
crash dump file: C:\WINDOWS\Minidump\012217-12890-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x14A510)
Bugcheck code: 0x12B (0xFFFFFFFFC00002C4, 0xE67, 0x7507C960, 0xFFFF9580E5546000)
Error: FAULTY_HARDWARE_CORRUPTED_PAGE
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 a single-bit error was found in this page. This is a hardware memory error.
This is likely to be caused by a hardware problem problem. This error suggests a case of memory corruption because of a hardware problem. It is suggested you do a test on your RAM modules (memory test).
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
- Bsod - Guide
- Kb5063060 bsod - Guide
- Problème BSOD !!! - Forum Matériel & Système
- Kb5055627 bsod - Guide
- [Bsod] driver_power_state_failure ✓ - Forum Windows 10
4 réponses
Salut,
This is likely to be caused by a hardware problem problem. This error suggests a case of memory corruption because of a hardware problem. It is suggested you do a test on your RAM modules (memory test).
Vérifie ta mémoire avec memtest :
=> memtest
=> comment vérifier ses barettes de RAM avec Memtest
et pour voir :
Suis le tutoriel FRST. ( prends le temps de lire attentivement - tout y est bien expliqué ).
Télécharge et lance le scan FRST, 3 rapports FRST seront générés :
Envoie ces 3 rapports sur le site http://pjjoint.malekal.com/ et en retour donne les 3 liens pjjoint qui mènent aux rapports ici dans une nouvelle réponse afin que l'on puisse les consulter.
This is likely to be caused by a hardware problem problem. This error suggests a case of memory corruption because of a hardware problem. It is suggested you do a test on your RAM modules (memory test).
Vérifie ta mémoire avec memtest :
=> memtest
=> comment vérifier ses barettes de RAM avec Memtest
et pour voir :
Suis le tutoriel FRST. ( prends le temps de lire attentivement - tout y est bien expliqué ).
Télécharge et lance le scan FRST, 3 rapports FRST seront générés :
- FRST.txt
- Shortcut.txt
- Additionnal.txt
Envoie ces 3 rapports sur le site http://pjjoint.malekal.com/ et en retour donne les 3 liens pjjoint qui mènent aux rapports ici dans une nouvelle réponse afin que l'on puisse les consulter.
Bonjour et merci de votre réponse!
le memtest n'a pas trouvé d'erreur...
voici les liens demandés :
Additionnal : https://pjjoint.malekal.com/files.php?id=20170131_x10x5i8p9b5
FRST : https://pjjoint.malekal.com/files.php?id=FRST_20170131_q15n13q10n10g8
Shortcut : https://pjjoint.malekal.com/files.php?id=20170131_j9t8n7h8w8
le memtest n'a pas trouvé d'erreur...
voici les liens demandés :
Additionnal : https://pjjoint.malekal.com/files.php?id=20170131_x10x5i8p9b5
FRST : https://pjjoint.malekal.com/files.php?id=FRST_20170131_q15n13q10n10g8
Shortcut : https://pjjoint.malekal.com/files.php?id=20170131_j9t8n7h8w8
j'ai eu encore un BSOD :
On Mon 30/01/2017 21:05:44 your computer crashed
crash dump file: C:\WINDOWS\Minidump\013017-9093-01.dmp
This was probably caused by the following module: ndis.sys (ndis+0x6F80)
Bugcheck code: 0xC2 (0x7, 0xE5E5E5E5, 0xE5E5E5E5, 0xFFFFDE042DF0A6C0)
Error: BAD_POOL_CALLER
file path: C:\WINDOWS\system32\drivers\ndis.sys
product: Système d’exploitation Microsoft® Windows®
company: Microsoft Corporation
description: NDIS (Network Driver Interface Specification)
Bug check description: This indicates that the current thread is making a bad pool request.
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 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 Mon 30/01/2017 21:05:44 your computer crashed
crash dump file: C:\WINDOWS\Minidump\013017-9093-01.dmp
This was probably caused by the following module: ndis.sys (ndis+0x6F80)
Bugcheck code: 0xC2 (0x7, 0xE5E5E5E5, 0xE5E5E5E5, 0xFFFFDE042DF0A6C0)
Error: BAD_POOL_CALLER
file path: C:\WINDOWS\system32\drivers\ndis.sys
product: Système d’exploitation Microsoft® Windows®
company: Microsoft Corporation
description: NDIS (Network Driver Interface Specification)
Bug check description: This indicates that the current thread is making a bad pool request.
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 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.
