Build related bios corruption? possible?  


  1. Posts : 129
    Windows 10
       #1

    Build related bios corruption? possible?


    Might be a coincidence but my laptop updated to 15327, soon afterwards it went to sleep. A couple of hours later I woke it up, got a black screen and 3 beeps over and over. Rebooted, same 3 beeps, black screen. I took it apart, removed the cmos battery, main battery and removed 1 stick of ram.
    I've had this issue before but never connected it to an update. To fix it I discovered that if I cycle the power numerous times with the cmos and laptop batteries removed the bios randomly catch and the machine would fire up but might not boot again for many, many power cycles. I was about to give up when it finally caught.
    I had put a ms-dos bootable memory stick with the bios file executable in a USB port. As soon as the Dell logo appeared I hit F12, from the boot menu I had to select legacy boot, to be able to boot from USB. It did, At the DOS prompt I ran the bios update file with the switch /forceit. The update went without a hitch. Then the laptop booted normally but on reboot it would try to boot from the network. I went into the bios and set the boot sequence back to windows boot manager and it's been working perfectly ever since.
    Before the bios corruption I noticed that I still didn't have news and interests on the taskbar. After I re-flashed the bios and as soon as it booted up I saw that news and interests had appeared. That made me wonder if the insider update had somehow corrupted the bios.
    My laptop is a Dell Inspiron 15z 5523. To create the bootable flash drive I followed # 2 in these instructions:
    https://www.dell.com/support/kbdoc/e...t-package-dddp
      My Computer


  2. Posts : 16,191
    Windows 10 Home x64 Version 22H2 Build 19045.3693
       #2
      My Computer


  3. Posts : 129
    Windows 10
    Thread Starter
       #3

    [QUOTE=Try3;2173445]Beeps during booting indicate hardware faults.
    True and hardware fault is what the Dell beep code list indicated. Is it possible that a corrupted bios could cause a false positive for failed hardware. Hard to imagine that a bios re-flash would fix faulty hardware. It's been working fine and took the 21332 update.
      My Computer


  4. Posts : 16,191
    Windows 10 Home x64 Version 22H2 Build 19045.3693
       #4

    The answer should be in the links I posted.

    Denis
      My Computer


  5. Posts : 13,321
    Win10 Version 22H2 Pro and Home, Win11 Pro and Home
       #5

    A comment, since the Operating System reads the BIOS settings during startup then Yes, a corruption in the BIOS can cause issues, usually with the Users settings available in it. Updating the BIOS frequently fixes such problems.
      My Computers


  6. Posts : 93
    Windows 10 pro 64 Bit Version 21H1 (OS Build 19043.844)
       #6

    Berton said:
    A comment, since the Operating System reads the BIOS settings during startup then Yes, a corruption in the BIOS can cause issues, usually with the Users settings available in it. Updating the BIOS frequently fixes such problems.
    Precisely. My roommate just built 4 PC for our house and one had the beep issue, it was a simple fix by updating the proper BIOS. But if updating your BIOS doesnt help and you still get beeps then I would look into using a Hardware diagnostic software to test whats going on. Check this post....
    5 best hardware diagnostic tools for PC [2021 Guide]
      My Computer


 

  Related Discussions
Our Sites
Site Links
About Us
Windows 10 Forums is an independent web site and has not been authorized, sponsored, or otherwise approved by Microsoft Corporation. "Windows 10" and related materials are trademarks of Microsoft Corp.

Designer Media Ltd
All times are GMT -5. The time now is 23:37.
Find Us




Windows 10 Forums