Forum |  HardWare.fr | News | Articles | PC | S'identifier | S'inscrire | Shop Recherche
1708 connectés 

  FORUM HardWare.fr
  Windows & Software
  Win 10

  Nombreux BSOD ss win10

 


 Mot :   Pseudo :  
 
Bas de page
Auteur Sujet :

Nombreux BSOD ss win10

n°3350729
napster13
Posté le 18-08-2019 à 16:07:14  profilanswer
 

Bonjour,
 
J'ai une config neuve mais j'ai un souci.
J'ai reformater mon PC x fois.
J'ai de nombreux BSOD et mon pc plante très très souvent.
 
J'ai testé la ram via l'utilitaire windows.. RAS
 
Ma config :  
AMD RYZEN 7 2700
MSI B450 ARMOR  GAMING PLUS
MSI GTX 1080 ARMOR 8GO OC
RAM HYPERX FURY 32GO 4*8GO  
ALIM NZXT 500W
 
Les barettes de ram sont overclockable j'ai donc désactivé l'OC via la carte mère pour essayer de voir si cela venez de la..
 
Je ne sait pas du tout d'ou cela viens..
J'ai fait un diag via whocrashed mais pas de solution..
 
Merci par avance,
Cordialement,

mood
Publicité
Posté le 18-08-2019 à 16:07:14  profilanswer
 

n°3350730
Profil sup​primé
Posté le 18-08-2019 à 16:33:36  answer
 

alim 500w  
pour une 1080 et cpu AMD sa pompe aussi ?
 
ta check tes voltages ?
si ta moyen de testé une plus grosse alim


Message édité par Profil supprimé le 18-08-2019 à 16:35:15
n°3350731
leroimerli​nbis
Posté le 18-08-2019 à 17:03:29  profilanswer
 

napster13 a écrit :

Bonjour,
 
J'ai une config neuve mais j'ai un souci.
J'ai reformater mon PC x fois.
J'ai de nombreux BSOD et mon pc plante très très souvent.
 
J'ai testé la ram via l'utilitaire windows.. RAS
 
Ma config :  
AMD RYZEN 7 2700
MSI B450 ARMOR  GAMING PLUS
MSI GTX 1080 ARMOR 8GO OC
RAM HYPERX FURY 32GO 4*8GO  
ALIM NZXT 500W
 
Les barettes de ram sont overclockable j'ai donc désactivé l'OC via la carte mère pour essayer de voir si cela venez de la..
 
Je ne sait pas du tout d'ou cela viens..
J'ai fait un diag via whocrashed mais pas de solution..
 
Merci par avance,
Cordialement,


 
"overlockées" tu veux dire.
 
y a des chances que ça vienne de là oui.
Et overlockée la RAM ne sert à rien, avec le risque de plantage en plus..

n°3350734
napster13
Posté le 18-08-2019 à 17:32:54  profilanswer
 

Merci pour vos réponses. J'ai viré l'overclock des rams..
Pour ce qui est de l'alimentation, comment vérifier qu'elle soit assez puissante pour supporter tous le matos ?
 
Merci les gars.

n°3350751
Profil sup​primé
Posté le 18-08-2019 à 20:35:39  answer
 

normalement ta les voltages dans le bios de la CM
fouille regarder deja si t'est a 5.0x volts ,12.1 ? v ? 3.3v ?
 
apres ta des outils sous windows
https://www.commentcamarche.net/dow [...] 60203-occt
 
ta les tensions ,et apres tu peu charger ton CPU ou ta CG
check les T° et les voltages sur 30min

n°3350768
nex84
Dura lex, sed lex
Posté le 19-08-2019 à 09:27:40  profilanswer
 

Le rapport de Whocrashed, il dit quoi ?


---------------
#TeamNoBidouille || Come to the Dark Side, we have cookies || Mangez 5 fruits et légumes par an ! || Le digital, c'est les doigts
n°3350825
ZYX68
Posté le 19-08-2019 à 21:32:19  profilanswer
 

As-tu installé les softs MSI ?

n°3350985
napster13
Posté le 22-08-2019 à 11:17:06  profilanswer
 

Bonjour,
 
Voici le rapport WHOSCRASHED :  
 
System Information (local)
--------------------------------------------------------------------------------
 
Computer name: DESKTOP-0G72RIS
Windows version: Windows 10 , 10.0, version 1903, build: 18362
Windows dir: C:\Windows
Hardware: MS-7B86, Micro-Star International Co., Ltd, B450 GAMING PLUS (MS-7B86)
CPU: AuthenticAMD AMD Ryzen 7 2700 Eight-Core Processor AMD8664, level: 23
16 logical processors, active mask: 65535
RAM: 34308100096 bytes (32,0GB)
 
 
 
 
--------------------------------------------------------------------------------
Crash Dump Analysis
--------------------------------------------------------------------------------
 
