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

Hi Guys,
Getting random yet sometimes frequent 0x133 (1) Bugcheck on my laptop since the win10 v1809 update. I had this several months ago, and the only way to fix it was to roll back to v1803, problem solved.
Forward to now, and I recently allowed it to update again, and again the bugcheck is back. Seems youtube aggravates it somewhat, or intensive web pages.
As I say, going back to 1803 everything is fine, it only happens in 1809. I just don't really want to have to keep rolling back. A friend suggested trying 1903, but I'm not sure.

Things I've done so far:
- Disabled fast startup.
- Upgraded graphics driver to intel v5063, made things worse.
- Downgraded graphics driver to the latest offered by Toshiba, v4300. Still happening, but not as often.
- Disabled windows update from updating drivers.

I've had a look at the dump in Windbg preview, and it's not very informative, more often than not it names acpi.sys, which is a bit vague. Also tried bluescreenview, which names hal.dll and igdkmd64.sys as suspicious.
I have included a link below to the most recent Memory dump which I believe has the circular logger information included in it. Perhaps if anyone could be so kind as to have a pick through it?
System specs filled in on profile.

Dropbox - MEMORY2.DMP - Simplify your life

Many thanks

@spark001uk
See posting instructions.

Apologies, forgot to put it in. Done now.

Update:
Toshiba ACPI driver (check in Snappy Driver Download)

1) Open administrative command prompt and type or copy and paste:
2) sfc /scannow
3) dism /online /cleanup-image /restorehealth
4) chkdsk /scan
5) wmic recoveros set autoreboot = false
6) When these have completed > right click on the top bar or title bar of the administrative command prompt box > left click on edit then select all > right click on the top bar again > left click on edit then copy > paste into the thread

7) Make sure that there is no over clocking while troubleshooting.



8) Make a new restore point:
Create System Restore Point in Windows 10

9) Create > 30GB free space on the Windows drive

Code:

      Drive: C:
 Free Space: 26.5 GB
Total Space: 237.0 GB
File System: NTFS
      Model: Samsung SSD 850 EVO 250GB

10) Make a backup image using Macrium:
Macrium Software | Your Image is Everything

11) Save the backup image to another disk drive (do not use another partition on the same drive)

12) Read these links on Windows driver verifier:
Enable and Disable Driver Verifier in Windows 10
https://answers.microsoft.com/en-us/...3-c48669e4c983

13) When you have performed all of the above steps you can start using the tool with the settings in this link:

Enable and Disable Driver Verifier in Windows 10

14) For any BSOD:

a) run the V2 log collector to collect new log files

b) open file explorer> this PC > C: > in the right upper corner search for: C:\Windows\memory.dmp
> if the file size is < 1.5 GB then zip > post a separate share link into the thread using one drive, drop box, or google drive

15) Download and install: Everything
voidtools
16) Launch the application and search for: NDIS-20190511-1017.dmp > zip > post a share link into the thread

Code:

Name                      LastWriteTime       Size (MB)
----                      -------------       ---------
NDIS-20190511-1017.dmp    11/05/2019 10:17:52   1613.94

Ok thanks, I'll work through the steps and report back.
I do have one ndis dump available, but it's from a different day, is that still any good?
Also did the memory dump turn up anything?
Thanks for your help

Multiple memory dump files are needed for bugcheck 133 with parameter 1.
There was no non-Microsoft driver seen in the debugging with the typical commands.

Windows driver verifier should produce different types of bugchecks which can be debugged.

Any kernel dump files within 30 days of the latest BSOD that are < 1.5 GB can be zipped and share links can be posted into the thread for debugging.

@zbook
OK thanks. I have the following files collected over the last couple of weeks, let me know if I should dropbox any/all of them, or whether I should just wait for the ones produced by driver verifier.

1 ndis dump, ndis20190519-1429.dmp (1.8gb)
5 additional full memory.dmp files, from 06/05 to 23/05, (size from 1.1-1.6gb)

I also have a cbs.log available from the sfc I ran just now..

Let's move forward in time with new mini and memory dump files produced by Windows driver verifier.

Windows may automatically delete memory dump files when free space is < 25 GB
The dump file may be 500 MB to 3 GB so please maintain drive free space > 30 GB.

OK no problem.
Here's the output of steps 1-6 for you.