U310 bios flash back

So my issue is that i updated my bios to 65cn99ww however the computer i have is a win 7 u310 and the supposed bios is 65cn21ww, didnt think i wouldnt be able to restore the old bios but here i am.
Is there a way to remove the secure capsule from an old bios, or disable/bypass the secure flash check?
I mean how do the lenovo engineers do when testing their systems? dont they have a way to revert back to older bios versions`?

forsaken123 wrote:
So my issue is that i updated my bios to 65cn99ww however the computer i have is a win 7 u310 and the supposed bios is 65cn21ww, didnt think i wouldnt be able to restore the old bios but here i am.
Is there a way to remove the secure capsule from an old bios, or disable/bypass the secure flash check?
I mean how do the lenovo engineers do when testing their systems? dont they have a way to revert back to older bios versions`?
Have you tried enabling Bios Back Flash in the bios (I'm not sure if you have this feature)?

Similar Messages

Looking for MSI FX5900 TD128 BIOS !! Need to flash back from 5950

I had flashed my BIOS a couple of months back using the WFFLash utility of Leadtek and since then ive been gettin low scores on 3dmark03!
Overclocking my 5900 once get me to get a 6300 3dmark03 score and now it doesnt go over 5800 or even less!!
I was hoping if some1 could either give me a link or if some1 had the BIOS of the GPU i own, it was be grateful!!
Even has any1 else encountered this low scores after their Flash!
Oh yeah which utility do i need to re-flash - WFFLASH or NvFlash!
Hope to find some help here ! !
THanksss !!

Utk,
The BIOS is static and flashing back probably won't make things better. I believe your scores or performance is suffering from OS decay. It might be a good idea to review all the software you have installed since you flashed your BIOS and see what's running in the backround. Perhaps even a fresh install of the drivers, maybe even a fresh install of the OS.
Read this link, it saves me the time of going into detail http://www.computerclub.org/tips_tricks/tip_performance2.htm
Quote
Looking for performance degradation
Before I move on, let me point out that there's another area where benchmarking software really shines for computer users and that is in keeping an eye out for performance degradation due to OS (Operating System) Decay.
This type of problem is little understood but very common. Let's take a closer look. As you've been using your existing operating system over time, you've probably installed, upgraded, and uninstalled numerous applications. In addition, you've probably added and removed lots of hardware and device drivers. Furthermore, you may have upgraded your operating system with a multitude of patches, bug fixes, and updates.
Considering all the wear and tear these types of operations put on your operating system, chances are good that you've experienced OS decay first hand. Some of the symptoms of OS decay are frequent system lockups or crashes, strange error messages, unusually slow performance, and Windows directory that's bloated with files.
Of course you must realize that OS decay is actually a natural occurrence that results from the heavy use of your system. You could look at the OS decay problem much as you would look at an aging automobile—no matter how well you take care of it, eventually you're going to have to buy a new one.
Fortunately, you don't have to buy a new computer to solve the OS decay problem; you just have to rebuild the operating system from scratch.
As such, the question is not if you must rebuild, but when you must rebuild. If you regularly check your computer and keep tabs on your system's progress over time, you'll have a much better picture of when the OS decay has gotten so bad that it's degrading the overall performance of your system.

Can I flash back my bios????

Hello together,
My questions is, can I flash back Bios from Version 3.5 to 3.4????
Please help me

Quote
Originally posted by wyattcoop
You could go to progam files on your hard drive then go to set up files and their you will find your old bios that you had previously downloaded. Just click on the previously down loaded file and it will run just like the live update utility did the first time you downloaded it. I,ve flashed this way two times without any problems.
That I never heard before.
A good tip if you have a running system

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]

Can't Enable XMP after BIOS flash to V1.4 on P55-GD85

