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

Remurr loving tell me how to downgrade to win8 pls
You need a Windows install disk for a previous version, you'll need to boot with that disk instead of your HDD and you need to select the option that lets you format the Hard Drive; this will completely wipe the drive and remove everything so your new install works.

You need a Windows install disk for a previous version, you'll need to boot with that disk instead of your HDD and you need to select the option that lets you format the Hard Drive; this will completely wipe the drive and remove everything so your new install works.
i think I have a Windows eight disk somewhere

Never mind I just remembered I got rid of it
Any way I can downgrade without the disk

Never mind I just remembered I got rid of it
Any way I can downgrade without the disk
Explain to me how you think you can install a copy of Windows if you don't have something to install from.

The only other way is to get a copy of Windows on a USB and boot off there, but that is a very complicated process and requires a large USB and a lot of time.

if you don't want to lose all your junk, you can use puppy linux to move what you need to another hard drive first
The only other way is to get a copy of Windows on a USB and boot off there, but that is a very complicated process and requires a large USB and a lot of time.
4GB = large???
I recently installed windows 10 from a thumb drive and it didn't take very long once I got the drives set up right. it was only complicated because of way the drive was partitioned. since he'd be installing on a drive that already had windows on it, he'd be fine

he'd be fine
Given that he couldn't understand very clear instructions on how to clear his CMOS or what AutoBahn instructed him to do, do you really think he's going to be okay putting Windows onto a USB?

Besides, we're assuming he has another PC to set up this USB on.

do you really think he's going to be okay putting Windows onto a USB?
uh, yeah. that media creation tool microsoft provides makes it incredibly simple

If you want to help him through this, then go ahead and give him some steps. I'm guaranteeing you it's not going to be easy.
« Last Edit: June 10, 2016, 07:56:48 PM by McJob »

If windows 10 keep failing to startup it should come up with a "windows failed to start" screen where you can click advanced and get into booting into safe mode.

It's okay, clearing CMOS is the WRONG solution to this problem

Anyone who doubts the power of clearing the CMOS and it's somewhat absurd ability to fix problems that you would not expect to be even remotely related to it will suffer later in life. There are two things you should always try before doing more complicated, time consuming things when faced with an issue with your computer regardless of what the problem seems to be. Those things are simply restarting your PC and clearing your CMOS.
Sure, it might not fix the problem, but it very easily could and will cost you nowhere near as much time and frustration as any of the other solutions available. It's a case of you can't lose anything but stand to gain everything, so why would you not give it an attempt?


If windows 10 keep failing to startup it should come up with a "windows failed to start" screen where you can click advanced and get into booting into safe mode.

According to the OP he left his PC on overnight and it never stopped cycling

so why would you not give it an attempt?
Because if you understand how your computer/Windows works and the nature of the problem, you can very quickly rule out potential faults.

Windows very clearly listed the problems, and I explained in detail on the previous page what it all actually meant. The CMOS is only responsible for holding your BIOS settings. Errors involving the CMOS usually involve problems with the clock or hardware configuration settings (such as your fans not operating at the right speed).

In this case, the problem involves a kernal-level Windows driver. It's a problem with the Windows installation (or possibly a hardware fault, but that's less likely). It doesn't involve the CMOS at all. Resetting that will only wipe your BIOS settings, which may even cause problems if you have a custom boot-order or you've been overclocking your components.

if you understand how your computer/Windows works

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. Now of course, I'm not saying that it isn't a problem that will require a clean OS re-install or at least the use of Windows repair. 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.
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.

If it's quick, easy, has the potential to work and won't cost you anything if it doesn't then there's no reason to not give it a go, even if only for the sake of making sure that it isn't the solution

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.

If you're going to resort to insulting me and accusing me of making stuff up then forget off. I have no desire to argue with someone like you, especially considering you know so little about computers that you think you need to take the CMOS battery out to clear the CMOS and reconfigure the BIOS after doing so. IIRC you also made somewhat of a reputation for yourself as thinking you know what you're talking about in regards to computers without actually knowing anything other than a few things you read online. While it's certainly possible that it was Espio I just as certainly don't give a stuff either way.

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