
-
Similar Content
-
By Shazzybear
Hi, I wanted to know my Intel UHD number but couldnt find it in Device Manager so I looked up in the Intel website followed their instructions but found nothing. I looked up my CPU in the intel website no numerical digit was there in the graphics section.
CPU is Intel core I3 1005G1
Thanks in advance
-
By Henrik9979
Okay here is what's going. I have a alienware m18x r1 running an amd 8970m, I wanted to upgrade it to crossfire but I could see a 8970m was more expensive than a r9 m290x
So I decided to buy a r9 m290x and see if I could make it work in my alienware and also run crossfire.
Even though many shops refused to sell me one because the didn't think it would work in an alienware m18x r1 only in the r2.
Here is the whole process.
19/08/17 23:15
No post bios showing when booting, so impossible to enter bios menu, but can boot into windows 10 with no problems.
19/08/17 23:20
Because I haven't deleted the old AMD 8970m the r9 m290x shows as a 8970m with no problems.
19/08/17 23:34
First performance test was a success. The r9 m290x changed p-state normally. The gpu fan start spinning normally. But because of no thermal paste, the test lasted 20 seconds because the temperature raised fast.
20/08/17 00:00
Created a backup of the vbios version
015.032.000.004.044450
20/08/17 00:10
Flashed a new clevo vbios version 015.032.000.003.044465
Caused the card to be corrupted and resulted the 8 beep code.
20/08/17 00:35
Finally managed to flash the back and return the graphics card to its original state.
20/08/17 00:50
Flashed a new dell vbios version 015.046.000.014.045579
No change in behavior
20/08/17 01:07
After trying multiple vbios with no luck I finally found one.
Dell vbios Version 015.041.000.000.044966
Brings back the post bios screen and I can now enter the bios menu through the r9 m290x.
Note: This vbios reduce the cards performance from 900 mhz to 850 mhz
20/08/17 01:21
After more testing I found one that is working with no limits.
Clevo vbios version
015.036.000.005.044618
Brings back the post bios screen and I can now enter the bios menu through the r9 m290x.
This will be the vbios I will keep at the moment.
20/08/17 01:56
I completely uninstalled the previous driver and installed the newest driver. The graphics card is recognized as a 8970m but works normal.
21/08/17 20:15
I have inserted my old 8970m in the secondary slot and will start testing crossfire.
21/08/17 21:45
I have found out that the fan for the secondary fan did not spin. The is a cable that have felt out. I will fix it now.
21/08/17 22:00
In my try to test crossfire compatibility, I installed the newest AMD driver 17.7.2 but as soon it installed the driver for the secondary card it caused black screen. Only booting the computer in safe mode brings the screen back.
21/08/17 23:02
After many frustrating hours I finally managed to get crossfire working with the r9 m290x as the primary card and my old 8970m as the secondary.
I have flashed the same vbios on both cards so the r9 m290x shows up I device manager as a 8970m.
I first installed AMD driver version 16.2.1
Then installed AMD driver version 16.6.1 in order to play battlefield
21/08/17 23:20
First test run in battlefield 1
21/08/17 23:40
Battlefield 1 is flickering bad, this can maybe be solved with a new patch or driver.
Other games I have tried is working perfect with crossfire on.
Now what I would like to try is somehow force the r9 m290x driver to be installed and see if it will make it possible to run the latest AMD driver without getting a blackscreen.
I have tried to edit the .inf file like you would do with nvidia but no luck.
I have also tried to figure out how to edit the device id in the vbios, but I find it too complex.
-
By Klem
Klem's_vbios_ASUS_GTX870M_80.04.F4.00.01_UNLOCKED
1. Unlocked Nvidia core limit +135 MHz.
2. Unlocked Power Limit.
3. Unlocked Power adjustment by software (for example with Nvidia Inspector).
4. Increased Power Limit and Power Target.
5. Enabled some additional tweaks.
If you liked my mod, you can buy me some beer: https://www.buymeacoffee.com/ekushukovZ
-
By narbardarse
ok, so, i have a serious problem atm.
im trying to mod my bios so that i can go past the normal overclocking limit. however, everytime i try to do it, it always says "file size does not match existing bios size!", and it's really annoying, since i had to find everything myself, as no one else online tried this on my specific model, besides me. (which surprises me, really)
this is the guide im following:
So this is my detailed description how I managed to mod and overclock my GTX 960M in my Lenovo Y50-70. Please note: it is very dangerous to play with the BIOS, so you need to be very careful! I take NO RESPONSIBILITY for any damage or misuse of the information below! Use it AT YOUR OWN RISK!
-------
Necessary tools:
A. Fptw64 from Intel (9.5 or above)
http://forum.hwbot.org/showthread.php?t=75024
B. PhoenixTool (2.50 or above)
C. Maxwell II BIOS Tweaker (1.36)
https://www.techpowerup.com/downloads/2562/maxwell-ii-bios-tweaker-v1-36/
-------------------------
How to flash Modded BIOS:
0. Flash the latest (3.03 now) official BIOS
1. From Windows, start 'cmd' as Administrator and read your your BIOS via Fptw64:
Fptw64 -d BIOS.ROM -bios
2. Reboot, enter your BIOS and check "Enable downgrading BIOS" feature (we need to downgrade first in order to flash the modded BIOS)
3. From Windows, downgrade to 1.13 (this is necessary because the newer BIOSes have protection against mod-ding)
4. After reboot & reflash, start Windows, then enter standby, wait a bit, then wake up the machine
5. Create your modded BIOS, see separate list below
6. Start 'cmd' as Administrator and write your _modded_ BIOS via Fptw64:
Fptw64 -f BIOS_MODDED.ROM -bios
-------------------------
How to create modded BIOS (point 5 above):
5.1 Start PhoenixTool.exe from Phoenix Tool 2.50 and open your previously saved original BIOS.ROM from point #1 above
.2 The tool analyses it and shows some messages, click OK
.3 Now you can find your vBIOS in the "DUMP" subfolder in the folder containing your BIOS.ROM, with the file name:
BE13645B-2C2C-44D2-A64F-0EA052C34597_1796.ROM
.4 Create your modded vBIOS, see separate list below -> let's call it 960M_OC.MOD
.5 Click on "Structure"
.6 Open "EFI BIOS" tag
.7 Open second "File Volume {7A9354D9-...}" tag
.8 DXE Core -> Compressed Section -> Raw section -> File Volume {7A9354D9-...}
.9 In the very long list, find the following tag (usually displayed at around 80% of the list):
Freeform {BE13645B-2C2C-44D2-A64F-0EA052C34597}
This is the item containing the latest vBIOS
.10 Open the tag, then "GUID defined section", then click on Raw section. "Internal number" (in the top right corner) should be 1796 for BIOS 3.03.
.11 Click on "Replace" and select your modded vBIOS (called 960M_OC.MOD above)
.12 Click exit "Exit" and say Yes to "Save changes?"
.13 Close the Phoenix Tool; now you should have your BIOS.ROM updated (the original will be saved as BIOS.ROM.OLD for safety)
-------------------------
How to create modded vBIOS (point 5.4 above):
Use Maxwell II BIOS Tweaker to change BE13645B-2C2C-44D2-A64F-0EA052C34597_1796.ROM;
5.4.1 Open the ROM
.2 Change "Boost Clock" on "Common" tab to the new boost-ed maximum value
.3 On "Boost table" tab, use the slider in the right bottom corner to increase your max boost-ed value to the same number
.4 On "Boost states" tab, at P00 profile, change the MAX values in the GPC, L2C and XBAR fields to the same max boost-ed value
.5 Save your modified BIOS and rename it to 960M_OC.MOD
(My boost-ed max value was 1359 MHz. I could then use MSI Afterburner's software tuning -> my 960M could reach 1454 MHz without voltage increase.)
i know that it's for a different laptop, but its basically the same
ill provide more info when im home
-
By Zoarilamb
I fiddled around with modding my laptops BIOS to unlock XMP profiles and hopefully seeing if optimus could be disabled. After flashing my modded bios and trying it out, I noticed that my keyboards backlight no longer turns on. I was unaware it requires an official BIOS to function. They backlights wont turn on unless ASUS ATK package is installed but now it seems it also needs an official BIOS?
The modded ROM and tool I used if anyone has any experience with this and doesn't mind telling me what to enable/disable, or anything else i can do to re-enable them
-