BSOD playing Total War Warhammer II, 0x00000133

I today started playing the campaign mode in Warhammer II; after finishing a battle and entering the loading screen back to the campaign map, I'll get a DPC_watchdog_violation BSOD.

This is the only game that produces the BSOD and only in the above circumstances. I've updated pretty much every driver I can think of (short of a BIOS update) and tried the simple proposed fixes for a DPC_watchdog_violation. I do have my CPU and GPU overclocked, but have still get a BSOD after disabling them.

Any help would be appreciated.

I have attached my HDTune Benchmarks as I am still running other tests.

I do want to note my PC is only a few months old and I doubt the SSD and one of the HDDs will have bad health. I have one other HDD I took from my old PC which is being used purely for storage of movies/music/photos etc) so shouldn't be affecting games at all.

I couldn't set my SATA controls in BIOS to anything other than AHCI and RAID, so I am running SeaTools for Windows.

Thanks

No worries, hopefully I should have it all done by tonight.

What does paging errors imply?

How would you generally resolve paging error issues? Are there any software fixes (is this related to page file)?

These are some of the errors in the event.vwr related to the drive.
To evaluate the drive tests (chkdsk, HD Tune, Sea Tools) were ordered on all drives to rule in / rule out drive problems.

Code:

Event[9453]:  Log Name: System  Source: Disk  Date: 2017-10-22T19:11:56.463  Event ID: 32  Task: N/A  Level: Warning  Opcode: N/A  Keyword: Classic  User: N/A  User Name: N/A  Computer: DESKTOP-TCBBH5U  Description: The driver detected that the device \Device\Harddisk2\DR2 has its write cache enabled. Data corruption may occur.

Code:

Event[5881]:  Log Name: System  Source: Microsoft-Windows-Ntfs  Date: 2017-09-16T09:50:32.321  Event ID: 140  Task: N/A  Level: Warning  Opcode: Info  Keyword: N/A  User: S-1-5-18  User Name: NT AUTHORITY\SYSTEM  Computer: DESKTOP-TCBBH5U  Description: The system failed to flush data to the transaction log. Corruption may occur in VolumeId: G:, DeviceName: \Device\HarddiskVolume40.(A device which does not exist was specified.)

Code:

Event[5866]:  Log Name: System  Source: Microsoft-Windows-Ntfs  Date: 2017-09-16T09:49:19.313  Event ID: 140  Task: N/A  Level: Warning  Opcode: Info  Keyword: N/A  User: S-1-5-18  User Name: NT AUTHORITY\SYSTEM  Computer: DESKTOP-TCBBH5U  Description: The system failed to flush data to the transaction log. Corruption may occur in VolumeId: G:, DeviceName: \Device\HarddiskVolume39.(A device which does not exist was specified.)

Code:

Event[7177]:  Log Name: System  Source: Disk  Date: 2017-10-03T08:51:19.658  Event ID: 153  Task: N/A  Level: Warning  Opcode: N/A  Keyword: Classic  User: N/A  User Name: N/A  Computer: DESKTOP-TCBBH5U  Description: The IO operation at logical block address 0x600878 for Disk 3 (PDO name: \Device\0000003e) was retried.

Code:

Event[6922]:  Log Name: System  Source: Disk  Date: 2017-09-30T09:55:44.655  Event ID: 153  Task: N/A  Level: Warning  Opcode: N/A  Keyword: Classic  User: N/A  User Name: N/A  Computer: DESKTOP-TCBBH5U  Description: The IO operation at logical block address 0x19fdfb68 for Disk 3 (PDO name: \Device\0000003e) was retried.

Code:

Event[6581]:  Log Name: System  Source: Disk  Date: 2017-09-25T21:12:47.409  Event ID: 153  Task: N/A  Level: Warning  Opcode: N/A  Keyword: Classic  User: N/A  User Name: N/A  Computer: DESKTOP-TCBBH5U  Description: The IO operation at logical block address 0x19fdfb50 for Disk 3 (PDO name: \Device\0000003e) was retried.

Code:

Event[5427]:  Log Name: System  Source: Disk  Date: 2017-09-16T09:35:33.688  Event ID: 153  Task: N/A  Level: Warning  Opcode: N/A  Keyword: Classic  User: N/A  User Name: N/A  Computer: DESKTOP-TCBBH5U  Description: The IO operation at logical block address 0x3a37c450 for Disk 3 (PDO name: \Device\000000b9) was retried.

Code:

Event[5059]:  Log Name: System  Source: Disk  Date: 2017-09-16T09:21:18.818  Event ID: 51  Task: N/A  Level: Warning  Opcode: N/A  Keyword: Classic  User: N/A  User Name: N/A  Computer: DESKTOP-TCBBH5U  Description: An error was detected on device \Device\Harddisk3\DR4 during a paging operation.

Code:

Event[5120]:  Log Name: System  Source: Disk  Date: 2017-09-16T09:24:36.996  Event ID: 51  Task: N/A  Level: Warning  Opcode: N/A  Keyword: Classic  User: N/A  User Name: N/A  Computer: DESKTOP-TCBBH5U  Description: An error was detected on device \Device\Harddisk3\DR6 during a paging operation.

Code:

Event[5224]:  Log Name: System  Source: Disk  Date: 2017-09-16T09:31:48.371  Event ID: 51  Task: N/A  Level: Warning  Opcode: N/A  Keyword: Classic  User: N/A  User Name: N/A  Computer: DESKTOP-TCBBH5U  Description: An error was detected on device \Device\Harddisk3\DR11 during a paging operation.

Code:

Event[5621]:  Log Name: System  Source: Disk  Date: 2017-09-16T09:39:56.791  Event ID: 51  Task: N/A  Level: Warning  Opcode: N/A  Keyword: Classic  User: N/A  User Name: N/A  Computer: DESKTOP-TCBBH5U  Description: An error was detected on device \Device\Harddisk3\DR23 during a paging operation.

I'll post the other reports tonight, but that is concerning as the 4TB hard drive is actually the newer one.

I recall I manually changed the page file a while ago, could this potentially have an effect?