Windows 10: Constant BSOD, IRQ_NOT_LESS_OR_EQUAL

I'm getting a BSOD every day, if not twice a day now. No new hardware has been installed on my PC. I'm running Windows 11, Version 21H2.After digging around, I found out the system creates a dump file and stores it in \Windows\minidump directory which can help identify my potential issue. Unfortunately, I have zero idea how to open and analyze these types of files. I've attached the BSOD, but not too sure how to upload the dump file. Any help here would be super appreciated.

:)

 

Installing XP : IRQ_NOT_LESS_OR_EQUAL

Hello, i am building a new computer, and while formatting windows, it gets a BSOD : IRQ_NOT_LESS_OR_EQUAL.

• i have tried multiple sticks of ram, one being generic, one being A-Data
• i have tried multiple hard drives
• i have tried multiple power supplies
• i have tried more than one windows cd

Can a faulty mobo/cpu cause this?

This is the computer specs :

• Sempron 3000+ (s754, comes included with the motherboard)
• ECS 791GX
• 2x1GB DDR400

At the same time, i have built two other computers with the same setup, i just cannot figure this one out.

 

Installing XP : IRQ_NOT_LESS_OR_EQUAL

Boot in step-by-step confirmation mode, and see what service or drive is causing the bsod.

 

KernelBase.dll is broken constant BSOD's constant game crashing.

Hi Darry,

User Profile corruption is one of the possible reasons why you are experiencing constant BSOD's on your computer. You mentioned that you ran the
System File Checker (SFC) tool, but is still getting a stop code. To further troubleshoot the issue, we suggest that you create a new User Profile and check if the issue persists.

To create a user profile, follow these steps:

• Go to Settings. Click Accounts.
• Select Family & other people.
• Select the Add someone else to this PC tab.
• Name the user as Test.
• Leave the password field blank.
• Hit Next.
• Sign in as Test user.

You may also check this link
to fix BSOD errors. Choose the situation when you experienced the problem and follow the troubleshooting steps.