I really need some help. My father sent me this Cyberpower Fangbook laptop that has a BIOS bug where it will not boot unless you press Delete and F10 to get to the BIOS screen. Then if you exit it, it boots. But now, due to windows auto updates, Windows wanted to restart itself, and it couldn't because of the BIOS issue. So it went into the endless starting auto repair loop. I tried doing a system restore from the recovery options, but even though it said the restore was successful, it went right back to not being able to restart because of the BIOS bug. I have tried booting from the cd drive. It just does the same thing. I don't know what to do to get it out of this loop. My father said the BIOS bug started after he tried to install Windows 10 on it and it failed to install. So he created this bug, I guess. I'm afraid to set the BIOS to factory defaults. I could totally brick it up doing that. I can get to a command prompt from the recovery options. What should I do? Is there a command line I can type in to fix it? I don't even know the tech specs because it happened so fast I never got the chance to really check the system out.
I got the model name from the BIOS. Marketing Name: Fang HD8970 Model: MS-176K
Cyberpower Fangbook Evo AFX7-800
OS is Windows 8.1
Raedon HD Graphics
Update: I think I fixed the BIOS bug, it's booting straight to the Recovery screen. The bad news is, it says it has a corrupt or missing boot file and needs repairs. But it insists the drive is locked every time I try with the recovery disk in the dvd drive. How do I unlock the drive when trying to repair from the dvd disc? The startup repair option fails. And it won't let me refresh or anything, just tells me to unlock the drive. I can get to a command prompt if there's a way to tell it to unlock it.
Update 2:
I ended up reinstalling Windows 8.1, but the BIOS bug is back. Basically, it boots to BIOS, pausing Windows boot cycle. If you press Delete twice, you get the BIOS. Press esc and tell it not to save changes, you boot to Windows. If you dare to tell the BIOS to save changes and restart, you break Windows boot cycle and end up in the endless Windows startup repair cycle and it locks the drive. That's how I accidentally killed the pc and bricked it. I can't fix the BIOS boot issue because resetting the drive letters seems to damage Windows boot boot files and then it's a dead drive stuck in the same repair loop. I'm not sure how to fix this BIOS boot without bricking it again. It's not a battery issue. A new battery was put in six months ago and the time is correct in the BIOS. If you unplug the power cord and boot from the battery, sometimes it will boot straight to Windows. So I don't know what's causing it. But it's a dangerous glitch to leave because it's one wrong move from bricking every time you or Windows restarts. I've tried different boot settings in BIOS, but nothing is fixing that. I'd appreciate some suggestions as to what to do. It's a pretty nice system, I'd hate to leave it or lose like this. But I wouldn't trust my work to it when it's doing this.
Operating System: Windows 8.1 64-bit (6.3, Build 9600) (9600.winblue_gdr.140221-1952)
Language: English (Regional Setting: English)
System Manufacturer: CYBERPOWER Corporation
System Model: FANG HD8970
BIOS: E176KACP.509
Processor: AMD A10-5750M APU with Radeon(tm) HD Graphics (4 CPUs), ~2.5GHz
Memory: 16384MB RAM
Available OS Memory: 15560MB RAM
Page File: 2467MB used, 16036MB available
Windows Dir: C:\Windows
DirectX Version: DirectX 11
DX Setup Parameters: Not found
User DPI Setting: 144 DPI (150 percent)
System DPI Setting: 96 DPI (100 percent)
DWM DPI Scaling: Enabled
DxDiag Version: 6.03.9600.16384 64bit Unicode
-------------
Sound Devices
-------------
Description: Speakers (Realtek High Definition Audio)
Default Sound Playback: Yes
Default Voice Playback: Yes
Hardware ID: HDAUDIO\FUNC_01&VEN_10EC&DEV_0892&SUBSYS_146210EF&REV_1003
Manufacturer ID: 1
Product ID: 100
Type: WDM
Driver Name: RTKVHD64.sys
Driver Version: 6.00.0001.7101 (English)
Disk & DVD/CD-ROM Drives
------------------------
Drive: C:
Free Space: 93.3 GB
Total Space: 120.1 GB
File System: NTFS
Model: SanDisk SSD U110 128GB
Drive: D:
Free Space: 866.3 GB
Total Space: 953.3 GB
File System: NTFS
Model: HGST HTS721010A9E630
Drive: E:
Model: HL-DT-ST DVDRAM GTA0N
Driver: c:\windows\system32\drivers\cdrom.sys, 6.03.9600.16384 (English)
SOLVED: So far, the real problem all this time was bad drivers trying to load at bootup. Windows kept reinstalling them and that's why I couldn't fix it and it took me days to figure it out. The auto updates are the worst thing they ever put on an OS. And I should have made a boot log first thing. I would have seen it immediately. Just one or more bad drivers loading at boot can kill a pc. It's fixed. I had to tell Windows updates to hide the bad updates and I did a format and clean install of Windows. No more boot problems.
I got the model name from the BIOS. Marketing Name: Fang HD8970 Model: MS-176K
Cyberpower Fangbook Evo AFX7-800
OS is Windows 8.1
Raedon HD Graphics
Update: I think I fixed the BIOS bug, it's booting straight to the Recovery screen. The bad news is, it says it has a corrupt or missing boot file and needs repairs. But it insists the drive is locked every time I try with the recovery disk in the dvd drive. How do I unlock the drive when trying to repair from the dvd disc? The startup repair option fails. And it won't let me refresh or anything, just tells me to unlock the drive. I can get to a command prompt if there's a way to tell it to unlock it.
Update 2:
I ended up reinstalling Windows 8.1, but the BIOS bug is back. Basically, it boots to BIOS, pausing Windows boot cycle. If you press Delete twice, you get the BIOS. Press esc and tell it not to save changes, you boot to Windows. If you dare to tell the BIOS to save changes and restart, you break Windows boot cycle and end up in the endless Windows startup repair cycle and it locks the drive. That's how I accidentally killed the pc and bricked it. I can't fix the BIOS boot issue because resetting the drive letters seems to damage Windows boot boot files and then it's a dead drive stuck in the same repair loop. I'm not sure how to fix this BIOS boot without bricking it again. It's not a battery issue. A new battery was put in six months ago and the time is correct in the BIOS. If you unplug the power cord and boot from the battery, sometimes it will boot straight to Windows. So I don't know what's causing it. But it's a dangerous glitch to leave because it's one wrong move from bricking every time you or Windows restarts. I've tried different boot settings in BIOS, but nothing is fixing that. I'd appreciate some suggestions as to what to do. It's a pretty nice system, I'd hate to leave it or lose like this. But I wouldn't trust my work to it when it's doing this.
Operating System: Windows 8.1 64-bit (6.3, Build 9600) (9600.winblue_gdr.140221-1952)
Language: English (Regional Setting: English)
System Manufacturer: CYBERPOWER Corporation
System Model: FANG HD8970
BIOS: E176KACP.509
Processor: AMD A10-5750M APU with Radeon(tm) HD Graphics (4 CPUs), ~2.5GHz
Memory: 16384MB RAM
Available OS Memory: 15560MB RAM
Page File: 2467MB used, 16036MB available
Windows Dir: C:\Windows
DirectX Version: DirectX 11
DX Setup Parameters: Not found
User DPI Setting: 144 DPI (150 percent)
System DPI Setting: 96 DPI (100 percent)
DWM DPI Scaling: Enabled
DxDiag Version: 6.03.9600.16384 64bit Unicode
-------------
Sound Devices
-------------
Description: Speakers (Realtek High Definition Audio)
Default Sound Playback: Yes
Default Voice Playback: Yes
Hardware ID: HDAUDIO\FUNC_01&VEN_10EC&DEV_0892&SUBSYS_146210EF&REV_1003
Manufacturer ID: 1
Product ID: 100
Type: WDM
Driver Name: RTKVHD64.sys
Driver Version: 6.00.0001.7101 (English)
Disk & DVD/CD-ROM Drives
------------------------
Drive: C:
Free Space: 93.3 GB
Total Space: 120.1 GB
File System: NTFS
Model: SanDisk SSD U110 128GB
Drive: D:
Free Space: 866.3 GB
Total Space: 953.3 GB
File System: NTFS
Model: HGST HTS721010A9E630
Drive: E:
Model: HL-DT-ST DVDRAM GTA0N
Driver: c:\windows\system32\drivers\cdrom.sys, 6.03.9600.16384 (English)
SOLVED: So far, the real problem all this time was bad drivers trying to load at bootup. Windows kept reinstalling them and that's why I couldn't fix it and it took me days to figure it out. The auto updates are the worst thing they ever put on an OS. And I should have made a boot log first thing. I would have seen it immediately. Just one or more bad drivers loading at boot can kill a pc. It's fixed. I had to tell Windows updates to hide the bad updates and I did a format and clean install of Windows. No more boot problems.
Last edited:
My Computer
System One
-
- OS
- Win 8.1
- Computer type
- PC/Desktop
- System Manufacturer/Model
- Lenovo
- Memory
- 4GB
- Browser
- Firefox
- Antivirus
- AVG