2926
Off Topic / Re: DRIVER_IRQL_NOT_LESS_OR_EQUAL Windows 10 - Day 2
« on: June 11, 2016, 12:05:25 AM »That's one hell of an insinuation there. If you truly think that OS/Hardware problems can be perfectly diagnosed and resolved according to the book then you've got a hell of a lot to learn about the irrational bullstuff that is computers.No, it's YOU who needs to understand more about how computers work.
Computer technology wouldn't be as advanced as it is in this modern era if computers were "irrational". There's nothing "irrational" about how PCs work, it's just that you may not have a grasp on all of the factors involved when a PC develops a problem (such as a harmless program developing a memory leak in a certain function which you've never used before).
What I am saying is that if you don't try the most basic "cure-all" solutions first then you're going to feel like a real loving idiot later if your big, time consuming solution doesn't work out and then, when you try it out of desperation, these "cure-all" solutions fix your problem completely despite it being completely unrelated to what should be able to what those solutions are supposed to do.Yes, let's get everybody to clear their BIOS settings which involves opening the case, discharging yourself and pulling/replacing the battery and then reconfiguring the BIOS just because something isn't working quite right.
Your solution is not a "cure-all", you loving idiot. It will only help in very specific situations that involve the BIOS doing something wrong (such as setting the clock to the wrong date and not retaining clock settings from your OS). The CMOS has NOTHING TO DO WITH WINDOWS DRIVERS, WHICH THE BLUE SCREEN VERY CLEARLY POINTED OUT AS BEING THE FAULT.
Starbound would presumably like to get his PC back and running ASAP. Pulling the CMOS battery is only going to waste more time that could be spent getting driver replaced.
I will not even attempt to regale you the many tales of my being left completely dumbfounded when a problem with my OS, which I spent all day attempting to fix using various guides and threads online, is instantaneously resolved once I clear the CMOS.Which you're either making up or which you didn't understand the problem clearly.