The encoding of the left PC (as has been done several times before), came back and it restarted

0


Hello,

All of the components in my PC are new (only about 3 months) and it generally performs as expected. I let my PC encode a file queue (x265) which has been done before, without problem. A few hours later it had restarted (which it was supposed to do if it got wrong, instead of shutting down).

Software

-Windows 11 (to clean install, current at time of writing)

– BIOS (latest version available at time of writing)

– System chipset and drivers (all latest available at time of writing except Nvidia which Windows installed after using Safe Mode + DDU to remove the old driver – because I think nvlddmkm was the cause of the crash, although I’m happy to be wrong, I’m installing the latest Nvidia drivers without GFE, or the Nvidia audio drivers)

– The crash took approximately 13 hours from verification on PC to when the crash was reported in Event Viewer

– SFC / SCANNOW does not report any violation

– Quick start / quick start is disabled

– The atrocious “Armory Crate” software from Asus is enabled by default in BIOS to install once in Windows (!) – it installed and I have removed / cleaned it since, including the legacy services it installed and not removed.

– Edit: I have now installed the latest Nvidia ‘Creative’ drivers and will repeat the same test to see if I can reproduce the crash. I will also keep this thread monitored on my phone to respond if asked.

Hardware – Speccy link in this thread is not working

➡️ Species release: http://speccy.piriform.com/results/IkSK7FPz1Np1TLSrIbsv6T3

Stuff Speccy Misses:

– M.2 NVMe drive is: WDS100T2B0C-00PXH0

– RAM is Corsair Vengeance LPX 3600 CL18 ‘Optimized for Ryzen’

– The power supply is Corsair RM850X

– Fans: 240mm radiator (2 * 140mm) + 140mm fan = inlet | 360mm radiator (3 * 120mm) + 140mm fan = outlet

Material – Temperatures

️CPU ccooling is provided by a Corsair H150 (360mm radiator) running at 2000rpm * 3 which keeps the hottest part of the processor at 68 ° C under x265 workload (AVX2)

️GPU cooling is provided by an attached 240mm radiator. At idle / low usage, GPU stays at ~ 25 ° C and memory at ~ 26 ° C. When fully loaded, the GPU rises to ~ 50 ° C and the memory rises to 85 ° C (within specification limits)

Hardware – Overclocking

The only item that can be considered overclocked is memory. It works at its rated XMP (3600, CL18, 1.35V) and was tested for 48H in memtest before installing Windows. The CPU is not overclocked (apart from the memory which forces 1: 1 FCLK: UCLK). Processor power limits are in stock.

Dump and requested files

I downloaded both the MEMORY.DMP and the 122821-8703-01.dmp Minidump to my pCloud public directory.

2.16 GB | MEMORY.DMP here: https://filedn.com/lNL17ziIgWrVnCREc5hiAem/MEMORY.DMP WHERE MEMORY.DMP

10.80 MB | Minidump 122821-8703-01.dmp here: https://filedn.com/lNL17ziIgWrVnCREc5hiAem/122821-8703-01.dmp WHERE 122821-8703-01.dmp

And as requested, I downloaded SysnativeFileCollectionApp, let it run, and attached the output (which seems to include the minidump).

Information

It’s been many years since I’ve seen BSODs on my personal workstation, but remember WhoCrashed? as being good software, but not quite sure about its accuracy. I also went through Event Viewer to see what was logged at the time of the crash / restart – it appears to be a crash since a full dump file was created.

Who crashed? reports the following:

On Tue 12/28/2021 20:17:57 your computer crashed or a problem was reported

crash dump file: C: Windows Minidump 122821-8703-01.dmp

This is probably due to the following module: amdppm.sys (amdppm + 0x2f38)

Verification code: 0x133 (0x0, 0x501, 0x500, 0xFFFFF80780105330)

Error: DPC_WATCHDOG_VIOLATION

file path: C: Windows system32 drivers amdppm.sys

product: Microsoft® Windows® operating system

company: Microsoft Corporation

description: Processor device driver

Bug Check Description: The DPC watchdog detected an extended execution time at an IRQL of DISPATCH_LEVEL or higher. This could be due to an unresponsive driver or unresponsive hardware. This bug check can also occur due to overheating processors (thermal issue).

The crash took place in a Microsoft module. The module description can give a clue about an unresponsive device in the system.

