Jump to content

JoelS

Honorary Members
  • Content Count

    28
  • Joined

  • Last visited

Community Reputation

0 Neutral

About JoelS

  • Rank
    New Member

Recent Profile Visitors

The recent visitors block is disabled and is not being shown to other users.

  1. Yesterday, I got a bunch of Riskware, Generic Injector detections which I understand are false positives, so I removed them from quarantine. However, today, this popped up on the report: Malware.AI.1338826517, C:\WINDOWS\INSTALLER\1ED5E.MSI, Quarantined, 1000000, 0, 1.0.40732, 1B63E81907980D144FCCDF15, dds, 01254988, 1CDE2A414CB4C7457788153E5EE4836E, EBAF35D74AD6CEB3C44CBEA81C207C9A7BB123E6D641E09678D12C9DE2770DC4 I have it in quarantine. Is it a real detection?
  2. I had blue screen crashes starting three months ago, right after the Creators update of Windows. Forum assistance made all sorts of recommendations, most of which I tried and which did not work. I took it into the shop and paid a fair piece of change to diagnose. As their first step, they uninstalled MBytes and never saw a repetition of the problem. On returning it home, I re-installed MB. Within a day I had a black screen crash (computer becomes unresponsive). On re-starting, Malwarebytes failed to boot properly (several times) and finally locked up. It kept complaining about not being able
  3. Assorted BSODs: 10/20: Kernel Security Check Failure 12/12 Clock Watchdog Timeout 12/15 System Service Exception 12/15 Critical Structure Corruption 12/19 Clock Watchdog Timeout PerfmonRpt-12-15-17.7z SysnativeFileCollectionApp.zip
  4. When trying to follow the link in the thread, I get the reply Blue Screen of Death (BSOD) Posting Instructions - Windows 10, 8.1, 8, 7 & Vista Sorry, there is a problem The page you requested does not exist Error code: 2S100/6 Could you please update the link? Thank you!
  5. I followed your instructions and successfully ran PerfMon and Sysnative. When I got to the link for posting results from these, I get a message that the page does not exist. What PerfMon said was that a service had stopped ungracefully, resulting in a third of events not being logged in the event log.
  6. Ron, I have been very hesitant to rely on just Defender. So--forgive me-- I haven't done as suggested, hoping that somehow I could solve the problem in another way. I also did not have blue screen crashes from Dec. 7th until Dec. 13th. So, even if I had turned off everything except Defender, we would have gotten a false sense that the problem had been solved. Last night I had a BSOD listing Clock_watchdog Timeout as the cause. Following instructions on the WIndows Forum, I ran Driver Verifier. This turned up as a Driver Verifier Error MBAM Chameleon.sys. Could this
  7. This does not seem very safe. But I will see what I can do.
  8. Ron, I tried the Components Update on Computer #1. I had two blue screen crashes thereafter. After the second, Malwarebytes and my antivirus suite did not come up. I had to restart again. Could this represent a conflict? I have Malwarebytes on a brief delay, since I have had some problems there before. I have not yet observed another crash of MBytes after startup, however. I scanned again using Sophos. This time, aside from tracking cookies, the only thing it came up with as suspicious was Farbar (FRST64.exe). Just to be thorough, I ran AdwCleaner. Nothing.
  9. Farbar logs for computer#2. Addition.txt FRST.txt
  10. AdwCleaner log from second computer attached AdwCleaner[C0].txt
  11. MBytes log from second computer (also suffering unexplained stoppages of Web Protection) attached. MBytes report#2-11-30-17.txt
  12. Finally, I should note that the same problem (Malwarebytes crashing) has now occurred on a second computer. When I am able, I will go through this sequence with that computer. Perhaps we will find something there.
  13. I have not previously done the Farbar, so thanks for this. Here are the requested files. Addition.txt FRST.txt
  14. Also, as mentioned above, I had run AdwCleaner. Nothing was found. But I repeated it. This is attached. AdwCleaner[C0].txt
  15. Please don't dismiss this as traces of an old piece of malware. There is a real problem with MalwareBytes crashing. The version is current and the machine is scanned daily, and the settings should detect PUPs. The most recent report is attached. MalwareBytes Report-11-30-17.txt
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.