Blue screen nvlddmkm.sys et dxgkrnl.sys

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

Modérateur : Mods Windows

AlexCnl
Messages : 22
Inscription : 03 août 2020 13:37

Blue screen nvlddmkm.sys et dxgkrnl.sys

par AlexCnl »

Bonjour

Alors depuis peu j'ai des bluescreen.

J'ai fait un réinstallation windows y'a peu.
J'ai ajouté les driver AMD, ceux de la carte graphique, réseau et son et aussi les majs windows.

Mais malgré ça j'ai eu des bluescreen :

On Tue 27/04/2021 17:34:40 your computer crashed or a problem was reported
crash dump file: C:\Windows\Minidump\042721-7953-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x3F5210)
Bugcheck code: 0x3B (0xC0000005, 0xFFFFF807486DE1E2, 0xFFFF89017D24B770, 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 Tue 27/04/2021 17:34:40 your computer crashed or a problem was reported
crash dump file: C:\Windows\MEMORY.DMP
This was probably caused by the following module: dxgkrnl.sys (dxgkrnl!NtGdiDdDDICreateSynchronizationObject+0x3CF8)
Bugcheck code: 0x3B (0xC0000005, 0xFFFFF807486DE1E2, 0xFFFF89017D24B770, 0x0)
Error: SYSTEM_SERVICE_EXCEPTION
file path: C:\Windows\system32\drivers\dxgkrnl.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: DirectX Graphics Kernel
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 Wed 28/04/2021 18:43:36 your computer crashed or a problem was reported
crash dump file: C:\Windows\Minidump\042821-9156-01.dmp
This was probably caused by the following module: nvlddmkm.sys (0xFFFFF80441ED48E3)
Bugcheck code: 0xD1 (0x1, 0x2, 0x0, 0xFFFFF80441ED48E3)
Error: DRIVER_IRQL_NOT_LESS_OR_EQUAL
file path: C:\Windows\System32\DriverStore\FileRepository\nv_dispi.inf_amd64_7d91b2ed40558a26\nvlddmkm.sys
product: NVIDIA Windows Kernel Mode Driver, Version 466.11
company: NVIDIA Corporation
description: NVIDIA Windows Kernel Mode Driver, Version 466.11
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 466.11 , NVIDIA Corporation).
Google query: nvlddmkm.sys NVIDIA Corporation DRIVER_IRQL_NOT_LESS_OR_EQUAL



On Wed 28/04/2021 18:43:36 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 (0xFFFFF80441ED48E3)
Bugcheck code: 0xD1 (0x1, 0x2, 0x0, 0xFFFFF80441ED48E3)
Error: DRIVER_IRQL_NOT_LESS_OR_EQUAL
file path: C:\Windows\System32\DriverStore\FileRepository\nv_dispi.inf_amd64_7d91b2ed40558a26\nvlddmkm.sys
product: NVIDIA Windows Kernel Mode Driver, Version 466.11
company: NVIDIA Corporation
description: NVIDIA Windows Kernel Mode Driver, Version 466.11
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 466.11 , NVIDIA Corporation).
Google query: nvlddmkm.sys NVIDIA Corporation DRIVER_IRQL_NOT_LESS_OR_EQUAL



Je soupçonne ma carte graphique c'est une 750ti elle date et c'est le seul truc qui est vieux dans mon PC, pour le moment compliqué d'en acheter une.

Voila voila je vous remercie d'avance pour votre aide
Malekal_morte
Messages : 107565
Inscription : 10 sept. 2005 13:57

Re: Blue screen nvlddmkm.sys et dxgkrnl.sys

par Malekal_morte »

Salut,

Tu as le pilote NVIDIA qui plante.
Commence par ceci : DDU : Réinstaller proprement les pilotes de cartes graphiques avec Display Driver Uninstaller

et :


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.
WhoCrashed : analyser les écrans bleus, BSOD ou code d’arrêt
Fais un copier/coller du contenu ici comme indiqué dans le tuto.
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.
AlexCnl
Messages : 22
Inscription : 03 août 2020 13:37

Re: Blue screen nvlddmkm.sys et dxgkrnl.sys

par AlexCnl »

J'ai eu des crashs sur 4 jeux différents et j'ai des fois google qui crash quand je regarde un live sur twitch.
Les bsod sont souvent aléatoires mais la plus part du temps c'est en jeu.