I didn't put this in the BIOS section because while the BIOS is involved, I don't think it's necessarily a BIOS issue. However, if it should go there please move it.
While not new to computers by any stretch I committed the cardinal sin of updating my BIOS when I didn't absolutely have to. While their were some issues I'd hoped would be fixed with a new BIOS revision, they weren't critical.
I have a i7 860 Lynnfield system running Win 7 Home Premium 64 with a MSI P55-GD85 mobo which has been running fine since being built in March of this year. This was the first BIOS flash since I've built the system. The system came with either V1.0 or V1.1 (I think it was V1.1). I checked using Live Update (yes, I now know this is bad) and found there had been several udpates since my current version. I went ahead and used Live Update to flash the BIOS (yes, I know...not a good idea). Contrary to the horror stories the flash itself went fine. I watched it flash the BIOS and everything verified fine. Of course after the update I had to reset my BIOS settings to get the system to run which went fine. The problem is that the one thing I can't do is enable the XMP option for the memory without the system crashing. If I enable this option the system will POST and then do a memory dump before ever getting to the desktop. Without turning this option on I can't take full advantage of my RAM. I am running G.SKILL Trident 4GB (2 x 2GB) 240-Pin DDR3 SDRAM DDR3 2000 (PC3 16000) which are XMP compliant and ran without issue up until the BIOS update. It is possible that there is some other setting that I didn't reset after the BIOS change to allow this to work that I am missing. I know I did a bunch of tweaking and changing of settings trying to get things to run correctly when I first built the system. I've gone over and over the BIOS and can't find anything else to try to get me to allow to enable the XMP option without crashing. By simply enabling that option my system would normally run stable at about 3.6-3.7GHz.
Does anyone have any ideas as to why this might be happening or what I can do about it? About the only other thing I can think of is to reflash the BIOS back to a previous version to see if that helps. I am sure there is something I am missing as there is no reason the BIOS shouldn't allow the XMP feature to be enabled without crashing. Any help would be most appreciated. Thanks.

Have you try to increase your RAM voltage to 1.55v ~1.6v?

Bios flashed, rma, windows still wont load

Evening,
I flashed with live update (yes i know now..) and it went wrong. Board, P55-cd53, sent to MSI who reprogrammed it. Unfortunately windows wouldnt load. I think i have tried every described method posted here, even flashed back to the old version, to no avail. I even tried a boot dvd with ubuntu but even that OS wont run (either with or without installation). The pc simply reboots when trying to execute these commands.
If i were to replace any hardware: what would it be?
System specs
P55-CD53
intel i5 750
ocz-gold-low-voltage-ocz3g1333lv4gk
Msi hawk 5770
Samsung spinpoint f3 500gb
Cooler master real power M520
Thanks,
Harry

Quote from: Svet on 10-October-10, 16:16:23
Before this bios flash it was worked fine?
I was having regular BSOD, especially when leaving the pc on overnight. Other than that everything worked fine.
Quote
Do >>Clear CMOS Guide<< with power cord removed.
Then Load BIOS Defaults
I did this before sending it back to MSI. I haven't done this after i received the mb back from MSI. Will try today.
Quote
Check memory voltage in BIOS setup, you may need to apply voltage recommended by your memory vendor for your sticks
Also do check with >>Memtest86<<
Memtest came with the Ubuntu-disc. I ran it and the Memtest results were shocking. I only did 5 runs but received thousands of failures.
I will replace the OCZ rightaway instead of finetuning them in BIOS.
Also adressed to Jack: Would the G-skill F3-12800CL9D-4GBNQ be a good choice? Right out of the box without adjusting anything inside BIOS?
Quote
Else reinstall OS
So far i haven't been able to reinstall or repair (from disc and usb) my windows 7 at all, not even Ubuntu.
System just keeps telling me 'the ntoskrnl is missing or corrupt' and keeps doing restart loops.
Would replacing the DRAM solve my problems likely or would it cost me a new MB or HDD too (if al else fails)?
Thanks,
Harry

Stupid Move on Promise Bios Flash

I foolishly tried to get the last bit of performance out of my Promise controller by obtaining a bios flash from the Promise website. I am flashed to a bios that probably doesn't go with this board, and although it works, its not smoking like it used to (that was a good thing). Anyone help me get my Promise bios back to what it was or back to spec if I promise (no pun intended) not to do it again.
My bios rev overall is 1.2 and a full mobo bios flash doesn't change anything.
The Promise bios is 1.0.1.34.
tia,
Bill

