IRQL_LESS_OR_EQUAL error in windows 10 need help

[Mr Waffles]

I have been getting this error lately on my laptop and need help.

System Information (local)
--------------------------------------------------------------------------------

Computer name: MICHAELS-LAPTOP
Windows version: Windows 10 , 10.0, build: 10586
Windows dir: C:\Windows
Hardware: GL502VT, ASUSTeK COMPUTER INC.
CPU: GenuineIntel Intel(R) Core(TM) i7-6700HQ CPU @ 2.60GHz Intel586, level: 6
8 logical processors, active mask: 255
RAM: 12743622656 bytes total




--------------------------------------------------------------------------------
Crash Dump Analysis
--------------------------------------------------------------------------------

Crash dump directory: C:\Windows\Minidump

Crash dumps are enabled on your computer.

On Sat 1/14/2017 12:29:08 PM your computer crashed
crash dump file: C:\Windows\Minidump\011417-52250-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x142970)
Bugcheck code: 0xA (0x28, 0x2, 0x0, 0xFFFFF8026859220F)
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 Sat 1/14/2017 12:29:08 PM your computer crashed
crash dump file: C:\Windows\memory.dmp
This was probably caused by the following module: ntkrnlmp.exe (nt!KeBugCheckEx+0x0)
Bugcheck code: 0xA (0x28, 0x2, 0x0, 0xFFFFF8026859220F)
Error: IRQL_NOT_LESS_OR_EQUAL
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 12/23/2016 7:30:11 PM your computer crashed
crash dump file: C:\Windows\Minidump\122316-24937-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x142970)
Bugcheck code: 0xA (0x28, 0x2, 0x0, 0xFFFFF802D620520F)
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.





--------------------------------------------------------------------------------
Conclusion
--------------------------------------------------------------------------------

3 crash dumps have been found and analyzed. No offending third party drivers have been found. Connsider using WhoCrashed Professional which offers more detailed analysis using symbol resolution. Also configuring your system to produce a full memory dump may help you.


Read the topic general suggestions for troubleshooting system crashes for more information.

Note that it's not always possible to state with certainty whether a reported driver is responsible for crashing your system or that the root cause is in another module. Nonetheless it's suggested you look for updates for the products that these drivers belong to and regularly visit Windows update or enable automatic updates for Windows. In case a piece of malfunctioning hardware is causing trouble, a search with Google on the bug check errors together with the model name and brand of your computer may help you investigate this further.

 

[Colif]

Sometimes who crashed will point out driver and go>> its this one... but other times, like this, it just blames windows which doesn't help us at all.
Can you follow option one here: http://www.tenforums.com/tutorials/5560-bsod-minidump-configure-create-windows-10-a.html
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
copy that file to documents
upload the copy from documents to a cloud server and share the link here and someone else with right software to read them will help you fix it

 

[Mr Waffles]

https://www.dropbox.com/s/mh4fw1r8qas6bhq/minidump.txt?dl=0