BSOD intempestifs windows 10

Tous les problèmes de Windows : message d'erreur, BSOD et écran bleu, erreur Windows Update ou d'installation, etc

Modérateur : Mods Windows

GlazeMoyu
Messages : 4
Inscription : 01 janv. 2021 15:44

BSOD intempestifs windows 10

par GlazeMoyu »

Bonjour,

J'ai un problème avec mon pc depuis plusieurs jours. En effet, celui-ci fait des BSOD à longueur de journée, autant lorsque je lance un jeu que lorsque je ne fait rien en particulier.

Les specs de mon PC :
-Intel core i5-10400F @ 2.90GHz
-PNY Geforce GTX 1660 6GB
-Asrock z490 phantom gaming 4
-2x8go ram Corsair Vengeance LPX 3200MHz
-seagate barracuda 2TO
-ssd samsung 1to
-alim aerocool 650w 80+ bronze
-boitier aerocool split

J'ai fait un coup de crystaldisk pour voir si mes disques durs n'avaient rien : ils fonctionnent tous les deux très bien.
Je suis allé sur le cmd faire un /scannow, des fichiers corrompus ont été détectés et corrigés, mais rien n'y fait.
Je suis aussi allé sur WhoCrashed, et le problème est dû à hardware.sys

Alors, j'ai voulu vérifier si la ram était en cause, alors j'ai fait un memtest86+, j'ai des erreurs lors des tests 7 et 9, et en deux passages j'ai environ 6144 erreurs.

Qu'est-ce que je peux en déduire ? J'ai vraiment besoin d'aide.

Merci d'avance.
Malekal_morte
Messages : 112131
Inscription : 10 sept. 2005 13:57

Re: BSOD intempestifs windows 10

par Malekal_morte »

Salut,


Les écrans bleus ou BSOD sont des plantages de Windows qui ne peut plus continuer à fonctionner.
Ces plantages ont plusieurs sources possibles :
- sources logiciels : plantage d'un pilote d'un périphérique comme ceux de la carte graphique, l'antivirus qui plante ou tout autre logiciel qui peut se charger "dans un bas niveau" sur Windows.
- sources matériels : problème matériels sur le disque dur, barrettes de mémoire défectueuses ou incomparabilités, etc

Il faut impérativement que tu regardes si ces plantages ont lieu à des moments particuliers, par exemple, si c'est lorsque tu lances une vidéo sur ton navigateur internet ou un jeu, il y a des chances que ce soit le pilote de la carte graphique. Il faudra alors réinstaller les pilotes de la carte graphique.
Débranche aussi tout autre périphérique que le clavier/souris (manette de jeu, webcam en USB, imprimante USB, etc), si tu as un de ces périphériques, indique le, ça peut être une source.

plus d'informations sur ces écrans bleus, sur la page suivante : Les écrans bleus de plantages (BSOD)

On peut aussi utiliser WhoCrashed pour obtenir des informations sur ces plantages.
Tutoriel WhoCrashed
Fais un copier/coller du contenu ici comme indiqué dans le tuto.

Réponse générique :


Suivre ce lien : Résoudre BSOD sur Windows
Première règle élémentaire de sécurité : on réfléchit puis on clic et pas l'inverse - Les fichiers/programmes c'est comme les bonbons, quand ça vient d'un inconnu, on n'accepte pas !
Comment protéger son PC des virus
Windows 11 : Compatibilité, Configuration minimale requise, télécharger ISO et installer Windows 11

Comment demander de l'aide sur le forum
Partagez malekal.com : n'hésitez pas à partager les articles qui vous plaisent sur la page Facebook du site.
GlazeMoyu
Messages : 4
Inscription : 01 janv. 2021 15:44

Re: BSOD intempestifs windows 10

par GlazeMoyu »

Bonjour, voici les résultats WhoCrashed (en plus de hardware.sys) :
On Fri 01/01/2021 17:22:30 your computer crashed or a problem was reported
crash dump file: C:\Windows\Minidump\010121-7500-01.dmp
This was probably caused by the following module: dxgmms2.sys (0xFFFFF8016D8ADA7A)
Bugcheck code: 0xD1 (0xFFFFFFFFEBBB60A6, 0x2, 0x0, 0xFFFFF8016D8ADA7A)
Error: DRIVER_IRQL_NOT_LESS_OR_EQUAL
file path: C:\Windows\system32\drivers\dxgmms2.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: DirectX Graphics MMS
Bug check description: This indicates that a kernel-mode driver attempted to access pageable memory at a process IRQL that was too high.
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 a 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 Fri 01/01/2021 17:22:30 your computer crashed or a problem was reported
crash dump file: C:\Windows\MEMORY.DMP
This was probably caused by the following module: nvlddmkm.sys (nvlddmkm+0x79B7F)
Bugcheck code: 0xD1 (0xFFFFFFFFEBBB60A6, 0x2, 0x0, 0xFFFFF8016D8ADA7A)
Error: DRIVER_IRQL_NOT_LESS_OR_EQUAL
file path: C:\Windows\System32\DriverStore\FileRepository\nv_dispi.inf_amd64_a51067c0ac557884\nvlddmkm.sys
product: NVIDIA Windows Kernel Mode Driver, Version 460.89
company: NVIDIA Corporation
description: NVIDIA Windows Kernel Mode Driver, Version 460.89
Bug check description: This indicates that a kernel-mode driver attempted to access pageable memory at a process IRQL that was too high.
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.
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: nvlddmkm.sys (NVIDIA Windows Kernel Mode Driver, Version 460.89 , NVIDIA Corporation).
Google query: nvlddmkm.sys NVIDIA Corporation DRIVER_IRQL_NOT_LESS_OR_EQUAL



