To users of MSI 6800GT running doom3

does any of u guys experience a form of horizontal pixellation/distortion which occurs when u move the character from left to right during the game? I notice this and although its not bad to a point which makes the game unplayable .. it is still visible... it doesnt occur when not moving ... is this normal ? updated vga drivers n bios to the latest already and also installed the patch for the game

MSI 875P NEO FISR FSB 800 HT BIOS V3.1
INTEL P4 2.8 prescott @ 3.15 FSB800 HT
MSI NX 6800GT(copper sink ver.) o/c 375mhz .6177 MSI Drivers
Kingston DDR400 DUAL CH 1GB
HDD Maxtor D'Max9+ 120&160 GB 8M cache
DVD-ROM Pioneer DVR 107
Onboard sound 8ch surround, 33ch Realtek AC'97 Audio
COLORSit 550w PSU (PCF)
WIN XP Pro SP1 (media player10 best yet)
MONITOR IIYAMA Vision Master Pro411 19"
PRINT epson R200
Microsoft Multimedia Keyboard & Intelli Mouse Optical
2 CASE FANs (system temp. 28c)
3DMark 01: 19121
3DMark 03: 11690
3DMark 05: 4087
Aquamark : 60656
GFX : 8958
CPU : 9388
Doom III 65fps on High 1024x768
This is due to the frame rate going higher than the refresh rate of the game VSync swiched on gets rid of it but also drops your framerate by about 10 frames which might make it too slow if your only getting 40 to 50 fps
P.S i get it too also a bit on Far Cry

Similar Messages

MSI 6800gt problems

Last week i baught a MSI 6800gt to replace my old mx440. All was going well for the first day however when i went to play any games or anything the next day my computer would crash( this appears to be a result of the screen resolution changing). I got the latest drivers off the msi site which didnt fix it so i got the lates ones from the nvidia website which had no effect either. I also did a compelte re-install of windows but it did nothing.
When i first put the card in i could run all the 3dmark03 tests however now it gets to the cpu tests and displays an error message(cant rermember the exact message). Also I cant load up any farcry levels( computer restarts its self) and in brothers in arms if i try to change the screen resolution it either turns my monitor off and i cant turn it back on without restsrting or makes the screen flicker black and orange. If i do manage to get the game to run when i exit out windows stays on the same resolution as i was playing and if i try to change it it tells me i have to restart the computer.
Can anyone help me. Did i get a dodgy card? or does it have compatiblity issues with my motherboard? im fresh out of ideas

Im now running a new motherboard - ABIT NF7-S not that this has helped matters. This involved formatting and re-installing windows, with the latest nforce drivers and graphics drivers(v71.89) all was good for the first time i ran my computer but after re-booting it was back to its same old problems.
I tryed my card in my mates computer (A64 3500+, 1Gig Geil RAM, Antec True480 PSU) who also has a MSI 6800GT which worked fine with both mine and his cards. His card however wouldnt work in my computer. After putting the card back into my computer i disconnected my 2nd HDD, Case fans and Hardcano, put my CPU back to stock settings, and pulled out my VT and network cards, all of which had no effect. This is driving me up the wall, all i want to do is to be able to play Farcry and HL2 and it wont work Interestingly enough i can play DX7 games with no issues however it appears that anything using DX8 or 9 wont work. HL2 turns my monitor off and farcry restarts my computer. I have even tryed changing resolutions and refresh rates of my monitor (Samsung 753DFX) not that it made any difference.
If anyone is having similar problems and managed to fix them can you let me know how.

MSI 6800GT

a have a NX 6800GT-T2D256E that looks not like the other MSI 6800GT-T2D256E... on the MSI site is the VGA colored red, and has a big red cooler... But my 6800GT is greed and looks like a NVIDIA 6800GT reference card.. ??? is it a fake 6800GT one?

That copper cooler has one huge draw back... it uses thermal pads for the memory cooling, -AND- the GPU temp overheats the memory, because of the ONE LARGE sink design... I think... I have noticed more and more of these red PCB MSI 6800GTs with this cooler and no one seems to get above 1070 or so on the memory... I am so going to go with the new Vantech or Logisys VGA copper cooler and ram-sinks for this... this is a good card! it's got Samsung memory on it and my cards don't OC worth anything... and I think it's this cooler... also, the mosfets have a large thermal pad between them and the copper sink on my cards... and they run HOT... I can't help but to think that is not the best way to make good use of that copper cooler... thermal pads are just not great heat conductors... hmmm... well, anyways... I am thinking about stripping the coolers off of my PNY 6800GT and trying them on my MSI... it's got the reference cooler on it... and it OC's like a BEAST. lol.
I was alll psyched that this copper cooler would be awesome... but am pretty bummed that it's got thermal pads...and it's noisy as hell at the all but the fastest fan speed. what is up with that. wow... anyways. I hope others have having better luck with these cards than I am.

