[SOLVED] - system non responsive, kernel power 41 (2024)

punkncat said:

Event 41 is in response to any unexpected shutdown. In many cases it can be an indication of a failing power supply but wouldn't expect such out of a platinum level supply, assuming it's of the proper rating for your equipment.

Is this all you see in Event Viewer?

thanks for reply
i think i may see too many, list them briefly here. Do you see anything of concern?

my power supply is either 750 or 800watt type size, though only using one cable to gpu with the split plug. Whole system was working well on last motherboard, better motherboard and windows 11 only changes.
Event viewer In critical only kernel power,

List
in error

EventData


\Device\NetBT_Tcpip_{B9F3EF71-EA8C-4C08-B44D-62F53286293B}

34000000

Binary data:

In Words
0000: 00000034
In Bytes
0000: 34 00 00 00 4...
Next error


\Device\NetBT_Tcpip_{B9F3EF71-EA8C-4C08-B44D-62F53286293B}

34000000

Binary data:
In Words
0000: 00000034
In Bytes
0000: 34 00 00 00 4...

next error
Log Name: Application
Source: VSS
Date: 11/04/2022 12:32:46 am
Event ID: 13
Task Category: None
Level: Error
Keywords: Classic
User: N/A
Computer: Troy
Description:
Volume Shadow Copy Service information: The COM Server with CLSID {4e14fba2-2e22-11d1-9964-00c04fbbb345} and name CEventSystem cannot be started. [0x8007045b, A system shutdown is in progress.
]
Event Xml:
<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
<System>
<Provider Name="VSS" />
<EventID Qualifiers="0">13</EventID>
<Version>0</Version>
<Level>2</Level>
<Task>0</Task>
<Opcode>0</Opcode>
<Keywords>0x80000000000000</Keywords>
<TimeCreated SystemTime="2022-04-10T12:32:46.5062821Z" />
<EventRecordID>5480</EventRecordID>
<Correlation />
<Execution ProcessID="6896" ThreadID="0" />
<Channel>Application</Channel>
<Computer>Troy</Computer>
<Security />
</System>
<EventData>
<Data>{4e14fba2-2e22-11d1-9964-00c04fbbb345}</Data>
<Data>CEventSystem</Data>
<Data>0x8007045b, A system shutdown is in progress.
</Data>
<Data>
</Data>
<Binary>2D20436F64653A20575254575254494330303030343932332D2043616C6C3A20575254575254494330303030343931362D205049443A202030303030363839362D205449443A202030303030373735362D20434D443A2020433A5C57696E646F77735C73797374656D33325C737663686F73742E657865202D6B204E6574776F726B53657276696365202D70202020202D20557365723A204E616D653A204E5420415554484F524954595C4E4554574F524B20534552564943452C205349443A532D312D352D3230</Binary>
</EventData>
</Event>

next error
Log Name: System
Source: Microsoft-Windows-Kernel-Boot
Date: 8/04/2022 10:34:18 am
Event ID: 29
Task Category: None
Level: Error
Keywords: (8796093022208)
User: SYSTEM
Computer: Troy
Description:
Windows failed fast startup with error status 0xC0000001.
Event Xml:
<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
<System>
<Provider Name="Microsoft-Windows-Kernel-Boot" Guid="{15ca44ff-4d7a-4baa-bba5-0998955e531e}" />
<EventID>29</EventID>
<Version>1</Version>
<Level>2</Level>
<Task>0</Task>
<Opcode>0</Opcode>
<Keywords>0x8000080000000000</Keywords>
<TimeCreated SystemTime="2022-04-07T22:34:18.7259897Z" />
<EventRecordID>9575</EventRecordID>
<Correlation />
<Execution ProcessID="4" ThreadID="8" />
<Channel>System</Channel>
<Computer>Troy</Computer>
<Security UserID="S-1-5-18" />
</System>
<EventData>
<Data Name="FailureStatus">3221225473</Data>
<Data Name="FailureMsg">A fatal error occurred processing the restoration data.
</Data>
</EventData>
</Event>

next error

Event 2, USER_ESRV_SVC_QUEENCREEK

