F5F Stay Refreshed Hardware Desktop Did you just install the newest BIOS on your GA-EP35-DS3?

Did you just install the newest BIOS on your GA-EP35-DS3?

Did you just install the newest BIOS on your GA-EP35-DS3?

T
TNTGirlMC
Junior Member
Find
13
11-27-2016, 06:58 AM
#1
I own a ga-ep35-ds3 equipped with a dual-core E5700 and a 2048+1024+512+512 MB DDR2 6400U, paired with an RX 470 chipset since there’s no VGA output. I considered going retro. For my session, I ran Infernal:Hell's Vengeance, upgraded the GPU as seen online, and everything worked smoothly. I also thought about updating the CPU but opted for a Q9400 instead. Before making changes, I saved the current BIOS and installed the F4 BIOS from Gygabyte’s site. My Windows 7 64-bit reported the .exe as corrupted, showing a pop-up with the same error message. I swapped in a quad-core processor but it still won’t boot—worse, it gives a blue screen after a short time. RAM tests in Windows 7 passed fine. The F1, F2, F3, and F4 SHA-256 checksums differ from the backup BIOS, or maybe Notepad++’s SHA-256 tool isn’t functioning correctly? I attached a backup of the working BIOS via Q-flash, then flashed the updated F4 and backed it up to a fat32 4 GB drive. Any advice?
Reply
Reply
T
TNTGirlMC
11-27-2016, 06:58 AM #1

I own a ga-ep35-ds3 equipped with a dual-core E5700 and a 2048+1024+512+512 MB DDR2 6400U, paired with an RX 470 chipset since there’s no VGA output. I considered going retro. For my session, I ran Infernal:Hell's Vengeance, upgraded the GPU as seen online, and everything worked smoothly. I also thought about updating the CPU but opted for a Q9400 instead. Before making changes, I saved the current BIOS and installed the F4 BIOS from Gygabyte’s site. My Windows 7 64-bit reported the .exe as corrupted, showing a pop-up with the same error message. I swapped in a quad-core processor but it still won’t boot—worse, it gives a blue screen after a short time. RAM tests in Windows 7 passed fine. The F1, F2, F3, and F4 SHA-256 checksums differ from the backup BIOS, or maybe Notepad++’s SHA-256 tool isn’t functioning correctly? I attached a backup of the working BIOS via Q-flash, then flashed the updated F4 and backed it up to a fat32 4 GB drive. Any advice?

Reply
Reply
E
EliteChicagoan
Member
Find
228
11-29-2016, 08:46 PM
#2
You haven't confirmed whether the CMOS was cleared after updating the BIOS. It's also good to consider replacing the battery just in case it's affecting settings. I re-downloaded the BIOS and saved it elsewhere to avoid file corruption. Regarding the checksums, it's important to verify that the downloaded files match the expected values.
Reply
Reply
E
EliteChicagoan
11-29-2016, 08:46 PM #2

You haven't confirmed whether the CMOS was cleared after updating the BIOS. It's also good to consider replacing the battery just in case it's affecting settings. I re-downloaded the BIOS and saved it elsewhere to avoid file corruption. Regarding the checksums, it's important to verify that the downloaded files match the expected values.

Reply
Reply
K
KingPro
Junior Member
Find
3
12-07-2016, 01:23 PM
#3
I was busy all day today... Ventoy+Linux caused a kernel panic around second 2.something. Ventoy+Windows triggered a hard error and a blue screen, with some random DLL issues. Using Rufus on W7 set my boot drive to show 35 MB, but I’m not sure if the motherboard is actually dead.
Reply
Reply
K
KingPro
12-07-2016, 01:23 PM #3

I was busy all day today... Ventoy+Linux caused a kernel panic around second 2.something. Ventoy+Windows triggered a hard error and a blue screen, with some random DLL issues. Using Rufus on W7 set my boot drive to show 35 MB, but I’m not sure if the motherboard is actually dead.

Reply
Reply