On Fri 01/01/2021 17:21:28 your computer crashed or a problem was reported
crash dump file: C:\Windows\Minidump\010121-8250-01.dmp
This was probably caused by the following module: cng.sys (0xFFFFF8073CCEA127)
Bugcheck code: 0x3B (0xC0000005, 0xFFFFF8073CCEA127, 0xFFFFC4838C771C60, 0x0)
Error: SYSTEM_SERVICE_EXCEPTION
file path: C:\Windows\system32\drivers\cng.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: Kernel Cryptography, Next Generation
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 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 Thu 31/12/2020 17:13:46 your computer crashed or a problem was reported
crash dump file: C:\Windows\Minidump\010121-8125-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x3F5780)
Bugcheck code: 0x3B (0xC0000005, 0x193600000C08, 0xFFFF8384882E6F80, 0x0)
Error: SYSTEM_SERVICE_EXCEPTION
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 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 the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.



On Thu 31/12/2020 13:53:13 your computer crashed or a problem was reported
crash dump file: C:\Windows\Minidump\123120-7609-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x3F5780)
Bugcheck code: 0x18 (0xFFFFAB0F2F2FB2A0, 0xFFFFAB0F54023520, 0x1, 0x80)
Error: REFERENCE_BY_POINTER
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 reference count of an object is illegal for the current state of the object.
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 Thu 31/12/2020 13:42:58 your computer crashed or a problem was reported
crash dump file: C:\Windows\Minidump\123120-7812-01.dmp
This was probably caused by the following module: ntfs.sys (0xFFFFF8037FFFA12F)
Bugcheck code: 0x1E (0xFFFFFFFFC0000005, 0xFFFFF8037FFFA12F, 0x0, 0x71B949BF)
Error: KMODE_EXCEPTION_NOT_HANDLED
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 kernel-mode program generated an exception which the error handler did not catch.
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 a file system driver. Since there is no other responsible driver detected, this could be pointing to a malfunctioning drive or corrupted disk. It's suggested that you run CHKDSK.





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

6 crash dumps have been found and analyzed. A third party driver has been identified to be causing system crashes on your computer. It is strongly suggested that you check for updates for these drivers on their company websites. Click on the links below to search with Google for updates for these drivers:

nvlddmkm.sys (NVIDIA Windows Kernel Mode Driver, Version 460.89 , NVIDIA Corporation)

If no updates for these drivers are available, try searching with Google on the names of these drivers in combination with the errors that have been reported for these drivers. Include the brand and model name of your computer as well in the query. This often yields interesting results from discussions on the web by users who have been experiencing similar problems.


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.

J'ai un clavier et une souris de branché, ainsi qu'un bird um1 et une tablette graphique wacom ctl-472
Malekal_morte
Messages : 112131
Inscription : 10 sept. 2005 13:57

Re: BSOD intempestifs windows 10

par Malekal_morte »

Première règle élémentaire de sécurité : on réfléchit puis on clic et pas l'inverse - Les fichiers/programmes c'est comme les bonbons, quand ça vient d'un inconnu, on n'accepte pas !
Comment protéger son PC des virus
Windows 11 : Compatibilité, Configuration minimale requise, télécharger ISO et installer Windows 11

Comment demander de l'aide sur le forum
Partagez malekal.com : n'hésitez pas à partager les articles qui vous plaisent sur la page Facebook du site.
GlazeMoyu
Messages : 4
Inscription : 01 janv. 2021 15:44

Re: BSOD intempestifs windows 10

par GlazeMoyu »

Bonjour,

J'ai effectué les manipulations, et jusqu'à preuve du contraire, le pc n'effectue pas encore de bsod.

Mais malgré ça, j'ai donc fait un memtest86+ et j'ai eu ces résultats :
MEMTEST86.jpg
Je voudrais savoir si cela aurait un quelconque impact sur le fait que mon pc fasse des bsod.
Merci d'avance.
Vous ne pouvez pas consulter les pièces jointes insérées à ce message.
Malekal_morte
Messages : 112131
Inscription : 10 sept. 2005 13:57

Re: BSOD intempestifs windows 10

