progress update:
I eventually forced shut the PC at the mains. waited many minutes to be sure any memory including firmware memory was cleared, then mains on, and tried the flash BIOS button again, and the led was flashing ongoingly.
more than 8 hours later after breakfast, the led was still flashing, the word flashing is ambiguous here as could mean the led flashing, or the flashing of the BIOS. anyway, the led still flashing, forced the machine off directly at the mains. waited many minutes, then mains on, waited several minutes, then tried booting. and this time booted really quickly to Windows, so maybe the flashing has worked. will have to check later as I have a shopping expedition later.
if it has worked, the mobo isnt functioning the way the manual says, which does show incompetence of MSI in not properly documenting, or the mobo is defective. because p71 the 2nd item 6. says the led will be off when the process is completed. FALSE.
From MoBo manual, page 71:
Updating BIOS with Flash BIOS Button
1. Please download the latest BIOS file that matches your motherboard model from
the MSI® website.
2. Rename the BIOS file to MSI.ROM, and save it to the root of the USB storage device.
3. Connect the power supply to CPU_PWR1 and ATX_PWR1. (No need to install CPU
and memory.)
4. Plug the USB storage device that contains the MSI.ROM file into the Flash BIOS
Port on the rear I/O panel.
5. Press the Flash BIOS Button to update BIOS, and the LED starts flashing.
done all that, and its as described
6. The LED will be off when the process is completed.
false! even after 8 hours the led was still flashing. but maybe it has reflashed the rom. this shows either a defective mobo, which then means poor quality assurance, or incompetence of incorrect documentation.
Sure it does.
Page 11, item #11 is the flash BIOS USB port, type-A.
its not on p11!
p11 is "connecting the power connectors"
but I did find it mentioned on p 24, but it is well hidden, it ought to be labelled on the diagram.
It is located just above USB type-C port.
there are 3 USB C ports, and "above" is highly relative! relative to the diagram? relative to the tower case?
Flipping the PSU switch should suffice in terminating power to the PC.
So, flip the PSU switch (you can disconnect from the mains as well), wait for ~5 mins, plug the power cord back in (or flip the PSU switch) and power on. It is possible that MoBo could continue flashing the BIOS.
If no image is seen and the Flash BIOS button doesn't blink, things get hairy.
Power down, flip PSU switch, remove USB thumb drive with MSI.ROM.
Flip PSU switch to ON, power back up. Look if you get an image.
If 0 life and no image, power off, flip PSU switch. Open up PC case and move the dual-BIOS switch to position B (it should be in position A).
MoBo manual, page 55 for further reading.
After that, flip the PSU switch to ON and power on. Dual-BIOS LED above the switch, should change from white LED to red LED. Look if you now get the image.
looks like forcing the machine off at the mains, then mains on, and flash BIOS button again may have worked, it has either worked or it has done nothing. it booted much faster than it ever has, so I think it may have worked. if so, that is good, but shows the manual is unreliable.
Then, power off, flip PSU switch, move dual-BIOS switch to position A, flip the PSU switch to ON.
Prepare the USB thumb drive with MSI.ROM in root directory (as described in MoBo manual). Format the USB thumb drive in FAT32 format. Don't format the file system into FAT (aka FAT16).
somewhere I read it can be FAT or FAT32, but I cannot locate the quote. as FAT is more ancient, I would expect that to be the safest. I think FAT has been designed to be a bootstrap conformant filesystem, ie you can use a bit of the format easily directly without filesystem eg when the UEFI saves screenshots. a general filesystem might be unfeasible without an OS to hand.
Also, better to have just single file on the root directory, rather than two or more (like you had).
DO NOT POWER ON THE PC, plug the USB thumb drive into item #11 USB port, press Flash BIOS button on the back of the MoBo. LED should start blinking. Once LED stops blinking (goes off), BIOS flash is complete.
I cannot rely on the blinking stopping! will just have to leave it on for several hours to be absolutely sure.
will find out later if the BIOS got reflashed.
Richard, you were warned this was risky.
Why did you decide to flash BIOS? It's rhetorical.
Immediately before your latest post Aeacus warned you not to do this because risk is high, and said to only do it if you know for a fact the new version fixes your problem.
I didnt want to, but the machine often doesnt boot. generally rebooting doesnt work, the mobo led counter just either keeps going round and round, or it halts at some number, and never boots, not even after 30 minutes.
only with mains off, then mains on, it usually boots, but not always, sometimes it freezes up.
I have been using my 2010 Gigabyte mobo for 14 years, and never had this problem. nor the other PCs I have used, all boot first time. now the OS boot might freeze up. but not the mobo boot, ie the process up till the OS starts booting.
MSi support replied with a generic reply. They told you to use the latest BIOS just to get you to go away. There was no fix in this version and only a prayer it might somehow, some way solve a problem.
You should have known better.
MSI didnt deny there was a problem, but wouldnt help unless I flashed the BIOS.
lack of denial is generally interpreted as confession.
denial here would be "that is normal, the machine wont always boot up".
thus the mobo was in unacceptable condition, and so this either has to be fixed or the mobo junked, as I cant spend the next 10 years having to hope the machine boots each time I use it.
so the only way forwards was to flash the BIOS.
This has been a very convoluted and overly complicated process to go through. I hope it wasn't all just to lead you to a bricked motherboard.
luckily it isnt bricked.
You can return the motherboard since it was MSi support that urged you to flash it. Sort of.
You have shown you are not one to be held back by rules, warnings, advice or common sense.
Sometimes that is fine, like the left handed guitar conversation we had.
But if something isn't safe, like firearms or medicine then having an indipendent mind about it is as wise as jumping off a cliff.
following advice also is highly risky!
I was told in 2006 by a financial advisor that over any 20 year period, the stock market outdoes all investments. but in fact the FT100 didnt outdo where it was at start of 2000 until 2015, and was outdone from 2000 to 2020 by gold.
eg Aeacus said the USB C mobo port will just be CPU graphics, but in fact is faster than the 4060's DP port.
either that, or the benchmarking software is benchmarking the wrong thing. but the benchmarking software is also his advice.
the mobo manual says the led flashing will halt once the flashing is complete, well either the flashing doesnt work or the led doesnt halt flashing! so if I followed the manual's instructions I might wait 10 years!
But that's besides the point.
Helping you complete a build and put it together should have been finished ages ago. You were interested in experimenting with lots of different things, and that's fine. Sometimes it was not what i would advise trying but there was no risk.
Guiding you through unneccessary BIOS flashes or possible bricked motherboard issues is not something i hoped to see.
You have every right to treat your possesions as your own playground but ...i wish you were more willing to keep it simple and just get from A to B, and B to C and so on, and enjoy a new PC instead of looking for new ways to get mired in OS installs and reinstalls, display tests and who knows what else
yes, but from these experiments, I now know how to have Windows 10, Windows 11, Linux Mint 21.1 all booting directly from the same disk.
these experiments arent mobo tourism, its to understand a lower level of stuff which isnt documented.
Then again, it's all part of a new PC. I guess. Going against the grain as often as you do, you might end up breaking something. Esp. taking chances with BIOS flashes.
Please don't.
I did take into account that there was a spare BIOS, if there wasnt, I would have been more hesitant.
What's this about the motherboard never booting properly?
when I switch on the mains, then press the power button on the tower,
it somtimes never reaches the UEFI screen, where there is the dragon and it says press delete for the UEFI, and press ???? to reflash the rom, and ????? for boot options.
instead, the fans come on, and all the continual led colour changes, the led counter on the mobo might cycle round and round, or it might halt at some number. and this just continues forever, eg wait 30 minutes or an hour and still no boot.
this happens virtually every time with reboots, ie when you select restart on Windows. the machine powers down, then powers up, and it never reaches the UEFI options.
so its not "never" but "sometimes" from mains on, and "usually" if you reboot.
now with the possible reflashing, it booted much faster.
This wasn't actually the 1st time when i warned about BIOS updates.
In this very topic, 1st page, in my 7th reply (reply #16), i wrote this:
you warned me plenty, this is why I was hesitant. but MSI's lack of denial told me the mobo was malfunctioning, and they wouldnt help me unless I reflashed. I asked you various times and you were unable to help me with the problem that the mobo often doesnt boot to the OS.
the fact the mobo has a spare BIOS meant I could take the risk. but if that failed, I wouldnt risk flashing the 2nd BIOS.
it must have been kaput right from the start, probably a returned item which they offloaded onto me
No, it was not. BIOS worked. You got your build running. OSes installed. It worked fine.
incorrect!
it DIDNT work fine, it often doesnt boot. I would have to hope it booted each time I used the machine.
sometimes I had to power off at the mains maybe 4 times before it would boot properly.
this is like the Fiat car my parents bought in 1973, where they would have to keep trying the ignition for 5 minutes before the car would start!
as kids we used to say:
toyoyoyoyo ... for trying the ignition,
then
brrrm brrm for when the engine started!
I have used several PCs over the years, the 2004 HP Pavilion tower, the 2006 Gigabyte PC, the 2007 Fujitsu-Siemens PC, the 2010 Gigabyte, the 2023 HP Laptop, a few PCs of other people, and EVERY PC BOOTS EVERY TIME TO THE OS BOOT. the OS boot can fail, where it might freeze up.
with the Gigabyte, the moment you power on, you instantly get hardware info, with the message that press Delete to go to the early startup.
there is no waiting and no doubt.
so I know what to expect, and the mobo didnt meet my expectations. same way the mobo graphics via HDMI was WORSE than my Intel Celeron powered HP Pavilion of 2004 with ATi Radeon!
I am not going to pretend this or any hardware is better than it is, nor pretend it is worse than it is.
I will describe it as it is, good or bad or mediocre. because part of the value of the internet is to warn people of bad stuff, and also to point out good stuff. but if you do this dishonestly, either overrating or underrating, it deteriorates the internet.
I once was talked into an HP printer, then delays arriving, so I read amazon reviews, and these were lukewarm, with one guy saying "its alright, but not a patch on my Epson". I then cancelled the purchase as it wasnt delivered when promised, and no clear date when it would, and bought an Epson Ecotank, best decision I made with printers!
if it has been fixed by reflashing, where I have only tried this once, then the BIOS must have been corrupted, or bugged.
and the MSI person didnt deny the description.
its not good enough if some hardware or software sometimes works, sometimes doesnt.
what you might call temperamental.
it is defective if this happens.
now in the old days, eg with the Amiga 500, there was sometimes indispensible software, where there were no alternatives, and which did have bugs. but from continual use I knew where the bugs were and would step around those.
eg I found a bug even with the GNU C compiler, gcc, where it processed a certain kind of expression incorrectly. but in the modern era, gcc is the only option, so I worked around the problem.
Warranty doesn't cover user made mistakes. It only covers manufacturing defect.
You knowingly going through the process of updating BIOS, while very well knowing the risks, is not something MSI is responsible of.
it wasnt a user made mistake, I havent made any mistake. right off the bat it wasnt always booting.
the very first boot was alright. but right from day 1, it often wouldnt boot. which was a new experience for me as I have been using PCs for 20 years, and I used real Amigas from 1988 till 2003, which is 15 years, and never had such a problem. 2004 onwards I started using emulated Amigas, as that enabled me to use a much higher res screen, AND have say 1 gigabyte of memory. my real Amiga 1200 had 6MB, 2MB factory installed, and 4MB expansion.
Its a fully valid warranty claim, legally they either have to replace it with the same or better, OR issue a full refund. they can refuse to refund, but only if they replace it.
to deny a refund, they would have to prove I made a mistake, the law in Britain is always on the side of the consumer, the consumer doesnt have to prove they didnt make a mistake, the firm has to prove they did make a mistake.
so without scarring of the machine, its not viable for them to do this. I am ultra careful in the handling of all equipment, so there are no scars on this machine.
I only went to update the BIOS because MSI by not denying the description was a problem, tacitly confessed to there being a problem, and they werent going to help further unless I reflashed the BIOS.
eg if I said: I bought one of your apples, and it was bitter.
and you reply: you need to boil the apple for one hour.
you have tacitly confessed that the bitterness is a problem, as you havent denied this.
you are essentially saying an apple being bitter is a problem, and some further processing is necessary to remedy the bitterness.
whereas if I said: I bought one of your apples, and it was a delicate sour taste,
and you reply: that is how better quality apples are meant to be.
then you are denying there is a problem.
you are essentially saying an apple being sour isnt a problem.