Author Topic: DRIVER_IRQL_NOT_LESS_OR_EQUAL Windows 10 - Day 2  (Read 6569 times)

holy forget seriously how is clearing the CMOS supposed to do anything
it's a driver issue, and clearing the CMOS won't help one bit because it's a windows issue involving drivers and the CMOS is for the BIOS which isn't a part of the OS
how many times do you have to be told that

More times than any of you have the breath for. It works for me, it works for anyone I suggest it to and when it doesn't then oh well, no harm; no foul. The fact that you guys are getting so offended by my suggesting something will either do something or do nothing with no negative side effects is pathetic, if you disagreed with it so much then all you needed to do was ignore it rather than calling my knowledge of computers into question and insulting me over it.

How you people can get so offended over a simple suggestion that will neither harm nor inconvenience anyone is beyond me. And besides, I'm not trying to fix the bluescreen; I'm trying to fix the infinite boot loop, which I know from personal experience with several different systems can be solved by clearing the CMOS according to my method
« Last Edit: June 11, 2016, 01:03:50 AM by Tokthree »

you could just remove the battery too


All clearing the CMOS does is discard modified hardware settings in the BIOS and reload the factory defaults. Yes, this can fix SOME driver issues, but this is a waste of time and requires messing around with hardware which has more potential to go wrong(especially for someone who isn't necessarially experienced in taking apart a computer and messing with it's innards) than attempting to modify software in a way that can potentially fix the problem.

When attempting to fix a computer problem, you always point at the software first because it's the thing that usually goes wrong. If it's not the software, then it's the firmware, because that's the next most likely thing. If it's not the firmware, it's the hardware. This is a basic rule of troubleshooting any computer and you don't normally deviate from it because it's not only a waste of time, but a potentially harmful(yes, I recognize that clearing CMOS is normally harmless AT IT'S LEVEL, however, with faulty drivers, there's no telling how it may react to changes down the line) interaction.

On the note of 'irrationality' within troubleshooting computers, however, you are both right. Computers can be notably finicky, but, at the same time, they are quite straightforward. This is due to the fact that complex problems such as, say, an intermittent BIOS connection issue, can occur - error messages given from top level interfaces(the OS) can be decieving with such issues as they do not necessarially list the source problem, but simply the problem that the software encountered while trying to run.

It would be best if this is kept civil so as not to waste time.


this

also autobahn, not trying to be rude, but the link you posted earlier towards my quote was for the BSOD error in general
in terms of for the specific driver, i couldn't find a single solution

i remember getting this error when I was overclocking my CPU
i haven't had the error ever since I brought the clock and voltage down but this probably didn't help a single bit because you're on a laptop dammit
ontopic: id suggest getting drivers on a flash drive and like trying to install them, i tried to read the whole thread but i have a loving attention span of 2 seconds so i didnt and if youre stuck in a boot loop clear the cmos
« Last Edit: June 11, 2016, 05:19:06 PM by Willco2 »


it might causing the problem
Sorry about the page stretch
Woah! Please, use [img height=-number-]http://(URL)[/img]

Woah! Please, use [img height=-number-]http://(URL)[/img]
Ok thank you i forgot about that.