Résolu Blue screen récurrent

lexaa

Nouveau membre
Bonjour,

J'ai acheté et monté mon PC fin septembre.
Malheureusement j'ai régulièrement des blue screens (dont 2 rien qu'aujourd'hui).
En cherchant les erreurs, se serait du à la mémoire, et j'ai tenté plusieurs conseils trouvés sur internet.
J'ai fait un diagnostique de mémoire de Windows, qui n'a détecté aucun souci, j'ai lancé memtest86 qui lui aussi n'a trouvé aucun problème et les drivers semblent à jour ...
Avez vous des idées de ce que ça peut être et comment réparer ?

J'ai des captures d'écran de l'historique de fiabilité (mais ne sait pas comment les mettre sur le forum) et je peux donner les codes des erreurs rencontrées.

Merci d'avance pour votre aide.
 

dandibot

Grand Maître
Bonjour, il nous faudrait en effet les codes erreur en question et la configuration complète de ton pc.
 

lexaa

Nouveau membre
Bonjour,

Voici la configuration du PC :


Pour les codes d'erreurs j'ai eu les suivants:
21/10/2017 : 0x00000050 et 0x0000007e
20/10/2017 : 0x0000001a
18/10/2017 : 0x0000001a
16/10/2017 : 0x000000ef
15/10/2017 : 0x0000001a
13/10/2017 : 0x0000001a
09/10/2017 : 0x0000001a
04/10/2017 : 0x00000050
03/10/2017 : 0x00000050
01/10/2017 : 0x00000050

Voilà l'historique.
 

dandibot

Grand Maître
Tu es sous quel windows? Tu fais bien tes mises à jours?

Télécharges whocrashed et envois nous le rapport:


Parce que pour l'instant les erreurs ne semblent pas toutes pointer vers la même chose.
 

lexaa

Nouveau membre
Windows 10.

J'ai bien fait toutes les mises à jour mais samedi j'ai fait un récupération du système au 05/10 (ce que n'était peut être pas très malin, je m'en rend compte maintenant ... )

Voici le rapport de whocrashed :


--------------------------------------------------------------------------------
System Information (local)
--------------------------------------------------------------------------------

Computer name: DESKTOP-D6OL310
Windows version: Windows 10 , 10.0, build: 15063
Windows dir: C:\Windows
Hardware: MS-7A39, MSI, B350M GAMING PRO (MS-7A39)
CPU: AuthenticAMD AMD Ryzen 5 1600 Six-Core Processor AMD586, level: 23
12 logical processors, active mask: 4095
RAM: 17130115072 bytes total




--------------------------------------------------------------------------------
Crash Dump Analysis
--------------------------------------------------------------------------------

Crash dump directory: C:\Windows\Minidump

Crash dumps are enabled on your computer.

On Wed 04/10/2017 18:28:43 your computer crashed
crash dump file: C:\Windows\Minidump\100417-5781-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x16C580)
Bugcheck code: 0x50 (0xFFFFDD8BDBD15F60, 0x0, 0xFFFFF80134274EA2, 0x2)
Error: PAGE_FAULT_IN_NONPAGED_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 invalid system memory has been referenced.
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 Wed 04/10/2017 18:28:43 your computer crashed
crash dump file: C:\Windows\memory.dmp
This was probably caused by the following module: ntfs.sys (NTFS+0xCDF44)
Bugcheck code: 0x50 (0xFFFFDD8BDBD15F60, 0x0, 0xFFFFF80134274EA2, 0x2)
Error: PAGE_FAULT_IN_NONPAGED_AREA
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 invalid system memory has been referenced.
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 Tue 03/10/2017 18:20:18 your computer crashed
crash dump file: C:\Windows\Minidump\100317-16468-01.dmp
This was probably caused by the following module: ntfs.sys (0xFFFFF805ED6CD87C)
Bugcheck code: 0x50 (0xFFFFBB8FF5056250, 0x0, 0xFFFFF805ED6CD87C, 0x2)
Error: PAGE_FAULT_IN_NONPAGED_AREA
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 invalid system memory has been referenced.
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 Sun 01/10/2017 13:40:52 your computer crashed
crash dump file: C:\Windows\Minidump\100117-6390-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x16C580)
Bugcheck code: 0x50 (0xFFFFAA0106394428, 0x0, 0xFFFFF8007412B09F, 0x2)
Error: PAGE_FAULT_IN_NONPAGED_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 invalid system memory has been referenced.
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.





