PC can't boot ... Is bios update could do it ?

[KrazyT]

Hi all !
I've ran into a problem with a new PC.

Quick resume :
It's a PC for my job.
i7 12700KF / RTX 3060 / Asus ProArt B660 / 64 Go Corsair 3200 / Crucial SSD NVME 500 Go (for Win) and Crucial NVME 1 To (for the rest)
I've mount it and install Win 10 ... (but not activated it, as I need a new license key) about 3 month ago.
1 st problem, the Ram can't stand 3200 Mhz ... but fine with 2133 Mhz ...
PC was working and Win 10 started fine ...
I leave it this way for 3 month, no using it, unplugged.

Now, I have some time to care about,
Plug everything, start ... and well , i can access to the bios, (seems a little buggy, sometimes it freezes)
Win seems still install as labelled on the bios (Crucial SSD Win boot something) ...

Here the question at last :
Should I upgrade the bios ?
Is it easy as Asus says (put the file on a USB drive > go to bios > Asus EZ flash and let's roll ?)

 

[bug]

When systems stop booting, the proper diagnosis procedure is to take as many components out as possible (this is where you'll regret not have an IGP). If it doesn't boot, it's the mobo, CPU or PSU at fault. It could also be the RAM, try swapping the lone stick for another. If it boots, start adding other components, one by one. This way you'll find out which one is at fault so you can take it from there.

BIOS update is fairly painless these days, but unlikely to fix a non-boot problem.

Also, it's always nice to be able to tell French posters looking at how they spell Go or To. Bonne chance!

 

[AsRock]

You need a 100% stable system before doing any kind of bios updates.

 

[Deleted member 232534]

clear CMOS (bios) using the jumper on the motherboard

 

[KrazyT]

When systems stop booting, the proper diagnosis procedure is to take as many components out as possible (this is where you'll regret not have an IGP). If it doesn't boot, it's the mobo, CPU or PSU at fault. It could also be the RAM, try swapping the lone stick for another. If it boots, start adding other components, one by one. This way you'll find out which one is at fault so you can take it from there.

BIOS update is fairly painless these days, but unlikely to fix a non-boot problem.

Also, it's always nice to be able to tell French posters looking at how they spell Go or To. Bonne chance!

Yes I should have go for a iGPU processor, but this one was way cheaper ... Ahhh ... greed !
I'll take the PC back home, and I'll try this.
I suspect the Ram ...

You need a 100% stable system before doing any kind of bios updates.

Seems logical ... but if the bios improves Ram stability (for example), you'll have to do it before runing a stable system ? (just a question, not an affirmation )

For the bios update ... I haven't a FAT usb drive here, just a NTFS, i'll check this at home.
The latest version of the bioses need an upgarde of the Intel version ME ... so I guess Win should be runing fine ...

clear CMOS (bios) using the jumper on the motherboard

Start with it, easy to do (I've reset the bios via F5, restore bios by default)

Little update :
I suspect the ram : why ?
because, it was ok in the QVL but after the Ram X.XX rev (don't rembember the numbers exactly) ... and of course i've get the anterior ram rev'.
That's why i've asked about a bios upgrade ...

 

[Deleted member 232534]

you have a problem with booting or with os?

 

[KrazyT]

With booting the OS
I have access to bios, so I guess GC and the HDMI port should work.

Strange thing, i've put a Win 10 USB stick, trying to boot on the Win 10 install, but the PC doesn't shown anything, no bios ... strange :/

 

[Deleted member 232534]

don't hesitate to upgrade the bios

 

[Kyan]

Also, it's always nice to be able to tell French posters looking at how they spell Go or To. Bonne chance!

What do you mean ? I don't see the problem on KrazyT post. I'm French too, so that's probably why i can't see the problem

 

[bug]

What do you mean ? I don't see the problem on KrazyT post. I'm French too, so that's probably why i can't see the problem

Everybody else says "bytes" not "octets"
It's not a problem, obviously, just a telltale sign.

 

[pressing on]

With Asus B660 boards you need to upgrade the Intel Management Engine (ME) driver, then the matching firmware and then to the latest BIOS in that order. The problem is that the ME driver and firmware updates can only be done in Windows and as you cannot boot you cannot access Windows to do the updates...

If the boot NVME SSD is in slot M2_1 moving it to M2_2 should enable a boot. If that's the case install the latest Intel Management Engine Interface V2306.4.3.0 For Windows 10/11 driver from your local Asus support site. The firmware update is listed under the BIOS updates, you need MEUpdateTool Version 16.1.27.2176. Once this two are done you can update the BIOS. A USB key to do this has to be formatted in FAT 32 format, not NTFS. The latest BIOS for your board is BIOS 2602. After doing the three items the boot drive should work OK is slot M2_1.

 

[Kyan]

Everybody else says "bytes" not "octets"
It's not a problem, obviously, just a telltale sign.

Oh ok i was reading Go and To not as storage value but word
I understand the "problem" now

 

[bug]

Oh ok i was reading Go and To not as storage value but word
I understand the "problem" now

Fwiw we also have the word "octet". But no one ever uses it, so "byte" was also added to the dictionary later on.
I suspect it exists in other languages, too, because "octet" is not strictly related to computing, it can mean a grouping eight several other things. Or even human beings, if we're talking about a band of eight.

 

[AsRock]

I wounder if it's just fast boot, and some thing like the cmos battery died really quick.

As the Original OS should work still if it was left working and might want to use just the boot drive

 

[bug]

I wounder if it's just fast boot, and some thing like the cmos battery died really quick.

As the Original OS should work still if it was left working and might want to use just the boot drive

If the battery dies, it usually just reverts to default settings (it's still powered when you turn the system on), it doesn't prevent booting. But it's worth taking a look at the system clock, see if it was reset.

 

[AsRock]

If the battery dies, it usually just reverts to default settings (it's still powered when you turn the system on), it doesn't prevent booting. But it's worth taking a look at the system clock, see if it was reset.

Maybe fast boot was disabled originally, there fore it would, well it does on my systems.

 

[KrazyT]

Ok, just tried the Clear CMOS ...
PC auto-restart 2-3 times, and on the post there was something about VMD ...

I go for F5 : load optimized defaults (exept install Asus shitware)

> PC restart, no image and restart again > screen shows "Asus blabla" press Del to bios, i press nothing and no Win loading, just a black screen ...

Keyboard and mouse have lights on, GC as well

*edit 1 : removed the battery and short-circuited, results are the same as the Clear CMOS trick ...
but here is the correct text on the bios post page :
"Please enter setup to recover BIOS setting.
After setting up Intel(R) Optane Memory or RAID,
VMD options must be set according to the interface type to avoid unknown issues.
Press F1 to Run SETUP"

*edit 2 : the bios is the v.0604 literally the first release bios :/

*edit 3 : test with 1 ram stick (32 Go Corsair Vengeance LPX) > same
test with the other single stick > same
test with a stick of Crucial Ballistix Elite 2400 > same
[each tested in the right slot (B2 as says in the manual for a solo stick)]

*edit 4 : i'll test this solution later

If the boot NVME SSD is in slot M2_1 moving it to M2_2 should enable a boot.

 

[Deleted member 232534]

IMO this is a problem with OS or failing SSD.

 

[MarsM4N]

First, a BIOS doesn't just go "bad" and needs a fix. But if you try to do a BIOS update on a unstable rig you sure going to end up with a broken BIOS.

screen shows "Asus blabla" ... but here is the correct text on the bios post page :
"Please enter setup to recover BIOS setting.
After setting up Intel(R) Optane Memory or RAID,
VMD options must be set according to the interface type to avoid unknown issues.
Press F1 to Run SETUP"

If you wouldn't just ignore the "bla bla" from the BIOS you would see what the fix is. Just read, gsus! What did you do between the state of working & non working? Changed some settings in the BIOS? Connected your boot OS to a different SATA port? Shuffled your RAM sticks around? Installed Intel raid drivers? Are you using a boot drive from a different PC? I guess something of the following should fix it:

- disable "Intel(R) Optane Memory"
- put the RAM sticks back in the previous slots
- plug in your drive to the non raid controller port (port 0 or 1)
- disable "Raid" in the BIOS and enable AHCI
- if you've installed raid drivers, remove them in the device manager & replace them with the standard AHCI drivers

If there is a new BIOS out it's wise to update it, once the PC is stable. BIOS'es include bug & security fixes and also add new hardware compatibility.

 

[Deleted member 232534]

1. update the bios to ProArt B660 D4 BIOS 1720. The latest bios that does not require Intel ME update (which is done in windows).
2. try to boot installed os. if this fails try to boot other drive or os from usb pendrive like ubuntu linux.

 

[KrazyT]

If you wouldn't just ignore the "bla bla" from the BIOS you would see what the fix is. Just read, gsus!

the bla bla thing is just the standard "press R2 to enter bios" with the Asus logo.

What did you do between the state of working & non working?

I mounted the PC this winter at home, install an old version of Win 10 without activate it.
Everything worked fine.
The plan was : bring the PC to my office, plug it, activate Win 10 and make all the updates.
The first part of the plan was successful, bring to the office, plug it ... start it, and then the Asus logo shown, normal, and black screen as Win doen't launch.

Changed some settings in the BIOS?

At the very first try, i've set 3200Mhz ram speed, PC reboot 1 or 2 times and set automaticaly to 2133 Mhz (I leave it that way)
Since i've made many F5 / Reset to load Defaults, and severals Clear CMOS.

Connected your boot OS to a different SATA port?

Nope sir !

Shuffled your RAM sticks around?

Tried 1 stick and another, even a different stick from another brand, same.

Installed Intel raid drivers?

I do not mess with Raid or something since the old Abit motherboard

Are you using a boot drive from a different PC?

Nope sir !

I'll try to check if *maybe* some Raid / Optane stuff are enabled, but my last check, everything was disabled ... i could have miss a thing :/

I'll try the solution to change the SSD port this afternoon ...
If fail, i 'll try the 1720 bios as M440 says ...

 

[KrazyT]

Edit :
Today i've only tried to re-install Win 10 -- No hardware change
Seems to work
Now i'll go for dowloading drivers & Win update.

Remarks, ram still runs @ 2133 instead of 3200 Mhz
Should I update bios when all will be correctly installed ?

 

[P4-630]

Should I update bios when all will be correctly installed ?

If you don't have PC crashes in BIOS you should be fine.

 

[KrazyT]

Edit : Bad news, after downloading LAN drivers on an another PC, I've plug the USB stick on the *new* PC (was off) and disable the Intel 2.5 LAN (the Realteck 1G is enough for my job) and start the PC ...
Back to the origin of the problem
No acces to bios, and after 3-4 restarts, acces to bios but Win doesn't lauch ...

*Edit 1 :
I reinstalling Win on the same disk again and i'll try to update ...

Just a question : could a USB plug (the one from the case) could be the issue ?

 

[Deleted member 232534]

Edit :
Today i've only tried to re-install Win 10 -- No hardware change
Seems to work
Now i'll go for dowloading drivers & Win update.

Remarks, ram still runs @ 2133 instead of 3200 Mhz
Should I update bios when all will be correctly installed ?

you should have started with the bios update. Why you work with ancient first release of the bios is unknown to me.

if you can log to windows you can install newest version requiring intel me installation from the microsoft os. I would check what is the intel me version flashed - this might have caused the mismatch and problem with booting the os.

if you can't log to windows install 1720