Gimp the Imp Pimp
[Esquire]
- Joined
- Sep 28, 2021
- Messages
- 2
Hi there.
I have a P67A-GD65(B3) with a i7-2600K@4.4GHz, 16GB@1600MHz in three sticks (4+8+4 configuration), and a RX580(4GB). Been running this configuration ROCK-SOLID with the beta BIOS 4.43 for 12 months, and for 6 years before that with the i7@4.3GHz, 8GB@1600MHz (4+4), and a HD6850(1GB). The extremely rare BSOD were mainly due to some USB/External HDD cock-up. Never had one while playing games (or rather, one HW related) or encoding H.264 videos, with CPU/RAM at 100%, for hours.
Yesterday, when I was (admittedly) doing things I shouldn't be doing (messing with the BCD settings of my dual-boot/dual-SSD PC, which locked me off both), during one of the reboots it made a couple of tries (like the ones when trying new OC parameters, although I wasn't changing anything in the BIOS except boot settings) and I couldn't get the screen to turn-on. Everything was spinning fine but no Windows, no USB drive and no BIOS/Setup. Only when I removed the case panel to start unplugging/removing/switching stuff and saw the steady blinking blue LED I realized what happened: primary BIOS failure.
What I didn't realized though was that "Blinking-Blue-Light-Primary-BIOS-Failure" doesn't mean "NO BIOS!!!".
To cut a very time-consuming, nerve-wrecking, story short: I had a working BIOS all along (that's the secondary BIOS), but because it was v1.18 it didn't, of course, know what a "RX580" is (nor what DisplayPort is either apparently, because even with the HD6850 only when I connect an old monitor through DVI, I got the screen to turn on).
As things stand I've already tried to update v.1.18 to v4.43 (twice) with the forum's tool but it returns "4 - Error: ROM file ROMID is not compatible with existing BIOS ROMID", and then re-flashes the backed-up one (v1.18).
I really would appreciate some help here. Thanx.
I have a P67A-GD65(B3) with a i7-2600K@4.4GHz, 16GB@1600MHz in three sticks (4+8+4 configuration), and a RX580(4GB). Been running this configuration ROCK-SOLID with the beta BIOS 4.43 for 12 months, and for 6 years before that with the i7@4.3GHz, 8GB@1600MHz (4+4), and a HD6850(1GB). The extremely rare BSOD were mainly due to some USB/External HDD cock-up. Never had one while playing games (or rather, one HW related) or encoding H.264 videos, with CPU/RAM at 100%, for hours.
Yesterday, when I was (admittedly) doing things I shouldn't be doing (messing with the BCD settings of my dual-boot/dual-SSD PC, which locked me off both), during one of the reboots it made a couple of tries (like the ones when trying new OC parameters, although I wasn't changing anything in the BIOS except boot settings) and I couldn't get the screen to turn-on. Everything was spinning fine but no Windows, no USB drive and no BIOS/Setup. Only when I removed the case panel to start unplugging/removing/switching stuff and saw the steady blinking blue LED I realized what happened: primary BIOS failure.
What I didn't realized though was that "Blinking-Blue-Light-Primary-BIOS-Failure" doesn't mean "NO BIOS!!!".
To cut a very time-consuming, nerve-wrecking, story short: I had a working BIOS all along (that's the secondary BIOS), but because it was v1.18 it didn't, of course, know what a "RX580" is (nor what DisplayPort is either apparently, because even with the HD6850 only when I connect an old monitor through DVI, I got the screen to turn on).
As things stand I've already tried to update v.1.18 to v4.43 (twice) with the forum's tool but it returns "4 - Error: ROM file ROMID is not compatible with existing BIOS ROMID", and then re-flashes the backed-up one (v1.18).
I really would appreciate some help here. Thanx.
