MSI Radeon R9 270X GAMING 4GB and GOP UEFI vBios Flash?

I'm thinking about getting a MSI Radeon R9 270X GAMING 4GB for my HTPC since it's kind of shorter and was wondering if MSI provides a GOP UEFI flash for it or if it's capable of doing so?
Thank you.

the card has 2 VBIOS's and some have one that is Legacy and another that is GOP already (others have a Legacy and a LN2) so its a 50/50 if it has it out the box!
if it doesn't there will probably be one available as the Rx - 2xx have been around a while now!

Similar Messages

Re: Radeon R9 270x Gaming 4GB LE Black Screen

Quote from: Svet on Today at 14:53:25if nothing helps think you still need to test the card in another computer to figure what's wrong
other option is to RMA the card, but if the problem is not the card, this will...

These eight boards were announced...
A88XI AC V2
A88X-G41 PC Mate V2
A88XM-P33 V2
A88XM-E54 V2
A88XM-E35 V2
A78M-E45 V2
A78M-E35 V2
A68HM-E33 V2
For example I have the original A78M-E35 board and there hasn't been a BIOS update yet, and the godavari ba...

MSI Radeon R9 270X Hawk - Screen corruption

Hello,
I dearly ask for your help, I have an issue with my MSI HAWK Radeon R9 270X, after using my computer for a while the screen on the primary/secondary monitor will become unreadable(see the first link), If I switch the monitor off via Catalyst Control Center the screen corruption will appear onto the other monitor. Maybe the newer BIOS would help, I have the same issue with another MSI HAWK R9 270X. I didn't have any problems with my former video cards (Geforce GTS 250, GTS450, Radeon 6850 and Radeon 7850).
I tried both 13.12 drivers as well as the newest betas 14.1 ,the only difference was the first target affected, on 13.12 the corruption would appear on primary monitor whereas on 14.1 it would affect the secondary one.
Also occasionally I experience the screen flicker issue as well, maybe newer BIOS could solve both of them.
My system specs:
Asus Sabertooth 990FX R2.0 with 2104 Bios version
4x Corsair XMS 2000MHz 4GB
Thermaltake Evo Blue 2.0 750W Power Supply
MSI Radeon R9 270X HAWK - Serial Number: 602-V303-02SB1310007935
Monitor#1 - IIyama ProLite X2377HDS
Monitor#2 BenQ FP73E S
Both of them connected via DVI
Here is a screenshot of the problem:
ht.tp://i.imgur.com/xdEPS7h.jpg
My current BIOS:
ht.tp://we.tl/cP65V8NsRx
I would appreciate any help from you guys