next error
Log Name: Microsoft-Windows-Kernel-EventTracing/Admin
Source: Microsoft-Windows-Kernel-EventTracing
Date: 13/04/2022 2:27:23 pm
Event ID: 3
Task Category: Session
Level: Error
Keywords: Session
User: SYSTEM
Computer: Troy
Description:
Session "PerfDiag Logger" stopped due to the following error: 0xC0000188
Event Xml:
<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
<System>
<Provider Name="Microsoft-Windows-Kernel-EventTracing" Guid="{b675ec37-bdb6-4648-bc92-f3fdc74d3ca2}" />
<EventID>3</EventID>
<Version>1</Version>
<Level>2</Level>
<Task>2</Task>
<Opcode>14</Opcode>
<Keywords>0x8000000000000010</Keywords>
<TimeCreated SystemTime="2022-04-13T02:27:23.6430291Z" />
<EventRecordID>225</EventRecordID>
<Correlation />
<Execution ProcessID="4" ThreadID="38712" />
<Channel>Microsoft-Windows-Kernel-EventTracing/Admin</Channel>
<Computer>Troy</Computer>
<Security UserID="S-1-5-18" />
</System>
<EventData>
<Data Name="SessionName">PerfDiag Logger</Data>
<Data Name="FileName">C:\Windows\system32\WDI\LogFiles\ShutdownPerfDiagLogger.etl</Data>
<Data Name="ErrorCode">3221225864</Data>
<Data Name="LoggingMode">41943168</Data>
<Data Name="FailureReason">0</Data>
</EventData>
</Event>

next error

Log Name: System
Source: volmgr
Date: 8/04/2022 10:34:21 am
Event ID: 162
Task Category: None
Level: Error
Keywords: Classic
User: N/A
Computer: Troy
Description:
Dump file generation succeded.
Event Xml:
<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
<System>
<Provider Name="volmgr" />
<EventID Qualifiers="4">162</EventID>
<Version>0</Version>
<Level>2</Level>
<Task>0</Task>
<Opcode>0</Opcode>
<Keywords>0x80000000000000</Keywords>
<TimeCreated SystemTime="2022-04-07T22:34:21.1150623Z" />
<EventRecordID>9595</EventRecordID>
<Correlation />
<Execution ProcessID="4" ThreadID="368" />
<Channel>System</Channel>
<Computer>Troy</Computer>
<Security />
</System>
<EventData>
<Data>\Device\HarddiskVolume3</Data>
<Binary>000000000100000000000000A20004002C2F00000000000000000000000000000000000000000000</Binary>
</EventData>
</Event>

next error

Log Name: Application
Source: Application Error
Date: 14/04/2022 1:54:00 am
Event ID: 1000
Task Category: (100)
Level: Error
Keywords: Classic
User: N/A
Computer: Troy
Description:
Faulting application name: Aac3572MbHal_x86.exe, version: 1.2.8.0, time stamp: 0x61c29640
Faulting module name: combase.dll, version: 10.0.22000.527, time stamp: 0xa296a824
Exception code: 0xc0000005
Fault offset: 0x000beee1
Faulting process id: 0x93c
Faulting application start time: 0x01d84f02cf8e3dbf
Faulting application path: C:\Program Files\ASUS\AacMB\Aac3572MbHal_x86.exe
Faulting module path: C:\Windows\System32\combase.dll
Report Id: 17f20611-5eac-4cbc-94ed-e1cbcaa32880
Faulting package full name:
Faulting package-relative application ID:
Event Xml:
<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
<System>
<Provider Name="Application Error" />
<EventID Qualifiers="0">1000</EventID>
<Version>0</Version>
<Level>2</Level>
<Task>100</Task>
<Opcode>0</Opcode>
<Keywords>0x80000000000000</Keywords>
<TimeCreated SystemTime="2022-04-13T13:54:00.8733944Z" />
<EventRecordID>6046</EventRecordID>
<Correlation />
<Execution ProcessID="22124" ThreadID="0" />
<Channel>Application</Channel>
<Computer>Troy</Computer>
<Security />
</System>
<EventData>
<Data>Aac3572MbHal_x86.exe</Data>
<Data>1.2.8.0</Data>
<Data>61c29640</Data>
<Data>combase.dll</Data>
<Data>10.0.22000.527</Data>
<Data>a296a824</Data>
<Data>c0000005</Data>
<Data>000beee1</Data>
<Data>93c</Data>
<Data>01d84f02cf8e3dbf</Data>
<Data>C:\Program Files\ASUS\AacMB\Aac3572MbHal_x86.exe</Data>
<Data>C:\Windows\System32\combase.dll</Data>
<Data>17f20611-5eac-4cbc-94ed-e1cbcaa32880</Data>
<Data>
</Data>
<Data>
</Data>
</EventData>
</Event>


