Jump to content

Virus_Fighter

Honorary Members
  • Posts

    40
  • Joined

  • Last visited

Reputation

0 Neutral

Contact Methods

  • Website URL
    http://
  • ICQ
    0

Profile Information

  • Location
    Hamburg / Germany / Europe

Recent Profile Visitors

1,275 profile views
  1. Hi exile360 I made a clean install on a new HDD with Windows 7 Home Premium 32-bit. It took me a couple of hours since yesterday, but I finally succeeded ! After I downloaded MBAM - free version and updated it I made a quick scan and also a full scan with MBAM 1.44 without any problems and no funds ! Hopeful this "clean" status of my system now will remain for a long time.... Thanks again and if you agree, we declare this thread to be CLOSED
  2. Exile360, I really feel obliged to thank you and the MBAM - Team for the strong support and your efforts you provided to my problem so far ! I will let you know how things are going with my new Hard Drive and with windows 7 Thank you very much, Virus_Fighter
  3. Hi exile360, how are things going with analyzing my procmon-logs ? I am planning to replace my 3 year old Harddisk (Hitachi HTS541080G9SA00; 80GB, 5,400 rpm) within the next days and make a new install (today Vista) of Windows7, 32bit. I
  4. Hi exile360, I finally "performed". Sent you a link with the zip via Personal Message. Now I am excited to hear some results from the MBAM-Team, maybe not before next week, when "the factory" start to work again... Have a nice week-end buddy !
  5. I 've read again your post #34, in that instructions I was told to set a "filter" within the procmon-process. I did not set a filter (mbam.exe) this time, maybe that`s the reason why the procmon-log-files are so large ?
  6. Hi exile360, this time the procmon-record did work ! I'm the proud owner now of 8 brandnew *.pml - files with the MBAM full scan, which I aborted because of looping after 24 minutes. The zip-file of the 8 logs is a real fat monster: more than 500 mb (compression rate with 7zip 13%) ! How can I transmit this to you ?
  7. That`s it ! Thank you for adjusting your instructions. I did not close Procmon.exe and reopened it before the mbam-scan ! I am so stupid..... I will follow the instructions in a couple of hours, then I hope to be back with a useful log
  8. Yes, that is what I did three times before. But there are no *.pml - files on my desktop nor on the computer I will try it again.
  9. No, it only crashes after I started Malwarebytes. Maybe we save the logfile of Procmon not to the desktop but to an usb-stick/usb-external drive and hope that it will save some infos before it is crashing. Or will the logfile only by saved after finishing the mbam-scan ?
  10. No success... I tried it three times now with Procmon.exe. After some minutes of mbam-scan windows gives a notice: Procmom.exe does not respond anymore. Then I stop it and abort the mbam-scan. I can
  11. Here I am back again with bad news The issue is still there, the content of the dam**d directory .../windows/... has become smaller, but it is still looping in there ! Shall I insert c:\del *.* ???
  12. Hi Buddy exile360 that sounds very optimistic. Good !!! Well, I installed ATF Cleaner and followed your exact instructions. I did not install CCleaner, because I already have installed it earlier. I updated my "old" version but it was still a current one. Then I started it following your instructions. After it I started a full scan with MBAM (6 minutes ago, I am now at my second computer to write this post ), but I did not start it as a developer, I hope that is okay for you ! Guess what.... ... it`s still doing the full scan. Within the next 18 minutes we will have the result
  13. Okay, I updated MBAM, started as developer, did a full scan and aborted the scan when it arrives the looping point. The issue is still there This is the log file. Malwarebytes' Anti-Malware 1.44 Database version: 3876 Windows 6.0.6002 Service Pack 2 Internet Explorer 8.0.6001.18882 17.03.2010 17:11:19 mbam-log-2010-03-17 (17-11-19).txt Scan type: Full Scan (C:\|) Objects scanned: 68942 Time elapsed: 14 minute(s), 56 second(s) Memory Processes Infected: 0 Memory Modules Infected: 0 Registry Keys Infected: 0 Registry Values Infected: 0 Registry Data Items Infected: 0 Folders Infected: 0 Files Infected: 0 Memory Processes Infected: (No malicious items detected) Memory Modules Infected: (No malicious items detected) Registry Keys Infected: (No malicious items detected) Registry Values Infected: (No malicious items detected) Registry Data Items Infected: (No malicious items detected) Folders Infected: (No malicious items detected) Files Infected: (No malicious items detected) I think this is what you wanted me to do. Thanks, Virus_Fighter
  14. Hi everybody, I am back again after a vacation time. The "looping-problem" still exists, even with the newest MBAM-update, though I am glad the quick scan is fine. Before I made the last full scan yesterday, I also updated my BIOS-Version. If there is still some interest to fix it, I am with you !
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.