J'ai trouvé ces logs la après un crash sur rocket league si ça peut aider:

[0707.16] Critical: appError called: Online thread exception:
Fatal error!

Address = 0x301dfaad (filename not found) [in C:\Windows\SYSTEM32\ntdll.dll]
Address = 0xce0ba7d2 (filename not found) [in C:\Program Files (x86)\Steam\steamclient64.dll]
Address = 0xce2cfd92 (filename not found) [in C:\Program Files (x86)\Steam\steamclient64.dll]
Address = 0x55d19608 (filename not found) [in C:\Program Files (x86)\Steam\steamapps\common\rocketleague\Binaries\Win64\steam_api64.dll]
Address = 0x55d1902a (filename not found) [in C:\Program Files (x86)\Steam\steamapps\common\rocketleague\Binaries\Win64\steam_api64.dll]
Address = 0xddc8f41c (filename not found) [in C:\Program Files (x86)\Steam\steamapps\common\rocketleague\Binaries\Win64\RocketLeague.exe]
Address = 0xddb959ca (filename not found) [in C:\Program Files (x86)\Steam\steamapps\common\rocketleague\Binaries\Win64\RocketLeague.exe]
Address = 0xddba1337 (filename not found) [in C:\Program Files (x86)\Steam\steamapps\common\rocketleague\Binaries\Win64\RocketLeague.exe]
Address = 0xdd2f2670 (filename not found) [in C:\Program Files (x86)\Steam\steamapps\common\rocketleague\Binaries\Win64\RocketLeague.exe]
Address = 0x2fca7034 (filename not found) [in C:\Windows\System32\KERNEL32.DLL]
Address = 0x30202651 (filename not found) [in C:\Windows\SYSTEM32\ntdll.dll]
Address = 0x30202651 (filename not found) [in C:\Windows\SYSTEM32\ntdll.dll]

[0707.16] Critical: Windows GetLastError: Lopération a réussi. (0)
[0707.16] Log: === Critical error: ===
Online thread exception:
Fatal error!

Address = 0x301dfaad (filename not found) [in C:\Windows\SYSTEM32\ntdll.dll]
Address = 0xce0ba7d2 (filename not found) [in C:\Program Files (x86)\Steam\steamclient64.dll]
Address = 0xce2cfd92 (filename not found) [in C:\Program Files (x86)\Steam\steamclient64.dll]
Address = 0x55d19608 (filename not found) [in C:\Program Files (x86)\Steam\steamapps\common\rocketleague\Binaries\Win64\steam_api64.dll]
Address = 0x55d1902a (filename not found) [in C:\Program Files (x86)\Steam\steamapps\common\rocketleague\Binaries\Win64\steam_api64.dll]
Address = 0xddc8f41c (filename not found) [in C:\Program Files (x86)\Steam\steamapps\common\rocketleague\Binaries\Win64\RocketLeague.exe]
Address = 0xddb959ca (filename not found) [in C:\Program Files (x86)\Steam\steamapps\common\rocketleague\Binaries\Win64\RocketLeague.exe]
Address = 0xddba1337 (filename not found) [in C:\Program Files (x86)\Steam\steamapps\common\rocketleague\Binaries\Win64\RocketLeague.exe]
Address = 0xdd2f2670 (filename not found) [in C:\Program Files (x86)\Steam\steamapps\common\rocketleague\Binaries\Win64\RocketLeague.exe]
Address = 0x2fca7034 (filename not found) [in C:\Windows\System32\KERNEL32.DLL]
Address = 0x30202651 (filename not found) [in C:\Windows\SYSTEM32\ntdll.dll]
Address = 0x30202651 (filename not found) [in C:\Windows\SYSTEM32\ntdll.dll]

DDU je l'ai déjà fait mais ça n'a rien donné

Et voici pour WhoCrashed :


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

Computer name: DESKTOP-I5G6LTC
Windows version: Windows 10, 10.0, version 2009, build: 19042
Windows dir: C:\Windows
Hardware: B450 AORUS ELITE, Gigabyte Technology Co., Ltd.
CPU: AuthenticAMD AMD Ryzen 5 2600X Six-Core Processor 8664, level: 23
12 logical processors, active mask: 4095
RAM: 17128951808 bytes (16,0GB)




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

