Nov 14, 2016  I have managed to get my U410 back to the 65cn21ww BIOS Contrary to the warnings not to install a BIOS that you are not absolutely sure is for you computer I installed the 65cn13ww BIOS and as the warnings say the computer was almost bricked It wouldn't boot the installed Windows 8.1 or much of anything and just give me a black, unresponsive screen after showing the Lenovo logo. Dec 23, 2010 - [Resolved] Cannot update the BIOS of Dell Inspiron E1405 from A03 to. An unexpected error occurred while running the Flash application.

Ok so I have a Dell Inspiron 17 7720 laptop that had a bad mother board.I replaced it with another one and all works fine now. I installed Windows 10 Pro and noticed that I get my screen flashing on so I went to the dell Website to make sure I have all the right drivers. It recommended a few updates and also showed A17 BIOS that could be used also. I downloaded the files and then tried to do the flash bios program and got the above error. Found software PC Scan and repaitr that was recommended and it did not resolve any issues, instead found some malware and wants my CC card to repair software errors (not happening).

Prodam blank stvola pm 2. So my issues are flashing screen which I did not have with Lunix Mint and the command line error when trying to upgrade my BIOS.

Hello, So as it says in the title i have a 4 years old Inspiron 7720, and for the larger portion of that period of time it worked like a charm. However lately it started doing some quirky things. About two weeks ago my GPU (GeForce GT 650M) just disappeared from my Device Manager. I tried updating my GPU drivers, updating Windows (10) but it didn't seem to change anything. So i did some digging and found this: Apparently I'm not the only one who encounterd this problem and there is a solution. HOWEVER, whenever I try to flash my BIOS an error pops up which reads: 'ERROR 105 - Command line error!

Status = 105.' I searched and found more users that experienced this problem, but the only solution I managed to find was reinstalling the OS, which is quite a drastic measure. Is there any other way to fix this error?