Irql_not_less_or_equal after overclocking

Feb 18, 2018
1
0
10
Hello everyone,

Recently I have tried to overclock my 1080ti using MSI Afterburner, and although I followed a tutorial video, I might have pushed my card a little too far.
After overclocking, I tried to launch the game Kingdom Come: Deliverance, which made my PC freeze on a black screen (the computer kept working, but I couldn't access the task manager, desktop, lock my PC etc) and I had to manually restart my PC.
I tried to launch the game a couple of times, but the problem persisted so I reverted my settings and completely removed MSI Afterburner. Everything seemed to work perfectly fine.

However, ever since the overclock (and although I restored the stock settings), I started getting random BSODs with the error code "Irql_not_less_or_equal".
I get the blue screen randomly about two times a day, it has never happened while playing games, and most crashes occur while using Google Chrome, plus Google Chrome has a harder time loading pages and HD videos.

Do you think that the overclocking had anything to do with it?
How can I possibly fix this issue?

Specs:
GPU: GTX 1080ti
CPU: I5 4670K
Ram: 16GB 1600mhz & 800mhz
PSU: 850W
1TB older HDD drive
Windows 10 64 bit

*UPDATE:
Two days ago I decided to get rid of Bitdefender because of the instabilities and website blocks caused by the recent update, and the problem was gone.
It appears that the latest update of Bitdefender was the cause of the crashes.
 
Solution
irq errors are normally drivers or maybe ram, not normally associated with overclocking

Can you follow option one here
and then do this step below: Small memory dumps - Have Windows Create a Small Memory Dump (Minidump) on BSOD

that creates a file in c windows/minidump after the next BSOD
copy that file to documents
upload the copy from documents to a cloud server and share the link here and someone with right software to read them will help you fix it :)

Colif

Win 11 Master
Moderator
irq errors are normally drivers or maybe ram, not normally associated with overclocking

Can you follow option one here
and then do this step below: Small memory dumps - Have Windows Create a Small Memory Dump (Minidump) on BSOD

that creates a file in c windows/minidump after the next BSOD
copy that file to documents
upload the copy from documents to a cloud server and share the link here and someone with right software to read them will help you fix it :)
 
Solution