Steam Client Suddenly Crashing my Computer

[Pegasus Rescue Brigade]

Last month, my computer (which is less than two years old and has always run Steam perfectly) suddenly decided launching the client is grounds for a crash. Every time I attempt to log into Steam, I get a blue screen of death with the error code "IRQL_Not_Less_Or-Equal" and my computer reboots. Note this is not when I'm opening a game within Steam, this is when I'm opening Steam itself.

I've tried uninstalling and reinstalling Steam, as well as updating Windows and updating all my drivers, but nothing works! I haven't been able to use Steam or any of its games in over a month now. Is there anyone out there who might know how to fix this? I'm using a gaming laptop from Asus currently running Windows 10.

Thanks.

[🜂∴🜏 Cassie]

are you using symantec software, like norton ?

[Pegasus Rescue Brigade]

No, I don't believe I have anything by that company running. If you're asking about my security software, I use Webroot Secure Anywhere, I don't know if that matters.

[🜂∴🜏 Cassie]

have you tried the fixes in this article:
https://www.kapilarya.com/driver-irql-not-less-or-equal-bsod-in-windows-10

[Pegasus Rescue Brigade]

I will read that thoroughly and try what it suggests now. I'll post later with an update on whether it works or not.

[Pegasus Rescue Brigade]

First update: Steam DOES work if I boot the computer in safe mode. So some nonessential piece of software is running that's conflicting with it. I'm just not sure what. I guess I should continue with the steps in that article?

[🜂∴🜏 Cassie]

yes, try every possible fix, it will help narrow down what the problem is

[Pegasus Rescue Brigade]

Running Startup Repair doesn't work, it says it can't repair anything. System restore doesn't seem to help. For some reason after first launching in safe mode I can now get into the Steam Client, but still can't use all of it. Clicking on critical parts of it, like the games library, still cause the same crash, it's just happening a step later than it previously was.

The final fix on that page involves using the command prompt to delete and reinstall drivers, which sounds like a kind of dangerous fix. I'll need to do a system backup or something before I attempt that, unless someone here has a more straightforward idea.

[🜂∴🜏 Cassie]

one of the links i found related to your issue:

https://answers.microsoft.com/en-us/windows/forum/windows_10-hardware/blue-screen-of-death-irql-not-less-or-equal/47cc538b-1a96-4743-8ee8-f3c2f043568e

These crashes were related to memory corruption (probably caused by a driver).

Please run these two tests to verify your memory and find which driver is causing the problem. Please run verifier first. You do not need to run memtest yet unless verifier does not find the cause, or you want to.

If you are over-clocking anything reset to default before running these tests.
In other words STOP!!! If you do not know what this means you probably are not

1-Driver verifier
answers.microsoft.com/en-us/windows/wiki/windows_other-system/driver-verifier-tracking-down-a-mis-behaving/f5cb4faf-556b-4b6d-95b3-c48669e4c983

2-Memtest.
answers.microsoft.com/en-us/windows/wiki/windows_other-system/bsod-memory-problems-test-easily-and-completely/21c3f63f-f570-4522-b2ef-ecc7b7ff6461