Share via

Help me solve the Kernel-Power 41 (63) problem

Anton Maksimov 0 Reputation points
2026-03-13T12:56:23.57+00:00
BugcheckCode 190
BugcheckCode 190
BugcheckParameter1 0xffff8c1804b842b8
BugcheckParameter1 0xffff8c1804b842b8
BugcheckParameter2 0x8a00000000102121
BugcheckParameter2 0x8a00000000102121
BugcheckParameter3 0xfffffa846ab4ea40
BugcheckParameter3 0xfffffa846ab4ea40
BugcheckParameter4 0xa
BugcheckParameter4 0xa
SleepInProgress 0
SleepInProgress 0
PowerButtonTimestamp 0
PowerButtonTimestamp 0
BootAppStatus 0
BootAppStatus 0
Checkpoint 0
Checkpoint 0
ConnectedStandbyInProgress false
ConnectedStandbyInProgress false
SystemSleepTransitionsToOn 0
SystemSleepTransitionsToOn 0
CsEntryScenarioInstanceId 0
CsEntryScenarioInstanceId 0
BugcheckInfoFromEFI false
BugcheckInfoFromEFI false
CheckpointStatus 0
CheckpointStatus 0
CsEntryScenarioInstanceIdV2 0
CsEntryScenarioInstanceIdV2 0
LongPowerButtonPressDetected false
LongPowerButtonPressDetected false
LidReliability false
LidReliability false
InputSuppressionState 0
InputSuppressionState 0
PowerButtonSuppressionState 0
PowerButtonSuppressionState 0
LidState 3
LidState 3
WHEABootErrorCount 0
WHEABootErrorCount 0
Windows for home | Windows 11 | Performance and system failures

3 answers

Sort by: Most helpful
Most helpful Newest Oldest
  1. David-M 111.8K Reputation points Independent Advisor
    2026-03-13T16:20:46.13+00:00

    Thanks.

    One minidump file doesn't mention drivers, only a generic system file. The other, however, mentions an AMD RAID driver as the cause of the crash.

    I suggest doing the following:

    Go to the Gigabyte website using the link below, download the suggested drivers, and install them.

    https://www.aorus.com/pt-br/motherboards/b550m-aorus-elite-rev-13/Support

    Driver 1: AMD RAID Utility

    Driver 2: AMD Chipset Driver

    (You will need to expand the SATA RAID/AHCI and Chipset categories to find the mentioned drivers.)

    (Extract the ZIP file, and double-click the file setup to run the RAID driver installation. Then, follow the on-screen instructions to install the driver.)

    (Extract the ZIP file, and double-click the file mb_driver_597_chipset_5.11.02.217 to run the Chipset driver installation. Then, follow the on-screen instructions to install the driver.)

    Then, restart (not shutdown) your PC and see if the system will work stably.

    If the crash occurs again after doing this, please share the minidump it created.

    Feel free to ask any questions you may have.

    Standard Disclaimer: There is a link to a non-Microsoft website. The page appears to be providing accurate, safe information. Watch out for ads on the site that may advertise products frequently classified as a PUP (Potentially Unwanted Products). Thoroughly research any product advertised on the site before you decide to download and install it.

    Was this answer helpful?

  2. David-M 111.8K Reputation points Independent Advisor
    2026-03-13T13:29:32.0066667+00:00

    Hi. I'm David, and I'm happy to help you.

    This behavior can occur for several reasons. It is necessary to investigate.

    Please see if your computer created minidump files.

    These files are in C:\Windows\Minidump.

    (If you don't have a Minidump folder, check if it is in the plural Minidumps.)

    Copy any files you have to your desktop and store them in a ZIP file. Then, upload the ZIP file to the cloud (OneDrive), choose to share it, and get the link.

    Then, post the link to the ZIP file here so I can have a look.

    I await your reply.

    Was this answer helpful?

  3. Q&A Assist
    2026-03-13T12:56:43.7466667+00:00
    AI generated content. This question contains an answer created with AI from Q&A Assist. Learn more

    BugcheckCode 190 in Event ID 41 corresponds to bug check 0x000000BE (0xBE), which indicates a Stop error (blue screen) caused the restart. Event ID 41 is only a container for the bug check data; the real analysis is done using the bug check code and parameters.

    From the event data:

    • BugcheckCode: 190 → 0x000000BE
    • BugcheckParameter1: 0xffff8c1804b842b8
    • BugcheckParameter2: 0x8a00000000102121
    • BugcheckParameter3: 0xfffffa846ab4ea40
    • BugcheckParameter4: 0xa
    • SleepInProgress: 0
    • PowerButtonTimestamp: 0

    This means Windows crashed with a Stop error and then rebooted. To proceed:

    1. Convert and confirm the bug check code
      • Event ID 41 stores the bug check in decimal. The documentation shows how to convert it to hexadecimal (using Calculator in Programmer mode). For 190, the result is 0x000000BE.
      • After conversion, use the Bug Check Code Reference to look up 0x000000BE and see its specific meaning and typical causes.
    2. Collect and analyze the memory dump
      • Ensure the system is configured to write a dump file (typically using the pagefile). If there are issues like Event ID 46 from volmgr (Crash dump initialization failed! Crash dump initialization failed!), fix the pagefile configuration so future crashes generate dumps.
      • Once a dump exists, analyze it with WinDbg:
        • Open the dump in WinDbg.
        • Run !analyze -v to identify the faulting driver or module.
        • Use the bug check–specific documentation from the Bug Check Code Reference to interpret the parameters.
    3. Use the bug check documentation
      • After identifying 0x000000BE in the Bug Check Code Reference, follow its guidance (for example, checking for faulty or incompatible drivers, memory issues, or other kernel-mode components). The reference will describe what each parameter means and how to debug further.
      • For more general guidance on debugging kernel crashes, follow the “How to Debug Kernel Mode Blue Screen Crashes (for beginners)” article referenced from the Event ID 41 documentation.
    4. Check for hardware issues if no clear driver cause
      • If the bug check analysis does not clearly point to a driver, follow the hardware checks recommended for Event ID 41 scenarios:
        • Disable any overclocking and test at stock speeds.
        • Test system memory with a memory checker and verify all modules are correctly configured.
        • Verify the power supply is adequate and stable.
        • Check for overheating (CPU, GPU, VRMs) and ensure proper cooling.
    5. If Event ID 41 sometimes shows all zeros
      • If some Event ID 41 entries show BugcheckCode 0 and all parameters 0, and there is an accompanying volmgr Event ID 46, that indicates the system could not write the dump (for example, due to pagefile misconfiguration or very abrupt power loss). In that case, correct the dump/pagefile configuration so future crashes can be captured and analyzed.

    In summary, the Kernel-Power 41 (63) entry confirms that a Stop error 0x000000BE occurred. The next steps are to ensure dump creation works, analyze the dump with WinDbg using the Bug Check Code Reference, and then follow the driver or hardware remediation indicated by that analysis.

    References:

    Was this answer helpful?

Your answer

Answers can be marked as 'Accepted' by the question author and 'Recommended' by moderators, which helps users know the answer solved the author's problem.