Hi, Does anyone have, or know where I can find, a VBIOS for a 675m with the P0 and P1 clocks and voltages matched at 620/0.087v?
I'm having a few problems in some high stress games whereby I can't OC since this causes P1 and the voltage drop (0.085v) seems to be too much for it to handle- I hope.
Had the machine hang in two different games when P1 is at anything above 620 and it cuts in...
TIA.
-
MickyD1234 Notebook Prophet
-
675m92v.rom
Here's one with both P0/P1 at 0.92v -
NotebookReview.com: 580m -> 675m (by svl7)
http://forum.notebookreview.com/showpost.php?p=8459195
Sent from my iPhone using Tapatalk -
MickyD1234 Notebook Prophet
Thanks guys! I'll give it a try.
edit: That did the trick :thumbsup:
Now I can run Crysis 2 at 700 nice and stable. Temp never goes above 70C.
Curiously the fps drop in 3d in this game is much less than others. Around 10% - currently getting around 35FPS against 40 FPS w/o 3D. Very pretty, now to see how the hi-res pack impacts it...
-
The high-res texture pack won't affect frame rates, but the dx11 patch [on] will, so I'd say the former is a must. If your temps are good and you're under warranty, try out the overvolted vbios for an even bigger overclock (800 core) and more FPS.
-
MickyD1234 Notebook Prophet
Warranty is good but as this is already a replacement I'd like to avoid any more 'dell calls'.I try to 'work' an OC specific to what I want out of a game - all part of the fun
I'm having a couple of 'issues' with the game that I need to sort but I'm still trying to decide if I like the game enough to work at it. -
Check the ASIC quality with GPUz. That sounds really really low for 0.92v, but not impossible. My 460M was rated at 71.4% and I could barely hold 750mhz on the core without it flipping out on me.
-
I've been running the 0.92 over-volt bios for over a month now and when I'm gaming I switch to a 810/1875 overclock profile and my temps never go above 65'C. No problems noticed thus far.
Could someone briefly explain the P1 and P0 business please? Is there a way of checking their values? -
Nvidia inspector will show you those values, they are different speed states that the card can take. Most likely if you have not changed the P1 state your card is constantly running at 620 core in the P1 state, since the .92v bios will make it go to P1 with almost any stress at all. Thus you low temps and no problems.
Quite frankly, the .92v bios is not safe. We have shown it time and again. Your card will fail eventually using the .92v bios, if that is fine with you then carry on, but just be aware. You can do 720 stable on basically any 580m/675m at stock voltage. Some cards can do 740 stable at stock. The overvolted bios just isn't getting you that much more, and eventually your card, motherboard, or both will die. -
MickyD1234 Notebook Prophet
P1 is the first low power state and is either triggered by a power option setting allowing the card to slow down when in low usage, OR there is a high power draw on the card (the power throttle). 420/0.85v
You then have P8 which is either a very low power state like you might see in windows OR the card is overheating. The 78C. throttle. 75/0.80v
There is also a P12 which seems to be just an even slower state. 50/0.80v
These are the default values
If you use msiafterburner to get the clock speed on-screen and set P1 slightly lower than P0 you can see it trigger, along with your real-time temp.
-
Micky which vBios did you use in the end? The one by Svl7 I posted a link to? I might drop the voltage back down to stock and try that vBios. -
MickyD1234 Notebook Prophet
-
I wish I could see how you guys are keeping the temps so low. I bought a new heatsink and then found out my old heatsink WAS the redesigned model. My in-game temps are always in the high 60's and low 70's and after an hour it starts to throttle. Honestly I'm getting tired of it. I've done everything short of replacing the card and the card I doubt is causing the issue.
-
Sent from my iPhone using Tapatalk
Looking for VBios for 675m
Discussion in 'Alienware 17 and M17x' started by MickyD1234, Aug 21, 2012.