I am the OP from above, Gian88. My MB forum was perma-banned from posting (again) due to merely forgetting to close my VPN before posting. This is probably my 10th MB forum account due to this same reason but this is not what I am here to say. I am pasting below my original message about the BSOD:
-------------
This is a production machine and I cannot keep the shield enabled hoping for a BSOD so that I can provide logs (I also formatted windows so I don't have old logs anymore). I would do it happily if the situation was different. Anyway, enough users have posted logs and other files and it looks like I am in the category of those affected by the openVPN incompatibility (not using PIA but using ProtonVPN which is also related to OpenVPN).
It seems Malwarebytes has made itself incompatible with even more software that was just working absolutely fine for a very long time. This is very unfortunate. I now have to keep a shield disabled because you "upgraded" it in an incompatible way, meaning your upgrade effectively changed my web protection to zero since I am now forced to keep it disabled. If impossible to make it compatible I suggest reverting that upgrade back so that at least we can enable the shield again.
By the way, this is the second shield I have to keep disabled (after the ransomware shield since last year). I am running out of shields here, I assume you know what this means.
But if you want to help solve this you could easily test ProtonVPN-related netio.sys BSODs on a test machine with some artificially-initiated web traffic, it is very likely to BSOD within a few hours max.
Can I keep my hopes up that you will test this?
