It turns out, I already had been getting Event ID: 86 CertificateServicesClient-CertEnroll errors long back before I started experiencing DPC_WATCHDOG_VIOLATION BSOD. (other AMD users I know were also getting this error in Event Viewer, but they don't experience crashing). Hence, why disabling the task in Task Scheduler, replacing it with someone else's copy, and even deleting the task (I restored the task back via system restore) does not prevent the error.
This BSOD occurs even when using Safe mode with Networking.
So far what I did was use Display Driver Uninstaller (DDU) and uninstall the AMD graphics driver. After restarting the computer, I noticed the wifi driver was back. After waiting for a couple of hours longer than when the BSOD would occur, the error did not occur so far. I decided to install the AMD graphics driver from Asus specific for my laptop, the version older than the most recent one because I still got the error with the latest version after the recent windows update.
Before I installed the AMD Graphic driver, I renamed the old folder destination. During the installation of this driver, the Wifi driver was removed. I did a network reset and after a while, I got an internet connection. I waited for several hours to see if it would crash again. I am still getting the Event ID: 86 CertificateServicesClient-CertEnroll error though but so far it has not crashed yet.
*Edit:
After plugging the charger into the laptop, the Wifi driver was removed, and a DPC_WATCHDOG_VIOLATION BSOD occurred. Checking the Event Viewer, there was the Event 86 error when the BSOD occurred.
Performing a network reset did not remove the hidden Wifi driver so I manually uninstalled the Wifi driver and reinstall the latest Wifi driver from Asus. However, the driver was unable to connect to the internet, and eventually, the driver was removed again. This time I installed the Wifi driver that is closer to the release date of the AMD graphics driver I installed, however, the same thing happened. Performing "netsh winsock reset", "netsh int ip reset", and "ipconfig /flushdns" didn't help.
I turned the laptop off and waited for a couple of hours and turned it on again. The Wifi driver was back and there was an internet connection. I waited again for a while to see if the BSOD would occur again but so far it has not crashed yet.
I noticed in notifications that Microsoft Visual C++ 2012, 2013, and 2015 UWP Desktop Runtime Package and DirectX Runtime are starting but they won't finish. I am not sure if this is a symptom because they usually would finish in a few seconds. So I ignored them and closed their notification.