Can't download the vbios from that site you linked to.
None the less >>this<< is the latest vbios
TV303MH.131 is normal vbios, TV303MH.141 is LN2
Create a bootable usb stick (https://forum-en.msi.com/index.php?topic=165175.0).
Then unpack the previously provided archive (131_141.rar) and put the included file (TV303MH.131 or TV303MH.141) on that stick.
Rename TV303MH.131 / TV303MH.141 to 131.rom / 141.rom. Put the atiflash.exe also included in the archive on the USB stick too. Now boot from the stick.
Type atiflash -p -f -noaper 0 131.rom (or 141.rom) [ENTER] and let it flash the vbios.

MSI Radeon R9 270x 4 gb Help

Hey guys!
The other day I got MSI Radeon R9 270x 4 gb to upgrade my fairly old PC. I've been gaming on it for about 3 years.. When I connect the card with the two 6 pin cables the fans starts spinning
but my computer wont boot. Any suggestions?
I've been thinking about updating my BIOS but I can't seem to find drivers for my motherboard.. And I have no experience updating BIOS either :(
Any help would be much appreciated!
My specs:
Windows 7 ultimate 64 bit
Motherboard: MSI X79A-SD40
i7-3930K 3.20GHz
16 gig memory
PSU 1200W
Old GPU(s)
HIS radeon hd 6970 x2 (crossfire)

To figure out what bios version you have, >>use the MSI HQ Forum USB flasher<<. After starting the MSI HQ Forum USB flasher it will automatically detect your board's current bios and save the details in a file on your desktop called MSIHQ_INFO.txt. There you can read up the exact bios version. Quote this details to check if there is a new version.

VGA BIOS for MSI RADEON R9 270 GAMING

Can someone please post me a BIOS for VGA BIOS for MSI RADEON R9 270 GAMING?
I flashed mine with the wrong BIOS and realised to late that the BIOS backup did not actually work. This is the 270 and not the 270x. Any help would be appreciated.

There seems to be none so far: >>How to contact MSI.<<
I removed the other line. Better don't mention the payment method again. Also such reward is not needed. Either there's such file from MSI or not.

[REQUESTS] GOP/UEFI Vbios - MSI R9 290X Gaming 4G

Model: MSI R9 290X GAMING 4G
S/N: 602-V308-01SB1402008189
BIOS Version: 015.042.000.000.000000
Thanks in advance.

Quote
BIOS Version: 015.042.000.000.000000
That is useless. Add link to your real vbios saved to file:
Quote from: GOP / UEFI Vbios requests - Read Here First on 29-March-13, 22:47:26
If you are looking for a UEFI / GOP Vbios for your video card here are a few things we need and there are a few things you need to know.
1.) Vbios versions vary with-in models. This is due to different variations and improvements made in time. In order for us to be able to get you the right VBIOS. We need your serial number. The serial number can be found on a sticker on the bottom of your card or on the box in which it came.
2.) Don't use a vbios provided to another users. Just because you have the same model, doesn't mean you need the same vbios. While flashing the wrong vbios is recoverable, it is still more work. It is fine to post in that thread with your serial number asking if you can use that VBIOS.
3.) If we need to check if thier is a more recent version. We can check your Vbios in one of two ways.
A.) Upload a copy of your current vbios somewhere and give us a link. You can save a copy of your vbios using >>GPU-Z<<.
B.) You can also just use NVFLASH >>Download NVFLASH for windows<<
Syntax:
nvflash /v >rep.txt [ENTER]
This will copy all of the information we need into a txt file you will fine in the folder in which you placed nvflash.
4.) Be aware that gpu-z screenshots or what gpu-z reads out as bios version are NOT of any use for identifying the required vbios version. While it doesn't hurt to add those when S/N and an actual copy of the vbios are also supplied simply just adding screenshots or version readouts will not get you any further and us having to ask for the required informations.

Msi z87 gd 65 gaming freezing and bsod

