Jump to content

Scan Fails With Error Code 8


Recommended Posts

Hello All,

 

Apologies if I have posted this in the incorrect forum.

 

My installation of MBAM recently started producing an error code at the end of the scan. On one hand, the scan completes and tells me that no harmful items were found. It then pops up and error message: Scan Failed With Error Code 8.

 

Enlighten me?

 

Thanks.

Link to post
Share on other sites

Hello Tedford and :welcome:

Without a great deal more information, it would be very difficult to assess an error code 8.

Please read the following and individually attach the 3 requested logs in a reply to this thread: Diagnostic Logs.

The 3 files, from Step 2, to be individually attached from your desktop are: CheckResults.txt, FRST.txt and Addition.txt. Please do not Copy and Paste them into a reply.

Thank you.

Link to post
Share on other sites

Hello Tedford:

Until this issue has been resolved, please do not uninstall Spybot Search & Destroy, but please do disable it from starting service(s) and launching. Then:

Thank You. :)
Link to post
Share on other sites

Hi 1PW,

 

I followed all of your instructions to the letter, including  running the cleaner, letting the computer reboot, disabling Spybot and Avira AV, and then running the new install 2.0.3.1025 RC1. Unfortunately Error Code 8 popped up again. Should I rerun the diagnostics?

 

Thank you for your help and insight.

Link to post
Share on other sites

Hello Tedford:

Please leave Spybot Search & Destroy disabled till the issue has been resolved. However, please do allow Avira to run unless directed otherwise.

Yes - if you would post a fresh CheckResults.txt from mbam-check-2.1.1.1001.exe, that would be very helpful and also leave MBAM v2.0.3.1025 RC1 installed.

Thank you.

Link to post
Share on other sites

Hello Tedford:

Please run a MBAM v2.0.3.1025 RC1 Threat Scan with both Spybot Search & Destroy and your Avira applications disabled.

Regardless of the result, please immediately re-enable only your Avira application at the completion of the Threat Scan and let us know your results in a reply to this forum thread.

Thank you.

Link to post
Share on other sites

Hi Tedford,

 

I have been following your thread with great interest. I too had installed MBAM v 2.0.3.1025 RC1 and I had an almost identical issue except my error code was 6 instead of 8. My case was escalated and the MBAM employee tried EVERY single thing that he could think of and nothing ever solved the problem after 2 days of trying. So I finally had to revert back to MBAM v 1.75 which works fine. But I do miss all the greatly improved features of MBAM 2.0.3. I hope you will have better success than I did. I will continue following your thread and hope that a solution is found which I will try so I can get back to MBAM v 2. Best of luck to you!!!

Link to post
Share on other sites

Hi Tedford,

 

I am just curious. Have you had any further contact with an MBAM Moderator perhaps in a different posting?

 

Thanks,

 

Richard

Link to post
Share on other sites

Hi, @rwharold:

Thanks for your input.

You wrote:
 

I had an almost identical issue

Alas, problems that sound "the same" most often are not.

Each computer is unique.

Your computer runs Win XP/x86 and @Tedford's computer runs Win7/x64 (entirely different platforms), with entirely different installed software, hardware and drivers.

Moreover, the error codes you both reported are NOT the same, and @Tedford's error was under MBAM version 2.0.2, not version 2.0.3.

As such, both the problem and the solution are likely to be different.

Until the staff have had a chance to review @Tedfords logs and make expert recommendations, it would be premature & confusing at this time for a regular forum member to suggest that @Tedford revert to version 1.75 before investigation is complete.

 

@Tedford:

 

Please continue to work with @1PW and with forum staff to resolve your issues.

@1PW has already escalated your case to the staff -- someone will assist you as soon as possible.

As it is the weekend, please be patient.

 

 

Thanks to you both for your patience and understanding,

Link to post
Share on other sites

Hello Ted,

 

I will be helping you going forward.  I would like to start by getting some additional logs from you.

First, you need to set Windows to show all folders.

 

Set Windows 7 to Show all files  by doing this:

Press and hold Windows-key+E key on keyboard to start Windows Explorer   ( File Manager for Windows).

From the Windows Explorer menu options, Select Tools, then Folder Options.

Next click the View tab.

Locate and uncheck "Hide protected operating system files (Recommended).

Locate and click "Show hidden files and folders and drives. "

Click Apply > OK.

 

Go to this folder  on your system C:\ProgramData\Malwarebytes\Malwarebytes Anti-Malware\Logs

 

Locate and attach these in a reply  ( you may zip them up & send 1 file if you wish)

protection-log-2014-10-11.xml

+

protection-log-2014-10-12.xml

+

mbam-log-2014-10-11 (05-20-13).xml

 

On the Supe*Antispyware, as Pete said, make it such that it does not auto-start with Windows.

And as to Avira, it should not be a source of interference, but we should probably have you make Trusted seetings for our program in "Avira" settings.

 

For now, set Avira to off  ( and not active) so that we can make runs without it on.

Reference at BleepingComputer

http://www.bleepingcomputer.com/forums/index.php?showtopic=114351

 

In addition, Close any other opened user-app-windows  so that we have "a clear slate".

 

