BSOD Since Win10 1809 update, 0x133(1) DPC Watchdog Violation

The memory dump was corrupt.
ckcl?

Ckcl = circular kernel context logger.

There still doesn't seem to be any symbol information so we can't see what's actually being called. Can you check to see if the setting I mentioned in reply 22 is set?

It was on, but 1903 must have reset it. It's back on now. Just one question though, I've verified ckcl is running as a trace session, but what trace providers do you recommend setting? Or is it sufficient to leave it on automatic?

The CKCL logger should be watching ISR, DPC, and driver calls which I think is where we need to be looking. I'm trying to figure out how to get the symbol information to be included so they can be resolved and we'll actually be able to see function names in the etl analysis. I think disabling the paging executive might keep such information resident in memory which should make it show up in the etl but I'm not certain of that. I'm hoping we can find out.

Current trace session has process, img, dpc, isr, and hard page faults enabled.

I suspect you'll be interested in this post at Bleeping Computer. OP has your exact same laptop and is having the same problem. badtoad says they talked with someone at Toshiba who says they know about the problem, that it started with 1809, and they are trying to find a solution.

If the setting to disable the paging executive is sticking and you get another memory.dmp please make it available so I can check to see if symbol information shows up in the etl file from the dump.

All those who own a Toshiba laptop and have BSoDs 0x133 through the fault of ACPI.sys, let them install this latest ACPI Toshiba driver:
tch0533200e.exe - Google Drive
Let me know if the problem has been resolved

cwsink said:

If the setting to disable the paging executive is sticking and you get another memory.dmp please make it available so I can check to see if symbol information shows up in the etl file from the dump.

OK will do. I did have a couple of etl that i extracted recently, followed the instructions I found in the ms blogs, opened them in WPA, but when I expanded the offending address (the longest dpc times), all the entries were blank.