Jump to content


  • Content Count

  • Joined

  • Last visited

Community Reputation

0 Neutral

About chuckstanley

  • Rank
    New Member

Recent Profile Visitors

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

  1. In this particular case, I had several browsers open with multiple windows open in each browser. I was not at the computer when the BSOD occurred. In the past, the BSOD occurred while I was accessing websites. I will remove Kaspersky and BitDefender and let you know. thank you.
  2. Here's the link... https://www.transfernow.net/29ajf9g9ym3u thanks for the help!
  3. Hi Nikhil - Can you please explain what is the "latest release build". I'm still experiencing BSODs and cannot run with Real Time Protection Enabled. I tried 804 and got a BSOD almost immediately. I checked for updates and it went to 810, which is the crash I posted last Tuesday. Today, I checked for updates again and am now running 1.0.18836 1.0.810 Still getting the BSOD. Crash info attached. thanks! WhoCrashed.docx mbst-grab-results.zip
  4. I waited until the Beta went live to turn Real-Time Protection back on. Immediately BSOD. I turned off Real-Time Protection. 1.0.18710 1.0.810 thanks for your help! mbst-grab-results.zip SysnativeFileCollectionApp.zip
  5. I have suddenly been plagued with BSODs. Using WhoCrashed, I see that most are caused by mwac.sys (mwac_0xD592) BAD_POOL_CALLER. I looked up mwac.sys in the Windows driver folder and see that it was updated last week about the time the BSOD started happening. I used the Malware Support Tool to completely remove and then re-install Malwarebytes. No change. I also tried the "repair" the installation option, but that didn't help either. I had to completely remove Malwarebytes because the BSODs would not stop. Thanks for your help! mbst-grab-results.zip SysnativeFileCollectionApp.zip
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.