Jump to content

burf

Members
  • Posts

    7
  • Joined

  • Last visited

Reputation

0 Neutral
  1. I recently updated my databases, and have the same problem (on XP SP3). I don't have those fonts that caused the issue, with MT. My HD is new, on a pretty new install of XP. I had already added the Fonts folder to my ignore list, and all scans completed successfully. I also checked the Fonts folder for corrupt fonts, using a Font Manager, and everything came up OK. When I dragged the Fonts folder back to Windows, the only error I received, was that it couldn't copy "arial.ttf", because the file existed, and I should rename it. After, I did a quick scan again, and MB crashed again. How would I figure out what fonts may be causing this? If need be, is there a way to just reinstall the default fonts? By the way, this never happened until recently, and I usually do a scan every few weeks. Any help appreciated... Thanks!
  2. Just upgraded to the new version of Mbam, and for the first time,during install KAV detected it as a trojan. I thought you guys might want to let KAV know, that you're not a Trojan
  3. Thanks for the responses. I actually did a memory test, over 7 hours, thinking the same thing. All came out ok. Nothing in my event logs. It's never happened before, nor did it happen with any other scans I did today to test (KAV & Spybot), which are much longer scans. It happened that first time, then I did a bit of simple maintenance (chkdsk & a defrag)... happened a second time, with the exact same error (same numbers). But the third time I tried it, a while ago, it was fine. I also do a lot of memory/cpu intensive video processing, and nothing happens. It seemed to happen shortly after the scan moved from the registry to files. Weird. I'll keep my eye on it. Thanks again for the responses... I was wondering if you guys had seen it before.
  4. I'm not affiliated with MB, but is it possible your firewall is blocking MB access to the net? I had the same problem initially, and gave MB access, since then it's been fine.
  5. I did my normal database update, before doing a quick scan today. A couple of minutes into the scan, I got ye olde Blue Screen - - Stop 0x0000000A (0x00000004, 0x00000002, 0x00000000, 0x804ED4E9) IRQL_NOT_LESS_OR_EQUAL This never happened before. Running XP Pro Sp3, GB memory. Very tight, clean install, with no problems ever. Just chugs along flawlessly, so this was a surprise. Any help/ideas would be appreciated. Thanks!
  6. I have the similar problem with registering those two dlls, since I first installed it months ago. But when I install a new version, I'll get the error messages again. If I ignore both, mbam installs, and seems to work. Even so, I reinstalled virtual basic, uninstalled mbam, rebooted, then reinstalled mbam. Same thing. So, I'm wondering if it seems to be working, and has detected a beast in the past (as well as a few documented FPs), does not registering those files present a problem? Also, I'm wondering, *Advanced Setup* suggested above, that he thought he knew the fix, but never returned to post it. Any ideas? I know my system is clean, by the way, so this seems to be otherwise related to certain system incompatibilities. Thanks for any help!
  7. I did a scan this morning, and all was clean. After updating, I got this: Adware.Agent - aspsetup.exe, which is the AOL Spyware Protection Module. The file location is: "C:\Program Files\Common Files\aolback\Comps\asp\aspsetup.exe" I imagine this is a false positive.
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.