Jump to content

After some time with an overclock applied, I get the Driver_IRQL_Not_Less_Or_Equal BSOD, I looked online and this is attributed to a driver issue, but I am wondering if it is simply the result of an unstable overclock? This only happens when I am running an overclock. 

Link to post
Share on other sites

It says what driver caused the issue. My notebook had several of this BSOD, and no OC, so if it happened right after you OC'd, maybe, but if not, could probably be something else.

CPU: R7 5700X3DMotherboard: ASRock B550M-ITX A/C | Cooling: Deepcool AG400 Digital w/ Corsair ML120 Elite + 1 ML120 Elite exhaust + 2 ML140 Elite intake

RAM: 2x16GB Netac DDR4 3200MT/s | GPU: Gainward RTX 3080 Phoenix (+212MHz / +1000MHz / -6% PL)

Storage: 2TB XPG S70 Blade, Seagate Barracuda 2TB, Samsung 850 Evo 250GB (caching the HD) PSU: MSI MAG A750GL

Monitor: 2x Pichau Cepheus Fuse 28" 4k 144Hz HDR | Keyboard: Corsair K100 optical-mechanical

Headphone/headset: Kuba Disco Pro/Gamer + Beyerdynamic DT-770 Pro | OS: Windows 11 Home

Mouse: Logitech G502X + Ugreen Ergonomic MouseCase: Corsair Carbide 400C

 

Link to post
Share on other sites

5 minutes ago, Iron Knickers said:

This only happens when I am running an overclock. 

Are you absolutely sure that it only happens when running an overclock? Also, what are you overclocking: GPU or CPU?

 

IRQL_Not_Less_Or_Equal means that a kernel level application (including windows itself) tried to access memory that it did not have permission for. It would be weird for you to get only that blue screen due to an overclock. 

ENCRYPTION IS NOT A CRIME

Link to post
Share on other sites

6 minutes ago, straight_stewie said:

Are you absolutely sure that it only happens when running an overclock? Also, what are you overclocking: GPU or CPU?

 

IRQL_Not_Less_Or_Equal means that a kernel level application (including windows itself) tried to access memory that it did not have permission for. It would be weird for you to get only that blue screen due to an overclock. 

CPU, yes only when OC'ing. 

Link to post
Share on other sites

8 minutes ago, Mateus Campello said:

It says what driver caused the issue. My notebook had several of this BSOD, and no OC, so if it happened right after you OC'd, maybe, but if not, could probably be something else.

Is there a log that tells me what driver caused the issue some where?

Link to post
Share on other sites

3 minutes ago, Iron Knickers said:

I OC in the mobo bios

Well, if it definitely only happens when you OC, there are two possibilities: The OC is unstable (I would expect other BSODS too), or your OC profile has had some settings changed that are incompatible with something.

 

Log is located at "%systemroot%\minidumps". Or you can use the Event Viewer if you know how, I never learned it.

ENCRYPTION IS NOT A CRIME

Link to post
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now

×