Share via

Computer keeps crashing randomly, Event ID:41 Task Category:(63)

Camrun 0 Reputation points
2026-06-09T23:38:15.32+00:00

My desktop keeps crashing randomly and I am hoping to finally put this issue to rest because it has become quite infuriating. Any help is appreciated.

Log Name: System

Source: Kernel-Power

Event ID: 41

Level: Critical

User: SYSTEM

Keywords: (70368744177664),(2)

Windows for home | Windows 11 | Performance and system failures
0 comments

7 answers

Sort by: Most helpful
Most helpful Newest Oldest
  1. Lester Bernard Reyes 81,845 Reputation points Independent Advisor
    2026-06-10T00:18:09.2366667+00:00

    Hi, I'm Bernard. I'm happy to help!

    Can you upload and share the System logs on your PC so I can further examine the root cause of the issue?

     

    To share the System logs, please follow the steps in the link below:

     

    Press the Windows key + X, then select "Event Viewer"

    Click the drop-down of "Windows logs"

    Right-click System > click Filter Current logs > Check: Critical, Warning, and Error > Hit OK

    On the right pane, click "Save Filtered Log File As..."

    Save the System logs file to your desktop and share it by following the steps from the link:

    https://support.microsoft.com/en-us/office/share-onedrive-files-and-folders-9fcc2f7d-de0c-4cec-93b0-a82024800c07

     

    Note: You can also use your preferred cloud storage to upload and share the logs.

    Note: This is a public forum. I may respond shortly, but I apologize in advance for any delays. I am simply a fellow user trying to provide helpful insights and information.

    Was this answer helpful?

    2 people found this answer helpful.
  2. Lester Bernard Reyes 81,845 Reputation points Independent Advisor
    2026-06-10T00:52:21.4466667+00:00

    Perfect! Kindly upload and share the logs so I can further check the issue.

    Was this answer helpful?

    1 person found this answer helpful.
  3. Lester Bernard Reyes 81,845 Reputation points Independent Advisor
    2026-06-10T16:07:12.7+00:00

    Hi, thank you for patiently waiting. As per checking and analyzing the event logs, there are multiple WLAN-AutoConfig warnings on the PC, this means there is an error with the Intel Wireless driver on the PC. To sort out the issue, kindly follow the steps below:

    First, what we will do is enable WWAN and WLAN services. These services are essential to run the Wireless and wired connections perfectly.

    Open Services (Press Windows key + R, then type in services.msc then click OK)

    Look for WLAN Autoconfig and WWAN Autoconfig> Right-Click Properties and set it to automatic (If it's already set to automatic, right-click, then click stop, then start it again)

    Restart the PC and check

    If the issue persists, run the following command in Terminal (Admin). Follow the steps below to do so.

    These sets of commands will reset the internet connection and recalibrate the internet settings you have.

    Press Windows Key + X.

    Click on Terminal (Admin).

    Type the following commands, and hit Enter after each command:

    netsh int tcp set heuristics disabled
netsh int tcp set global autotuninglevel=disabled
netsh int tcp set global rss=enabled
netsh winsock reset
netsh int ip reset
ipconfig /release
ipconfig /renew
ipconfig /flushdns

    Restart the PC and check.

    Method 3. Do a clean boot:

    A “clean boot” starts Windows with a minimal set of drivers and startup programs so that you can determine whether a background program is interfering with your game or program.

    • In the search box on the taskbar, type msconfig and select System Configuration from the results.
    • On the Services tab of System Configuration, select Hide all Microsoft services, and then select Disable all.
    • On the Startup tab of System Configuration, select Open Task Manager.
    • Under Startup in Task Manager, for each startup item, select the item and then select Disable.
    • Close Task Manager.
    • On the Startup tab of System Configuration, select OK. When you restart the computer, it's in a clean boot environment.

    Troubleshooting reference: https://support.microsoft.com/en-us/topic/how-to-perform-a-clean-boot-in-windows-da2f9573-6eec-00ad-2f8a-a97a1807f3dd

    Was this answer helpful?

  4. Lester Bernard Reyes 81,845 Reputation points Independent Advisor
    2026-06-10T00:14:32.69+00:00

    Hi, I'm Bernard. I'm happy to help!

    Can you upload and share the System logs on your PC so I can further examine the root cause of the issue?

     

    To share the System logs, please follow the steps in the link below:

     

    Press the Windows key + X, then select "Event Viewer"

    Click the drop-down of "Windows logs"

    Right-click System > click Filter Current logs > Check: Critical, Warning, and Error > Hit OK

    On the right pane, click "Save Filtered Log File As..."

    Save the System logs file to your desktop and share it by following the steps from the link:

    https://support.microsoft.com/en-us/office/share-onedrive-files-and-folders-9fcc2f7d-de0c-4cec-93b0-a82024800c07

     

    Note: You can also use your preferred cloud storage to upload and share the logs.

    Note: This is a public forum. I may respond shortly, but I apologize in advance for any delays. I am simply a fellow user trying to provide helpful insights and information.

    Was this answer helpful?

    0 comments

  5. AI answer

    2026-06-09T23:38:51.28+00:00

    Event ID 41 (Kernel-Power) means Windows detected that the system was not shut down cleanly. It does not by itself identify the exact cause, but it indicates one of these general categories:

    1. Power loss or forced power-off
    • Sudden loss of power (unplugging, power outage, drained laptop battery, faulty PSU) causes Windows to log Event ID 41 on the next boot.
    • Pressing and holding the power button to force a shutdown or restart also leads to Event ID 41. In this case, the event typically has a nonzero PowerButtonTimestamp value.
    1. Stop error (blue screen) or system hang
    • If the system hits a Stop error (BSOD) and restarts, Windows logs Event ID 41 and, when possible, includes a bug check (Stop) code in the event data.
    • If the system hangs (hard freeze) and must be powered off, or if it restarts so quickly that it cannot write error codes or a dump file, Event ID 41 may:
      • Not be recorded at all, or
      • Be recorded with BugcheckCode and PowerButtonTimestamp equal to 0.
    1. Hardware or configuration issues When Event ID 41 appears with no useful bug check data (BugcheckCode = 0), the documentation highlights typical hardware-related causes:
    • Underpowered or faulty power supply (desktop PSU, or drained/removed battery on laptops).
    • Power interruptions (power outages, loose power cable, faulty power strip/UPS).
    • Overclocking (CPU, GPU, or RAM) causing instability.
    • Faulty or misconfigured RAM.
    • Overheating components.
    • In virtualized environments, automatic restart by heartbeat/cluster mechanisms.

    Recommended troubleshooting path

    1. Check if there is a Stop (bug check) code
    • Open Event Viewer → Windows Logs → System → find the Event ID 41 entry.
    • Inspect the event details:
      • If BugcheckCode is nonzero, convert it to hexadecimal and use it to troubleshoot the specific Stop error using the bug check references.
      • If BugcheckCode is 0 and PowerButtonTimestamp is 0, suspect power or hardware issues.
    1. Correlate with other events
    • Look for related events around the same time:
      • Event ID 6008 (unexpected shutdown) and 6006 (clean shutdown) to see if shutdowns are dirty or clean.
      • Event ID 1074 (User32) to see if any shutdowns were initiated by software or a user.
      • Event ID 46 from volmgr (“Crash dump initialization failed!”) indicating dump configuration/pagefile issues.
    1. If there is no bug check code (or it is 0) The official guidance for this scenario is to focus on hardware and power:
    • Disable any overclocking and run the system at stock speeds.
    • Check memory:
      • Ensure all RAM modules are correctly seated and configured.
      • Verify all modules run at the same supported speed.
    • Check the power supply:
      • Confirm the PSU has sufficient wattage for CPU, GPU, drives, and peripherals.
      • If power outages or brownouts are possible, consider using a UPS.
    • Check for overheating:
      • Monitor internal temperatures and ensure fans and heatsinks are clean and working.
    • If running in a virtual machine:
      • Check Hyper-V or other hypervisor heartbeat/cluster settings that might restart an unresponsive VM.
    1. If a Stop error is visible on screen but not in Event ID 41
    • Disable automatic restart on system failure so the BSOD remains visible and the bug check code can be captured:
      • System Properties → Advanced system settings → Advanced → Startup and Recovery → Settings → clear “Automatically restart”.
    1. Clean up repeated dirty shutdown tracking (optional)
    • Windows tracks dirty shutdowns in the Reliability registry key. Clearing values like DirtyShutdown, LastAliveStamp, and TimeStampInterval under HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Reliability can prevent repeated Shutdown Event Tracker prompts after unexpected shutdowns.

    In summary, Event ID 41 indicates that the system is not shutting down cleanly. To resolve random crashes, correlate Event ID 41 with bug check codes and other events, then systematically check for Stop errors, power issues, overclocking, RAM problems, and overheating as described above.

    References:

    AI-generated content may be incorrect. Read our transparency notes for more information.

    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.