Jump to content

Breach

Members
  • Posts

    33
  • Joined

  • Last visited

Everything posted by Breach

  1. Just to chip in here. 1920x1080 , 125% DPI (default for laptops I think). By default the window doesn't fully extend, and unfortunately windows position is not persisted. Not a biggie, but still mildly annoying:
  2. @nikhils Hi, any update on this? It's getting pretty annoying, not to mention that my RAID array takes 6 hours to resync after a BSOD...
  3. Hi nikhils, Just to say that I usually, but not always, get the BSOD shortly after Windows startup or during shutdown. Hope this helps.
  4. Same issue (see below). I see you're also running ESET like me, so that seems related. It doesn't happen on my laptop where I don't have ESET.
  5. MalwareBytes updates (not sure whether related).
  6. Just happened again, I think I manually tried checking for updates:
  7. Hey, Installed 3.4.4 on both laptop and desktop yesterday. Laptop is fine, but desktop (windows 10 64, latest) BSOD'ed twice so far with an mwac.sys reference. Anyone else/ideas? Thanks.
  8. That's textbook. The low disk space was because when Windows runs out of memory is starts increasing the virtual memory (swap or paging file). When you rebooted in safe mode Windows automatically downsized the swap file. Provided you follow the recovery instructions (update definitions, restart), you should be good.
  9. Well, not sure this is going to work, but give this a try: 1. WIN Key + R -> type ipconfig /flushdns <ENTER> 2. In Chrome go to: chrome://net-internals/#dns click on Clear host cache If this doesn't work try: Open Malwarebyes, click Current (to check for updates), restart the computer Malwarebytes manipulates the local DNS cache, in case it cannot verify whether a destination URL is malicious for some reason it may lead to issues.
  10. What's the message you're getting? I'm guessing you didn't deactivate your license before reinstalling. If you use the same license in too many installations (I guess even if the hardware is the same) eventually it gets blocked. Contact support, they'll sort it out. Though it may be some time before they reply - I guess they'll be dealing with yesterday's fallout for the next 2 weeks.
  11. Don't see what they can do. Complete power off, power on and deploy before RAM runs out... the damage is done anyway.
  12. 1. Open MalwareBytes 2. Click on Current. 3. Wait to finish. 4. Restart Windows.
  13. Of course it's automated, and it couldn't be any other way. Machines are much less error-prone than humans in running repetitive tasks - but you got to teach them first. Unless you really work with a good QA team which keeps asking "what if" you end up with a limited test suite which isn't ready for the real world. Then it's "improving by tackling reported customers cases". (not that this doesn't always happen).A long time ago, I remember reviewing a recovery test document - it was all fine with respect to stored procedures, monitoring, scripts, etc, but... they didn't check whether... Apache was set for auto-start in init.d.
  14. Ah, you meant it won't *physically* cause hardware damage? Sorry, but if the bar is "it won't destroy my DRAM sticks" then I guess we have some profound differences in terms of expected software quality. By the way, System Restore does NOT protect against user data loss - it can help you with a registry restore, but that's about it. If you want security you need a full backup solution.
  15. I was replying to your original statement which said that it "will not break your PC". You were wrong. Now you've changed the subject. On this matter, yes, that's why both consumers and businesses keep backups, have to save regularly, etc. But this won't help with immediate loss of data which can be critical, especially in time sensitive projects. Consider long-running rendering jobs, compilers, live streams, Diablo III HC characters, etc. (yes, this was a joke). But let's say you recover from backup - still, this won't compensate for the productivity time lost or the frustration. Most people have better ideas of spending half of their Saturday than troubleshooting their computer. Could it happen to any software vendor? Surely. Windows 98 BSOD'ed in front of Bill Gates during a presentation after all. But it's the quality aspect which is one of they key defining aspects which determines software consumers choose. In the business world, product management is much more severe and such incidents have major repercussions in product selection - no one wants a high cost of doing business after all.
  16. 1. The leak was about 32MB/sec. You can do the math on how much time it takes to exhaust physical memory. 2. Once RAM starts decreasing Windows starts swapping to HDD/SDD. At some point swap space runs out. There are other limitations too. 3. Finally processes start crashing due to out of memory (OOM). Critical Windows components crash, Windows typically locks up. Anything not saved or not flushed to disk is lost. Hard reboot is required to recover. Rinse and repeat.
  17. Thanks.for the update and the relatively quick resolution Just a few relevant questions: 1. If each update is tested before it goes out, why did this one slip through undetected? 2. Does the client verify the integrity of the updates before they're applied? 3. Doesn't the client have appropriate error handling for such situations so that they don't result in memory leaks (or CPU load or whatever)?
  18. How about a post-mortem in due course? I'd surely like to know what happened and how this "will never happen again". Thanks.
  19. Hmmm... with a leak at about 32 MB RAM / sec. That's maximum of 250 seconds with 8 GB RAM and 500 seconds for 16, 2000 for 64GB (before swapping to disk starts happening). Then it's a matter of disk space. Also these writes are terrible for SSDs with their limited writes life...
  20. Most EULA clauses, especially with regard to damages, are either outright illegal or challangeable in court. Plenty of case law out there.
  21. Oh, it's alright then. Let's hope the business edition is not affected.
  22. You surely can't be serious. Do you realise there are servers down at the moment with admins scrambling on a Saturday? That people are losing data because of a hard crash/reboot the moment Windows runs out of memory? You're really taking fanboism to the next level. You don't know me, so I don't appreciate the ad hominem remark too.
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.