Jump to content

Search the Community

Showing results for tags 'crashing'.

  • Search By Tags

    Type tags separated by commas.
  • Search By Author

Content Type


  • Announcements
    • Malwarebytes News
    • Beta Testing Program
  • Malware Removal Help
    • Windows Malware Removal Help & Support
    • Mac Malware Removal Help & Support
    • Mobile Malware Removal Help & Support
    • Malware Removal Self-Help Guides
  • Malwarebytes for Home Support
    • Malwarebytes for Windows Support Forum
    • Malwarebytes for Mac Support Forum
    • Malwarebytes for Android Support Forum
    • Malwarebytes for iOS Support
    • Malwarebytes Privacy
    • Malwarebytes Browser Guard
    • False Positives
    • Comments and Suggestions
  • Malwarebytes for Business Support
    • Malwarebytes Nebula
    • Malwarebytes Nebula Modules
    • Malwarebytes Endpoint Security
    • Other Malwarebytes Business Products
    • Malwarebytes Business Products Comments and Suggestions
  • Malwarebytes Tools and Other Products
    • Malwarebytes AdwCleaner
    • Malwarebytes Junkware Removal Tool Support
    • Malwarebytes Anti-Rootkit BETA Support
    • Malwarebytes Techbench USB (Legacy)
    • Malwarebytes Secure Backup discontinued
    • Other Tools
    • Malwarebytes Tools Comments and Suggestions
  • General Computer Help and Security Updates
    • BSOD, Crashes, Kernel Debugging
    • General Windows PC Help
  • Research Center
    • Newest Rogue-Ransomware Threats
    • Newest Malware Threats
    • Newest Mobile Threats
    • Newest IP or URL Threats
    • Newest Mac Threats
    • Report Scam Phone Numbers
  • General
    • General Chat
    • Forums Announcements & Feedback

Find results in...

Find results that contain...

Date Created

  • Start


Last Updated

  • Start


Filter by number of...


  • Start





Website URL






