irql_not_less_or_equal windows 10 opening lid laptop (Dell XPS)

Hey all,

I've been getting a really annoying issue/BSOD since yesterday (24/6/2019) on my Dell XPS 15 (9560).

It started first thing in the morning when I arrived at work, I opened my laptop and after a minute or 2 of use, I get a BSOD (irql_not_less_or_equal).

After I restarted and logged in again, I could use my laptop without any issues. However, during break, I closed the lid since I have to in regards to work safety and file privacy... So I closed the lid. After I opened it again, I got almost exactly the same time of use before I got the same BSOD.

To further validate the issue, I tested it a few times again and got the same result each time. This means that for 2 days now, I can't close or sleep my laptop during my work shift since everything will be closed and gone when I open it again due to the BSOD.

You can understand that this is a big issue knowing that I use my laptop for work. Putting it to sleep when I'm not around is essential for business privacy.

I have obviously tried some things myself first, before posting here. I used "Driver Booster Pro" to check all my drivers (something I've been doing for years) and found no missing,broken or faulty drivers.

I also installed every windows update up to this day which puts me at "Windows 10 HOME v. 1903"

After that, I check on Dell's website to make sure I had the latest BIOS and indeed had to update the firmware and everything to get it up-to-date. This means that I now have XPS_9560_1.14.3

Lastly, I also ran my antivirus FULL SCAN and used CMD to run sfc /scannow.

After all these attempts, I just had another BSOD before writing since I had to open my laptop an hour ago to start my work.

I haven't included any images or files here yet since I don't know which ones would be useful to you to help me solve this, so I'm happy to know what you need.

I really need this issue solved ASAP since I need to be able to work.

Thanks in advance!

Sounds like a sleep mode is to blame... Can you disable it and use hibernation mode instead?

krzemien said:

Sounds like a sleep mode is to blame... Can you disable it and use hibernation mode instead?

What do you mean exactly with 'disable'? Having no sleep mode at all or changing it to another state? Since I obviously don't want my laptop doing anything when closed...

Let me answer you in this way: My work Surface Laptop has felt generally unstable once it went to sleep (standard lid closure scenario) - it has not been crashing per se once woken up, but was generating numerous LiveKernelEvents upon powering up (so: semi-crashes, but from which OS was able to recover) and felt rather unstable afterwards.

All these issues went away once I disabled sleep mode (admittedly by fiddling registry somewhere).

Attachment 238311

krzemien said:

Let me answer you in this way: My work Surface Laptop has felt generally unstable once it went to sleep (standard lid closure scenario) - it has not been crashing per se once woken up, but was generating numerous LiveKernelEvents upon powering up (so: semi-crashes, but from which OS was able to recover) and felt rather unstable afterwards.

All these issues went away once I disabled sleep mode (admittedly by fiddling registry somewhere).

Attachment 238311

Ok, so how do you suggest I do this?

Any of these scenarios will probably do:

windows 10 disable sleep - Google Search

Start with just settings change within Power Settings / Options / Plans, and leave any registry tweaks for later.

And unless it's enabled already you could turn hibernation on (as I did) so when the lid closes, laptops hibernates. Drawback is slightly longer wake-up time (and hopefully nothing else, Windows OS does not really handle any of these sleep / hibernation modes well like Apple hardware does - IMHO, naturally).

Still , it would be good to narrow down what's the exact culprit.

krzemien said:

Any of these scenarios will probably do:

windows 10 disable sleep - Google Search

Start with just settings change within Power Settings / Options / Plans, and leave any registry tweaks for later.

And unless it's enabled already you could turn hibernation on (as I did) so when the lid closes, laptops hibernates. Drawback is slightly longer wake-up time (and hopefully nothing else, Windows OS does not really handle any of these sleep / hibernation modes well like Apple hardware does - IMHO, naturally).

Still , it would be good to narrow down what's the exact culprit.

Indeed I could use that as a temporary solution, but I obviously want to fix the BSOD cause eventually since I never had this issue and never want it to happen again.

Do you know what has changed in the last couple of days? Anything you (knowingly or not) installed?

If in doubt, check Reliability app and see what shows up there.

krzemien said:

Do you know what has changed in the last couple of days? Anything you (knowingly or not) installed?
If in doubt, check Reliability app and see what shows up there.

Mainly software updates such as VLC and Teamviewer nothing out of the ordinary. What is "Reliability app" by the way?

View Reliability History in Windows 10