Hello
In general this stop code is caused by faulty driver code that under certain conditions, does not complete its work within the allotted time frame.
Cast the address of the nt!DPC_WATCHDOG_GLOBAL_TRIAGE_BLOCK to display information about it:
dt nt!DPC_WATCHDOG_GLOBAL_TRIAGE_BLOCK fffff801116fb320
Use the !dpcs command to display the queued DPCs:
!dpcs
Or use some basic troubleshooting techniques:
If a driver is identified in the bug check message, to isolate the issue, disable the driver. Check with the manufacturer for driver updates.
Check the System Log in Event Viewer for additional error messages that might help identify the device or driver that is causing bug check 0x133.
Confirm that any new hardware that is installed is compatible with the installed version of Windows. For example for Windows 10, you can get information about required hardware at Windows 10 Specifications.