A Bug(?) discovered in AMI BIOS 3.A0

Hi everyone, this is my first post here although I've been browsing throught his forum for long...
I have an MSI 865PE Neo2-P PLS MS-6728 Motherboard, and have just flashed it with the new 3.A0 BIOS after the ridiculously unrealistic temperatures with 3.90,... But I've discovered a problem with it (or maybe my computer in this case), please help...
-> The problem is with the BIOS suspend/resume capabilities, I currently have the "StandBy" setting at S3/STR in the BIOS, so when I choose to suspend from Windows, the computer almost completely powers down.... That's great, and used to work with 3.90 and 3.80, but today I discovered this bug by accident...
---> I clicked Start > Turn off the computer > Suspend and watched Windows XP Pro's blue "Preparing to stand by...." screen, then the system suspended...
----------- Then a blackout occured while the system was suspended
------> Then when I press the power button the ATX chassis (after power was back on), the Green Power LED comes on, and all the fans spin up and I can see the D-LED bracket going through the first two phases:  "Early Chipset Initialization" and "Init Onboard Memory Size" (as documented by the 865PE manual)...
--> It does that in 2 seconds, then everything turns off (the fans stop, power LED goes off, CPU off...etc.), then it tries to turn on back again.... and so on, constantly looping the first 2 phases....so once I suspend the PC it cannot get back to normal mode....
--------> Through trial and error and eliminating any of my components to be the issue, I temporarily got it to boot by removing one RAM module and pressing Reset on the case, twice, then turning it off again, and re-inserting the RAM module, then power back on....
---> After that, I was able to reproduce the problem several times, with the same solution....(even tried to reset BIOS but same results)
------------> This has never happened before and I do not have any hardware issues, Did a MEMTEST86 for more than 12 hours with both modules and all tests pass (even the extended ones), also checked PSU: running fine...
--> I think this is a bug, please experiment with the BIOS and try to confirm if it exists....
---> Running Windows XP Pro updated with SP2...
---> 2x256MB PC3200 DDR-SDRAM Dual-Channel Mode (Slots 1 and 3)
---> 2.60C GHz Intel Pentium 4 CPU (Northwood core) 800 MHz FSB
---> MSI nVidia GeForce FX5200U 128MB AGP 8x (v3.0) Graphics Card....
---> 1x80GB 7200 RPM Western Digital Caviar ATA100 Hard disk drive....
---> ASUS CD-500S CD-ROM drive...

Please Help !!!
My problem has just got worse !!!
--> The day before yesterday (when I posted on the forum), I shut down the computer normally, and went to sleep....
----> Next morning, I wanted to boot the computer to check if the problem is still there, and to my surprise and extreme frustration, the board will ABSOLUTELY NOT BOOT no matter what I do !! I'm posting now from a CyberCafe since I can't get my PC started at all!!
-----> Details:
---> First when I turn on the PC for first time... The power and HDD LEDS come on and the fans just start to spin, then everything goes off.. (similar to before) but without looping.. Once it's off it won't turn on again (ie: won't respond to power button), to get it to turn on, I have to disconnect the mains and reconnect it, just to see it do that again after I press ON...
--> Checked D-LED, gives code for "Early Chipset initialization" before it turns off...
-----> Removed one RAM module (same trick before) and tried to boot ...
  > It's behaviour changed: When I press On, the power LED doesn't come on, but the HDD LED comes on (but without the HDD spinning up) and all the fans spin up and then it stays like that.... It does however respond to force OFF "Press OFF for 10 seconds", but once it's off it won't turn on again (as before)....
   > Checked D-LED... Gives 4 Red lights (System power on) and points to the CPU as the culprit, so I tried to reset the BIOS (clear CMOS jumper) and same problem...
    > So I started checking the CPU, I removed it and connected it again to no avail...., started checking the ATX12V connector...
      > Got some interesting results, when I first removed the ATX12V connector and tried to boot, it did behaviour number one (starts and then immediately turns off), but I booted it again anyway and got behaviour number two (HDD LED and all fans spinning and nothing)... Hmm that's strange....
       > Reconnected the ATX12V connector and tried to boot, same results...
Conclusion: The mainboard behaves the same way, whether the CPU is installed or not!!! That means either the PSU is gone, mainboard is gone or the CPU got fried, although I can't imagine how that could have happened as all the Voltage readings were within normal limits and temperatures were within my normal (43-57) temps.......
---> I have currently disconnected the PSU and will take it to a service shop to have it checked out, also thinking of disconnecting mainboard and taking it to place of purchase and see if it needs to be repaired and/or replaced......(I have absolutely NO idea how it got damaged in the first place !)
Another question:
  > How do I contact MSI's tech support (by email), I tried using their quirky method (via MSI LiveUpdate WebPage) but I don't think it got sent, since when you click "Send" it tries to send via "Outlook" and I don't have that configured or even use it (I use Yahoo! Mail).... can someone provide a direct mail address since I can't seem to find it on their website....
-----> Although I will go offline now in like 30 minutes, I will check the forums again tomorrow before I take any action...
---> Any feedback will be seriously appreciated...

Similar Messages

  • Xp 64 bit no longer works with AMI bios 1.2?!

    Hi,
    Having managed to get XP 64 bit working ok on my new machine I thought I should upgrade my AMI bios on my K8t Neo Fis2r MoBo.
    I upgraded from 1.1 to 1.2 and now XP 64 bit will not boot!
    It will work in safety mode but not normal, so I suspected a driver.
    Removed all the drivers and that did not work so I decided to reinstall the OS.
    And now during the OS setup it just hangs!!!!
    My bios settings are the same the only difference is the bios version.
    Has anyone else had this problem or got a soloution???
    System spec:
    CPU: Athlon64 3200+
    MoBo: MSI K8T Neo fis2r
    RAM: 2 x kingston cl3 512mb
    HDD: seagate 160gb SATA
    Video: PNY geforce fx 5600

    Quote
    Originally posted by threedaysdwn
    I posted about this last week when I discovered the Cool And Quiet problem.  Lots of people have encountered this problem and it took me a good 5 hours to figure it out... swapping every device I owned in and out of the computer.   After analysing the setup log I found that it was the CPU driver causing the problem.  And after that it wasn't long before I found the solution.
    I posted the solution to the Microsoft newsgroup and some other forums.  Glad to see your got yours working again.
    This appears to be related to MS having a nasty kludge to work around erratum93 (smm mode bug relating to the execution of the HLT instruction on stepping C athlons) included in XP64 which gets enabled at install time; please note I dont have any forensics to back this up at this stage as I havent had time to put any real effort into reverse engineering it, Im just presenting an opinion based on the facts I have observed in my tests.
    I have now succeeded in several installs of XP-64 on identically configured 1.1 and 1.2 bios systems; but in no cases has XP-64 survived a bios upgrade from 1.1 to 1.2 *unless* legacy USB (and all other sources of smm mode operation) were disabled, regardless of the Cool n Quiet issue.
    I am trying the 1.32 bios later today (as this apparently has a correct fix for erratum 93 *cough*aboutbloodytime*cough* included).
    err!
    jak.

  • AMI BIOS 2.2 Memory Settings

      Maybe it's just me, but I can't get the memory settings in the AMI BIOS 2.2 (MSI K8T-Neo FIS2R) to do anything.  Changes make no difference and the memory just runs at its SPD information every time (I'm using sandra to make this determination).  I've run memtest 86+ on this memory at lower settings (3-3-3-6-1T) with no problems.  In addition, A64 tweaker shows memory values as reserved values, so I can't tweak with it either.
    The system is perfectly stable (it should be, given that it's running at the most conservative settings possible).
    RAM is in slots 1&2 so it's not a DDR333/DDR400 1T/2T Athlon64 limitation.  I have an Abit Kv8-max3 that runs this memory fine at 2.5-3-3-6-1T. (Hate to say it, but Phoenix's award core is MUCH more feature rich than these AMI BIOSes)
      I didn't have this problem with the previous BIOS, but I'm a believer in running the latest, greatest BIOS. This statement is based on the 7 years I spent in x86 BIOS development at Compaq and Dell (while sempron D0 fix is all that's listed, I'd bet there's other subtle bugs resolved in the latest BIOS).  Push comes to shove and I'll just reflash the 2.1 or 2.0 BIOS, but I can't imagine that MSI would have just broken this in a recent BIOS release.

    There are a lot or reports on this Bios being broken. Just do a search for 2.2 Bios and see what is up.

  • SVET . can you modify AMI bios ?

    You enabled the overclocking features of my MSI a5000 bios.
    So, I have to ask you if this is possible........ ?
    I have an amd am2+ motherboard asus m3a78-em with AMI bios. It does not have northbridge frequency multiplier feature in bios.
    But, I think it is hidden and not enabled.
    The bios you can download below.
    Code: [Select]
    here is the m3a78-em latest bios:
    http://dlcdnet.asus.com/pub/ASUS/mb/socketAM2/M3A78-EM/M3A78-EM-ASUS-2701.zip
    I looked at the m3a78-em bios strings, and there is "0x03AD CPU/NB Frequency", which can also act like NB freq multiplier.
    there are also strings for speed values- 1000mhz, 1200,1400,1600,1800,2000.....2600mhz.
    How do you safely enable the cpu/nb frequency in bios ??
    I do not know how to edit the bios. Can you tell me how ?
    If it can be enabled, it should look something like this......... but up to 2600mhz.
    [Advanced>Jumper free configuration>CPU Ratio and voltage > CPU/NB Frequency]

    This is an MSI forum, not Asus, as such Svet does not modify Asus BIOS.
    Sorry, topic locked.

  • Msi Kt133 & Ami Bios

    Hi,
    I'd like to upgrade the bios of a KT133 motherboard, but is an AMI BIOS, and  i found nowhere an upgrade concerning this bios.
    The most recent bios found are Award Bios.
    Can i use them to flash my motherboard ? If not what could i do ?
    Thanks for the help .
    Cyz

    https://forum-en.msi.com/index.php?threadid=33939&sid=&hilight=6340
    https://forum-en.msi.com/search.php?searchid=274086&sid=
    you can try wadding through that lot
    there are several 6340 boards as well  it seems
    but i dont hold out a lot of hope

  • AMI BIOS 1.49

    Where can i download ami bios 1.49 for the msi k9n sli platinum.  I upgraded to 1.5 and im having hardware problems that worked with 1.49. So i want to revert back to 1.49.
    Thanks

    bios exact date? why not roll back to 1.40 official?
    there are allot of version but no such thing like 1.49.
    112,122,132,143,144,145,14A,14D,151

  • Ami Bios Flash

    I was in the process of flashing my 5.1 KT600 FISR AMI BIOS to the 5.2 release to hopefully fix the 20 second hang after POST as I am using a single SATA drive, but could not actually run the command to flash the bios.
    As instructed in the doc file, I made a Win98 boot disk and a disk containing the self-extracting file from the MSI website. Then I reset and booted up with the boot disk and copied the files from the disk containing the flash files to the ramdrive on c:\
    When I ran the exe file I was supposed to, it gave me a line about Command Usage, and the commands. But I couldn't for the life of me get any of these commands to do anything!!
    First, I typed in: DOSFLASH ROM_FILE /S    but just got I then realised that dosflash rom_file meant the exe file.
    So I typed: EXE FILE.EXE /S   (can't remember the exe file name right now), but all this did was refresh the exe and brang up the commands and command usage again.
    Am I doing this completely wrong?
    I also copied over the over file along with the EXE file, a .520 file- I guess this file is needed if you actually run the EXE with a command, which I didn't work out how to do!!!
    Can someone help me out?? Your help would be greatly appreciated!!
    Thanks
    Sam

    Best to ask somebody that did it before or use LiveUpdate....

  • K9AG Neo2-DIgital: AMI BIOS v1.7 has no AHCI setting

    Hi folks,
    I recently upgraded my K9AG Neo2-Digital AMI BIOS from its original version (I don't remember what exactly) to v1.7 (the latest available on the MSI website).  Before the upgrade I had three choices for the SATA mode: IDE, ACHI, and RAID.  Now the setting is called "RAID Mode" and the only choices are: IDE, RAID.
    What happened to the AHCI setting?  I've been doing a lot of reading lately, and there doesn't seem to be a shortage of people having problems with AHCI and this board.  Perhaps the latest BIOS simply disables it because of issues?
    Anyway, it's a bit of a bummer because I finally got the latest Vista x64 AHCI drivers from both Microsoft (msahci.sys) and MSI (ahcix64s.sys) slipstreamed into my Vista setup DVD so I could try to do a repair install and get Vista to work in AHCI mode.  I had originally installed it in IDE mode, and thought, hey why not try AHCI (or RAID in the future).  Now I can't even choose AHCI mode in the BIOS.  The original Vista install DVD wouldn't even load if I enabled AHCI in the BIOS - presumably due to the older msahci.sys drivers not supporting the SB600 at all.
    I tried RAID mode, and the RAID BIOS detected my existing Vista drive as 1+0 JBOD, and the Vista install DVD detected the Vista installation on the drive (after loading the ahcix64s.sys driver), but I don't see any Vista repair installation option.  This is off topic, but is there even such a thing in Vista?  I know XP has a repair install that will fix the OS but leave all your apps and settings in tact.
    I get the feeling that Vista and AHCI/RAID were just never meant to work with the SB600 :(
    Any thoughts?
    -Paul

     sharfe, no need to hijack a 2 year old topic. Please start you're own new topic.
          >> Please read and comply with the Forum Rules << 
          >> Posting Guide <<     

  • BIOS recovery process for HP systems with AMI BIOS?

    Hi,
    I'm trying to fix an HP a6718uk model PC which has an M2N78-LA motherboard and (I think) and AMI BIOS.  A BIOS update that came through HP Update has failed, and the machine will not boot.
    As it's out of warranty the HP Repair Centre want £200.00 to fix it, even though a simple BIOS recovery process should be sufficient - does anyone know the BIOS recovery process for these systems?   Everything I've read (not specific to these boards) says you should be able to put a BIOS update (called AMIBOOT.ROM) on either a floppy, CD, or USB memory stick, and boot holding down Ctrl-Home and it will perform the recovery, but I've not been able to get this to work successfully.  HP don't supply a standalone update so I've extracted the file from the BIOS update SP.exe on the HP support site.
    Any help would be most appreciated!
    Cheers,
    Andrew
    This question was solved.
    View Solution.

    Brilliant idea - I tried AMIBOOT.BIN and that didn't work, but then took the Hex Editor to the file - it's HPBIOS.ROM
    Renamed the file to HPBIOS.ROM and all now works.
    To recap for anyone reading the thread, this was from an HP machine with a corrupt AMI BIOS, to get it back, extract the ROM file from the SP.exe file from the HP website, rename it from VLE5.22 (or whatever the file is that ends in a numeric) to HPBIOS.ROM and copy onto a floppy diskette.   Put the floppy in the internal diskette drive (in my case a Sony OEM drive attached using a grey floppy ribbon cable) and boot the machine.  You may need to hold down Ctrl-Home, but not 100% sure.   After a long while the machine will give 4 or 5 beeps, and reset itself.  Once it's done that it will boot normally.
    Thanks for your help David - much appreciated.
    Cheers,
    Andrew

  • ICal Bug Discovered

    I just discovered a big bug thanks to my 80-year-old dad. The bug is a "year" bug in Birthdays from Address Book when subscribing to a published calendar through MobileMe.
    Okay, please bear with me as I attempt to explain this.
    For some reason the Birthday calendar (when turned on in iCal's preferences) won't sync over to my iPod Touch, iPhone and iPad. I posted help in this forum a while back in getting it to sync and user AAPL gave me a work around solution (http://discussions.apple.com/thread.jspa?threadID=2165278&tstart=0).
    Basically I had to publish my Birthday calendar and email the published link to myself. In my email on my mobile device I downloaded the calendar by clicking on the link and it would show in my iCal under subscriptions, giving me my Birthday calendar.
    Okay, now here's where the bug comes in. My father's birthday would never show up on my mobile devices but every other birthday I had in Address Book would show up. And the reason for that is because of the birth year in Address Book. Any birth year from 1932 and before will not sync over to mobile devices through MobileMe as a subscription to a published calendar. It will still show up on my Mac's iCal, however.
    Now I've had one other person try it on their Mac and iPhone and he too couldn't get any birthday before 1933 to show up on his iPhone.
    In all honesty, I really don't know where the bug lies, whether its iCal, Address Book, MobileMe or Apple mobile devices, but I do think this is a big bug that should be looked into by Apple.
    Jeff

    I assume that it has something to do with a 1900 vs. 2000 preference. I was setting the date and time on a device earlier this week and one of the choices was something to the effect of: "Use 20_ _ for any year ending before 32." I just looked but did not see any such setting for iCal or in the System Prefs but I might of overlooked it.

  • Bricked laptop b/c of a major bug in the W530 BIOS password!?

    I have purchased a W530 (model 2441CTO). I had to add a short/low security but convenient password to protect the BIOS. It that was exactly ** (star-star, easy to remember and fast to type on a French keyboard as it sits next to the Enter key). The BIOS accepted it  without any warning.
    Now when I reboot, the BIOS asks for the password. But it WILL NO MORE take into account any special character, including the stars, it just totally ignores them. I read (too late) that a dirty way around was to skip the special characters in the password. But in my case it leaves the password empty, and an empty password means read-only mode in the BIOS. By the way, it also does not check if the stored admin password is empty *before* it checks if the entered password is empty (a second programming mistake imho).
    I spent a lot of time trying to understand until I read about such an issue that dates back to 2009 !!!
    http://forums.lenovo.com/t5/SL-Series-ThinkPad-Laptops/Undocumented-problem-with-BIOS-password/td-p/...
    So my question is: what shall I do now?
    Send it back for an exchange?
    Would a BIOS upgrade (or downgrade+upgrade) bypass this one-way security?
    I am really upset by my 1775 euro brick featuring a 4 year warranty that gets half-bricked in a week or so. I just cannot understand how such an ugly and MAJOR bug could go through unfixed till 2013. This is really a serious hit to lenovo reputation.
    please do help!

    Empty password means no password. The discussion you reference is for an older machine where there was an option to make the bios settings visible but not changeable when there was a pw. I am not going to get into a discussion of how passwords are stored, but I will say that the data stored is encrypted and the date depends on the scan code of the key, so that a password can be entered on one type of keyboard and cleared on a different one.  The data stored for an empty password or no password is all zeros.

  • Bug discovered in LabVIEW 8.5.1 with reentrant VIs

    Hi NI,
    I discovered a bug with the way LabVIEW handles the state of front panel controls for reentrant VIs that have the front panel open during execution.  Essentially, what is happening is that the Boolean text on the FP button is not getting updated properly.  Sometimes it will update correclty, other times it won't.  This makes the bug intermittent.
    Please see the attached example code for a demo.
    Doing the following does NOT make the bug go away:
    reentrant_gui.vi --> VI Properties --> Execution --> Check "Clear indicators when called"
    Doing the following does make the bug go away:
    reentrant_gui.vi --> VI Properties --> Execution --> Select "Preallocate clone for each instance"
    However, in theory it should not be necessary to preallocate a clone since the FP values are wired into the vi before it is called (see the simple demo code).  Plus, for my application, I need to minimize the amount of RAM occupied by my program, so I don't want to preallocate clones for each instance.
    Cheers,
    Richard
    Attachments:
    lv_reentrant_bug_illustrated.llb ‏35 KB

    I'm running 8.6.1, and I see what I would expect, when I run your code
    Your instance:
    copies NUMERIC IN to NUMERIC OUT
    Copies its BOOLEAN's property BOOLTEXT.TEXT to STRING OUT
    Sets its BOOLEAN's property BOOLTEXT.TEXT from STRING IN
    Reads the BOOLEAN  (no effect)
    Waits 100 mSec
    You call two of these in a loop, one fed with the loop counter "i", and a string of "i", the other called with 0.0, and "blah"
    The first time up, I don't know what I'll get from the STRING OUT, it depends on what the BOOLTEXT.TEXT property is set to.
    The NARRAY 1 is labeled "should contain 0 to N", and it indeed should contain 0 to N-1, and it does.
    The NARRAY 2 is labeled "should contain all 0s, and it indeed should, and it does.
    The SARRAY 1 is labeled "should contain all OKs". but it really should  contain the strings "X","0',"1","2","3",... where X is indeterminate the first time up.
    The SARRAY 2 is labeled "should contain all OKs, but it really should contain all "blah"s, and it does.
    I don't know why you are expecting "OK".
    I see no bug at all. 
    Steve Bird
    Culverson Software - Elegant software that is a pleasure to use.
    Culverson.com
    Blog for (mostly LabVIEW) programmers: Tips And Tricks

  • Neo AMI bios Splash Screen?

    Is there any way to change the MSI splash screen on my Neo 875p (8xtreme graphic &c.)? My dell inspiron has a program for doing this, and it's a very cool feature. I was told by MSI that it can be done, but only for oem vendors. Has anyone stumbled across software for changing the splash screen on ami bioses? Moderators: maybe you can request the software from MSI?
    Thanks

    Yes, there is a way to put your own picture or logo in a bios. There are several programs and many steps to be taken in the process. Go to vp6-board.com and look in the hacked bios section. The links to all necessary programs are there and full instructions as to each step in the process. I have done this in the past on an Abit VP6 mobo I just retired a few days ago. Be SURE to follow all instructions! If you screw up your bios... since it isn't a plug-in type... I don't think Microstar will be any help to you or even badflash.com
    I don't recommend trying this unless you have mucho experience, and money to buy another board if ya make a mistake.

  • Podcasting URL font bug discovered...

    Hello folks,
    I have discovered a bug in GarageBand while video podcasting. When you create a chapter marker that uses a URL name & link - the final export to disk or send to iWeb messes up the URL font style, font size and font colour. When inspecting the final podcast in iWeb or Quicktime Pro the URL font is dark blue in colour and too small to see or click on.
    What is the purpose of this podcast feature if the URL font can't be edited ?
    The same holds true for still pictures from iPhoto as well if used in a podcast.
    If anyone from the GarageBand development team could discuss this problem that would be much appreciated - time is of the essence, no pressure...
    mac mini, mac book, mac book pro, imac, mac pro   Mac OS X (10.4.7)   podcasting

    Thank you WarriorAnt for your shout out.
    Since you've been around the GB forum for awhile maybe you have some constructive advice to share with my specific question. I hoped at least 2 people have tried the podcasting feature in GB 3.0 and perhaps have experienced the problems I outlined in my first post.
    Drop me a line if you come up with a solution or two.
    mac mini, mac book, mac book pro, imac, mac pro   Mac OS X (10.4.7)  

  • Current AMI Bios save instructions?

    Hi,
    1) Am running the KT4VL with 1.1 bios - using liveupdate 2, it does NOT detect the new bios that it available for KT4V boards...how' that :(
    I also tried MSI Live Monitor search capabilities and same issue - cannot detect new bios for the board...weird..I could flash it the manual way but I like how it was done when flashing the 1.1 bios using liveupdate2...
    2) Are there any instructions to save current bios out to disk/floppy for AMI? I like to save previous bios eventhough you can get them back from the site...just to be safe...
    Thanks,
    --fibo

    I can just add that I have always used the floppy method but then I also have a UPS. I don't trust the Windows LiveUpdate for BIOS.
    I see that my 1.3 disk that I created from MSI does setup a RAM disk and flashes from RAM (although that solves the bad floppy issue - it does not help if you lose power during the flash) - that's why I purchased a BIOS Savior (12 pounds from scan.co.uk), not sure about Official 1.4 from MSI as I now use beta's.
    The only flash I have seen fail was when I tried 1.52Beta into my Bios Savior (had to first flash 1.3 then 1.52)

Maybe you are looking for