Please report all spam threads, posts and suspicious members. We receive spam notifications and will take immediate action!
Results 1 to 1 of 1

Thread: H170M-D3H No POST from main bios chip, how to recover?

  1. #1
    Join Date
    Feb 2009

    Exclamation H170M-D3H No POST from main bios chip, how to recover?

    An H170M-D3H with a custom firmware version (via Gigabyte's own toolkit, minimal alterations: PC Health max temps., enabling SATA ports, etc.) F5 in the main and backup BIOSes had utilized the Gigabyte Firmware Update utility, believing it to be an Intel M. E. I. firmware update utility. The software updated the system and rendered in non-POSTable. It had worked well for many months. It was a brand new installation of Windows 10 and a new S. S. D., which should have otherwise ruled out virus interference or any other type of problem during the flash. Had the understanding been it was a Windows-based automatic firmware updater, it would have been avoided. The damage is done.

    The computer will now start only if the power button is held until the system powers then shuts off (it would appear this boots from the backup BIOS). Normal startups do not beep or initialize the video. It would appear the GFU utility corrupted the main BIOS and flashed it to the new "unable to flash back to previous versions" Kaby Lake updates. It is unclear if incompatibility with previous versions or some other problem is causing the issue.

    I spent some time today attempting to flash backup to main and was unable to utilize any key combination to do so. Main to backup (CTRL+F10) would not function either (tested for reference). I was using a PS/2 keyboard. As this was unsuccessful, I would assume I can either: a) utilize a flash drive and a recovery flash via holding INS / CTRL+HOME / CTRL+PGUP or PGDN during power-on (IIRC), or b) same as (a) with a USB floppy drive, or c) some sort of pin short on the primary BIOS chip as documented on a few enthusiast sites (if someone is knowledgeable). It may be none of these will succeed as having attempted several combinations of CTRL+* with AMIBOOT.ROM on a flash drive did not yield results (the floppy is out as the firmware is much larger).

    At the present the system has a brand new Samsung 850 EVO drive and Windows 10 x64 installation and is unable to boot without the hold until on then off sequence completes. It would appear sleep or hibernation causes a deeper problem as attempting to wake the system tonight was met with complete lack of power until a CMOS clear was completed. Any suggestions are welcome. The assistance is appreciated.

    P. S. If the worst is feared I am willing to attempt something to the tune of these posts, if someone is familiar with the chips in these newer boards: How to fix "dead" dual BIOS motherboard if flashing failed
    Last edited by silekonn; 02-03-2017 at 04:04 PM.

Thread Information

Users Browsing this Thread

There are currently 1 users browsing this thread. (0 members and 1 guests)

Tags for this Thread

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts