Windows 10: BSOD with stop code DRIVER_IRQL_NOT_LESS_OR_EQUAL - no Ralink Adapter

Hi, recently my computer began bluescreening frequently I think I had two or three just this week. It says that netr28x.sys is what failed, and all the other forums I've seen have had to do with a Ralink adapter. Unfortunately, when I opened the Device Manager I was unable to find that adapter. Instead, I have a d-link DWA-548 Wireless Adapter, which seems to be apart of MediaTek. I'm not sure if this the problem, but all the forums I've read have said that it has to do with an adapter. I'm attaching a folder with the minidump files, in case someone can find what the problem is. Thanks in ad

:)

 

BSOD stop code: DRIVER_IRQL_NOT_LESS_OR_EQUAL

Hi Team,
I just experienced bsod with code stop code: DRIVER_IRQL_NOT_LESS_OR_EQUAL, unfortunately, i wasnt quick enough to take a screenshot of the window.
In the attachment is the dump file.
Attachment 172878

Can anyone help track down which driver/component triggered the crash.

 

Got a BSOD with stop code DRIVER_IRQL_NOT_LESS_OR_EQUAL

hi

My lenovo 720 has been intermittently showing me a BSOD saying Stop Code: DRIVER_IRQL_NOT_LESS_OR_EQUAL What Failed: BthA2DP.sys

how should i fix this? Also the rotation sensor has stopped working

Thanks

 

BSOD stop code: DRIVER_IRQL_NOT_LESS_OR_EQUAL

Hi
Thank you for the reply and instructions.
I followed steps as described on the forum:
Use this link for the methods to turn off windows driver verifer
Enable and Disable Driver Verifier in Windows 10 Performance Maintenance Tutorials
I selected only 3 options as per instructions:

• I/O Verification
• Force pending I/O requests
• IRP logging

System was running fine and no BSOD happen.

Then I tried settings as described on windows forum
>>Use this link for the windows drive verifier test settings:
>>Driver Verifier-- tracking down a mis-behaving driver. - Microsoft Community

After the first reboot, windows booted and after username login prompt, while loading user profiles BSOD happen.
I let it run for the second time, and exactly at same point system crashed.

Stop code: DRIVER_VERIFIER_DETECTED_VIOLATION
What failed: vstor2 mntapi20 shared.sys

Looking into the system for any of the file names, I found that this is Vmware driver Virtual Storage Volume Driver.

I doubt that this crash has anything to do with the first one, but anyway i am attaching crash dumps just in case.
I am thinking to exclude VMWARE drivers from verify tool and let it run again.