Перейти к основному содержанию

Repair and disassembly information for HP 15 Laptop PCs, specifically 15-ef models. The HP 15-ef is a budget laptop series featuring 15.6-inch touchscreen displays, AMD processors, DDR4 memory, and solid-state storage. Identified by model numbers starting with 15-ef.

Вопросов 2 Показать все

Computer freezes at slightest movement.

I have a problem with my laptop that sometimes it freezes at the slightest movement. The Model is a "HP Laptop 15-ef0020ca (12C25UA)". This has been going on for a long time and I still haven't found a solution. It is inconsistent with when it happens but it seems to stay in this highly sensitive state for a period of time before fixing itself. Last time this happens there was a single frame where the screen had a glitched line on a black screen before staying at a black screen. After that, it becomes unresponsive and I am forced to hold the power button to shut it down. Usually after this happens it freezes on boot up and I am then again forced to shut it down, followed by it freezing again at the same spot, and the 3rd time it freezes while windows is trying to diagnose the problem. This repeats until it decides to start working again, or sometimes, it boots up successfully but pressing any key will crash it. I checked the event viewer and it seems to be a power issue with the kernel. Here is what info it told me,

- <Event xmlns="***http://schemas.microsoft.com/win/2004/08...>

- <System>

  <Provider Name="Microsoft-Windows-Kernel-Power" Guid="{331c3b3a-2005-44c2-ac5e-77220c37d6b4}" />

  <EventID>41</EventID>

  <Version>8</Version>

  <Level>1</Level>

  <Task>63</Task>

  <Opcode>0</Opcode>

  <Keywords>0x8000400000000002</Keywords>

  <TimeCreated SystemTime="2024-09-16T18:15:02.3463320Z" />

  <EventRecordID>101738</EventRecordID>

  <Correlation />

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

  <Channel>System</Channel>

  <Computer>LAPTOP-ER33I967</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>

  </EventData>

  </Event>

I've tried multiple diagnostic tools and they all come back good. I've also tried /sfc scan and it did find some corrupted files that I think were due to the system crashing. I've opened up the laptop to have a look and I remember that the ram sticks are not the same. I didn't check the power connections while it was open so maybe something there is the problem. If I forgot any information let me know.

Отвечено! Посмотреть ответ У меня та же проблема

Это хороший вопрос?

Оценка 0
Добавить комментарий

Ответов (1)

Выбранное решение

Very common cause of error. RAM must be matching pair or you are asking for trouble - timing issues, etc.

Try each of the RAM modules separately. Now it MAY work fine with both of them separately. In that case buy the twin of which ever one you can find. If not available purchase a new matching pair.

If that does not fix the problem try removing the NVMe SSD drive and just boot up into the BIOS.

The other thing is something is loose as you say ". . . sometimes it freezes at the slightest movement." Re-seat all components and cables slowly and gently.

Oh and Wagnard Tools has a diagnostic which checks

  1. Component Store against Windows Update Servers so must be online.
  2. Verifies and fixes any corruption in Windows against 1.) above.

You did mention corrupt files. Wagnard does a more thorough check than /sfc scan.

Let us know how it goes.

Был ли этот ответ полезен?

Оценка 2

2 Комментариев:

It started happening again last night and this afternoon just after 12pm. I replaced the ram like you suggested with a new pair I had on hand and it made it past the windows diagnosis screen. Maybe the problem solved itself again and will come back or maybe your answer actually worked. I'll try to keep you posted but I am considering it solved for now. Thanks so much.

из

@ali_h_repair Good to hear.

из

Добавить комментарий

Добавьте свой ответ

Ali H будет очень признателен(а).
Статистика просмотров:

За последние 24 час(ов): 0

За последние 7 дней: 2

За последние 30 дней: 9

За всё время: 47