Crash dumps are enabled on your computer.  
 
Crash dump directories:  
C:\Windows
C:\Windows\Minidump
 
On Thu 22/08/2019 11:04:23 your computer crashed or a problem was reported
crash dump file: C:\Windows\Minidump\082219-6390-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x1BFCC0)  
Bugcheck code: 0x13A (0x9, 0xFFFFB20C32000000, 0xFFFFB20C432425C0, 0x0)
Error: KERNEL_MODE_HEAP_CORRUPTION
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 kernel mode heap manager has detected corruption in a heap.  
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 22/08/2019 11:04:23 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!RtlTraceDatabaseValidate+0x5C48)  
Bugcheck code: 0x13A (0x9, 0xFFFFB20C32000000, 0xFFFFB20C432425C0, 0x0)
Error: KERNEL_MODE_HEAP_CORRUPTION
Bug check description: This indicates that the kernel mode heap manager has detected corruption in a heap.  
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 18/08/2019 18:45:05 your computer crashed or a problem was reported
crash dump file: C:\Windows\Minidump\081819-6640-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x1BFCC0)  
Bugcheck code: 0xDE (0x2, 0xFFFF8402CB1C5D38, 0xFFFF8402CB1C6480, 0x3EBD818C0)
Error: POOL_CORRUPTION_IN_FILE_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 a driver has corrupted pool memory that is used for holding pages destined for disk.  
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 the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.  
 
 
 
On Sun 18/08/2019 17:38:55 your computer crashed or a problem was reported
crash dump file: C:\Windows\Minidump\081819-6203-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x1BFCC0)  
Bugcheck code: 0x4E (0x99, 0x1E1282, 0x2, 0x60003100031D281)
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 Sun 18/08/2019 15:38:42 your computer crashed or a problem was reported
crash dump file: C:\Windows\Minidump\081819-7171-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x1BFCC0)  
Bugcheck code: 0xDE (0x2, 0xFFFFDD05733A7D38, 0xFFFFDD05733A7D78, 0x3F2F798C0)
Error: POOL_CORRUPTION_IN_FILE_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 a driver has corrupted pool memory that is used for holding pages destined for disk.  
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 the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.  
 
 
 
On Sun 18/08/2019 15:33:35 your computer crashed or a problem was reported
crash dump file: C:\Windows\Minidump\081819-6859-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x1BFCC0)  
Bugcheck code: 0x1A (0x402, 0xFFFF8C0936E8CD38, 0x67A3FB8C0, 0xFFFF8C0939C6F1F8)
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.  
 
 
 
 
 
--------------------------------------------------------------------------------
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.  
 
 
 
 
 
 
J'ai installé les derniers pilotes a jour pour la suite MSI.
Merci pour vos réponses les gars.

n°3350987
napster13
Posté le 22-08-2019 à 11:34:38  profilanswer
 

Je viens de faire le test via OCCT le proc monte grave en température (au dessus de 80 lors des tests au bout de 30sec).
J'utilise le cpu fan d'origine AMD fourni avec le proc..
 
Merci pour vos retours.
 
 

n°3350988
nex84
Dura lex, sed lex
Posté le 22-08-2019 à 11:37:01  profilanswer
 

Tu as testé tes barrettes de RAM avec Memtest ?


---------------
#TeamNoBidouille || Come to the Dark Side, we have cookies || Mangez 5 fruits et légumes par an ! || Le digital, c'est les doigts
mood
Publicité
Posté le 22-08-2019 à 11:37:01  profilanswer
 

n°3350993
napster13
Posté le 22-08-2019 à 11:50:44  profilanswer
 

Oui, en fait j'avais OC les barrettes de rams et j'pense que le problème venez de la, donc j'ai désactivé l'OC et laisser d'origine.
Mais le problème persiste. S'matin j'ai encore eu un BSOD POOL KERNEL..
 
Voici le rapport WHOSCRASHED pour les crashs de ce matin :  
 
Crash Dump Analysis
--------------------------------------------------------------------------------
 
Crash dumps are enabled on your computer.  
 
Crash dump directories:  
C:\Windows
C:\Windows\Minidump
 