--------------------------------------------------------------------------------
Conclusion
--------------------------------------------------------------------------------

4 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.


Read the topic general suggestions for troubleshooting system crashes for more information.

Note that it's not always possible to state with certainty whether a reported driver is responsible for crashing your system or that the root cause is in another module. Nonetheless it's suggested you look for updates for the products that these drivers belong to and regularly visit Windows update or enable automatic updates for Windows. In case a piece of malfunctioning hardware is causing trouble, a search with Google on the bug check errors together with the model name and brand of your computer may help you investigate this further.




 

dandibot

Grand Maître
Ok, tu as fait la dernière mise à jour du bios pour ta carte mère disponible?
Mise à jour des drivers de la carte mère? Via le site de MSI?
 

dandibot

Grand Maître
Ici:
Attentions choisies bien le système d'exploitation concerné.
Pour la mise à jour du bios, je recommande le flash via usb.
 

lexaa

Nouveau membre
Pour la mise a jour du bios, je dois prendre la dernière version sortie ou celle juste après celle de ma carte mère ?
Par exemple, j'ai la ver 1.0, dois-je prendre la 2.0 ou la 2.9 ?
 

dandibot

Grand Maître
La dernière en date. Et c'est une image iso, donc a faire via une clé usb bootable de préférence.
 

lexaa

Nouveau membre
J'ai fait la mise à jour du BIOS.
Hier j'ai testé les drivers de MSI mais j'obtenais a chaque fois " la meilleure version est déjà installée".
Je n'utiliserai pas mon PC les prochains jours, on verra si j'ai encore des soucis plus tard.
 

lexaa

Nouveau membre
Encore un blue screen ajd ...
Voici ce qu'en dit whocrashed:

--------------------------------------------------------------------------------
Crash Dump Analysis
--------------------------------------------------------------------------------

Crash dump directory: C:\Windows\Minidump

Crash dumps are enabled on your computer.

On Fri 27/10/2017 08:28:32 your computer crashed
crash dump file: C:\Windows\Minidump\102717-5656-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x16C580)
Bugcheck code: 0x1A (0x41793, 0xFFFFC88000111400, 0x81, 0x80)
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. 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 the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.



On Fri 27/10/2017 08:28:32 your computer crashed
crash dump file: C:\Windows\memory.dmp
This was probably caused by the following module: ntkrnlmp.exe (nt!KeBugCheckEx+0x0)
Bugcheck code: 0x1A (0x41793, 0xFFFFC88000111400, 0x81, 0x80)
Error: MEMORY_MANAGEMENT
Bug check description: This indicates that a severe memory management error occurred.
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 the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.



On Thu 26/10/2017 20:20:51 your computer crashed
crash dump file: C:\Windows\Minidump\102617-5640-01.dmp
This was probably caused by the following module: win32kfull.sys (win32kfull+0x26973C)
Bugcheck code: 0x3B (0xC0000005, 0xFFFF93AE51E6973C, 0xFFFF9C80CEC3BE10, 0x0)
Error: SYSTEM_SERVICE_EXCEPTION
file path: C:\Windows\system32\win32kfull.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: Full/Desktop Win32k Kernel Driver
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 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 24/10/2017 18:23:34 your computer crashed
crash dump file: C:\Windows\Minidump\102417-6625-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x16C580)
Bugcheck code: 0x50 (0xFFFFB004FDC1E018, 0x0, 0xFFFFF8035AE8223F, 0x2)
Error: PAGE_FAULT_IN_NONPAGED_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 invalid system memory has been referenced.
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 Wed 04/10/2017 18:28:43 your computer crashed
crash dump file: C:\Windows\Minidump\100417-5781-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x16C580)
Bugcheck code: 0x50 (0xFFFFDD8BDBD15F60, 0x0, 0xFFFFF80134274EA2, 0x2)
Error: PAGE_FAULT_IN_NONPAGED_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 invalid system memory has been referenced.
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.





