Windows Server 2016 DPC Watchdog Violation 133 HP ProLiant

Question

Been having lots of reboots on my HP ProLiant DL380 (Gen 10). Have analyzed memory dumps and came across a few different issues causing the BSODs. This server is utlized to run 5 VMs through Hypervisor.

Total of 3 Memory Dumps, after analysis shows these errors.

1) fffff802ab28e000 fffff802abaab000 nt (pdb symbols) C:\ProgramData\Dbg\sym\ntkrnlmp.pdb\517E128F7B7C4EA79491DE6B9B9CE1901\ntkrnlmp.pdb
Loaded symbol image file: ntkrnlmp.exe
Mapped memory image file: C:\ProgramData\Dbg\sym\ntoskrnl.exe\6104D5BB81d000\ntoskrnl.exe
Image path: ntkrnlmp.exe
Image name: ntkrnlmp.exe

2)fffff801d4e07000 fffff801d5624000 nt (pdb symbols) C:\ProgramData\Dbg\sym\ntkrnlmp.pdb\517E128F7B7C4EA79491DE6B9B9CE1901\ntkrnlmp.pdb
Loaded symbol image file: ntkrnlmp.exe
Mapped memory image file: C:\ProgramData\Dbg\sym\ntoskrnl.exe\6104D5BB81d000\ntoskrnl.exe
Image path: ntkrnlmp.exe
Image name: ntkrnlmp.exe

3)fffff803a7480000 fffff803a76f9000 tcpip (pdb symbols) C:\ProgramData\Dbg\sym\tcpip.pdb\BD2D21339F504FB385C47F22D747CD751\tcpip.pdb
Loaded symbol image file: tcpip.sys
Mapped memory image file: C:\ProgramData\Dbg\sym\tcpip.sys\6104D4C3279000\tcpip.sys
Image path: \SystemRoot\System32\drivers\tcpip.sys

Not sure what to make of these, got in touch with HP support and they told me to update the BIOPS and ILO channel Interface....but I suspect that is only the common solution given by their reps as they could not even tell me what is causing the nt errors which are the main concern?? nt errors causing BSOD has been happening at random times, sometimes in the morning right before operations start.

Maybe I'm missing something from the dumps/minidumps. Seems to be caused whenever I use Kaseya to remote onto the desktop, otherwise will run properly otherwise. Upon further troubleshooting Windows troubleshooter mentioned 9 corrupted payload files and a repair for windows is necessary. Completed a Memory Diagnostic Tool pass and no errors were detected so not corrupt memory.

Just want this server to be operational and not obsolete....

Answer 1

See if you can run either the V2 or DM log collector and post a share link into this thread using one drive, drop box, or google drive.

If the memory dumps are each < 1.5 GB then post separate share links for each file into this thread.

https://www.windowsq.com/t/bsod-posting-instructions.17/
https://www.windowsq.com/resources/v2-log-collector.8/
https://www.windowsq.com/resources/dm-log-collector.9/
https://www.tenforums.com/bsod-crashes-debugging/2198-bsod-posting-instructions.html

.
.
.
.
Please remember to vote and to mark the replies as answers if they help.

On the bottom of each post there is:

Propose as answer = answered the question

On the left side of each post: Vote = a helpful post
.
.
.
.
.

Answer 2

Hello @EW Inc

Without a more thorough dump analysis, I would recommend the next in my experience. I need to advice extreme care with next actions, as they contain steps that may damage your system in case of not executed properly:

1. Download and update to latest firmware and BIOS versions from the manufacturer website.
2. Remove connected devices such as printers, external drives, usb devices, etc
3. Update Windows to latest version
4. Disable third party services, and if fixed re-enable on single basis to find with causes the issue (using msconfig.exe>Services tab, select Hide Microsoft services, then Disable All)
5. Reposition your components by, -once computer if off, and PSU turned off as well, AC cable disconnected-, disconnect your RAM modules, GPU, and other PCI and connect them again.

Try one step a a time, and test for a while to verify if the issue is still happening or is fixed.
Best regards,

Answer 3