Jump to content


  • Content Count

  • Joined

  • Last visited

Everything posted by RTL434

  1. Built a new PC using an ASUS Prime X570 PRO motherboard, AMD Ryzen 5 3600 and a Samsung EVO Plus 970 for the OS. Windows 10 Pro 18363.815. With MWB installed I was getting problems at Power On. It would display the Windows Logo and the "five rotating dots" but then that would disappear. I was left with a blank screen, the Power On LED lit and an occasional burst of the disk activity LED. Had to press Reset and it would then come up Tonight I ran the Support Tool and removed MWB and powered off. Now powers up o.k. Installed MWB 4.1.056 1.0.896 and it automatically picked up my licence from the Desktop. Disabled "Registering with the Security Centre", Enabled Event Log Data, set my Scan Schedule and then ran a scan. AOK. Set for a "Complete Memory Dump" in case it took a dump and restarted to apply the setting. PC came up O.K. Powered down. Powered on and the problem was there--pressed reset and up it came. Only way I can get it to run is by enabling "Delay Real Time Protection to 15 seconds". Is this o.k.? Logs attached. mbst-grab-results.zip EventLogs.zip
  2. @BillH99999 Just a thought. According to Post #20, your wife did a Feature Update. She must have been on 1809 or lower possibly. During a Feature Update she would get the latest level applied as a matter of course.
  3. @LiquidTension Hi, Everything has been fine since. When you used the word verify, I assumed there would be an entry there that needed changing. There were no entries for Malwarebytes---majority seem to be for NVidia. So I have created one for MBAMService.exe as per the attached. Have also added the original Windows Error Reporting data. Hope this is what you wanted me to do. Files.zip
  4. @LiquidTension Hi, here are the Event Logs as requested. The CrashDumps folder is present but it is empty. EventLogs.zip
  5. This PC is set to automatically download Beta program versions. This morning, it installed Component Version 1.0.793. No problem after that other than having to do a reboot---my backups were scheduled to start running very soon! I switched the PC on again about 13:55ish and it seemed to "stick" with just a few icons in the System Tray. The Windows Defender one was there but no MWB. I ended up pressing the Reset button. PC came up this time o.k. Checking in Reliability, it said that MBAMService.exe had a problem at 13:59. Have set MWB to collect Event Log Data and run the Support Tool. Couldn't remember the sequence to force a Memory Dump that was set in this machine from a previous topic but have since checked and verified that it works. So if it happens again, I will force a memory dump. In the meantime here is the Support Tool Log File. mbst-grab-results.zip
  6. The Scan Reports are showing my Windows Info wrongly. They say it is 18362.476. I'm on 18363.476. Installed the Beta 1.0.777 just in case it fixed it. Doesn't--it's still wrong.
  7. Thanks. O.K. now with 1.0.15048.
  8. Have used TreeSizeFree for a while now with no problems. I currently have version installed. Was informed today that there is an update available---4.4. I downloaded it but when I tried to run it, MWB quarantined it. Uninstalled 4.3 and then re-installed it. No problem there. Don't know if this is a false positive or what. Ran the False Positive tool but it didn't find anything to report. Would like an opinion on this. Report attached and downloaded file also in zip format. TreeSize_Trojan_Report.txt TreeSizeFreeSetup.zip
  9. When I "Check for Updates" on my four machines it downloads a new Version 1.0.718. Can't see any info as to what it fixes anywhere in the Forum.
  10. Well said @TempLost. My feelings exactly.
  11. @LiquidTension Hello, Have updated all my PC's to the latest beta Have run the sequence twice as per Post#8 on the two PC's that were getting the C35 errors. They are now clean-- no problems.
  12. @LiquidTension No the error does not seem to be consistent. I powered this PC up at 07:34 this morning and it had the error. Powered up at 11:06 to do as you requested and it didn't show the error. I installed the on all my three desktops and laptop yesterday. Desktop 3 and the laptop are fine. Desktops 1 and 2 show the error. I have run your request twice on both those PC's. C35_errors_test_sequence_report.docx EventLogsDesk1.zip mbst-grab-results-Desk1.zip C35_Errors.zip EventLogsDesk2.zip mbst-grab-results-Desk2.zip
  13. I had seen the new beta release but wasn't sure what release it was and had PM'd Erix for clarification. Then I saw Jekko's response in another post. Am now running on it. BTW if we're going to be pedantic---it should be " 1 zip too much " . ☺️
  14. @LiquidTension, Looks like my component package is now at 1.0.690. Must have updated just lately as it was at 1.0.682 in this morning's scan report.
  15. @LiquidTension, I'm seeing the error as well in that location throkr calls out----and I'm not doing Restores at the time. Currently on Win 10 1903 18362.387 and 4.02.41 1.0682 1.0.13531. Everything seems normal. Have also set Event Log on in MWB. mbst-grab-results.zip EventLogs.zip.zip
  16. No you're not losing your mind. I saw this a couple of times. It was while I was on the Free Version prior to activating my licence. I took it to be a plug for a Free User to upgrade to Premium. Since this is a beta and they might be using a different name when it goes live, they are using Wossname as a placeholder.
  17. Update. On Saturday 14th. Sept. I removed 4.0.1 and reverted to 3.8.3 as I wasn't sure what would happen in the meantime if I received Windows Updates and they got screwed up because of the restart problem. Ran like that until the 20th.---no problems. On Friday the 20th. a new version was shared in private and that fixed the problem. Still running on it and restarted numerous times.
  18. Hi @LiquidTension Thanks for the update, appreciated.
  19. @LiquidTension Hello, I had a problem this morning when I powered up. Forced a Dump. PC came up after it had created the dump file. No problems since and have used the PC for the last three and a half hours. 14th_September.docx mbst-grab-results.zip
  20. @LiquidTension Hello, have done as requested (hopefully) and results are attached. 12th_September.docx mbst-grab-results.zip
  21. @LiquidTension Restored back to normal. Updated Windows and did an "Update & Shutdown" as opposed to a Restart, Came up and now at 18352.356. Set MP ON. Powered off and then on. Came up fine. Did a further two and no problems. Did a Restart and the problem is there. Reset and it came up. Did a further two PD/PU's and they were fine. So it definitely looks like a Restart is what screws it up-----only on 4.0.1! Will do further checks tomorrow as time is getting on. Didn't bother running the tool for the logs as the previous entry logs should have the data.
  22. @LiquidTension I think I hit a wrong key!! Anyway I think I have found what my problem is. Yesterday I tried removing startup items to see if they were the culprit but at one stage I couldn't set MP ON. Could reset the others and set them back on. Could change various options but got an error when I tried to scan. At that stage I took an image after running the logs so that I could return there later. Tonight, I restored back to it. I then did a Clean with the tool and 3.8.3 got loaded. Had to activate my licence but that went o.k. Adjusted my scan schedule time and ran a scan. Then I updated to 4.0.1. and changed the language to U.K. Also set Event Log. Ran a scan. AOK. Then I removed some more Startup items but the problem persisted. Looking at my notes, I noticed that a couple of times after a Power Down the PC came back up o.k. It was only after a restart that it had the problem that needed a reset before it came up. Now 3.8.3 worked fine like that, MWB doesn't seem to like a restart---at least on this machine. I have done a sequence of Pwr/Down then up four times with success. I then did a Restart and it needed a reset to come up. After it came up, I then did a further 3 Pwr/Down then up ---all successful. I'll run the log in case it helps before I restore back to my setup at 18:00. Will attach the logs for Sept. 10th in case you want to see why I couldn't set MP. (Windows has obviously been installing updates while I've been playing with this as it just threw a notification out about a restart which I will ignore.) Fast Startup is currently ON but it was happening with it off as well. Also I knocked off the Delay Real Protection and it worked fine. Right that's me, am going to restore back. mbst-grab-results_10th_Sept.zip Files.zip mbst-grab-results.zip
  23. @LiquidTension Hello,well I tried it several times and it started to come up but then the mouse froze! On one occasion I left it sitting there and suddenly it burst into life. Icons I had clicked on earlier fired up. The time lag was in minutes!! I had set the delay at various settings but was currently at 60 secs. Using my phone, I had started a video when I hit the Enter key. This was at 20:26. I was double-clicking the following icons after the Protection had come on and obviously before the mouse freezing:- CCleaner, Nextbase and Procexp64. You'll see from the video up until the mouse froze. The picture after that was the jobs now fired up. I took another video at 21:40 with the delay at 30 seconds. Came up and eventually the Protection was enabled. I then clicked on the same icons as before, None of them fired up and at 1 min 54 secs. into the video, the freeze occurs. Left it. At approximately 4 mins. 18 secs. into the video it all comes good. Am attaching the logs and will PM you a link to the videos. In the videos, I kept going to the MWB icon and you'll see it going from "Protection Disabled" to Enabled. Once it's up I don't have any problems--so far. mbst-grab-results.zip
  24. @LiquidTension Hello, I tried rolling PC back to the 14th. August and then installed the beta. No good -still fails. Ran the Support Tool for the logs in case they help. Am now restored back to today. mbst-grab-results.zip MWB_Problem_8th_September.zip
  • 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.