Originally Posted by Forceman
IRQL not less or equal BSODs are normally driver problems. The BSOD should tell you what driver it was the generated the error (near the bottom of the screen). Did you see what it said, or maybe post a picture of the BSOD?
IRQL_NOT_LESS_OR_EQUAL bugchecks happen due to a process or device driver trying to access protected memory locations that they don't have permission to access. It can also be related a IRQL attempting to accesses a memory address that is too high.
This can be caused by device drivers, memory issues, unstable overclocks especially, etc.
It's important to remember that even if the BSOD's true cause is the unstable overclock, the bugcheck we are seeing is simply because that's what Windows knows what last happened. The unstable OC could have caused an incorrect IRQL and that's the last thing Windows knew happened, so that's what it labeled it as.
Once we have the OC out of the way, then it's worth troubleshooting. An overclocked system adds way too many variables and can over-complicate things.
yes I did see this code 0x00000001
From the screenshot that appears to be a 0xD1 which would be a DRIVER_IRQL_NOT_LESS_OR_EQUAL. However, a 0x00000001 bugcheck is APC_INDEX_MISMATCH. Essentially, the kernel detected a mismatch of thread and asynchronous procedure call (APC) indexes.
Again, bring the OC to stock so we can be sure it's not related to the OC. After that, report back and I will assist you.Edited by pjBSOD - 8/14/13 at 6:46pm