Jump to content


Honorary Members
  • Content Count

  • Joined

  • Last visited

Everything posted by CommonCurt

  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.
  12. Just found another BSOD when I woke up today. WhoCrashed is again saying that it's iaStorA+877b8. 120517-19952-01.zip
  13. I'll definitely try uninstalling some things, but the whole reason I created this thread was to avoid having to do Windows7 re-installs.
  14. Okay, had another BSOD with Driver Verifier turned on again. Ugg, you listed 3 of the programs i'd really prefer not to have to get rid of. 112717-21512-01.zip
  15. Sorry it has taken me so long to reply. Been dealing with Holiday stuff. Should I keep Malwarebytes Ransomware & Exploit Protection turned off after I turn Driver Verifier back on, or is it okay to turn those back on? Also, I notice in the Event Viewer almost every time right before a BSOD there is an Event ID: 3 "Session "Microsoft Security Client OOBE" stopped due to the following error: 0xC000000D"" Not sure if that helps anything, but I thought i'd mention it. Lastly, in that list you posted above. The second driver "cpuz136_x64.sys". If it belongs to a program
  16. Okay, I uninstalled all MSI programs that I could see. Also, Malwarebytes Ransomware was already turned off. I went ahead and turned off Malwarebytes Exploit Protection just now to see if it might make a difference.
  17. Okay, had another BSOD on this machine today. RealTemp was deleted a few days ago, and I had the Malwarebytes Ransonware turned off. I just turned off Malwarebytes Exploit Protection to see if that is what's causing the problem. 111817-8736-01.zip
  18. Okay, finally had a BSOD on this system when I woke up this morning. It looks like it's saying that it's iaStor.sys again just like the other system. I went ahead and turned off Driver Verifier on this one now, but I didn't get another BSOD like on the other system during the restart. The funny thing is that I had already deleted the RealTemp folder from this system about 2 days ago. Guess I'll start disabling the Malwarebytes live protections now. 111717-13993-01.zip
  19. Still running Driver Verifier on this system as there's still not been a BSOD yet. This system doesn't get them quite as often as my main system. Sometimes it can take more then days for a BSOD to be triggered. I've also deleted the RealTemp folder just like the my other system.
  20. I turned RansomWare protection off before I left the house. When I get home I'll see what else I can turn off. I really don't want to have to uninstall MalwareBytes. I have two lifetime licenses, and I do really like the program. The thing that sucks is that like I said before. BSOD's usually take 3 -5 days. I never get BSOD's when shutting down. or restarting the system. So I'm guessing Driver Verifier is the reason the last one happened when I restarted after turning turning Driver Verifier off?
  21. should I disable MalwareBytes RansomWare protection right away even tho I just deleted RealTemp to see if stops the iaStorA.sys BSOD's? Could farflt.sys have been responsible for making the iaStorA.sys BSOD's also?
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.