Ok, are you sure you really want to go from a working bios, to the unknown? If so, copy the two files you outlined to the "ramdrive", copy a:file to be copied c:,assuming the ramdrive letter it gave you is c. Change to drive c, c:\, now you have a c prompt. type in "adsfi707 a6758ims.132", this is the exact command line you need, and you need to do it from the c prompt of the ramdrive after copying the two files to it. My current experience tells me to pass along this, DONT FLASH YOUR BIOS IF IT WORKS FINE FOR THE MOMENT!!!! I'm just talking about normal stability. Overclocking right now is too wierd for this board, till MSI pulls their collective heads out, and fixes this bios issue once and for all.

K7N2 Delta2 Bios Flash

Ok so just got this board and flashed it to version b40 and it is unstable. When i try to flash back to version b30 i get a message that the bios is write protected. Can anybody tell me how to un write protect the bios so i can reflash the board.

Quote
Originally posted by Dancer
The moral of the story is:
Don't flash your bios unless there is a specific problem on your board that the new update addresses. Too many people flash there bios to have the latest and greatest, when there was really no need to flash at all. If it ain't broke then don't try and fix it.
Actually my board came with that B40 version.... I might attempt to flash to old verison B30 tonite.
Then do some mad ocing tests :P

CnQ prob after BIOS flashing (K8N)