par Malekal_morte »

ha oui en plus tu as des erreurs de barrettes de mémoire :/
Du coup si ça revient, faudra tester le PC avec une barrette à la fois.
Si tu as activé XMP dans le BIOS avant, désactive le aussi.
Première règle élémentaire de sécurité : on réfléchit puis on clic et pas l'inverse - Les fichiers/programmes c'est comme les bonbons, quand ça vient d'un inconnu, on n'accepte pas !
Comment protéger son PC des virus
Windows 11 : Compatibilité, Configuration minimale requise, télécharger ISO et installer Windows 11

Comment demander de l'aide sur le forum
Partagez malekal.com : n'hésitez pas à partager les articles qui vous plaisent sur la page Facebook du site.
GlazeMoyu
Messages : 4
Inscription : 01 janv. 2021 15:44

Re: BSOD intempestifs windows 10

par GlazeMoyu »

Re,

J'ai de nouveau blue screen, avec ce message d'erreur sur whocrashed :
Crash dumps are enabled on your computer.

Crash dump directories:
C:\Windows
C:\Windows\Minidump

On Sun 03/01/2021 17:36:19 your computer crashed or a problem was reported
crash dump file: C:\Windows\Minidump\010321-7406-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x3F5780)
Bugcheck code: 0x3B (0xC000001D, 0xFFFFF8034BE24396, 0xFFFFF20BBFC065D0, 0x0)
Error: SYSTEM_SERVICE_EXCEPTION
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 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 the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.



On Sun 03/01/2021 17:36:19 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!setjmpex+0x8299)
Bugcheck code: 0x3B (0xC000001D, 0xFFFFF8034BE24396, 0xFFFFF20BBFC065D0, 0x0)
Error: SYSTEM_SERVICE_EXCEPTION
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 the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.



On Sun 03/01/2021 17:24:06 your computer crashed or a problem was reported
crash dump file: C:\Windows\Minidump\010321-10250-01.dmp
This was probably caused by the following module: win32kbase.sys (0xFFFFC518C26FE2FC)
Bugcheck code: 0x50 (0xFFFFE8A1382FAF10, 0x0, 0xFFFFC518C26FE2FC, 0x2)
Error: PAGE_FAULT_IN_NONPAGED_AREA
file path: C:\Windows\system32\win32kbase.sys
product: Système d’exploitation Microsoft® Windows®
company: Microsoft Corporation
description: Pilote du noyau Base Win32k
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 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 Fri 01/01/2021 18:57:04 your computer crashed or a problem was reported
crash dump file: C:\Windows\Minidump\010221-7937-01.dmp
This was probably caused by the following module: hardware.sys (hardware)
Bugcheck code: 0x3B (0xC0000005, 0xFFFFF8048F27713D, 0xFFFFDC011B6D9920, 0x0)
Error: SYSTEM_SERVICE_EXCEPTION
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.
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 SYSTEM_SERVICE_EXCEPTION



On Fri 01/01/2021 17:22:30 your computer crashed or a problem was reported
crash dump file: C:\Windows\Minidump\010121-7500-01.dmp
This was probably caused by the following module: dxgmms2.sys (0xFFFFF8016D8ADA7A)
Bugcheck code: 0xD1 (0xFFFFFFFFEBBB60A6, 0x2, 0x0, 0xFFFFF8016D8ADA7A)
Error: DRIVER_IRQL_NOT_LESS_OR_EQUAL
file path: C:\Windows\system32\drivers\dxgmms2.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: DirectX Graphics MMS
Bug check description: This indicates that a kernel-mode driver attempted to access pageable memory at a process IRQL that was too high.
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 a 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 Fri 01/01/2021 17:21:28 your computer crashed or a problem was reported
crash dump file: C:\Windows\Minidump\010121-8250-01.dmp
This was probably caused by the following module: cng.sys (0xFFFFF8073CCEA127)
Bugcheck code: 0x3B (0xC0000005, 0xFFFFF8073CCEA127, 0xFFFFC4838C771C60, 0x0)
Error: SYSTEM_SERVICE_EXCEPTION
file path: C:\Windows\system32\drivers\cng.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: Kernel Cryptography, Next Generation
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 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
--------------------------------------------------------------------------------

6 crash dumps have been found and analyzed. A third party driver has been identified to be causing system crashes on your computer. It is strongly suggested that you check for updates for these drivers on their company websites. Click on the links below to search with Google for updates for these drivers:

hardware.sys

If no updates for these drivers are available, try searching with Google on the names of these drivers in combination with the errors that have been reported for these drivers. Include the brand and model name of your computer as well in the query. This often yields interesting results from discussions on the web by users who have been experiencing similar problems.


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.

Je suppose que c'est la ram, je vais devoir la changer ou ya t il des manipulations à faire pour éviter tout ça ?
  • Sujets similaires
    Réponses
    Vues
    Dernier message

Revenir à « Windows : Résoudre les problèmes »