The computer has rebooted from a bugcheck, crash = IRQL_NOT_LESS_OR_EQ

The computer has rebooted from a bugcheck. The bugcheck was: 0x0000000a (0xfffff8a000277508, 0x0000000000000002, 0x0000000000000000, 0xfffff80003c8025b). A dump was saved in: C:\Windows\MEMORY.DMP. Report Id: 060914-63679-01.

Do I need to provide the memory dump file?

The weird this is this crash always happens when I'm not using the pc. So I don't know what triggers it.

It didn't start to occur randomly though. No I don't know when it happened but either after I tried Advanced System Orignizer 3, then found out its a scam did a system restore and thought that fixes everything.

But I tried an other program to speed up my pc and maybe that is the cause. IT is a legit program though but I disabled alot of windows services on startup and that may have caused it.

Again I'm not sure. Need to do more testing but any help is welcome.

Hello Max,

Please read the instructions here: Blue Screen of Death (BSOD) Posting Instructions, and post back with the needed information. One of our BSOD experts should be by later when able to further help. :)

Hey thanks for your reply the DM Log Collector does not work. I can't locate the zip file on desktop or anywhere else.

Also I turned back on ALL windows services and the crash occurred right in front of my nose when windows was starting up, I was adding for my programs to load on my desktop and then bang it happened.

I hope I did it alright the zip file. That nothing is missing. Cause the second tool was lagging and not loading when it was 4/5 done.

Hey any news guys? I think it occurs when I'm not using the computer. When it goes to sleep mode it happens.

I tried increasing the memory but I think I could try re-installing my gaming driver. But how do I know what driver is broken?

We can't analyse the logs without the information requested in the link Brink posted, run it again until you get the .zip file as it seems to work for everybody else.

But I have in the second post.

There are a lot of files missing from the resulting .zip file. Run the tool again and let it run its course then upload the new logs.