声誉积分: 93.5千
307
278
152
I'm shooting from the hip on this one, but I've had the 840 G3, G5, and G6 and now a 640 G9, so thanks to Corporate America, I've had a few of these (I don't know which one it was, but one of them had an issue and was stupid cheap). I might be wrong or miss something critical.
Corrupted CMOS RAM settings cause this a lot of the time, and sometimes a corrupted BIOS—but generally, it's the CMOS RAM that has issues. If the BIOS was corrupted, the machines would automatically restore it from the shadow copy kept in secured address space on the backup EEPROM and very clearly notify you of a BIOS recovery event, even logging it in the BIOS. I very much doubt it's the BIOS here. Pull the primary battery connector (the G5 and up use a wire, the G1-G3 use a battery you physically have to remove), and the pigtail wire on the CMOS battery (there's no need to remove it from the chassis - just unplug it). Hold the power button for 30 seconds to clear the CMOS RAM, and plug the CMOS battery in and then the main battery. Plug the laptop into power if need be and wait ~1-5 minutes, it's normal for it to take a minute due to the BIOS flipping out when you do this and checking the signatures closely.
As soon as the BIOS passes, it will have you press Enter, and then it will go back to default settings. You might need to enter the BIOS and reset the clock but Win10 and Win11 generally will sync with the BIOS so this may not be needed.
I have also seen intermittently failing RAM cause a similar issue since these machines are very unforgiving about cheap RAM modules and when the RAM does fail or the integrity checks do not like it, they will often just flat out refuse to boot; but if the RAM works well enough, then it could fail in ways like this where new modules fix the issue.
这个答案有帮助吗？
过去 24 小时： 1
过去 7 天： 3
过去 30 天： 85
总计 85
6条评论
@kennyfx "switches off with a little notice on the screen" what little notice, what kind of flashing? What have you checked? What have you tried? What is the complete model number for your computer? Since we can't see or hear anything your computer does, we rely heavily on your skills to describe what is going on when you try to turn it on.
由 oldturkey03 完成的
@oldturkey03 That being said, it's probably something commonplace I've seen like corrupted CMOS RAM. But given I've had the G3 Skylake, G5 8th gen, a G6 I got (8th gen refresh, but it had 2 years of warranty for cheap) and now a 640 G9 (I wanted the Ethernet port, the 800 dropped it after G6; the 640/645 has the aluminum chassis AND ethernet port) I know these things - HP's Sure Start BIOSes will flip out and default them to factory settings if the BIOS signature checks out but the CMOS RAM is messed up, or pull from the backup BIOS ROM chip.
由 Nick 完成的
@nick yeah, my first thought was BIOS as well.
由 oldturkey03 完成的
@oldturkey03 The way it works is that full BIOS corruption freaks the machine out, triggers the backup BIOS restore with the known good shadow copy, and forces you to acknowledge it was done by default (you can disable that but really, I leave it on for obvious reasons) and creates the BIOS log I mentioned before. CMOS RAM corruption doesn't do that - it just tends to hang the machine up or forces a CMOS default if it's not so broken the machine can recover at POST.
You can tell a Sure Start BIOS restore from bad CMOS RAM settings, the difference is painfully obvious. Even someone who doesn't know this stuff due to experience can easily tell. The BIOS is super locked down on these (more then the Haswell-present Boot Guard standard affair) and the extra security can trip them up a bit more easily, especially given HP uses Boot Guard to enhance Sure Start.
由 Nick 完成的
@nick i took it to an engineer and he said it was BIOS
由 Kennyfxx 完成的
显示更多的1条评论