Share via

Kernel-Power (63) id:41 key words : (70368744177664),(2)

Anonymous
2018-02-07T22:57:41+00:00

- <Event xmlns="**http://schemas.microsoft.com/win/2004/08/events/event**">

- <System>

<Provider Name="Microsoft-Windows-Kernel-Power" Guid="{331C3B3A-2005-44C2-AC5E-77220C37D6B4}" />

<EventID>41</EventID>

<Version>6</Version>

<Level>1</Level>

<Task>63</Task>

<Opcode>0</Opcode>

<Keywords>0x8000400000000002</Keywords>

<TimeCreated SystemTime="2018-02-07T18:41:52.232381400Z" />

<EventRecordID>10447</EventRecordID>

<Correlation />

<Execution ProcessID="4" ThreadID="8" />

<Channel>System</Channel>

<Computer>DESKTOP-P7I3RNH</Computer>

<Security UserID="S-1-5-18" />

</System>

- <EventData>

<Data Name="BugcheckCode">0</Data>

<Data Name="BugcheckParameter1">0x0</Data>

<Data Name="BugcheckParameter2">0x0</Data>

<Data Name="BugcheckParameter3">0x0</Data>

<Data Name="BugcheckParameter4">0x0</Data>

<Data Name="SleepInProgress">0</Data>

<Data Name="PowerButtonTimestamp">0</Data>

<Data Name="BootAppStatus">0</Data>

<Data Name="Checkpoint">0</Data>

<Data Name="ConnectedStandbyInProgress">false</Data>

<Data Name="SystemSleepTransitionsToOn">0</Data>

<Data Name="CsEntryScenarioInstanceId">0</Data>

<Data Name="BugcheckInfoFromEFI">true</Data>

<Data Name="CheckpointStatus">0</Data>

</EventData>

</Event>


- System
- Provider <br> --- --- <br><br><br><br> [ Name] Microsoft-Windows-Kernel-Power <br> --- --- --- --- --- <br><br><br><br><br> [ Guid] {331C3B3A-2005-44C2-AC5E-77220C37D6B4} <br> --- --- --- --- ---
EventID 41 <br> --- --- ---
Version 6 <br> --- --- ---
Level 1 <br> --- --- ---
Task 63 <br> --- --- ---
Opcode 0 <br> --- --- ---
Keywords 0x8000400000000002 <br> --- --- ---
- TimeCreated <br> --- --- <br><br><br><br> [ SystemTime] 2018-02-07T18:41:52.232381400Z <br> --- --- --- --- ---
EventRecordID 10447 <br> --- --- ---
Correlation <br> --- ---
- Execution <br> --- --- <br><br><br><br> [ ProcessID] 4 <br> --- --- --- --- --- <br><br><br><br><br> [ ThreadID] 8 <br> --- --- --- --- ---
Channel System <br> --- --- ---
Computer DESKTOP-P7I3RNH <br> --- --- ---
- Security <br> --- --- <br><br><br><br> [ UserID] S-1-5-18 <br> --- --- --- --- ---
- EventData
BugcheckCode 0
BugcheckParameter1 0x0
BugcheckParameter2 0x0
BugcheckParameter3 0x0
BugcheckParameter4 0x0
SleepInProgress 0
PowerButtonTimestamp 0
BootAppStatus 0
Checkpoint 0
ConnectedStandbyInProgress false
SystemSleepTransitionsToOn 0
CsEntryScenarioInstanceId 0
BugcheckInfoFromEFI true
CheckpointStatus 0

Moved from: Windows / Windows 10 / Sleep and Power on/off

Windows for home | Windows 10 | Performance and system failures

Locked Question. This question was migrated from the Microsoft Support Community. You can vote on whether it's helpful, but you can't add comments or replies or follow the question.

0 comments No comments

3 answers

