Toopy
-
Posts
53 -
Joined
-
Last visited
Content Type
Profiles
Forums
Downloads
Posts posted by Toopy
-
-
@svl7 Hi, just wondering if you got around to sending me that flashed bios chip? http://forum.techinferno.com/general-notebook-discussions/1847-nvidia-kepler-vbios-mods-overclocking-editions-modified-clocks-voltage-tweaks-193.html#post47652
-
Hello
Card Clevo
Yes Vbios OV
I posted it a couple of pages ago, you should be able to find it. I'll add it to the first post when I get around to do so.I'll have a look, by the way svl7 I wonder if the reason my 675mx varies and wont flash, as in the locked the bios is because GPU-z ID's it as a KAPOK not a dell?
-
Very good svl7 vbios 1.08
limit with the slide ):
[ATTACH=CONFIG]7218[/ATTACH]
hi Riri-Fifi
is your card a DELL or Clevo,
I noticed that GPU-z ID's it as dell.
also
where are you getting the OV/Vbios from, please share
-
yep tried the nvflash command
nvflash --protectoff
if you could send me a pre-programmed chip that would be absolutley fantastic
-
so the plot would thicken as it seems.
In my determined attempt to flash your modded bios, I desoldered the bios chip from my GTX675MX and attempted to flash it with an external SPI programmer.
I first read the chip, which read fine, then tried to flash your bios to it. This is where all my attempt failed.
While the flash completed upon rereading the chip the stock bios was still in place, I attempted to erase the chip first.
Once again when reread the chip had not been erased.
It seems that my bios chip is locked and I can only assume that it has something to do with the soft straps as the hardware Write lock pin pin is unlocked. Alas I could not find how to issue the commands to unlock the soft straps with my spi programming tool.
It seems that I'm the only one with a locked 675MX bios chip
so in the meantime I've resoldered the bios chip.
If anybody knows the corret command syntax in nvflash to set BP0 and BP1 lock bits(I think these are the soft straps) to 0 I would be most greatful.
Now I continue my hunt for a blank mx25l2005 rom IC.
- - - Updated - - -
-
Probably it's not flashing. Make sure your machine has the latest EC and BIOS on it. Did you use MS DOS or FreeDOS? It might not work with FreeDOS. Also if nothing helps you can try the windows version of nvflash.
Using MSDOS, swapped back from prema's mod to the latest Clevo BIOS (which had never been on the machine before as it had the Horize BIOS), still didn't flash. back to premas mod still wont flash. I have a feeling that the #WP pin on the flash chip is enabled in hardware. I'm away from home at the moment so I don't have a any tools to check. Hopefully that's what the problem is which shouldn't be to hard to overcome.
I also wonder if they are using a newer flash chip and nvflash only partially supports this one. Once I ope it up I'll check.
-
What did you try so far?
pretty much everything, I have tried the following in both dos and with nvflash windows.
Trying to flash your Clevo GTX675MX 4GB bios
nvflash -6 xxx.rom
nvflash -4 -5 -6 xxx.rom
nvflash --protectoff
then the above
nvflash -j -6 xxx.rom
all error out with a mismatch in 256 byte page programming mode?
when I try to flash the original bios saved from my card nvflash completes. I am not sure if it is flashing, is there any way to tell?
-
-
I don't if this will help but here is some extra info from my card. The last command shows the mismatch offset when comparing your modded 675mx 4gb Clevo Rom. If you could please have a look I'd be most thankfull.
C:\nvflash>nvflash --pciblocks
NVIDIA Firmware Update Utility (Version 5.118)
Adapter: GK1xx (10DE,11A7,1558,7102) 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 (C2,2012) : MX MX25L2005 2.7-3.6V 2048Kx1S, page
Reading adapter firmware image...
Location Size Type
000000:00FBFF 64512 x86
00FC00:0209FF 69120 EFI
C:\nvflash>nvflash -h work.rom
NVIDIA Firmware Update Utility (Version 5.118)
Adapter: GK1xx (10DE,11A7,1558,7102) 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 (C2,2012) : MX MX25L2005 2.7-3.6V 2048Kx1S, page
Reading adapter firmware image...
Current - Version:80.04.58.00.05 ID:10DE:11A7:10DE:1010
GK104 Board - 2051b004 (Normal Board)
Compare with - Version:80.04.58.00.05 ID:10DE:11A7:10DE:1010
GK104 Board - 2051b004 (Normal Board)
ERROR: Mismatch at offset 0x00000208 -
EDIT: Got it working! And wow this things amazing! My max temp was 65 on 3Dmark 11 and I got a score of P6264!! That's over 2000 points higher than stock! The stock speed was 667 core and 900 mem, I pushed it easily to 1050 core and 1100 mem. Pushing it like this gives it really close result to the 7970m, as its max score on 3dmark 11 is a little over P7000. It pushes way over stock 7970m though. Thanks svl7!!!
can I ask what you did to get it working? as I'm currently stuck with the 256byte mismatch error
-
I had this issue when I flashed a custom vbios to my 460m on an Asus.
Try -nvflash -4 -5 -6 newrom.rom
Thanks, still didn't flash though Mismatch in 256 byte page mode programming. I now have a hatred of that sentence
Pretty much about to give up now, pity as I upgraded to this laptop and didn't take the 680M option as I though I could flash and get stock 680M speeds out of the 675mx for les outlay. Are you sure that one of the pages in the modded VBios isn't larger than 256bytes? ( I could be entirely wrong here) I'm willing to experiment to try to sort out this problem if you are willing to helpYeah, try this, I can't think of much more. Clevo seems to have a very weird implementation of the SPI bus.I have a msi 16f3 (gt60 barebones) with a 675mx. When I try to install the mod with nvflash, I get "ERROR: No NVIDIA display adapters found". I can confirm my card is working, its the 4gb 675mx, scores 4300 stock on 3dmark 11. Any help would be appreciated, ive seen some get to 6000 on 3dmark 11 with this mod and id love if I could do the same. Thanks.Flashing in dos? or via nvflash in windows? if in windows open gpu-z and try again, it seems unless you activate the gpu it won't see it. That's what I've found anyway. If in dos I have no idea.
That's great. It seems just the modified vbios sent me from ~5800 to about 6200. Running 915/2150 I reach about 7200 in 3dmark11 which is a huge jump on stock volts. Temps went from about 74 to 79 however, though definitely still safe.All of 3dmark11 benches run without any artifacting, but between tests there is sometimes some flashing lines of static that I believe are just due to changing resolution from 1080p (native) to the 720p used during testing. Should I be worried?
Also, what does GPU-Z report others' 680m Asic quality? Mine reads 66%.
ASIC on my 675mx is 68.8%. Makes sense really as all of the mobile GK104's will be chips with faulty shader clusters(the ones on the outer edge of the silicon wafer) that didn't cut the mustard as desktop GTX680's
-
Do you have any ideas why the modded bios wont flash to my GTX675mx? nvflash errors out at the fourth dot, while as I said before the bios read from the card reflashes without problems. One thing that gets me is that when nvflash errors out with the mismatch error, while it states before hand that it clears the EEPROM, if I verify straight after the original bios is still there and I don't need to reflash with my backup to retain a working card. I've tried -protectoff and it still doesn't haven't any effect. Could it be strap settings?
-
I'm not sure what the issue is, you say you can flash your stock vbios... does it really flash it?
It's weird, if you can flash the stock there's no reason why it should be different for the mod.
as far as I can tell it does flash, nvflash completes and report being successful. Could you modify the original bios I posted to see if that will flash?
-
Do you have a Clevo notebook?
I have a Horize P170EM http://www.horize.com/index.php/computers/horize-p170em-notebook-pc.html, the mainboard ID's itself as a Clevo in CPU-z and I've flashed Prema's Clevo P170EM sBIOS to it.
-
@svl7 I was wondering if you could help me flash your modified bios to a CLEVO GTX675MX, Bios ver 80.04.58.00.05. I've tried to flash your modded bios and nvflash errors out with "Error: Mismatch in 256 byte page mode programming" Here is my original bios if it helps.
Has anybody got any idea's?
-
@svl7 I was wondering if you could help me flash your modified bios to a CLEVO GTX675MX, Bios ver 80.04.58.00.05. I've tried to flash your modded bios and nvflash errors out with "Error: Mismatch in 256 byte page mode programming" Here is my original bios if it helps.
-
@Toopy
I didn't even think about rolling back the drivers. Thanks. You can actually go up to 310.90 and still overclock, unlike with 314.07. However, I did notice that the 306.97 still has slightly better (3-5%) performance. I was able to get up to 1040/2900 for the best performance. Just benchmark data so far, using Heaven. But got a 23% increase by bumping up the mhz by almost 25%. I did notice that Heaven, GPU-z, and NvidiaInspector all read the core speed and memory speed differently. Heaven and Nvidia would get the memory right, but the core wrong. GPU-z would get the core right but the memory was cut in half. Now to go try some real testing and fire up Assassin's Creed.
I have been running with the stock A12 bios from Dell and haven't had any of those issues. I did, however, have the same problem when I was running A09. The upgrade to A12 actually helped. You could try limiting the cpu from turbo and see if that helps your fps.
GPU-z will report the real speed that the ram is actually running at, as it is DDR(Double Data Rate Double data rate - Wikipedia, the free encyclopedia- GDDR5 in our case GDDR5 - Wikipedia, the free encyclopedia) the clock is quadrupiled to obtain the final memory clock speed.
I'd use either MSI afterburner or EVGA Precesion with the OSD to display the Clocks, it will also display other usefull info like temp, GPU usage etc. However stick with NVinspector batch files for overclocking.
-
Well, at +900 memory clock is about the highest I have pushed it for testing. I can go up to about +1000 but I start getting artifacts. Past that and it starts to lock up. Although I have noticed there isn't a significant difference with moving the memory past +450/500 as far as real performance so I usually run it around there. I'm still stuck at 970mhz for core clock though, with turbo. Tried the batch files for Nvidia Inspector, and can change everything, however, it will not go past the +135 offset, no matter what I try to do with it in the batch files. And if I don't set the offset up, it won't go past the 745 default. And no luck with the batch file to increase the offset. Running version 1.9.6.9 of inspector. 3D version, with no Optimus.
The latest NV drivers cause this issue, its a problem with NVinspector and the new drivers, go back to 306? I think it was and your problems will be solved.
- 1
-
I found that to recovery flash the bios I had to put the USB drive into the port closest to the HDMI port, not closest to the user. I have a 3610QM version of the PC
- 3
-
This is the modified VBios from the Russian mod, I'm just not sure how to roll it back into the bios to flash it, maybe svl7 can help here.
-
Is it possible to increase the voltage through a modded bios then? or can at least you modify the core speed in your modded bios back to 950 for us?
-
actually a 950/2800 bios will be fine sv17. Thanks or just let me know what to edit in the bios,
-
to anyone that has bricked their board, the recovery process is here.[Request] Dell Inspiron 17r SE 7720 Unlocked Bios
-
Can we please have a 950/2475 Bios please SVL7, Thankyou
He's Dead Jim
in General Notebook Discussions
Posted
RIp my poor GTX675MX,
you were so kind to me with your locked bios chip that I had to source spares and a programmer,
flash a new chip and perform open vbios transplant surgery so I could clock past 823Mhz. Good thing I had a rework station already.
Anyway from what I can tell it seems that one of the ram chips has died a horrific death (maybe), I can still flash/read/change the bios etc so its not that.
Was running at ~1130GPU and 1230(4920DDR) on the ram, pushing for higher without thermal throttling in kombuster when everything crashed and upon restart I'm left with this.
Now go to hell you dam 675mx that required surgery to flash you vbios, I was looking for an excuse to upgrade to a 970/80M anyway so here it is.
However in the meantime(until prema gets these bios mods done) it surely will be missed.