This does confirm the problem is more a hardware problem somewhere and not really a W10 problem.
Do you plan to use CH341A Software v1.34 and ASProgrammer v1.4 for your tests ?

ASprogrammer 1.4 seems to work with both CH341A programmers for Winbond 25Q128FV, too. I think that's good enough for me...

I never spared a thought on Windows 10 by the way, I always use the programmer/programming software as a normal user (UAC fully enabled) and there was no difference between Windows 7 and Windows 10?

Thanks for the information that for you ASProgrammer v1.4 does work fine under W10 as well as under W7.
On my side I am stuck with no Programmer solution working for the BIOS chip for any of my two ASUS Prime Z390M_Plus mboards.

Zitat von 100PIER im Beitrag #48

---

Thanks for the information that for you ASProgrammer v1.4 does work fine under W10 as well as under W7. ......

---

@lfb6
Thanks a lot for sharing your experiments.
You are right I had a contact problem with the Clip Board !!
I do significant progress and finally do succeed today under W10 x64 with ASProgrammer v1.4 as well with CH341A Software v1.34:




@Lost_N_BIOS
I "ll send you a PM about ASUS Z390M-Plus modded BIOS file to use for CH341A programmer.

However, a strange situation because Read/Verify operation does fail with CH341A Software v1.34 and is OK with ASProgrammer v1.40 (test done twice):




So, what Programmer Tool is good ?

Tested with CH341A Software v1.40 the Read/Verify operation is OK under W10:


Nota: I do observe CH341A Software v1.34 Read/Verify operation always does fail at about 50% of the operation. Is it a buffer size limitation bug ?

Zitat von 100PIER im Beitrag #50

---

@lfb6

So, what Programmer Tool is good ?

---

@KedarWolf
With CH341A Software v1.40 Free under W10 interface the Read/Verify operation is OK on my side.
Which Z390 mboard do you tested ?

Zitat von 100PIER im Beitrag #52

---

@KedarWolf
With CH341A Software v1.40 Free under W10 interface the Read/Verify operation is OK on my side.
Which Z390 mboard do you tested ?

---

Zitat von 100PIER im Beitrag #50

---

...... However, a strange situation because Read/Verify operation does fail with CH341A Software v1.34 and is OK with ASProgrammer v1.40 (test done twice). .... So, what Programmer Tool is good ?

---

@KedarWolf
What exact Manufacturer/type/model 128Mbits BIOS Chip do yo have on your mboard ?

Zitat von 100PIER im Beitrag #55

---

@KedarWolf
What exact Manufacturer/type/model 128Mbits BIOS Chip do yo have on your mboard ?

---

My BIOS chip is soldered (not socketed removable) and is a MICRONIX MX25L12873F, so may be very different from yours.

@lfb6
Thanks for your very interesting comments:

So, in my case (ASUS Prime Z390M-Plus) I do keep only 2 software programmer solutions running under W10 64bit v1809 interface :

1) CH341A Software v1.4
2) AsProgrammer v1.4.0

I have triple checked that for the both tools a "Read/Verify" operation is OK
and for the both tools a "Read/Verify/Save" operation does produce identical 16MB .bin saved file (checked with Hex Editor HxD tool v2.2.1.0)

Question: 'You don't rely on the Verify function of the software alone.'
But, I am not sure to understand your 'verify' method:

Does your "Verify" method consist of these successive operations :
1st_Read_IC_Memory => Save 'File_1' => Program from the saved 'File_1' => 2nd_Read_IC_Memory => Save 'File_2' => Compare (HxD tool) 'File_1' and 'File_2'.
'File_1' and 'File_2' should be detected as identical files via the 'Compare' function of HxD tool.
But if the files are not identical you have programmed your BIOS with may be one uncertain file and may be your BIOS is bricked ?
Do you confirm I have well understood your 'risky' Verify method ?

Normally I start with a changed bios file I want to flash, that's my source file. I program it into the chip and if the program says 'Verify OK' I read the content of the newly programmed chip again, save it and compare it to the source file once again on the PC.
May be a bit paranoid, but I don't trust especially the CH341 programmer software too much here. What do you mean is risky?

I understand you check that your changed bios file is well properly programmed into the bios chip.
But if your changed bios file does brick the bios chip contents you have to recover the bios chip contents with a good reference bios file.
So, I assume you have somewhere archived a 100% sure reference bios file for a 'recover' operation to avoid the risk to have a definitevly bricked BIOS.
Is it correct ?

Like you, my preference is definitively AsProgrammer v1.4.0 under W10 interface.
Do you use 'Blank check' function ? What is it ? What is the purpose ?
When we use "Erase" function it is a "FF" fullfillemnt or a "00" (blank ?) fullfilement with this tool ?