MSI-6590 USB & Overclocking problem

Got two things for a real long time messed up on my computer:
the first: my keyboard (Logitech Internetkeys USB) won't always work when booting up when it is connected
the computer just boots etc but the USB port where it is plugged in (and others to) won't work anymore, but when i unplug it, press the powerbutton and just after less than a sec plug it in, it always works fine
sometimes it does work when it is plugged in, got this going on for like two years now... just wondered if it could be fixed in a simple way or that anyone recognizes the problem
(I'm running latest bios driver and VIA driver)
Second one: when i raise my fsb over 136 my system gets unstable or when I want to "save bios and exit" it just hangs, screen goes out, no image, no beeps, nothing, after resetting bios by shorting the two pins on my mainboard everything just works as normal
I know that 133fsb is the normal correct speed but as I am planning to buy a new board (the diamond series board) I wanted to know how far I could push this system
(I have a 350watt power supply, it came with the case (Codegen) the whole case incl PSU came at 59.9€ two years ago)
Hope someone can help me with either one of the probs
Grtz

just added the drive etc info on  my last reply srry I didn't think of that rightaway
Now you mention it, it really makes sence (or however you spell that word)   still strange tough that even after a while the usb ports won't "powerup"... But it is true that most times the thingy still works is when i reboot after about a few mins shut down, and transistors do tend to keep power for a while before the board is completely "powerless"
when resetting my keyboard also keeps working, gonna trie to boot with mouse (optical also logitech) disconnected, joystick disconnected, maybe my mouse consumes a bit to much when booting up when put all together? dunno, don't really know alot about voltage etc
PS: i am going to upgrade in about a month, but i will fetch me a new psu (because i'm planning on buying a diamond series board so 350watt just won't do it) and a new cooler that fits both sockel A and 939, my temps are ok, even at 136fsb when it's running stable temps is still same as normal +/- 40° on low usage, and +/- 52° at max usage, (depends alot on room temp but bottom line is: no high temps are the problem)

Similar Messages

  • MOVED: MSI X58A-GD65 Overclock Problem

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

    I bought the MSI X58A-GD65 because I am a complete moron who wanted a hardware Easy Switch.
    It works really well,but I was pissed when I noticed that my 12GB's of RAM was no longer recorgnized. Only showed 8GB's..............
    So I set the Easy Switch to deafualt ( 133 ) and decided to overclock the CPU and tweak the RAM.
    I just read every forum where people had problems w/ various settings, and since I only want 3.2GHz w/ 12GB's of RAM @1.4v it was a walk in the park.
    Clearing the CMOS after a day of torturing myelf and committing Human errors,I easily was able to simply undervolt the RAM from the 1.65v default,and raise the 133 default setting up by a factor of 5 and rebooting.
    So this is my first OVerclocking experience and MSI seems like a worthy board..
    I use this to perform hardware and virtual musical synths and instruments 6 nights a week.
    Since I cam from a solid 32bit DAW that ran 100% for 3 yerars,I didn't upgrade, but actually did an entire new rebuild since I wasn't sure ofthe stability in x64.
    But this DAW has worked for days on end now flawlessley.
    I Declare This Dog Will Hunt.............

  • MSI X58A-GD65 Overclock Problem

    Hi there,
    I have been trying to overclock my mainboard and it doesnt change my Clock Frequency, actually it changes but when I try to reboot system, it comes back to 133mhz again! I'm sure that it is not failure of overclocking, what should I do about this problem?
    Every detail can change but clock frequency...!
    I updated mainboard by the way to the last firmware.
    NOTE: I manually change frequency on mainboard to 200mhz. now Setup says 200 mhz, while computer starts, startup says 200mhz, in Windows, it says 133 mhz! even CPUZ says 133mhz!... what is going on :S

    I bought the MSI X58A-GD65 because I am a complete moron who wanted a hardware Easy Switch.
    It works really well,but I was pissed when I noticed that my 12GB's of RAM was no longer recorgnized. Only showed 8GB's..............
    So I set the Easy Switch to deafualt ( 133 ) and decided to overclock the CPU and tweak the RAM.
    I just read every forum where people had problems w/ various settings, and since I only want 3.2GHz w/ 12GB's of RAM @1.4v it was a walk in the park.
    Clearing the CMOS after a day of torturing myelf and committing Human errors,I easily was able to simply undervolt the RAM from the 1.65v default,and raise the 133 default setting up by a factor of 5 and rebooting.
    So this is my first OVerclocking experience and MSI seems like a worthy board..
    I use this to perform hardware and virtual musical synths and instruments 6 nights a week.
    Since I cam from a solid 32bit DAW that ran 100% for 3 yerars,I didn't upgrade, but actually did an entire new rebuild since I wasn't sure ofthe stability in x64.
    But this DAW has worked for days on end now flawlessley.
    I Declare This Dog Will Hunt.............

  • MSI 890GXM-G65 Overclocking Problems

    I have:
    MSI 890GXM-G65 motherboard
    4 GB OCZ PC3-16000 Platinum Edition memory (OCZ3P20004GK) runs at 1.95v and 2000 MHZ at 9-9-9-30
    Sapphire 5870 1 GB video Card
    AMD 955 Processor (Black Edition that runs at 3.2 GHZ)
    Without anything else overclocked I cant even raise my front side bus to 204 without it not posting at 16 multiplier.  203 post fine.  I upgraded Bios to 1.B.
    I have several other questions, but this is the first concern I have and that I would I like to address.  Hope my motherboard is not not "broken".  This is mainly just a thread starter and will get into more overclocking questions/problems later one...after addressing this issue.

    Here are my screenshots:
    Im sorry but I made a mistake.  Before I use the Control Center my Ram speed is around 1666 instead of 1706.  I get 1706 after I up the Front Side Bus in Control Center to 256.  Hope this didnt confuse any. 
    As far as the Hyper Transport speeds.  I am getting as you can see in the mid 2500's.  The Box and website show 2600.  So is this a misprint because you would think that 2600 would be out of the box instead of an overclock?
    My 12 volt rail is 70 amp.  I am using the 850 watt Kingwin MK Power Power Supply.
    And again another question that really hasnt been answered yet.  If I can overclock on the software side of things (Control Center) should't I be able to overclock on the hardware side as in bios.  For example I am getting 250 FSB on Bios, but I can only get up to 256 in Control Center.  You would think that if it works in Control Center is should work in Bios.  And this is a very Stable FSB too (after testing with 3dMark etc.)

  • MSI K9N2 SLI overclocking problem

    Having a slight problem here.  Had Bios 3.4 then updated to 3.5.  Noticed in Vista my CPU is at 3.2GHZ (stock), then everest and CPUid both show 3466Mhz.  No matter what I do in BIOS these numbers never changed.  BIOS was saying 3.5.  Decided to go back to BIOS 3.4 and am still having the same issue.  Any ideas?

    I put your name on the list there.  You found the thread where you posted already.  So its all good.  Feel free to discuss anything about the motherboard over there too.  I am trying to band a group together who have share the same motherboards as we run, so that it be easier to help out and share tips (overclocking, ram experience, etc).  Sorta like a tight knit family and for those who have hands-on knowledge with the board itself already.
    Quote from: Griplessoneder on 12-October-09, 03:55:26
    Sorry guys. figured out the problem, for some reason someone had changed the settings in the Nvidia control panel which is taking the complete control over the overclocking issue.  Now if I could just shut that ability off I would be happy.  Thanks for the help.  Raisethe3, you sent me a e-mail to join overclockers.net, I have joined overclockers.net but do not see a link to join this particular topic.  Will join as soon as I can find it.
    "Hi, I am writing this to gather all MSI K9N2 SLI Platinum users to share our appreciation for this board. As I have noticed from this message board, that you guys are owners of this board. We can share from our experiences (i.e. problems, discuss, rants, etc) and use to assist one another. We can have this central location and have support from one another especially people who run this specific type of board. Discussion can be anything related with this board (memory problem, cpu problem, boot-up, etc). We can all help each other out and assist when needed. No more scrambling to find help from other places! Come and join at http://www.overclock.net/amd-motherboards/589277-unofficial-msi-k9n2-sli-platinum-owners.html"

  • MSI VOX USB driver problem (XP PRO SP2)

    When I plug in the VOX to the USB Windows looks for the MSI MS8609 driver, but does not find it (even if it is installed). Then after a while it finds a driver called USB2800. I've tried to uninstall this an reinstall VOX SW but I can not change it into MS8609 !

    Have you tried installing the drivers from the MSI website?
    The drivers are available >>here<<.
    Also, make sure your motherboard drivers are installed properly and that there are no yellow exclamation marks in device manager as that would also explain why the sound card drivers won't install.

  • Re: MSI M510C Usb Boot Problem

    Hello , i contacted MSI support via e-mail and this is what they said me....
    Ticket: 
    Sound Blaster Cinema
    QuoteContent:...

     Personally I do think the problem could be with your RAM. You have 1.65V and specs call for 1.5V RAM. There are even some low voltage (1.35V) listed for that MB. 1 example is: HyperX 8GB (2 x 4GB) 240-Pin DDR3 SDRAM DDR3 1600 (PC3 12800) Desktop Memor...

  • MOVED: MSI P35 Neo, Overclocking problems

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

    Quote from: Maesus on 29-October-07, 11:52:50
    welcome to the forum.
    For overclocking question, please post in the OC forum.
    Maesus, Isn't that this forum?
    Adomax, I feel for you.
    I can only get about +10% out of the FX60 on my RX480 Neo2 (MS7151). :(

  • COM-port problem with MSI BToes USB Dongle

    I´ve had problem to get my Sony Ericsson T610 to work with my MSI BToes USB Dongle, so I tried to update my drivers. Now I have Microstar Bluetooth Software 1.4.2 build 10 but can´t get my Serial Port service to work. In Advanced configuration / Client Applications under "Bluetooth Serial Port" / "Properties", the only serial port I can choose is com0. Does anyone know how to fix this problem?
    /Peter

    Well, I think i´ve solved the problem. To get the com-ports to work I installed the software. Then I had a problem to get the phone to communicate with Sony Ericssons synk-software and outlook, but suddenly it worked and has worked since then. I have no idea what the problem was but now it works and I´m satisfied.
    /Peter

  • MSI RS480M2 - USB Problems - RS480M2 USB

    Anyone having any strange behavior using wireless USB kb and / or USB mouse on the MSI RS480 board?
    I have 100% failure rate using 3 different wireless keyboards... The only way to fix is to reboot the system which will reestablish the connectivity.  then in about 1-3 days I loose the wireless kb connection.  USB trackball mouse is fine except for some studdering.
    this is killing me - but I'm hopeful a bios fix or something related to my setup could be to blame.  Anyone? Moderators?  The MSI quality seems very very good.  Should I contact MSI support?
    I use bios rev. 3.2
    specs:
    a64 3200 939; msi rs480; corsair xms3200 1gb; x700pro 256mb; pioneer dvd108; wd 200gb 8mb cache; silverstone LC11 w/ 240W tfx w/ pfc, 3.3v @18A, 5v @19A, 12v @16A

    Quote from: dannol48 on 06-May-05, 05:34:47
    I do have a Logitech wireless keyboard and mouse, but have them connected PS/2.  I'll test them in USB when I get a chance.  I usually avoid USB when PS/2 ports are present.....It just seems to avoid problems.
    I haven't had any problems with the USB 2.0 Flash memory reader on USB internal.  No systems log errors to indicate any type of USB problem.  I've even booted from the Flash (I posted a thread on that result).  I tried a USB 1.1 CAM on all the ports front and back to verify they were working, but not any prolonged tests.  Sounds like more testing is needed.
    I have seen mention (during google searches on the chipset) of a possible issue with ATI's USB having problems.  ATI seems to have licensed alot of what's integrated on the SB400 from others, so I check who and what on the USB.  Drivers are always a possibility.  I do have XP-SP2 installed.
    Danno
    Edit:  OK...you guys got me concerned enough that I just switch to USB on keyboard and mouse.  They detected and installed fine.  I'll let you know if it fails in the next hour.  I'll try Sleep mode and return too.
    Edit2:  Sleep works...no problem other than it asks what I wanted to do when I hit the Sleep button on the keyboard.  I use a "giggle" on the mouse to return from sleep.  I looked at the USB vendor codes and they're ATI's.  It's using the standard generic SP2 drivers.  Other than waiting, any way to MAKE IT FAIL?  I will stay with USB for the next few days and report back any problems.
    Edit3:  Since there's no room in my profile, here's the link to my keyboard-mouse.
    http://www2.newegg.com/product/product.asp?item=N82E16823126131
    thx Dannol48,  I use logitech elite, memorex, msft black standard wireless, even a phillips wireless kb.  all work great... then after 1-3 days I need to reboot.
    I run MS XP MCE2005 w/ Ms remote + at least 4 other USB devices attached besides the wireless KB.  the usb trackball (MSFT thumb ball) mouse is attached via a USB hub I velcro'd to my couch.  I operate this 20ft away from the TV - which is the only display device.  I've loaded the OS 3X now trying to isolate if it's the OS w/ no change. 
    I've been using a very similar setup to above for about 4 years now. never had an issue like this.  It could be ATI issue... or BIOS?  i dunno.

  • Msi vox usb 2.0 remote/sound problems

    please help! i just purchased a new MSI VOX USB 2.0 external tv tuner and i'm having lots of problems...
    1. the dial on the side of the box that is supposed to turn the tuner on/off or change channels doesn't do a thing.
    2. the remote doesn't work at all
    3. sound - i'm using this on a notebook computer and i don't have a line in port. i assume i would be able to just go through the microphone port but it is not so. in the options under properties>device, i can only choose the audio input source to line in (which i don't have) or cd audio (?). it doesn't even work if i set my computer recording settings to 'microphone'... even though i CAN record the microphone input in a sound recording program, i can't hear in in real-time... right now the only way i can hear the TV is to connect the audio cable through my desktop's line in! i can't even hook my speakers directly into the box because the pin hole is too small to fit a normal audio jack...
    is my only solution to buy some sort of audio pin converter so i can hook my speakers/headphones directly into the box??
    i've downloaded the newest drivers and they don't help at all with any of my problems.
    i'm using a notebook computer with windows xp...
    please help! thanks very very much!!

    I had/have the same problem, with a Dell Laptop running windows XP.  
    my first solution was to buy a male-male audio connector and hook it directly to my speakers, but having to switch from that and my computer wasn't much fun, I found another work around.
    I bought snapstream's beyond TV, and everything has worked well, and I like the snapstream software better than the default software, anyway.  The only problem is that you can't use the composite or S-video inputs, as far as I can tell.  (and having to spend $50 on another piece of software, but use the trial version first to make sure it works)

  • MSI VOX USB TV BOX problem!

    i tried to use MSI vox usb tv box to my laptop (zt3340EA - Hewlet packart) i tried to install driver from CD but,installation fails and says : driver works only with SP1 (i m using SP2) i have downloaded newest driver from msi site ,still problem. Driver getting installed but my Laptop finds this as Uknown device,and MSIPVS says : no msi Device connected.
    Is there any Driver for this device working on M$ windows Xp Sp2?
    i have switched usb ports but device still unrecognized.
    this device was working great on another pc (xp,sp1).  Please Help me :(
    Nikos.

    Well, I got MSIVPS3 to recognize my tv box but I can't seem to get a lock down on any channels.  All i get is snow from every channel. No audio either.  Everything works peachy on my desktop running win2k but my laptop is where I need the video input from a camcorder.  Grrrr.  I think I wasted my money buying this P.o.S.

  • MSI 6590 K4-Ultra CMOS Problem.

    Hello,
    I have a problem with the MSI 6590 Motherboard, There is a problem with the CMOS Jumper.  If it is set to 1-2 the board will now power on.  There isno power going to the board.  If the CMOS Jumper is set to 2-3 the board will get power.  Has anyone had this problem, and if so how did you fix this problem, or does anyone have any suggestions on how to fix this problem.
    Thanks in advance...

    I see.
    My board also says 1-2 to keep and 2-3 to reset.
    When its on 2-3, and you change a setting in the BIOS, does it remain?
    To test this you must turn the PC off and back on.
    If it does then you could have made a mistake with the pin numbers.
    It is possible  
    Is something shorting?, try taking the board out and put in back in.

  • User guide: MSI HQ USB BIOS Flash Tool

    Guide based on USB tool v1.17c
    HOW TO properly use the MSI Forum HQ USB Flashing Tool to update your BIOS
    This user guide provides a step-by-step explanation for properly using the >>MSI Forum HQ USB Flashing Tool<< to prepare a USB Flash Drive for a safe BIOS-Flash in a pure DOS Environment. The tool itself will not perform the actual flashing operation.  It will "only" help you to get your USB Stick set up for an automated DOS flashing procedure which requires final confirmation.  (If you should run into any problems before you are prompted for final confirmation in DOS, no attempt to flash has been made yet and there is no danger of a bad flash.)
    NOTE: If you are having problems getting your USB device to boot correctly, you may need to format it correctly as the geometry data may be incorrect. You can do that by pickup option "Fix My USB key" from the Tool or by using >>> THIS <<< tool here! For future usage you can skip this step, it need to be done only once if your stick need adjustment.
    Symptoms that your USB key need a fix after booting from the USB key:
    * Error: "No bootable partition in table"
    * Blinking cursor in a top left corner and nothing happens
    * "RIVER2 MSI"
    * "Error loading operating system"
    * "Missing operating system"
    * "Disk in drive is not a bootable"
    * Booting from selected USB key is IGNORED, the other/typical OS continue to load as usual
    If still no change after using "Fix My USB key" Tool's option or HP Formatter Tool as alternative.
    Then try with different USB key, the issue is there.
    Note: Those USB keys who support "U3 Smart", this "feature" must be removed before proceed.
    Refer to followed link: http://u3.sandisk.com/launchpadremoval.htm
    Read the three notes that follow first before you move on:
    1. Note: Before you even think about flashing a different BIOS, be sure that your system is stable. If it is not stable, make it stable first. (Read >>here<<.)
    2. Note: Make sure your system meets the preconditions and system requirements mentioned below before you attempt to use the tool.
    3. Note: Do know that flashing your BIOS, be it with the help of the tool or otherwise, is done at your own risk.
    Contents of the Guide:
    0. Preconditions & System Requirements
    1. Basic Description of Functionality
    2. Installing/Starting the tool.
    3. Choosing a Preparation Method
      3.1. Method 1: Processing a BIOS Archive Directly (ZIP/RAR)
      3.2. Method 2: Processing a BIOS File Directly
      3.3. Method 3: SureHands Live Update
      3.4. Method 4: Geometry Change
    4. Selecting the USB Flash Drive for preparation
    5. BIOS Settings, Booting & Flashing
      5.1. BIOS Settings to Check
      5.2. Booting from USB Flash Drive
      5.3. Flashing Procedure/Running MemTest86+ & CMOS-Clear
    6. FAQ: Common Problems & Solutions
    7. Version History
    0. Preconditions & System Requirements
    The main precondition for using the tool is a working & healthy Windows installation on the system that needs the BIOS flash.  The Tool is designed to work with MSI Retail Boards & Laptops only.
    Please note mainboards of other brands and OEM boards that are manufactured by MSI but sold by Medion, HP, NEC and others are not supported. If you have an OEM board that needs a BIOS update read this topic: >>OEM boards manufactured by MSI<<
    Supported Operating Systems: All current Windows Versions (32bit & 64bit, any service pack (SP)): Windows NT, Windows 2000, Windows 2003, Windows XP, Windows Vista, and Windows 7.
    The second requirement is that you have a fully functional USB Flash Drive that uses the FAT file system (FAT/FAT32).  NTFS is not supported. If your USB Flash Drive is using the NTFS File System, reformat it to FAT or FAT32.
    As the tool also provides a Live Update Option ("SureHands"), you'll need a working internet connection if you want to choose this method. Not all boards are supported at this point.*
    * Check section 3.3 of this guide to see if your board is currently supported by the SureHands feature.
    1. Basic Description of Functionality
    The MSI Forum HQ USB Flashing Tool will help you to easily prepare an USB flash drive for an automated BIOS flash in a pure DOS environment, which is the safest way to perform such a procedure. The tool will also allow you to run MemTest86+ in a pure DOS environment. However, the preparation of your USB Stick is done in Windows and basically includes two steps:
    (1) The device will be made bootable.
    (2) All necessary files (incl. BIOS file, actual flasher and MemTest86+ executable) and all DOS commands that are needed to flash/test memory will automatically be implemented.
    Because the tool does not reformat your USB Flash Drive*, no files that may currently be on the stick will be lost during the procedure.  Just make sure that there is still some free drive space, otherwise there will not be enough room for the files that are needed for BIOS Flashing.
    * Excluding the Geometry Change method which will destroy all data on the USB storage device.
    2. Installing/Starting the tool
    Treat the forum's USB Flashing Tool like a regular application.  Download it to and run it from your hard drive, there is no need to copy & start it from the USB Flash Drive that you want to use for flashing.  Both, the installer version and the stand-alone version, do precisely the same job.  Which of the two versions you use, is solely up to you and your preferences.  The stand-alone version can be started directly by clicking on the executable file.  The installer version will perform an installation and provide you with an entry in your start menu and a desktop shortcut to start the tool.
    When you start the tool a DOS box should open up to provide you with status messages and prompts.  Do not close that box unless you want to abort the preparation procedure!
    Please ensure that you connect the USB flash drive you wish to use before starting the Tool!
    NOTE: If you do not connect your USB storage device before starting the tool, or the tool doesn't detect it. You can still insert the drive letter, as the tool will continue as normal.
    The tool will first check, if an MSI mainboard is installed in your system and show you its model name and PCB Version in a message box. Click >OK< to continue to choose the tool's preparation method that you want to use to prepare your USB Flash Drive.
    3. Choosing a Preparation Method
    If your MSI Retail Board is properly detected and you have pressed the >OK< button in the message box, an option box will pop up that allows you to choose between three different operating modes.  The options you can choose from are more or less self-explanatory, however, read the detailed description if you are unsure how to proceed at this point:
    3.1. Method 1: Processing a BIOS Archive Directly (ZIP/RAR)
    Official MSI BIOS-Updates that can be downloaded from the product site of your board model do usually come as .ZIP or .RAR archives that contain the actual BIOS File and the corresponding AWARD or AMI flashing utility (depending on the BIOS Type of your board).  If you have downloaded such an archive, you should choose the first method from the option box. 
    You do not need to extract the files from the BIOS archive.  The tool will ask you to point it to the archive you downloaded and automatically extract the BIOS File and the AMI or AWARD flashing utility and put it them on your USB Flash Drive.  You don't have to worry about anything else.  All you have to do is to remember where you saved the ZIP or RAR file you downloaded:
    3.2. Method 2: Processing a BIOS File Directly
    If you do not have a ZIP or RAR archive that already contains a BIOS File and the proper flashing utitility, but only the plain unpacked BIOS File, choose the second Method from the option box.  In most cases BETA BIOS Files supplied by MSI Support or shared here in the Forum do not come with the proper flashing utility.  If the MSI Forum HQ USB Flashing Tool is told to process a plain BIOS File, it will automatically check the type of BIOS File (AMI or AWARD) and then select the proper flashing utility that needs to be used.  All you need to do is point the tool to the BIOS-File that is supposed to be flashed:
    3.3. Method 3: SureHands Live Update
    "SureHands Live Update" is the third operation method you can choose from the option box.  It provides a much safer and more reliable alternative to MSI Live Update as the actual BIOS Flash is performed in a pure DOS environment as well.  If you decide to use this option, you do not to supply the tool with a BIOS-Archive or a BIOS-File.
    Not all MSI Retail Boards are currently supported.  With every update of the USB Flashing Tool more boards will be added.  At present, you can use the "SureHands" Live Update method with the following boards only (the list will be updated regularly):
    AMD based boards:
    K8N Neo4-F (MS-7125, PCB 3.0)
    K8NGM2-FID (MS-7207, PCB 2.0)
    K8N Diamond Plus (MS-7220, PCB 1.0)
    K8N Neo3 (MS-7135, PCB 1.0 & 2.0)
    K9A Platinum (MS-7280, PCB 1.0)
    K9A2 Platinum (MS-7376, PCB 1.0)
    K9A2 CF-F (MS-7388, PCB 1.0)
    K9N Neo-F (MS-7260, PCB 1.0 & 2.0)
    K9VGM-V (MS-7253, PCB1.0)
    K9N2GM-F V2 (MS-7509, PCB 1.0)
    K9N Neo V2 / V3 (MS-7369, PCB 1.1)
    K9N Platinum & K9N SLI Platinum (MS-7250, PCB1.0)
    K9N2 Diamond (MS-7375, PCB 1.1)
    K9N2 SLI Platinum (MS-7374, PCB 1.1)
    K9N2 Zilent (MS-7374, PCB 1.1)
    K9N2 Neo-F (MS-7511, PCB 1.1)
    DKA790GX Platinum (MS-7550, PCB 1.1)
    790FX-GD70 (MS-7577, PCB 1.0)
    790GX-G65 (MS-7576, PCB 1.0)
    Intel based boards
    HydroGenX48C & X48C Platinum (MS-7353, PCB 3.0)
    X48 Platinum (MS-7353, PCB 1.0)
    X38 Diamond Plus
    X38 Diamond (MS-7353, PCB 1.0)
    X38 Platinum (MS-7353, PCB 1.0)
    EFINITY-FP (MS-7395(E), PCB 1.0)
    P35 Neo Combo-F (MS-7365, PCB 1.0)
    P35 Neo2 Series (MS-7345, PCB 1.1)
    P35 Platinum (MS-7345, PCB 1.1)
    P35 Neo-F (MS-7360, PCB 1.0)
    G33 Platinum (MS-7345, PCB 1.1 & PCB 1.2)
    P965 Platinum (MS-7238, PCB 1.1)
    975X Platinum PowerUp Edition (MS-7246, PCB 2.1)
    865PE Neo2-P Platinum Edition (MS-6728, PCB 2.0C)
    P7N SLI Platinum (MS-7380, PCB 1.0)
    P7N2 Diamond (MS-7523 PCB 1.0)
    P7N Diamond (MS-7510, PCB 1.0)
    P7N SLI Platinum (MS-7380, PCB 1.0)
    P6N Diamond (MS-7320, PCB 1.0)
    P6N SLI Platinum (MS-7350, PCB 1.0)
    P6N SLI-FI (MS-7350 PCB 2.0)
    P6N SLI V2 (MS-7346 PCB 1.0)
    ECLIPSE SLI (MS-7520, PCB 1.0)
    ECLIPSE Plus (MS-7566, PCB 1.0)
    P35 Neo3-F (MS-7395, PCB 1.0)
    After selecting "SureHands" from the option box, the tool will automatically check for all available official BIOS-Versions for your mainboard.  It will also look for the latest available BETA BIOS Version for you board and save that information in a TXT-File on your Desktop:
    Note: The SureHands option will not provide you with the latest BETA BIOS, it will only provide the information.
    When the tool is done scanning for official BIOS releases for your board, it will give you the possibility to manually choose the BIOS Version you want to flash.  SureHands Live Update will not automatically select the latest version and use it for flashing, it will give you the chance of choosing between all available official BIOS releases that are available:
    Note that the "May not exist" comment that appears behind some versions does not mean that the BIOS does not exist.  If you know the latest BIOS for your board is e.g. v1.8, SureHands will retrieve it even though there may be such a comment.  That message is part of a prediction feature that tries to determine future BIOS Releases.  If a BIOS version that was predicted by the SureHands feature is not available yet, the tool will tell you if it cannot retrieve the files and ask you to select an earlier version.
    3.4 Geometry Change
    If the tool fails to make your USB storage device bootable then you will need to use this mode. It will make your drive bootable, select it:
    Select your drive then let the tool do it's business.
    Once the process is complete, run the tool again via method 1, 2 or 3, restart your computer and try booting from the USB storage device again.
    NOTE: This method will destroy ALL data on the USB storage device!
    NOTE: This method is available in v1.17 and beyond.
    4. Selecting the USB Flash Drive for preparation
    When you have chosen one of the three methods from the option list and pointed the tool at the corresponding archive, BIOS File or selected the desired BIOS Version from the list in case you chose to use SureHands Live Update, the MSI Forum HQ USB Flashing Tool will prompt you to enter the drive letter of the USB Flash Drive you want to use for flashing:
    Note that certain drive letters are reserved and will therefore not be accepted by the tool (currently A:, B: and C:). If you are sure you have connected an USB Flash Drive to the system that works properly but it does not appear in the table that appears in the DOS box, enter the corresponding drive letter anyway and see if the tool accepts it.  This can happen in rare cases, but it is usually no problem.
    The tool will check the selected drive and will provide you with status messages.  If everything is okay, the message should look like this:
    The tool will attempt to make the device bootable and automatically write all files that are needed for flashing to the drive to prepare it for flashing.  If the procedure was successful, you will get the following message in the DOS box:
    5. BIOS-Settings, Booting & Flashing
    If the Tool has prepared your drive for booting & flashing, no BIOS flash attempt has been made yet. Only the preparation process. In order to initiate the flashing procedure, you have to restart your system and make it boot from the USB Flash drive. Before you move on to do that, enter the BIOS Setup and check a few options:
    5.1. BIOS Settings to Check
    Check USB-related Options in BIOS:
    - USB Controller
    - USB 2.0 Controller
    - USB Legacy Support
    - USB Storage Support
    - Boot from other devices
    - etc.
    Not all of these options may be found in BIOS and the precise name may vary as well.  Just make sure you checked for such options and that they are enabled (if present).
    Another option you should check for is "Boot Sector Protection".  If such an option is present in your BIOS, make sure it is disabled because it may make a BIOS Flash impossible.
    @all Overclockers: In case your system is currently overclocked, make sure you roll back to default clock and voltage settings before you attempt to start the flashing procedure. Otherwise you increase the risk of an unsuccesful flash, and you most probably don't want something like that to happen.
    5.2. Booting from USB Flash Drive
    To boot from your USB drive you can either change the boot sequence in BIOS accordingly or just press F11 during POST* to get access to the BIOS Boot Menu.  From here, you can select you drive directly without having to adjust the boot sequence in BIOS.  Note that your USB Flash Drive may be listed as a hard drive (if you choose that entry you will get another list to choose from).
    * Not all mainboards use F11, for the boot menu. If F11 fails for you, please consult your manual for the correct key.
    Note: If you have problems booting from your drive, look at the FAQ-Section of this guide and see if any of the tips resolve the issue.
    5.3. Flashing Procedure/Running MemTest86+
    As soon as the system boots from the drive, DOS will be loaded and you will be displayed with two options. One option will start MemTest86+, the other will begin the flashing procedure. If no choice is made, MemTest86+ will automatically start.
    The flashing procedure will automatically be initiated from there.  You will see status messages on the screen that will supply you with information and also prompt you for final confirmation for the actual BIOS-Flash.  A backup of you current BIOS will automatically be saved to a file on the drive (backup.bin) before the flashing actually starts.  You do not need to enter any commands in DOS.  All you have to do is acknowledge the information on the screen by pressing a key.
    The flash itself will only take a couple of seconds (20-30s at the most).  If the flashing is successfully completed, shutdown the system and clear CMOS with main A/C power cable removed from PSU.  Read the >>Clear CMOS Guide<< for further information. 
    After clearing CMOS you have completed the BIOS-Flash. 
    Guide created by Jack The Newbie and the forum team

    Version updated to 1.18x:
    * Mode 3 Sure Hands, Live Update:
    - Removed beta BIOS query check[global]
    - Fixed issue K9N2 Diamond unable to be detected as supported unit if onboard is installed BIOS version 2.4,
     add dynamic detection for future versions.
    - Fixed issue 790FX-GD70 unable to be detected as supported unit and add dynamic detection for future versions.
    - Fixed issue 790GX-G65 unable to be detected as supported unit and add dynamic detection for future versions.
    - Add support for 785G-E65, add dynamic detection for future versions, prediction BIOS range 3.1 - 3.A
    - Add support for 785G-E53, add dynamic detection for future versions, prediction BIOS range 3.1 - 3.A
    - Add support for 790GX-G65 Winki ED, prediction BIOS range 2.1 - 2.A
    - Fixed issue P7N Diamond unable to be detected as supported unit if onboard BIOS installed is 1.3 and above,
     add dynamic detection for future versions.
    - Add support for K9A2 Neo2, prediction BIOS range 7.4 - 7.D
    - Add support for 790XT-G45, prediction BIOS range 2.2 - 2.B
    - Add support for 770T-C45, prediction BIOS range 8.4 - 8.D
    - Add support for 770T-C35, prediction BIOS range 8.4 - 8.D
    - Fixed issue K9A2 Platinum[V1,V2] unable to be detected as supported unit if onboard BIOS installed is 1.9,
     add dynamic detection for future versions, prediction BIOS range extended to 1.F0
    - 790GX-G65 board prediction BIOS range extended to ver: 1.D0
    - 790GX-G65 board update bios base ver from 1.xx to 4.xx [following new msi rule for this board jumping from 1.xx to 4.xx]
    - Add support for 770-C35|C45 boards [p1] BIOS range 1.40 - 1.D0
    - Add support for 770-G45 board [p2] BIOS range A10 - AA0
    * Add "Exit" option to navigation screen
    * Update version info related to boot part
    * Update boot part to handle newest features
    * Modify Self update sequence of Installer version
    * Update internal version check ID
    * Mode 4 minor update
    * Build and add new Tool's module for newest features
    * W32 Tool's exit time part decreased by 10 seconds
    * On received OS reboot user request, time delay before execution decreased by 15 seconds
    * Update EC decoder
    * Update start-up information screen
    * Auto store start-up detected information to user's desktop ==> [MSIHQ_INFO.TXT]
    Details:
    Easy to show machine information on request, instead write down from the screen manually, now just copy/paste can be used from MSIHQ_INFO.TXT
    User can check and compare information before and after the BIOS update
    Also usefull if didn't remember what was his original BIOS or EC versions before the update, Tool will auto store it there.
    And easy can be checked if needs. E.g Tool's log file of each Tool's execution, each report will include date and time as well.
    F.A.Q example:
    Q: I flashed BIOS on my notebook and now it doesn't work properly.. And i don't remember what was my old BIOS version.. What can i do?
    A: Take a look in MSIHQ_INFO.TXT at your desktop, there is auto recorded your detailed information about your notebook before the BIOS update.
    So you can easy find what was your original BIOS & EC versions.
    Is it OEM one or not, and the exact original BIOS & EC versions.
    So you can roll back easy or if crossflashing were done to reflash to correct versions.
    Example question:[this board now use 4.xx bios, but don't have time to make a new images.]
    It's just example, do not mean that this BIOS used in the example is bad. But generally often can need to roll back to older version.
    Or to use Sure Hands because[The BIOS is N/A for manual download, By SureHands no need to browse/search/download and point to the BIOS version, also eliminate any chances to pickup the wrong BIOS, and not at last its more quickly[save a time]]
    Q: I flashed my BIOS via MSI Live Update, but the new BIOS has an issues.
        How i can roll back to my old BIOS version?
        The MSI LiveUpdate can only update to the latest BIOS version, which is not good for me.
        And i can't download my old BIOS version manually... Because "This BIOS can only update via Live Update function"
        http://eu.msi.com/index.php?func=downloaddetail&type=bios&maincat_no=1&prod_no=1739
        How i can re-flash to my original BIOS version and from where can i get it?
    A: Run >>Use the MSI HQ Forum USB flasher<<,
    then choose Mode 3 [Live Update{aka SureHands}]:
    MSIHQ: Information detected by MSIHQ Tool ver: 1.18x
    MSIHQ: Report generated in ба 30.12.2009 Ј. at 21:09:45,15
    Mainboard:  790GX-G65 (MS-7576)       
    PCB Version:  1.0
    BIOS Version: V1.3
    BIOS Date:  05/08/2009
    MSIHQ: Information detected by MSIHQ Tool ver: 1.18x
    MSIHQ: Report generated in ба 30.12.2009 Ј. at 21:22:38,42
    Mainboard:  790GX-G65 (MS-7576)       
    PCB Version:  1.0
    BIOS Version: V1.6
    BIOS Date:  11/30/2009
    Then choose your old BIOS version from the list:
    The followed image used below is a sample from Eclipse board,[no time to make accurate image] but will look similar for others boards too:
    In a list will be noticed that there is a future BIOS versions.
    Some of them will be not released yet. If you pick some of those the Tool will note you:
    It's a part of Tool's BIOS prediction system called "Crystal Ball", when MSI release a future BIOSes for your board,
    Tool can find them immediately. By that way the Tool no need to be updated to be actual in each moment
    * Add new feature "True BIOS Version Ready"
    - Updated Mode 1
    - Updated Mode 2
    - Updated Mode 3
    Details:
    Q: What "True BIOS Version Ready" means? Does the Tool show the wrong BIOS version until now? 
    A: Of course not, the Tool always show accurate info.
    The same as CPU-Z/Everest of whatever other Tool.
    However Tool also detect EC-FW versions for notebooks:
    The "True BIOS Version Ready" Tool's feature is aimed to eliminate user's mass confusion about MSI BIOS versions.
    And not only users are confused, but MSI's Live Update is confused too... which confuse users even more..
    Few typical real examples of confusion:
    "K9A2 CF wont flash to Bios v. 1.A !!!" 
    Quote from: Fingon on 25-October-09, 16:53:15
    Hi MSI,
    I have a problem. I have bought a new processor: AMD Phenom II x545. I looked on the support page of my MB (MSI K9A2 CF) and there the CPU is supported from the bios version 1.A. So I wanted to flash the Bios the the newest version (1.A). I used the MSI live update 4 program to flash it via windows mode. But everytime it boots it writes "CMOS checksum BAD", then I hit F1 to Bios and I see the version of my BIOS fell to the oldest version 1.1. Then I tried to flash it thru Flash disc (with boot files) and dos mod. The result is the same. I can flash my MB to version 1.8 but when I try the 1.A it wont flash it and my Bios fell to the oldest version (1.1). I realised that the exe files in version 1.1-1.8 are the same (afud412.exe) but the exe file in 1.A is different (afud4310.exe).
    My questions are:
    1) How to flash my MB to the version 1.A ?
    2) Is version 1.A really needed for AMD Phenom II x545? I guess yes, because CPU was avaible in July 2009 and the bios 1.A went out in June 2009. I am able to flash it only to version 1.8 (december 2008).
    Thank you for any help!!
    EDIT: After reading this topic: https://forum-en.msi.com/index.php?topic=129204.0 I realised I have the VERSION 1 of this board (I purchased it right after the launch of the MB (November 2007). It means it doesnt support CPU over 95W, but my Phenpom II x545 has only 80W. I still cant update Bios to the 1.A version.
    So my third question is:
    3) Is the Bios update 1.A only for version 2 of this MB?
    Thx for replies!
    Quote from: Jack t.N. on 25-October-09, 17:16:16
    A CMOS Checksum error is normal and expected after a BIOS Flash and/or a CMOS Clear.  The fact that this message appears, shows, that there was actually something programmed to the chip.
    If you haven't done that yet, please clear CMOS with the main A/C power cable removed from your PSU and load "Optimized Defaults" in BIOS Setup.
    The BIOS Version should be shown on the POST Status Screen and there should be a date behind it.  Please check the BIOS Date and write it down:
    Are you absolutely and entirely sure that what you see is "1.1" and not "1.10"?  Because v1.A0 is actually just the hexadecimal notation for v1."10" (one dot ten).  The hexadecimal notation is only used in the BIOS File Ending.  Once flashed, the BIOS will not identify itself in hexadecimal notation but in decimal code (which means you will never see "v1.A0" after the flash but "v1.10" instead.
    Here is a piece of well-meant advice for now and the future:  MSI Live Update should be avoided under all circumstances when it comes to BIOS Updates and/or information retrieval regarding your current BIOS Version.  Why?  Because this tool is stupid and one of there most risky applications for performing a BIOS Flash.  Please uninstall it completely.
    Why do I call it stupid?  I call it stupid because it does not differentiate between hexadecimal notation and decimal notation.  It will show you that "v1.A0" is available.  The it will flash it, if you allow it to do so.  Of course, a v1.A0 Version will always come out as "v1.10" (one dot ten).  When you re-run MSI Live Update it will not recognize that v1.A0=v1.10 and tell you again that there is a newer version available (1.A0, which, again, is the same as v1.10, which was just properly flashed).
    I believe that the update went just fine, that you are currently using v1.A0=v1.10 and that MSI Live Update is actually just creating a pseudo-problem which is currently confusing you.  The pseudo-problem will immediately be out of the world, if you uninstall MSI Live Update and rely on the BIOS ID String as it appears on the POST Status Screen (this includes the date shown there).
    If a BIOS Update should ever be necessary again, please make sure that you won't use MSI Live Update but >>Use the MSI HQ Forum USB flasher<< instead.
    Quote from: Fingon on 25-October-09, 18:03:44
    Thank you for the quick reply!!
    Thats exactly what I have JUST found in this post by Svet: https://forum-en.msi.com/index.php?topic=127672.msg974800#msg974800
    Yes it is 1.10 of course!! I didnt know that 1.10 = 1.A0 ! Thank you for the reply. Then the MSI live update 4 program is dump that he wanted from me another update of Bios.
    So thank you! Problem is solved. 
    Edit: Yes, because of MSI live update I learned how to flash bios via flash disc. :-) But I was still confused by that 1.10 and of course by program saying me I should update again.. :-P
    Quote from: Lostsoul777 on 14-August-09, 05:46:25
    I had the same problem with 1.90 bios, so i updated to 1A, i just want to know why Bios Version says: v.1.10 instead v.1A?
    Quote from: LinuxGuy on 29-December-09, 01:17:45
    My computer does not have a floppy drive.  How do I update the BIOS?  (I tried the online utility 3 times.  It always updates the BIOS "successfully" and when I restart my PC, I have to do either F1 to config or F2 to load setup defaults.  So it looks like it's working, but the online update says that I have versions H.10 and version H.A0 is available (or maybe the other way around).  So either the BIOS is getting updated, but the online tool is not recognizing this or it's not getting updated.  Either way, I would like to manually flash it in DOS.  Is it safe to burn the setup files to CD and boot from CD into DOS?
    That's the same BIOS version... Just the "MSI Live Updater" is not very smart...
    H.A=H.10=17.A=17.10 [A=10, H=17], the last "0" suffix in H.A0 means its official version.
    Quote
    I tried the online utility 3 times.  It always updates the BIOS "successfully" and when I restart my PC, I have to do either F1 to config or F2 to load setup defaults.
    So it looks like it's working, but the online update says that I have versions H.10 and version H.A0 is available (or maybe the other way around).
    So ignore this MSI Live Updater's no sense, and stop flashing your BIOS. You already have the latest version installed.
    The Tool now will detect and shows BIOS versions alias when the MSI BIOS version is known with more than one name.
    So no more flashing and flashing and flashing to the same version because of MSI LiveUpdate suggest again BIOS update...
    Also no more confusion:
    "What's my BIOS version?" -> I flashed my BIOS to 1.A0 [A7520IMS.1A0], but BIOS says its 1.10
    And MSI Live Update also says that i have 1.10 and 1.A0 is available and i should update it. I flashed it again, but its still 1.10?
    What's going on?
    Just run the MSIHQ USB Flash Tool and will show you all that you need to know
    Examples[with real/accurate info]:
    MSI Eclipse:
    BIOS version 1.9:
    BIOS version 1.10:[Tool now shows both BIOS versions alias]
    Report stored respective in MSIHQ_INFO.TXT at user's desktop:
    MSIHQ: Information detected by MSIHQ Tool ver: 1.18x
    MSIHQ: Report generated in ба 30.12.2009 Ј. at  5:30:55,34
    Mainboard:  Eclipse SLI (MS-7520)
    PCB Version:  1.0
    BIOS Version: V1.9
    BIOS Date:  09/22/2009
    MSIHQ: Information detected by MSIHQ Tool ver: 1.18x
    MSIHQ: Report generated in ба 30.12.2009 Ј. at  5:37:25,66
    Mainboard:  Eclipse SLI (MS-7520)
    PCB Version:  1.0
    BIOS Version: V1.A (aka Version: V1.10)
    BIOS Date:  10/27/2009
    More examples =>K9N6SGM-V / K9N6PGM-FI / K9N6PGM-F :
    More examples =>945GCM5-F V2 (FSB 1333) :
    Report stored respective in MSIHQ_INFO.TXT at user's desktop:
    MSIHQ: Information detected by MSIHQ Tool ver: 1.18x
    MSIHQ: Report generated in ба 30.12.2009 Ј. at  5:47:34,35
    Mainboard:  MS-7267
    PCB Version:  4.0
    BIOS Version: VH.9 (aka Version: V17.9)
    BIOS Date:  11/20/2008
    MSIHQ: Information detected by MSIHQ Tool ver: 1.18x
    MSIHQ: Report generated in ба 30.12.2009 Ј. at  5:52:46,26
    Mainboard:  945GCM5-F V2  (MS-7267)
    PCB Version:  4.0
    BIOS Version: VH.A (aka Version: V17.10)
    BIOS Date:  06/02/2009
    More examples =>780GT-E63 [N/A at MSI web yet] :
    For MSI Notebooks such decoding isn't need, examples:
    * Add new feature "Triple BIOS flash Recovery Ready"
    - Updated Mode 1
    - Updated Mode 2
    - Updated Mode 3
    Details:
    The feature include 3 auto prepared BIOS backups for followed purpose:
    * Internal BIOS recovery:
     - In a failure case Tool perform auto flash recovery [3 attempts, check for success after each and stop flashing if successful] before give control to BK_IO2, notice users about results and give control for manual attempts[if need]. [This a case if system isn't lockup/reboot, if bad flash occur]
     - This mode also have own store up to 5 backups[+1, the last saved copy is always backup.bin, if there was older one they become backup1.bin .. till 5]
    * BIOS backup stored as AMIBOOT.ROM [AMI BIOS only] [Auto clean up older if there is any, before take a new backup to avoid recovery confusion]
    * BIOS backup detected and stored for M-Flash style boot/recovery [AMI BIOS only] [Auto clean up older if there is any, before take a new backup to avoid recovery confusion]
    Performing test simulations with random generated BIOS versions[including betas] for M-Flash boot/recovery style, some examples:
    Copy/paste Tool log file:
    MSIHQ: Information detected by MSIHQ Tool ver: 1.18x
    MSIHQ: Report generated in 03.01.2010 г. at  7:00:53,46
    Mainboard:  945GCM5-F V2  (MS-7267)
    PCB Version:  4.0
    BIOS Version: VD.XB2 (aka Version: V13.33B2)
    BIOS Date:  06/02/2009
    Co-respond BIOS backup created  ==> A7267IMS.DX2 
    Where:
    * V13.33B2 ==> MSIHQ Tool detection [The same as CPU-Z, Everest]
    * VD.XB2 ==> MSIHQ Tool "True BIOS Ready" detection feature
    * A7267IMS.DX2 ==> MSIHQ Tool BIOS recovery created by "Triple BIOS flash recovery Ready", part M-flash boot/recovery [1/3]
    MSIHQ: Information detected by MSIHQ Tool ver: 1.18x
    MSIHQ: Report generated in 03.01.2010 г. at  7:12:23,95
    Mainboard:  945GCM5-F V2  (MS-7267)
    PCB Version:  4.0
    BIOS Version: VK.VB7 (aka Version: V20.31B7)
    BIOS Date:  06/02/2009
    Co-respond BIOS backup created ==> A7267IMS.KV7 
    Where:
    * V20.31B7 ==> MSIHQ Tool detection [The same as CPU-Z, Everest]
    * VK.VB7 ==> MSIHQ Tool "True BIOS Ready" detection feature
    * A7267IMS.KV7 ==> MSIHQ Tool BIOS recovery created by "Triple BIOS flash recovery Ready", part M-flash boot/recovery [1/3]
    MSIHQ: Information detected by MSIHQ Tool ver: 1.18x
    MSIHQ: Report generated in 03.01.2010 г. at  7:18:34,46
    Mainboard:  945GCM5-F V2  (MS-7267)
    PCB Version:  4.0
    BIOS Version: V3.9
    BIOS Date:  06/02/2009
    Co-respond BIOS backup created ==> A7267IMS.390 
    Where:
    * V3.9 ==> MSIHQ Tool detection [The same as CPU-Z, Everest]
    * MSIHQ Tool "True BIOS Ready" detection feature isn't need here, since this BIOS version can be known only with one name.
    * A7267IMS.390 ==> MSIHQ Tool BIOS recovery created by "Triple BIOS flash recovery Ready", part M-flash boot/recovery [1/3]
    MSIHQ: Information detected by MSIHQ Tool ver: 1.18x
    MSIHQ: Report generated in 03.01.2010 г. at  7:22:24,04
    Mainboard:  945GCM5-F V2  (MS-7267)
    PCB Version:  4.0
    BIOS Version: V8.1B9
    BIOS Date:  06/02/2009
    Co-respond BIOS backup created ==> A7267IMS.819 
    Where:
    * V8.1B9==> MSIHQ Tool detection [The same as CPU-Z, Everest]
    * MSIHQ Tool "True BIOS Ready" detection feature isn't need here, since this BIOS version can be known only with one name.
    * A7267IMS.819  ==> MSIHQ Tool BIOS recovery created by "Triple BIOS flash recovery Ready", part M-flash boot/recovery [1/3]
    MSIHQ: Information detected by MSIHQ Tool ver: 1.18x
    MSIHQ: Report generated in 03.01.2010 г. at  7:25:38,51
    Mainboard:  945GCM5-F V2  (MS-7267)
    PCB Version:  4.0
    BIOS Version: V4.E (aka Version: V4.14)
    BIOS Date:  06/02/2009
    Co-respond BIOS backup created ==> A7267IMS.4E0 
    Where:
    * V4.14 ==> MSIHQ Tool detection [The same as CPU-Z, Everest]
    * V4.E ==> MSIHQ Tool "True BIOS Ready" detection feature
    * A7267IMS.4E0 ==> MSIHQ Tool BIOS recovery created by "Triple BIOS flash recovery Ready", part M-flash boot/recovery [1/3]
    MSIHQ: Information detected by MSIHQ Tool ver: 1.18x
    MSIHQ: Report generated in 03.01.2010 г. at  7:28:16,62
    Mainboard:  945GCM5-F V2  (MS-7267)
    PCB Version:  4.0
    BIOS Version: V1.BB1 (aka Version: V1.11B1)
    BIOS Date:  06/02/2009
    Co-respond BIOS backup created ==> A7267IMS.1B1 
    Where:
    * V1.11B1 ==> MSIHQ Tool detection [The same as CPU-Z, Everest]
    * V1.BB1 ==> MSIHQ Tool "True BIOS Ready" detection feature
    * A7267IMS.1B1 ==> MSIHQ Tool BIOS recovery created by "Triple BIOS flash recovery Ready", part M-flash boot/recovery [1/3]
    MSIHQ: Information detected by MSIHQ Tool ver: 1.18x
    MSIHQ: Report generated in 03.01.2010 г. at  7:31:57,78
    Mainboard:  945GCM5-F V2  (MS-7267)
    PCB Version:  4.0
    BIOS Version: VI.FB5 (aka Version: V18.15B5)
    BIOS Date:  06/02/2009
    Co-respond BIOS backup created ==> A7267IMS.IF5 
    Where:
    * V18.15B5 ==> MSIHQ Tool detection [The same as CPU-Z, Everest]
    * VI.FB5 ==> MSIHQ Tool "True BIOS Ready" detection feature
    * A7267IMS.IF5 ==> MSIHQ Tool BIOS recovery created by "Triple BIOS flash recovery Ready", part M-flash boot/recovery [1/3]
    MSIHQ: Information detected by MSIHQ Tool ver: 1.18x
    MSIHQ: Report generated in 03.01.2010 г. at  7:36:02,40
    Mainboard:  945GCM5-F V2  (MS-7267)
    PCB Version:  4.0
    BIOS Version: V7.O (aka Version: V7.24)
    BIOS Date:  06/02/2009
    Co-respond BIOS backup created ==> A7267IMS.7O0 
    Where:
    * V7.24 ==> MSIHQ Tool detection [The same as CPU-Z, Everest]
    * V7.O ==> MSIHQ Tool "True BIOS Ready" detection feature
    * A7267IMS.7O0 ==> MSIHQ Tool BIOS recovery created by "Triple BIOS flash recovery Ready", part M-flash boot/recovery [1/3]
    MSIHQ: Information detected by MSIHQ Tool ver: 1.18x
    MSIHQ: Report generated in 03.01.2010 г. at  7:39:11,84
    Mainboard:  945GCM5-F V2  (MS-7267)
    PCB Version:  4.0
    BIOS Version: VC.8B6 (aka Version: V12.8B6)
    BIOS Date:  06/02/2009
    Co-respond BIOS backup created ==> A7267IMS.C86 
    Where:
    * V12.8B6 ==> MSIHQ Tool detection [The same as CPU-Z, Everest]
    * VC.8B6 ==> MSIHQ Tool "True BIOS Ready" detection feature
    * A7267IMS.C86 ==> MSIHQ Tool BIOS recovery created by "Triple BIOS flash recovery Ready", part M-flash boot/recovery [1/3]
    MSIHQ: Information detected by MSIHQ Tool ver: 1.18x
    MSIHQ: Report generated in 03.01.2010 г. at  7:49:38,46
    Mainboard:  945GCM5-F V2  (MS-7267)
    PCB Version:  4.0
    BIOS Version: VG.PB6 (aka Version: V16.25B6)
    BIOS Date:  06/02/2009
    Co-respond BIOS backup created ==> A7267IMS.GP6 
    Where:
    * V16.25B6 ==> MSIHQ Tool detection [The same as CPU-Z, Everest]
    * VG.PB6 ==> MSIHQ Tool "True BIOS Ready" detection feature
    * A7267IMS.GP6 ==> MSIHQ Tool BIOS recovery created by "Triple BIOS flash recovery Ready", part M-flash boot/recovery [1/3]
    MSIHQ: Information detected by MSIHQ Tool ver: 1.18x
    MSIHQ: Report generated in 03.01.2010 г. at  7:53:17,26
    Mainboard:  945GCM5-F V2  (MS-7267)
    PCB Version:  4.0
    BIOS Version: VU.H (aka Version: V30.17)
    BIOS Date:  06/02/2009
    Co-respond BIOS backup created ==> A7267IMS.UH0 
    Where:
    * V30.17 ==> MSIHQ Tool detection [The same as CPU-Z, Everest]
    * VU.H ==> MSIHQ Tool "True BIOS Ready" detection feature
    * A7267IMS.UH0 ==> MSIHQ Tool BIOS recovery created by "Triple BIOS flash recovery Ready", part M-flash boot/recovery [1/3]

  • Recent Conversation with MSI and Neo4 overclocking "thing"

    I had a recent email transaction with MSI if anyone is interested. I tried my best to represent the group, and I know we all experience the problem a little bit different which is why it has been hard to explain and fix. I tried to give them the best info to duplicate the issue in the lab. It seems clear at this point that MSI still isn't duplicating the issue. They are using 166 Mem Clock Index, and the HT freq of 3x and still not understanding the issue, hopefully I have gave them a guide to duplicate what we have been trying to say. Yes I have explained this to MSI before but I really feel I am getting somewhere with my last 2 emails. Once we get them to duplicate the results then I think we will all have our solution shortly. Before anyone says anything negative, at least they aren't saying, oh that's an overclocking problem we don't deal with that. Also remember how long it has taken to get many people to see the issue, this isn't easy to understand so just stay cool, don't say negative sh-t if you reply and we'll see how this pans out. It was actully kind of hard since I am sitting in a hotel room 500 miles away from the motherboard but I was able to use modbin6 to view the BIOS and since I have done this about 7 zillion times I remember the settings LMAO. They have their Venice to 2750, not bad... 
    Hello MSI Engineer,
    The information you requested. The data you sent shows a Venice running at 166 Memclock index value at HT at 3x, the goal is to run at 200 Memclock Index and HT at 4x. In order to duplicate this issue in the lab here is my recommendation. It MUST be tried with a CBBID Winchester RevD CPU and a Venice Rev E CPU and the Gskill memory you have in dual channel. The issue happens everytime with a CBBID Winchester and less often with Venice.
    Starting with the Venice 3500+, Set the following in BIOS
    [Memclock Index] 200
    [CAS# latency (Tcl)] 3
    [Min RAS active] 11
    [RAS to CAS delay] 6
    [Row Precharge] 6
    [User config mode] manual
    [bottom of 32 bit] (default)
    [1T/2T] 1T
    [Read Preamble] 6ns (default)
    [Async Latency] 6ns (default)
    [S/W mem hole] Disable (default)
    [H/W mem hole] Disable (default)
    [MTRR mapping] Continuous (default)
    [High Performance] manual
    [Agreessive timing] Disable
    [Dynamic Overclocking] Disable
    [Adjust CPU FSB Frequency] 200
    [HT Frequncy] 4
    [HT Width] 16 up 16 down
    [CPU Spread] Disable
    [SATA Spread] Disable
    [PCI Spread] Disable
    [PCIe Clock] 101
    [SSE/SSE2] Enable
    [CnQ] Disable
    [CPU Ratio] 11x
    [Adjust CPU VID] 1.45
    [Extra CPU Voltage] your choice for stability
    [Mem Volt] your choice for stability
    [NF4 Volt] your choice for stability
    Now boot into Windows. Using Clockgen, increase HTT to 250. This should be stable based on your screen shot and your RAM modules. Now having a CPU 2750Mhz, RAM at 250Mhz, and a HT of 4x250(1000). Test for stablity with Prime95 or other Stress Testing tool. Now we can say motherboard is stable at 2750Mhz CPU, 250Mhz RAM, and HT 4x250(1000). Now return to the BIOS at set the following
    [Adjust CPU FSB Frequency] 250
    This reults in a no POST condition for me and others. Now install the CBBID, except you will have to set a lower CPU max speed based on CBBID overclocking potential. In the BIOS, Return [Adjust CPU FSB frequency] to 200, Perhaps [CPU ratio] of 10x or 9x but a [Memory Clock Index] 200Mhz. Boot to Windows and use Clockgen to raise HTT to 250 again. Once you find a [CPU Ratio] that will have a STABLE overclock with a 250HTT. Return to the BIOS and set [Adjust CPU FSB Frequency] to 250. Try and POST. Try this experiment with the 3.1, 3.3, and 3.4 BIOS's. For the CBBID and the 3.1 BIOS you should be able to change the [HT Freq] to 3x, 2x or 1x and get a POST with [FSB Freq] 250, [Memclock Index] 200, and a known stable [CPU Ratio] you found in Windows. The 3.3, and 3.4 BIOS have made this work around not possible. Why does [HT Freq] 4x work in windows but not at POST time?
    As a side note. The 1.3 BIOS for the 7125 works with the Venice, and the 1.4 and 1.5 do NOT. So somewhere between the 1.3 and 1.4 MSI created the issue on the Venice. Perhaps that is where you can find the answer and solution to the problem.
    Here are some articles that describe the issue on a ECS and Chaintech board that were remidied by a BIOS update. So the problem is not uncommon and should be able to be fixed.
    http://www.xbitlabs.com/articles/mainboards/display/chaintech-nforce4_6.html
    http://www.xbitlabs.com/articles/mainboards/display/ecs-kn1-extreme_9.html
    Here is some other users data of NF4 SLI and Ultra MSI Neo4's if you want to see some other BIOS settings.
    https://forum-en.msi.com/index.php?topic=81364.0
    Here is a screen shot of my Neo4 Plat SLI (MS-7100) 3.1 BIOS and CBBID Winchester(The Venice will NOT POST at all above [Adj CPU Freq] ~219-229 under any situation but is stable in Windows at HTT 250 with Clockgen). The system is stable and POST's when [HT Freq] is 3x, it will NOT at [HT freq] 4x which is stable in windows but won't POST.
    http://home.comcast.net/~aicjofs/cbbidMSI2501.jpg
    Here is another screenshot of the Asus A8N Plat SLI with all peripherals the same. Only changed the motherboard. This is POSTing at [HT Freq] 4x. This is just as a reference that the components do indeed POST with [Adjust FSB freq] 250, [Memclock Index] 200, and [HT Freq] 4x. This board will POST both my 3200+ Venice and Winchester CBBID at the settings described above.
    http://home.comcast.net/~aicjofs/cbbid250asus1.jpg
    The following are my BIOS settings that will create a non-POST condition, but the board is stable at these settings when ADJUSTED FROM WINDOWS.
    [ADVANCED BIOS]
    [Gate A20] Enable
    [APIC] Enable
    [MPS Table] 1.4
    [Boot OS2] No
    [ADVANCED CHIPSET]
    [System BIOS Cacheable] Disabled
    for newer BIOS
    [SLI Brodcast apeture] Whatever default is.
    [INTEGRATE PERIPHERALS]
    [Onboard IDE 0 and 1] Enabled all channels in Auto
    [IDE DMA] Enabled
    [SATA 1,2,3,4] Enabled
    [IDE PREFETCH] Enabled
    [NVDA RAID] Enabled
    [all IDE raid channels] Disabled
    [all SATA raid channels] Enabled
    [On Chip USB] 1.1-2.0
    [USB KB/Storage] Disabled
    [NVDA LAN] Enabled
    [NVDA ROM] Disabled
    [Onboard VIA 1394] Enabled
    [Marvell Gigabit] Disabled
    [Onboard Creative] Enabled
    [SiI3132] Disabled
    [FDC] Enable
    [Serial Ports] Disabled
    [Parallel Port] Disabled
    [POWER MANAGMENT] all defaults
    [PNP/PCI]
    [Init display] PCIe
    [Resources] Auto
    [PCI Express Max Payload] 4096
    [CELL MENU]
    [Timing mode] manual
    [Memclock index value(MHz)] 200
    [CAS# latency (Tcl)] 3
    [Min RAS active] 8
    [RAS to CAS delay] 4
    [Row Precharge] 4
    [Row cycle time] Auto
    [Row refresh] Auto
    [Row to Row delay] Auto
    [Write Recovery] Auto
    [Write to Read] Auto changing this to known working value will lock system sometimes
    [Read to Write] Auto changing this to known working value will lock system sometimes
    [Refresh] Auto
    [User config mode] manual
    [bottom of 32 bit] whatever it defaults to
    [1T/2T] 1T
    [Read Preamble] 6ns
    [Async Latency] 6ns Attempts to change this to 8ns will lock system
    [S/W mem hole] Disable
    [H/W mem hole] Disable
    [MTRR mapping] Continuous
    [High Performance] manual
    [Agreessive timing] Disable
    [Dynamic Overclocking] Disable
    [Adjust CPU FSB Frequency] 250
    [HT Frequncy] 4 (For 1000Mhz)
    [HT Width] 16 up 16 down
    [CPU Spread] Disable
    [SATA Spread] Disable
    [PCI Spread] Disable
    [PCIe Clock] 101
    [SSE/SSE2] Enable
    [CnQ] Disable
    [CPU Ratio] 10x
    [Adjust CPU VID] 1.45
    [Extra CPU Voltage] +9.9%
    [Mem Volt] 2.7v
    [NF4 Volt] 1.65v
    BIOS Tested 3.0, 3.1, 3.2, 3.3, 3.4. I have not tested 3.51 but forum users are still not getting positive results
    -------------- Original message --------------
    Dear Aicjofs
    This is MSI technical support engineer from Taiwan.
    We receive some message from MSI LA office & Anandtech.com.
    We are sorry for inconvinence experience when you try to Overclock MS-7100.
    We hope to contact with you directly and help you to solve it.
    Depends on related message from others, we know that you have several problem for MS-7100 overclocking.
    According to your info at MSI Forum, Here is your system configuration:
    Neo4 Plat SLI(MS-7100) 3.1 BIOS
    3200+ Venice (8x313) @ 2500Mhz
    Patriot PC4000 (200:133) 2.5-3-3-7
    HT x3
    Aopen 6800GT @ Ultra speed
    AthenaPower 500W 3.3v - 26a 5v - 47a 12v - 28a
    Could you give us more info about what changed item inside your BIOS?
    [Memclock index value(MHz)]
    [CAS# latency (Tcl)]
    [Adjust CPU FSB Frequency]
    [HT Frequncy]
    [Adjust CPU VID]
    [Extra CPU Voltage]¡Kor others
    We try to Overclock MS-7100 with BIOS v3.2 and 3500+ (Venice core).
    CPU ADA3500DAA4BW ABBWE made in Malaysia
    Memory G-skill PC4400 512MB*2 (Dual Channel)
    We only change some item inside BIOS as: (Based on Optimized defaults)
    [Memclock index value (MHz)] à166
    [CAS# latency (Tcl)] à 3
    [Adjust CPU FSB Frequency] à250
    [HT Frequncy] à3x
    [Adjust CPU VID] à 1.450V
    [Extra CPU Voltage] àOver VID 6.6%
    We will try to find similar CPU as yours to test it.
    If possible, please tell us the CPU OPN number like we listed. (ADA3500DAA4BW)
    We also help to know any other info that you can provide.
    If possible, please help to tell us more setting and system info.
    Thanks!
    Waiting for your responding.
    Best Regards!
    Technical Support Engineer
    Technical Support Department
    E-mail: msi.com.tw
    [Post edited by Glenn]

    Quote from: Indigian on 15-June-05, 19:41:43
    Good news and good work guy's
    On a side note to chakkasol....
    are you using coolbits 1 or 2?
    I heard that coolbits2 is the one for our later cards
    Good question - coolbits 2.  I happened to take a chance from this website and downloaded this file...ran it up against my antivirus and antispyware software and it looked clean.  I simply ran the program and viola, coolbits functionality automatically added to the winxp registry.  I cleaned out the msi DOT drivers first before I loaded this program.  Even though I have tweaked on occasion the winxp registry to speed things up and make winxp shut down quicker, this was too complicated for me to do on my own.
    The highest overclock with the MSIs DOT is 11% at 555/1100.  My MSI card is actually very stable at 580/1160 for a 16% overclock.  I have gotten it to 600/1200 but I usually run the coolbits stability program a few times and it has never failed at 580/1160.  I am sure if I had a better cooling system than the stock fan it would probably go to 600/1200 or higher.  At a 3DMark05 of 4133 (and much higher if I could get it stable at 600/1200, I would be bumping up against the stock speeds of the 6800s vid cards.   
    EDIT: Of course, if you download this coolbits 2 program you do so at your own risk...I take no responsibility for the download.
    The coolbits download:
    http://downloads.guru3d.com/download.php?det=815
    The MSI 6600gt card that I purchased:
    http://www.zipzoomfly.com/jsp/ProductDetail.jsp?ProductCode=321916
    btw, I have ordered more stuff from ZZF than newegg...they seem cheaper (but dont always have the stock of newegg) and the stuff gets here 1 day sooner usually (west coast to east coast USA). 

Maybe you are looking for

  • Cannot start weblogic server anymore in oracle user after config. in root

    Hi all, My weblogic server 10.3.4.0 installed in oracle developer days in oralce linux guest was able to start before using the oracle user account. However, after I copied a folder into the autodeploy directory in weblogic server under the root acco

  • Connecting the ipad to a data projector when projector is on the ceiling

    I am trying to connect the ipad to a data projector when projector is on the ceiling. I have the VGA cord but it is way to short ...is there another cord to connect the both?

  • How to find header bom for a particular child bom

    for a particular serial number (sernr-equi) contains material number( matnr-equi) this is a child material number. so i need to find header material(bom component) for this particular material . i am passing material idnrk(equi-matnr) in stpo table t

  • Uninstalling OSX Mountain Lion

    My macbookpro has become increasingly slow. I want to uninstall my latest software which is OSX Mountain Lion, but I purchased the software off of iTunes so i do not have a hard CD copy to re-install the software. Is uninstalling then re-installing t

  • Why am i not getting the sony points?

    I am new to this forum and this might be in the wrong place, i do not know how to work the sony forums much so if an admin would like to move this topic to the correct place, i wouldnt mind.... but i have ordered 2 things from sony and it keeps talki