Jump to content

CommonCurt

Honorary Members
  • Content Count

    36
  • Joined

  • Last visited

Community Reputation

0 Neutral

About CommonCurt

  • Rank
    New Member

Recent Profile Visitors

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

  1. I have tried, both of those things. I'll probably try them one more time just in case. I'm all for trying that clean up maintenance script to see if it helps. Please go ahead and send it to me.
  2. Like I mentioned in my first post. I did that before starting this thread. After it re-installed it seemed fixed for 2 days then the problem started again. Are you saying that you want me to do it again?
  3. Thanks. After trying the first command it said: cannot run disk in use, would you like to run on next restart Y/N. When I typed in Y and pressed enter it said not a valid command. I then restarted the computer, and ran sfc /scannow, and it says: Did not find any integrity violations.
  4. I'm not sure. All I know is that I had no problems until after I updated malwarebytes.
  5. Thank you :) It's not that I don't wan't your help. I'll take any help I can get to fix this issue. I tried what you recommended the first time, and then replied that it didn't fix my problem.
  6. Anyone who works for Malwarebytes got any ideas that can help me?
  7. Yeah, it's always connected. I uninstalled GlassWire, but it did not help.
  8. Hi, I have a life time license. When I try to open Malwarebytes it tells me "Unable to contact license server". I have ran the support tool and tried the "clean" option. I uninstalled then re-installed Malwarebytes. It seemed like it fixed my problem, but then two days later I'm getting the "Unable to contact server" again. Please help. mbst-grab-results.zip
  9. Hey, Not sure if you saw my last post above due to the holidays, but I managed to find the first BSOD (when all this started), and it looks like the very first one might say something a little different.
  10. I haven't tried doing a clean boot on either system because of how long it takes for the BSODs to show up (this system around 5 days, and on the other system 7-10 days). It never happens right after a restart. After I try uninstalling somethings if that doesn't flush out what's causing it I might consider trying clean boot, but it would take a long time with how long in between the BSODs are. I also will look into the other forum that you mentioned. Then, as a last resort, I might go back and start installing the Monthly roll up Updates starting with the Month when my problem start
  11. Yeah, when I get some time in the next day or two I will uninstall it and see what happens.
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.