help！blue screen：DPC WATCHDOG VIOLATION。

Question

Recently, my server often has blue screens, which bothers me a lot. I hope I can get help.
This is a DMP file。
https://drive.google.com/file/d/1Y0CaKWdinY2d1qkfm8z4deESIra_NCVB/view?usp=sharing

Answer 1

Hi,
I'm afraid that the DPM file has been damaged. Debugger could not find nt in module list, module list might be corrupt.
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.

If you are not equipped to use the Windows debugger to this problem, you should 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.
Meanwhile, I suggest that we could check for update. If any security update could be found, installing firstly to check.
Hope this helps and please help to accept as Answer if the response is useful.
Best Regards,
Carl

Answer 2

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 > save to the downloads folder > zip > post a separate share link into the thread using one drive, drop box, or google drive

Please run V2 > post a share link into this thread

https://www.windowsq.com/resources/v2-log-collector.8
https://www.tenforums.com/bsod-crashes-debugging/2198-bsod-posting-instructions.html
https://www.elevenforum.com/resources/v2-log-collector.1/

.
.
.
.
.

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 3

The latest mini and memory dumps were corrupt.

Unable to read NT module Base Name string at 0000000000000064 - NTSTATUS 0xC0000147 Missing image name, possible paged-out or corrupt data. Page fffffa294 too large to be in the dump file. Unable to read KLDR_DATA_TABLE_ENTRY at 00007ffbba294df0 - HRESULT 0x80004002

The logs were in a foreign language with some English words.

So scanning was limited.

There were 4 BSOD recorded:

Date: 2021-07-24T09:04:15.247

Date: 2021-07-14T15:01:30.694

Date: 2021-07-13T07:15:08.296

Date: 2021-07-10T13:54:35.637

Name : Microsoft Windows Server 2016 Standard
Version : 10.0.14393
LicensingStatusReason : 0xC004F00F
LocalGenuineState : SL_GEN_STATE_INVALID_LICENSE
ActiveSkuDescription : Windows(R) Operating System, VOLUME_KMSCLIENT channel

Please activate Windows.
https://www.tenforums.com/tutorials/55383-use-activation-troubleshooter-windows-10-a.html
https://support.microsoft.com/en-us/help/20527/windows-10-activation-troubleshooter
https://support.microsoft.com/en-us/help/4051701/global-customer-service-phone-numbers
https://support.microsoft.com/en-us/help/4028407/windows-10-activate
https://support.microsoft.com/en-in/help/12440/windows-10-activate

https://learn.microsoft.com/en-us/windows-server/get-started/activation-troubleshoot-kms-issues
https://learn.microsoft.com/en-us/windows-server/get-started/activation-troubleshoot-kms-general
https://learn.microsoft.com/en-us/windows-server/get-started/server-2016-activation
https://learn.microsoft.com/en-us/windows-server/get-started/kmsclientkeys

1) Open administrative command prompt (ACP) and type or copy and paste:

2) sfc /scannow
3) dism /online /cleanup-image /scanhealth
4) dism /online /cleanup-image /restorehealth
5) sfc /scannow
6) chkdsk /scan
7) bcdedit /enum {badmemory}

8) 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

Type: win + r keys
Type: Sysdm.cpl
Click the advanced tab
In startup and recovery click settings
Post an image or share link for the startup and recovery window

Click cancel so that the startup and recovery window closes

Under performance click settings
Click the advanced tab
Under virtual memory click change
Post an image or share link for the virtual memory window

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 > save to the downloads folder > zip > post a separate share link into the thread using one drive, drop box, or google drive

.
.
.
.
.

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
.
.
.
.
.