Bsod irql_not_less_than_or_equal

Hello Jonny and welcome to Sevenforums! :)

I've looked through the dmp files and they don't really point to anything specific that makes your computer crash, however I did find an entry in your eventlog that says that when your PC crashed it registered really high degrees in your laptop.

So what I would recommend you to do is to buy if you can get your hands on a can of compressed air to clean out the fans and if you are tech savvy enough to do a disassembly to further clean it.

Also I would recommend that you update your system:
Laptops and netbooks :: IdeaPad Y Series laptops :: IdeaPad Y410p Notebook - Lenovo Support (US)

Cheers! Boris :)

re11ding said:

Oh huh. I didn't think overheating was the issue. Usually when crashing occurs, I'm not doing anything heavy. How strange. I'll see what I can do about getting that fan cleaned up though. When it comes to updating, do you mean the bios? I'm not sure which ones I should specifically be updating here.

Well with updating, anything and everything that has got to do with system stability really.

Yeah do as Roy suggested but if you don't find anything, run driver verifier

Create a system restore point...

I would recommend that you run driver verifier. It will stress test your system and point out what is causing your system to crash

1) Open an elevated command prompt and run as administrator.
2) Type "verifier /standard /all"
3) Reboot your machine
4) Run machine again until it crashes which shouldn't take long.
5) Verifier should list the faulty driver, once known uninstall the bad driver and re-install a good one.

After the crash & reboot, go into safe mode (during post press and hold F8).

Once into safe mode disable driver verifier
1) Open an elevated command prompt as an administrator.
2) Type "verifier /reset"
3) Reboot your machine

It crashed almost immediately. Welp, second edit now. The driver that made it crash is certainly not the culprit I'm pretty certain. I've had this driver installed for much longer than the issue started to arise. Is there anyway to have Driver Verifier ignore this driver while it checks for drivers?

The driver is for using DS3 Controllers on a windows system since plugging into the controller doesn't work by default, in case anyone was wondering.

As for Lenovo and finding any information in regards to the transition between 7 to 8, I didn't find anything. It seems all they did when they made the transition was change the OS.

You said in your original post that when these crashes occurred you didn't see a blue screen rather a black one, have you tried to uninstall graphics drivers, reboot and reinstall them?

Not that I think that this is the final fix but just as a test.

BorisTheAnimal said:

You said in your original post that when these crashes occurred you didn't see a blue screen rather a black one, have you tried to uninstall graphics drivers, reboot and reinstall them?

Not that I think that this is the final fix but just as a test.

This is entirely true. I never thought of trying that. I just hope that Nvidia doesn't go and throw away all my settings once I try this. I will give that a shot on both the intel and nvidia drivers. I can't believe I'm saying this, but it'd be nice if the BSOD happened a little more frequently to even know if anything we've tried ever fixes the problem or not.

I also meant to mention, the BSOD was visible. It wasn't a flickering black screen like usual when Driver Verifier made the computer crash. Meaning either that whatever causes the crash causes that to occur or it's just something my computer does when it BSODs when fully booted, but I have no way to test that as far as I know, like a way to cause an intentional blue screen. The BSOD verifier caused happened before the "Starting Windows" even showed up.

EDIT: I have done so, uninstalled the drivers and reinstalled them. I actually have a good feeling about this to be honest, despite you saying it may not be the initial fix. I only think it may do the trick as I realized that my latest Nvidia driver update was installed on 12/31/15. This is the only kind of driver installation I did in that month and perfectly fits to where the issue starting several days later began to occur. We'll have to see how it goes.