Laptop Doesn't Power On Every Time, but Does Eventually

Does anyone else ever run into the issue referenced in the subject line?

My machine has never not powered on, but sometimes it takes a few soft resets to get it going. Thought it might have been a connection issue somewhere, so I disassembled and reassembled, but it still happens on occasion. It’s not even every time I start up the machine, just here and there.

Any thoughts?

Do you mean “get going” as in it boots into OS? If so which OS?
I had a similar issue with my work laptop where I had to force Windows to do a full shutdown or force it to power off a couple times.

Hi and welcome to the forum.

FernAnne asked the obvious, like which OS and do you have and have you/ could you try another.

You also give no info on which BIOS version you have.

Also you say powering on, but how do you power off. Hopefully not from sleep. ~ via the GUI, closing the lid, power button.

Have you disabled ‘fast startup’ in Win Power Option, which although sounds of some benefit actually stops proper new power on and then you have to do a restart via the gui to clear that each time.

YES. My AMD laptop has been having the same issue, I’ve been in talk with support right now to diagnose it but it seems to be an issue with the expansion cards. Cause if the cards aren’t slotted in then the failures to turn on don’t happen. And it doesn’t seem to matter which cards are inserted or where.

It’s windows, and yes that’s what I meant by get going. Sounds like Romero below has provided an explanation that makes sense given what I’ve troubleshooted and what they’re experiencing.

Thanks for this. Very interesting, I didn’t try to boot up without the cards slotted. Could you please let me know what support comes back with for a resolution?

Appreciate the checklist, but I of course covered the basics—OS, BIOS update, fast startup quirks. Pretty sure the issue goes deeper–not firmware or OS settings, like Romero points out below.

1 Like

I am experiencing the same issue, but on FW 13 Intel Core Ultra: AMD Framework 13 required multiple boot attempts before actually booting - #10 by James3 (see my replies in that topic).

I am already in contact with support and it seems to be related to the system memory i’m using, which i supplied myself. This the memory i’m using:

Kingston FURY Impact - DDR5 - kit - 32 GB: 2 x 16 GB - SO-DIMM 262-pin - 5600 MHz / PC5-44800 - CL40 - 1.1 V - unbuffered - on-die ECC

With 1 stick there’s no issue (doesn’t matter which stick). 2 sticks and i repeatedly have the issue. If i mix 1 stick with another test stick (4800 MHz even…) then there’s no problem also. I’m wondering which memory you are using?

For me OS, drive and BIOS all have been already ruled out as possible suspects. The memory seems to be compatible and i see it’s a popular choice in this forum, but regardless there seems to be something wrong with it or the combination.

1 Like

If it helps, I have a FW16 with 2x Kingston FURY Impact 32G - KF556S40-32
They work fine here. No power on problems. So similar RAM to @Mr.V, just different size.

2 Likes

I am advised by support to try other memory. They pointed to this page which lists compatible memory for FW 13 Core Ultra: What memory (DRAM) parts are compatible with the Framework Laptop? (Intel® Core™ Ultra Series 1)

My memory is listed, but as “limited validation”. So i have now ordered Framework’s own memory 2x 16GB to see if this fixes the issue. If it does i think it’s good if FW updates that page to warn other users of possible issues with that Kingston memory.

To be continued

Thanks, i think the difference might be that you are on AMD and i’m on Intel.

This is really helpful. Thank you for sharing.

I’m using two Samsung 8G - M425R1GB4PB0-CWM. When I remove one I can’t replicate the power issue, but when both are in I’m seeing the issue on every other startup attempt.

Think I’ll just pick a stick off the list with full validation and see if that does the trick.

1 Like

I have received the Framework branded memory (which is identified as A-Data by lshw). With this memory first results seem to indicate the problem is solved. But it will take some more time to be certain of this.

1 Like