Brand new Framework 13 AMD 7040 DIY — no display, no fan, nothing

Community Support
, ,
1

Hey everyone. Just received my brand new Framework 13 AMD Ryzen 7040 DIY edition and I can’t get a display on first boot. I’ve already opened a support ticket but wanted to post here in case anyone has seen this before.

My build:

  • Framework 13 AMD Ryzen 7040

  • Kingston Fury Impact DDR5 5600MT/s 2x16GB

  • 1TB SN7100 NVMe SSD

Symptoms:

  • No display output at any point, screen completely black, no backlight

  • No fan activity

  • Never booted before, brand new out of box

Blink sequence:

  • 12 green blinks (all passing)

  • Then POST code sequence: GBBGGGBG

  • Then slow repeating red blinks

What I’ve tried:

  • Reseated RAM multiple times

  • Tested each stick individually in both slots

  • Chassis intrusion switch reset x10

  • Power drain method (battery disconnected, SW1 held 30 seconds, 15 minute wait)

Has anyone seen this before?

Thanks for your help!

2

Sorry to hear. Is your powersource at least 60W and plugged directly to a wall outlet? Tried a different charger with 60W or greater? You can also try disconnecting the battery, and plugging in the charger to see if it boots that way.

3

This did not solve it… but when I had it open I decided to retry each stick in each slot. And one stick it does work. That same stick can work in either slot. I guess the other one is bad.

I ordered some new RAM, hoping that once that gets here I can have the full 32GB!

Will update here if the new sticks solve the problem once they get here (yay Amazon 1 day).

1 Like
4

Oh wow, sucks about the RAM but good to know it’s not the motherboard!

Disregard*: I looked up your RAM make/model, and it looks like it uses Intel XMP 3.0. Per Framework’s FAQ, “We recommend avoiding XMP DDR5.” I wonder if this is related somehow?

*Correction: That ONLY affects the Ryzen AI 300 series of laptops, NOT your AMD Ryzen 7040.

5

Its all good. I got some crucial sticks on the way!

6

The crucial sticks work. Apparently it was one bad stick that I happened to try both times.

7

Just so it is clear to others that come across this. The Kingston Fury DDR5-5600 ram has been known to cause issues with AMD mainboards. It is something with the sub timing is the best guess as to what caused it to not POST. Great that one stick worked but that model of memory is known to have issues with Framework AMD mainboards.

1 Like
8

@pkunk
To add to your message about Kingston Fury RAM and AMD mainboards.
The Kingston Fury is OK with 7040 Series AMD mainboards, but is not so successful on the AI 300 series AMD mainboards.

1 Like
9

Maybe the 13" mainboards. The Framework Laptop 16 has had many threads of memory not working and they almost all had Kensington Fury DDR5-5600Mhz memory.

Possibly it has to do with the slower timing of the 13" board compared to the 16" mainboard? That would help align with it being just slightly out of whatever spec the board is expecting front the memory though it is not performing as expected and causes system hang.

10

Return and refund both Kingston sticks, RAM works in pair for dual channel, use Crucial for both slots

11

Not sure if this helps, but on my very first out-of-the-box boot the screen stayed black for about a whole minute until I even came to the Framework logo. But for me it was a one time event.

12

Hi @Alex_H,

This is standard practice on all newer generation AMD devices when new or different memory configurations are installed on the device. The board goes through a memory training to learn the new configuration and can take up to a few minutes though this is a one-time process until the configuration changes again.

This is not just for Framework, but all newer generation boards that use AMD processors (desktop and laptop).