Windows 10: Bluescreens after last Windows update featureId:11 DRIVER_POWER_STATE_FAILUR

Hi everyone,i get crashes ever 5-10minutes after starting the pc. It crashes, when im in games or just have the computer run in idle.I tried alot of troubleshoot in the last 8 hours, but nothing helps. I reinstalled and/or updated drivers.https://drive.google.com/file/d/1aLXoqfbleh2KvC28Pc6TRB3hpiJuyEP0/view?usp=drive_linkhttps://drive.google.com/file/d/1Vp30fIuDkZQYUjqHTfJadmnz-_gYjXEG/view?usp=drive_linkhttps://drive.google.com/file/d/1dQhzp6KD1aqoLi25yyUwQffD7Tovq_X9/view?usp=drive_linkhttps://drive.google.com/file/d/1ksUJYshmFR-qd1f-SDSyNfTs1tn080dr/view?usp=drive_linkWhoCrashed gave me mu

:)

 

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:
  
  https://drive.google.com/file/d/1Vdg9SPWBuVZbzvN7NebeAj1OeUY1Q21i/view?usp=sharing
  
• 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:
  

[table][tr][td]Crash dump file:[/td][td]C:\WINDOWS\Minidump\021724-8453-01.dmp (Minidump)[/td][/tr][tr][td]Bugcheck code:[/td][td]0x133(0x1, 0x1E00, 0xFFFFF8045A91C340, 0x0)[/td][/tr][tr][td]Bugcheck name:[/td][td]DPC_WATCHDOG_VIOLATION[/td][/tr][tr][td]Driver or module in which error occurred:[/td][td](0xfffff804`57f60003)[/td][/tr][tr][td]Bug check description:[/td][td]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).[/td][/tr][tr][td]Analysis:[/td][td]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 issuesA full memory dump will likely provide more useful information on the cause of this particular bugcheck.[/td][/tr][/table]

[table][tr][td]Crash dump file:[/td][td]C:\WINDOWS\MEMORY.DMP (Full memory dump)[/td][/tr][tr][td]Bugcheck code:[/td][td]0x133(0x1, 0x1E00, 0xFFFFF8045A91C340, 0x0)[/td][/tr][tr][td]Bugcheck name:[/td][td]DPC_WATCHDOG_VIOLATION[/td][/tr][tr][td]Driver or module in which error occurred:[/td][td]featureId:11.sys (featureId:11)[/td][/tr][tr][td]Bug check description:[/td][td]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).[/td][/tr][tr][td]Analysis:[/td][td]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[/td][/tr][tr][td]Google query:[/td][td]featureId:11 DPC_WATCHDOG_VIOLATION[/td][/tr][/table]

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

 

Windows 10 Bluescreen DRIVER_POWER_STATE_FAILURE

My PC is bluescreening, and giving me a DRIVER_POWER_STATE_FAILURE. I was able to update windows last week, and the bluescreening stopped, but it has started again today. From what I can tell, nothing we do in particular causes the issue, as the system crashes within 1-2 minutes of starting up

 

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

No worries Igor, actually thanks for taken the time to help me here.

Yesterday I uninstalled/rebooted everything related to ASUS using ASUS Armoury Create Uninstaller, right now I don't see any apps from ASUS, however I just had another crash unfortunately.

How could I confirm this "IOMap64.sys" driver is gone for real? The minidump file is pointing to exactly the same file:

[table][tr][td]Crash dump file:[/td][td]C:\WINDOWS\MEMORY.DMP (Full memory dump)[/td][/tr][tr][td]Bugcheck code:[/td][td]0x133(0x1, 0x1E00, 0xFFFFF8051AB1C340, 0x0)[/td][/tr][tr][td]Bugcheck name:[/td][td]DPC_WATCHDOG_VIOLATION[/td][/tr][tr][td]Driver or module in which error occurred:[/td][td]featureId:11.sys (featureId:11)[/td][/tr][tr][td]Bug check description:[/td][td]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).[/td][/tr][tr][td]Analysis:[/td][td]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[/td][/tr][tr][td]Google query:[/td][td]featureId:11 DPC_WATCHDOG_VIOLATION[/td][/tr][/table]