F5F Stay Refreshed Hardware Desktop Hardware flashing on ASUS C7H indicates the firmware storage chip used.

Hardware flashing on ASUS C7H indicates the firmware storage chip used.

Hardware flashing on ASUS C7H indicates the firmware storage chip used.

C
CLPSGAMER
Member
176
05-06-2023, 07:21 PM
#1
seems to me that the EZFlash function has partially corrupted the bios in other words some functions like mem oc fail detect doesnt work anymore and it seems to have zero control over the vddp in tweakers paradise and the auto values for vddg and cldo vddg end up excessive voltages sooo im trying to find which chip stores the firmware on this freakin board chips on ebay display the standard 8 pin chips and a multimeter shows 0.2v on at least 2 of the pins if thats the case then i dont have to figure out getting a jtag connector for my usb programmer since theres no way im getting a test clip for that chip thats has bios labeled on it let alone that winbond chip
C
CLPSGAMER
05-06-2023, 07:21 PM #1

seems to me that the EZFlash function has partially corrupted the bios in other words some functions like mem oc fail detect doesnt work anymore and it seems to have zero control over the vddp in tweakers paradise and the auto values for vddg and cldo vddg end up excessive voltages sooo im trying to find which chip stores the firmware on this freakin board chips on ebay display the standard 8 pin chips and a multimeter shows 0.2v on at least 2 of the pins if thats the case then i dont have to figure out getting a jtag connector for my usb programmer since theres no way im getting a test clip for that chip thats has bios labeled on it let alone that winbond chip

G
goephi
Member
210
05-06-2023, 11:03 PM
#2
It seems the motherboard is still having trouble posting without any problems even when the CPU is dead.
G
goephi
05-06-2023, 11:03 PM #2

It seems the motherboard is still having trouble posting without any problems even when the CPU is dead.

S
SuperGlasses
Member
57
05-07-2023, 04:31 AM
#3
It seems you're feeling overwhelmed. You've been working too hard on unstable memory.
S
SuperGlasses
05-07-2023, 04:31 AM #3

It seems you're feeling overwhelmed. You've been working too hard on unstable memory.

C
CrazyGenius
Junior Member
4
05-07-2023, 05:18 AM
#4
Have you attempted a re-flash from the board level rather than using software? Also, the BIOS being on a single chip doesn’t include separate storage, according to what I understand.
C
CrazyGenius
05-07-2023, 05:18 AM #4

Have you attempted a re-flash from the board level rather than using software? Also, the BIOS being on a single chip doesn’t include separate storage, according to what I understand.

_
_Walk3rsPlay
Junior Member
7
05-10-2023, 01:46 PM
#5
I don't believe you can achieve that on the C7H within Windows, and I don't want to damage the board until I find a method to flash it using my USB programmer.
_
_Walk3rsPlay
05-10-2023, 01:46 PM #5

I don't believe you can achieve that on the C7H within Windows, and I don't want to damage the board until I find a method to flash it using my USB programmer.

D
denkrosava
Junior Member
3
05-15-2023, 02:13 AM
#6
Consider attempting a fresh flash using EZFlash once more, as I initially thought it was a software fix.
D
denkrosava
05-15-2023, 02:13 AM #6

Consider attempting a fresh flash using EZFlash once more, as I initially thought it was a software fix.

J
JustRhune
Member
199
05-15-2023, 10:10 PM
#7
ezflash was the reason I reached this point. I went through four BIOS updates; the first two worked fine, but after the memory failure detection stopped functioning, I lost that feature in later updates. I had to rely on the BIOS flashback to prevent black screens and reboots even when using default settings. From what I understand, ezflash doesn’t have full access or functionality on the BIOS chip, unlike a USB programmer. I faced the same issue with an ASUS P8Z68-V Pro/Gen3, where despite using the built-in flashing tool repeatedly, restoring CPU overclocking capabilities failed because the IntelME block was corrupted. That’s why I chose this USB programmer.
J
JustRhune
05-15-2023, 10:10 PM #7

ezflash was the reason I reached this point. I went through four BIOS updates; the first two worked fine, but after the memory failure detection stopped functioning, I lost that feature in later updates. I had to rely on the BIOS flashback to prevent black screens and reboots even when using default settings. From what I understand, ezflash doesn’t have full access or functionality on the BIOS chip, unlike a USB programmer. I faced the same issue with an ASUS P8Z68-V Pro/Gen3, where despite using the built-in flashing tool repeatedly, restoring CPU overclocking capabilities failed because the IntelME block was corrupted. That’s why I chose this USB programmer.

S
SevensGamer
Member
154
05-15-2023, 10:53 PM
#8
I used a Samsung BDie to kill a R7 1700 on this board and now I'm running an R5 3600.
S
SevensGamer
05-15-2023, 10:53 PM #8

I used a Samsung BDie to kill a R7 1700 on this board and now I'm running an R5 3600.