Crash dumps are enabled on your computer.

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

On Wed 28/04/2021 18:43:36 your computer crashed or a problem was reported
crash dump file: C:\Windows\Minidump\042821-9156-01.dmp
This was probably caused by the following module: nvlddmkm.sys (0xFFFFF80441ED48E3)
Bugcheck code: 0xD1 (0x1, 0x2, 0x0, 0xFFFFF80441ED48E3)
Error: DRIVER_IRQL_NOT_LESS_OR_EQUAL
file path: C:\Windows\System32\DriverStore\FileRepository\nv_dispi.inf_amd64_7d91b2ed40558a26\nvlddmkm.sys
product: NVIDIA Windows Kernel Mode Driver, Version 466.11
company: NVIDIA Corporation
description: NVIDIA Windows Kernel Mode Driver, Version 466.11
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 466.11 , NVIDIA Corporation).
Google query: nvlddmkm.sys NVIDIA Corporation DRIVER_IRQL_NOT_LESS_OR_EQUAL



On Wed 28/04/2021 18:43:36 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 (0xFFFFF80441ED48E3)
Bugcheck code: 0xD1 (0x1, 0x2, 0x0, 0xFFFFF80441ED48E3)
Error: DRIVER_IRQL_NOT_LESS_OR_EQUAL
file path: C:\Windows\System32\DriverStore\FileRepository\nv_dispi.inf_amd64_7d91b2ed40558a26\nvlddmkm.sys
product: NVIDIA Windows Kernel Mode Driver, Version 466.11
company: NVIDIA Corporation
description: NVIDIA Windows Kernel Mode Driver, Version 466.11
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 466.11 , NVIDIA Corporation).
Google query: nvlddmkm.sys NVIDIA Corporation DRIVER_IRQL_NOT_LESS_OR_EQUAL



