Jump to content


  • Posts

  • Joined

  • Last visited

Everything posted by Dave_H

  1. I can't figure out how to edit my post. I see that 527 has been already released today. Excellent news, thank you everyone for your hard work.
  2. To follow up, I have over 4 days uptime now without a single problem. My system would have defiantly locked up by now with the previous build. I was getting lockups approx once every 24 hours and never was able to go more than a day and a half. I recommend anyone using Windows 7 who had to turn off any of the features to update to this build. Dave
  3. I have been running component package 527 for over 48 hours now with no issues or freezes. This is on a windows 7 64bit system that I first posted about here: This system would lockup approx once every 24 hours, almost always when the system was idle and not in use. I do however have some network cameras attached so even while idle it was using network traffic. One time it locked up while I resetting my router, other than that I was never able to reproduce the cause of the issue, it would just randomly lockup at least once every 24 hours. Since installing 1.0.527 I have not had a freeze and I have been unable to cause a freeze or break anything. I have spent considerable time trying to cause a freeze by resetting my router, using assorted cable speed tests online with different browsers, going into Devices and Printers in the control panel, and other assorted things reported on other topics from users with windows 7 freezes. I also saw a MB expert or employee report the issue as being related to Win 7 multiprocessors and I have tried my best to overstress the cores with burn-in tools for my 4 cores with and without hyperthreading enabled. Normally I would have had at least 2 maybe 3 lockups by now but everything has so far been working just fine. I'll report again in a couple days or if I encounter a lockup. Dave
  4. I keep thinking about all the people who are experiencing lockups that have no idea what is causing the problem. Most people may not be experianced enough to figure out it's malwarebytes. Even I thought it was a hardware problem and wasted several days in that direction. You really should consider rolling back systems to the previous component package, send out the previous one as a live update. If your able to send out the "update" to only windows 7 systems, all the better. If you have to send it out to everyone than do it, if it was good enough a couple months ago it's good enough until you get this all figured out. You need to think hard about the benefits of the 508 component package verses the negative impact of an unknown number of windows 7 users. Thats just my honest opinion, Dave
  5. My system also has the Intel(R) 82579V Gigabit Network Connection. ASUS P8Z77-V PRO, Intel CPU, Intel chipset. But I can't disable the NIC, my accounting program uses the MAC as one of the hardware identifiers for activation. I'm still closing out last year and can't go without it. Dave
  6. Post #19 on the first page of this topic has a link to a 3'rd party site you can download a previous version from. Dave
  7. I never installed the December windows update, in fact I'm a few months behind. Also, this system is not a Dell, it's self built with a ASUS P8Z77-V PRO motherboard. Since turning off Everything in Malwarebytes I have now gone 8 days without it freezing with the system being on 24/7 since. Before it was freezing up about once a day and it never went more than a day and a half without locking up. Oddly, most of the time (more then 8 out of 10) it would freeze up overnight or early morning without the system being used. It was random times and did not correspond to any of my scheduled tasks or daily images. I do however have 3 security cameras attached and although they are not set to record overnight they are set for motion detection. I also remember one time it locked up when I was resetting my modem and router because of ISP problems. Now that you mention it, at home the other day my Wife said she had "funny network problems" where she could not get a wifi connection to our router. At home we have 2 windows 7 systems networked together (not home grouped, networked). The desktop has never frozen but I realized it's because I had the "update new component" feature turned off so it's not using 1.0.508 update. That desktop is also almost identical to my office system, I did that on purpose to have a complete backup system in case of problems. That may explain why I was so upset this system was having problems, I need this system working properly. Dave
  8. I have been experiencing the same lockup problem for weeks. Windows 7 /64 and did not install the December windows updates. I spent hours and hours trying to figure out the problem I thought for sure it was hardware related and wasted my time cleaning the fans, updating my video drivers, testing and even changing my RAM, using temp and voltage monitors, etc, etc. 3 days ago I thought it might be Malwarebytes because I tried everything else and (no offense) the last major problems I have had was due to your program. (The malformed update last January, the VSS conflict, High CPU usage) So anyway, I came to the forum a few days ago and saw the problem and I have now gone 3 days without a lockup. Longer than I have gone since about 3 weeks ago. ( I turned off everything). I think you are doing a disservice to your customers by not doing anything about it. I think it's a lot more than 1% and I feel bad about all the people who may not have figured out it's Malwarebytes causing it. I think you should at least send out a email to all your customers or push out an "update" that rolls everyone back to a previous component update. I only lost hours of my time, I almost wasted money getting another power supply, video card, or RAM. There is no shame in having a problem only in not being upfront with your customers. Hope you can deal with this quickly. I must have done over 15 hard resets over the last few weeks and it really bothered me to do so on such an otherwise stable and important computer. Regards, Dave
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.