Kernel-power Critical Error 41 - Keywords: 0x8000400000000002

Anonymous
2024-07-03T11:50:17+00:00

Hi,

Hope all is good, thanks for any help in advance & that this is the right place to send  this post. If not pls advise ....

We have 3x RDS servers (1x broker / gateway, 2x session servers where the session are load balanced too by the broker).

The 2x sessions server keep on randomly crashing and rebooting - multiple times a day and we see a Kernel-Power EventID 411 and would like to / need assistance to figure out why they are constantly crashing.....

Error General details:

The system has rebooted without cleanly shutting down first. This error could be caused if the system stopped responding, crashed, or lost power unexpectedly.

unsure if this is necessary:

Task Category: (63)

Keywords: (70368744177664),(2)

Details are:

  • System
    • Provider
    [ Name] Microsoft-Windows-Kernel-Power [ Guid] {331c3b3a-2005-44c2-ac5e-77220c37d6b4} EventID 41 Version 6 Level 1 Task 63 Opcode 0 Keywords 0x8000400000000002
    • TimeCreated
    [ SystemTime] 2024-07-03T10:56:47.240695800Z EventRecordID 500193 Correlation
    • Execution
    [ ProcessID] 4 [ ThreadID] 8 Channel System Computer <Computername>
    • Security
    [ UserID] S-1-5-18
  • 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 false CheckpointStatus 0

can anyone asssits pls to check why it keeps on happening?

Bit more setup background:

The server run 2x main apps (Office & 3rd party - Merit - app that worked no issues) and dynamic user disks are setup in this environment...

This all started after an issue we had with the vendor platform and we had to restore all servers from backup .....

The system details of this particular machine that the error above is from are:

Vendor Virtuozzo Model OpenStack ComputeMotherboard N/ABIOS manufacturer SeaBIOSBIOS version Default System BIOSBIOS version date 2014-03-31T23:00:00 Processor AMD EPYC Processor (with IBPB)Memory 64 GBVideo card Microsoft Basic Display AdapterSound N/A

OS edition Microsoft Windows Server 2019 Standard x64 OS version 1809OS build 17763.5933Office version Microsoft Office 365 ProPlus, Build 16.0.17726.20126

Any help, tips or assistance would be so much appreciated ....

Thanks and regards

Andre

Windows for business | Windows Server | User experience | Remote desktop services and terminal services

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. To protect privacy, user profiles for migrated questions are anonymized.

0 comments No comments
{count} votes
Accepted answer
  1. Anonymous
    2024-07-03T17:18:40+00:00

    Hello,

    Kernel-Power Event ID 41 errors usually indicate problems such as system overheating, driver problems, or hardware failures.

    Here are some steps you can take to troubleshoot the problem:

    1. Check the server hardware to ensure that the power supply to the server is stable and sufficient, and the operating temperature is within the normal range.
    2. Update drivers and firmware to ensure that all hardware drivers (especially those for networking and storage) are up to date.
    3. Users have reported that the quick-start feature may cause such problems. You can try to disable it by opening Control Panel > Power Options > Select Functions of the Power Button > Change Settings that are currently Unavailable. Uncheck Turn On Quick Launch and save your changes.
    4. Use the built-in Windows memory diagnostic tool CHKDSK to check for RAM problems, and run the SFC command to check for software conflicts and system file corruption.

    Right-click the Start button and select Command Prompt (Administrator) to bring up the promoted command prompt. At the command prompt, run the following commands:

    sfc /scannow

    chkdsk /f /r

    Then restart the computer

    If the problem persists, check the application log and system log in the event Viewer for further error messages. Please enable the options below before viewing.

    I hope this helps.

    Best regards

    0 comments No comments

0 additional answers

Sort by: Most helpful