Sort by: Most helpful
  1. Anonymous
    2018-02-18T17:40:18+00:00

    The Event ID 6008 is logged to the System event log when a shutdown operation is initiated automatically by a program. Meanwhile, the DCOM event ID 10016 is related to certain processes not having permissions to the DCOM components that are mentioned in the event logs. The specific communications that are blocked are determined to have no adverse functionality other than generating 10016 event logs. We highly recommend that you just ignore these errors because they don't adversely affect functionality. You may refer to this support article for more information: DCOM event ID 10016 is logged in Windows.

    We hope the information we provided helps.

    Was this answer helpful?

    0 comments No comments
  2. Anonymous
    2018-02-17T01:00:32+00:00

    Hi Joaquín,

    Based on the error log information that you have provided, your system encountered something unexpected that prevented Windows from shutting down correctly. As of now, we don't have enough information to explicitly define what happened. To determine what may have caused the issue, we need to take note of the tasks or programs running just before the unexpected shutdown behavior occurred. It's important that the installed drivers for your devices and version of your Windows are up-to-date. You may refer to the following support article to get updated to the most recent version:

    This also could be related to a power interruption or an underpowered or failing power supply. If you have installed additional devices such as RAM or hard drives when the issue began, the power supply may have caused the problem.

    The following possibilities related to hardware can also be taken into consideration:

    1. Overclocking: Disable overclocking to see whether the issue occurs when the system is run at the correct speed.
    2. Check the memory: Verify the memory by using a memory checker. Verify that each memory chip is the same speed and that it is configured correctly in the system.
    3. Power supply: Make sure that the power supply has enough wattage to appropriately handle the installed devices. If you added memory, installed a newer processor, installed additional drives, or added external devices, such devices can require more energy than the current power supply can provide consistently.
    4. Overheating: Check whether the system is overheating by examining the internal temperature of the hardware.
    5. Defaults: Reset the system back to the system defaults to see whether the issues occur when the system is running in its default configuration.

    You may need to contact your computer manufacturer to seek assistance with your hardware configuration. Refer to this support article to help you find your: Computer manufacturers' contact information.

    We are eager on getting this resolved for you; we will wait for your feedback.

    Hi thanks for the answer but all that you told me i`ve already cheked and i´m not able to find the issue. But i have 2 events before the kernel power (41); they are: 

     1- Event log (6008): it said that the system was shut down improperly as a description; but i can assure that it´s not true. 

    2-Distributed COM (10016)--> CLSID {D63B10C5-BB46-4990-A94F-E40B9D520160} and APPID  {9CA88EE3-ACB7-47C8-AFC4-AB702511C276}. 

    In the second one i´ve tried to change the permissions but it doesn´t get fixed.

    Regards, Joaquín.

    Was this answer helpful?

    0 comments No comments
  3. Anonymous
    2018-02-15T20:30:20+00:00

    Hi Joaquín,

    Based on the error log information that you have provided, your system encountered something unexpected that prevented Windows from shutting down correctly. As of now, we don't have enough information to explicitly define what happened. To determine what may have caused the issue, we need to take note of the tasks or programs running just before the unexpected shutdown behavior occurred. It's important that the installed drivers for your devices and version of your Windows are up-to-date. You may refer to the following support article to get updated to the most recent version:

    This also could be related to a power interruption or an underpowered or failing power supply. If you have installed additional devices such as RAM or hard drives when the issue began, the power supply may have caused the problem.

    The following possibilities related to hardware can also be taken into consideration:

    1. Overclocking: Disable overclocking to see whether the issue occurs when the system is run at the correct speed.
    2. Check the memory: Verify the memory by using a memory checker. Verify that each memory chip is the same speed and that it is configured correctly in the system.
    3. Power supply: Make sure that the power supply has enough wattage to appropriately handle the installed devices. If you added memory, installed a newer processor, installed additional drives, or added external devices, such devices can require more energy than the current power supply can provide consistently.
    4. Overheating: Check whether the system is overheating by examining the internal temperature of the hardware.
    5. Defaults: Reset the system back to the system defaults to see whether the issues occur when the system is running in its default configuration.

    You may need to contact your computer manufacturer to seek assistance with your hardware configuration. Refer to this support article to help you find your: Computer manufacturers' contact information.

    We are eager on getting this resolved for you; we will wait for your feedback.

    Was this answer helpful?

    0 comments No comments