Irql_not_less_or_equal after overclocking
Irql_not_less_or_equal after overclocking
Hello everyone,
I recently attempted to overclock my 1080ti with MSI Afterburner. Although I followed a tutorial video, I might have pushed the card beyond its safe limits.
After the overclock, I tried to run Kingdom Come: Deliverance, which caused my PC to freeze on a black screen. The system was still operational, but I couldn’t access the task manager, desktop settings, or lock the PC manually. I had to restart the computer myself.
I launched the game several times, but the issue continued, so I reset all settings and completely removed MSI Afterburner. Everything functioned normally afterward.
However, since the overclock was done (and I restored the original settings), I began receiving random BSODs with the error code "Irql_not_less_or_equal".
I experience a blue screen about twice a day, which never occurred during gameplay. Most crashes happen when using Google Chrome, and it seems Chrome struggles more with loading pages and HD videos.
Do you think the overclocking contributed to this problem?
How can I resolve 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 switched off Bitdefender due to instability and website blocking issues from the recent update. The crashes seem linked to that update.
Irq errors usually relate to drivers or RAM, not typically overclocking. Can you follow option one? Here we go: Small memory dumps - Windows should generate a small memory dump (minidump) during the BSOD, creating a file in c windows/minidump after the next crash. Copy that file to documents, upload it from documents to a cloud server, and share the link with someone who has the right software to assist you in resolving the issue.
Irq errors usually relate to drivers or RAM, not typically linked with overclocking. You can proceed with option one.
Small memory dumps - Windows should generate a small memory dump (minidump) during the BSOD, saving it as a file in C with minidump after the next BSOD. Transfer that file to documents, upload it from there to a cloud server, and share the link with someone who has the appropriate software to assist you.