Windows 10: Multiple IRQ_NOT_LESS_OR_EQUAL bsod with memory corruption bsod's

Hello.

I got multiple bsod's in any day when using my laptop. Some of them blaming hardware fault, others just that memory is corrupted. Here is link to answers.microsoft.com thread and there is seen what i have done so far. After last post there i have alredy got new bsod's as you can see in collected info. And after my last message there yesterday i removed all symantec software, installed back eset nod 32 antivirus and Macrium reflect backup. I hope that someone can point me what is failing, is it driver or hardware issue, because my laptop quarantee will end in middle of next month.

:)

 

Multiple IRQL_NOT_LESS_OR_EQUAL or SYSTEM_SERVICE_EXCEPTION bsod help needed

Next bsod with IRQ_NOT_LESS_OR_EQUAL.

Memory dump file is
here.

Hope that someone can figure out what is going on with my computer and drivers.

 

Hangouts Crashes Windows 10 - BSOD

BSOD on reboot after verifier.exe : LhdX64.sys --> IRQ_NOT_LESS_OR_EQUAL

DMP files are limited to last Hangouts crash before last system
restore point, it seems, as the computer was not able to recover after the verifier BSOD and I rebooted from system restore. Unless, system restore would not have erased the minidump file, in which case there simply was none.

 

Hi erki,

Welcome to the 10forums *Smile

I didn't have time to read the Microsoft, I will tomorrow *Smile

I assume that you still need help so I would ask to upload a new zip providing us new information necessary for analysis.

 

Hello.
Yes, i need You help. I'v reinstalled vmware ,oracle virtualbox and checkpoint mobile. I'm also running verifier with default settings and with all loaded none microsoft drivers selected. Issue seemd to improved after uninstalling all symantec software ( bsod's are not so frequent any more).

 

And please note, that some of latest bsod's is maybe my fault, when selecting wrong settings in verifier and set things "too tight" for eset and got bsod while laptop coming up from restart.

 

No problem *Smile
I would however recommend to remove any 3rd party AV and use Windows Defender while troubleshooting, to ensure they won't cause any conflict as some often do.

Please remove all USB devices while troubleshooting.

Daemon tools, Alcohol 120% and Power Archiver Pro uses SCSI Pass Through Direct (SPTD), which is a well known cause for BSOD's.
Please remove Daemon Tools and run the SPTD pass through remover.

• Uninstall Daemon Tools
• Download the SPTD standalone installer and follow these steps:
  • Double click the executable to open it
  • Click on the button shown below

If the button is grayed out, like in the image, there is no more SPTD installation on your system, and you can close the window

No problem, there is an 'easy' method for quickly finding out if a problem is a hardware issue or a driver issue.
I would suggest to read my post carefully and below quote for recovery instructions.
My post is about using driver verifier in an advanced way, using all options in driver verifier on all available drivers but in phases to prevent certain issues like boot problems.

Warning Please make a backup of your important files and get your rescue media or create one.
Please create a restore point.
Please follow this tutorial to run driver verifier.

Driver verifier stresses your drivers and will crash your pc if any driver fails due to a violation.

Driver verifier should be performed for a max of 48 hours, or when you have a bluescreen, whatever comes first.

If driver verifier has found a violation and you can't get back into windows normally, try to boot into safe mode and reset in safe mode driver verifier, or in the troubleshooting options open command prompt and type verifier /reset.



Note Your system will act very sluggishly while driver verifier is enabled, this is normal as your drivers will be being subjected to heavy testing in order to make them crash.

 

Hello.
Removed Eset NOD 32 and seems that Defender taked over *Smile
Uninstalled Daemon Tools Pro, and SPTD install says that there are nothing installed ( uninstall is grayed out).
I readed you post and runned verifier with setting you described in you post. Just after restarting ( not while loading winddows) for verifier to start running, got new bsod INTERRUPT_EXCEPTION_NOT_HANDLED.
Can't remove all usb devices, because this is laptop and some of built in hardware is connected to usb. Removed logitech unified receiver after i got bsod (i didn't remembered it stayed connected... ).

 

Diagnostics Test

Clean boot
Please try the following:

• Open taskmanager
  • Go to the tab startup
  • disable everything
• Search msconfig and open it
  • Go to the tab services
  • Check 'hide microsoft services'
  • Uncheck all other services
  • Click apply and click ok
• Reboot if asked

See if the problem persist, if the problem does not persist enable in the startup tab in taskmanager 1 item and in the services tab in msconfig also 1 service, reboot and see if the problem persist. Keep doing this until you find the culprit or there is nothing left.

 

Hi, did both. Nothing happened, when averything was disabled. Enabled all vmware services and got bsod IRQL_NOT_LESS_OR_EQUAL after restart. next disabled vmware usb and got new bsod REFERENCE_BY_POINTER after restart. this one is saying that process failing was sqlsrv.exe ?

 

Uninstall VMware temporary.

Sqlsrv.exe is a part of the program 'Microsoft SQL Server', see here for more information about this file

 

Enabled in hour basis services in msconfig ( enabled logical group like all nvidia services etc, let it run an hour) and no bsod happened on sunday. but after let laptop to run overnight got new bsod after midnight ( I was not using laptop for hours). This time it is SPECIAL_POOL_DETECTED_MEMORY_CORRUPTION.
Now i will reinstall vmware, because i need it for work.

 

I've analyzed the crashes of the last few days (19th, 18th & 17th), some flag a driver but most do not where all are caused by driver verifier.

It is safe to say that this is a hardware issue.

 

Thank You. Laptop is going to supplier tests tomorrow. Got multiple bsod's today.