Forum Discussion

WhatAPlayer1's avatar
WhatAPlayer1
Copper Contributor
Nov 19, 2024

Kernel - power 41 (63) error on new pc

Hi, after assembling a new pc after a week I started to get an error where a blue screen always appears when 1 turns on the computer (it also shows error 0xFFFFAD0F21175140). Updated all drivers, checked cables from PSU and everything looks normal. In addition, I tried reinstalling windows and the problem fixes itself for 3/4 days. After which it comes back again in exactly the same form. CPU/GPU/motherboard temperatures are normal, voltage does not jump and is at a stable level. Do you have any ideas what could be causing this error?

- <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>10</Version>

  <Level>1</Level>

  <Task>63</Task>

  <Opcode>0</Opcode>

  <Keywords>0x8000400000000002</Keywords>

  <TimeCreated SystemTime="2024-11-19T10:16:42.2482356Z" />

  <EventRecordID>10498</EventRecordID>

  <Correlation />

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

  <Channel>System</Channel>

  <Computer>DESKTOP-M06OANS</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">false</Data>

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

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

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

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

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

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

  <Data Name="LidState">3</Data>

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

  </EventData>

  </Event>

 

  • GabrielHayes's avatar
    GabrielHayes
    Iron Contributor

    Even if you've updated the drivers, sometimes particular drivers (especially graphics or chipset drivers) may still cause issues. Try reverting to older versions of critical drivers or updating them directly from the manufacturer’s websites.

  • If your CPU has integrated graphics, remove the dedicated GPU and see if the system is stable with the integrated graphics.

  • Even if your voltage seems stable, the PSU itself might be malfunctioning or underpowered for your system. Ensure that your PSU has enough wattage to support all of your components.

  • NevadaDesert's avatar
    NevadaDesert
    Copper Contributor

    Even if everything looks fine, there might be intermittent problems with the power supply unit (PSU), such as inadequate wattage for the components or faulty cables.

  • WhatAPlayer1's avatar
    WhatAPlayer1
    Copper Contributor

    In addition, I performed all the steps involved in repairing the system files (console record below):

    (1/4) Chkdsk
    The type of the file system is NTFS.

    Stage 1: Examining basic file system structure ...
      273664 file records processed.
    File verification completed.
     Phase duration (File record verification): 1.72 seconds.
      9515 large file records processed.
     Phase duration (Orphan file record recovery): 3.84 milliseconds.
      0 bad file records processed.
     Phase duration (Bad file record checking): 0.20 milliseconds.

    Stage 2: Examining file name linkage ...
      17917 reparse records processed.
      389468 index entries processed.
    Index verification completed.
     Phase duration (Index verification): 4.22 seconds.
      0 unindexed files scanned.
     Phase duration (Orphan reconnection): 134.25 milliseconds.
      0 unindexed files recovered to lost and found.
     Phase duration (Orphan recovery to lost and found): 0.21 milliseconds.
      17917 reparse records processed.
     Phase duration (Reparse point and Object ID verification): 24.28 milliseconds.

    Stage 3: Examining security descriptors ...
    Security descriptor verification completed.
     Phase duration (Security descriptor verification): 26.20 milliseconds.
      57903 data files processed.
     Phase duration (Data attribute verification): 0.20 milliseconds.
    CHKDSK is verifying Usn Journal...
      35204968 USN bytes processed.
    Usn Journal verification completed.
     Phase duration (USN journal verification): 86.93 milliseconds.

    Windows has scanned the file system and found no problems.
    No further action is required.

    1952726015 KB total disk space.
     177399592 KB in 195224 files.
        151976 KB in 57904 indexes.
             0 KB in bad sectors.
        441675 KB in use by the system.
         65536 KB occupied by the log file.
    1774732772 KB available on disk.

          4096 bytes in each allocation unit.
     488181503 total allocation units on disk.
     443683193 allocation units available on disk.
    Total duration: 6.23 seconds (6233 ms).

    (2/4) SFC - 1st scan

    Beginning system scan.  This process will take some time.

    Beginning verification phase of system scan.
    Verification 100% complete.

    Windows Resource Protection found corrupt files and successfully repaired them.
    For online repairs, details are included in the CBS log file located at
    windir\Logs\CBS\CBS.log. For example C:\Windows\Logs\CBS\CBS.log. For offline
    repairs, details are included in the log file provided by the /OFFLOGFILE flag.

    (4/4) SFC - 2nd scan

    Beginning system scan.  This process will take some time.

    Beginning verification phase of system scan.
    Verification 100% complete.

    Windows Resource Protection found corrupt files and successfully repaired them.
    For online repairs, details are included in the CBS log file located at
    windir\Logs\CBS\CBS.log. For example C:\Windows\Logs\CBS\CBS.log. For offline
    repairs, details are included in the log file provided by the /OFFLOGFILE flag.

    CBS  FILE :
    https://1drv.ms/u/c/0190b53d52098b23/ERGzw4Ea00lEjyTP_V8Ax70BrfTQYYh2leQIocQrtskIoA

Resources