Incorrect bios readings

hi community
i have an issue with how bios reads my cpu temp, it seems its reporting back my cpu surface temp instead of my core temp which is 25c lower than the actual core temp(i boot into bios and it reads my cpu temp as 6c but in windows, everest and speedfan both report 31c as my core temp)...
i am using the latest bios and everything runs great but this is making me really wonder.
athlon 64 3800+ venice(stock all the way)
msi rs480m2
2x512mb kbyte(dual channel)
ati radeon x700 256/128 pci e
seagate barracuda
western digital
thanks
still learning
arnee

Sounds like a Bios issue as Speedfan and Everest read directly from the sensor chips. I doubt it is anything to worry about and somewhere down the road when you reflash the Bios it will likely be corrected. Though I would certainly not flash the Bios just for that issue as it won't affect anything else as far as I am aware.

Similar Messages

Satellite 1410-604 - BIOS update Incorrect BIOS update in the web?

Hi there again!
Now with a new and weird matter.
We all know that old say... "If it is not break, don't fix it". And if you put it into more informatic terms, "specially if it is a BIOS".
Yes, we all know that the BIOS is something quite dellitate to handle. For some reason we normally feel like if we were handling something like nitro-glycerine, or some radioactive product. And this is because we all know what is being put in risk in that moment: our (or sometimes others) computer, the full system could end as dead as some pieces of metal, plastic, and wires.
Well. I passed through all of that more than ten times in my life, and only once it went wrong. But since that old motherboard was already dead, It was not important. But I allways was EXTREMELY care. I allways cross checked everything before doing anything, allways got a backup and a way to restore that backup... and allways did this in COMPAQ systems, that were prepared that way. Updating a BIOS was just about preparing a disk, turn on the PC with the disk in the diskette drive, and wait. And if you didn't like the results, you simply click "return to previus BIOS" and that was it... very nice. And easy.
Few days ago, a friend brought me a Toshiba Satellite 1410-604 to solve some issues that were driving him crazy. After removing an expired Norton Internet Security, install avast and scan, I found more than one hundred files infected with a wide variety of virus, malware, trojans, and whatever you could imagine. Avast removed them all, but the remains of the operating system was so unstable that we decide to format and install from scratch.
I asked for the restoration disks, that obviously he don't have because they were lost in one of his movings. After we got the confirmation from Toshiba reps that there are no recovery disk available for this model, because it is too old, we decided to install from scratch like any other normal PC, and resigned to loose some of the utilities that come with that CDs and that are not available for download in the website.
I downloaded all of the software available for this model, including two BIOS updates. (Actually only one update, but in two versions: Windows and Traditional), and prepared a CD with all the drivers and programs just like if it were a brand new system install. And everything went very well, no problems at all. Until we got to the Wireless LAN card, but that is another issue that is already solved (the mini PCI card for the WLAN does not support WEP or WAP encription, and it is not possible to connect to any wireless LAN encripted).
At this point, and when I started configuring and enabling PCMCIA devices, and USB devices (this computer only supports USB 1.1 not 2.0) I discovered this text in the Toshiba Website:
"This Bios Update adds increased functionality to your system.
(BIOS is an acronym for Basic Input and Output System. This program is stored in a Read-Only Memory chip on the motherboard.
When the computer powers up, the BIOS is launched to perform various start-up functions.)
For detailed update information please refer to Toshiba BIOS-Update Information"
(you can find this here:
[http://eu.computers.toshiba-europe.com/innovation/download_drivers_bios.jsp?service=EU] you have to look for:
Archive
Satellite
Satellite 14xx
Satellite 1410-604
PS141E
Quite specific. Isn't it?)
According to the information in that same website, the BIOS available fits the following models:
"Satellite 2410-414, Satellite 1410, Satellite 1410-654S, Satellite 1410-814, Satellite 2410-303, Satellite 2410-304S, Satellite 1410-354, Satellite 2410-601, Satellite 1410-401, {color:#ff0000}*Satellite 1410-604*{color}, Satellite 2410-404, Satellite 1410-301, Satellite 1410-304, Satellite 2410-S403, Satellite Pro 2100, Satellite 1410-S203, Satellite 2410-304, Satellite 1410-554, Satellite 1410-S102, Satellite 1410-354E, Satellite 2410-703, Satellite 1410-303, Satellite 2410-S203, Satellite 1410-801, Satellite 2410-603, Satellite 1410-902, Satellite 1410-313, Satellite 1410-802, Satellite 1410-714, Satellite 2410-354, Satellite 2410-514, Satellite 1410-614, Satellite 1410-704, Satellite 2410-515, Satellite 2410-504, Satellite 2410-702, Satellite 1410-S103"
Yes... it's there!
Now, when you go to the "Toshiba BIOS-Update Information", you get:
"FAQ Ref.: TRO0000000b07
A BIOS update is a {color:#ff0000}*relatively simple operation and can be carried out by most competent computer users*{color}. All BIOS upgrades can be obtained from "BIOS Update" Download Section click here..
Note: The BIOS files are machine specific so the correct BIOS for your machine must be used."
Please note that Toshiba does not disencourage the handling of BIOS, on the contrary: they even encourage people to do so. This is not necessary bad, but at the same time they encourage people to 'play around' with such a delicate matter, at the end of that same page, in little letters they say:
"Toshiba provides this information "as is" {color:#ff0000}*without warranty of any kind*{color}, either expressed or implied, including, but not limited to, the implied warranties of merchantability or fitness for a particular purpose. Toshiba shall not be responsible for the topicality, correctness, completeness or quality of the information provided. {color:#ff0000}*Toshiba is not liable for any damage caused by the use of any information provided, including information that is incomplete or incorrect*{color}."
This should trigger yellow alarms in our minds.
+"Human error is inherent to humans, and it is not possible to erradicate. It will allways appear, sooner or later" (Prof. James Reason).+
And finally I made the mistake. Even though I read that warning, I remembered all those successfull BIOS update with COMPAQ, and relied in Toshiba. That update was available there, and Toshiba was telling me that it was for this computer. Great!
So finally I unplugged all devices (USB), removed the PCMCIA (WLAN),plugged the battery charger to avoid any possible battery problem, restarted windows, and then from within windows I started the updater (windows version, as recommended by Toshiba). Everithing looked fine, nothing different of what I used to see on those old COMPAQs.
As warned by the updating program, the system was going to reboot. And actually it did so.
Windows closed quite normally (a bit quicker than normal, but without errors, and since there were no other programs than the essentials -even the antivirus was not running-), the computer switched of, all lights off (normal), and then it switched on again...
{color:#0000ff}*BEEEEEEEEEEEEP... BEEEP... BEEEEP...*{color}
OMG! I never espected something THAT bad. 3-1-1!
And now... What a 3-1-1 stands for here? Award BIOS would mean no video card or deffective video card, but it is not true, since it was working up to 20 seconds ago. It must be the BIOS.
It never came again to life. It is still beeping 3-1-1.
But now comes the investigation of the human-factors involved in this accident.
I found I commited the following failures:
*(1)* To rely in the manufacturer, even though they WROTE their information could be wrong or incomplete. (BAD if I were a QA&QC inspector).
*(2)* I didn't cross checked deeply enough (until it was already too late).
*(3)* I didn't looked previously for the way to make a backup of the BIOS, in order to restore should anything go wrong.
*(4)* Let Toshiba lead me to a path I didn't want to walk, just because of their offer of "increased functionality".
*(5)* Beleave in Toshiba when they said "relatively simple operation and can be carried out by most competent computer users"... they never said it is failproof.
Then I started the most interesting part of the investigation.
{color:#0000ff}*"What went wrong?"*{color}
Obviously, the BIOS update failed somehow, somewhere. And I wanted to know what and where.
First thing I discovered was that there are another search engine in Toshiba called "askiris" ([http://askiris.toshiba.com]) and I looked there in order to see if for any chance I could get the old 1.20 BIOS version that was installed originally in that machine.
And I found something... VERY interesting:
bq. {color:#800080}*From: * \\ {color}{color:#800080}* ACPI Flash BIOS version 1.10 for Satellite 1410/1415/2410* \\ {color}{color:#800080}* bios for these models. TAIS. Downloads. DL. 105481 289838 289838 ACPI Flash BIOS version 1.10 for Satellite 1410/1415/2410. 2002-10-04. 105589...* \\ {color}{color:#800080}* Published 10/4/02* \\ {color}{color:#800080}* From: * \\ {color}{color:#800080}* ACPI Flash BIOS version 1.40 for Satellite 1410/1415/2410/2415* \\ {color}{color:#800080}* FDD Version 1.30 TAIS. Downloads. DL. 105481 357972 357972 ACPI Flash BIOS version 1.40 for Satellite 1410/1415/2410/2415. 2003-01-31. 105589 PUB...* \\ {color}{color:#800080}* Published 1/31/03 | Rating:* \\ {color}{color:#800080}* From: * \\ {color}{color:#800080}* ACPI Flash BIOS version 1.20 for Satellite 1410/2410* \\ {color}{color:#800080}* error message during BIOS TAIS. Downloads. DL. 105481 305240 305240 ACPI Flash BIOS version 1.20 for Satellite 1410/2410. 2002-11-01. 105589 PUB...* \\ {color}{color:#800080}* Published 11/1/02 | Rating:* \\ {color}{color:#800080}* From: * \\ {color}{color:#800080}* ACPI Flash BIOS version 1.30 for Satellite 1410/1415/2410* \\ {color}{color:#800080}* 1) Changed the content TAIS. Downloads. DL. 105481 330963 330963 ACPI Flash BIOS version 1.30 for Satellite 1410/1415/2410. 2003-01-03. 105589...* \\ {color}{color:#800080}* Published 1/3/03 | Rating:* {color}
Those are: V110, V140, V120 and V130 for series 1410/15 and 2410.
GOOD! Or not?
Let's take a look:
First thing I did was download everything all four files.
Then I took the same version that made the crash: 1.40
Than I uncompressed the file, and I found:
06/05/2009 00:17 <DIR> .
06/05/2009 00:17 <DIR> ..
31/01/2003 08:38 1,605,632 11410v14.iso
31/01/2003 08:38 511,764 1370D14.EXE
{color:#ff0000}*08/01/2003 17:03 724,480 2410a9v140.exe*{color}
09/01/2003 09:32 250,663 biofca9t.com
08/10/2002 05:26 30,697 chgbiosa.exe
31/01/2003 08:36 1,087 instinfo.bat
13/05/2002 15:25 378,175 launcher.exe
31/01/2003 08:36 433 launcher.ini
06/05/2009 00:17 0 list.txt
31/01/2003 08:36 14,768 readme.com
*{color:#ff0000}31/01/2003 08:36 12,513 readme.txt{color}*
11 archivos 3,530,212 bytes
3 dirs 9,404,600,320 bytes libres
And I got my first surprise here: There is a {color:#ff0000}*README.TXT*{color} that was not present in the file I downloaded previously from the drivers repository.
So I went to the readme.txt and I found this:
"README.TXT 01-31-2003 CDC
Flash BIOS version 1.40 for Satellite 1410
This BIOS is applicable to the following models:
Satellite 1410-S105
Satellite 1410-S106
Satellite 1410-S173
Satellite 1410-S174
Satellite 1410-S175
Satellite 1410-S176
Satellite 1415-S105
Satellite 1415-S106
Satellite 1415-S115
Satellite 1415-S173
Satellite 1415-S174
Satellite 1415-S175
Satellite 1415-S176
Satellite 2410-S203
Satellite 2410-S204"
Please note that the model 1410-604 is *NOT* listed.
I thought "well, it must be another archive..."
But then I realized of a name that sounds familiar, it was there, in the directory where I uncompressed this 1.40 file, and the name is:
{color:#0000ff}*2410A9V140.EXE*{color}
So I took the other file, the BIOS_Win update, and I discovered that the file name is:
*{color:#0000ff}2410A9V140.EXE{color}* (Ups!)
So I uncompressed it again, to find:
El volumen de la unidad D no tiene etiqueta.
El n£mero de serie del volumen es: 8838-E175
Directorio de D:\Shared\diskette\2410A9v140
06/05/2009 00:43 <DIR> .
06/05/2009 00:43 <DIR> ..
*{color:#0000ff}09/01/2003 09:32 _250,663_ BIOFCA9T.COM{color}*
17/07/2002 03:38 35 biosupd2.ini
13/07/2001 13:22 6,277 chgbios2.vxd
*{color:#0000ff}08/10/2002 04:26 _30,697 _CHGBIOSA.EXE{color}*
09/11/2001 09:14 134 clean2.reg
17/07/2002 03:35 342,064 install2.exe
16/07/2002 06:55 241,664 nchgbios2.exe
18/08/2001 11:41 3,435 nchgbios2.sys
23/10/2001 18:55 11,476 nchgbios2NT.sys
26/08/2001 09:00 49,152 nchgbios2svc.exe
13/07/2001 17:05 49,152 tbdecode.dll
14/03/2002 06:42 49,152 TCHGBIOSInfo.dll
21/06/2002 11:25 1,796 tosclean2.bat
09/11/2001 12:01 967 tosclean2.pif
21/06/2002 11:34 1,841 toscleanAUTO2.bat
21/06/2002 11:44 1,796 toscleanSMS2.bat
21/06/2002 08:51 2,038 tosntclean2.bat
21/06/2002 08:51 2,084 tosntcleanAUTO2.bat
21/06/2002 08:52 2,038 tosntcleanSMS2.bat
20 archivos 1,046,461 bytes
2 dirs 9,402,793,984 bytes libres
No readme file...
Then another question arised in my mind: What about the other 1.40 file? What does the other 2410A9V140.EXE have inside?
This:
El volumen de la unidad D no tiene etiqueta.
El n£mero de serie del volumen es: 8838-E175
Directorio de D:\Shared\diskette\comparacion_toshiba\askiris\241 0a9v140
06/05/2009 00:46 <DIR> .
06/05/2009 00:46 <DIR> ..
*{color:#0000ff}09/01/2003 09:32 _250,663 _BIOFCA9T.COM{color}*
17/07/2002 03:38 35 biosupd2.ini
13/07/2001 13:22 6,277 chgbios2.vxd
*{color:#0000ff}08/10/2002 04:26 _30,697 _CHGBIOSA.EXE{color}*
09/11/2001 09:14 134 clean2.reg
17/07/2002 03:35 342,064 install2.exe
16/07/2002 06:55 241,664 nchgbios2.exe
18/08/2001 11:41 3,435 nchgbios2.sys
23/10/2001 18:55 11,476 nchgbios2NT.sys
26/08/2001 09:00 49,152 nchgbios2svc.exe
13/07/2001 17:05 49,152 tbdecode.dll
14/03/2002 06:42 49,152 TCHGBIOSInfo.dll
21/06/2002 11:25 1,796 tosclean2.bat
09/11/2001 12:01 967 tosclean2.pif
21/06/2002 11:34 1,841 toscleanAUTO2.bat
21/06/2002 11:44 1,796 toscleanSMS2.bat
21/06/2002 08:51 2,038 tosntclean2.bat
21/06/2002 08:51 2,084 tosntcleanAUTO2.bat
21/06/2002 08:52 2,038 tosntcleanSMS2.bat
20 archivos 1,046,461 bytes
2 dirs 9,402,781,696 bytes libres
*{color:#ff0000}They both have 20 files, and 1,046,461 bytes. I asumed they are both the SAME file{color}*.
And the readme file does not list the model 1410-604 in its readme file, therefore I cannot explain this except as a mistake from Toshiba. *{color:#ff0000}They put an incorrect BIOS in their website, and suggested the update, and somehow leaded to this kind of errors.{color}*
(Except in the case that one of those models is a different name of the 1410-604 model, and if it is the case... now I don't know why this BIOS do not work with this computer).
The worst part is that neither of those other files (V1.10, 1.20 and 1.30) lists the 1410-604, therefore there seems no possible workaround for this problem. I need an original v1.20 for this CMOS, and Toshiba seems not to have it. They offered me to solve the problem, by leaving the notebook at an ASP, and paying only 95€ for the work and about 280€ for a motherboard replacement, I will get it solved. But they offer no warranty of their possibilities because is a model 'too old' and 'discontinued' and with 'no support'...
In other words, they said "don't bother with this, just go out there and buy a new one" (something absolutely out of my scope in this crisis-time) :P
Thank you for reading soooo far.
Now what I need is to get any ideas of a workaround for this, my ideas are:
(1) This CMOS has a boot-part that still works (it allows a roll-back if you have the appropriate file). So I need a good BIOS to burn into the CMOS, from the VERY SAME model (a BIOS backup) but the backup must be adequate for the burning program (CHGBIOSA.COM).
(2) It is still possible that the BIOS could be OK but the data on the CMOS got somehow corrupted. If so, clearing the CMOS could solve de problem. But I was not able to find a clear cmos button from outside, and after disasembling I took of the battery, with no good results. I have to try leaving the MOBO without battery for longer period (I left it about 20 seconds) just in case 20 seconds don't allow all the capacitors to fully go to zero values. I have not much hope in this point.
(3) Try to get a REAL good update from Toshiba. I contacted several times technical support, and I was able to verify they are only phone-operators, with a script in front of them, and when the problem goes-out-of-scope they fall always in the same answer: "you have to go to an ASP". I still have a low hope to find someone who really knows a bit, and could enlighten with a good BIOS to put in this disks.
(4) As far as I could find, this BIOS is not from any known BIOS-maker. It seems it has been developed by Toshiba (own brand), therefore the Crisis Recovery Disk from Phoenix will not be of any help here. As well as any other BIOS recovery tool not designed for Toshiba's BIOS. But I'm open to any ideas, that could be tested more or less safely. (Remember that the 'BIOS-BOOT-PART' feature is still working, I don't want to loose this only possibility of redemption).
Wwwaaaaoooowww... what a long-post falks! Sorry for that!
Forgive me, but I wanted to be really clear.
Should anyone give some hints or advice, will be greatly appreciated.
Please don't say what I shouldn't do... I already know that. I already researched and already found my mistakes, in order not to repeat them. Now I need to move on, to advance, and to try to solve this, or at least learn how to solve similar things. As much as possible.
Thank you again, in advance, and sorry again.
FenixDigital
Message was edited by: Fenix_D
Changed subject to beter reflect what is the matter about (apparently erroneous BIOS file in Toshiba download center).

Well. 
 
It's not dead, certainly. 
 
The steps that I put in my procedure were: 
 
--> There are two memory sims, that I am going to identify as M1 and M2 
--> There are two memory banks, that I am going to identify as A and B 
 
Next step in order to identify if there are some module or bank that is not working properly are: 
 
The modules were installed as: 
 
M1 --> A 
M2 --> B 
 
1--> Boot without any memory chip. 
 
<blockquote>
A--> X 
B--> X 
</blockquote>
 
2--> Boot with ONE module 
 
<blockquote>
A-->M1 
B-->X 
</blockquote>
 
3--> Boot with the OTHER module 
 
<blockquote>
A--> X 
B--> M2 
</blockquote>
 
4--> Boot with BOTH modules swapped: 
 
<blockquote>
A--> M2 
B--> M1 
</blockquote>
 
5--> Boot with ONE module swapped: 
 
<blockquote>
A--> M2 
B--> X 
</blockquote>
 
6--> Boot with the OTHER module swapped: 
 
<blockquote>
A--> X 
B--> M1 
</blockquote>
 
At this point I got a great difference. It booted, finally. But in order to make a diagnostic, I have to complete the full test, and the results were: 
 
1--> Boot without any memory chip. 
 
A--> X 
B--> X 
 
NOT BOOTING Actually the computer not even tries to read the disk. Only the power led turns on, but even prior to press the 'on/off' button. I think this indicates 'no memory installed'. I would have expected a post failure beeps, but there were no beeps at all. 
 
2--> Boot with ONE module 
 
A-->M1 
B-->X 
 
BOOTED NORMALLY Well. This obviously means that the 3-1-1 beep code means memory error, or one bank failing of two installed. Now I didn't know if the problem was the module, or the bank B. 
 
3--> Boot with the OTHER module 
 
A--> X 
B--> M2 
 
NOT BOOTING Just like the condition in 1. Like no memory installed, therefore there are two possibilities: The bank B is not working, or the memory module M2 is not working. 
 
4--> Boot with BOTH modules swapped: 
 
A--> M2 
B--> M1 
 
NOT BOOTING Just like previous to test condition. Beep code 3-1-1, no boot at all. 
 
5--> Boot with ONE module swapped: 
 
A--> M2 
B--> X 
 
NOT BOOTING This was the important test, because it finally let me determine that the problem is at the module 2 (M2) not at the bank B. But still there could be a failure IN THE BANK B and IN THE MEMORY MODULE 2. Have to do the other test. 
 
6--> Boot with the OTHER module swapped: 
 
A--> X 
B--> M1 
 
BOOTING NORMALLY This really confirmed there is nothing wrong with ANY bank, but one of the modules is not working, actually is not being even detected. This is quite weird, because this computer was working perfectly with those two modules, and in the moment of the BIOS upgrade it seems to fail... How come? 
 
Something weird happened here. I don't know what, but something ruined one memory module (fortunately only one), what I would like to know now is what happened. But at least I have the machine running, with very low memory, but running. 
 
What I am thinking now is what about this BIOS upgrade makes the motherboard not to recognize one of the modules for some reason? 
 
<img class="jive-emoticon" src="images/emoticons/happy.gif" border="0" alt=":)" /> 
 
I will continue my research, but certainly the memory made the difference. 
 
I am not sure why I didn't discover this before, I think I didn't perform this test before, for two reasons: 
 
(1) I tried to boot with no memory, and this was impossible, so I assumed that the problem was not at the memory. 
 
(2) When I heard the beep code (3-1-1), somewhere I read it was a video problem, and I asume most probably it was a video problem (since no video at all was being displayed) but I should have take into consideration that Phoenix BIOS also means with the same 3-1-1 a DMA problem (memory problem). 
 
Okis... It's a pitty having to wait so much between a post and it's approval. I posted my answer two days ago, and since it didn't appear, I believe It didn't upload, so I replied again, and also didn't appeared... until now. It is obvious that a moderator approval is required. That's why I have to wait 24 hours or more to read my post. This slows this forum effectiveness. 
 
Thank you very much for your help. I'll keep you informed. Until we get to a final diagnosis and solution.

Core center readings VS. Bios readings ?

Hi there,
I am getting a core centre alarm saying my +12V is at 1.74V only!
The wierd thing is when i cehcked the bios system health tab all reading were ok for both +12 and -12.
What is the correct reading? the Core centre one or the bios?
See my sig. For my PSU specs.
i got windows XP Pro with all drivers and bios updated to the latset with "live update 3" by MSI.
Thank you!
Gil

dcasole,
You say
Not sure if this is the problem as I do not put any faith in CoreCenter but what I can tell you for sure is your powersupply is severly underpowered on the 12v rail if you are using a prescott .
If CoreCentre if not any good, should i trust PC alert 4?
And how come the health reading on the bios are all ok ?!?
thank you,
Gil

Incorrect Densitometer Readings

I am running Aperture 2.0 and recently did a greyscale test on a Canon 40D using an 18% grey card as the control.
The RGB densitometer readings (using the loupe) were largely as expected when reviewed with the 18% grey card falling in Zone 5
There are effectively 10 stops of dynamic range (Zone 0 to 9), and Zone 5 falls approximately in the middle of this dynamic range both as a numeric value and as a step in the greyscale.
There does seem however to be a notable anomaly in my results, as depicted in the spreadsheet below:
ZONE R G B
Zone 0 20 21 20
Zone 1 25 25 25
Zone 2 28 31 31
Zone 3 44 46 47
Zone 4 67 68 68
Zone 5 113 114 115
Zone 6 163 165 165
Zone 7 207 210 209
Zone 8 246 247 247
Zone 9 255 255 255
HOWEVER, an anomaly occurs in Zone 0 to 2 as follows:
1. In Zone 0 to 2 the RGB values seem squashed into a narrow RGB band (effectively 20 to 30)
2. As ridiculous as this sounds There seems to be no “pure black” zone in my grey-scale test.
I know it is not the camera as if I run the same test in the canon software I get more correct RGB readings with the final zone reading 0,0,0 for the RGB values, which is effectively pure black
Any ideas?

Hear is one idea - maybe different RAW processors process RAW files differently with different tone curves. Maybe that's what is causing this unheard of effect.
RB

Update to incorrect BIOS? 4200 VTD8X 128Mb

Hi, I've an MSI Gforce4 Ti4200 VTD8X with 128Mb. The card came with BIOS version 4.28.20.05.11, and I have updated it with the one at http://tw.msi.com.tw/autobios/SVga/Bios/Ms8894/v111/MS-8894.htm which is version 4.28.20.10.00.
But in the list at http://tw.msi.com.tw/autobios/VerChk/ListBios.asp says that the latest version for my card is the fist one, and now Live Update 2 says I have an TD8X64.
Will I have any problem with the second BIOS?
Where can I find the correct version for my VGA card?
Thanks.

For now don't do any BIOS updates, There has been some confusion with Live Update. I have sent notification to our contact at MSI but won't be addressed until monday or later due to the holiday.

URGENT: u410 incorrect bios version provided at Lenovo website

The u410 Ultrabook currently sold by Lenovo is being shipped with Bios version 65CN15WW.
Online, Lenovo provides an older version 65CN13WW.
Bios version 65CN15WW is corrupt, network problems with the wireless adapter have been reported. Also, Windows clean install on models with this bios are not possible, especially if the original partitioning table has been changed and the RAID has been deleted.
If one disables UEFI in bios, the bios can no longer be accessed.
Flashing the Bios witn version 65CN13WW is not possible. Because 65CN13WW is an older version of the bios, all attempts to flash the bios result in a message "invalid bios" and the flash is not applied.
THIS NEEDS TO BE FIXED ASAP. The different forums (English, Deutsch, Espanol) are littered with messages where users are not able to install Windows 7 and are not able to upgrade to Windows 8 because of this corrupt bios.

just to clear up one of the points made in this thread; it is not uncommon, (other manufacturers included), for a system to be delivered with a different bios version to that which is available for download.
This has been stated on previous occasions by Lenovo employees; an example.
Mark_Lenovo wrote:
sometimes we introduce newer versions into manufacturing to support an update to something like the chipset or later version of processor introduced during product life. Since the particular change doesn't apply (doesn't benefit) the field population, it may not be immediately placed on the support site for download. Development may wait for a later iteration that includes updates that are relevant (fixes) and then release that as a cumulative update.
Andy ______________________________________
Please remember to come back and mark the post that you feel solved your question as the solution, it earns the member + points
Did you find a post helpfull? You can thank the member by clicking on the star to the left awarding them Kudos Please add your type, model number and OS to your signature, it helps to help you. Forum Search Option T430 2347-G7U W8 x64, Yoga 10 HD+, Tablet 1838-2BG, T61p 6460-67G W7 x64, T43p 2668-G2G XP, T23 2647-9LG XP, plus a few more. FYI Unsolicited Personal Messages will be ignored.
Deutsche Community Comunidad en Español English Community Русскоязычное Сообщество
PepperonI blog

990FXA-GD80 BIOS temperature reading incorrect?

I got my board yesterday and i put in an AMD Phenom II X6 1100T CPU with cooler master V8 cooler. I have the Fan Speed on it set to max 2100 RPM and applied artic silver 5. On my old board MSI 890FXA-gd70 the cpu temp in the bios displayed 33-35C however in the 990 it says it is constantly at 53-55C. I took it apart again cleaned the cpu and the v8 with Isotropyl 99% alcohol, reapplied thermal paste (first time i reasoned maybe the layer was too thick so i only applied a small pea sized ammount of AS5 and spread it to thin layer) and again same problem. I then decided to check temps via software. So i installed Win7 fearing the cpu might overheat for some reason but it installed just fine. I downloaded HW Monitor since that program can be installed quickly and read temps on the fly and it displayed that the CPU cores (Cores #0-#5) were 27-28C idle and when i was updating the cores worked up to 35C-36C. I then installed MSI Control Center latets version 2.2.024 and it said cpu temp was 33C and system is 36C. I looked back to HW Monitor and matched System temp with TMPIN2 Temp listed in HW Monitor. TMPIN0 reads 44-45C constantly i reasoned this must be NB temp. I looked back to the bios after rebooting and the temps again were 53C-54C for CPU and 35C-36C for system. Based on readings from HW Monitor, MSI Control Center and AMD Overdrive (i downloaded that one too to be sure) I am going to have to assume that the BIOS temp readings for CPU are incorrect. In HW Monitor there is no reading labeled "TMPIN1" or "CPU" and it was the only program that would say the general temp reading of my CPU. Does anybody else have this problem? Should I just shrug it off and say meh it happens? If for any reason my CPU is running too hot what are the symptoms of overheating? Thank you :smiley:

Quote from: Fredrik on 11-August-11, 07:37:52
Odd you get correct(?) readings from software programs - they have no separate thermometer. Sure, BIOS may be incorrect. That is a common problem, but then your monitoring programs should be up the wall, too. More common is in fact, the BIOS readings are correct and programs are wrong.
Comparing with a different system is impossible. Case and cooling can not be the same; a case built for a Pentium II wont cope nicely with a 6-core processor of today.
well apparently its happening to me, and im not the only one. That other dude using water cooling and his bios temps are 20C of true readings. looking at it from a coding perspective maybe its just adding 20 to the temp. by mistake, but i can't say for sure since I am expert in programming languages not so much into BIOS and firmware kinda stuff.

[MSI P55-GD65] Different XMP readings from MSI Control Center, CPU-z, BIOS

Hello,
I have a MSI P55-GD65 with a 4 GB Corsair XMP DDR3-1600 CL8 kit (2x2GB, in dual channel configuration),
however I am getting very different readings for the XMP profile from MSI Control Center, CPU-z and the BIOS.
Here is a screenshot from CPU-z and Control Center: http://img683.imageshack.us/img683/2217/xmpv.jpg
The memory is rated at 1.65v for 1600mhz CL8, however control center reports it as being 1.5v, CL9.
CPU-z reports timing rate to be 2T, however when setting the RAM settings to XMP/Auto in the BIOS (which automatically clocks to 1600 mhz, CL8),
timing rate gets set to 1T (which tends to be unstable with CL8).
So my question is: how can I reliably read the XMP information? My bios is the latest version by the way (v1.9).

Quote
the bios readings are almost the same, except that the BIOS sets 1T timing.
The BIOS readings (or: what the BIOS actually sets) is not that important when we talk about SPD/XMP Profiles. When you are in BIOS Setup you should be able to find Memory-Z which does nothing else but reading the SPD/XMP Profiles that are programmed onto the SPD Chip (regardless of what the actual settings are).
Quote
So I'll just use the bios XMP settings but change the timing to 2T and see if that is stable.
Yes. AND: The fact that the BIOS automatically sets the Command Rate to 1T instead of 2T is not okay. Please report this problem to MSI Technical Support: http://support.msi.com/

I have to change bios rev. Which version?

Hi to u all,
I'm tired of MSI's late with no advice to develop a new bios release, also because the previous versions are all affected by some problems.
But i've got to upgrade my bios now, I've got a 1.20 release, all but stable with my configuration (cpu and nb temp detection failure and crashes).
In your opinion, what's the most stable release for the 875P neo bios?
I've read that 1.60 has problems with the "light" overclock it does also at slow mode to the AGP bus... Somebody with ATI video cards finds this a real problem?
And also: some bios releases , in e.g. 1.50 or also the beta like 1.74... Where should I find that? On MSI's website there's nothing except the official version 1.0, 1.20, 1.40, 1.60.

Quote
Originally posted by goalie20
lordtheuz-other than incorrect temp. readings-what are your specific problems with 1.2 bios? There should be no \"automatic\" overclocking with that bios.
There SHOULD be... In fact, i don't know if my probs could be related to the "automatic overclock" feature, but...
- I've got MANY crashes, specially when playing, that make me think that this is a video card related problem... But it's not a software thing, it's probably a problem between the mobo and my Radeon9500 (not pro).
No one of the games i play (there are about 15 games on my pc) works well... sometimes the computer freezes, sometimes it autoreboots without any advice, sometimes gives me some errors at the startup of win2000 (original, certified, and updated version with every service pack).
I think i'll pass to the 1.50 release... Hoping that everything goes well, I could be not the first to have an MSI mobo "wrecked" by a bios update... I've read one just 2 days ago on this forum.
Bye! :D

990FXA-GD80 - Incorrect voltages

Hello All,
I just picked up a new MSI 990FXA-GD80 V2 am experiencing some interesting issues. My CPU is a 960T that unlocks to a stable hex-core. On default settings, everything works as it should. When I set a voltage manually in the BIOS, things start to get wonky. Cool 'n Quiet only has two voltage states: one is .04v - .06v over the voltage I set in the BIOS, and the second (which only comes into play at high load) is .04v - .06v over the first. For example, I have the CPU Voltage in the bios set at ~ 1.31v. The voltage for idle through ~ 80+% utilization is 1.35v - 1.37. The voltage at max load is 1.40v - 1.42v.
The board came with BIOS version 13.5. I reflashed the BIOS to see if that might have something to do with it. I even flashed back to a D4 BIOS and the results are the same.
Is this typical behavior with the D4/D5 BIOS and a AM3 CPU? If anyone could shed any light on this, I would greatly appreciate it. I will be finishing up my troubleshooting, and isolation of the problem when I get home from work tonight, then I will be contacting MSI as well. I will be sure to post any reply I receive from them here.
The system specs are as listed in my sig.
Thanks for your time.
P.S.: I prefer to overclock with Cool 'n Quiet on because the CPU is cooler and far more efficiently utilized with the lower power states. It is, at max, a 1% penalty on a Phenom II. The increase in the longevity of my CPU worth the extra 30 - 40 Mhz to me.

Quote from: Fredrik on 11-August-11, 07:37:52
Odd you get correct(?) readings from software programs - they have no separate thermometer. Sure, BIOS may be incorrect. That is a common problem, but then your monitoring programs should be up the wall, too. More common is in fact, the BIOS readings are correct and programs are wrong.
Comparing with a different system is impossible. Case and cooling can not be the same; a case built for a Pentium II wont cope nicely with a 6-core processor of today.
well apparently its happening to me, and im not the only one. That other dude using water cooling and his bios temps are 20C of true readings. looking at it from a coding perspective maybe its just adding 20 to the temp. by mistake, but i can't say for sure since I am expert in programming languages not so much into BIOS and firmware kinda stuff.

K8N Neo2 platinum: should I flash to 1.3 bios?

Currently I have BIOS 1.1. Does anyone recommend that I should flash to 1.3?
I was not sure what this buys you. I do have some problems with temperature reading, perhaps this might go away.
Anyhow, maybe someone knows if it fixes some major bugs lurking out there that I might want to fix now before I find them.
What is your recommendation? Perhaps I should wait until version 1.4 comes out?

Well. I have the same board (Neo2) and the bios upgrade from 1.2-1.3 stated that it resolved incorrect temperature readings according to the MSI driver's download page. I would assume that since you have 1.1 this would also be the case.So in answer to your question, YES.

Bios Flashing and Recovery

BIOS FLASHING
We do not recommend using the MSI LiveUpdate tool to update your BIOS! It may be okay for updating your drivers, but please do not use it to flash the BIOS in Windows!
Windows-based flashing - If you REALLY insist on flashing the BIOS under Windows, if you encounter any error during flashing, whatever you do, DON'T restart your PC! Try again until the flash is successful, otherwise your board will not start! Disable any anti-virus program (along with any other programs) prior to flashing.
Boards with built-in M-Flash function - While M-Flash work's properly most of the time, it has still proved to be less reliable than the forum tool / manual flash.
Before flashing your BIOS, you must ensure your system is fully stable! Any instabilities can cause a bad flash and create an expensive paper weight. Included with the forum flash tool is MEMTEST, we recommend running this for 2 or more passes prior to a flash.
If you do not understand what your BIOS is, or what it does, please read: >> BIOS. What it is, and all you need to know <<
Our first choice we recommend you use is our own USB flashing tool, developed by Svet.
It is important to note, that the only way to flash the ME extension of the BIOS of modern Intel boards is through the use special processes. The bios versions posted by moderators here: >>BIOSes<< include the additional files to accomplish this. These bios are all official and are directly from MSI.
>>>MSI Forum HQ USB Flashing Tool<<<
If you are unable to use the MSI HQ USB BIOS Flashing Tool
>>How to create a dos bootable USB stick>>
It is important to note that if any BIOS, EC FIRMWARE or any other type of FIRMWARE downloaded from MSI for a manual flash contains an BAT file it must be used. Not doing so will cause the flash to fail and require RMA.
For Intel Users, flash via FPT
Socket LGA 1150 : >>ME 9 FPT files & Instruction>>
Many of the bios versions posted here: >>BIOSes<< Contain a .bat file. All you need to do is extract all of the contents of the archive into the root directory of a DOS bootable USB stick and run the bat file from pure DOS.
Socket LGA 1155 & 2011: >>ME 7&8 FPT Files and instruction<<
Linux users
See this topic: >>Flash your BIOS, the Linux way! [beware the dangers!!]<<
Modified and BETA BIOSes
Use only at your own risk! All BETA BIOS versions posted by the moderators of this forum are directly from MSI and will not effect your warranty.The use of user modified BIOS versions may damage the board and may void your warranty. Exercise extreme caution in regards to user posted BIOS versions. Please also be aware that MSI and this forum can not be held responsible if you trash your mobo by using a modded, beta or otherwise incorrect BIOS.
WHEN IT ALL GOES WRONG...
BIOS RECOVERY
In many cases, provided the 'bootblock' of your BIOS is not corrupted during a bad flash, the BIOS can often be recovered by following the recovery procedures detailed below. NOTE: this recovery method should not be followed for normal practice of updating your BIOS!
For Modern MSI Systems, refer to:
<<Multi-Bios Equipped Mainboards>>
<<Single-Bios Equipped Mainboards>>
Legacy Systems:
For Award BIOS
Make a bootable floppy disk*
Copy the Award flash utility & BIOS file to the said floppy disk
Create an autoexec.bat with "Award_Flash_Utility BiosFilename" in the content (e.g. awdfl823K w6378vms.130)
Sample on how to create an autoexec:
a. On Windows, open the notepad
b. On the notepad, write "awdfl823K w6378vms.130" (without the " ")**
c. Save the file as autoexec.bat
Boot up system with the said floppy (it will take less than 2 minutes before screen comes out)
Re-flash the BIOS & reboot.
*Need a bootable floppy disk? Look here: http://www.bootdisk.com
**Make sure you enter the correct filenames for your flasher program and BIOS ROM file!
For AMI BIOS
Rename the desired AMI BIOS file to AMIBOOT.ROM and save it on a floppy disk. e.g. Rename A569MS23.ROM to AMIBOOT.ROM
Insert this floppy disk in the floppy drive. Turn On the system and press and hold Ctrl-Home to force update. It will read the AMIBOOT.ROM file and recover the BIOS from the A drive.
When 4 beeps are heard you may remove the floppy disk and restart the computer.
For new boards with AMI BIOS core 8 (4MB)
Discovered by Jack The Newbie:
Of course, the steps are similar to the standard AMI BIOS Recovery Procedure for internal floppy drives (rename corresponding BIOS File to AMIBOOT.ROM, hit CTRL + HOME after starting the system).
What has to be done (tested on P45 Platinum):
1. An optical SATA Drive needs to be connected to one of the Intel ICH10R SATA ports. {After a lot of testing, I found that it does not work with the same optical drive connected to the SATA Ports hosted by the secondary JMicron Controller. Also, using an optical drive on the JMicron IDE/PATA port does not help either.}
2. A proper BIOS File has to be renamed to AMIBOOT.ROM and burned on an empty CD.
3. CMOS-Clear with main A/C power cable removed from PSU has to be performed. {If this step is not done, the system will reboot after pressing CTRL + Home and will not proceed with recovery procedure.}
4. Press CTRL + Home to trigger BIOS Recovery. -> The system should enter BIOS Recovery Routine. {Will basically work with both USB & PS/2 keyboard. However, a PS/2 Keyboard is recommended as the system will respond earlier to PS/2 Keyboard than to USB Devices.}
What should happen now:
1. After pressing CTRL + HOME the LED Status should change to "Intializing Hard Disk Controller" and there should be access to the optical drive connected to the Intel ICH10R SATA ports.
2. It can take up to 30+ seconds until the BIOS File that was renamed to AMIBOOT.ROM is found. {Drive Bay can be opened to try a different CD without turning off or restarting the system.}
3. When the system finds the BIOS File, LED Status will change to "Testing RTC" and there should be a message on the screen indicating that the Flash Recovery Procedure has started.
4. Since the BIOS File is 4MB in size, it will take a while until the BIOS is actually reflashed.
Its also possible that BIOS recovery on boards with AMIBIOS8 can be done using a FAT-formatted USB stick, containing the renamed BIOS file. Be warned, in some circumstances it may take several moments before recovery procedure actually begins. See Bas' reply below for further information.
BIOS recovery on Wind netbooks
See this post here:
https://forum-en.msi.com/index.php?topic=130509.msg982711#msg982711
BIOS recovery on non-UEFI notebooks
In order to recovery this type of system you will need an FAT32 formatted USB stick.
Download the applicable bios from MSI's website and rename this bios.
It must be re-named to either AMIBOOT.ROM or xxxxIMS.ROM / xxxxAMS.ROM You may need to try each way to determine which one is necessary.
Then place the renamed bios onto the root directory of the FAT32 formatted USB stick.
Now you are ready to cover the Notebook.
To do this, remove the AC power cord and battery. Once that has been completed, install the USB stick you prepared earlier.
Now, apply AC power (leaving the battery disconnected) and turn on the notebook. Recovery should begin after 5 minutes.
IF ALL ELSE FAILS...
Locate the BIOS chip on your mainboard. If it is soldered directly to the PCB like...
...then you have no choice but to return the board to your supplier, or to MSI, for replacement.
To request an RMA from MSI, open a support ticket at https://register.msi.com/ocss/
If your BIOS chip is in a socket, like...
...then you may be able to source a replacement BIOS chip, either from MSI, or from a website such as www.badflash.com
Updated 11/21/2013, original post by Stu

A.) Download >>this<< bios archive and place it on your desktop. Do not decompress.
B.) Download and install the >>MSI HQ Forum USB flasher<< .
C.) Insert your FAT32 formatted usb stick.
D.) Make sure that all win 8 options are disabled. (Fast Boot etc) Also make sure the legacy USB is enabled.
E.) Start the forum flash tool and select option 1. Then point the tool at the compressed archive we downloaded earlier. Then to your USB Flash Drive.
F.) Boot to the USB from working bios B.
G.) Once it booted successfully switch to bios A without powering down or rebooting
H.) Now follow the directions and let the tool flash bios A with desired version

BIOS Update Fail - Aspire XC-603G Win 8.1

Hello,I have searched here for a couple days and read a bunch of posts - some of which I have tried. I am NOT trying to go back down to Win 7 (though I really like Win 7) I am trying to stick with Win 8.1. I was running BIOS P11-A1 and suddenly started having trouble with the USB 3.0 controller.I read some posts here and on other forums that stated I should see if there is a BIOS update. There are actually four for this machine and so I started with the oldest one P11-B0LTTo be honest the instructions in the README pdf file were not that helpfulbut I found soem great data on the AMI website that helped me update to P11-B0L. I ran the BIOS-DOS.BAT file first but got this error: "4 - Error: ROM File ROMID is not compatible with existing BIOS ROMID"So I went ahead and ran the AFUDOS file without all the parameters in the batch file and everything updated fine. But I am still having troubles with the USB 3.0 controller and the process just seemed to be fairly complex.Both my HP's and three other Dell's had Flash BIOS programs, or simple instructions that worked with no problems. Was I just getting lucky with them and there is some hidden UEFI and/or MS-DOS secret ritual that I am missing here ?Am I perhaps using the incorrect BIOS update file - and if so which one should I use ? Thanks,-Bil

Thanks that makes sense. Would of course be nice if Acer didn't offer them as options when one selects Win 8.1 as the OS.Or at least put that note in the description for each. I of course got jammed up when I forced the next BIOS version (with the "L") after B2 worked fine. She was hanging up at the POST so I cleared the CMOS by swapping the jumper pins.I then put the B2 BIOS on the USB and renamed it AMIBOOT.ROM and I am back to a functioning box. USB 3.0 controller is still DOA but I am probably going to dump this MB for one with a couple PCI slots.I have been wanting to dump the Celeron POS anyhow - and this will be my tester for Win 10. Thanks again for the info and maybe it will help the next poor soul...Consider this one resolved -bil

6714 Ver 1 BIOS issue : will not boot OS

Hi ya,
I'm wondering if there's a way to force the flash program to replace the BIOS even though it detects it as a different / incorrect version ?
Just having an interesting problem with an old(ish) MSI 6714 motherboard.
The system was installed and working fine on a users desk, however we replaced the 6714 machine with a newer one and were going to re-format 6714 system, re-install the OS and use it to replace another users system.
During the OS installation (Windows 2K SP3 corp media), after the first re-boot the system will blue screen with an error similar to IRQ_NOT_EQUAL_TO or something to that effect.
No matter how we installed the system it kept dying at the same point.
I tried ghosting a copy of the OS onto the HDD, however it gets to the initial 'Windows 2K press F8' part, the loading line flicks across, and then it hangs.
The machine always POSTS and always allows entry to the BIOS.
A strange thing is though, if you change the 'USB Mouse Support' option from Disabled to Enabled then the system POSTS as normal but dies before it even brings up the 'Windows 2K press F8' section.
Looking at the BIOS though I think this system has been installed with an 845GEM Bios, when it may have needed the 845GVM Bios instead .. as the board has no AGP slot.
I've found some other people in the Forum's who have encountered a similar issue, but none of the links in the replies have worked.
The current BIOS on the sustem is the 2003/05/07 845GEM v1.2 BIOS (4Mb)
There isn't an updated version of this BIOS, and this was the BIOS version that was on the system before I started messing around with it (I tried over-writting it again but it does the same thing when booting the OS).
To be honest I think I encountered the same problem when I first got the system, but I somehow got it working by ghosting a copy of the OS onto the system. That may have just been pure luck though .. as nothing I've tried has gotten this system to work.
Specs are :
AOpen H340D case
MSI 6714 Ver:1 (BIOS 845GEM v1.2 2003/05/07)
256Mb DDR266 (tested with MEMtest without error)
WD 300B/400B drives (we've tried a few)
Also tried it with a PCI graphics card to no effect.
All capaciters are flat and look in good condition.
All cables have been checked and changed.
Thanks ???

Thanks Greyone, but I think I found the problem.
In answer to your Q though, the chip in front of where the AGP slot should be has a sticker on it saying 845GV ICH4.
System was made up by one of our venders. But I'm not sure if they could have been the culprit for the incorrect BIOS though as they would have had to have forced the BIOS onto the system since it returns a BIOS-Lock error if you try the GEM Bios on a GVM system and vice versa.
I downloaded the MSI-6714 845GVM v4.2 bios and flashed it with the /f switch, and it seems to be running ok.
Windows 2K had to find all the hardware again (and required the driver files for the GFX card), but it does now seem to be running and stable (that is if you can call something stable thats only been running for 45 minutes thus-far )
Hope this post can help out anyone else who comes across this issue though.
Thanks

HP mini 110-1116NR BIOS password

when I start my net book (HP mini 110-1116NR) its asking me for password and then Error-CNU94198NX
Please someonetell me whats happening

Hi,
It looks like your machine has generated a halt code which happens after entering an incorrect Bios Password 3 times, so try the following.
Please be aware that this is not supported by HP and you try it at your own risk.
Try entering e9lov3ou94 ( Note: the 3rd character is a lower case L )
Regards,
DP-K
****Click the White thumb to say thanks****
****Please mark Accept As Solution if it solves your problem****
****I don't work for HP****
Microsoft MVP - Windows Experience

Incorrect bios readings

Similar Messages

Maybe you are looking for