Ask a new question

PC Crash featureId:11.sys (featureId:11)

Hi there, I need help to identify the root cause of my PC crashing like once every 3 days. Below you can find more details:

1. Problem Description:

I've had this PC for one year working fine but during the last month it has started to crash when gaming and also when NOT gaming, happens 2-3 times per week. No recent software installed, no overclock, the only software installations I run are the regular Windows and NVidia GeForce Experience updates.

2. PC components:

-ASUS ROG STRIX X670E-E GAMING WIFI

-AMD Ryzen 9 7900X

-NVIDIA GeForce RTX 4080

-Teamgroup T-Force Delta 2x 16 GB 6200 MHz CL38

-PSU: Corsair HX1200 Platinum

3. Actions Taken:

  • Collected logs from Event Viewer here are the messages found during the crash:

    • The previous system shutdown was unexpected, event ID 6008

    • Power (Microsoft-Windows-Kernel-Processor-Power), event ID 55

    • The server Windows.Gaming.GameBar.PresenceServer.Internal.PresenceWriter did not register with DCOM within the required timeout.

  • Collected the Reliability history:

    Description

    A problem with your hardware caused Windows to stop working correctly.

    Problem signature

    Problem Event Name: LiveKernelEvent

    Code: 141

    Parameter 1: ffffda8676ab8460

    Parameter 2: fffff804a694f270

    Parameter 3: 0

    Parameter 4: 0

    OS version: 10_0_22631

    Service Pack: 0_0

    Product: 768_1

    OS Version: 10.0.22631.2.0.0.768.101

    Locale ID: 1033

  • Uploaded the minidump file to this location:

  • I also have the full memory DMP, but the size is around 30 GB and 14 GB after compression, so not sure how to share that one.

  • According to the DMP analyzer tool "Whocrashed" this is what I get:

Crash dump file:

C:\WINDOWS\Minidump\021724-8453-01.dmp (Minidump)

Bugcheck code:

0x133(0x1, 0x1E00, 0xFFFFF8045A91C340, 0x0)

Bugcheck name:

DPC_WATCHDOG_VIOLATION

Driver or module in which error occurred:

(0xfffff804`57f60003)

Bug check description:

The DPC watchdog detected a prolonged run time at an IRQL of DISPATCH_LEVEL or above. This could be caused by either a non-responding driver or non-responding hardware. This bug check can also occur because of overheated CPUs (thermal issue).

Analysis:

This is likely caused by a hardware problem, but there is a possibility that this is caused by a misbehaving driver.
This bugcheck indicates that a timeout has occurred. This may be caused by a hardware failure such as a thermal issue or a bug in a driver for a hardware device.
Read this article on thermal issues
A full memory dump will likely provide more useful information on the cause of this particular bugcheck.

Crash dump file:

C:\WINDOWS\MEMORY.DMP (Full memory dump)

Bugcheck code:

0x133(0x1, 0x1E00, 0xFFFFF8045A91C340, 0x0)

Bugcheck name:

DPC_WATCHDOG_VIOLATION

Driver or module in which error occurred:

featureId:11.sys (featureId:11)

Bug check description:

The DPC watchdog detected a prolonged run time at an IRQL of DISPATCH_LEVEL or above. This could be caused by either a non-responding driver or non-responding hardware. This bug check can also occur because of overheated CPUs (thermal issue).

Analysis:

This is likely caused by a hardware problem, but there is a possibility that this is caused by a misbehaving driver.
This bugcheck indicates that a timeout has occurred. This may be caused by a hardware failure such as a thermal issue or a bug in a driver for a hardware device.
Read this article on thermal issues

Google query:

featureId:11 DPC_WATCHDOG_VIOLATION

  • I use MSI Afterburner to keep track of temperatures, during the crash the GPU is around 55 degrees and CPU 65-70 Celsius. So no temperature spikes before or during crash.

  • I've ran the following diagnostics tools and always the result is success, no problems found:

    • Memory Diagnostic Utility (mdsched)

    • CHKSDK

    • SFC

  • I have done a lot of research online using the messages from the Event Viewer/Windows Logs/System but I have already applied the suggestions without any luck, so decided to contact the experts.

Any help will be appreciated. Thanks in advanced.

Answer
Answer

If possible please detach all Logitech hardware and uninstall all Logitech software / drivers > reattach and reinstall only a absolutely necessary hardware and drivers

logi_lamparray Logitech LampArray Device Driver c:\windows\system32\driverstore\filerepository\logi_lamparray_usb.inf_amd64_0772df9f9e65a702\logi_lamparray.sys

Logitech LampArray Service logi_lamparray_service c:\windows\system32\driverstore\filerepository\logi_lamparray_usb.inf_amd64_0772df9f9e65a702\logi_lamparray_service.exe

Restart WDV.

If there is no immediate BSOD then post a verifier /querysettings share link.

For any BSOD post a new V2 share link.

2 people found this reply helpful

·

Was this reply helpful?

Sorry this didn't help.

Great! Thanks for your feedback.

How satisfied are you with this reply?

Thanks for your feedback, it helps us improve the site.

How satisfied are you with this reply?

Thanks for your feedback.

 
 

Question Info

Last updated April 16, 2025 Views 1,005 Applies to: