MSI MS-16F2 Barebone Bios Updates

yes but the Problems are the Little changes on the Mainboard.

Dolby Home Theater V3 or V4 in the same model but different Revisions of the board.

so there is a Problem if i Flash a bios for a newer Revision with V4 Support or Dolby Advance V2 or what ever they used

 

no Replys from the pros ? plz help to make sure i get the right bios and stuff.

 

This bios works on E16F2IG6?
Mine is: V3.05

I guess that the resseller doesn't change much (or aything) from the barebone, once there are places on bios where I can see: "To be filled by O.E.M." or "Series Number: FFFFFFFF", etc...

 

I've not seen a barebone using another bios from a standard barebone and having issue.

 

Good evening hacktrix2006,

I hope you will read this post.
I tried sending you a PM, but somehow i am unable to.

I would like to request the Modded Bios for MS-16F2

(I currently have a MS-16F2 with stock bios E16F2IG6 V3.03).

Regards, dikkydik

 

Hi,

maybe this is not the best thread for my problem but I think it is bios related. Has anybody experienced constant 100% cpu usage in task manager under windows 10? Personally this problem really annoys me and all I know that this is a sandy bridge cpu related problem and it can be fixed with bios upgrade (if you have a desktop motherboard). Unfortunately, if I am right, there are not so many bios versions for this notebook. Maybe the 3.05 is the newest. Now I am running on v3.03 and would appriciate somebody could check the the issue also exist on v3.05 beacause if not I will upgrade my bios.

Thank you

 

I have a problem with MS-16F2 barebone. I thought to pull bios battery off from the socket when I went sleeping, aim was to reset values like every now and then. Then, morning came and I put the bios battery back to mobo. Booted, managed to go into bios once. Changed the boot mode from RAID to AHCI (using ssd). Reboot. Splash logo came up (powernotebooks.com since 1999), saying F11 to boot menu and del to setup, then flashed RAID for some time, back to the first splash screen and then nothing. Just stays there. I thought wtf, and pulled battery, ac cable and bios battery out resetting values again. Now same thing, but cant enter bios setup anymore. Shows raid menu, then back to powernotebooks-logo and just staying there. Took hdd's out, now raid thingy is not showing, just blinks a few times and back to first screen. Can't enter boot menu, or setup. Bios seems not to reset, or then just hangs. 2 keyboards tested, ctrl+alt+del restarts but f11 won't go boot menu or del setup. Any advice, I'm running out of options here, worked fine yesterday....

 

If its one of ours you can call for support. But if it's not booting try re-seating the ram and running with a single stick. Usually I would leave the cmos battery out for 30 secs, it does not need to be out al night

 

Yes, I've tried only single stick, today I'm gonna go through them all. But if the BIOS doesn't get power for 30 secs or 30 days, it should come right up and reset every time. Also I only changed the RAID to AHCI and that messed the bios up?

 

Hi guys,

I'm trying to update the bios on my Medion Erazer X6819 - MS-16F2
I've replaced the GTX 570m recently with a GTX 970m 6gb and now trying to get all the bois up to date

I ran Afudos with E16F2IG6.30R using /p /b /n but it says ROM file ROMID is not compatible with existing ROMID - i was pretty sure this is the right bios
Here's my specs
MS-16F2
i7 2670QM
8gb 1333 mhz ram
GTX 970m 6Gb

Existing Bios
Bios - E16F2IM7.509
EC - 16F2EM71 VER4.06
ME FW - 7.0.4.1197
Microcode ver - 1A

vBios
84.4.22.0.11

Tried to flash
Bios - E16F2IG6.30R
EC - 16F2EG1.422

Any advice would be very much appreciated


Thanks

 

It's all fine now,

I WAS trying to flash the wrong bios - got sorted today with a little help and installed MS-16F2 version 50E bios and also got my GTX970m 6gb vbios sorted as they wouldnt update to latest driver

 

Could you provide a new link for me? It would be awesome!
Tried to use a "broken" X6819 with my three harddrives, but somehow the bios does not manage to recognize more than two at a time.
Maybe I can figure this out within the unlocked bios.