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.
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.
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.
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.
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.
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.
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.
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.
Just to confirm; i haven’t seen the problem once since swapping the memory. So i recommend not using the Kingston KF556S40IBK2-32 (kit of 2x 16GB) and maybe also the other kits from the same range in the Framework 13 Core Ultra.