Jump to content
jmdepise

BSOD ANALYSE MABAM mode rootkit

Recommended Posts

Bonjour

Je viens vous demander de l'aide concernant un BSOD a chaque analyse personnalisée avec l'option "recherche de Rootkit".

En effet, a chaque fois que je lance une analyse avec cette option cochée, un BSOD surviens après 10 secondes .

Lorsque je lance une analyse personnalisée sans l'option rootkit, l'analyse réussit.

J'ai une version premium a vie (la dernière version 3.4.4) depuis 5 ans, et c'est la première fois que cela arrive...

Tout est ok sur mon PC (RAM, DRIVERS, ZERO INFECTION, MATERIEL OK, TESTE CPU OK .....)
Je suis Helper, donc j'ai déjà fais toutes les recherches d'infection ou matériel .... 

Le BSOD surviens uniquement en lançant l'analyse MBAM 

Pourriez-vous me dire si cela concerne un bug de MBAM SVP?

I come to ask you for help regarding a BSOD with each analysis personalized with the option "search of Rootkit".

Indeed, every time I run a scan with this option checked, a BSOD will occur after 10 seconds.

When I run a custom scan without the rootkit option, the scan succeeds.

  • I have a premium version for 5 years (Version 3.4.4), and this is the first time it happens ...
  • Everything is OK on my PC (RAM, DRIVERS, ZERO INFECTION, HARDWARE OK, TEST CPU OK)
  • I am a Helper, so I have already done all the research of infection or equipment ....

 

  • The BSOD only happen by launching the MBAM analysis


Could you tell me if this concerns an MBAM bug please ?

 

Merci  pour vos réponse et votre aide

 

jmi

Edited by jmdepise

Share this post


Link to post
Share on other sites

***This is an automated reply***

Hi,

Thanks for posting in the Malwarebytes 3 Help forum.

 

If you are having technical issues with our Windows product, please do the following: 

Spoiler

If you haven't done so already, please run these two tools and then attach the logs in your next reply:

NOTE: The tools and the information obtained is safe and not harmful to your privacy or your computer, please allow the programs to run if blocked by your system.

  • Farbar Recovery Scan Tool (FRST)
    1. Download FRST and save it to your desktop
      Note: You need to run the version compatible with your system. You can check here if you're not sure if your computer is 32-bit or 64-bit
    2. Double-click to run FRST and when the tool opens click "Yes" to the disclaimer
    3. Press the "Scan" button
    4. This will produce two files in the same location (directory) as FRST: FRST.txt and Addition.txt
      • Leave the log files in the current location, they will be automatically collected by mb-check once you complete the next set of instructions
  • MB-Check
    1. Download MB-Check and save to your desktop
    2. Double-click to run MB-Check and within a few second the command window will open, press "Enter" to accept the EULA then click "OK" 
    3. This will produce one log file on your desktop: mb-check-results.zip
      • This file will include the FRST logs generated from the previous set of instructions
      • Attach this file to your forum post by clicking on the "Drag files here to attach, or choose files..." or simply drag the file to the attachment area

One of our experts will be able to assist you shortly.

 

If you are having licensing issues, please do the following: 

Spoiler

For any of these issues:

  • Renewals
  • Refunds (including double billing)
  • Cancellations
  • Update Billing Info
  • Multiple Transactions
  • Consumer Purchases
  • Transaction Receipt

Please contact our support team at https://support.malwarebytes.com/community/consumer/pages/contact-us to get help

If you need help looking up your license details, please head here: https://support.malwarebytes.com/docs/DOC-1264 

 

Thanks in advance for your patience.

-The Malwarebytes Forum Team

Share this post


Link to post
Share on other sites
3 hours ago, jmdepise said:

Bonjour


Je viens vous demander de l'aide concernant un BSOD a chaque analyse personnalisée avec l'option "recherche de Rootkit".

En effet, a chaque fois que je lance une analyse avec cette option cochée, un BSOD surviens après 10 secondes .

Lorsque je lance une analyse personnalisée sans l'option rootkit, l'analyse réussit.

J'ai une version premium a vie (la dernière version 3.4.4) depuis 5 ans, et c'est la première fois que cela arrive...

Tout est ok sur mon PC (RAM, DRIVERS, ZERO INFECTION, MATERIEL OK, TESTE CPU OK .....)
Je suis Helper, donc j'ai déjà fais toutes les recherches d'infection ou matériel .... 

Le BSOD surviens uniquement en lançant l'analyse MBAM 

Pourriez-vous me dire si cela concerne un bug de MBAM SVP?

I come to ask you for help regarding a BSOD with each analysis personalized with the option "search of Rootkit".

Indeed, every time I run a scan with this option checked, a BSOD will occur after 10 seconds.

When I run a custom scan without the rootkit option, the scan succeeds.

  • I have a premium version for 5 years (Version 3.4.4), and this is the first time it happens ...
  • Everything is OK on my PC (RAM, DRIVERS, ZERO INFECTION, HARDWARE OK, TEST CPU OK)
  • I am a Helper, so I have already done all the research of infection or equipment ....

 

  • The BSOD only happen by launching the MBAM analysis


Could you tell me if this concerns an MBAM bug please ?

 

Merci  pour vos réponse et votre aide

 

jmi

Hi! Do you use encryption on your disk drive? Or another security program that might be interfering with MBAM? 2 of the ideas I thought of, for possible BSOD when doing a rootkit scan.

Share this post


Link to post
Share on other sites

Hello plb4333
Thank you very much for your answer.


I do not have an encryption program on my pc, and windows defender is disabled.

I made a test with MBARootkit and the scan succeeds. I launched a GMER scan, no rootkit infection problem.
My hard disk (ssd crucial) is correct [CrystaldiskInfo] and the RAM are not defective.

 

Quote

Bonjour plb4333
Merci infiniment pour ta réponse.
Je n'ai pas de programme de cryptage sur mon disque dur, et Windows defender est désactivé.

J'ai fais un teste avec MBARootkit et le scan réussit. j'ai lancé un scan GMER, aucun problème d'infection rootkit.
Mon disque dur (ssd crucial) est correcte [CrystaldiskInfo] et les RAM ne sont pas défectueuses

thank you very much

 

jm

Share this post


Link to post
Share on other sites

If I was to guess, I'd say it might be a MBAM bug, and see if a later update takes care of it. Not really sure what it could be since everything sounds fine on your end.

Share this post


Link to post
Share on other sites
Quote

Oui, je pensais aussi à un probable Bug de MBAM, mais je préférais demander.

Je reviendrais après la prochaine mise a jour pour vous dire si le problème est résolu

 

Yes, I was thinking also a probable MBAM bug, but I preferred to ask for advice. 

I will come back after the next update to tell you if the problem is solved

Thank you very much

jm

Share this post


Link to post
Share on other sites

 

Quote

Bonjour

Je reviens ici juste pour vous donner l'évolution de la panne.

Toutes les mises à jours des versions antérieurs n'ont rien réparer.

Depuis cette dernière mise a jour installée (le 10 10 2018) tout est OK

Aucun BSOD .... Parfait?

Problème résolu !

jm

 

?

Share this post


Link to post
Share on other sites
Just now, jmdepise said:

Hello

I'm coming back here just to give you the evolution of the breakdown.

All updates of previous versions have nothing to repair.

Since this last update installed (the 10 10 2018) everything is OK

No BSOD .... Perfect?

Problem solved !

jm

?

 

 

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.