--------------------------------------------------------------------------------
Conclusion
--------------------------------------------------------------------------------

6 crash dumps have been found and analyzed. Only 5 are included in this report. 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.


Read the topic general suggestions for troubleshooting system crashes for more information.

Note that it's not always possible to state with certainty whether a reported driver is responsible for crashing your system or that the root cause is in another module. Nonetheless it's suggested you look for updates for the products that these drivers belong to and regularly visit Windows update or enable automatic updates for Windows. In case a piece of malfunctioning hardware is causing trouble, a search with Google on the bug check errors together with the model name and brand of your computer may help you investigate this further.




 

dandibot

Grand Maître
Meilleure réponse
Bon et bien, selon moi, il ne reste plus qu'a faire une réinstallation clean de windows. Et si ça ne change rien, tu peux alors renvoyer tes barrettes de ram au SAV.
 

lexaa

Nouveau membre
Bonjour,
Après récupération de mes fichiers, je me suis lancée dans une réinstallation de Windows.
Sauf que lors du choix de la partition, je me retrouve avec le choix entre 6 partitions (4 sur le SSD ( récupération- système- MSR- principal) et 2 sur l'autre(MSR-principal)).
Et pour toutes les partitions j'ai le message " Impossible d'installer Windows sur le lecteur X, partition X".
Si je cliques dessus, le message suivant s'affiche "Windows ne peut pas être installé sur ce disque. Le disque sélectionné est du style de partition GPT. "

Dois-je supprimer ou formater des partitions pour pouvoir refaire mon installation ?

Merci d'avance.
 

lexaa

Nouveau membre
La réinstallation a été faite, via clé USB, le 06/11.

Mais ce matin écran bleu au démarrage ...

whocrashed me sort le rapport suivant :

--------------------------------------------------------------------------------
Crash Dump Analysis
--------------------------------------------------------------------------------

Crash dump directory: C:\Windows\Minidump

Crash dumps are enabled on your computer.

On Sun 12/11/2017 10:34:25 your computer crashed
crash dump file: C:\Windows\Minidump\111217-5171-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x163960)
Bugcheck code: 0x50 (0xFFFF990C2956DEA8, 0x2, 0xFFFFF80323CC16EB, 0x2)
Error: PAGE_FAULT_IN_NONPAGED_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 invalid system memory has been referenced.
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 12/11/2017 10:34:25 your computer crashed
crash dump file: C:\Windows\memory.dmp
This was probably caused by the following module: ntfs.sys (NTFS+0xF5009)
Bugcheck code: 0x50 (0xFFFF990C2956DEA8, 0x2, 0xFFFFF80323CC16EB, 0x2)
Error: PAGE_FAULT_IN_NONPAGED_AREA
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 invalid system memory has been referenced.
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.





--------------------------------------------------------------------------------
Conclusion
--------------------------------------------------------------------------------

2 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.


Read the topic general suggestions for troubleshooting system crashes for more information.

Note that it's not always possible to state with certainty whether a reported driver is responsible for crashing your system or that the root cause is in another module. Nonetheless it's suggested you look for updates for the products that these drivers belong to and regularly visit Windows update or enable automatic updates for Windows. In case a piece of malfunctioning hardware is causing trouble, a search with Google on the bug check errors together with the model name and brand of your computer may help you investigate this further.
 

mathieu.ferstler

Habitué
Bonjour,
Je viens d'ouvrir un post car j'ai l'impression d'avoir exactement le même problème que lexaa.

@lexaa : as-tu réussis à résoudre ton problème ?
 
Vous devez vous inscrire ou vous connecter pour répondre ici.
Derniers messages publiés
Statistiques globales
Discussions
730 098
Messages
6 717 065
Membres
1 586 286
Dernier membre
petitangebleu1977
Partager cette page
Haut