I'd like you to do the following:

  • Download Process Monitor.
  • Unzip and extract the contents so that PROCMON.exe is in place on your system.
  • Run procmon.exe. It will open and start capturing events.

    post-119961-0-33882200-1412872175.png]

  • Open MBAM and start a scan.
  • Wait until you see the error prompt you reported "... Failed with Error Code: ...x or y or z".
  • Go back to procmon, click File in the top left, and click on "Capture Events" to stop it from capturing events.

    post-119961-0-18726800-1412872458.png]

  • When it is finished, click file in the top left, and click on "Save..."
  • Keep note of the location the log is saved:

    post-119961-0-70689600-1412872729.png]

  • Attach the saved procmon log back to us. (If it's too big, we can provide you a link for uploading. Just let us know ;))
Thank you in advance.

Please have lots of inifnite patience and faith. Take your time and go slow thru all this.

As long as you have a hardware router between your computer and the incoming internet connection, and you do not do free-wheeling websurfing, your pc will be ok.

Again, patience because the process will take some back and forth rounds.

Plus also know, we are not always on 24x7

After you finish this round, you may turn back on the Avira.

I would like to know what other antivirus or security apps were ever installed on this box.

I see a bit of a trace of AVG. But I still would like a full history of security suites.

I see some Mcafee

C:\Program Files\McAfee Security Scan\3.8.150\McCHSvc.exe [289256 2014-04-09] (McAfee, Inc.)

and also some Spybot S & D

Link to post
Share on other sites

Maurice,

 

Thank you so much for your time and detailed instructions.

 

"Stranger than fiction..." Or so the old saying goes. I downloaded Procmon, etc. I disabled Avira. I removed Super Anti Spyware and McAfee Security Scan on Saturday (10/11). With the exception of Firefox, I closed all other apps. I opened MBAM, updated the app, and then ran a scan. SUCCESS! NO ERROR MESSAGE!

 

However, confirmation from an impartial set of eyes could verify the result.

 

As far as the security/diagnostic utilities I have ever installed on the box, they are:

 

~ Avira

~ AVG - very briefly installed and removed in favor of Avira quite some time ago

~ Spybot S&D

~ Super Anti Spyware - removed on 10/11/2014

~ Glary Utilities

~ Reg Cleaner (from Glary)

~ CC Cleaner

~ McAfee Site Advisor

~ McAfee Security Scan - removed on 10/11/2014

~ MBAM (of course!)

 

I should say I am well aware that multiple utilities may cause a conflict at some point.

 

In the MBAM Log File, I did not find protection-log-2014-10-12.xml.

 

I captured the events via Procmon. The file is, indeed, too large to upload. Please provide the link if necessary.

 

Please let me know if I have provided enough information, if you need more, and if the latest scan was successful.

 

Tedford

 

 

 

mbam-log-2014-10-11 (05-20-13).xml

protection-log-2014-10-11.xml

protection-log-2014-10-13.xml

mbam-log-2014-10-13 (00-22-03).xml

Link to post
Share on other sites

I would suggest getting and apply the AVG removal tool & the McAfee removal tool to insure no stray remains are left.
Just about any antivirus program can leave traces behind.
And then restart system.

If 32-bit --- AVG remover http://download.avg.com/filedir/util/support/avg_remover_stf_x86_2015_5501.exe
If 64-bit --- AVG remover http://download.avg.com/filedir/util/support/avg_remover_stf_x64_2015_5501.exe

McAfee uninstaller --- start at this page http://service.mcafee.com/FAQDocument.aspx?id=TS101331


The Procmon link is there in the original reply ( if you simply click on it).
http://download.sysinternals.com/files/ProcessMonitor.zip

The "error code 8" has something to do with memory.
That could possibly mean either disc space or physical RAM or virtual memory space.
Check to see how much hard drive space is free.
We will likely have to review closer all startup programs as well.

The good news is that the logs show NO malware detected.

Link to post
Share on other sites

p.s.  about "registry cleaners"   ( since I see your box has one of this type) :

 

Registry cleaners range from the non-effective snake-oil to the ok ones --- but they can lead to causing more harm than good.

Some can even lead to removing actually needed entries.

I rarely suggest that folks use these "tools".

 

Please see Ed Bott's blogpost "Why I don’t use registry cleaners"
http://www.edbott.com/weblog/2005/04/why-i-dont-use-registry-cleaners/

In the context of the notion of a registry cleaner, I would refer you to  Mark Russinovich's ( at Microsoft ) statement (from Registry Junk: A Windows Fact of Life ).   http://blogs.technet.com/b/markrussinovich/archive/2005/10/02/registry-junk-a-windows-fact-of-life.aspx

I haven't and never will implement a Registry cleaner since it's of little practical use on anything other than Win2K terminal servers and developing one that's both safe and effective requires a huge amount of application-specific knowledge.

 


There has not been a real need for registry cleaners ever since Win XP and later o.s. came out. ~ Maurice

Also see http://miekiemoes.blogspot.ca/2008/02/registry-cleaners-and-system-tweaking_13.html
 

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.
Back to top
×
×
  • 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.