On Thu 22/08/2019 11:04:23 your computer crashed or a problem was reported
crash dump file: C:\Windows\Minidump\082219-6390-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x1BFCC0)  
Bugcheck code: 0x13A (0x9, 0xFFFFB20C32000000, 0xFFFFB20C432425C0, 0x0)
Error: KERNEL_MODE_HEAP_CORRUPTION
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 kernel mode heap manager has detected corruption in a heap.  
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 22/08/2019 11:04:23 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!RtlTraceDatabaseValidate+0x5C48)  
Bugcheck code: 0x13A (0x9, 0xFFFFB20C32000000, 0xFFFFB20C432425C0, 0x0)
Error: KERNEL_MODE_HEAP_CORRUPTION
Bug check description: This indicates that the kernel mode heap manager has detected corruption in a heap.  
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.  
 
 
 
Merci par avance,


Message édité par napster13 le 22-08-2019 à 11:51:47
n°3350994
nex84
Dura lex, sed lex
Posté le 22-08-2019 à 12:13:35  profilanswer
 

Parce que là tout indique un problème mémoire (barrettes de RAM, contrôleur, ...)


---------------
#TeamNoBidouille || Come to the Dark Side, we have cookies || Mangez 5 fruits et légumes par an ! || Le digital, c'est les doigts
n°3350998
napster13
Posté le 22-08-2019 à 12:42:40  profilanswer
 

Même les erreurs du 22/08 ?  
 
Bon beh je les renvoi chez amazon :).
Cela vient toujours de la donc ?

n°3351011
nex84
Dura lex, sed lex
Posté le 22-08-2019 à 17:20:37  profilanswer
 

Memtest a donné quoi ?
Est-ce que ta RAM est dans la liste QVL de ta carte mère ?


---------------
#TeamNoBidouille || Come to the Dark Side, we have cookies || Mangez 5 fruits et légumes par an ! || Le digital, c'est les doigts
n°3351017
napster13
Posté le 22-08-2019 à 22:06:51  profilanswer
 

Memtest ne détecté rien en test étendu..
Ram ok sur le site msi
 
T'as vu les resultats de ce jour sur whocrashed ?

n°3351117
napster13
Posté le 24-08-2019 à 13:55:40  profilanswer
 


Crash dumps are enabled on your computer.  
 
Crash dump directories:  
C:\Windows  
C:\Windows\Minidump  
 
On Thu 22/08/2019 11:04:23 your computer crashed or a problem was reported  
crash dump file: C:\Windows\Minidump\082219-6390-01.dmp  
This was probably caused by the following module: ntoskrnl.exe (nt+0x1BFCC0)  
Bugcheck code: 0x13A (0x9, 0xFFFFB20C32000000, 0xFFFFB20C432425C0, 0x0)  
Error: KERNEL_MODE_HEAP_CORRUPTION  
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 kernel mode heap manager has detected corruption in a heap.  
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 22/08/2019 11:04:23 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!RtlTraceDatabaseValidate+0x5C48)  
Bugcheck code: 0x13A (0x9, 0xFFFFB20C32000000, 0xFFFFB20C432425C0, 0x0)  
Error: KERNEL_MODE_HEAP_CORRUPTION  
Bug check description: This indicates that the kernel mode heap manager has detected corruption in a heap.  
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.  

n°3351121
ZYX68
Posté le 24-08-2019 à 14:41:00  profilanswer
 

napster13 a écrit :

 
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.  


J'avais le même problème d’écrans bleus sur mon PC neuf avec carte-mère MSI. Je l'ai résolu en désinstallant tous les softs MSI (Eco Center Pro, Eco Meter,...).

n°3351128
napster13
Posté le 24-08-2019 à 17:13:15  profilanswer
 

Merci pour ton retour, cependant j'ai installé aucun soft MSI sur mon PC.

n°3351235
nex84
Dura lex, sed lex
Posté le 26-08-2019 à 08:42:35  profilanswer
 

Soit l'OC a endommagé quelque chose, soit quelque chose est installé et ne lui plait pas.
 
Peux-tu faire un scan FRST et poster les 2 rapports avec www.cjoint.com ?


---------------
#TeamNoBidouille || Come to the Dark Side, we have cookies || Mangez 5 fruits et légumes par an ! || Le digital, c'est les doigts

Aller à :
Ajouter une réponse
  FORUM HardWare.fr
  Windows & Software
  Win 10

  Nombreux BSOD ss win10

 

Sujets relatifs
Win10 , écran bleu, reboot, un p'ti coup de main ?cle usb win10
migrer de Win10N vers Win10 ProBSOD/freeze à l'activation de la CG/installation des drivers
utiliser un windowsimagebackup sous win10[rien, ça marche]
Arret de Win10 interminableplantage win10
W10 BSOD Erreur d'indexation 
Plus de sujets relatifs à : Nombreux BSOD ss win10


Copyright © 1997-2022 Hardware.fr SARL (Signaler un contenu illicite / Données personnelles) / Groupe LDLC / Shop HFR