Solved Event41 Kernel Power error fix

So if I play a game like R6 or Minecraft, I won't have any problems, but if I play something like Battlefield 1 or Warzone, my computer will randomly stop displaying and restart. How do I fix this?

SPECS: https://uk.pcpartpicker.com/list/nW9hh3

Here is a report from Event Viewer

Log Name: System

Source: Microsoft-Windows-Kernel-Power

Date: 8/7/2024 12:47:45 AM

Event ID: 41

Task Category: (63)

Level: Critical

Keywords: (70368744177664),(2)

User: SYSTEM

Computer: SeansPC

Description:

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

Event Xml:

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

<Level>1</Level>

<Task>63</Task>

<Opcode>0</Opcode>

<Keywords>0x8000400000000002</Keywords>

<TimeCreated SystemTime="2024-08-07T04:47:45.2799547Z" />

<EventRecordID>5369</EventRecordID>

<Correlation />

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

<Channel>System</Channel>

<Computer>SeansPC</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">16</Data>

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

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

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

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

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

<Data Name="CsEntryScenarioInstanceIdV2">6</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>

</EventData>

</Event>

Thanks for the live kernel reports in addition to V2 log files.

The computer has been having GPU problems (18 bugchecks in the past 30 days with one BSOD).

A similar thread was seen.

Please use just one forum to avoid or reduce any confusion.

zbook said:

Thanks for the live kernel reports in addition to V2 log files.

The computer has been having GPU problems (18 bugchecks in the past 30 days with one BSOD).

A similar thread was seen.

Please use just one forum to avoid or reduce any confusion.

Click to expand...

My GPU is still eligible for a return through Amazon since it hasn't been 30 days since I bought it. Should I return it and get a new RX6800? I ask this because if you scroll to the bottom of a kernel dump then it says "FriendlyEventName=Hardware error." and also "ReportDescription=A problem with your hardware caused Windows to stop working correctly."

Live kernel events are recorded as hardware events.

It is nomenclature / recording.

Live kernel events are recorded when Windows recovers without an unexpected shutdown.

zbook said:

Code:

Microsoft definition:  A kernel live dump is effective for a category of problems where something is taking a long time, and yet nothing is technically failing.

Live kernel events are recorded as hardware events.

It is nomenclature / recording.

Live kernel events are recorded when Windows recovers without an unexpected shutdown.

Click to expand...

So a new GPU wouldn't do anything?

Please close this thread and use one forum (thread etiquette).


It's usually useful to identify software versus hardware problems, keeping in mind warranty time periods.

Once you've eliminated software problems then move to hardware.

Hardware testing and replacement may require fees for postage, restocking, etc.

There could be other causes of GPU problems with a normally functioning GPU.

For example drivers, GPU port, motherboard, etc.


Please close this thread and use one thread (thread etiquette).