[German]Short question for users of Windows 10 version 2004 who also use Malwarebytes Pro 4.1.0. Do you facing BlueScreens with the stop code DPC_WATCHDOG_VIOLATION?
Advertising
I don't use it – but blog reader Karl pointed me to a problem on Twitter. According to my interpretation he has Windows 10 Version 2004, but the release preview ring is active.
@Malwarebytes seems like current 4.1.0 pro is again causing issues when all pro featured protections are enabled
2004 release install, with release preview active (driver and apps) here.@windowsinsider anyone else reporting this?@Deskmodder @etguenni
DPC_WATCHDOG_VIOLATION pic.twitter.com/kd0OmTy1Wo— al Qamar (Karl Wester-Ebbinghaus) (@tweet_alqamar) June 16, 2020
As soon as it activates all Malwarebytes Pro features (version 4.1.0), a blue screen with the stop code DPC_WATCHDOG_VIOLATION appears. During a search I only came across older posts from April 2020, like here in the Malwarebytes forum. The post even refers to version 4.1.0.56. This forum post from May 2020 also deals with this stop error. A year ago, a filter driver was mentioned as the cause in this post. Karl also writes that the system is slowing down – probably occurs since Malwarebytes Pro 3.8. Does anyone else have that?
Addendum: On Twitter a user confimed this BSOD – here is the follow up tweet.
Haven't faced BSOD issue here. But the system stalls after login. Web browsers don't open.
Workaround: Turning off the Ransomware protection module helps. MB support has no clue so far.
— Ramesh 🇮🇳 (@rameshs79) June 17, 2020
Advertising
His workaround is disabling the ransomware protection in Malwarebytes Pro.
