Blue Screen

Signaler
Messages postés
4
Date d'inscription
mercredi 15 janvier 2020
Statut
Membre
Dernière intervention
18 janvier 2020
-
Malekal_morte-
Messages postés
174301
Date d'inscription
mercredi 17 mai 2006
Statut
Modérateur, Contributeur sécurité
Dernière intervention
25 janvier 2020
-
Salut,
J'ai récemment mit un nouveau proco, cm ram et alim dans mon pc, et j'ai eu quelques BDOS... help !
Memory Managment

Et WhoCrashed :

'''Crash dumps are enabled on your computer. This system is not configured for complete or automatic crash dumps. For best results, configure your system to write out complete or automatic crash dumps. Select Tools->Crash Dump Configuration from the main menu to configure your system to write out complete memory dumps.

Crash dump directories:
C:\WINDOWS
C:\WINDOWS\Minidump

On Wed 15/01/2020 17:38:16 your computer crashed or a problem was reported
crash dump file: C:\WINDOWS\Minidump\011520-13015-01.dmp
This was probably caused by the following module: hardware.sys (hardware)
Bugcheck code: 0x1A (0x41792, 0xFFFF9580006BE008, 0x20000000, 0x0)
Error: MEMORY_MANAGEMENT
Bug check description: This indicates that a severe memory management error occurred. A corrupted PTE has been detected.
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. This problem might also be caused because of overheating (thermal issue).
A third party driver was identified as the probable root cause of this system error. It is suggested you look for an update for the following driver: hardware.sys .
Google query: hardware.sys MEMORY_MANAGEMENT

On Sun 12/01/2020 19:14:52 your computer crashed or a problem was reported
crash dump file: C:\WINDOWS\Minidump\011220-28578-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x1C14E0)
Bugcheck code: 0x1A (0x41201, 0xFFFFDE8103AF7108, 0x810000021CF64867, 0xFFFFE1873C5899C0)
Error: MEMORY_MANAGEMENT
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 severe memory management error occurred.
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. This problem might also be caused because of overheating (thermal issue).
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 11/01/2020 23:58:25 your computer crashed or a problem was reported
crash dump file: C:\WINDOWS\Minidump\011120-28843-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x1C14E0)
Bugcheck code: 0x1A (0x6000, 0xFFFF988ABB3A8D40, 0xFFFFFFFFC0000225, 0x0)
Error: MEMORY_MANAGEMENT
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 severe memory management error occurred.
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. This problem might also be caused because of overheating (thermal issue).
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 08/01/2020 15:24:40 your computer crashed or a problem was reported
crash dump file: C:\WINDOWS\Minidump\010820-28328-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x1C14E0)
Bugcheck code: 0x1A (0x41201, 0xFFFFBD00C60D2108, 0x86000003073C9847, 0xFFFFAD0F4EB15C90)
Error: MEMORY_MANAGEMENT
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 severe memory management error occurred.
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. This problem might also be caused because of overheating (thermal issue).
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 02/01/2020 18:56:53 your computer crashed or a problem was reported
crash dump file: C:\WINDOWS\Minidump\010220-27265-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x1C14E0)
Bugcheck code: 0x4E (0x99, 0x736EB, 0x2, 0xC000360003668EA)
Error: PFN_LIST_CORRUPT
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 the page frame number (PFN) list is corrupted.
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 31/12/2019 16:55:36 your computer crashed or a problem was reported
crash dump file: C:\WINDOWS\Minidump\123119-28750-01.dmp
This was probably caused by the following module: hardware.sys (hardware)
Bugcheck code: 0x1A (0x41792, 0xFFFF823FFC8B6008, 0x20000000, 0x0)
Error: MEMORY_MANAGEMENT
Bug check description: This indicates that a severe memory management error occurred. A corrupted PTE has been detected.
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. This problem might also be caused because of overheating (thermal issue).
A third party driver was identified as the probable root cause of this system error. It is suggested you look for an update for the following driver: hardware.sys .
Google query: hardware.sys MEMORY_MANAGEMENT

On Mon 30/12/2019 19:23:01 your computer crashed or a problem was reported
crash dump file: C:\WINDOWS\Minidump\123019-28375-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x1C14E0)
Bugcheck code: 0x4E (0x99, 0x7E2C8, 0x2, 0xC000100001091C7)
Error: PFN_LIST_CORRUPT
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 the page frame number (PFN) list is corrupted.
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.'''

1 réponse

Messages postés
174301
Date d'inscription
mercredi 17 mai 2006
Statut
Modérateur, Contributeur sécurité
Dernière intervention
25 janvier 2020
19 123
Bonsoir,

Vérifie l'état de santé de tes barrettes de mémoire :
- memtest : vérifier barette de mémoire (malekal.com)
- memtest : vérifier barette de mémoire (CCM)
Utilise bien memtest86+ et pas celui de Windows


Malekal_morte-
Messages postés
174301
Date d'inscription
mercredi 17 mai 2006
Statut
Modérateur, Contributeur sécurité
Dernière intervention
25 janvier 2020
19 123 > leahpaR_
Messages postés
4
Date d'inscription
mercredi 15 janvier 2020
Statut
Membre
Dernière intervention
18 janvier 2020

Tu as surement une barrette de mémoire qui plante.
donc oui faut vérifier cela.
leahpaR_
Messages postés
4
Date d'inscription
mercredi 15 janvier 2020
Statut
Membre
Dernière intervention
18 janvier 2020
> Malekal_morte-
Messages postés
174301
Date d'inscription
mercredi 17 mai 2006
Statut
Modérateur, Contributeur sécurité
Dernière intervention
25 janvier 2020

Salut, désolé pour la réponse tardive. Il n'y a aucune erreur... Une autre idée ?
Malekal_morte-
Messages postés
174301
Date d'inscription
mercredi 17 mai 2006
Statut
Modérateur, Contributeur sécurité
Dernière intervention
25 janvier 2020
19 123 > leahpaR_
Messages postés
4
Date d'inscription
mercredi 15 janvier 2020
Statut
Membre
Dernière intervention
18 janvier 2020

oui tu testes le PC plusieurs heures avec une seule barrette à la fois
voir si les BSOD s'arrêtent avec une en particulier.
leahpaR_
Messages postés
4
Date d'inscription
mercredi 15 janvier 2020
Statut
Membre
Dernière intervention
18 janvier 2020
> Malekal_morte-
Messages postés
174301
Date d'inscription
mercredi 17 mai 2006
Statut
Modérateur, Contributeur sécurité
Dernière intervention
25 janvier 2020

Pourquoi une seule barrette ? Si je renvoie les barrettes a corsair je doit renvoyer les 2... C'est pas le HDD ?
Malekal_morte-
Messages postés
174301
Date d'inscription
mercredi 17 mai 2006
Statut
Modérateur, Contributeur sécurité
Dernière intervention
25 janvier 2020
19 123 > leahpaR_
Messages postés
4
Date d'inscription
mercredi 15 janvier 2020
Statut
Membre
Dernière intervention
18 janvier 2020

Pour voir si une des deux provoquent les BSOD.