Écran bleu DRIVER IRQL INFERIEUR OU ÉGALE
IHaveAQuestions
Posted messages
154
Status
Member
-
billmaxime Posted messages 50526 Registration date Status Contributor Last intervention -
billmaxime Posted messages 50526 Registration date Status Contributor Last intervention -
Hi everyone,
I'm having a problem (a blue screen appearing) with my PC lately, and I haven't done anything special...
The stop code is: DRIVER IRQL NOT LESS OR EQUAL
and the failing element is: nvme.sys
I've had this before (multiple times) when I didn't reach out to the experts on this forum; it was related to the drivers of my Wi-Fi card if I remember correctly... The connection would drop, the PC would freeze, and then the blue screen. I looked into it and tinkered a bit and it didn't happen again... (I reinstalled the drivers, tried to update) but here it's apparently a different error and alone.
Can you help me fix this? I haven't done much special, and I don't really understand why Windows is suddenly targeting me...
Thanks in advance
I'm having a problem (a blue screen appearing) with my PC lately, and I haven't done anything special...
The stop code is: DRIVER IRQL NOT LESS OR EQUAL
and the failing element is: nvme.sys
I've had this before (multiple times) when I didn't reach out to the experts on this forum; it was related to the drivers of my Wi-Fi card if I remember correctly... The connection would drop, the PC would freeze, and then the blue screen. I looked into it and tinkered a bit and it didn't happen again... (I reinstalled the drivers, tried to update) but here it's apparently a different error and alone.
Can you help me fix this? I haven't done much special, and I don't really understand why Windows is suddenly targeting me...
Thanks in advance
19 answers
-
Is it normal that the link you provided is the link to my topic?
And do I have to disassemble my computer then? -
Thank you, and how can I do this concretely?
Moreover, what I forgot to mention is that when I put my PC to sleep and then leave for half an hour, when I come back and press the space bar to wake it up, I often (maybe not every time but almost) encounter a blue screen.
And then it restarts, and once I return to the Windows desktop, I notice that there is the same sound as when an USB drive is unplugged. However, I haven’t plugged anything in, so it's my SSD, or it makes a sound for no reason... but I don't believe in a loose connection because I can flip the PC in all directions, it doesn't unplug. And as I said, it is flat when this happens, clearly when I wake it up from sleep mode.-
See here:
https://lecrabeinfo.net/demarrer-windows-10-en-mode-sans-echec.html
Safe mode will successively load all drivers and will crash at the first error, which allows you to identify the culprit, but it is indeed likely that in these conditions it is not the SSD itself but its controller.
No alerts in the device manager, no recently hastily updated driver?
Once identified, the first thing to do is to see if there is a driver update that resolves the issue, but it may also be a hardware failure.
-
-
Hi, I started in safe mode and it didn't crash. It loaded, then I quickly found myself on the desktop.
I even took a screenshot of the device manager. (I even started in safe mode with networking, but the wifi didn't work). Here is the screen.
Thanks-
Hello,
Check here... https://treexy.com/products/driver-fusion/database/network-adapters/mediatek/wi-fi-6-mt7921-wireless-lan-card/ there is the driver(s) for your network card.- Certainly, but if the screenshot is in safe mode, there is no evidence to suggest that the network card is more to blame than other devices on alert, remaining to be seen if the situation is the same in the device manager during normal startup.
The various lines of investigation are summarized here:
https://neosmart.net/wiki/irql-not-less-or-equal/ likely remaining and if nothing works, a failure of some more or less removable hardware (RAM, Disk Controller...).
Malekal offers a number of tests for this purpose: https://www.malekal.com/diagnostiquer-les-problemes-materiels/
Here you can find a number of these tools: https://www.commentcamarche.net/informatique/composants/25371-tester-des-composants-de-pc-les-meilleurs-outils-gratuits/
The event viewer (critical) and system information (hardware resources, conflicts, and IRQ) can help pinpoint a problematic device.
-
-
hi
regarding your initial problem --> the failed element is: nvme.sys
check this page --> click here
give the brand and model of your PC
PS: if you don't know, type DXDIAG in search and run the command
provide the info like in my screenshot
@+
--
the radiation level is higher at the employment office than at Chernobyl-
Hello,
I saw that too, but the reported error is not exactly the same (except perhaps for a Samsung SSD).
In any case, if this is related to that Windows bug, it's a lesser evil since there is an optional Windows Update for versions 2004 and 20H2, with 21H1 seemingly not affected, so if this is the problem at hand, the first step is to directly upgrade to 21H1 if possible.
https://www.bleepingcomputer.com/news/microsoft/microsoft-fixes-windows-10-bsod-crashes-caused-by-nvme-ssds/ -
-
-
In normal mode, I don't see any orange warning triangles. Not even on the network map.
As I said before, I had encountered this issue before, and with whocrach or something like that, it would give me errors that would come suddenly in the middle of a video after a certain time, and it was related to my network card. Since then, I've tried reinstalling the drivers, and it seemed to be fixed.
Here, lately, it's the nvme.sys that's bothering me, and that one crashes when I take it out of sleep mode. I would be surprised by a loose connection; the PC is new, it's one month old. Yet when I watch 4 hours of a lecture, it doesn't flinch... -
re
in the search, type WINVER and run the command
example
tell us the version of W10
@+
--
the radiation level is higher at the employment center than at Chernobyl -
I have this
I am also in the process of installing the 21H1 update because it was indeed available.
I followed this https://www.malekal.com/verifier-etat-sante-disque-dur-ssd-smart/
and I am told that my hard drive is 100% good. -
I am also in the process of installing the 21H1 update because it was indeed available.
Let us know how it goes after the update.
@+
--
The radiation level is higher at the employment office than at Chernobyl.-
Hi, the issue with the network card has come back. The PC freezes, I lose connection, then a blue screen. I didn't have time to take a picture.
I also just got this when coming out of sleep even though it's not the same error.
I also found this: https://www.malekal.com/driverscloud-mettre-a-jour-ses-pilotes/
So I think my drivers should be fine... At least I hope.
How can I get out of this hell? I don't understand why Windows is so hard on me when it's practically brand new.
-
-
re
I had the same error code on one PC --> 0xc000021a (PC for office use, no games, etc...)
I reinstalled W10 (clean install) from a 128GB USB stick that I formatted in NTFS instead of FAT32
I had tested with a 16GB USB stick in FAT32, and the PC wouldn't boot from the stick... why, I don't know
The PC is working fine now
You can always check this page for error code 0xc000021a --> click here
=============
For your questions in the previous messages:
I even took a screenshot of the device manager. (I even started in safe mode with network support, but the Wi-Fi didn't work). Here is the screen.
For devices with alerts in the device manager in safe mode, that's not normal
In normal mode, I don't see any orange alert triangles. Not even on the network card.
In theory, that means your drivers are up to date since you don't have any alerts
I'm also in the process of installing update 21H1 since it was indeed available.
Did the update go through?
@+
--
the radiation level is higher at the unemployment office than at Chernobyl -
re
the problem with the error 0xc000021a is that the cause of the issue can be diverse and it's not obvious to find it
I understand that you are not enthusiastic about a clean install, but a reset without file loss is unlikely to change your problem
PS: I haven't tested this option
the thing with the network card has come back
do you have an alert in the device manager for the network card?
the pc is new, but don’t you think it could be infected?
@+
--
the radiation level is higher at the employment center than at Chernobyl -
I don't know if a clean install would be a solution, but in any case, it would be monumental work.
I don't know if it's infected. I just restored a backup I made a few weeks ago, and it didn't change anything; I'm still getting this.
Les rapports d'erreur sont activés sur votre ordinateur.
Répertoires de rapports d'erreur :
C:\Windows
C:\Windows\Minidump
Le dim 11-07-21 à 11:25:19, votre ordinateur a crashé ou un problème a été signalé
fichier de rapport d'erreur : C:\Windows\Minidump\071121-15890-01.dmp
Cela a probablement été causé par le module suivant : intelppm.sys (intelppm+0x138f)
Code d'erreur : 0x133 (0x1, 0x1E00, 0xFFFFF8072FCFB320, 0x0)
Erreur : DPC_WATCHDOG_VIOLATION
chemin du fichier : C:\Windows\system32\drivers\intelppm.sys
produit : Système d'exploitation Microsoft® Windows®
entreprise : Microsoft Corporation
description : Pilote de périphérique processeur
description de la vérification des erreurs : Le watchdog DPC a détecté une durée d'exécution prolongée à un niveau IRQL de DISPATCH_LEVEL ou supérieur. Cela pourrait être causé par un pilote non répondeur ou un matériel non répondeur. Cette vérification d'erreur peut également se produire en raison de processeurs en surchauffe (problème thermique).
Le crash a eu lieu dans un module Microsoft. La description du module peut donner un indice sur un périphérique non répondeur dans le système.
Le dim 11-07-21 à 11:25:19, votre ordinateur a crashé ou un problème a été signalé
fichier de rapport d'erreur : C:\Windows\MEMORY.DMP
Cela a probablement été causé par le module suivant : mtkwl6ex.sys (mtkwl6ex+0x31be9)
Code d'erreur : 0x133 (0x1, 0x1E00, 0xFFFFF8072FCFB320, 0x0)
Erreur : DPC_WATCHDOG_VIOLATION
chemin du fichier : C:\Windows\system32\drivers\mtkwl6ex.sys
produit : Adaptateurs sans fil MediaTek 802.11AX
entreprise : MediaTek Inc.
description : Pilote d'adaptateur sans fil MediaTek 802.11AX
description de la vérification des erreurs : Le watchdog DPC a détecté une durée d'exécution prolongée à un niveau IRQL de DISPATCH_LEVEL ou supérieur. Cela pourrait être causé par un pilote non répondeur ou un matériel non répondeur. Cette vérification d'erreur peut également se produire en raison de processeurs en surchauffe (problème thermique).
Un pilote tiers a été identifié comme la cause probable de cette erreur système. Il est suggéré de rechercher une mise à jour pour le pilote suivant : mtkwl6ex.sys (Pilote d'adaptateur sans fil MediaTek 802.11AX, MediaTek Inc.).
Recherche Google : mtkwl6ex.sys MediaTek Inc. DPC_WATCHDOG_VIOLATION
Le dim 11-07-21 à 11:04:47, votre ordinateur a crashé ou un problème a été signalé
fichier de rapport d'erreur : C:\Windows\Minidump\071121-16796-01.dmp
Cela a probablement été causé par le module suivant : nvlddmkm.sys (nvlddmkm+0x10a48a)
Code d'erreur : 0x133 (0x1, 0x1E00, 0xFFFFF807314FB320, 0x0)
Erreur : DPC_WATCHDOG_VIOLATION
chemin du fichier : C:\Windows\System32\DriverStore\FileRepository\nvam.inf_amd64_c6854566f73c85ac\nvlddmkm.sys
produit : Pilote en mode noyau Windows NVIDIA, Version 457.63
entreprise : NVIDIA Corporation
description : Pilote en mode noyau Windows NVIDIA, Version 457.63
description de la vérification des erreurs : Le watchdog DPC a détecté une durée d'exécution prolongée à un niveau IRQL de DISPATCH_LEVEL ou supérieur. Cela pourrait être causé par un pilote non répondeur ou un matériel non répondeur. Cette vérification d'erreur peut également se produire en raison de processeurs en surchauffe (problème thermique).
Un pilote tiers a été identifié comme la cause probable de cette erreur système. Il est suggéré de rechercher une mise à jour pour le pilote suivant : nvlddmkm.sys (Pilote en mode noyau Windows NVIDIA, Version 457.63 , NVIDIA Corporation).
Recherche Google : nvlddmkm.sys NVIDIA Corporation DPC_WATCHDOG_VIOLATION
Les fichiers de rapport d'erreur suivants ont été trouvés mais n'ont pas pu être lus. Ces fichiers peuvent être corrompus :
C:\Windows\LiveKernelReports\NDIS-20210711-1124.dmp
C:\Windows\LiveKernelReports\NDIS-20210711-1104.dmp
--------------------------------------------------------------------------------
Conclusion
--------------------------------------------------------------------------------
5 rapports d'erreur ont été trouvés et analysés. Seuls 3 sont inclus dans ce rapport. Si des fichiers de rapport d'erreur sont trouvés et qu'ils n'ont pas pu être analysés, cela signifie qu'ils sont corrompus. Comme les rapports d'erreur sont une mesure d'urgence, il n'est pas inhabituel que cela se produise, cependant, cela indique souvent un problème dans la pile de stockage. Il est suggéré d'exécuter CHKDSK sur votre disque système pour vérifier votre disque à la recherche d'erreurs.
2 pilotes tiers ont été identifiés comme étant à l'origine des crashes système sur votre ordinateur. Il est fortement suggéré de vérifier les mises à jour pour ces pilotes sur les sites Web de leurs entreprises. Cliquez sur les liens ci-dessous pour rechercher avec Google des mises à jour pour ces pilotes :
mtkwl6ex.sys (Pilote d'adaptateur sans fil MediaTek 802.11AX, MediaTek Inc.)
nvlddmkm.sys (Pilote en mode noyau Windows NVIDIA, Version 457.63 , NVIDIA Corporation)
Si aucune mise à jour pour ces pilotes n'est disponible, essayez de rechercher avec Google les noms de ces pilotes en combinaison avec les erreurs qui ont été signalées pour ces pilotes. Incluez également le nom de marque et de modèle de votre ordinateur dans la recherche. Cela donne souvent des résultats intéressants d'échanges sur le Web par des utilisateurs ayant rencontré des problèmes similaires.
Lisez le sujet sur les suggestions générales pour résoudre les crashes système pour plus d'informations.
Notez qu'il n'est pas toujours possible d'affirmer avec certitude si un pilote signalé est responsable du crash de votre système ou si la cause sous-jacente se trouve dans un autre module. Néanmoins, il est suggéré de rechercher des mises à jour pour les produits auxquels appartiennent ces pilotes et de vérifier régulièrement les mises à jour Windows ou d'activer les mises à jour automatiques pour Windows. En cas de dysfonctionnement d'un matériel causant des problèmes, une recherche avec Google sur les erreurs de vérification des erreurs en combinaison avec le nom et la marque de votre ordinateur peut vous aider à enquêter davantage là-dessus. -
Hello
You have an issue with these 2 drivers:
mtkwl6ex.sys (MediaTek 802.11AX Wireless Adapter Driver, MediaTek Inc.)
nvlddmkm.sys (NVIDIA Windows Kernel Mode Driver, Version 457.63, NVIDIA Corporation)
and a possible issue with the CPU temperature
Check out this page for the stop code of --> dpc watchdog violation --> click here
Also look at this page for the issue of drivers installed via the manufacturer's site, and via Windows Update --> click here
I'm also attaching the DDU page --> click here
See you later
--
The radiation level is higher at the unemployment office than in Chernobyl.-
I just reinstalled from a USB stick and the same problem
it crashes, making bug noises in my headset and then a blue screen of dpc watchdog violation.
I want to say that I have a dual boot with Linux and there are no problems, so if it were a hardware issue, it would also manifest on Linux.
Personally, I think there is a problem with Windows... but I have no idea what it is and why.
-
-
re
I just reinstalled from a USB and the same problem
Where does the ISO image come from?
It crashes, making bug noises in my headphones and then blue screen dpc watchdog violation.
After the installation?
I must say that I have a dual boot with Linux and there are no issues, so if it were a hardware problem, it would also manifest on Linux.
Theoretically yes..., and I would say that it's the driver that is causing the problem, not the graphics card.
Personally, I think it's Windows that has a problem... but I have no idea what and why.
The error code 0xc000021a "is broad" and the problem is difficult to pinpoint.
If you can, test your graphics card on another PC.
Also test this:
Right-click in an empty area of the taskbar --> Task Manager
In the Task Manager --> Startup, disable everything except Windows Defender.
Restart the PC and see what happens with the BSODs.
If you no longer have BSODs, reactivate the programs one by one to see which one causes the problem.
@+
-
Hi, the ISO came from the Microsoft site...
And yes, after the installation it crashed without much delay
I have a laptop, so it's hard to test the GPU on another PC
As for the startup programs, I disabled everything and then reactivated some like iCue from Corsair for my mouse because it wasn't lighting up anymore, but other than that, that's it.
Here, I simply restored the backup I had made because my tests were useless and reinstalling everything wasn't a solution either.
In fact, after the restore, the Wi-Fi didn't work right away, and in the Device Manager, Windows didn't recognize it immediately, I want to say. So, I connected an Ethernet cable and NO bugs, I finished a conference (no crackling in my headphones, and there's no crackling with music from my USB stick), updated everything little by little, etc... Then after some Windows updates that it did and after a few restarts, the network card was recognized again, and the Wi-Fi has been working for just under an hour. But I haven't had any BSODs.
I suspect this notorious network card (for Wi-Fi, not Ethernet then) is still bipolar. I'm wary that it will produce blue screens again soon...
And a question, my PC was resting on the chair, whereas here it's on a desk. (I know it shouldn't normally be) Does the fact that it's on fabric make airflow more difficult and cause crashes, due to tired fans or high temperature? Personally, I doubt it because I haven't seen any difference in CPU temperature, etc., so I think it doesn't change anything. It's rather just the network card drivers...
Also, for the crackling in my headphones, the drivers for the latter start with Realtek audio... and the Wi-Fi card Mediatek Wifi, etc.. But the Ethernet one: Realtek PCIe GBE, etc... Since there's a link with the names, maybe the drivers interfere.
I'm saying this because when the Wi-Fi bugs, the sound crackles and it always ends with a blue screen. Here, no crackling, so I theoretically shouldn't have a BSOD, FOR NOW, may God be with me.
Thank you
-
-
Hi
As for the startup programs, I've disabled everything and then reactivated a few like Corsair's iCue for my mouse because it wasn't lighting up anymore, but other than that, that's it.
No BSOD?
Did you reactivate the others to see if the PC crashes?
The wifi has been working for a little less than an hour. But I haven't had any BSODs since.
I suspect that infamous network card (for wifi, not Ethernet) is still bipolar. I'm wary of it possibly causing blue screens again soon...
With the updates, the drivers were reinstalled correctly, which means you don't have BSODs anymore (for now)
And just a question, my PC was sitting on the chair, whereas here it is on a desk.
If it’s a desktop PC, it shouldn’t change anything as the ventilation happens at the back and the sides
Of course, if the vents are blocked by the chair, that could cause issues
Also, for the crackling in my headset, the drivers for it start with Realtek audio... and the wifi card is Mediatek Wifi, etc. But the Ethernet one: Realtek pcie gbe, etc. Since there’s a link with the names, maybe the drivers are interfering.
No, because the drivers have different functions
Test and see what happens
@+
--
The radiation level is higher at the unemployment office than at Chernobyl.-
Hi, thanks.
For the startup programs, I haven't reactivated everything because there were some useless ones, so I've left some disabled. Windows Defender and Ovule are enabled... I can activate them all and then restart to see if they were the issue...
Afterwards, I hope, as you say, that the problem is resolved thanks to the update, but knowing that all of this happened suddenly... I hope it won't come back in a week or even a month...
Regarding the drivers, I understand, but it's weird that I'm experiencing crackling and then a guaranteed BSOD from the Wi-Fi drivers. But when there are no cracklings, I know in advance that the Wi-Fi will work perfectly and that, in theory, it won't crash (at least for now).
I'm going to use my PC normally, hoping it holds up. I've already made a backup to restore it in case of emergency; it's always useful. And I'll contact you again if it starts happening again, but I’ll do everything I can to prevent that. ;-)
Thanks again.
-
-
hi
For the startup programs, I didn't reactivate everything because there were unnecessary things, so I left some disabled. Windows Defender and Ovule are activated... I can activate them all and then restart to see if they were the issue...
activate them one by one to see which one is causing the BSOD
@+
--
the radiation level is higher at the unemployment office than at Chernobyl -
hi
are you still having BSOD issues?
have you tested reactivating the programs one by one to see which one is causing the problem?
if everything is fine for you, remember to mark your topic as resolved --> click here
thanks
@+
--
the radiation level is higher at the unemployment office than at Chernobyl -
Yes, I disabled all of them and it didn't change anything. So the problem isn't that...
On the other hand, when I disable my Wi-Fi card, there is nothing. So the problem seems to be with that and not a startup program in my opinion. -
re
if you need to change your Wifi card --> click here for the card
PS: when I searched, I found this --> Wifi and Bluetooth card for Asus PC for FX706LI (your PC model)
for changing the Wifi card --> click here
if you have any questions...
@+
--
the radiation level is higher at the employment center than at Chernobyl -
Hello,
A preliminary response found on the CCM Forum... https://forums.commentcamarche.net/forum/affich-37274093-blue-screen-driver-irql-not-less-or-equal
It mentions a driver "nvme.sys" or a device not properly seated in its slot. Check if it's securely in place.
--
ASUS ROG G752 VSK | QuadCore Intel i7 7700HQ | 32 GB-DDR4 | 2 SSD M.2 500 GB | 2 HDD Seagate 2TB | GeForce GTX 1070M 8 GB | 17.3" Screen (120 Hz) | DirectX 12 | Windows 10 (x64)
