Random BSOD every so often, varies between different errors.

[Dr_Faz]

Typically when I am doing something intensive on my PC like playing games, I get a BSOD with either system_service_exception, irql_not_less_or_equal, and a couple others I can't remember. I haven't been able to figure out what it is, all help is appreciated. Thank you in advance!

 

[Colif]

Can you download and run whocrashed - it will create a summary of the errors and might help us fix them

Copy/paste results in here

 

[Dr_Faz]

Can you download and run whocrashed - it will create a summary of the errors and might help us fix them

Copy/paste results in here

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

Computer name: JORDANS
Windows version: Windows 10 , 10.0, build: 14393
Windows dir: C:\WINDOWS
Hardware: ASUSTeK COMPUTER INC., SABERTOOTH 990FX R2.0
CPU: AuthenticAMD AMD FX(tm)-8350 Eight-Core Processor AMD586, level: 21
8 logical processors, active mask: 255
RAM: 17090691072 bytes total




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

Crash dump directory: C:\WINDOWS\Minidump

Crash dumps are enabled on your computer.

On Sat 2/18/2017 12:46:14 PM your computer crashed
crash dump file: C:\WINDOWS\Minidump\021817-25453-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x14A6F0)
Bugcheck code: 0x1E (0xFFFFFFFFC0000005, 0xFFFFF8000849CBE2, 0x0, 0xFFFFFFFFFFFFFFFF)
Error: KMODE_EXCEPTION_NOT_HANDLED
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 a kernel-mode program generated an exception which the error handler did not catch.
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 2/18/2017 12:46:14 PM your computer crashed
crash dump file: C:\WINDOWS\memory.dmp
This was probably caused by the following module: mbamchameleon.sys (MBAMChameleon+0x177B)
Bugcheck code: 0x1E (0xFFFFFFFFC0000005, 0xFFFFF8000849CBE2, 0x0, 0xFFFFFFFFFFFFFFFF)
Error: KMODE_EXCEPTION_NOT_HANDLED
file path: C:\WINDOWS\system32\drivers\mbamchameleon.sys
product: Malwarebytes Chameleon
company: Malwarebytes
description: Malwarebytes Chameleon
Bug check description: This indicates that a kernel-mode program generated an exception which the error handler did not catch.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
A third party driver was identified as the probable root cause of this system error. It is suggested you look for an update for the following driver: mbamchameleon.sys (Malwarebytes Chameleon, Malwarebytes).
Google query: Malwarebytes KMODE_EXCEPTION_NOT_HANDLED



On Sat 2/18/2017 12:14:52 PM your computer crashed
crash dump file: C:\WINDOWS\Minidump\021817-23203-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x14A6F0)
Bugcheck code: 0x1E (0xFFFFFFFFC0000005, 0xFFFFF8009122FBE2, 0x0, 0xFFFFFFFFFFFFFFFF)
Error: KMODE_EXCEPTION_NOT_HANDLED
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 a kernel-mode program generated an exception which the error handler did not catch.
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 2/18/2017 11:42:14 AM your computer crashed
crash dump file: C:\WINDOWS\Minidump\021817-25500-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x14A6F0)
Bugcheck code: 0xA (0xFFFF830022B00490, 0x2, 0x1, 0xFFFFF8013E82DBE2)
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
--------------------------------------------------------------------------------

4 crash dumps have been found and analyzed. A third party driver has been identified to be causing system crashes on your computer. It is strongly suggested that you check for updates for these drivers on their company websites. Click on the links below to search with Google for updates for these drivers:

mbamchameleon.sys (Malwarebytes Chameleon, Malwarebytes)

If no updates for these drivers are available, try searching with Google on the names of these drivers in combination with the errors that have been reported for these drivers. Include the brand and model name of your computer as well in the query. This often yields interesting results from discussions on the web by users who have been experiencing similar problems.


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.


Thank you much!

 

[Colif]

remove malwarebytes chameleon and update lan drivers, as often when malewarebytes is blamed for errors, its actually lan drivers to blame

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 with right software to read them will help you fix it

dump files may show more than who crashed did, in case something else is hiding in background.

 

[Dr_Faz]

remove malwarebytes chameleon and update lan drivers, as often when malewarebytes is blamed for errors, its actually lan drivers to blame

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 with right software to read them will help you fix it

dump files may show more than who crashed did, in case something else is hiding in background.

Here's the link to those files! https://drive.google.com/drive/folders/0B_6tZFo-3o8sQnN3Ym1iV3dUaFk?usp=sharing
I appreciate all your help this far man!