#BIOS update for Intel DH61CR

37 messages · Page 1 of 1 (latest)

lone shore
#

"BIOS Version 0042 - BEH6110H.86A.0042.2012.0327.2202" updates higher than this version, if you know where to find me please ping me i really need them to fix my built-in ethernet card and fix more issues on my bios so pls help gang 💔 😢

dreamy ledge
#

Please state what you are actually trying to achieve. Update the BIOS for what purpose?

lone shore
#

ethernet issue

#

although it's fixed now.. but i dont know if it'll be that way without an actual update

#

and for some reason the documents for the flashing say to use "BIOS recovery process"

#

for the first flash from 0042 to 0048

dreamy ledge
#

If the issue is fixed, make your backups and observe. Do not unfix it by fiddling with it.

lone shore
#

and the new updates also fix more issues like where the bios actually saves the hard drive boot order

dreamy ledge
#

If it does not save the boot order, you may be looking at an empty CMOS battery.

lone shore
#

the latest version does fix that issue tho

dreamy ledge
#

If that is actually on the fix list, then that update might be useful.

lone shore
#

and it might permanently fix my ethernet issue too

#

and maybe my channel B ram slot will start working too

dreamy ledge
lone shore
#

not a single .pdf

#

no instructions

#

that's the thing i cant find

#

ok

#

@dreamy ledge my dumb ass didnt properly read the instructions

#

this one is for me

#

my bios is older than 0048

dreamy ledge
#

I guess you need to hunt down ExpressUpdate or iFlash Update.

lone shore
#

but the system indentification says intel me firmware ver. 0.0.0.0

lone shore
dreamy ledge
lone shore
#

or iflash update?

lone shore
#

found it

#

@dreamy ledge should i use the F7 bios update tool to update even though it doesn't say i should use it?

dreamy ledge
#

I have no idea. This is proprietary stuff, I never used it. Worst case, you brick your mainboard.

lone shore
#

maybe when the ethernet starts to give me the same issue i'll update it then

#

drive boot order is not that big of an issue