next error

Log Name: System
Source: Microsoft-Windows-WER-SystemErrorReporting
Date: 8/04/2022 10:34:25 am
Event ID: 1001
Task Category: None
Level: Error
Keywords: Classic
User: N/A
Computer: Troy
Description:
The computer has rebooted from a bugcheck. The bugcheck was: 0x000000a0 (0x00000000000000f1, 0x0000000000000005, 0x0000000000000021, 0xffffca0771f2a040). A dump was saved in: C:\Windows\MEMORY.DMP. Report Id: e718d109-5a7c-4ead-92be-4c849c958a8e.
Event Xml:
<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
<System>
<Provider Name="Microsoft-Windows-WER-SystemErrorReporting" Guid="{ABCE23E7-DE45-4366-8631-84FA6C525952}" EventSourceName="BugCheck" />
<EventID Qualifiers="16384">1001</EventID>
<Version>0</Version>
<Level>2</Level>
<Task>0</Task>
<Opcode>0</Opcode>
<Keywords>0x80000000000000</Keywords>
<TimeCreated SystemTime="2022-04-07T22:34:25.5471021Z" />
<EventRecordID>9640</EventRecordID>
<Correlation />
<Execution ProcessID="804" ThreadID="0" />
<Channel>System</Channel>
<Computer>Troy</Computer>
<Security />
</System>
<EventData>
<Data Name="param1">0x000000a0 (0x00000000000000f1, 0x0000000000000005, 0x0000000000000021, 0xffffca0771f2a040)</Data>
<Data Name="param2">C:\Windows\MEMORY.DMP</Data>
<Data Name="param3">e718d109-5a7c-4ead-92be-4c849c958a8e</Data>
</EventData>
</Event>

next error,

number of there types
Log Name: System
Source: Server
Date: 14/04/2022 1:40:46 am
Event ID: 2505
Task Category: None
Level: Error
Keywords: Classic
User: N/A
Computer: Troy
Description:
The server could not bind to the transport \Device\NetBT_Tcpip_{B9F3EF71-EA8C-4C08-B44D-62F53286293B} because another computer on the network has the same name. The server could not start.
Event Xml:
<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
<System>
<Provider Name="Server" />
<EventID Qualifiers="49152">2505</EventID>
<Version>0</Version>
<Level>2</Level>
<Task>0</Task>
<Opcode>0</Opcode>
<Keywords>0x80000000000000</Keywords>
<TimeCreated SystemTime="2022-04-13T13:40:46.4549069Z" />
<EventRecordID>11390</EventRecordID>
<Correlation />
<Execution ProcessID="5232" ThreadID="0" />
<Channel>System</Channel>
<Computer>Troy</Computer>
<Security />
</System>
<EventData>
<Data>\Device\NetBT_Tcpip_{B9F3EF71-EA8C-4C08-B44D-62F53286293B}</Data>
<Binary>34000000</Binary>
</EventData>
</Event>

next error

Error 13/04/2022 6:50:40 pm EventLog 6008 None

next error

, heap of different ones
Log Name: System
Source: Service Control Manager
Date: 8/04/2022 1:17:22 pm
Event ID: 7000
Task Category: None
Level: Error
Keywords: Classic
User: N/A
Computer: Troy
Description:
The Audiosrv service failed to start due to the following error:
The service did not start due to a logon failure.
Event Xml:
<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
<System>
<Provider Name="Service Control Manager" Guid="{555908d1-a6d7-4695-8e1e-26931d2012f4}" EventSourceName="Service Control Manager" />
<EventID Qualifiers="49152">7000</EventID>
<Version>0</Version>
<Level>2</Level>
<Task>0</Task>
<Opcode>0</Opcode>
<Keywords>0x8080000000000000</Keywords>
<TimeCreated SystemTime="2022-04-08T01:17:22.5954264Z" />
<EventRecordID>9791</EventRecordID>
<Correlation />
<Execution ProcessID="1032" ThreadID="1084" />
<Channel>System</Channel>
<Computer>Troy</Computer>
<Security />
</System>
<EventData>

