Jump to content


  • Content Count

  • Joined

  • Last visited

About JohnSmith1

  • Rank
    New Member

Recent Profile Visitors

The recent visitors block is disabled and is not being shown to other users.

  1. I've just left my office, I'll either do it tonight or tomorrow morning. Best regards, J
  2. Thanks! BTW, adding exclusions as shown in the attached file, does not solve the problem. Best Regards, J
  3. At the time of the BSOD, our project was being navigated for the first time after re-building in Visual Studio and deleting the temporary ASP.NET files (at which point the IIS is starting to generate the temporary files needed). I cannot really test the exclusion right now, if I have the time, I'll try and do it tomorrow. NOTE: this only happens with our largest solution (100+ .csproj projects) and does not happen with several other smaller ones.
  4. ********************************************************************** ** Visual Studio 2017 Developer Command Prompt v15.4.2 ** Copyright (c) 2017 Microsoft Corporation ********************************************************************** C:\Windows\System32>csc /version (f0cdbe92)
  5. We are using Windows 10 Enterprise (64-bit) version 1709 (16299.19). csc.exe is version 4.7.2556.0 Unfortunately, I could get permission to upload any dump file anywhere. I apologize for this.
  6. Hi, We are using MBARW (beta) I'll try to find a full dump and upload it somewhere for you. Best regards, J
  7. Hello, I would like to +1 this issue with the new update. There are ~20 developers in my office and we all use MBARW for sometime now. Yesterday, everyone in my office started getting BSODs at what seemed to be random times (by analyzing the logs in "C:\ProgramData\Malwarebytes\MB3Service\logs", we later realized that it was because we've received the update at different times). We debugged the issue to be a conflict between the Microsoft C# compiler (csc.exe) and the MB3service. NOTE: all of us got a different BSOD messages and since our PCs crashed multiple times before we found the problem, I can confirm that the BSOD message was always random, even when we did multiple tests on the same PC. Best regards, J
  • 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.