On Tue 27/04/2021 17:34:40 your computer crashed or a problem was reported
crash dump file: C:\Windows\Minidump\042721-7953-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x3F5210)
Bugcheck code: 0x3B (0xC0000005, 0xFFFFF807486DE1E2, 0xFFFF89017D24B770, 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.





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

3 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 466.11 , 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.
Malekal_morte
Messages : 107565
Inscription : 10 sept. 2005 13:57

Re: Blue screen nvlddmkm.sys et dxgkrnl.sys

par Malekal_morte »

Tu as quoi comme carte graphique ?
Car tu parles de pilotes AMD alors que c'est le pilote NVIDIA qui plante.

Quelle est la config matériel du PC ?
Voir : https://www.malekal.com/connaitre-confi ... rdinateur/
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.
AlexCnl
Messages : 22
Inscription : 03 août 2020 13:37

Re: Blue screen nvlddmkm.sys et dxgkrnl.sys

par AlexCnl »

Les drivers AMD c'est les chipsets truc de genre.
Et carte graphique une vielle 750ti avec le dernier driver

Mon setup :
Vous ne pouvez pas consulter les pièces jointes insérées à ce message.
Malekal_morte
Messages : 107565
Inscription : 10 sept. 2005 13:57

Re: Blue screen nvlddmkm.sys et dxgkrnl.sys

par Malekal_morte »

réinitialise Windows 10
N'installe aucun pilote à part ceux de NVIDIA et vois ce que cela donne, si les BSOD reviennent.
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.
AlexCnl
Messages : 22
Inscription : 03 août 2020 13:37

Re: Blue screen nvlddmkm.sys et dxgkrnl.sys

par AlexCnl »

Je vais faire ça plus tard

Mais tout mes jeux plantes et je vois pas d'ou ça vient
Malekal_morte
Messages : 107565
Inscription : 10 sept. 2005 13:57

Re: Blue screen nvlddmkm.sys et dxgkrnl.sys

par Malekal_morte »

Ca peut être matériel.
Si tu réinitialises et que c'est pareil alors c'est matériel, surement un problème avec la carte graphique.

Tu ne dis pas non plus au départ, pourquoi tu as réinstallé...
Si c'était à l'origine à cause de plantage, alors ça sent le problème matériel.
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.
AlexCnl
Messages : 22
Inscription : 03 août 2020 13:37

Re: Blue screen nvlddmkm.sys et dxgkrnl.sys

par AlexCnl »

Oui j'ai réinstallé à cause du plantage.

J'attendrais qu'il y ait du stock pour en racheter une c'est pas grave
Malekal_morte
Messages : 107565
Inscription : 10 sept. 2005 13:57

Re: Blue screen nvlddmkm.sys et dxgkrnl.sys

par Malekal_morte »

Ok après si tu peux, teste la sur un autre PC pour s'assurer que c'est bien elle et pas autre chose (comme une faiblesse sur le bloc d'alimentation)
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.
AlexCnl
Messages : 22
Inscription : 03 août 2020 13:37

Re: Blue screen nvlddmkm.sys et dxgkrnl.sys

par AlexCnl »

Pendant 4 jours je n'ai eu aucun bsod mais la j'en ai eu 5 en l'espace d'un jour:

On Thu 06/05/2021 00:51:21 your computer crashed or a problem was reported
crash dump file: C:\Windows\Minidump\050621-11015-01.dmp
This was probably caused by the following module: tcpip.sys (0xFFFFF80257B9B5A0)
Bugcheck code: 0x109 (0xA39FFC599CE8D6AF, 0xB3B708DFEF6B8833, 0xFFFFF80257B9B5A0, 0x1)
Error: CRITICAL_STRUCTURE_CORRUPTION
file path: C:\Windows\system32\drivers\tcpip.sys
product: Système d’exploitation Microsoft® Windows®
company: Microsoft Corporation
description: Pilote TCP/IP
Bug check description: This indicates that the kernel has detected critical kernel code or data corruption.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem. 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 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 06/05/2021 00:51:21 your computer crashed or a problem was reported
crash dump file: C:\Windows\MEMORY.DMP
This was probably caused by the following module: tcpip.sys (0xFFFFF80257B9B5A0)
Bugcheck code: 0x109 (0xA39FFC599CE8D6AF, 0xB3B708DFEF6B8833, 0xFFFFF80257B9B5A0, 0x1)
Error: CRITICAL_STRUCTURE_CORRUPTION
file path: C:\Windows\system32\drivers\tcpip.sys
product: Système d’exploitation Microsoft® Windows®
company: Microsoft Corporation
description: Pilote TCP/IP
Bug check description: This indicates that the kernel has detected critical kernel code or data corruption.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem. 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 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 Wed 05/05/2021 00:37:12 your computer crashed or a problem was reported
crash dump file: C:\Windows\Minidump\050521-12750-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x3F5E40)
Bugcheck code: 0x18 (0x0, 0xFFFFCD067F87C080, 0x2, 0xFFFFFFFFFFFFFFFC)
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 Wed 05/05/2021 22:52:45 your computer crashed or a problem was reported
crash dump file: C:\Windows\Minidump\050521-9781-01.dmp
This was probably caused by the following module: dxgmms2.sys (0xFFFFF80745F33C00)
Bugcheck code: 0x1E (0xFFFFFFFFC000001D, 0xFFFFF80745F33C00, 0xFFFFF80739F27600, 0xFFFFF8073956)
Error: KMODE_EXCEPTION_NOT_HANDLED
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 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 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 Wed 05/05/2021 03:38:08 your computer crashed or a problem was reported
crash dump file: C:\Windows\Minidump\050521-10671-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x3F5E40)
Bugcheck code: 0x109 (0xA39FFAE88F8035D4, 0xB3B7076EE1FE7E8C, 0xFFFFF80081A97E40, 0x1)
Error: CRITICAL_STRUCTURE_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 has detected critical kernel code or data corruption.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem. 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.


C'est bizarre de rien avoir et d'un coup ça revient
Malekal_morte
Messages : 107565
Inscription : 10 sept. 2005 13:57

Re: Blue screen nvlddmkm.sys et dxgkrnl.sys

par Malekal_morte »

Faire un memtest - pour vérifier les barrettes de mémoire RAM

et :

Installe et lance OCCT.
Lance une vidéo Youtube ou Netflix (si tu as).
Laisse tourner la vidéo 5min.
Donne une capture d'écran :
- de l'onglet Système
- des températures
- des ventilateurs
- de l'onglet puissance.
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.
  • Sujets similaires
    Réponses
    Vues
    Dernier message

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