msi z87 gd 65 gaming freezing and bsod happens in a game or on desktop
build 26/09/2013 08:16 PM
i7 - 4770k
msi z87 gd65 gaming
corsair 32 gb ddr3 cmy32gx3m4a2400c10r
asus r9280x-dc2-3gd5 r9 280x
h110i corsair
corsair hx860i
crucial m4
cooler master cormos 2 case
system started to freeze and bsod
items I have done
osri
new psu
memtest all sticks and one at a time all passed
hd tune smart test passed
increased voltage on memory in case it was that as the x m p does it at 1.5v increase 4 steps from 1.5v to 1.9v all 4 gave the same issue
1.65v bsod as well
who crashed says amd ccc is causing the issue reinstalled with driver from asus and latest also the beta same issue is happening
this is why I think its the main board but was going to run the system from intel gpu by removing the amd gpu from system maybe even test an alt slot x8 to see what happens
currently testing r9 280z card with default gpu clock 850mhz instead of 1000mhz incase that's whats causing it
I know this is another post the other post does not have edit on the post any more so making you aware of this
any one got any ideas as to what to try next
On Sat 06/09/2014 04:26:29 GMT your computer crashed
crash dump file: C:\Windows\Minidump\090614-8346-01.dmp
This was probably caused by the following module: dxgmms1.sys (dxgmms1+0x2DBA1)
Bugcheck code: 0x3B (0xC0000005, 0xFFFFF8800FFB3BA1, 0xFFFFF8800CFEE540, 0x0)
Error: SYSTEM_SERVICE_EXCEPTION
file path: C:\Windows\system32\drivers\dxgmms1.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: DirectX Graphics MMS
Bug check description: This indicates that an exception happened while executing a routine that transitions from non-privileged code to privileged code.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
The crash took place in a standard Microsoft module. Your system configuration may be incorrect. Possibly this problem is caused by another driver on your system that cannot be identified at this time.
On Fri 05/09/2014 21:27:51 GMT your computer crashed
crash dump file: C:\Windows\Minidump\090614-8564-01.dmp
This was probably caused by the following module: win32k.sys (0xFFFFF9600012E354)
Bugcheck code: 0x50 (0xFFFFFD00C0873680, 0x0, 0xFFFFF9600012E354, 0x7)
Error: PAGE_FAULT_IN_NONPAGED_AREA
file path: C:\Windows\system32\win32k.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: Multi-User Win32 Driver
Bug check description: This indicates that invalid system memory has been referenced.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
The crash took place in a standard Microsoft module. Your system configuration may be incorrect. Possibly this problem is caused by another driver on your system that cannot be identified at this time.
On Fri 05/09/2014 17:54:09 GMT your computer crashed
crash dump file: C:\Windows\Minidump\090514-7909-01.dmp
This was probably caused by the following module: dxgmms1.sys (dxgmms1+0x3267E)
Bugcheck code: 0x3B (0xC0000005, 0xFFFFF88004A3267E, 0xFFFFF880060F6A30, 0x0)
Error: SYSTEM_SERVICE_EXCEPTION
file path: C:\Windows\system32\drivers\dxgmms1.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: DirectX Graphics MMS
Bug check description: This indicates that an exception happened while executing a routine that transitions from non-privileged code to privileged code.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
The crash took place in a standard Microsoft module. Your system configuration may be incorrect. Possibly this problem is caused by another driver on your system that cannot be identified at this time.
On Thu 04/09/2014 23:44:42 GMT your computer crashed
crash dump file: C:\Windows\Minidump\090514-9796-01.dmp
This was probably caused by the following module: watchdog.sys (watchdog+0x122F)
Bugcheck code: 0x10E (0x1F, 0xFFFFF8A00B7F9E50, 0x0, 0x15B641)
Error: VIDEO_MEMORY_MANAGEMENT_INTERNAL
file path: C:\Windows\system32\drivers\watchdog.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: Watchdog Driver
Bug check description: This indicates that the video memory manager has encountered a condition that it is unable to recover from.
The crash took place in a standard Microsoft module. Your system configuration may be incorrect. Possibly this problem is caused by another driver on your system that cannot be identified at this time.
On Thu 04/09/2014 21:54:59 GMT your computer crashed
crash dump file: C:\Windows\Minidump\090414-7878-01.dmp
This was probably caused by the following module: dxgmms1.sys (dxgmms1+0x2112B)
Bugcheck code: 0x1000007E (0xFFFFFFFFC0000005, 0xFFFFF8800494A12B, 0xFFFFF88011FF4558, 0xFFFFF88011FF3DB0)
Error: SYSTEM_THREAD_EXCEPTION_NOT_HANDLED_M
file path: C:\Windows\system32\drivers\dxgmms1.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: DirectX Graphics MMS
Bug check description: This indicates that a system thread generated an exception which the error handler did not catch.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
The crash took place in a standard Microsoft module. Your system configuration may be incorrect. Possibly this problem is caused by another driver on your system that cannot be identified at this time.
On Thu 04/09/2014 21:30:05 GMT your computer crashed
crash dump file: C:\Windows\Minidump\090414-8470-01.dmp
This was probably caused by the following module: dxgmms1.sys (dxgmms1+0x308F0)
Bugcheck code: 0x3B (0xC0000005, 0xFFFFF8800FF8F8F0, 0xFFFFF8800907E420, 0x0)
Error: SYSTEM_SERVICE_EXCEPTION
file path: C:\Windows\system32\drivers\dxgmms1.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: DirectX Graphics MMS
Bug check description: This indicates that an exception happened while executing a routine that transitions from non-privileged code to privileged code.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
The crash took place in a standard Microsoft module. Your system configuration may be incorrect. Possibly this problem is caused by another driver on your system that cannot be identified at this time.
On Tue 02/09/2014 18:50:50 GMT your computer crashed
crash dump file: C:\Windows\Minidump\090214-8143-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x75BC0)
Bugcheck code: 0x50 (0xFFFFF8B00E9D800C, 0x0, 0xFFFFF8000397A981, 0x5)
Error: PAGE_FAULT_IN_NONPAGED_AREA
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This indicates that invalid system memory has been referenced.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.
On Sun 31/08/2014 15:31:29 GMT your computer crashed
crash dump file: C:\Windows\Minidump\083114-7753-01.dmp
This was probably caused by the following module: dxgmms1.sys (dxgmms1+0x2112B)
Bugcheck code: 0x1000007E (0xFFFFFFFFC0000005, 0xFFFFF8800413B12B, 0xFFFFF88011DEF558, 0xFFFFF88011DEEDB0)
Error: SYSTEM_THREAD_EXCEPTION_NOT_HANDLED_M
file path: C:\Windows\system32\drivers\dxgmms1.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: DirectX Graphics MMS
Bug check description: This indicates that a system thread generated an exception which the error handler did not catch.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
The crash took place in a standard Microsoft module. Your system configuration may be incorrect. Possibly this problem is caused by another driver on your system that cannot be identified at this time.
On Sun 31/08/2014 08:49:23 GMT your computer crashed
crash dump file: C:\Windows\Minidump\083114-8424-01.dmp
This was probably caused by the following module: dxgmms1.sys (dxgmms1+0x308F7)
Bugcheck code: 0x3B (0xC0000005, 0xFFFFF880048308F7, 0xFFFFF88008DC2B00, 0x0)
Error: SYSTEM_SERVICE_EXCEPTION
file path: C:\Windows\system32\drivers\dxgmms1.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: DirectX Graphics MMS
Bug check description: This indicates that an exception happened while executing a routine that transitions from non-privileged code to privileged code.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
The crash took place in a standard Microsoft module. Your system configuration may be incorrect. Possibly this problem is caused by another driver on your system that cannot be identified at this time.
On Sat 30/08/2014 22:58:37 GMT your computer crashed
crash dump file: C:\Windows\Minidump\083114-9687-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x75BC0)
Bugcheck code: 0xA (0xFFFFDA801908C040, 0x2, 0x0, 0xFFFFF80003659EC9)
Error: IRQL_NOT_LESS_OR_EQUAL
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This indicates that Microsoft Windows or a kernel-mode driver accessed paged memory at DISPATCH_LEVEL or above.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.
Conclusion
26 crash dumps have been found and analyzed. Only 10 are included in this report. 2 third party drivers have been identified to be causing system crashes on your computer. It is strongly suggested that you check for updates for these drivers on their company websites. Click on the links below to search with Google for updates for these drivers:
atikmdag.sys (ATI Radeon Kernel Mode Driver, Advanced Micro Devices, Inc.)
atikmpag.sys (AMD multi-vendor Miniport Driver, Advanced Micro Devices, Inc.)
If no updates for these drivers are available, try searching with Google on the names of these drivers in combination the errors that have been reported for these drivers and include the brand and model name of your computer as well in the query. This often yields interesting results from discussions from users who have been experiencing similar problems.
Read the topic general suggestions for troubleshooting system crashes for more information.
Note that it's not always possible to state with certainty whether a reported driver is responsible for crashing your system or that the root cause is in another module. Nonetheless it's suggested you look for updates for the products that these drivers belong to and regularly visit Windows update or enable automatic updates for Windows. In case a piece of malfunctioning hardware is causing trouble, a search with Google on the bug check errors together with the model name and brand of your computer may help you investigate this further.

No need to edit, just add a reply as flobelix asked for exact models of RAM and motherboard.
As it's double posting, this one gets locked. Please continue this one:
https://forum-en.msi.com/index.php?topic=183138.msg1314803#msg1314803
>>Please read and comply with the Forum Rules.<<
Topic Locked

GOP / UEFI Vbios request for R9 270X GAMING 2G

GOP / UEFI Vbios request for R9 270X GAMING 2G
My vbios is here-- "www. techpowerup .com/vgabios/146850/msi-r9270x-2048-131007.html"
version:015.040.000.000.002887
Thanks!

Quote from: zx1239856 on 19-October-13, 11:19:36
GOP / UEFI Vbios request for R9 270X GAMING 2G
My vbios is here-- "www. techpowerup .com/vgabios/146850/msi-r9270x-2048-131007.html"
version:015.040.000.000.002887
Thanks!
h**p://www.techpowerup.com/vgabios/146850/msi-r9270x-2048-131007.html is the bios from techpowerup
my bios--------- h**p://www.rayfile.com/files/b4588742-3896-11e3-b688-0015c55db73d

GOP / UEFI Vbios request - MSI GTX 760 Twin Frozr Gaming 2GB OC

Hi,
I would need the GOP/UEFI VBios for the card in the subject...
S/N: 602-V284-55SC1310008526
Current BIOS: 80.04.C4.00.30 (P2004-0010)
NVFlash Report:
NVIDIA Firmware Update Utility (Version 5.118)
Adapter: GK1xx (10DE,1187,1462,2847) H:--:NRM B:01,PCI,D:00,F:00
The display may go *BLANK* on and off for up to 10 seconds during access to the EEPROM depending on your display adapter and output device.
Identifying EEPROM...
EEPROM ID (EF,3012) : WBond W25X20A 2.7-3.6V 2048Kx1S, page
Reading adapter firmware image...
Image Size : 62976 bytes
Version : 80.04.C4.00.30
~CRC32 : 6E793ADF
OEM String : NVIDIA
Vendor Name : NVIDIA Corporation
Product Name : GK104 Board - 20040010
Product Revision : Chip Rev
Device Name(s) : GK1xx
Board ID : E115
PCI ID : 10DE-1187
Subsystem ID : 1462-2847
Hierarchy ID : Normal Board
Chip SKU : 225-0
Project : 2004-0010
CDP : N/A
Build Date : 06/04/13
Modification Date : 07/30/13
Sign-On Message : GK104 P2004 SKU 0010 VGA BIOS (HWDIAG)
MSINV284MS.350
Thanks a lot in advance!!

