Jump to content
SkeeterVT

Installing Updated MB3 Causing BSOD (Kernel Security Check Failure)

Recommended Posts

I'm having a problem when I try to install the latest updated version of Malwarebytes 3. Every time I try to install it -- even in Safe Mode -- it triggers a BSOD crash (Kernel Security Check Failure).

I have a Lenovo ThinkPad X220 Tablet, with Windows 10 Professional 64-bit.

Here is the relevant crash info, as compiled by WhoCrashed:

* * *

Crash dump directory: C:\WINDOWS\Minidump
Crash dumps are enabled on your computer.

On Sun 7/16/2017 1:46:34 PM your computer crashed
crash dump file: C:\WINDOWS\Minidump\071617-92406-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x14ECE0)
Bugcheck code: 0x139 (0x3, 0xFFFFC280E178B930, 0xFFFFC280E178B888, 0x0)
Error: KERNEL_SECURITY_CHECK_FAILURE
file path: C:\WINDOWS\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: The kernel has detected the corruption of a critical data structure.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time. 


On Sun 7/16/2017 1:46:34 PM your computer crashed
crash dump file: C:\WINDOWS\memory.dmp
This was probably caused by the following module: mbamswissarmy.sys (MBAMSwissArmy+0x389F6)
Bugcheck code: 0x139 (0x3, 0xFFFFC280E178B930, 0xFFFFC280E178B888, 0x0)
Error: KERNEL_SECURITY_CHECK_FAILURE
file path: C:\WINDOWS\system32\drivers\mbamswissarmy.sys
product: Malwarebytes SwissArmy
company: Malwarebytes
description: Malwarebytes SwissArmy
Bug check description: The kernel has detected the corruption of a critical data structure.
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: mbamswissarmy.sys (Malwarebytes SwissArmy, Malwarebytes).
Google query: Malwarebytes KERNEL_SECURITY_CHECK_FAILURE

 


Conclusion


2 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:
mbamswissarmy.sys (Malwarebytes SwissArmy, 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. 

 

* * *

Based on the above information, any solution to this problem will be greatly appreciated. 

Share this post


Link to post
Share on other sites

Sorry for the delay in responding.  I didn't see a notification of your posting, nor did I see your posting when checking the forum page.

First, Please run this report collecting tool so that we can provide a complete analysis: (from the pinned topic at the top of the forum):  https://forums.malwarebytes.org/topic/170037-blue-screen-of-death-bsod-posting-instructions-windows-10-81-8-7-vista/

FYI - I don't often use the Perfmon report, so if it doesn't work please just let me know.
NOTE:  On problem systems it can take up to 20 minutes for the log files to complete.  Please be patient and let it run.

If you still have problems with it running, there's an alternate tool here (direct download link):  https://github.com/blueelvis/BSOD-Inspector/releases/download/1.0.5/BSODInspector-1.0.5.exe

NOTE:
Please zip up the (.ZIP) files - do not use .RAR, .7z or other compression utilities.
.ZIP is the type file that can be uploaded to the forums.

 

Then, while waiting for a reply, please run Driver Verifier according to these instructions:  http://www.carrona.org/verifier.html
In order to speed things up, if it doesn't have a BSOD within the first hour or two - then run the MBAM installer to force a BSOD.
Do this a couple of times so we'll have several memory dumps to look at.

Good luck!

Share this post


Link to post
Share on other sites

Share this post


Link to post
Share on other sites

Hello @SkeeterVT:

Just to save @usasma the trouble, for the future, all the individual files can be copied into one folder, then:

All Microsoft Windows systems are now capable of producing compressed/zipped archives if the source is/are not too large.

     How to Zip a file or folder.

To compress (or zip) a file or folder:

  1. Locate the file or folder that needs to be compressed.
  2. Single-right-click the file or folder, then move the display's pointer to hover over Send to, and then single-left-click Compressed (zipped) folder.


A newly compressed .zip archive is created in the same location.  To rename it (if needed), single-right-click the folder, left-click Rename, and then type the new name.

Reference: Compress and uncompress files (zip files)

Thank you.

Share this post


Link to post
Share on other sites

Please do this:

MSINFO32:
Please go to Start and type in "msinfo32.exe" (without the quotes) and press Enter
Save the report as an .nfo file, then zip up the .nfo file and upload/attach the .zip file with your next post.
Also, save a copy as a .txt file and include it also (it's much more difficult to read, but we have greater success in getting the info from it).

If you're having difficulties with the format, please open an elevated (Run as administrator) Command Prompt and type (or copy/paste) "msinfo32 /nfo %USERPROFILE%\Desktop\TEST.NFO" (without the quotes) and press Enter.  Then navigate to Desktop to retrieve the TEST.NFO file.  If you have difficulties with making this work, please post back.  Then zip up the .nfo file and upload/attach the .zip file with your next post.
 

You ZIP files by right clicking on the folder that they're in, then select "Send to", then select "Compressed (zipped) folder"
The ZIP archive will be made in the same location as the folder is in.

If you're still not able to zip it up and upload it, then please upload the file to a free file-hosting service (such as OneDrive).
Ensure that it's shared, and then post a link to it here.

As far as I can see, there are no memory dumps on your system (from the KernelDumpList.txt file)
As such, we'll have to look for evidence of the BSOD's in the MSINFO32.nfo file.
 

Share this post


Link to post
Share on other sites

Unfortunately, I had to reinstall Windows 10 in order to replace the corrupt file that kept triggering my laptop's repeated BSOD crashes. The file was in the OS itself, but I was unable to identify it -- let alone isolate and fix it. 

Edited by SkeeterVT

Share this post


Link to post
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now

  • Recently Browsing   0 members

    No registered users viewing this page.

×
×
  • Create New...

Important Information

This site uses cookies - We have placed cookies on your device to help make this website better. You can adjust your cookie settings, otherwise we'll assume you're okay to continue.