hi everybody
i've been flashing the bios of my k8n neo plat. from the start without any problems.
but since i installed v1.52, i got a prob with CnQ. whatever multiplier i select in bios, it only works as long as i enable CnQ in windows. from then on, the cpu keeps switching to 11x when occupied, leading to sudden crashes, because i usually run fsb of 250Mhz with mit A-Data RAMs.
now i cant get this fixed... flashing back to any older bios doesnt help at all :(
what to do? plz hlp!
thx

hi gabrielloewen ,
I'd try unplugging everything but the minimum, CPU, Grfx Card & 1 memory Module.
carefully follow Clear CMOS with jumper JBAT1 Make sure you leave the jumper on discharge for as long as specified, it's easy when your worried to do it to quickly. The continuous beeping is normal with memory removed. see Award Bios Beep codes in Main Menu - No Post/No Boot problems and fixes
If that works add back your drives etc.,
If that brings no success & you find no other solution you won't lose but may gain by following 5-2) Clear CMOS settings by removing battery in the last link leave the battery out overnight, & try again tomorrow (Minimum parts again.)
luck

Neo2 not booting after BIOS flash

Darn - after upgrading to v1.3 BIOS, my Neo2 FIS2R won't boot.
I got a brand new set of components - new CPU, Neo2 FIS2R, and 1GB of Kingston HyperX PC3200 memory (22261T). I put everything in my system (Antec case, 400W P/S) and it booted fine with the v1.0 BIOS and I was able to install WinXP to my new 120GB SATA drive and my ATI9700Pro. Great - I know all my components work.
I install LiveBios and it shows me that v1.3 is out and enables MAT and DOT - the two features I bought the mobo for. So I download the latest via LiveBios, build the floppy (my system uses NTFS to boot) and reboot.
The BIOS flash process goes smoothly and I wait all the way to the end. I shut off the system and reboot - nothing, just a blank screen. So I shut it off, clear CMOS, and reboot again - still nothing. I try several more times, still nothing. However, recovery mode works so I reflash 1.3 a couple times to see if that will help, but it does not.
Finally, I build a floppy with v1.2 BIOS as the recovery BIOS and use recovery mode to load that. Still no go.
It is at this point that I discover and plug in those diags LEDs (I was using the onboard USB header to bring the USB ports to the front of the case) and find that it is stopping almost immediately at the 'early chipset identification' phase. Ouch. Oh, and at this point the BIOS recovery mode no longer works. Ouch.
Any thoughts? At this point I got an RMA number from the vendor and I'm thinking I'm just sending it back.

Unfortunately I can't even get to that phase - the system won't show the post splash screen or post at all. It just sits there blank (I know I wasn't clear on where the boot process was stopping - it doesn't even allow me to enter rom-based setup.)
So I'd love to set vdimm to something else, but I can't.

Please help:System keeps rebooting after Bios flash update

Hello,
Ok for starters I have the K9A2 CF motherboard,4GB of ram,My last Bios was 1.8.
I was flashing to 1.9 using the bios flash tool and a usb 1GB stick.The Bios flash went without errors and I rebooted.After this I booted back up.It gets to the 512Mb on the screen then poof,the system reboots automatically and keeps doing so thereafter unless I shut the PC off.How can I restore my Bios or fix this issue.This is not good as I cant even get to the post screen before it reboots to change anything.
Thanks,
K9A2 CF board
Windows Vista 64
4GB Corsair ram
80GB Stata HD
200GB IDE HD
DVD-RW Drive

Quote from: soldat32 on 06-August-09, 05:16:16
CPU Type QuadCore AMD Phenom, 2500 MHz (12.5 x 200)AMD Phenom X4 9850 Quad Core Processor HD985ZXAGHBOX - Black Edition, Unlocked 2.50GHz, 4MB Cache, 2000MHz (4000 MT/s) FSB, Agena, Quad-Core, Retail, Socket AM2+, Processor with Fan
No errors were found in my memory.My PSU seems to be working fine.My VGA is a XFX Nvidia 9600GT with 512mb.
Have you tried that?:
Quote from: Svet on 06-August-09, 03:52:32
Try with your second stick alone in the same DIMM slot.
Quote from: soldat32 on 06-August-09, 05:16:16
CPU Type QuadCore AMD Phenom, 2500 MHz (12.5 x 200)AMD Phenom X4 9850 Quad Core Processor HD985ZXAGHBOX - Black Edition, Unlocked 2.50GHz, 4MB Cache, 2000MHz (4000 MT/s) FSB, Agena, Quad-Core, Retail, Socket AM2+, Processor with Fan
Its 125W CPU.
Can you shows picture of your board? Is it V2? Is there a heatsink over mosfets?:

XP 2400 detected as Sempron 2.0GHz after bios flash on KM4M-L

well the title says it all. cpu-z detects it corectly as an athlon xp, windows and sandra as a sempron 2.0GHz
Any fix to this?
bios is the latest

Sempron 2800 is a 2.0Ghz CPU, with the same L1/L2 cache as the the Athlon XP2400, which also runs at 2.0GHz. This means that you are experiencing a "Cosmetic" issue, in that the CPU is named incorrectly, yet functions 100% as designed. The BIOS update probably added support for the Sempron, and it is simply misreading the CPU name.
Was the BIOS flash done to solve an issue you were having, or just because it was available? If it was to solve an issue, and has done this, then just let it go, and know it is working correctly. If it was done just because it was available, flashing back to the previous version should resolve this.

So why wont my bios flash allow windows to start (raid 0 array).

Hi .. I have been running 1.36 beta bios ever since I had this board (K8N Neo2 plat), but have had the odd problem once in a while, after trying various things, I thought I would flash the bios to the newest official version ... but heres the problem.
It boots, gives me a "healthy" report on the raid array .. but right where the windows boot screen should appear it just stays black.
So I try safe mode .. it loads all the text then hangs.
I tried rebuilding the array, but no go .. still the same result ... flash back to 1.36b and windows loads fine
Bios was put back to defualt settings before the flash .. so I am a bit confused as to why I am having this issue, can anyone help ?

My fault Syar2003
I was looking at the scsci bit .. not the sata bit under ide controlers ... 1.4bios on and windows loaded (after a few secs blank screen when i went nooooooooooooo !!)
Great stuff thanks for all your help
Odd that installing the 5.1 drivers doesn't do these too ... but thats nvidia for ya I guess

Won't boot after using windows Bios flash utility

I used the windows bios flash utility i found on the toshiba website for this sat a135-s2386, all looked good until reboot, now just a white screen.

Attitude is not going to get you far.
Let's try a proper system reset, and see if this helps bring the unit back. Power off your system, unplug everything including the AC, remove the battery, press and hold down the power on button for 30 seconds, replace battery and AC, power on, if you see the Toshiba logo press the 'F2' key to enter BIOS Setup, in setup press 'F9' to load setup defaults, press 'F10' to save and exit, then try to boot into Windows.
Please let us know what happens. Good luck.
Mike

6715b bios flash failure

Windows 7 64 bit on a notebook that came with Vista 32 installed.
My system has a BIOS virus and system trojan probably.
The operating system has stopped recognizing external USB devices, so my reinstallation system image is not accessable.
The BIOS will not accept a change from enabling LBA access for USB devices, instead it keeps reverting to Bit-Shifted.
The external USB hard drive (1.5TB) appears in Device Manager, but not in Disk Management etc.
BIOS version F2.0
The BIOS flash utility from Windows displays the current BIOS as being from 2010 (a year that no BIOS was issued), and it uselessly reflashes whatever BIOS virus is here back into the BIOS. FYI this has occured ever since HP&co started allowing BIOS utilities to save backup versions of the BIOS during flashing. I have never found instructions for reinstalling BIOS settings from a saved BIOS.
Attempting to flash the BIOS from the FreeDOS utility generates an error claiming that the older version of the BIOS F0.7 offered by the FreeDOS utility is not compatable with this version of the system.
Attempting to reflash using an older version of the Windows utility generates the same error.
There is no FreeDOS version of BIOS F2.0
Attempts at removal of the CMOS battery, which is supposed to clear ALL passwords, according to the manual fail to clear the BIOS password, or enable the apparently necessary setting change from Bit-Shifted to LBA for the External USB device to work. Rebooting to the BIOS continually shows the Bit-Shifted option, even though the F10 Save and Save Chages options are chosen.
Odd side note, while unzipping the Vista64bit BIOS and checking the ver. file it shows a WRONG BIOS date: _ROM_ 68YTT v0F.20 12/01/2010 the WSSP5556 file shows:
EFFECTIVE DATE: December 02, 2011
What's really frustrating is that HP lists a different link to each and every version of the Windows Operating system. This displays like a dozen OS versions, and NONE of the Windows 7 verisons has a BIOS update link.
The BIOS displays the 2011 version information from Setup.
With the F2.0 version of the BIOS installed via a Windows Utility running in compatability mode, how can the same version of the BIOS be installed with the FreeDOS utility?
Or
Is there some sort of trick to changing the USB data transfer mode from Bit-Shifted to LBA?
The BIOS default setting is Bit-Shifted whether or not Legacy USB modes are enabled or not.
Is there some other reason besides the data transfer mode that could cause an external USB device to be recognized in Device Manager (with a device ID number) and not at all in Disk Management?

There is no need to change the HDD data transfer mode from Bit-Shifted, in order to get an external SATA/USB drive to work.
The malicious code was in the CMOS/BIOS.
The instruction manual for clearing the CMOS settings is incomplete. In order to clear the CMOS settings using the proceedure outlined on page 46 of the manual, a step must be added between steps 5 & 7.
After removing the Real Time Clock Battery, the AC power cable must be connected, the unit started by actuating the Power Button, and then the AC Power cable is disconnected.
Powering the unit up, without the Real Time Clock Battey installed, clears the CMOS settings, and BIOS.
Without reconnecting AC Power the malicious code and CMOS settings appear to be getting reflashed into the BIOS from CMOS.
As a self check as to whether or not the CMOS settings were cleared, check the date/time.
Without cycling the AC Power connection the time/date is NOT reset, and reflashing the BIOS does not remove the malicious code.
Also there is no need to wait 5 minutes after removing the Real Time Clock Battery(step #6).
This is a waste of time and does NOT clear the CMOS settings. The unit was allowed to sit for well over 5 minutes and the CMOS settings were not cleared, when the AC Power and the batteries were only removed.
Reflashing the BIOS from a Windows desktop, can be a complete waste of time, and risks further damaging the system in this case, because the malicious code was probably loading from CMOS and from the formated Hard Disk. Sanitizing the Hard Disk, clearing CMOS, and reflashing the BIOS from a CD cleared the malicious code.
"If it ain't coming from a friend, it proabaly isn't really free"

U310 bios flash back

Similar Messages

Maybe you are looking for