Yes it could be an HW problem…why not…such a surprise, doesn’t this happen anymore in 2023/2024???
If you have no other clues or indications of any automatic action or user action that can lead to a FW corruption, then yes it can be a hw issue on the board… in this case model everything is soldered, ram, sdd, gpu… just a tiny solder sphere from any bga chip is enough.
There is sometimes a mislead ideia from users that everything that breaks its now, due to bios or vbios firmware corruption… and there is no more hardware failures.
I found after hours of searching burned transistor not far from Bios chip on this machine. So it is hardware problem. I got another surface pro 5 which has similar problem. Logo appear for few seconds. I will upload bios of this machine shortly. Thanks so much for help.
There’s one 0x1000 Block missing in the beginning of the second padding. But this padding does contain _FIT_ and there’s an additional error message about parsing ACM:
Thanks for working your magic. It is booting now. Windows up and running. All good!! This is attempt to fix my daughters Surface pro as she uses it for drawing with pen. Thankfully she kept backup of all her drawings. Now its back to life I just need to put it back together. You made her smile and we saved anoter MS product going to bin and polluting our planet Point is Surface Pro is a crap machine, another Mobo I tried to fix, with HW problem, I cannot even find replacement transistor which was burned. Shame. Anyway, your help is much appreciated.
I wonder why MS keeps everything twice (despite NVRAM) in bios region but doesn’t use it? Anyway, that really seems to be an erased but not rewritten block in this case.
Can we speculate what caused this issue? There should be some safety protocol in place when anything gets erased and boot fails last known working copy is used. PC mobos got two bios chips for this purpose. Surface being quiet expensive piece of hardware when new should be more fault proof. I don’t get it.
Hi there, I’m new to the forum and I also have some trouble with a Surface Pro 5. The problem is slightly different : lost touch capability after firmware update, but I think it might be related to this topic. I’m no expert for this kind of repair (I understand it’s not simple) but not a total newbie either (I was PHP developer before and like to manipulate electronics). I don’t want to waste anyone’s time, so my question is :
Could someone point me to a guide to repair the “firmware update” (or try to) or some kind of detailed steps so I can figure out where to start ?
Hello I’m new. I have an error with surface pro 5 M1007506-015 . The situation shows the window logo then turns off and the logo appears again then turns off continuously like that. I tried another bios, loaded it into the bios chip with ch341 and the window logo just stood still and nothing happened. Is it still a bios error or a hardware error? please help . would like to thank
Can you please look at this bios dump, the surface laptop 4 stays stuck on windows logo and does not boot / get into UEFI. Thanks SL4-original-v1.zip (6.2 MB)
Completely different machine. MS doesn’t provide a full firmware image. You dump contains 2 a 100% identical (redundant?) UEFI volumes, the proprietary AMD stuff in padding, and an a little messy NVRAM.
=> Sorry, nothing obvious in static parts, looks more lit hardware to me. You could try with empty NVRAM and see if / what it writes again into NVRAM when trying to start up but I foubt that will help you any farther.
Point is Surface Pro is a crap machine, another Mobo I tried to fix, with HW problem, I cannot even find replacement transistor which was burned. Shame. Anyway, your help is much appreciated.