question

SR-8904 avatar image
0 Votes"
SR-8904 asked JennyFeng-MSFT answered

Bugcheck code: 0x133 (0x0, 0x501, 0x500, 0xFFFFF8034B03F540) BSOD

SA
SamiRiad
Bugcheck code: 0x133 (0x0, 0x501, 0x500, 0xFFFFF8034B03F540) BSOD

Hi

Been having random BSOD on Windows 2016 server, I have attached minidump if someone can please help me figuring out the cause

https://drive.google.com/file/d/1DAj6KyGlhLuQKOltucAmSQNsD0-LoASZ/view?usp=sharing

I hope this is not related to a hardware failure in anyway, I also confirm I have tested memory, CPU all good, there is no thermal problem on this machine and all temp running within average

Thank you in advance

0: kd> !analyze -v



  •                      Bugcheck Analysis                                    *
    



DPC_WATCHDOG_VIOLATION (133)
The DPC watchdog detected a prolonged run time at an IRQL of DISPATCH_LEVEL
or above.
Arguments:
Arg1: 0000000000000000, A single DPC or ISR exceeded its time allotment. The offending
component can usually be identified with a stack trace.
Arg2: 0000000000000501, The DPC time count (in ticks).
Arg3: 0000000000000500, The DPC time allotment (in ticks).
Arg4: fffff8034b03f540, cast to nt!DPC_WATCHDOG_GLOBAL_TRIAGE_BLOCK, which contains
additional information regarding this single DPC timeout

Debugging Details:



* Debugger could not find nt in module list, module list might be corrupt, error 0x80070057.


KEY_VALUES_STRING: 1

 Key  : Analysis.CPU.Sec
 Value: 0

 Key  : Analysis.DebugAnalysisProvider.CPP
 Value: Create: 8007007e on DESKTOP-OTFME57

 Key  : Analysis.DebugData
 Value: CreateObject

 Key  : Analysis.DebugModel
 Value: CreateObject

 Key  : Analysis.Elapsed.Sec
 Value: 0

 Key  : Analysis.Memory.CommitPeak.Mb
 Value: 52

 Key  : Analysis.System
 Value: CreateObject


BUGCHECK_CODE: 133

BUGCHECK_P1: 0

BUGCHECK_P2: 501

BUGCHECK_P3: 500

BUGCHECK_P4: fffff8034b03f540

DPC_TIMEOUT_TYPE: SINGLE_DPC_TIMEOUT_EXCEEDED

STACK_TEXT:
fffff803`4cf78d88 fffff803`4accc507 : 00000000`00000133 00000000`00000000 00000000`00000501 00000000`00000500 : 0xfffff803`4adf62e0
fffff803`4cf78d90 00000000`00000133 : 00000000`00000000 00000000`00000501 00000000`00000500 fffff803`4b03f540 : 0xfffff803`4accc507
fffff803`4cf78d98 00000000`00000000 : 00000000`00000501 00000000`00000500 fffff803`4b03f540 00000000`00000000 : 0x133


SYMBOL_NAME: ANALYSIS_INCONCLUSIVE

MODULE_NAME: Unknown_Module

IMAGE_NAME: Unknown_Image

STACK_COMMAND: .thread ; .cxr ; kb

FAILURE_BUCKET_ID: CORRUPT_MODULELIST_0x133

OS_VERSION: 10.0.14393.4350

BUILDLAB_STR: rs1_release

OSPLATFORM_TYPE: x64

OSNAME: Windows 10

FAILURE_ID_HASH: {13e3c9ef-8526-da41-b41d-06d8277b0319}

windows-server
5 |1600 characters needed characters left characters exceeded

Up to 10 attachments (including images) can be used with a maximum of 3.0 MiB each and 30.0 MiB total.

JennyFeng-MSFT avatar image
0 Votes"
JennyFeng-MSFT answered

@SR-8904
Hi,
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 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.
https://www.dell.com/support/kbdoc/zh-cn/000139766/windows-stop-error-133-occurs-on-windows-server-2012
Please note: Information posted in the given link is hosted by a third party. Microsoft does not guarantee the accuracy and effectiveness of information.
Due to security policy, community support cannot download and save user’s personal data such as dump or log files, please install WinDbg from Microsoft website and analyze crash dump files.
https://docs.microsoft.com/en-us/windows-hardware/drivers/debugger/debugger-download-tools
If you really need crash dump files analysis support, open a support ticket with Microsoft.

Thanks for understanding.
Hope above information can help you.
============================================
If the Answer is helpful, please click "Accept Answer" and upvote it.
Note: Please follow the steps in our documentation to enable e-mail notifications if you want to receive the related email notification for this thread.

5 |1600 characters needed characters left characters exceeded

Up to 10 attachments (including images) can be used with a maximum of 3.0 MiB each and 30.0 MiB total.

Docs-4663 avatar image
0 Votes"
Docs-4663 answered

There was corruption.

1) Open administrative command prompt (ACP) and type or copy and paste:
2) dism /online /cleanup-image /restorehealth
3) sfc /scannow

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

5) Run V2:
https://www.windowsq.com/resources/v2-log-collector.8/
https://www.tenforums.com/bsod-crashes-debugging/2198-bsod-posting-instructions.html

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

5 |1600 characters needed characters left characters exceeded

Up to 10 attachments (including images) can be used with a maximum of 3.0 MiB each and 30.0 MiB total.