道友，请留步

Post-Code: 00 我是做 BIOS 5 年的 OEM 搬砖工。从上电到 OS 载入，这中间有无数离奇的技术细节。 打算在 X 聊聊： 1️⃣ 那些被屏蔽的 BIOS 选项 2️⃣ 性能调优与功耗墙真相 3️⃣ 底层工程师眼中的硬件世界 保持好奇，保持底层。Hello World!🤝 #BIOS #UEFI #Hardware #工程师

@Daniel_Rubino 有另外一个2280规格的硬盘位吗

I finally have this review coming soon, but Dell's 2026 XPS 14 is quite possibly the best laptop I've ever used. Love the keyboard, touchpad, build quality, design, and this is the tandem OLED model with Intel Core Ultra X7 358H, 23GB, and 1TB SSD, which is 🔥 The only thing I could think would be better is the 16-inch, which I'm actually glad omits NVIDIA this time. Battery life for that config is waaay better than I would have thought (I also have the full HD IPS one, too). Anyway, if you have any questions for me for the review, thread 'em here.

@bdam555 @juergkoller But this requires OEM manufacturers to build their own servers.

@bdam555 @juergkoller Now there is also a way to update bios through the network under setup.

It’s 2026, and BIOS and firmware updates are still a pain. #Autopatch was a good idea, but unfortunately it takes forever for new BIOS versions to become available. Here’s an example for an EliteBook 860 G11. Now that everyone needs to be running the latest BIOS versions due to the #UEFICA2023 issue, it would be nice if it didn’t take seven months for new versions to become available in #WindowsUpdate. @ariaupdated @dan_felman @bytenerd @bdam555

Haha—speaking from my own experience—when a company is still relatively small, they typically don't actually give much thought to these kinds of things. It's only once they reach a certain scale, or encounter a wave of mass after-sales issues, that they truly start to take them seriously.

@Reset_Vector @juergkoller Right, but I _suspect_ this is similar to MSIX: technically clean solution, but with certain limitations. So, if OEMs have to do a bunch of extra work that limits their capabilities and only works for a singular update channel that isn't their own tools; the appetite is lower.

@chandlerblv @R3000C Indeed, this requires a case-by-case discussion; however, it is undeniable that even Intel's NUCs utilize AMI BIOS. (Laughs)

@Reset_Vector @R3000C It’s a yes and a no at the same time. Let's just say it depends on the project—I'm sure you catch my drift😁

個人的にWi-Fiルーターで選んでるのはASUS。 昔からPC向けマザーのBIOSやUEFIを作ってるとこは、他より信用できるだろうとの考えから。 セキュリティ的にも非常にクリティカルなソフトウェアの開発を長年やってる実績がある訳で、自前で相当やれる技術力、開発力、ソフトウェア資産があると期待して。

@bdam555 @juergkoller Indeed, I also believe that the "Capsule Update" feature is essential—not only for end users but also for OEMs, as it offers them significant benefits. All reputable OEMs should integrate with the Windows Update (WU) channel.

@Reset_Vector @juergkoller I can try and dig into this more, but my high-level understanding is that Capsule drivers are necessary to deliver an update that can safely install a BIOS update without triggering a BL prompt. However, capsule drivers are non-trivial and only apply to WU; so adoption is spotty.

@chandlerblv @R3000C Strictly speaking, IBV (AMI) provides a CRB-based BIOS; however, major PC manufacturers—such as Lenovo, ASUS, HP, and others—each possess their own unique features, a significant portion of which are developed in-house by these PC vendors themselves.

@R3000C みんな勘違いしてるけど、BIOS/UEFIを作ってるのはASUSではなくてBIOS Vendor(AMIとか)なんや。ASUSがやっとるのはあくまでもカスタマイズで、ASUS社内でカスタマイズしないでBIOS Vendor側でカスタマイズしてもらってるケースまである。開発をしてるのとパラメータいじってるのとは話が異なるんす。

@juergkoller @bdam555 Updating via Windows Update isn't difficult, but the headache is that the old BIOS on many machines simply doesn't support WU.

@bdam555 How hard can it be... Right now, there are millions of Windows devices that can't install the UEFI CA 2023 certificates because of outdated firmware versions, and many organizations aren't even aware of the problem.

@9550pro It's more like bios or microcode identification error.

The user purchased the 250K PLUS, but it displays as 270K PLUS. chiphell.com/thread-2795824…

@luciacrabs Maybe you can configure a full dump. When the next exception occurs, check whether memory.dmp is generated under C\windows. It can help you judge what caused the anomaly.

my computer just restarted completely again. 👍🏻 for no apparent reason. no lag leading up to it. just, “ran into a problem.”

国产适配的路确实难。目前内存价格疯涨，项目上不得不跑不在 AVL 里的颗粒，这对 OEM 来说是常态也是挑战。 核心 MRC 虽是原厂黑盒，但 BIOS 必须在受限的参数里找生路。反复尝试各种 ODT 配置、抓 Log ，用这种“穷举式调优”去填硬件兼容性的坑。 #UEFI #BIOS #国产芯片 #DDR5

5/5【国产芯片】 直到原厂补上适配逻辑，那条 16G 内存终于不再报错，开机也从“掉电重练 4 分钟”回到了 10s 秒亮。这一刻我才确定，那几千行 Log 没白抓。国产芯片的崛起不是宏大叙事，而是原厂与 OEM 工程师在无数深夜死磕出来的。我是 ResetVector，你经历过这种折磨吗？评论区见。🚀

4/5【改代码 2 分钟，开机 4 分钟】 开了 Debug 后，效率低到离谱：改代码 2 分钟，编译 5 分钟，开机又是 4 分钟+。一天下来大半时间都在等开机。由于算法封在原厂二进制里，我们只能抓 Log 甩给原厂。每天刷邮箱等救命的 PI 包，这种命门被攥在别人手里的焦虑，才是 BIOS 开发最深的阴影。

1/5【死亡代码：16G 内存的噩梦】 你见过让 BIOS 工程师绝望的代码吗？这是我做某国产 CPU 项目时的真实 Log：插 8G 勉强能亮，换成同型号 16G 直接卡死在 POST CODE: 0xEE00000A。满屏 DQErr 和 Assert，这种全世界静止的无力感，是底层人的噩梦。

@InternetTag 请问支持补差价升级套餐吗