Skip to main content
added 762 characters in body
Source Link
Astrogator
  • 129
  • 1
  • 5

I have two MSI Z270 SLI PLUS motherboards with intent to install matching hardware /software configuration. Unfortunately, they are not identical: one has BIOS E7A59IMS.140 from 12/15/2016, the other - E7A59IZ1.1J1 from 07/06/2017:

v.140 v.1J1

First puzzle: current highest official BIOS version is 7A59v1A from 2018-07-17.
M-Flash recognizes E7A59IMS.1A0 file on the first mobo (14), but not on the second. I attribute that to 1A being less than 1J, but would like to have a confirmation.
Even so, i can't explain dates being out of order.

Googling E7A59IZ1.1J1 results in only two links, https://bios.ethosdistro.com/motherboard-bios/current-bios-list.txt and a related direct file URL. So, this may not be an official BIOS?
Is there a way to re-flash 1J to official one (1A)?

Both sets (mobo + cpu + ram) have passed rigorous (24+ hrs) MemTest86 v7.3.


Next, Windows setup (from the same USB drive) looks normal on 14: v.140

but has dithered color depth on 1J: v.1J1 and lower resolution (dialog fills entire screen): v.1J1 occasionally with color (and in Classic theme!): v.1J1

Since CPU graphics is used on both, is this a result of BIOS mod on 1J, or 2nd CPU is somehow damaged? (I thought about swapping CPUs, but haven't gotten to it yet, will try next)


2019-May-03
Swapped CPUs, the problem remains on 1J.
So it seems to be a result of some BIOS mod (possibly from|by|for ethOS?)..

Would love to re-flash it with official 1A BIOS, but 1J's M-Flash does not recognize the file..

Wiped a 256MB USB 2.0 stick, copied a single 16MB E7A59IMS.1A0 file to it: 7A59v1A 1J refuses to see/recognize the update: 1J while 14 is perfectly happy recognizing it (also added sub-folders with drivers): 14

Is there any other way to force flashing of official 1A BIOS over this suspect 1J?

I have two MSI Z270 SLI PLUS motherboards with intent to install matching hardware /software configuration. Unfortunately, they are not identical: one has BIOS E7A59IMS.140 from 12/15/2016, the other - E7A59IZ1.1J1 from 07/06/2017:

v.140 v.1J1

First puzzle: current highest official BIOS version is 7A59v1A from 2018-07-17.
M-Flash recognizes E7A59IMS.1A0 file on the first mobo (14), but not on the second. I attribute that to 1A being less than 1J, but would like to have a confirmation.
Even so, i can't explain dates being out of order.

Googling E7A59IZ1.1J1 results in only two links, https://bios.ethosdistro.com/motherboard-bios/current-bios-list.txt and a related direct file URL. So, this may not be an official BIOS?
Is there a way to re-flash 1J to official one (1A)?

Both sets (mobo + cpu + ram) have passed rigorous (24+ hrs) MemTest86 v7.3.


Next, Windows setup (from the same USB drive) looks normal on 14: v.140

but has dithered color depth on 1J: v.1J1 and lower resolution (dialog fills entire screen): v.1J1 occasionally with color (and in Classic theme!): v.1J1

Since CPU graphics is used on both, is this a result of BIOS mod on 1J, or 2nd CPU is somehow damaged? (I thought about swapping CPUs, but haven't gotten to it yet, will try next)

I have two MSI Z270 SLI PLUS motherboards with intent to install matching hardware /software configuration. Unfortunately, they are not identical: one has BIOS E7A59IMS.140 from 12/15/2016, the other - E7A59IZ1.1J1 from 07/06/2017:

v.140 v.1J1

First puzzle: current highest official BIOS version is 7A59v1A from 2018-07-17.
M-Flash recognizes E7A59IMS.1A0 file on the first mobo (14), but not on the second. I attribute that to 1A being less than 1J, but would like to have a confirmation.
Even so, i can't explain dates being out of order.

Googling E7A59IZ1.1J1 results in only two links, https://bios.ethosdistro.com/motherboard-bios/current-bios-list.txt and a related direct file URL. So, this may not be an official BIOS?
Is there a way to re-flash 1J to official one (1A)?

Both sets (mobo + cpu + ram) have passed rigorous (24+ hrs) MemTest86 v7.3.


Next, Windows setup (from the same USB drive) looks normal on 14: v.140

but has dithered color depth on 1J: v.1J1 and lower resolution (dialog fills entire screen): v.1J1 occasionally with color (and in Classic theme!): v.1J1

Since CPU graphics is used on both, is this a result of BIOS mod on 1J, or 2nd CPU is somehow damaged? (I thought about swapping CPUs, but haven't gotten to it yet, will try next)


2019-May-03
Swapped CPUs, the problem remains on 1J.
So it seems to be a result of some BIOS mod (possibly from|by|for ethOS?)..

Would love to re-flash it with official 1A BIOS, but 1J's M-Flash does not recognize the file..

Wiped a 256MB USB 2.0 stick, copied a single 16MB E7A59IMS.1A0 file to it: 7A59v1A 1J refuses to see/recognize the update: 1J while 14 is perfectly happy recognizing it (also added sub-folders with drivers): 14

Is there any other way to force flashing of official 1A BIOS over this suspect 1J?

Source Link
Astrogator
  • 129
  • 1
  • 5

Two MSI Z270 SLI PLUS have different graphic output quality (BIOS mod?)

I have two MSI Z270 SLI PLUS motherboards with intent to install matching hardware /software configuration. Unfortunately, they are not identical: one has BIOS E7A59IMS.140 from 12/15/2016, the other - E7A59IZ1.1J1 from 07/06/2017:

v.140 v.1J1

First puzzle: current highest official BIOS version is 7A59v1A from 2018-07-17.
M-Flash recognizes E7A59IMS.1A0 file on the first mobo (14), but not on the second. I attribute that to 1A being less than 1J, but would like to have a confirmation.
Even so, i can't explain dates being out of order.

Googling E7A59IZ1.1J1 results in only two links, https://bios.ethosdistro.com/motherboard-bios/current-bios-list.txt and a related direct file URL. So, this may not be an official BIOS?
Is there a way to re-flash 1J to official one (1A)?

Both sets (mobo + cpu + ram) have passed rigorous (24+ hrs) MemTest86 v7.3.


Next, Windows setup (from the same USB drive) looks normal on 14: v.140

but has dithered color depth on 1J: v.1J1 and lower resolution (dialog fills entire screen): v.1J1 occasionally with color (and in Classic theme!): v.1J1

Since CPU graphics is used on both, is this a result of BIOS mod on 1J, or 2nd CPU is somehow damaged? (I thought about swapping CPUs, but haven't gotten to it yet, will try next)