Acer Predator Helios 300 PH315-54 crashes and reboots randomly after motherboard replacement

amnkr1905
amnkr1905 Member Posts: 6

Tinkerer

edited April 2023 in Predator Laptops

I have Acer Predator Helios 300 PH315-54 laptop. I recently got the motherboard replaced since it was not booting up. After the replacement, my laptop crashes on gaming and also sometimes reboots randomly. On checking in "Event Viewer", I can see the below event in the Critical section.

[Edited the thread to add model name]

Below is the detail for the above event.

Log Name:      System
Source: Microsoft-Windows-Kernel-Power
Date: 26-04-2023 21:56:07
Event ID: 41
Task Category: (63)
Level: Critical
Keywords: (70368744177664),(2)
User: SYSTEM
Computer: LAPTOP-8RNJOK06
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="2023-04-26T16:26:07.0551327Z" />
<EventRecordID>28301</EventRecordID>
<Correlation />
<Execution ProcessID="4" ThreadID="8" />
<Channel>System</Channel>
<Computer>LAPTOP-8RNJOK06</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">1</Data>
</EventData>
</Event>

On opening the details, the bugcheck code and PowerButtonTimestamp shows as 0.
Any idea on what maybe causing this issue?

Best Answer

  • amnkr1905
    amnkr1905 Member Posts: 6

    Tinkerer

    Answer ✓

    It was motherboard issue only. Got solved after getting this replaced again.

Answers

  • JackE
    JackE ACE Posts: 45,175 Trailblazer

    This suggests a battery failure. Try this.

    (1) Search 'cmd' in Windows start menu.
    (2) Right click command prompt near top of menu.
    (3) Click run as administrator.
    (4) Enter 'powercfg /batteryreport' at command prompt.
    (5) Then return to the desktop. Open file explorer.
    (6) Then search for' battery-report.html' in the c:\windows\system32\ sub-folder. Double-click to open it in the browser.
    (7) Post screenshot of the first part of the report if possible that compares design full charge capacity with its remaining full charge capacity.

    Jack E/NJ

  • amnkr1905
    amnkr1905 Member Posts: 6

    Tinkerer

    Answer ✓

    It was motherboard issue only. Got solved after getting this replaced again.

  • JackE
    JackE ACE Posts: 45,175 Trailblazer

    Very unusual. Did the service center identify the issue? For example, overheating? Manufacturing defect? Power surge? Motherboard chip failure?

    Jack E/NJ

  • amnkr1905
    amnkr1905 Member Posts: 6

    Tinkerer

    There was an overheating issue with the motherboard.

  • JackE
    JackE ACE Posts: 45,175 Trailblazer

    Then I suggest that you raise the laptop about an inch above a hard surface to promote better airflow in and out of the bottom and/or side vents, especially under heavy gaming loads. Avoid using a cooling pad since many actually block airflow proper airflow in and out of the case.

    Jack E/NJ