Computer is Hard Rebooting - IRQL_NOT_LESS_OR_EQUAL

Hey Everyone,

For the longest time I have had my computer hard reboot at certain times, typically during gaming sessions. I have already ruled out that its an overheating situation and was hoping someone with experience reading minidump files can give me some insight into what exactly is causing the problem for me. Thanks in advance!

https://drive.google.com/open?id=0B3RWhe9je1RsbHBVLV9vN...
https://drive.google.com/open?id=0B3RWhe9je1RsU19NNm1Za...
https://drive.google.com/open?id=0B3RWhe9je1RsT2U1M21tX...
https://drive.google.com/open?id=0B3RWhe9je1Rsel9SWHo3V...



Crash dump directory: C:\WINDOWS\Minidump

Crash dumps are enabled on your computer.

On Sat 10/22/2016 8:50:43 AM GMT your computer crashed
crash dump file: C:\WINDOWS\Minidump\102216-5781-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x14A2C0)
Bugcheck code: 0xA (0xFFFFA58C68234DD0, 0xFF, 0x0, 0xFFFFF8024FC54C38)
Error: IRQL_NOT_LESS_OR_EQUAL
file path: C:\WINDOWS\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This indicates that Microsoft Windows or a kernel-mode driver accessed paged memory at DISPATCH_LEVEL or above.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.



On Fri 10/21/2016 4:12:31 PM GMT your computer crashed
crash dump file: C:\WINDOWS\Minidump\102116-5968-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x14A2C0)
Bugcheck code: 0xA (0xFFFFD8898CE33190, 0xFF, 0x0, 0xFFFFF8025904FC38)
Error: IRQL_NOT_LESS_OR_EQUAL
file path: C:\WINDOWS\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This indicates that Microsoft Windows or a kernel-mode driver accessed paged memory at DISPATCH_LEVEL or above.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.



On Fri 10/21/2016 7:19:44 AM GMT your computer crashed
crash dump file: C:\WINDOWS\Minidump\102116-6031-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x14A2C0)
Bugcheck code: 0xA (0xFFFFDD0122813580, 0xFF, 0x0, 0xFFFFF800CE452C38)
Error: IRQL_NOT_LESS_OR_EQUAL
file path: C:\WINDOWS\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This indicates that Microsoft Windows or a kernel-mode driver accessed paged memory at DISPATCH_LEVEL or above.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.



On Wed 10/19/2016 7:56:13 AM GMT your computer crashed
crash dump file: C:\WINDOWS\Minidump\101916-8390-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x14A2C0)
Bugcheck code: 0xA (0xFFFFDA0C87084A60, 0xFF, 0x0, 0xFFFFF800533E7C38)
Error: IRQL_NOT_LESS_OR_EQUAL
file path: C:\WINDOWS\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This indicates that Microsoft Windows or a kernel-mode driver accessed paged memory at DISPATCH_LEVEL or above.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.


---Edit---

I do not get an actual BSOD, the system just hard reboots with no error.

Also, a side observation (not sure if its correlated) but the computer has difficulty keeping the current time. Consistently, the time shown on the computer is completely incorrect. I know that time is kept by the CMOS battery so this could be completely unrelated but I felt as though it should be mentioned.

Please remove all pirated programs and such from your system before we can start troubleshooting.
The Forum Rules is meant for everything regarding piracy

• Discussing it,
• Asking for guidance,
• Asking for a crack,
• The use of it,
• Etc.

4) No piracy or discussion of piracy allowed at all. Such as software, music, videos and other intellectual property violations (e.g. downloading youtube videos locally etc).

Can I be directed to exactly what is being flagged as pirated software? I don't actively have anything on my system that has been pirated but if I could be informed as to what the problem software is, I can remedy the situation more rapidly.

----Edit-----
I'm gonna venture to guess my hosts file is what led to the conclusion. I have removed the offending entries from the hosts file as they were there from a while ago.

The hosts file is indeed what led to it :)

Quick question, is the current problem an unexpected shutdown/restart, a BSOD or all of them?

Please fill in your system specs

Please follow this tutorial and download the tool. The tool will give you detailed information about your system specs, please fill in your system specs more completely including PSU, cooling and other used stuff like mouse, keyboard, monitor, case, etc.
The PSU, cooling and other stuff are NOT mentioned in the tool.

In the left corner below in your post you find 'My System Specs'. After clicking it you can find a link a little below that says 'Update your System Spec', click on this link to get to the page where you can fill in your system specs.

Glad to hear and thanks for posting your solution :)

How old is the hardware?