Found 12 results

  1. I'm having an odd problem, and I don't know if anyone can help, because it's so specific. I'm running windows 7, and I'm trying to use a Wacom Bamboo tablet. I had been using it, previously with no issues, but at some point, the tablet's settings crash Malwarebytes. Essentially, I'm stuck in a situation where my antivirus can't run while the tablet is installed. If somebody can help me I'd very much appreciate it, because I don''t want to have to choose between my computer's security and using my device.
  2. Hi MB team and users I’ve been looking at the event viewer as of this moment and I see some fault errors/crash’s caused by MLAEWAREBYTES v3 , others MBv3 processes all are to crashing which windows have to already created a Dumpfiles for them , just in case if they needed! in meanwhile I do not know whatsoever if someone’s else had the same crashing issue or not ? Windows event viewer report that the faulting application is MALWAREBYTES , so MBv3 still has an unresolved bugs! Log Name: Application Source: MBAMService Date: 1/11/2019 4:38:52 PM Event ID: 0 Task Category: None Level: Information Keywords: Classic User: N/A Computer: Description: Service stopped Event Xml: <Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event"> <System> <Provider Name="MBAMService" /> <EventID Qualifiers="0">0</EventID> <Level>4</Level> <Task>0</Task> <Keywords>0x80000000000000</Keywords> <TimeCreated SystemTime="2019-01-11T13:38:52.852598900Z" /> <EventRecordID>21919</EventRecordID> <Channel>Application</Channel> <Computer></Computer> <Security /> </System> <EventData> <Data>Service stopped</Data> </EventData> </Event> Log Name: Application Source: Application Error Date: 1/11/2019 4:38:49 PM Event ID: 1000 Task Category: (100) Level: Error Keywords: Classic User: N/A Computer: Description: Faulting application name: malwarebytes_assistant.exe, version:, time stamp: 0x5b9bcc2c Faulting module name: Qt5Core.dll, version:, time stamp: 0x5b9bc256 Exception code: 0xc0000005 Fault offset: 0x001b91fe Faulting process id: 0x11f4 Faulting application start time: 0x01d4a9b2ef0deabc Faulting application path: C:\Program Files\Malwarebytes\Anti-Malware\malwarebytes_assistant.exe Faulting module path: C:\Program Files\Malwarebytes\Anti-Malware\Qt5Core.dll Report Id: 0bd7a36c-c927-4795-88f8-a25fc1c87974 Faulting package full name: Faulting package-relative application ID: Event Xml: <Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event"> <System> <Provider Name="Application Error" /> <EventID Qualifiers="0">1000</EventID> <Level>2</Level> <Task>100</Task> <Keywords>0x80000000000000</Keywords> <TimeCreated SystemTime="2019-01-11T13:38:49.117424400Z" /> <EventRecordID>21918</EventRecordID> <Channel>Application</Channel> <Computer></Computer> <Security /> </System> <EventData> <Data>malwarebytes_assistant.exe</Data> <Data></Data> <Data>5b9bcc2c</Data> <Data>Qt5Core.dll</Data> <Data></Data> <Data>5b9bc256</Data> <Data>c0000005</Data> <Data>001b91fe</Data> <Data>11f4</Data> <Data>01d4a9b2ef0deabc</Data> <Data>C:\Program Files\Malwarebytes\Anti-Malware\malwarebytes_assistant.exe</Data> <Data>C:\Program Files\Malwarebytes\Anti-Malware\Qt5Core.dll</Data> <Data>0bd7a36c-c927-4795-88f8-a25fc1c87974</Data> <Data> </Data> <Data> </Data> </EventData> </Event> Log Name: Application Source: Application Error Date: 11/6/2018 10:48:54 PM Event ID: 1000 Task Category: (100) Level: Error Keywords: Classic User: N/A Computer: Description: Faulting application name: mbam.exe, version:, time stamp: 0x5bc8b269 Faulting module name: Qt5Core.dll, version:, time stamp: 0x5b9bc256 Exception code: 0xc0000005 Fault offset: 0x0019d749 Faulting process id: 0x11c4 Faulting application start time: 0x01d476099f92527d Faulting application path: C:\Program Files\Malwarebytes\Anti-Malware\mbam.exe Faulting module path: C:\Program Files\Malwarebytes\Anti-Malware\Qt5Core.dll Report Id: 2b61374f-a1b1-419b-9f8d-0165659b0101 Faulting package full name: Faulting package-relative application ID: Event Xml: <Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event"> <System> <Provider Name="Application Error" /> <EventID Qualifiers="0">1000</EventID> <Level>2</Level> <Task>100</Task> <Keywords>0x80000000000000</Keywords> <TimeCreated SystemTime="2018-11-06T19:48:54.253776700Z" /> <EventRecordID>3599</EventRecordID> <Channel>Application</Channel> <Computer></Computer> <Security /> </System> <EventData> <Data>mbam.exe</Data> <Data></Data> <Data>5bc8b269</Data> <Data>Qt5Core.dll</Data> <Data></Data> <Data>5b9bc256</Data> <Data>c0000005</Data> <Data>0019d749</Data> <Data>11c4</Data> <Data>01d476099f92527d</Data> <Data>C:\Program Files\Malwarebytes\Anti-Malware\mbam.exe</Data> <Data>C:\Program Files\Malwarebytes\Anti-Malware\Qt5Core.dll</Data> <Data>2b61374f-a1b1-419b-9f8d-0165659b0101</Data> <Data> </Data> <Data> </Data> </EventData> </Event> Log Name: Application Source: Application Error Date: 12/27/2018 5:36:30 AM Event ID: 1000 Task Category: (100) Level: Error Keywords: Classic User: N/A Computer: Description: Faulting application name: mbamtray.exe, version:, time stamp: 0x5c070ada Faulting module name: Qt5Core.dll, version:, time stamp: 0x5bd23201 Exception code: 0xc0000005 Fault offset: 0x0018dc19 Faulting process id: 0x1908 Faulting application start time: 0x01d49d8ceee8ae0c Faulting application path: C:\Program Files\Malwarebytes\Anti-Malware\mbamtray.exe Faulting module path: C:\Program Files\Malwarebytes\Anti-Malware\Qt5Core.dll Report Id: d2c51ac5-df18-4bd4-b995-eee6cf4d0a64 Faulting package full name: Faulting package-relative application ID: Event Xml: <Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event"> <System> <Provider Name="Application Error" /> <EventID Qualifiers="0">1000</EventID> <Level>2</Level> <Task>100</Task> <Keywords>0x80000000000000</Keywords> <TimeCreated SystemTime="2018-12-27T02:36:30.009463300Z" /> <EventRecordID>18681</EventRecordID> <Channel>Application</Channel> <Computer></Computer> <Security /> </System> <EventData> <Data>mbamtray.exe</Data> <Data></Data> <Data>5c070ada</Data> <Data>Qt5Core.dll</Data> <Data></Data> <Data>5bd23201</Data> <Data>c0000005</Data> <Data>0018dc19</Data> <Data>1908</Data> <Data>01d49d8ceee8ae0c</Data> <Data>C:\Program Files\Malwarebytes\Anti-Malware\mbamtray.exe</Data> <Data>C:\Program Files\Malwarebytes\Anti-Malware\Qt5Core.dll</Data> <Data>d2c51ac5-df18-4bd4-b995-eee6cf4d0a64</Data> <Data> </Data> <Data> </Data> </EventData> </Event>
  3. While I was asleep, MBAM started having high RAM usage, and began crashing other programs on my computer. Attached are the logs as per MBAM reporting. mb-check-results.zip
  4. I'm wondering if there's any chance that your "latest and greatest" V3.x program will work any better with my XP Pro? I don't want to install it and have it completely lock up my system, like it did a couple of months ago. I would appreciate an honest answer to this. Nathaniel, still hoping your program will get along with my legacy system.....
  5. Hello My malwarebytes Anti-Malware Home (free) - which was freshly installed today - crashes pretty soon into any scan. In fact it won't even let me update the databases without crashing. I am using BitDefender Total Security 2016 and Windows 10. I have another PC (a laptop this time) that has the same stuff installed and it runs fine. I don't know how to suspend BitDefender on a temporary basis. Any suggestions? With thanks J
  6. Hello, Today I faced a problem that I have never experienced before. First the web browers that I usually use (google chrome) started crashing whenever I was trying to download a file. I found that a little strange so I restarted my computer, and suddenly Skype started giving me an error while trying to load (It is set as a startup program). I tried the second browser that I have installed (Mozilla Firefox) and I experienced the same issue, crashing whenever I try to download something (example Malwarebytes Anti-malware). I have an old version of the program installed on my PC (ver And whenever I try to start it I am getting a message "Malwarebytes Anti-Malware has stopped working". I also tried the option "Run as Administrator" and then I got "external exception C000001D". It is funny that I also have MCShield installed which suddenly also stopped working along with Northen Power Eraser refusing to start. The antivirus program that I currenly have on my PC is ESET NOD 32 Trial version. (At least it is still working). I am almost sure that it is somesort of virus but I cant identify it. I would be happy to hear your professional oppinion what may be causing browsers to crash and preventing anti-malware and anti-viruses programs from starting
  7. Greetings, I've been experiencing some quite weird issues of late, where my computer suddenly just turns to a black screen, and then promptly reboots itself instantly only to require a hard shutdown before actually launching properly again. I'm suspecting it might be something related to drivers with the black screens of death, but I have zero idea about why the boot times take ages. Looking in the event log, there's stuff such as this; EventData BootTsVersion 2 BootStartTime 2015-03-26T18:15:41.624800200Z BootEndTime 2015-03-26T18:15:41.624800200Z SystemBootInstance 952 UserBootInstance 897 BootTime 200883 MainPathBootTime 148608 BootKernelInitTime 19 BootDriverInitTime 7311 BootDevicesInitTime 8885 BootPrefetchInitTime 0 BootPrefetchBytes 0 BootAutoChkTime 0 BootSmssInitTime 17151 BootCriticalServicesInitTime 8655 BootUserProfileProcessingTime 2743 BootMachineProfileProcessingTime 67 BootExplorerInitTime 85372 BootNumStartupApps 3 BootPostBootTime 52275 BootIsRebootAfterInstall false BootRootCauseStepImprovementBits 4 BootRootCauseGradualImprovementBits 0 BootRootCauseStepDegradationBits 0 BootRootCauseGradualDegradationBits 2097152 BootIsDegradation false BootIsStepDegradation false BootIsGradualDegradation false BootImprovementDelta 0 BootDegradationDelta 0 BootIsRootCauseIdentified true OSLoaderDuration 19073 BootPNPInitStartTimeMS 19 BootPNPInitDuration 12778 OtherKernelInitDuration 1206 SystemPNPInitStartTimeMS 13729 SystemPNPInitDuration 3419 SessionInitStartTimeMS 17404 Session0InitDuration 6985 Session1InitDuration 389 SessionInitOtherDuration 9776 WinLogonStartTimeMS 34556 OtherLogonInitActivityDuration 25868 UserLogonWaitDuration 18124 I'm not really an expert on this, but a boot time of 200,000 sounds really bad, and it really does take a very long time to boot. This thing also shows up as "Critical" in the event log, as does every single boot for a very long time back. Is there any way to fix this? Because I'm really not able to replace things if it happens to be something hardware related, so I'm going to ask for your professional help with seeing if it's drivers before anything. It should not be overheating, as my CPU clocks in around 50C, and my GPU around 65C at their peaks. I am not overclocking, nor have I ever done so in the past. Reason I haven't is because I don't want to risk burning my hardware for a few extra pixels. I hope to hear from you soon, -Mike
  8. Hello, We're seeing an issue with our terminal server crashing using Malwarebyte's managed client version and specifically MBAM version1.75.0.1300 Prior to the whole server freezing up we're seeing the following event: Application Error 1000 Faulting application name: mbamservice.exe, version:, time stamp: 0x512fc163 Faulting module name: mbamservice.exe, version:, time stamp: 0x512fc163 Exception code: 0x40000015 Fault offset: 0x0006248b Faulting process id: 0x6b4 Faulting application start time: 0x01d000e18a549eec Faulting application path: C:\Program Files (x86)\Malwarebytes' Anti-Malware\mbamservice.exe Faulting module path: C:\Program Files (x86)\Malwarebytes' Anti-Malware\mbamservice.exe Report Id: 0e223f85-6e6a-11e4-b3e2-005056800000 Has anyone seen this issue? Where at the client logs stored for MEE?
  9. I've been using MBAM for a while now, and have only had problems with the program since this summer. However, those problems were fixed, but not they have come back again. I am using MBAM v2014.11.02.06 at the moment. Already, I have done several clean re-installations and downloaded it again, only to find out that I am still having the same problem in that when I load up my MBAM: (see picture 1) Whenever I try to click on any button (scan, settings, history, Scan Now), the program acts as if I had not done anything and does not respond at all. It is as if I didn't even click anything. Eventually, it crashes. Sometimes I am able to click the "Settings" or "History" but when I try to click "Scan Now" it freezes on me again, and it's frustrating. My computer is having some problems and I've always been a loyal supporter of MBAM, but this is getting kind of ridiculous now. Please help, I am desperate.
  10. I have tried to install MBAM on my Windows 7 professional 64-bit for weeks but I keep getting this error after installing then starting the program. Every time I uninstall the program I go back & run MBAM cleaning tool then reboot. But still have the same problem with a fresh install. Even turned off my antivirus in case there was a conflict. Love the MBAM software but it's driving me crazy after this last update. HELP PLEASE!!!!
  11. Hello. I am messaging because of recurring problems with PUP bug files causing my computer to freeze or crash. Initially, I bought the Premium version of MBAM to resolve this. However, this fix has only been temporary. I am now finding that, when I can get my machine to stay on and functional long enough, that when I launch MBAM, I am told that the registry and other information is gone, and that I no longer have the latest daily downloaded version, or any prior one, present in my system. I have to then re-enter my product ID and Key numbers to re-enable protection. The same two PUP bug files are repeatedly being found, when I am finally able to complete a Malware scan without my system crashing. They are both of the Vendor "Optional.Spi..." {Not able to view the full Vendor name}, and both of their Item descriptions start with "C:\Users\Tim\..." From that point in the Item names, the first continues "Downloads\FreePDFTabletInstall.exe" and the second one continues "AppData\Local\Temp\Offercast2802_IJBM..." {unable to see the rest of the Item name}. Could someone please look into this? I am worried I may have an issue that has the capacity to work around the protection of even the Premium, paid version of MBAM software. Thank you very much.
  12. Hi there moderators. This is a followup from a post from a while back with a similar topic title. I had posted info about new incompatibility with Eset NOD 32. I'd like to continue exploring this as it is unresolved and the plot only thickened with a new recent discovery! Here is the original post: [snip] Hello. I haven't seen anyone post about NOD32 Antivirus 4.x. I install the free version on most of my customer's machines. Win7/Vista = no problems. WinXP SP3 = same hard crashing as mentioned above by many. I am one person, but am a tech and have installed MB & on dozens of machines in the past month or three and I am getting SLAMMED with calls about computer freezes from my customers with XP. When first came out and started crashing machines, I did indeed use the MBAM_cleaner to perform a clean uninstall. Upon reinstallation it seemed to work for a bit, but alas, came out and auto downloaded and all the machines starting crashing again upon reboot. (Quietly in the back of my head, I thought, they didn't fix all of it yet... I hope someone tells them about the newly created incompatibility with NOD32!) The IMPORTANT part of my story is that this is even happening with NEW WINDOWS BUILDS, meaning, I have: tested the hard drive for bad sectors, wiped the hard drive, reinstalled windows, patched windows fully, disabled windows firewall, installed MB, then NOD32 Antivirus 4.x and then CRASH! No need to use the cleaner as this is a brand new build. I am one person, but have experienced this hard crashing described in this thread on dozens of XP SP3 machines most of them being new builds with the commonality of NOD32 Antivirus 4.x and MB, and in the case of old builds, the problem persists after using the clean uninstall utility and reinstalling from scratch. As soon as you enable the protection module... BLAM! Within a few seconds, it's cyber bedlam. You cannot stop NOD32 from running its startup scan. My temp fix is to disable the protection module so I have control of the machine long enough to uninstall MB. Even with the protection module off, the MBAM.exe process still runs and crashes the machine at startup, so I have to uninstall the program entirely and wait for the next version which will hopefully have a fix. Hopefully with the info contained in this post, you wonderful folks at MB will be able to contact "Eset", the makers of NOD32, and have a chit chat... I have touted MB for years as being a rare and wonderfully harmonious program that just seems to work well with others. My winning combination of protection was NOD32 2.x and then 4.x, MB and SuperAntiSpyware. I could run all three program scans at once with NO problems as they all scan in different ways and don't step on each other’s toes. But with the advent of MB version, something went awry. Please, please, please know that has NOT solved all the issues! Thanks, Jayneg [end snip] I have to make some clarifications/additions to that 1st post: 1. This only affects paid for /trial versions of MB. The free version is fine due to MBAM service not running... 2. I may have been hallucinating, but I swear I BRIEFLY saw a version It may have only been out there for an hour or a day, and that's what I thought was the latest version when I 1st wrote the post a while back. In the end, it doesn't matter. The problem began in the version just before ( and persists in the current version! Plus I made a new discovery which I will detail in a bit 4. One of the admin’s replies to this first post: "I would love to test this out for you Jayneg but I'm not aware of any "free" version from ESET. They do offer a 30 free trial but it's certainly not a free version that I'm aware of. If you can provide more details on that I will investigate this error you're speaking of." *To clarify, when I am preparing a machine, I install the trial (which is a full version, but with a 30 day countdown timer). After this trial period is up, many customers go on to purchase the full program... But it did not matter if it was the trial or the paid version, the problem was occurring regardless. I realize I used the word "free" instead of "trial" in the original post. Sorry for the confusion. 3. After posting this, I started migrating folks over to the latest release of NOD 32 5.x to satisfy the MB admin's request and POOF! Same problem with the ADDITION of a new problem: 4. In NOD 5.x, there is a new feature that watches for and scans removable media when 1st inserted. Well, if MBAM.exe is running in Win XP SP3, your machine quickly grinds to a HALT whenever an external hard drive or USB key is inserted. The only solution: hard kill! I will give the link to the thread AND cut & paste from the forum I found this info on: http://www.wildersse...ad.php?t=309335 [snip from page 7, post #155] March 5th, 2012, 06:58 AM rcdailey Regular Poster Join Date: Dec 2009 Posts: 141 Re: NOD 32 & freezes when USB HD is connected Quote: Originally Posted by Marcos Oswald2 resolved the issue by installing the hotfix already provided to those who requested it here before. I believe that I have isolated and resolved the issue I was having with NOD32 v The conflict that I found and eliminated was with MalwareBytes. I have the paid version of that software and I found that even with real-time protection disabled in MalwareBytes, the MBAM service would still load with Windows. This service was what prevented ESET NOD32 from checking when a drive was initially connected to the system while up and running. When this happened, the system would lock up. By either disabling the MBAM service or setting it to "manual," the conflict went away and the popup to select the action to take with respect to the USB drive would display and the appropriate option could be selected. In any case, with my system running XP SP3, this is what I found and how I decided to handle it. I also have SuperAntiSpyware ver 5.0.1144 installed and running in real-time and it does not conflict with NOD32 ver It is a little disappointing to have to disable MalwareBytes, but I can live with it. I can now connect a USB hard drive while the system is running and it won't lock up. I can remove a USB hard drive while the system is running and it won't lock up. If anyone else using XP SP3 is running MalwareBytes in real-time and is having issues with ESET NOD32 v 5.x, try disabling the MBAM service and see whether that solves the problem. Adding to this, MalwareBytes will run a scan and can be updated manually without the MBAM Service enabled. I have checked that just now and can confirm that. Also, if the MBAM Service is set to "manual" it does not load when MalwareBytes is run. For most people who like to use MalwareBytes, that should be enough and there won't be a conflict with ESET NOD32 ver 5.x. One more note: If you do have the paid version of MalwareBytes and you decide to re-enable protection, then the MBAM Service will be reset to "automatic" and it will load with Windows, so keep that in mind. Last edited by rcdailey : March 5th, 2012 at 07:31 AM. [end snip] My only comment on rcdailey's post is that when you change the MBAM service to manual start in "services", MB starts spitting out periodic error messages about not being able to perform expected tasks. So, to me, this is not an option when preparing a customer's machine. They won't understand/want to see any error messages on a clean built/fixed machine. So AGIAN, my only option is to uninstall MB! Boo! I'd like to also add that I vouch for rcdailey's post. I tested it out. NOD32 + MBAM service running + plug in USB HD/USB key = disaster (hard kill only way to shut machine off) As soon as I turn MBAM service off, all systems nominal! I think MBAM service and NOD removable media watch service (not sure which process it is) are fighting! In closing, I assert that this is happening on ALL the XP machines I'm working on (over 100 by now) and there are no infections and that the systems are fully patched and all hardware is tested good. Final clarification: The problem where the XP machine would just lock/freeze at startup just outright without doing anything else seems to have gone away, although NOT with the release of the latest version. Did you guys sneak in a mini-patch on one of the definition updates? XP seems to get through the startup sequence now without crashing on its own, but only as of about a few weeks ago?!? (mystery) So I thought to myself YEAY! They fixed it in an unadvertised, non-version number changing mini-patch! I began installing it again on all my customer machines and then got hit with the External HD problem! ARGH! One last observation: There is even new quirky behavior in a few Win7 machines with NOD 5.x and MB newest ver. Again, it usually happens right at startup when I sometimes try to terminate mbam service from taking over 100% processor, so i can quickly bring up a video or program, the machine will lock up just like with XP. It feels different and of course it is being brought on by my terminating a running service, but the combo of Eset and MB both eating up startup juice for the first two minutes is sometimes too much to bear. & windows shouldn't totally hose itself from terminating a "non-critical" process. This is just a side note; something to think about in the future... The MAIN problem is XP as outlined above. What other info do you need from me to help you resolve this? NOD & MB used to work harmoniously together. Now between the latest few releases from both companies, this has changed... Please get on the "phone" with Eset and do some testing collaboratively. THANKS- Jayneg
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.