MOVED: K9a2 cf seriously BIOS bug!!!!!!!!!!!!

This topic has been moved to Overclockers & Modding Corner.
https://forum-en.msi.com/index.php?topic=117241.0

Quote from: BOSSKILLER on 27-May-08, 21:53:01
Read >>Posting Guide<<
"After changing FSB frequency or memory timings BIOS dont pass memory test that inside it(default 800Mhz)!"
What that is suppose to mean
P.S: Your board don't have "FSB"
I mean that when I CHANGE FSB FREQUENCY!!!! BIOS memory test fails on BIOS's form 1.3 to 1.6 revisions!
 

Similar Messages

  • MOVED: X79A-GD65 (8D) bios bug: TSC is badly out of sync

    This topic has been moved to Linux/Unix.
    https://forum-en.msi.com/index.php?topic=154242.0

    This topic has been moved to Linux/Unix.
    https://forum-en.msi.com/index.php?topic=154242.0

  • Thinkpad S540 possible BIOS bug concerning WOL

    I have had a Thinkpad S540 for a few months, and have it installed as dual boot Windows 8.1 and arch linux.  After completely shutting the machine down from linux I found that the battery would be down to around 70% charge after three days unused, and decided to investigate this problem since it was not reasonable for a new battery to lose charge at anything like this rate.
    By chance I came across a piece of information concerning the issue of disabling WOL (Wake on LAN) on the network interface, since I had seen one report that by default WOL is enabled and this requires power to be going to the network interface even when shut down in order to be able to respond to magic packets to start the machine up when it is shut down.
    First I checked the BIOS WOL setting and found it was set to "AC only" by default. So I changed it to disabled. This machine has the latest available BIOS version 1.54.
    However on investigating this after rebooting in linux I found that 
    # cat /sys/class/net/enp3s0/device/power/wakeup
    enabled
    # ethtool enp3s0 | grep Wake-on
    Supports Wake-on: pumbg
    Wake-on: g
    So WOL was still enabled despite it being set to disabled in the BIOS!
    I learned that I can make sure that in arch linux the WOL setting can be changed to set to disabled after bootup by using a udev rule:
    # cat 70-disable_wol.rules
    ACTION=="add", SUBSYSTEM=="net", KERNEL=="enp3s0", RUN+="/usr/bin/ethtool -s enp3s0 wol d"
    Then rebooting the machine I checked the WOL setting and it really is disabled now:
    # ethtool enp3s0 | grep Wake-on
    Supports Wake-on: pumbg
    Wake-on: d
    # cat /sys/class/net/enp3s0/device/power/wakeup
    disabled
    So I then ensured that the battery was 100% charged and shut down the machine and left it two and a half days - rebooting this morning the battery was still at 100% charge and no longer discharges unnecessarily when the machine is switched off,  so this is a clear indication of a bug in the BIOS for the WOL setting - it is still enabled despite the BIOS saying it is disabled!
    How do I report this to Lenovo so that they can fix the BIOS and release a new one that is working?
    I am aware of other users with different Thinkpads who seem to have the same problem, so this may be more widespread an issue than just on the S540.  
    It is also not just an issue with the battery running down when fully shut down but will likely also be a problem for a machine in suspend mode since the network interface may be consuming a watt or so of power when in suspend, which will again run the battery down at an unacceptable rate.
    I cannot imagine any use case where it would be necessary to have WOL enabled on a laptop that is mostly going to be used mobile - so having the default setting to AC only enabled, and having a BIOS bug enabling it when it is explicitely disabled is a serious problem.

    Anyone running windows in the same laptop can check the same issue of battery drain due to WOl being enabled by default - in the Device Manager under the network card, opening the settings menu for the ethernet wired card the default for Wake-on-LAN on my computer was set to enabled. This can be changed to disabled, and you may need to also disable the setting for Wake on Magic Packet. Also in the Power Management tab it is possible to uncheck the settings for "Allow this device to wake the computer" and "Only allow a magic packet to wake the computer"
    In my laptop these were all set to enabled by default.

  • U110 BIOS bug?

    Dear colleagues! Just got my new U110, seen Vista to work well and trying to install Debian Linux (Lenny) in it. When booting to the Linux system, I see in the very beginning this message:
    PCI: BIOS Bug MCFG area at e0000000 is not E820-reserved.
    PCI: Not using MMCONFIG
    PCI: Cannot allocate reseource region 98 of bridge 000000:1c.2
    Further, I have problem with starting X.org using xorg-xserver-video-intel . I am not sure if the problems are related, nor do I know if the first one is serious or not. Would appreciate any suggestions or solutions to either problem.
    Laura, Helsinki

    Hi Tommy,
    Tried the acpi off switch. Didn't work. In fact I redid the install with the linux acpi=off. However no luck. I switched acpi to no in BIOS too, however, no luck with that either.
    The reboot issue persists with ACPI: unable to locate RSDP showing up.
    Will try the to look for the USB setting in BIOS as per your suggestion and get back to you.
    Ta very much,

  • K8N Neo FSR, possible BIOS bug: setting Vcore with Cool'n Quiet enabled broken?

    Athlon 64 3400+, socket 754
    K8N Neo FSR, Pheonix-Award BIOS V1,5
    WinXP SP2
    Having Cool'n Quiet disabled in BIOS setup, CPU core voltage adjustment
    using 'Adjust CPU VID' below the Athlon 64 default 1,5V core voltage
    works like a charm. Fine!
    But with Cool'n Quiet enabled in BIOS setup (and WinXP), under load the
    CPU core voltage raises to 1,5V in any case, independently of what I did
    define in BIOS setup with 'Adjust CPU VID' (e.g. 1,4V). Software tools setting
    Vcore like Core Center are not running.
    So I can choose to either run a silent system in idle mode with Cool'n Quiet
    enabled or under heavy CPU load with Cool'n Quiet disabled but Vcore
    reduced :-( Am I missing something or does it rather look like a BIOS
    bug?
    Greetings, Falo

    Quote from: Tiresmoke on 21-March-05, 00:19:19
    As undervolting is not considured standard operating proceedures then how can it be considured a bug.
    nor is overclocking but MSI mobo manual reads 'This motherboard is designed to support overclocking.'
    So this mobo is designed for supporting at least one non standard operating procedure 
    Seriously, if BIOS offers a feature I suppose it to work as expected.
    regards, Falo

  • MOVED: R9 290X Gaming BIOS Status, Questions and Info

    This topic has been moved to BETA & MOD BIOS Section.
    https://forum-en.msi.com/index.php?topic=181463.0

    Hmm?  Wow.  That's odd that something IS indeed different enough that those BIOS doesn't work on your card but does on mine.  There must have been some revisions made on the physical board or something in the firmware hardware or something.  ??
    How old is your card?  I just got mine in the last 3 weeks and though stock can sit around at suppliers for weeks, experience dictates that because stock is a 'revolving door', often the actual age of a component is somewhat relevant to when it is purchased.
    I simply wouldn't try the Lightning BIOS for many reasons.  Good advice and good to know either way.
    I'm not willing to risk an expensive card but I've read of others who have flashed an HIS and Powercolor to an ASUS BIOS.  Wonder if things like that are possible and what are the potential implications?  I do have an old(er) 7970 than may be a good experimental device.
    Quote from: Pixelfenix on 02-July-14, 13:28:38
    Mine is SLIGHTLY different...
    Edit: I managed to flash V308MH.111 over V308MH.160 but it black screened as I got into Windows.. Since our cards have the same release date I thought maybe they were the same after all...
    Edit2: I know it sounds like a no brainer but don't EVER EVER flash a lightning vBIOS on the gaming edition, screen wouldn't receive signal anymore. I managed to reflash the stock vBios thanks to MSI's genius 2-bios switch solution :D
    Edit3: I tried flashing MH.100, same as 111, black screen in Windows

  • I'd heard about a bios bug!

    Hi guys,
    my system running not allways stable!I got some bluescreens of the art "STOP COMMAND"!
    Exactly this three ones:
    IRQL_NOT_LESS_OR_EQUAL
    PAGE_FAULT_IN_NONPAGED_AREA   and
    BAD_CALL_POOLER
    HERE are some information about it,but sorry,it's in german!
    I think that the faults causes maybe in that two ways!
    Once is a Memory error,because I become sometimes error Popups,that adresses can't written or read!
    I use one TwinMos Modul of PC3200,512 Mb!
    At the moment I test it in slot 3 and it seems to be more stable as in slot 1!The time settings seems to be not so important,I can use either 2.5-3-3-6,or 2-3-3-6!Normal is(I'm not sure 2.5-3-3-8)!
    But more important I think is,that the motherboard monitor shows me a core voltage of under 1.5V~1.48v!!!That is also the reason I mean,that I can't overclock my system over 205 MHz frontsidebus stable!In 3D Mark 3 I get instantly by the first test Wings of Fury a totaly blue screen(not the error bluescreen!Much darker and without any message!)
    So I'd heard about a bug in the AMI bios,that you can't  store a new core voltage!Either increase,nor decrease!My settings are on 1.55 Volt!Isn#t that the right voltage for the prozessor and if,why it isn't there a possibility to increase the core voltage for overclocking!But that is a must for a good result!I'm a little bit confused about that!The other possibility is,that my PSU is not strong enough!What for a Voltage is important for the CPU Core?I mean the 3.3V,or?My customer had said that he test the PSU and it's stable!It shall be have 32A,normaly it is enough to hold the voltage correct,but I knew that in china the electric is another as in germany!!!
    Another problem is that I have change my drive from the VIA controller to the promise,because I would first test  the speed and if this controller is able to read the correct monitoring data(Firmware,temperature,UDMA mode...)!The VIA doesn't do that but the promise can!And I use now together my old seagate drive on it.
    Because HDTunenow show me the correct UDMA mode,I'd seen that both drives are not running at their best settings!The samsung run at UDMA5,but can run on 7 and the seagate run on UDMA2,but can  do it on 5!So I would change it,but I have no idea where I can do that!In the hardware manager it isn't a possibility,neither on IDE(there is only the VIA),nor at the SCSI devices!I cannot see any settings therefor at the promise controller!And if I change the settings in bios on RAID(for S-ATA) and go into the RAID Menue with Ctrl+f on bootup,I can see keys for changing values,but their shows no result!And I think if their would working I can't use it,because with the RAID setting the computer will not boot if you don't create an array!
    Has anyone some ideas???
    Thank you very much!

    Thanx man!
    How I write it in my system specifications,I'd try to change the slot and it seems to be better with the RAM in slot 3!
    But,is it my not so good english or why you did not wrote anything about the bios bug I'd heard from!Is it true that it gives a bios version with this bug,that doesn't allow to store another core voltage?Because I think that is the problem!That my core voltage is only at 1.48V,wether I changed it to 1.55V,neither if I do that in bios,nor in bios on auto and do it with core center!
    What is the "normal" processor voltage?1.5 V?And if,why it gives no possibility to increase it higher than 1.55V for overclocking?What for voltage amounts are important for the processor to run stable?Only +3.3V or also the  +5V and +12V amounts?
    But anyway, it seems to be that the +3400  version of the processor is coming at its end of power and isn't so good to be overclocked!Better I'd bought a +3200 one I think!
    But my system is also good without overclocking if I take a look at my 3DMark and Aquamark results!!:worship:
    And my system isn't so old,only 2 month,but the errors comes also in the fresh system at the first days!
    Greetings from good old Germany!

  • BIOS BUG LEGACY FREE FADT DETECTED BUT FADT SIZE (129) is incorrect

    Dear all
    I am using linux ES4 (ORACLE LINUX) I am getting this issue while booting pl. any one has idea on this pls. give there suggestion for the same.
    BIOS BUG LEGACY FREE FADT DETECTED BUT FADT SIZE (129) is incorrect
    Tks/regs
    Lilly

    Maybe this links will help:
    https://bugzilla.redhat.com/show_bug.cgi?id=227202
    BIOS bug: Legacy free FADT detected

  • BIOS bug: Legacy free FADT detected

    Hi,
    It's a new install. I get the following info on booting the machine with OEL 4 update 5-Kernel 2.6.9-55.0.0.0.2.Elsmp
    BIOS bug: Legacy free FADT detected, but FADT size (129) is incorrect!
    The machine keep rebooting.
    Please help.
    Thanks and Regards,

    Hi Tommy,
    Tried the acpi off switch. Didn't work. In fact I redid the install with the linux acpi=off. However no luck. I switched acpi to no in BIOS too, however, no luck with that either.
    The reboot issue persists with ACPI: unable to locate RSDP showing up.
    Will try the to look for the USB setting in BIOS as per your suggestion and get back to you.
    Ta very much,

  • MOVED: I need a BIOS

    This topic has been moved to User modified BIOS.
    https://forum-en.msi.com/index.php?topic=117573.0

    Hi Britney
    You could try e9lo7ggkxf let me know if it works. The third letter is a lower case L.
    Good luck.
    Alan.

  • T440s fn ctrl swap bios bug

    Hi,
    I think this was documented before, but I am now experiencing the fn ctrl swap bug when going to sleep.
    I have swapped my fn and ctrl keys, and the setting never stays after resuming from deep sleep.
    I have updated my bios to the latest version (2.19) but it has not fixed it.
    Please advise. I do not want to turn off deep sleep.
    Cheers
    Solved!
    Go to Solution.

    Thank you for reporting this.  Yes, I can confirm it is BIOS bug.  We had this same issue on T430 generation and fixed it.  But now it seems T440 generation also suffers from this same bug, needs fix.  So I will report this to BIOS team.  Sorry for this inconvenience.

  • MOVED: MSI X48C Beta BIOS Required V7.46b

    This topic has been moved to BETA & MOD BIOS Section.
    https://forum-en.msi.com/index.php?topic=126034.0

    https://forum-en.msi.com/index.php?topic=117175.msg945441#msg945441

  • MOVED: X48C - New\Beta BIOS \ FTP

    This topic has been moved to User modified BIOS.
    https://forum-en.msi.com/index.php?topic=117175.0

    Gday ladies and gents,
    I've been MIA for a lil bit...  glad to be back
    I've received alot of help with My X48C and we're getting closer and closer to total sweetness.... 
    I am currently using 7.2B1 and for the most part she does ok.  A couple of issues tho:
    Legacy USB support seems to be a lil wonky....  every 2nd reboot BIOS tells me I have no Keyboard... I enter BIOS and sometimes it still says enabled....sometimes it switches back to disabled.  No matter which setting I choose the keyboard always works in BIOS post, so I can always get into bios, however I can never use my keyboard until I actually get into windows.  Its a minor inconvenience but this lil glitch prevents me from using the VISTA boot options.  IE I cant get into safe mode or even invoke the boot menu with F8 unless I hook up a wired keyboard.  I use a logitech wireless mouse \ KB combo not sure if its a hardware conflict or something -Asus had issues with Razor mice \ KBs for instance-
    The other issue is that damned 1N timing I keep moaning about...  On this BIOS it is intermittant...  sometimes it registers command rate 1 in everest etc... sometimes it doesnt.  Also my timings are a lil unstable.  Unless I specify them manually sometimes I'm 6-6-6-18, 6-6-6-16, 7-7-7-20 or 7-7-7-22.  The previous 7.1 beta bios I received -cant remember the build...but it was on of the later ones before the 7.2 beta- always had command rate 1 functioning but the board would be finiky posting...sometimes taking me 5+ mins to get it off the ground...  but once she posted all was good
    Are there any other betas or foolish experimental builds that I could take for a spin...  I love the rapid bios evolutions that this board seems to receive and am always up for further testing!  I'll be sure to be a regular PITA -pain in the @$$- again 
    Thanks again for all the test builds and wicked support!  You guys rock!   Its good to be back again!   
    Zyro

  • Help---MSI KT4AV bios BUG ?!

    Hi....(excuse my bad english... )  I try...
    I have the MB   MSI - KT4AV
    two days ago , I have buy a AMD CPU 3200 Ghz , 32bit ofcourse, Inside the shop have sayed to me...no problems with this MB !!!
    well  I try  , but I can't go UP  2800+  !!!
    I try and Try  with BIOS but no result.
    I have read with the last BIOS is corretc the right recognised 3Ghz+ cpu...
    I have update BUT always thesame.
    So I have read arround, this MB can't support CPU uo 3Ghz !...  so never 3,2   ...ok..but MY   not go up 2,8 !!!!
    BIOS setting....and here is the Myseriuos!!!
    FSB...I can't select UP 170 or the PC non start , amnd I must reset the cmos/bios!
    (200 I can't forget...I can work with 166.....)
    MOLTIPLIC.   I can set to x12.13      and My pc  (166 - x12.13) give 2800
    BUT....If i select   x14   I became 880 Mhz !!!  and if I set x 15  984 Mhz!!!!!!!
    Why  ?!?!?    this is sure a bios bug....

     impossible....sure NEVER He take back!!... later I used and Try....  sure I became in the...A..!  
       well IF this CPU is not supported  WHY work and to 2800 ?!? work or not work....
       and WHY x14 give the IDOT nummer 880 Mhz   and x15   980 Ghz ?   this is ONLY a BIOS problem....   to fixit!!!
    so..I not belive MSI have not to do, with this bios...

  • Post Code 9A Error, 990FXA-GD80, Bios bug

    After Bios B.40 i got same strange bug, sometimes when i load a oc profile my pc get stuck at 9A error and the only thing that i can do to recovery is use ctrl+home to recovery it, clear cmos is unless.
    After a lot of tests to try understand what was happening i got the answer.
    My CPU is a X3 710 (waiting for bulldozers) so i always use the unlock cpu core feature. I used this x3 with unlocked core for 2 years without any problem, so the locked core is good.
    If i load a oc profile with unlock cpu core feature enabled from a already unlocked stage, everyting is ok, but if my bios seting "unlock cpu core" is disabled and i load a oc profile with it enabled my pc do 6 beeps, restart and get stuck at 9A post code.
    I have sure that in Bios B.30 this wasnt happening.
    MB: MSI 990FXA-GD80 (MS-7640)
    BIOS: V11.5 (B.50)
    CPU: Phenom X3 710
    RAM: 2x2GB Corsair XMS3
    VGA: ATI Radeon HD 4890 (RV790) 1GB
    DISK1: 120 GB OCZ-VERTEX3 SATAIII SSD
    DISK2: 3TB Hitachi HDS5C3030ALA630 SATAIII HDD
    Optical Drive: SAMSUNG TSSTcorp CDDVDW SH-222AB SATA
    Power Supply: GenieX 800 Watts
    OS: WIndows 7 Ultimate Sp1

    Guy, did u see me asking anything about overclock?
    I was talking about a bios BUG that can damage the mainboard, and a lot of ppl cant recovery their bios like i did.
    I posted to help ppl with same issue and alert others to avoid it.
    I informed MSI about it using the right channel.
    Ty for help me bump this topic.
    Quote from: Fredrik on 26-September-11, 06:52:23
    Hello!
    Overclocking questions go somewhere else.
    If you don't absolutely need to update BIOS to solve a problem, resist the temptation.
    And if you do... Go back to the version that made you smile!  
    We ask people to state the max ampères the PSU can do. There is a list on the PSU box.

Maybe you are looking for