On Tue 12/28/2021 20:17:57 your computer crashed or a problem was reported

crash dump file: C: Windows MEMORY.DMP

This is probably due to the following module: nvlddmkm.sys (nvlddmkm + 0xfbb19)

Verification code: 0x133 (0x0, 0x501, 0x500, 0xFFFFF80780105330)

Error: DPC_WATCHDOG_VIOLATION

file path: C: Windows System32 DriverStore FileRepository nv_dispi.inf_amd64_1c83a5d7cffd7bff nvlddmkm.sys

Product: NVIDIA Windows Kernel Mode Driver, Version 456.71

company: NVIDIA Corporation

description: NVIDIA Windows Kernel Mode Driver Version 456.71

Bug Check Description: The DPC watchdog detected an extended execution time at an IRQL of DISPATCH_LEVEL or higher. This could be due to an unresponsive driver or unresponsive hardware. This bug check can also occur due to overheating processors (thermal issue).

A third-party driver has been identified as the probable cause of this system error. It is suggested that you check for an update for the following driver: nvlddmkm.sys (NVIDIA Windows Kernel Mode Driver, version 456.71, NVIDIA Corporation).

Google query: nvlddmkm.sys NVIDIA Corporation DPC_WATCHDOG_VIOLATION

Event Viewer (events recorded approximately at the time of the crash / in less than a minute):

ERROR

Event ID 6008 / EventLog

The previous system shutdown at 8:17:08 PM on 12/28/2021 was unexpected.

Event ID 1001 / BugCheck

The computer has restarted after a virus check. The bugcheck was: 0x000000133 (0x0000000000000000, 0x0000000000000501, 0x000000000000500, 0xfffff80780105330). A dump has been saved in: C: Windows MEMORY.DMP. Report ID: 9ed0ef1e-9be0-41b1-bdf3-c7f9248d5f1b.

Event ID 162 / volmgr

The generation of the dump file was successful.

Event ID 86 / CertificateServicesClient-CertEnroll (this is a problem that happens often, without a fix from AMD or MS)

GetCACaps

GetCACaps: not found

{“Message”: “The authority ” amd-keyid-578c545f796951421221a4a578acdb5f682f89c8.microsoftaik.azure.net “does not exist.”}

HTTP / 1.1 404 not found

Date: Tue 28 Dec 2021 20:18:37 GMT

Content-Length: 121

Content type: application / json; character set = utf-8

X-Content-Type-Options: sniff

Strict-Transport-Security: max-age = 31536000; includeSubDomains

X-ms Request ID: b503c0a0-2e5d-4398-a953-914af5155903

Method: GET (172 ms)

Step: GetCACaps

Not found (404). 0x80190194 (-2145844844 HTTP_E_STATUS_NOT_FOUND)

WARNING

Event ID 41 / Kernel-Power

The system restarted without shutting down properly first. This error can be caused if the system has stopped responding, crashed, or lost power unexpectedly.

Event ID 27 / e2fexpress – (occurs on every reboot)

Intel® Ethernet Controller (3) I225-V

The network link is disconnected.

Event ID 10016 / DistributedCOM – (there are several similar messages that are present since the installation of Windows 11)

Application-specific permission settings do not grant local activation permission for the COM server application with CLSID

{2593F8B9-4EAF-457C-B68A-50F6B8EA6B54}

and APPID

{15C20B67-12E7-4BB6-92BB-7AFF07997402}

to user WORKSTATION piers SID (S-1-5-21-2723446627-1228071440-4140764789-1001) from LocalHost (Using LRPC) running in application container Unavailable SID (Unavailable) . This security permission can be changed using the Component Services Administration Tool.

Application-specific permission settings do not grant local launch permission for the COM server application with CLSID

Windows.SecurityCenter.WscDataProtection

and APPID

Unavailable

to user NT AUTHORITY SYSTEM SID (S-1-5-18) from LocalHost (Using LRPC) running in application container Unavailable SID (Unavailable). This security permission can be changed using the Component Services Administration Tool.

I look forward to any help that can be offered and thank you for reading the above.

// Piers

Edit: Something happened to the SysnativeFileCollectionApp.zip file when I edited the post. I have now attached it here as well as in the response.

Published by PiersJ, Hier, 18:36.


Share.

About Author

Comments are closed.