Log Name: System
Source: Service Control Manager
Date: 29/03/2022 12:40:19 am
Event ID: 7000
Task Category: None
Level: Error
Keywords: Classic
User: N/A
Computer: Troy
Description:
The User Energy Server Service queencreek service failed to start due to the following error:
The service did not respond to the start or control request in a timely fashion.
Event Xml:
<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
<System>
<Provider Name="Service Control Manager" Guid="{555908d1-a6d7-4695-8e1e-26931d2012f4}" EventSourceName="Service Control Manager" />
<EventID Qualifiers="49152">7000</EventID>
<Version>0</Version>
<Level>2</Level>
<Task>0</Task>
<Opcode>0</Opcode>
<Keywords>0x8080000000000000</Keywords>
<TimeCreated SystemTime="2022-03-28T11:40:19.7672878Z" />
<EventRecordID>7712</EventRecordID>
<Correlation />
<Execution ProcessID="760" ThreadID="18964" />
<Channel>System</Channel>
<Computer>Troy</Computer>
<Security />
</System>
<EventData>
<Data Name="param1">User Energy Server Service queencreek</Data>
<Data Name="param2">%%1053</Data>
<Binary>55005300450052005F0045005300520056005F005300560043005F0051005500450045004E0043005200450045004B000000</Binary>
</EventData>
</Event>
<Data Name="param1">Audiosrv</Data>
<Data Name="param2">%%1069</Data>
<Binary>41007500640069006F007300720076000000</Binary>
</EventData>
</Event>

next error

heap of these types
Error 14/04/2022 12:07:10 am DistributedCOM 10010 None


next error

, heaps
Log Name: Application
Source: VSS
Date: 11/04/2022 12:32:46 am
Event ID: 8193
Task Category: None
Level: Error
Keywords: Classic
User: N/A
Computer: Troy
Description:
Volume Shadow Copy Service error: Unexpected error calling routine CoCreateInstance. hr = 0x8007045b, A system shutdown is in progress.
.
Event Xml:
<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
<System>
<Provider Name="VSS" />
<EventID Qualifiers="0">8193</EventID>
<Version>0</Version>
<Level>2</Level>
<Task>0</Task>
<Opcode>0</Opcode>
<Keywords>0x80000000000000</Keywords>
<TimeCreated SystemTime="2022-04-10T12:32:46.5062821Z" />
<EventRecordID>5481</EventRecordID>
<Correlation />
<Execution ProcessID="6896" ThreadID="0" />
<Channel>Application</Channel>
<Computer>Troy</Computer>
<Security />
</System>
<EventData>
<Data>CoCreateInstance</Data>
<Data>0x8007045b, A system shutdown is in progress.
</Data>
<Data>
</Data>
<Binary>2D20436F64653A20575254575254494330303030343933302D2043616C6C3A20575254575254494330303030343931362D205049443A202030303030363839362D205449443A202030303030373735362D20434D443A2020433A5C57696E646F77735C73797374656D33325C737663686F73742E657865202D6B204E6574776F726B53657276696365202D70202020202D20557365723A204E616D653A204E5420415554484F524954595C4E4554574F524B20534552564943452C205349443A532D312D352D3230</Binary>
</EventData>
</Event>


other errors

bits client

heap of warnings

Thanks

[SOLVED] - system non responsive, kernel power 41 (2024)

References

Top Articles
Latest Posts
Article information

Author: Pres. Lawanda Wiegand

Last Updated:

Views: 5997

Rating: 4 / 5 (71 voted)

Reviews: 94% of readers found this page helpful

Author information

Name: Pres. Lawanda Wiegand

Birthday: 1993-01-10

Address: Suite 391 6963 Ullrich Shore, Bellefort, WI 01350-7893

Phone: +6806610432415

Job: Dynamic Manufacturing Assistant

Hobby: amateur radio, Taekwondo, Wood carving, Parkour, Skateboarding, Running, Rafting

Introduction: My name is Pres. Lawanda Wiegand, I am a inquisitive, helpful, glamorous, cheerful, open, clever, innocent person who loves writing and wants to share my knowledge and understanding with you.