MSI 6800GT-T2D256E and power problem?

I've got ASUS A8N-Deluxe mobo, Nexus 400W PU and new, bright and shiny MSI 6800GT-T2D256E
And I get the damned:
"The NVIDIA system sentinel is reporting that the nvidia powered graphics card is not receiving sufficient power. To protect your hardware from potential damage or causing a potential system lockup, the graphics processor has lowered its performance to a level that allows continued safe operations."
message...
Tried diffrent lines from PU, different drivers, nothing. I get the message right after login.
One funny little thing: there's a sticker on the power cable that came with the card (close to the 2x3 connector) that says:
For use with RADEON X800 series graphics card only.
Could this be the problem or are the pwr cables the same for 6800's and X800's? Card works the same with or without pwr cable.
Looking from the left side of an open case (w cable attced to the card) there are two wires going into the leftmost holes of the 2x3 connector - yellow (top) and black (bottom).
Here're the PSU specs
Min Load NormLoad    Max Load   Load REG. Line REG. Ripple & Noise
+3,3V     0.5A     15.0A     3.0/30A   ±5%     ±1%   50mV P-P
+5V     1.0A     14.0A     10.0/28A   ±5%     ±1%   50mV P-P
+12V1     1.0A     7.0A     4.5/14A   ±5%      ±1% 120mV P-P
-12V2     1.0A     8.5A     5.55/15A   ±5%     ±1%   120mV P-P
-12V    0.0A        0.4A     0.5A     ±10%    ±2% 120mV P-P
+5Vsb     0.0A     1.0A     2.0A     ±5%     ±1%   50mV P-P
http://www.nexustek.nl/nx4090.htm
I have 20pin and 4 pin pwr connectors connected to the mobo.
Any ideas?

Update:
Tried HEC 475W psu - didn't help. Went back to the store, they tested the card and it seemed to run just fine.
So it's not the card nor the power cord problem. Guys at the strore said - get better psu. But I've tried better psu?!
So I threw out everything exept HDD - no luck.
This brings me to another question. I keep noticing peaple talking not just about watts but amps. My Nexus and that
HEC I tested produce 14 and 15 amps respectively.
Sadly in a small country stores don't keep expensive psu's on they shells. So I should order one. I want to be sure before that.
Any comments on the amperage issue?

[GeForce 6] I'm Cheated/receive wrong specs...MSI 6800GT, a Problem...what should i do...???

I recently bought a graphics card which is the MSI 6800GT...after i browse aroung the net i found out that MSI has flawlessly manufactured the card by putting an NV40 gpu instead of NV45...
below are the links and news about it:
Link 1
Lnik 2
Link 3
Link 4
MSI Responds Here...
MSI Will Replaced the Cards.....
Confusing & Confusion
What should i do....Should i go straight away to Cycom and ask them about replacing my cards....or should i contact MSI distro here in Malaysia...which is just to be Enlight....

antonio_zth,
MSI sells over a million Vid Cards a Month. There were a total of 350 vid cards with the wrong Pipelines and Vertex Units. I had one of them, so that only leaves 349 of them out there. By now all the Vid Cards in question should have been sent in to MSI and swapped out.
I would run Riva Tuner and see how many Pipelines and Vertex Units your Vid Card, if you have 16 Pipelines and 6 Vertex Units, then you have the correct card.
Take Care,
Richard

How many users on router? run torrent