Use >>this<<
Decompress the provided .rar archive with Winrar: http://www.rarlab.com/download.htm
Then flash the included file with Nvflash for dos: http://www.guru3d.com/files_details/nvflash_download.html
To do so rename the included file to .rom and create a dos bootstick (https://forum-en.msi.com/index.php?topic=165175.0)
Put nvflash and the vbios file on it and boot from the stick. Then type nvflash -4 -5 -6 gop.rom (if renamed vbios that way) and hit enter. Confirm the questions and let the tool flash.

GOP / UEFI Vbios request: MSI GeForce GTX 760 Gaming Edition (N760 TF 2GD5/OC)

Hi,
Could you please share GOP / UEFI Vbios for my gpu and provide some basic steps how to flash it?
S/N: 602-V284-46SB1307038723
Current vbios: h_ttps://docs.google.com/file/d/0B-oJKwAsft9FX1kzZTVnNlJjNkE/edit?usp=sharing
Thanks.

Quote from: xmad on 05-October-13, 01:33:11
Are you able to use win 8 mode with onboard or unable to use the card at all?
Yes, and it boots instantly.
Quote from: xmad on 05-October-13, 01:33:11
Here is the latest bios for the mainboard as well:
https://forum-en.msi.com/index.php?topic=170132.msg1260345#msg1260345
Successfully flashed. But I'm getting to the same efi with win 8 enabled. Also Reboot function is not working now..

GOP / UEFI Vbios request - MSI GTX 770 Twin Frozr Gaming 2GB OC

Hi,
I would like to request a GOP/UEFI vBios for my graphics card.
N770 TF 2GD5/OC (GeForce GTX 770 GAMING)
S/N: 602 - V282 - 220B1310066660
Current BIOS: 80.04.C3.00.21 (P2005-0000)
NVFlash Report:
*** NVFLASH LOG FILE ***
Version 5.142
Command: version
FindDevices:
Device:00:00:00=8086:0C00:1462:7821
Device:00:01:00=8086:0C01:1462:7821
Device:00:14:00=8086:8C31:1462:7821
Device:00:16:00=8086:8C3A:1462:7821
Device:00:1A:00=8086:8C2D:1462:7821
Device:00:1B:00=8086:8C20:1462:D821
Device:00:1C:00=8086:8C10:1462:7821
Device:00:1C:03=8086:8C16:1462:7821
Device:00:1D:00=8086:8C26:1462:7821
Device:00:1F:00=8086:8C44:1462:7821
Device:00:1F:02=8086:8C02:1462:7821
Device:01:00:00=10DE:1184:1462:2825 GPU
Device:01:00:01=10DE:0E0A:1462:2825
Device:03:00:00=1969:E091:1462:7821
Action: Display version.
Action: Identify EEPROM.
Atmel Serial EEPROM Identify.
Reported Manufacturer Code (JEDEC): EF
Reported Device Code (JEDEC): 3012
EEPROM ID (EF,3012) : WBond W25X20A 2.7-3.6V 2048Kx1S, page
Action: Read EEPROM image.
Reading EEPROM bytes.
Start: 0x00000000
Count: 262144
Read complete.
IFR Data Size : 1112 bytes
IFR CRC32 : 189B4216
IFR Image Size : 1536 bytes
IFR Image CRC32 : 4552879D
IFR Subsystem ID : 1462-2825
Image Size : 99328 bytes
Version : 80.04.C3.00.21
~CRC32 : D6321A32
OEM String : NVIDIA
Vendor Name : NVIDIA Corporation
Product Name : GK104 Board - 20050000
Product Revision : Chip Rev
Device Name(s) : GeForce GTX 770
Board ID : E12D (GK104 P2005 SKU 000)
PCI ID : 10DE-1184
Subsystem ID : 1462-2825
Hierarchy ID : Normal Board
Chip SKU : 425-0
Project : 2005-0000
CDP : N/A
Coproc Build : NO
Build Date : 06/03/13
Modification Date : 06/18/13
UEFI Support : No
UEFI Version : N/A
UEFI Signer(s) : Unsigned
Sign-On Message : GK104 P2005 SKU 0000 VGA BIOS
MSINV282MS.352
Thank you in advance!

here it is

Request: Latest GOP/UEFI VBIOS for R9 290X Gaming 4G

Hello,
I have an MSI Radeon R9 290X Gaming 4G card and would like to request the latest GOP / UEFI / VBIOS please.
S/N: 602-V308-01SB1402009506
I uploaded my current one here http://files.enjin.com/847491/hawaii.zip.
Thank you.

update is available [TV308MH.100 ==> TV308MH.101]
here is latest version attached below

[Request] GOP/UEFI Vbios for N770 TF 2GD5/OC GTX 770 Gaming

[Request] GOP/UEFI Vbios for N770 TF 2GD5/OC GTX 770 Gaming
Hello,
May I have the latest bios for my GTX770 so i can use it with windows 8.1 UEFI and get fastboot !
Here is the model : N770 TF 2GD5/OC GTX 770 Gaming
Here is the serial number :
602-V282-41SC1403007760
Best regards
By the way I can't register this card (Error: 00140002)
Looks like a return because no blister !

Use the attached.
Decompress the provided .rar archive with Winrar: http://www.rarlab.com/download.htm
Then flash the included file with Nvflash for dos: http://www.guru3d.com/files_details/nvflash_download.html
To do so rename the included file to .rom and create a dos bootstick (https://forum-en.msi.com/index.php?topic=165175.0)
Put nvflash and the vbios file on it and boot from the stick. Then type nvflash -4 -5 -6 gop.rom (if renamed vbios that way) and hit enter. Confirm the questions and let the tool flash
Quote from: mardigan on 05-June-14, 19:13:00
By the way I can't register this card (Error: 00140002)
Looks like a return because no blister !
If it is a used card that might be the cause but best would be to contact MSI about it: >>How to contact MSI.<<

Request: GOP/UEFI vBIOS - MSI N670GTX-PE2GD5/OC

Good day!
I'd like to request GOP/UEFI vBIOS as stated. Details are below.
S/N: 602-V284-030B1208192127
Current vBIOS: htt**://mega.co.nz/#!vY5FSLRA!itk06jjrJOxtKb-7rrSqMblJ3dUfr-8uhtSoN0kGru0
Q1: I'm running an SLI setup (2 different brands). Do i need to flash both or is it enough if i flash the one in first slot for UEFI to work?
Q2: Even if i flash just this card (my primary concern is updating this card with latest bios, since there are some issues with it), i guess it doesn't prevent SLI from running properly ?
Thanks !

Can't really identify your current vbios. Did you read the S/N from the card or box?
Quote
Q1: I'm running an SLI setup (2 different brands). Do i need to flash both or is it enough if i flash the one in first slot for UEFI to work?
Both need to use a UEFI vbios else it doesn't work and of course you can't use the vbios of the MSI card on the other brand's card. So you'll ask the other brand for an update too.
Quote
Q2: Even if i flash just this card (my primary concern is updating this card with latest bios, since there are some issues with it), i guess it doesn't prevent SLI from running properly ?
SLI will work fine as before. You just can't enable UEFI mode using just one card with a UEFI/GOP vbios.

GOP / UEFI Vbios requests for MSI GTX 670 PE OC

I would like to requests a GOP / UEFI Vbios for my MSI GTX 670 PE OC graphics card.
My serial number is 602-V284-02SB1207061629
Current Vbios: http://sdrv.ms/1bL1Uwk
Thank you.

Ah, there is more than meets the eye to it.
I recently newly installed Windows 8.1, why didn't it auto install it to GPT? I'm not gonna do a reinstall right away to test if it's working.
btw: what about GPT and SSD trim? It thought that didn't get along well?
btw 2: Is this particular thing also related to the fact that I can't enable the "Windows 8 feature" in the bios and so also not "Secure Boot"? With it enabled the PC won't go to Windows and keeps hanging on some black/yellow letter UEFI screen...

MSI Radeon R9 270X GAMING 4GB and GOP UEFI vBios Flash?

Similar Messages

Maybe you are looking for