Jump to content

Antec

Members
  • Content Count

    104
  • Joined

  • Last visited

About Antec

  • Rank
    Advanced Member

Profile Information

  • Location
    France

Recent Profile Visitors

1,625 profile views
  1. Hello, @Shelle3 ^^^^ C'est Tuto pour toi, essaye de faire pareil avec ton PC
  2. Hello, Yes but that's it, even on consumer PCs / home PCs ... the problem sometimes occurs. It happened to me on a Dell Latitude E5500 It is true that it is a PC with possibility of doc station, which could be actually in business environment. The OS used is W10 Enterprise LTSC ... (It's an OS that I use more and more, seeing the worries with other W10 editions that change every six months) Resolved Mbarw problem by doing a ghost with the OS of another PC (Dell Vostro 3550) with identical W10. Just the drivers to update. Functional Mbarw
  3. Hello, yes, it has become more rare, but unfortunately it still does ... Best regards
  4. Hello, Well the scan remains on the memory analysis ... as in the photo ... I stopped the scan (at 17s) just for shooting. The attached logs are with the scan for 9mn (on the memory scan) ... so I stopped it and restarted and it happened normally. the cpu is an i7 5820K on X99-Deluxe with 32GB of memory ... It's with the automatic threat scan when the PC starts ... Normally the scan lasts 1mn30 on this machine. It's very fast... The phenomenon is however very occasional ... but occurs on any of my PCs ... (under W10) ... That's already, at least three versions of Mbam3 that I found that ... and as in other topics you have already dealt with problems related to the use of memory ... I had already reported this problem, but you have deleted my posts ... I reported a 45-minute scan loop when I saw it ... and the Kingston PC SSD burned some time later. (HP 2540P-i7 L640 Ram 8GB) But I do not think I'm the only one where this happens ... Greetings
  5. Hello, That's what I had already explained on a PC or the scan had looped ... for three quarters of an hour, before I noticed it ... The phenomenon was reproduced on another PC ... under W10 Pro, last version of Mbam ... I stopped the scan which looped at 9mn Here are the logs Thank you mbst-grab-results.zip
  6. Hell to drop for the SSD ... it's a consequence, and not a repetition. At the limit of my fault ... you must always have your eyes everywhere But the blocking problem on the memory scan is repetitive. But not systematic. And whatever the PC. Latest version also 3.5.1.2522 - 1.0.374 - 1.0.5366 at the moment ... Analysis on Ram still running at 6.30mn. Stop and restart, the complete scan (Threats) lasted 6mn ... analysis on Ram, 2mn ... On other PCs, it's only a few seconds (except when it blocks lol) I do not think I'm alone with this problem, especially since it's been around since well before version 2522 Sorry, hardly any time to make logs right now ... and you know what's going on Good luck
  7. Hello, Where we are ? I do not know exactly with which versions 3.5.1. xxxx, but about the date of your posts ... I burned the SSD Kingston of a PC (the personal one that I take to work) ... during the personalized scan, he got stuck on the analysis of memory ... Hard Disk Sentinel alerted me, the temperature went up to 62 ° ... I stopped the scan ... but too late the SSD had suffered too much, it melted some time later .. (Arf, I was at work, and not watching the PC ... but the job) And it still happens from time to time, that the scan block on the analysis of the memory ... (now I pay attention during the scans ...!) Also, where are you? FJ
×
×
  • 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.