I share my router and I have "off-peak" internet time 2am to 8am - I needed a script to see if I am the only user on-line so that my torrents don't suck up the other people's bandwidth...
This works:
#!/bin/bash
# should torrent run?
# using a router shared by a number of people
# If I am the only user or it is off peak time (or other concerns) then decide whether to run torrent
#functions
# check who's online
function checkingprocess {
# start by saying there are zero users
homeusers="0"
echo "home users reset to zero"
# nong (important other user) is not on
nong="no"
echo "nong set to no"
# get the file with MAC addresses of people connected to wireless router
wget http://192.168.1.1/wlclientview.cmd --http-user=USERNAME --http-password=PASSWORD
echo "got list"
mv ~/wlclientview.cmd ~/mybin/whoosonline
echo "moved list"
# check if others are on-line
homeusers=$(grep -c "<tr>" ~/mybin/whoosonline)
echo "counted $homeusers table rows"
# remove extra 3 that are not useful
homeusers=`expr $homeusers - 3`
echo "that means we have $homeusers users (result -3)"
# check for special case "nong"
if grep -q "MAC:OF:USER:NONG" ~/mybin/whoosonline
then
# special case - Nong is online too
nong="nong"
echo "nong online"
else
echo "nong not on line"
fi
# report total to text file for conky to display
echo $homeusers > /home/tawan/mybin/whoosonlinenow
# check the time
function timechecker {
# off-peak internet use between 3 and 6 am
# actually 3 to 8 but give others a chance early morning from 6
TIME=`date +%H`
if [ "$TIME" -ge "02" ]
then
mytime="offpeak"
echo "off peak time?"
if [ "$TIME" -le "05" ]
then
mytime="offpeak"
echo "off peak time"
else
mytime="peak"
echo "peak time"
fi
else
mytime="peak"
echo "peak time"
fi
# run
function myrunner {
ps aux > /tmp/ps.log
# look in the file for this name to see if it is running
if grep rtorrent /tmp/ps.log
then
appcheck
if [ "$appkill" -ge "1" ]
then
echo "can't run torrent $appkill x web app open"
else
echo "torrent already running"
fi
else
echo "run torrent"
appcheck
if [ "$appkill" -ge "1" ]
then
echo "can't run torrent $appkill x web app open"
else
urxvt -g 46x1 -title rtorrent -e rtorrent -o http_capath=/etc/ssl/certs &
fi
fi
# kill
function mykiller {
ps aux > /tmp/ps.log
# look in the file for this name to see if it is running
if grep rtorrent /tmp/ps.log
then
killall rtorrent &
fi
echo "kill torrent"
# app check
function appcheck {
appkill="0"
# skype - kill torrents if skype in use
myapp="skype"
appkiller
# chromium - kill torrents if chromium in use
myapp="chromium"
appkiller
# firefox - kill torrents if firefox in use
myapp="swiftfox"
appkiller
# app killer
function appkiller {
if grep $myapp /tmp/ps.log
then
mykiller
echo "killed because of $myapp"
appkill=`expr $appkill + 1`
fi
# think about it all
function mythinker {
# in peak time we run if you are the only user
# in off peak time we run even with other users
# unless that user is nong and so we kill later
# always kill if nong is on-line
if [ "$nong" = "nong" ]
then
echo "nong on-line so kill torrent"
mykiller
else
if [ "$mytime" = "offpeak" ]
then
echo "....off peak time. Let's run torrent"
myrunner
else
if [ $homeusers -le 1 ]
then
echo "....peak time and think only user is you so run torrent"
myrunner
else
echo "....peak time and other users on-line so kill torrent"
mykiller
fi
fi
fi
#end functions
#loop
while [ 1 ]
do
echo "start of loop"
# run the above functions and loop
checkingprocess
timechecker
mythinker
echo "done functions, will sleep"
sleep 20s
echo "end of loop"
done
#end loop
edit : improved
Last edited by tawan (2010-07-25 07:05:20)

QoS means Quality of Service. Basically it reorders or delays packets depending on priority, so that time-sensitive packets always go first, and unimportant packets like bittorrent can be delayed until there is no other traffic being sent. What I specifally was suggesting here is that your use it to lower the priority of bittorrent traffic, so that you can run it all the time but it only uses spare bandwidth that isn't being used by any other service.
The only catch most routers can only do QoS on inbound connections which is mainly helps latency and not download speeds. However, if your router is running linux it may have that ability. Also look for the 'tc' utility or maybe you can install trickle.
This thread has little bit more info.
Last edited by xenobrain (2010-07-20 14:11:50)

We have two users that have been using Creative Cloud for almost a year. Recently, sometime in the last 4ish weeks, the users can no longer run Creative Cloud apps. (Yes, our subscription is paid.) Error simply says administrator access is required

We have two users that have been using Creative Cloud for almost a year. Recently, sometime in the last 4ish weeks, the users can no longer run Creative Cloud apps. (Yes, our subscription is paid.) Error simply says administrator access is required to install. The apps have already been installed. The users cannot run them unless they are in the local admin group.Using "Run as admin" does not work. It gives the same error.
I have opened a case with adobe support and was basically told to suck it up and put the users in the admin group. Actually, what was said was that it is "mandated that the users have administrative rights".
There are a couple of things wrong with this. It was working for both users until recently - a recent required creative cloud update. The users have never been local admins yet the apps were working (poorly, but working).
We are in an enterprise environment and users simply do not have administrative rights on the computers.
I have changed permissions on all adobe folders, granting users or authenticated users modify or full control rights, did the same in whatever Adobe registry HKLM keys I could find. Nothing has allowed the users to run the apps - unless they are put in the local admin group.
Someone has to have a fix for this. Adobe apps have proved to have far too many vunerabilities to even entertain the idea of elevating user rights. I can't imagine that enterprise environments are allowing this.
Any help or suggestions are greatly appreciated.

Jeff,
Thank you for your response. The users in question are "standard" domain users. We do not reduce users permissions below the standard level.
The apps do not load with their current standard user permissions.
The thing that makes this odd, is that up until recently they did this issue with cloud apps. The only way I can make it work for them now is to put them in the local administrator group on their pc's - which is not going to happen.
This is what they now see. As I said before, this was not a problem up until recently they would see all their available apps. If I put them in the local admin group the apps are listed without having to install. Everything is there, just not accessible to the user.

User not able to run a report from the portal

Hi Friends,
We have about 15 reports assigned to a Role. When the user logs on to the protal under new analysis --> Role he/she can see all the reports. One of the user is able to run all the reports except one. the user exectutes the report instead of showing the report out put following error meassage is comming "User is not authorized".
Can someone please suggest how come the user is able to see all the reports except this on.
This report is available in the role, i have checked PFCG and the user has the access to this roll.
Your help is appreciated.
Regards
BN

Hi friends,
As suggested I tried ST01, but unfortunately i dont have authorization for st01.
I did get the copy user of the actual user and i exectuted the report using RSECADMIN, I did check the box with Log and able to execute the report from RSRT. In the output was getting No Authorization, so i went back and checked the Log and in the Log it was showing the two Info Objects 0QUOTA and 0TCAACTVT do not have auhorizations.
0QUOTA is available in the cube, so i will ask the security team to include this in the role will *, but 0TCAACTVT is not used in my cube or in MP then why is it showing up in the logs?. Can someone suggest me please?.
Regards
BN

How to capture the user name who is running concurrent program

Hi Everyone
In oracle apps when i want to store the user name who is running a concurrent program in specific responsibility.
For that I created a table as USER_INFO which has a column called USERNAME.
T o capture the user name i created a before report trigger and wrote the following code which will store the username into USER_INFO
function insert_trg return boolean is
begin
insert into USER_INFO(USERNAME) values
(select fnd_profile.value('USERNAME') from dual);
COMMIT;
return (TRUE);
end;In the above code i used fnd_profile.value('USERNAME') to store the username but after running the concurrent program when i am query the table it returns no rows .
It means the fnd_profile.value('USERNAME') is not storing the value.
Please tell me what to do?
Regards
Sabyasachi

In order to fetch any FND_PROFILE or FND_GLOBAL values you need to initialize apps
fnd_global.apps_initialize(user, resp_id,resp_application_id)
begin
fnd_global.apps_initialize(0,20420,1);
dbms_output.PUT_LINE (FND_PROFILE.VALUE('ORG_ID'));
dbms_output.PUT_LINE (FND_PROFILE.VALUE('USER_ID'));
dbms_output.PUT_LINE (FND_PROFILE.VALUE('USERNAME'));
end; Check the following MOS note
How To Set the Applications Context (FND_GLOBAL.APPS_INITIALIZE) [ID 209185.1]
Cheers,
ND
Use the "helpful" or "correct" buttons to award points to replies / Mark the thread as answered, if your question is answered.

What previlege does user HR need to run a scheduler?

What previlege does user HR need to run a scheduler?
conn system;
BEGIN
DBMS_SCHEDULER.create_schedule (
    schedule_name   => 'add_partition_hourly_schedule',
    start_date      => SYSTIMESTAMP,
    repeat_interval => 'freq=hourly; byminute=0',
    end_date        => NULL,
    comments        => 'Repeats hourly,on the hour,for ever.');
END;
grant execute on add_partition_hourly_schedule to hr;
grant execute on add_partition_hourly_schedule to hr
Error on the line 1:
ORA-27487: SCHEDULE invalid object previlege.

pls, check doc: http://download.oracle.com/docs/cd/B19306_01/appdev.102/b14258/d_sched.htm#i1010076
>
Usage Notes
This procedure requires the CREATE JOB privilege to create a schedule in one's own schema or the CREATE ANY JOB privilege to create a schedule in someone else's schema by specifying schema.schedule_name. Once a schedule has been created, it can be used by other users. The schedule is created with access to PUBLIC. Therefore, there is no need to explicitly grant access to the schedule.

MOVED: Will the MSI 6800GT 256mb AGP 8x work on...

This topic has been moved to AMD SocketA based board.
Will the MSI 6800GT 256mb AGP 8x work on...

ask if you can return the card if it doesnt work cause for me the card wasnt working
https://forum-en.msi.com/index.php?threadid=37778&sid=
from the discussion with other members having the same bug as me it seems that they can be some incompatibiliy with 4x agp motherboard
Poubelle

MSI 6800GT or MSI 7800GT

I am getting the MSI 6800GT PCIe Card from $300 from Zip Zoom Fly:
http://www.zipzoomfly.com/jsp/ProductDetail.jsp?ProductCode=321924
and I am getting the MSI 7800GT PCIe Card for $348 (after the Mail In Rebate).....
is the 7800GT worth the extra $50 ??

ahmadka,
For $50.00 go with the 7800GT.
Take Care,
Richard

Counterfeit MSI 6800GT?

Hello,
I ordered an MSI 6800GT with 2 DVI ports from Tekheads.co.uk a couple weeks ago. I received the card in a retail box, and it looked just like the design on the box, and on the MSI webpage. After using it for a couple days it was apparent that there was a fault in the card. I would get crazy texture/graphical corruption after a few minutes of normal use in many games.
I returned the card to Tekheads, and they finally got around to testing it and I was issued a replacement which arrived today. What they did was take the exact same box that I sent back to them, and they put in a new card which has an Nvidia reference design cooler on it.
I immediately thought they had just thrown in any old 6800GT in there and hoped I wouldn't notice or wouldn't care. I've contacted Tekheads and they say the card was received as a replacement from MSI directly.
Is there any truth to this or is Tekheads full of ? Truth or not, I'm not happy with getting this reference design cooler over MSI's all copper solution.
Thanks,
Adrian

Her is a link to the tread.

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]

WOW!!MSI 6800GT arrived today

After a hard days work what do i find waiting on my door step??A huge box containing a brandnew MSI NX6800GT 256MB graphicscard,with shakey hands i unwrapped this much awaited piece of hardware.
I,ve been waiting 5 weeks for this day as i live in New Zealand and being a small country of only 4 million people we were at the bottom of the shipment list i guess,but it been well worth the wait,I installed the card(has a red PCB and and the copper cooling and fan speed switch)booted up the pc and proceded to benchmark using 3dmark03 and scored a healthy 12996 which really surprised me as i thought my pc would limit some performance(athlonxp2800+,epox8rda+nforce2mobo,1gig cheap pc2700 ram,cheap thermaltake purepower 420w powersuppy,21inch sony trinitron flatdisplay,audigy sound hooked up to 5.1 sound sytem)gonna upgrade cpu,mobo,ram &power when ican afford it.
I,ve upgraded from the gecube X800pro which was also very good,but this MSI/Invidia product is truly awesome ,my games are looking and playing so much better(BFvietnam,bf1942,farcry,doom3,homeworld2,CS:source beta)
Welldone you guys and girls that built such a fine graphicscard,and to those people that have yet to upgrade there card try the nx6800gt you won,t be disappointed .

Quote
Originally posted by teeffaa
Zimz plz tell me what psu you have with this card and how many amps on the +12v you have
what is your specs. any way
hi,i,m using a cheaper thermaltake purepower 420w +12@only18a ,i know people sa7y you need a higher rated supply than these but it works fine for me,games run great i can overclock the card to ultra levels and its stable so whats with that??
my specs are as follows=
athlon Xp2800+ barton core 333fbs cooled with coolermaster jet7
Epox EP-8rda+ nforce2 motherboard
1 gig corsair DDR2700 ram dualchannel enabled
2xwesterndigital 7200rpm 8mbcach 80gig harddrives
1xpioneer DVD-R+R dvr-107D writer
1xLiteon dvd-rom
Audigy sound hooked up to 5.1 sound system
4xcase fans
sony 21inch trinitron flatdisplay dom 2002
MSI NX6800GT 256mb vidcard
card temp=42c idle / 54 underload(cards fanspeed switch set to lowest setting)
as you can see i,m running alot on that cheap powersupply ,as of yet everything has been smooth sailing(so far)
but i,m goona do some upgrading when i,ve some spare cash.

To users of MSI 6800GT running doom3

Similar Messages

Maybe you are looking for